Automations
A few rules that earn their keep.
Support-specific automations only — routing, escalation, alerts and follow-ups. Deliberately not a general workflow engine, because the general version becomes an unmaintained graph nobody dares change.
Not a workflow builder
A blank canvas with triggers and branches is how small teams build something they cannot debug a year later. These rules are specific, named and few.
Every rule says what it did
An action taken by a rule appears on the case timeline naming the rule. Nothing in this product acts anonymously.
Nothing irreversible runs unattended
Rules route, alert, escalate and prepare. Refunds, cancellations and anything touching money or access wait for a person, always.
In this area
5 pages under Automations.
Each one is its own surface in the product, and each one is here because it does something the others do not.
Routing rules
Billing to Finance, technical to the right team, VIPs to their owner.
ReadEscalation
What happens when something is about to go wrong.
ReadAccount alerts
Telling the account owner when their customer is in trouble.
ReadFeedback follow-up
Negative feedback becomes a real follow-up, not a statistic.
ReadSuggesting an incident
When several similar cases arrive together, propose grouping them.
ReadThe rest of Resolivo
This is one part of one loop.
Take better care of every customer.
Give your team the context, knowledge and AI they need to resolve problems properly — and know who needs attention before they ask.
Keep the mailbox you already use · The AI is never metered · [email protected]