Automations
Build workflows around how your business actually operates.
Triggers, conditions, and actions in plain business language — reviewed, versioned, and different per service, location, or team.
Workflow
Active- WhenA new inquiry mentions a repair or replacement
- IfLocation is inside the service area AND urgency is under 7 days
- ThenOffer site-visit slots and mark the lead high priority
Workflow
Active- WhenA conversation arrives outside working hours
- ThenCapture details, set follow-up for 8:00, notify the morning team
Workflow tools shouldn’t need a developer on call
Routing and follow-up rules change with your business — seasonally, per location, per service. Trestelo keeps those rules readable and editable by the people who run the operation.
How automations run
Define the trigger
“When a new inquiry mentions a repair” — events from conversations, leads, and bookings start workflows.
Add business conditions
“If it’s inside the service area and urgent” — conditions read like your operations manual.
Choose the action
Offer slots, escalate to a person, set priority, notify a team, or deliver the lead to your CRM.
Review, publish, observe
Changes are drafted, reviewed, and versioned — you can see what changed, when, and by whom.
What you get
Plain-language rules
When / if / then — readable by managers, not just admins.
Versioned configuration
Draft, publish, and roll back agent behavior with a full change history.
Per-workspace variation
Different locations or business units run different rules under one account.
Working hours and routing
Time-of-day behavior, escalation targets, and notification rules per workspace.
Where teams use it
- Escalating high-value inquiries straight to senior staff
- Different qualification flows per service line
- After-hours capture with morning follow-up queues
Human control: Nothing goes live without publish. Every version is kept, every change attributed, and rollback is one action.
Common questions
Do I need technical skills to edit workflows?
No. Rules are expressed in business language. Deeper customization is available, but the day-to-day configuration is built for operators.
Can we test changes before customers see them?
Yes — changes are drafts until published, and the version history shows exactly what changed between releases.
Can different locations run different rules?
Yes. Each workspace has its own automations, working hours, routing, and knowledge.
See automations on your workflows.
Book a personalised demo and walk through your channels, qualification rules, and handover setup.