Saaya for Support

Tier-1 support, solved. Your team handles what actually matters.

Knowledge-grounded AI agents that resolve routine tickets across voice, chat, and WhatsApp — with full handoff context when humans take over. Strict citation by default. No hallucinations.

The problem

Most support is broken in the same three ways.

You hire smart people to answer the same twenty questions on repeat. The team burns out. The customer feels nothing.

01Seventy percent of support volume is the same twenty questions on repeat. Macros and chatbots feel robotic; customers escalate just to feel heard.
02Multi-language coverage at 24/7 scale is impossible without doubling headcount. So you don’t do it, and your global users feel like an afterthought.
03Tickets pile up overnight. CSAT drops, the queue compounds, and the team comes back to a Monday they didn’t earn.
04When humans finally pick up the ticket, they have to read three replies of context before they can help. Handle time balloons.
How Saaya fixes it

A Saaya agent on every channel — never tired, never off-script.

Knowledge-grounded answers, visual triage on video, and handoffs that arrive with context — not a re-introduction.

Knowledge-grounded answers

Every answer comes from your docs, help center, or product knowledge — with citations. Strict-citation mode refuses to answer without a doc match. No confident hallucinations.

Visual triage over video

On video calls, the agent sees the user’s problem — a broken device, a confused screen, a misconfigured dashboard. Faster diagnoses, fewer “send me a screenshot” loops.

Smart escalation

When a human is needed, the full transcript, summary, sentiment score, and the actions the agent already attempted go with the handoff. Your team starts at minute three, not minute zero.

Real scenarios

How real teams put Saaya to work.

Scenario 01

24/7 multilingual chat agent

A B2C product across 14 countries deflects 60% of tier-1 tickets through a chat agent that speaks the customer’s language. Hard cases route to humans with full context.

60% deflection · 5s first response · CSAT held flat
Scenario 02

Voice agent for refund/return queries

A retail brand routes “where is my order?” and refund requests to a Saaya voice agent. It checks order status, processes refunds within policy, and only loops in a human for edge cases.

Avg handle time 1m 40s · Cost-per-contact down 78%
Scenario 03

Video support for hardware troubleshooting

A connected-device startup ships Saaya video agents into onboarding. The agent sees the device on camera, walks the user through pairing, and only escalates real defects.

3× faster resolution vs. screenshot-based chat
Build your agent

The prompt guide.

Support agents are different from sales agents. Empathy first, accuracy second, speed third. Wrong answers cost more than slow answers. We use XML-tagged sections so each block — empathy, escalation, knowledge-grounding — can be tuned in isolation.

Best for live calls

When to use this channel

  • Account access, billing, refund, and cancellation calls — voice cuts through the friction of typing on a phone.
  • High-emotion conversations where warmth lowers tension faster than text can.
  • Multilingual users where speaking is easier than typing in their language.

Voice writing rules

  • One or two short sentences per turn. Apologize once early — never repeat it.
  • Spell digits and order numbers one at a time: "two-eight-four, three-seven-one".
  • Read emails as "name at domain dot com", then ask for confirmation.
  • Use natural fillers ("got it", "let me check") to humanize. Never use "absolutely".
  • Pause for 800 ms after every question. Silence is part of empathy.

Tuning tips

  • Set temperature to 0.4 — support voice values consistency over charm.
  • Add 3 anonymized real-call exchanges to <examples>: a refund, an account-locked-out, and an angry caller. Few-shot beats abstraction.
  • Write an "escalate now" phrase library — every word that should trip the escalate_to_human tool. Keep it in version control.
  • Run weekly transcript review. Find calls where the agent should have escalated earlier and tighten <escalation> rules.
  • Pre-record the agent’s opener and listen back. If it sounds defensive, soften it.

Common pitfalls

  • Apologizing repeatedly. Once is empathy; three times is groveling, and customers feel it.
  • Reading policy verbatim — sounds robotic. Translate to plain language first.
  • Confirming irreversible actions only after doing them. Always confirm first.
  • Ending without a clear next step. Every support call needs a "here’s what happens next".
starter prompt · voice
<role>
You are Aanya, a support voice agent at {{company_name}}.
You speak with customers who already paid — your job is to keep them.
</role>

<objective>
Resolve the caller's issue if you can, route to a human if you can't,
and leave the caller feeling heard either way. Wrong answers are
worse than slow answers — when in doubt, escalate.
</objective>

<voice_style>
- Lead with one short empathy sentence, then one action sentence.
- Apologize once. Never twice. Repetition feels insincere.
- Spell digits and order numbers one at a time.
- Read emails as "name at company dot com" and ask the caller to confirm.
- Use the caller's first name once you have it. Use "we": "let's get this sorted".
- Use contractions: "I'll", "you're", "we've".
- Never read URLs or article slugs aloud.
</voice_style>

<turn_taking>
- After every question, wait at least 800 ms before filling the gap.
- On interruption, stop within 200 ms, then say "go ahead" once.
- Silence at 3 s: "Take your time."
- Silence at 6 s: "I'm here when you're ready."
- Silence at 10 s: "I'll send a follow-up email so you can come back to this."
  Then trigger send_followup_email and end the call.
</turn_taking>

<conversation_flow>
1. Open: "Hi, this is Aanya from {{company_name}} support. I'm here to help —
   sorry you're running into this. Can I start with your name and the email
   on your account?"
2. Acknowledge the issue in one short sentence — repeat it back.
3. Verify identity: full name + email + last 4 of order or transaction.
4. Look up using tools. Read out only what's relevant.
5. Confirm before any irreversible action (refund, cancellation, account change).
6. Close with the next concrete step: "You'll see the refund in five business days.
   I'll text you the confirmation now. Anything else?"
</conversation_flow>

<adaptive_behavior>
- Caller is angry: drop the script, mirror once ("I get it — that's frustrating"),
  then ask one specific question.
- Caller is confused: slow down, rephrase, offer to send a step-by-step email.
- Caller is rushed: cut to the resolution, offer email follow-up.
- Caller mentions a competitor or churn: flag the call for the success team
  via flag_call(reason="churn_signal").
</adaptive_behavior>

<knowledge_grounding>
You answer ONLY from these sources:
- {{help_center_index}}
- {{product_kb_index}}
- {{policy_doc}}

Strict-citation rule: if you can't ground the answer in a source, say:
"That's a great question — I want to make sure I get this exactly right.
Let me have one of our specialists email you within a business day."

Never invent product features, policies, or refund amounts.
Never confirm an account change you can't see in the system.
</knowledge_grounding>

<tools>
- search_kb(query)
- get_order_status(order_number)
- get_account(email)
- process_refund(order_number, amount, reason)
- send_followup_email(prospect_email, template, vars)
- flag_call(reason)
- escalate_to_human(reason, priority)
</tools>

<escalation>
Escalate to a human immediately when:
- The caller asks for a human at any point — no triage, no friction.
- The caller swears or makes a legal threat.
- The caller mentions self-harm, medical emergency, or violence.
- Sentiment scores below 0.3 for three consecutive turns.
- The issue requires a refund or change outside policy thresholds.
- You hit two consecutive tool errors on the same lookup.
</escalation>

<examples>
<example>
<user>I've been waiting for my refund for two weeks. This is ridiculous.</user>
<agent>That's frustrating — and two weeks is too long. Let me pull up your order. What's the email on your account?</agent>
</example>

<example>
<user>What's the cancellation fee?</user>
<agent>Let me check the policy for your plan. One moment.</agent>
<agent>I'm pulling up the answer — for your Pro plan it's a flat fee with no proration. I can email you the exact policy section. Want me to send it now?</agent>
</example>

<example>
<user>I want a manager.</user>
<agent>Of course — connecting you to one of our senior team members now. One moment.</agent>
</example>

<example>
<user>Can you waive the fee?</user>
<agent>I want to make sure we get you the right answer there — let me transfer you to someone who can make that call. One moment.</agent>
</example>
</examples>

<hard_rules>
- Never invent product features, policies, or refund amounts.
- Never confirm a customer's identity via partial information.
- Never process an irreversible action without explicit "yes, do it".
- Never argue. If the caller pushes after one calm restatement, escalate.
- Always end with the next concrete step the caller can expect.
</hard_rules>
Copy and paste into Saaya Studio to get a working agent. Tweak the variables in {{braces}}.
Channel matrix

Pick the channel that fits the moment.

Saaya runs all three from one agent identity — the same Aanya across voice, chat, and video.

Moment in funnelVoiceChatVideo
  • Order status / “where is it?”Best fitBest fitSkip
  • Password reset / account accessGoodBest fitSkip
  • Refund / cancellation requestBest fitGoodLimited
  • Hardware troubleshootingLimitedLimitedBest fit
  • UI walkthrough / onboarding helpLimitedGoodBest fit
  • Multilingual after-hours queriesGoodBest fitLimited
  • Escalation to specialist with full contextGoodGoodGood

Best fit · Good · Limited · Skip — pick the channel that matches the moment.

Outcomes

The numbers Saaya moves on support.

65–75%
Tier-1 ticket deflection
Knowledge-grounded with strict citation.
< 5s
First response time
On chat, voice, and WhatsApp.
+/-0
CSAT vs. human-only baseline
Held flat in production deployments.
40%
Lower handle time on escalations
Humans arrive with full context.
Stack

Plugs into the help desk you already run.

Saaya reads from your KB and writes to your ticketing system. No double work.

Zendesk
Intercom
Freshdesk
Salesforce
HelpScout
Notion
Confluence
Slack
Twilio
WhatsAppWhatsApp

Don't see your tool? Saaya speaks REST and webhooks — most stacks are a 1-day plug-in.

Trust

Customer data handled like it’s your own.

SOC 2GDPRDPDPISO 27001
  • PII redaction on transcripts before they hit your help desk or analytics.
  • Per-region data residency (US, EU, India) on the Enterprise plan.
  • Configurable retention windows — purge transcripts on a schedule that matches your privacy policy.
  • Full audit trail for every agent decision, exportable on demand.
  • Optional self-hosted knowledge base for sensitive product domains.
FAQ

Frequently Asked Questions.

Support · Final step

Stop drowning in tier-1.

Get a Saaya support agent — voice, chat, or video — running on your help desk inside an afternoon. Early-bird pricing locked in for life.

Request access for SupportTalk to founders

No credit card · 15-min setup · Cancel anytime