Customer service automation without writing code
Greet, route, tag, say when you will reply. Eleven triggers and eighteen actions on a canvas do the routine, and people keep the judgment.
No credit card. Live in minutes.
When a customer opens a new conversation
Runs once, on their first message.
Rules
The channel is website chatEmma: Was I charged twice? I need a refund.
If the message contains
Raise a ticket
Turn the conversation into tracked work
BillingTicket #148 raised and assigned to Billing
Ask with buttons
What is this about?
What you can automate.
The routine part of support, built on a canvas from triggers, rules and actions, with the judgment left to people.
Start when
New conversation
Page visited
Message received
Customer goes quiet
Teammate goes quiet
Assigned
Ticket raised
Ticket changes state
Then
Message
Reply buttons
Let the AI answer
Tag conversation
Assign
Raise a ticket
Add a tag
refundTrigger
Rules
All rules must match for the workflow to run.
Let the AI answer
Hand the reply to your AI agent
Templates
When nobody answers
Every run shows on the conversation
A workflow is not a black box. What it sent, what it tagged and where it put the conversation are all there in the thread, so the person who picks it up knows what already happened.
- Every step a workflow took shows on the conversation, in order.
- Tags, priority and the owner it set are the same ones your team uses.
- Whatever it does not close lands in Unassigned for a person.
Emma Wright
Website chat · 2 minutes ago
Start from a workflow that already works
Fourteen templates in the builder, each a saved workflow you open, adjust and turn on.
Reply outside office hours
Says when you will reply, from your availability schedule.
Triage issues to teams
Asks what it is about and assigns to the right team.
Let the AI answer first
Hands website chat to the agent, people for the rest.
Tag conversations containing keywords
Labels refunds, bugs and cancellations as they arrive.
Ask for a rating when a chat closes
Sends the star card once the conversation is resolved.
Chase stale conversations
Nudges a customer who went quiet before closing.
Raise a ticket for bug reports
Turns a message with a bug in it into tracked work.
Notice visitors on your pricing page
Opens with an offer to help when someone lands on pricing.
Flag customers left waiting
Raises the priority when your team has not replied.
Building a workflow
- Step 1
Pick a trigger
For example, when a customer opens a new website chat.
- When a customer opens a new conversation
- When a customer sends a message
- When a customer goes quiet
- Step 2
Add rules and actions
Only outside office hours, then send a message with the expected reply time and tag the conversation.
Office hoursisoutsideSay when we'll replyTag conversation: after-hours - Step 3
Turn it on and watch the inbox
Runs are visible on the conversation. Everything the workflow does not close lands in Unassigned for a person.
Reply outside office hoursLive128 runsLast run 4 minutes ago, on Emma's chat
What is customer service automation?
Software that handles the repeatable part of support on its own: greeting, asking what a message is about, routing it, tagging it, saying when someone will reply, and answering the questions your content already covers.
The judgment stays with people. A good automation makes the first minute of every conversation the same, so the team spends its time on the part that is different. Four terms carry the whole thing.
- Trigger
- The event that starts a workflow: a new chat, a message, a page visit, an assignment, a ticket raised. Sellio has eleven.
- Rule
- A condition on the message, channel, subject, page URL or office hours. Every rule has to hold before the workflow runs.
- Action
- What it does: send, ask, tag, prioritise, assign, note, close, snooze, wait, raise a ticket. Eighteen, chained in any order.
- Branch
- A fork on a keyword or on the button a customer tapped, so one workflow can take different paths.
Automation questions
No. Workflows are built on a canvas from triggers, rules and actions, with no code anywhere.
- Pick a trigger, such as a new website chat or a conversation being assigned.
- Add rules so it runs only when the message, channel, subject, page URL or office hours match.
- Chain actions: send a message, ask with buttons, tag, set priority, assign, raise a ticket, close.
- Start from a template and adjust it, rather than from a blank canvas.
The builder is described on the chatbot builder page.
Still have a question? Contact us or browse the docs.
Automate the routine. Keep people for the judgment.
A workflow builder that greets, routes, tags and raises tickets, and an inbox that gets the rest.
No credit card required