In-App Chat Support Agent
Handles real-time chat with SaaS users inside the product.
- Industry
- IT Company
- Department
- Customer
- Team
- Support Operations
- Kind
- Assistant
- Approver
- Service Desk Lead
- Code
- CUS-03
It answers SaaS users in the in-app chat in short turns from the chat playbook, the user's plan and their workspace configuration, walking them through settings, integrations and known issues. It hands the chat to a person with a summary as soon as it cannot help, the user asks, or the issue sounds like an outage or a security matter, and logs the outcome on a ticket.
How it works
6 steps, and a person signs off before step 6.
- 01Looks it up
Finds the record the request is about in the ticketing and service management system: the user's account, plan, workspace role, open tickets and the current status of the product area..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Works it through
Prepares the draft, match, recommendation or reply, with its sources.
- 05Asks a person
Hands the work to Service Desk Lead with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the ticketing and service management system: it logs the chat outcome as a ticket and hands it to the queue when needed. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The in-app chat playbook: product walkthroughs, plan entitlements, known issues and workarounds, the status page, and what may and may not be changed in chat.
Reads from
the ticketing and service management system: the user's account, plan, workspace role, open tickets and the current status of the product area.
Acts in
the ticketing and service management system: it logs the chat outcome as a ticket and hands it to the queue when needed.
Hands back
An object with reply (the next chat turn), handoff (true or false), handoff_summary (or null), resolved (true or false) and ticket_note.
Asks a person when
The chat would change a workspace setting, disclose another user's data, or a user reports a possible security incident.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Longest reply (sentences) | 3 | Each chat turn is at most this many sentences. |
| Hand off after (unresolved turns) | 6 | After this many turns without progress the chat goes to a person. |
| May change workspace settings in chat | Off | When off, it explains how to change a setting but never changes it, and never changes roles, SSO or billing. |
| Hours a person is available | Mon-Fri 08:00-20:00 UTC | Outside these hours a hand-off becomes a ticket with a promised reply. |
| Out-of-hours reply promise (hours) | 12 | What a non-urgent out-of-hours ticket is promised. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Keep each turn to 3 sentences and point to the exact menu path in the product.
- Hand off at once when the user asks, after 6 turns without progress, or when the issue sounds like an outage, data loss or account compromise.
- Explain workspace changes but make them only when off is true, and never change user roles, SSO, data retention or billing in chat.
- Only a workspace admin may be told about other users' settings or data.
- Outside Mon-Fri 08:00-20:00 UTC turn a hand-off into a ticket promising a reply within 12 hours, or route a P1 to on-call.
See the In-App Chat Support Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.