Softwr

Customer Support · head to head

Assembled vs Forethought

Assembled logo

Assembled

Customer Support

Workforce management and AI agents for support teams that run on Zendesk, Salesforce or Intercom

From
$25/month
Rated
-
Full reviewWebsite
Forethought logo

Forethought

Customer Support

AI resolution and ticket triage layered on top of an existing helpdesk

From
On request
Rated
-
Full reviewWebsite

The short version

  • Each has a real cost: Assembled the published per-agent rate is not the whole bill, because a separate platform fee sits on top and is not published, so the headline 25 USD figure understates the real cost and you still need a quote to know the total.; Forethought forethought needs roughly 20,000 historical tickets and around 2,000 a month to train usefully, so a support team below that volume is not simply a smaller customer, it is ineligible, and the sales process will tell you so late.
  • They diverge on capability: Assembled covers Volume forecasting, Forethought covers Solve.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which Assembled and Forethought actually diverge.

Attributes where Assembled and Forethought differ
AttributeAssembledForethought
Starting price$25/monthOn request
Pricing modelPer user per monthquote
PlatformsWeb, APIWeb

Identical on both: free tier (No), user rating (Not yet rated), category (Customer Support).

What each one covers

Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.

Only in Assembled

  • Volume forecasting
  • Schedule generation
  • Real-time adherence
  • Agent self-service
  • Intraday reporting
  • AI Copilot
  • AI Agents
  • BPO management

Only in Forethought

  • Solve
  • Autoflows
  • Custom Actions
  • Triage
  • Assist
  • Discover
  • AI QA and Insights
  • Solve and Analytics APIs

What people use each for

The jobs each tool is most often brought in to do.

Assembled

  • A 200-agent software support team that has outgrown spreadsheet rostering and wants forecast-driven schedules tied to Zendesk ticket historynot Forethought
  • A support operations lead who needs to model in-house agents and two BPO vendors in a single capacity plan before the next peak seasonnot Forethought
  • A subscription business that wants to measure whether an AI deflection layer actually reduces required headcount, using the same forecasting tool that sizes the human teamnot Forethought
  • A finance team that needs a defensible per-agent cost line for support tooling before a board budget review, without a three-week vendor quoting cyclenot Forethought

Forethought

  • A retailer with 40,000 tickets a year in Zendesk wants order status, returns and refunds resolved end to end without an agent, including the API calls into the order system.not Assembled
  • A support operation that already abandoned a rules-based chatbot because the decision trees rotted, and wants resolution logic that does not need rebuilding every time a policy changes.not Assembled
  • A team drowning in triage where tickets sit in a general queue for hours before a human reads them and routes them to the right specialist group.not Assembled
  • A support leader who needs to know which questions have no knowledge article behind them, ranked by the volume of tickets they generate.not Assembled

Where each one falls short

Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

Assembled

  • The published per-agent rate is not the whole bill, because a separate platform fee sits on top and is not published, so the headline 25 USD figure understates the real cost and you still need a quote to know the total.
  • Pricing AI Agents per resolved conversation while pricing workforce management per seat means the two products pull in opposite directions financially: successful deflection shrinks the seat count you are billed for and grows the consumption charge, making year-two budgeting unpredictable.
  • Long-range capacity planning and what-if scenario modelling are thinner than in NICE or Verint, so organisations doing annual headcount planning across multiple sites often end up exporting to a spreadsheet anyway.
  • There is no quality management or agent evaluation module, so a support organisation that wants WFM and QA from one vendor has to buy a second tool and reconcile two sets of agent records.
  • The product assumes a modern ticketing system as the source of truth; teams running a legacy ACD or a homegrown queue face custom integration work that the standard connectors do not cover, and forecast accuracy suffers until that data is clean.
  • There is no native mobile application, so agents check schedules, request time off and swap shifts through a mobile browser, which is a persistent friction point for hourly and contact centre workforces who do not sit at a desk.

Forethought

  • Forethought needs roughly 20,000 historical tickets and around 2,000 a month to train usefully, so a support team below that volume is not simply a smaller customer, it is ineligible, and the sales process will tell you so late.
  • Billing is outcome based per resolution on top of a platform fee, so the invoice rises precisely when the product performs, and forecasting a year of spend requires forecasting your own deflection curve.
  • Channels are tier gated: email, voice and Slack agents sit above the entry tier while the Solve API, Analytics API and knowledge gap detection are Enterprise only, and buyers routinely scope a tier that turns out not to include the channel they came for.
  • Ease of setup is the lowest scored dimension in independent reviews, with 30 to 90 day rollouts, no self-serve path and continual configuration effort to keep flows accurate, which means a named internal owner rather than a set-and-forget deployment.
  • Zendesk acquired Forethought in March 2026, so anyone running a multi-helpdesk estate on Salesforce, Freshdesk or Intercom is buying their neutral AI layer from a direct competitor of their helpdesk vendor, and should get contractual commitments on non-Zendesk connector parity.

Pricing, plan by plan

Assembled

$25/month
  • Core$25/month
    • Forecasting
    • Scheduling
    • Real-time adherence
  • Pro$45/month
    • Everything in Core
    • Advanced forecasting models
    • BPO and vendor management
  • Enterprise$75/month
    • Everything in Pro
    • SSO and SCIM
    • Advanced security review
  • AI Copilot$35/month
    • Reply drafting
    • Knowledge retrieval
    • Agent workspace embed

Forethought

On request
  • Team$undefined/year
    • Solve for chat
    • Triage
    • Standard reporting
  • Professional$undefined/year
    • Adds email, voice and Slack agents
    • Assist for human agents
    • Multibrand add-on available
  • Enterprise$undefined/year
    • Solve API and Analytics API
    • Discover knowledge gap detection
    • Multibrand up to 20 brands

Which should you pick?

Choose Assembled if

  • You need volume forecasting.
  • You work on Web, API.
  • You also want schedule generation.
Assembled review

Choose Forethought if

  • You need solve.
  • You also want autoflows.
Forethought review

Questions people ask

Is Assembled or Forethought better?
Neither clearly leads. Assembled starts at $25/month and Forethought at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Assembled or Forethought?
Assembled starts at $25/month and Forethought at On request.
Does Assembled or Forethought run on more platforms?
Assembled runs on Web, API. Forethought runs on Web.
What is Assembled best used for?
Assembled is most often used for a 200-agent software support team that has outgrown spreadsheet rostering and wants forecast-driven schedules tied to zendesk ticket history, a support operations lead who needs to model in-house agents and two bpo vendors in a single capacity plan before the next peak season, a subscription business that wants to measure whether an ai deflection layer actually reduces required headcount, using the same forecasting tool that sizes the human team, a finance team that needs a defensible per-agent cost line for support tooling before a board budget review, without a three-week vendor quoting cycle. Of those, a 200-agent software support team that has outgrown spreadsheet rostering and wants forecast-driven schedules tied to zendesk ticket history and a support operations lead who needs to model in-house agents and two bpo vendors in a single capacity plan before the next peak season are not what Forethought is typically brought in for.
What can Assembled do that Forethought cannot?
Assembled covers Volume forecasting, Schedule generation, Real-time adherence, Agent self-service. Forethought covers Solve, Autoflows, Custom Actions, Triage.

Answered from the vendors’ own pages

Assembled: Does Assembled publish its real total cost?

It publishes per-agent tier rates of 25, 45 and 75 USD per month but adds an unpublished platform fee, so budget for the seat rate plus a fixed annual platform charge that you must ask for.

Forethought: Does Forethought replace my helpdesk?

No. It installs on top of Zendesk, Salesforce Service Cloud, Freshdesk or Intercom and reads their ticket history. You keep paying for the helpdesk.

Assembled: Can I buy the AI agents without buying workforce management?

Yes. Assembled sells WFM, AI Copilot and AI Agents as separately purchasable products, and AI Agents are billed at 0.65 USD per resolved conversation rather than per seat.

Forethought: Is there a free trial?

No. Forethought runs a Proof of Value programme instead, which is a scoped paid or sales-managed pilot rather than a self-serve trial.

Assembled: Is it suitable for a voice-first call centre?

Less so. The forecasting and scheduling are built around omnichannel ticketing volume, and voice-heavy operations running a legacy ACD will find the integration and intraday voice controls weaker than a traditional WFM suite.

Forethought: Is it still sold to non-Zendesk customers after the acquisition?

Zendesk says yes. Treat that as a commitment to negotiate rather than a guarantee, and ask for connector parity terms in writing.

Assembled: How long does implementation take?

Assembled states typically one month or less, which is realistic when your helpdesk is Zendesk or Salesforce and historical data is clean.

Forethought: How is it priced?

Platform access fee plus outcome-based charging per resolution, with usage overages. Nothing is published; every deal is quoted.

Share

Related pages

More on Assembled

More on Forethought

Keep looking

Other head to heads