Xellvio automations
Automations that follow up so you don't have to
Draw the journey once on a visual canvas — a trigger, a wait, a condition, a text — and Xellvio runs it for every contact, day and night.
- Trigger: keyword JOIN
- Check consent
- Send SMS · welcome
- Wait 2 days
- If clicked → offer
- Else → exit
Most leads are lost in the gap between interest and follow-up
Someone fills in your form on Friday evening, or texts a keyword during a rush. If the reply comes days later, the moment has gone — and manually chasing every contact does not scale past a few dozen people.
- Follow-up depends on someone remembering to send it.
- Timing drifts, so the message arrives after the intent has cooled.
- Different people get different treatment, so results are impossible to read.
Xellvio automations turn that follow-up into a workflow: the trigger fires the moment it happens, the wait is exact, and every contact gets the same considered sequence.
A visual canvas, not a list of rules
Drag steps onto the canvas, connect them, and see the whole journey at a glance. Xellvio checks the workflow before you switch it on, so orphaned steps or missing message text are caught up front.
- Triggers for contact added, keyword received, link clicked, tag applied, date reached and list joined.
- Waits in minutes, hours or days, plus conditions and yes/no branches on contact fields, tags, consent and engagement.
- Actions to send SMS, add or remove tags, move contacts between lists, call a webhook, or exit the journey.
- Draft, activate, pause and edit safely — activation validation and autosave with undo/redo built in.
- Trigger: keyword JOIN
- Check consent
- Send SMS · welcome
- Wait 2 days
- If clicked → offer
- Else → exit
How it connects to the rest of Xellvio
Automations sit in the middle of the platform: forms and pages feed contacts in, segments decide who qualifies, SMS and email carry the message, and reporting shows what the journey earned.
What you get
Visual builder
Build, rearrange and review the whole journey on one canvas.
Real triggers
Sign-ups, inbound keywords, link clicks, tags, dates and list changes.
Precise waits
Delay a step by minutes, hours or days before the next message.
Conditions & branches
Split on consent, tags, fields or whether a link was clicked.
Personalised sends
Merge first name and custom fields; shorten links automatically.
Webhooks
Push the event to your own systems as the journey runs.
Consent-aware
Opted-out contacts are skipped, not messaged again.
Activity log
See which contacts entered, where they are and what was sent.
Ways businesses use it
Welcome new subscribers
Greet a new contact instantly, then follow up with a first-order offer two days later.
Keyword opt-in
Someone texts JOIN, gets a confirmation, is tagged and added to the right list.
Follow up sign-up form leads
A form submission starts a short sequence that qualifies the lead over a few days.
Re-engage quiet contacts
Target people who haven't clicked in 60 days with a win-back message.
Clean the list
Handle opt-outs and repeated delivery failures without touching a spreadsheet.
Date-based sends
Birthday treats, renewal reminders and appointment nudges on the right day.
Looking for your industry? See solutions by industry or start from a template.
Common questions
Do I need to write code?
No. Automations are built by dragging steps onto a canvas and filling in the message text and timings.
Can an automation reply to an inbound text?
Yes. A keyword trigger fires when someone texts a word you choose, and the reply can go out immediately.
What happens if someone opts out mid-journey?
They are suppressed straight away and the remaining steps are skipped for them.
Can I test before going live?
Yes. Save the automation as a draft, simulate the path a contact would take, then activate when it reads correctly.
Does automation traffic cost the same as a campaign?
Yes — automated messages are charged at the same per-message rate for the destination country.
Build your first automation today
Start from a template or an empty canvas, activate it, and let the follow-up run itself.