Write the house rules once: what runs on policy, what waits for approval, what escalates to a human instantly. The routine handles itself and logs every step; the strange stuff reaches you with the whole story.
No credit card required. Cancel anytime.
Every request hits your rules first. Watch six of them route: four run on policy, two earn your attention.
Routine runs on rules you wrote. Edge cases reach you with the whole story.
The $50 line, the topics that always escalate, the hours agents answer - all of it is a setting you own. Change a number and the junction reroutes from the next request on.
The Operations systems land inside a queue that is already running: the same policies, approvals, and run log under every channel.
Help Desk and Live Chat, answering from your pages
Assistant · policies · Approvals queue · escalations · kill switch · run log
Scheduling that guards your calendar's rules
Customer Success watching accounts going quiet
Order questions answered from live store data
Live Chat and Help Desk are built end to end and finishing hardening QA - full detail below, chipped honestly. The Workflows engine underneath them is live for every tenant today.
Operations covers every support channel as its systems land - and the policies, approvals, and run log they route through are in the base today.
Caps at $599/mo for everything · failed actions never cost a credit · 7-day trial with 500 credits.
Rules you write: dollar thresholds, topics that always escalate, hours, tone triggers. Anything that doesn't match a rule defaults to you - the agent never guesses.
The spine every channel routes through: the Assistant, policies, the Approvals queue, escalations, and the run log. Help Desk, Live Chat, Scheduling, and Customer Success are rolling out on the roadmap; order operations already run in the Ecommerce module.
Your Knowledge Base and live data your systems hold - tracking, invoices, order history. Answers cite their source; if the answer isn't there, the request escalates instead of guessing.
Every action is in the run log with the rule that allowed it, replayable. Tighten the policy, and the change applies from the next request. One tap pauses everything.
Rules you wrote, a queue you can read, and a kill switch you'll probably never need.
No commitment. Month-to-month, cancel anytime.