Where do the answers come from? Won’t it make things up? +
It answers from the knowledge sources you upload — your policies, FAQs, and documents. Every answer carries a confidence score; below the threshold you set, it escalates instead of answering. And the ticket shows the exact source the answer was pulled from, by name.
How are category and priority decided? +
From the conversation itself: the type of issue, the customer’s tone, and the product or service being discussed. You define the categories, the priorities, and the SLA policy for each one. Your team can change any classification — and the change is logged.
When does the SLA clock start and stop? +
It starts from the customer’s first message, pauses while the ticket is waiting on their reply, and resumes the moment they answer. It respects the business hours you set. If a breach gets close, the conversation is reassigned to an available agent and the supervisor is notified.
What happens to questions the agent cannot answer? +
They are tracked in analytics as knowledge gaps: which question stopped it and how often it repeated. Each one comes with a suggested addition to your knowledge base — with your approval, never automatically. After you add it, you can see its effect on the same metric.