Ada and Helpdesk Coopetition

This dynamic means the AI agent layer and the help desk layer are separating into two distinct control points. Ada can answer routine questions in chat, then hand the thread into Intercom or Zendesk when a refund, exception, or sensitive case needs a human. That lets customers keep their existing ticket queues, agent seats, reporting, and knowledge base, while adding a new automation layer on top.

• In practice, the stack looks like this, Ada handles front line resolution, the help desk remains the system of record. Human agents still work inside Intercom or Zendesk, see the transcript, and take over escalations there. Open APIs make the handoff possible without forcing a rip and replace.
  1 sacra 3 sacra 4 sacra
• This creates coopetition because the same platforms Ada plugs into are also moving up into AI agents. Intercom sells Fin both inside its own suite and as a standalone product for teams already on Zendesk or Salesforce, while Zendesk keeps expanding from ticketing into automation and broader CX workflows.
  1 sacra 3 sacra 4 sacra
• The buyer tradeoff is clear. A best of breed agent on top of an existing help desk offers faster deployment and preserves established workflows. A bundled platform like Intercom promises fewer vendors and tighter packaging. Ada even migrated its own support stack off Zendesk to Pylon, showing the underlying help desk layer is still contestable.
  1 sacra 2 sacra 3 sacra

Over time, more of the value will shift to whoever owns resolution outcomes, not just tickets or seats. That pushes Ada, Intercom, and Zendesk to expand across the boundary, AI agent companies moving downward into workflow systems, and help desk incumbents moving upward into autonomous resolution, until the strongest vendors can do both.