Skip to content
Agents tracked: 271 Downloads (7d): 219M up 6.2% GitHub stars: 5.5M VS Code installs: 151M Releases (7d): 307 Agent status: 1 with issues Updated Oct 8, 2026
Case study Perplexity

How Perplexity gave its support team control of its Decagon AI agent

Perplexity's support team uses Decagon to run an AI agent named Sage across chat and email. Support operators write and refine its procedures in natural language, and the team reports a high deflection rate as volume grows.

The problem

Perplexity started with support handled through a single email channel. As the product grew, daily support volume rose 269% and users expected near-immediate replies across time zones. The team needed to decide which work could be automated consistently and which needed human judgment, without waiting on engineering for each policy change.

How they did it

  1. Deploy Decagon on chat and email support channels.
  2. Have support operators write policies and workflows as Agent Operating Procedures (AOPs) in natural language.
  3. Use Duet to turn an existing policy document into a first-draft AOP, then review, tighten and test it.
  4. Use Duet to surface gaps and edge cases in existing AOPs before updating them in production.
  5. Monitor user intent, escalations and sentiment in Decagon reporting, and ask Duet which AOPs have different deflection.
  6. Keep complex cases such as escalations, incidents, enterprise billing and privacy requests with human agents.

Results

  • As reported by Decagon, Perplexity reached a 78% deflection rate over the last 30 days.
  • As reported by Decagon, the agent supports 70+ user intents.
  • As reported by Decagon, average daily support volume rose 269% compared with last year.
  • Operators can change procedures directly instead of waiting for an engineering ticket, and Duet helps them spot edge cases.

As reported by the source (Decagon customer story); AgentGid did not measure these figures.

Takeaway. Let the people closest to customers write and edit the agent's procedures directly, and use usage reporting to decide which workflows to improve next.
AgentGid's take

This suits a support team with steady multichannel volume, operators comfortable writing and testing procedures in plain language, and a sales process they can work through, since Decagon has no public pricing. Treat the 78% deflection and 269% volume figures as Decagon-reported, not independent. For a smaller or cost-sensitive team, Rasa (Free) is open source, though it is limited to 1,000 external conversations a month.

The agent used here

Similar use cases