Answer from the help content you wrote
Customer support AI
Support AI drafts a reply from the pages, macros, and policies you already stand behind. If the answer is not there, it says so and hands the ticket to a person. It does not browse the open web for a policy you do not have.
Grounded replies
The first build uses a set of articles or macros you choose. Order status, hours, and shipping rules are typical. Refund exceptions and angry threads are not. Those stay in the queue.
A person in the loop
You can require approval on every send until the drafts are boring. Boring is the goal. A draft that adds a policy you did not write is a failed draft.
- A source list
- A refusal when the source is silent
- An easy handoff
Retail and restaurants
A store’s “where is my order?” and a dining room’s “are you open?” are both support, and they should not share a bot. We pick the queue that your team answers every day.
Questions
Will it close tickets by itself?
Only for the intents you mark as safe, and only after you have reviewed a sample of drafts. Refunds and account changes stay manual.
What if it is wrong?
The design assumes it will be wrong sometimes. That is why the source list and the handoff exist. We do not promise a deflection rate.
What does it cost?
Pricing on request. The audit prices the queue you would actually point it at.