Build your first automation
Automations are trigger → condition → action. Keep each flow single-purpose; three small flows are easier to debug than one branching monster.
- Pick a trigger — inbound message, keyword, form submission, tag change or schedule.
- Add conditions — channel, contact attribute, consent state, business hours.
- Add actions — send a template, assign a team, set an attribute, call a webhook.
- Test in draft against a test contact.
- Publish and watch the run log for the first day.
Common first automations
- Out-of-hours acknowledgement with expected response time.
- Keyword routing: BILLING to finance, HELP to support.
- Escalation when a conversation has been unanswered past your SLA.
Steps at a glance
- Pick a triggerChoose what starts the flow: inbound message, keyword, form submission, tag change or schedule.
- Add conditionsFilter on channel, contact attribute, consent state or business hours.
- Add actionsReply with a template, assign to a team, set an attribute, or call a webhook.
- Test in draftRun the flow against a test contact before publishing.
- Publish and monitorPublish, then watch the run log for the first day of live traffic.
Next step
Bring this to your enterprise stack
See how a dedicated Arino One instance — deployed in your region (EU, NA or APAC) — would sit inside your operation. Architecture, DPA, and rollout plan walked through live.