All features
AI agents

Give your AI assistant clear instructions and a defined role

Configure an assistant for each inbox using your business knowledge, preferred tone and handoff rules. Decide where it can respond and when a human should take over.

Choose when the assistant repliesSet the knowledge policyKeep a route to your team
AI agentsPRODUCT SCREENSHOT
Actual ai agents interface in a sample workspace
Actual product interface with sample workspace data
IN YOUR WORKSPACE

What your team can do

Choose when the assistant replies

Use the inbox response policy to prioritize AI, prioritize people or let the assistant respond when operators are unavailable.

Set the knowledge policy

Choose strict, balanced or open behavior and write the assistant's instructions. Maintain the knowledge sources that inform its answers.

Keep a route to your team

Configure handoff keywords, channel eligibility and response limits. Operators can also control the bot for an individual conversation.

AI response policyPRODUCT SCREENSHOT
Actual ai response policy interface in a sample workspace
Actual product interface with sample workspace data
FROM SETUP TO DAILY USE

Review the assistant's settings and knowledge policy

  1. Add and review the knowledge sources for the selected inbox.

  2. Set the assistant's instructions, tone, eligible channels and handoff policy.

  3. Test representative questions before enabling automated responses.

BEFORE YOU START

A closer look at how it works

Can I keep a channel under human support?

Yes. The inbox lets you select the channels where the bot is allowed to respond and configure the response priority.

Can I see the interface before choosing a plan?

Enlarge the product screenshots on this page or explore the interactive workspace demo. The demo uses local sample data; plan availability is listed on the pricing page.

Explore the workspace demo

Choose the workspace that fits your team

Compare the available plans and decide which capacities your support team needs.

Compare plans

Product screenshots use sample data; form examples are not necessarily enabled.