The difference between an operator and a chat that waits for a question is in the parts.
- Function
- Its specific job in the operation — support, recover, handle post-sale, prospect. Each function has its own mission: the recovery one knows which cart stalled; the post-sale one knows which strategy fired.
- Context
- What it sees to work. An agent that talks to a customer only sees the contact from its own conversation, and sees stock as "in" or "out" — never the count.
- Knowledge
- Two layers: the Company Brain (21 sections, applies to everyone) and the agent’s own base — questions and answers, PDFs, spreadsheets, persona, tone, objective.
- Rules
- Five come out of the box; yours go into the Brain. Discount and stock limits are locked in the code: if the agent tries, the system refuses.
- Tools
- By role, as a privilege: search the base, view and create a deal and a task, transfer to a person, apply a tag, look up a product, check stock, calculate a quote, record an order. No agent that talks to a customer has a reporting or financial tool.
- Triggers
- What wakes it up: a message, a stalled cart, a paid order, a product running out by estimated consumption.
- Ready-made strategies
- 50 recovery angles, over 20 repurchase strategies — switched on with a toggle, with a preview, no writing from scratch.
- Transfer
- Over 30 situations to bring in a person, in 8 groups, each with a toggle and a destination. Your own situations too.
- Schedule
- Respects the team’s hours: within them it stays on reserve; outside them, it answers on the spot.
- Scoreboard
- Measured by what it returned — replies and paid sales — by angle, by strategy, by attempt.