Faster answers, still written for a person to send
A support coworker reads your help articles, sorts the queue and drafts replies with the source quoted. Your team decides what goes out.
The parts of support that repeat
Answers from your own articles
It searches the help articles you add to Knowledge, quotes the one it used, and says so when the articles do not cover a question.
A morning digest
A routine reads yesterday's tickets, groups them by product area and lists the most common problems.
Inbox triage
With Gmail or Outlook connected, it sorts incoming mail and drafts replies for an agent to edit.
Tickets filed for engineering
With Jira or Linear connected, it files a bug with the steps a customer described, and updates it later.
A chat on your own site
An embedded chat puts a Bot on your website for people who are members of your workspace, such as clients you invited. Their messages run with the Bot's usual approvals. See the developer page.
Where your team already talks
Your agents can talk to the coworker and approve its requests from Slack, Microsoft Teams, LINE or WhatsApp.
Nothing reaches a customer without your say
- Sending a message waits for an approval until you decide it may go without one.
- Outgoing messages and files are checked for secrets and personal data.
- Every draft, approval and refusal is in the audit trail.
Planned, not yet available: an email address that hands what it receives to a Bot, and a Bot that answers when mentioned in shared Slack or Teams channels. Their status is on the roadmap.
Put your first coworker to work
Sign in, open a channel, and ask it to do something real on the web.
Open the workspace→