Our read
Think of Forethought as three layers on top of your existing helpdesk: Triage labels and routes, Solve answers customers, Assist supports the human who takes over. Upwork's vendor-published case shows all three in use but not how Solve hands over to a person. YNAB's describes that handoff for email.
Start from the helpdesk you already run
Forethought does not replace your ticketing system. The vendor describes agents that learn from past tickets and help center content and work with the existing help desk. That makes the first question practical: where do your tickets live today, and which of the four agents (Triage, Solve, Assist, Discover) do you want touching them?
Upwork's vendor-published story shows the pattern. Solve runs on the chat widget and on email, while Assist, Discover and Triage sit around the help desk agents already use. ActiveCampaign's story is similar: Assist is a browser extension inside Zendesk, and Solve answers from the help center knowledge base.
Triage: labelling and routing before a person reads
At Upwork, Triage uses historical ticket data to predict and classify new tickets, and routing then runs through the capabilities Upwork already had. Triage also tags each ticket's sentiment as positive, negative or neutral, and the team uses the topics that attract negative sentiment to decide which content and workflows to build next.
For agents, the change is less manual tagging and fewer clicks per case. Upwork reports 500K auto-classifications applied and 90% accuracy and coverage on new tickets. These are the vendor's published figures from one deployment, and the case study does not give a test method, so treat them as a claim to verify on your own tickets.
Solve: the answer the customer sees
Upwork replaced a keyword-and-decision-tree chatbot that had to be trained workflow by workflow. With Solve, the chat widget interprets the meaning of the question and surfaces an answer from support documents, and Solve Email does the same for long messages. Workflow Builder lets the team design short guided flows, but a workflow cannot be created until an intent has been trained for it.
One caution on the numbers: the same Upwork page gives a 52-65% average self-serve rate and also 75% for the chat widget, and the vendor homepage shows 65%. The page does not reconcile them, so none of these should be used as a benchmark.
Actions: from an answer to a finished task
The more consequential step is Solve acting on a request. MeUndies built a cancellation flow with Forethought's Autoflows and Action Builder: it checks elapsed time since the order, cancels in Shopify if it is early, and otherwise checks the logistics provider and NetSuite to see whether the order can still be intercepted. The team also set high, medium and low deflection paths, giving more conversations to humans when agents have capacity. Those results, including 80% containment on chat, are MeUndies' account as published by the vendor.
ActiveCampaign describes the same step from the staffing side. Autoflows take action inside tools such as CRMs and help desks, and the company now has a small team dedicated to building these backend workflows. Plan for that ownership: actions need someone who maintains them.
Assist and the handoff to a human
Assist is the human-facing layer. At Upwork it reads the open ticket and shows relevant knowledge articles, past cases, macros and notes inside the help desk, replacing the habit of keeping a chat open next to twenty help center tabs. Agents can also save their own templates and notes, which are suggested on related future tickets.
The Upwork story does not describe how a conversation moves from Solve to an agent. YNAB's does, for email: if a person is needed, the conversation goes to the next available agent with full details. It does not say whether Triage models influence that routing, so that remains a question for the demo.
An editorial suggestion, not a vendor feature: during a pilot, take tickets Solve could not finish and check what the agent actually sees on arrival, and whether the customer has to repeat anything.
After the Zendesk acquisition: what to ask
The usedby overview dates Zendesk's acquisition of Forethought to March 2026. Two recent vendor case studies, MeUndies and RemoteLock, already use the name Forethought AI Agents by Zendesk.
The sources do not say what the acquisition changes for teams on other help desks, for contracts or for pricing. Ask directly: will your current helpdesk stay supported, and how are the contract and data terms affected?
Method and limits
2026-11-05
This dated snapshot counts distinct companies in public customer evidence. CONFIRMED means a case study, named testimonial or press source; DECLARED means the company itself told usedby; OBSERVED means a vendor listing; SIGNAL means a job post. All four count, but their strength differs. Removed and unlevelled lines are excluded. Examples are a capped selection verified within 90 days. Vendor facts are sourced records checked within 60 days. Coverage is uneven and missing evidence is unknown. These figures measure neither market share nor product performance; capture dates are not adoption dates.
