Relevance AI
Relevance AI
ZendeskIntercomSlackNotion

Tickets understood before they ever reach a queue

Support Triage reads every inbound ticket, resolves the ones it can safely, and routes the rest to the right owner with the diagnosis attached.

New ticket · login loop
Support Triage

Enterprise customer reporting a login loop. Reading their setup before this sits anywhere.

Reading the ticket and account history3s

They are on SAML SSO, and the loop started after a server migration yesterday. That pattern is familiar.

Searching known issues4s

Confirmed: the documented SAML clock-skew issue. Same symptoms, same trigger, and we have a proven two-line fix.

Replying with the fix2s
Resolved without touching a queue. The "login loop" was the documented SAML clock-skew issue, triggered by yesterday\u2019s server migration, so I sent the two-line server fix and confirmed it worked. I also found 3 similar tickets from enterprise accounts this month and flagged the pattern to engineering.

How it works

New ticket · login loopNew chat · billing errorTicket reopened · RidgelineP1 flagged · enterprise
Fix sent · known issueRouted to auth teamRepro escalated to engPattern flagged · 3 tickets

Triggered by your support inbox

Every ticket that lands in Zendesk or Intercom gets read immediately, whatever the hour. Nothing waits for a human to notice it.

Diagnoses before it routes or replies

It reads the full conversation, the account’s history and your known issues, then decides: resolve with a proven fix, route with evidence, or escalate with a repro. Never a guessed answer.

Acts in your support stack

Replies, priorities and routing happen in the ticket itself; escalations and cross-ticket patterns go to engineering in Slack with the evidence attached.

Without Relevance

With Relevance

Tickets wait in a queue until an agent picks them up, however urgent they are.

Every ticket is read and understood the moment it arrives, day or night.

The same documented bug gets rediscovered from scratch by whoever picks it up.

The agent recognizes documented issues from the symptoms, even when the customer describes them differently, and replies with the proven fix.

Tickets bounce between teams because the first router went off the subject line.

The agent diagnoses before it routes, so the ticket lands with the right owner the first time, evidence attached.

Whoever wrote the angriest subject line gets P1.

Priority follows actual impact: what is broken, for whom, and what it blocks, with the reasoning on the ticket.

A plausible-sounding fix gets sent to close the ticket, and makes things worse.

The agent never guesses a fix. Unknowns get escalated to engineering with a clean repro instead of a wrong answer.

Five customers hit the same regression and nobody connects them for a week.

The agent connects similar tickets as they arrive and flags the pattern to engineering while it is still small.

Held to a quality bar, on every run

Every reply and routing decision is checked against eval test cases written for this exact job before it reaches a customer. If a run fails the bar, it never ships.

Support Triage

Pass rate · last 14 days

Sampling 2% of live runs · 94% passing this week

Fixes are proven, never guessed96%
Routing follows the diagnosis, not the subject line93%
Priority reflects actual impact94%
Repeating issues get flagged as patterns91%

Train your agent like an employee

Onboard it with your playbooks and correct it in plain English. It learns the lesson for good, and nothing changes until you approve it.

Support Triage
Instructions updated
Tool added
Known issues search
13 evals added
Fixes are proven, never guessedRouting follows the diagnosis, not the subject line+11 more
Publish version 4
PDFSupport Runbook.pdf240 KB
Triage every ticket the way this runbook lays out.
Read Support Runbook.pdf. Updated my instructions, added a known issues search tool, and wrote 12 evals to check every run.
If you are not certain of the fix, do not send one. Escalate with a repro instead.
Understood. I added an eval that fails any reply containing an unverified fix, so uncertain answers now escalate instead of shipping.
Teach it something new…
Ask

Built for enterprise teams

Run agents on your real data with the access controls, audit trails, and residency guarantees enterprises require all built in.

Monitoring

Real-time visibility into every agent’s activity, performance, and cost.

RBAC

Control who can use, build, edit, and deploy agents.

Data residency

Multi-region deployment keeps your data within your required geography.

Version control

Full version history on every agent. Roll back to any previous state.

Audit logs

Every action, every decision, every tool call logged and exportable.

Human-in-the-loop

Set approval gates on any action or allow agents to ask questions.

SSO / SAML

Enterprise single sign-on with SAML 2.0. Centralize identity & access.

PII masking

Detect and redact personally identifiable information.

SOC 2 Type IIGDPROTEL & Delta Sharing
KPMG
"The ability to be vendor agnostic and the ability to scale across a breadth of functions is a really key feature."

Levi Watters

Partner, KPMG Australia

Read more
Autodesk
"The key for us was how we can modularize industry knowledge and the best playbooks, and apply it."

Allen Roh

Senior Marketing Manager, Autodesk

Read more
Canva
"We're looking for every place where AI can allow sellers and customer success reps to be more engaged with customers."

Rob Giglio

Chief Customer Officer, Canva

Read more
"The ability to be vendor agnostic and the ability to scale across a breadth of functions is a really key feature."

Levi Watters

Partner, KPMG Australia

Read more

Team it up with more customer success agents

Deal won
  1. 1
    Handoff brief sent
  2. 2
    Intro email sent
  3. Kickoff booked

Customer Transitioner

Hands new customers off from sales to success.

Kickoff call done
Data imported
8 seats activated
Go-live Friday

Onboarding Guide

Drives new customers through every setup step.

Renews · +24%Push multi-yearFlat renewal

Renewal Manager

Tracks renewals and preps the motion early.

Seats
New team
Usage
Sponsor
Upsell

Upsell & Cross-Sell

Spots upsell and cross-sell potential per account.

Q2 Review

QBR Prepper

Assembles QBR decks with the metrics that matter.

Usage dipped
  1. 1
    Nudged low-usage users
  2. 2
    Emailed setup guide
  3. Enablement booked

Adoption Tracker

Watches feature usage and nudges the gaps.

72
Apr
55
May
42
Jun
Trigger exec check-in

Churn Risk Detector

Flags at-risk accounts and suggests next steps.

Every agent you add shares one stack

These agents all run on one platform: one gateway, one router, one eval suite, one audit trail. Every agent after the first ships faster.

  • Triggered by key events or signalslike Zapier
  • Given access to contextlike Zep
  • Connected to your appslike Composio
  • Access to all LLMslike OpenRouter
  • Performance evaluatedlike Braintrust
  • No-code agent builderlike Dust.tt
  • Coordinated into teamslike CrewAI
  • Chained into multi-step processeslike n8n
  • Kept alive through long-running worklike Temporal
  • Traced at every step of every runlike Langfuse

Put the Support Triage to work this quarter

We partner with enterprise teams to take this work off their plate. An agent built with you, proven against your quality bar, and live in weeks.