Control plane
The bot runs inside a real support workflow.
The important difference is not just answer quality. The AI is wired into the
same operational layer your team already uses for queue management, follow-up,
and auditability. That means you can review what happened, route it, and keep
working the issue after the bot's first response.
- Conversation starters give the bot a structured opening path instead of a blank box
- Handoffs land inside the ticket and transcript workflow with reason codes and summaries
- Macros, saved views, snooze, and CSAT keep the post-bot work manageable for the human team
- Signed webhooks and visitor events let engineering connect the bot to CRM, alerts, or internal tools
Automation surface
Starter prompt → identify intent
Bot answer + cited source
Handoff summary + reason code
Ticket reply / macro / CSAT loop
Webhook to CRM or alerting