Skip to content
On this page

Automation rules

Automatic rules that assign, label, change the status of, or close tickets, based on conditions you set.

Rules automate repetitive steps. Instead of sorting and assigning every ticket by hand, you let Elvo do it. Each rule checks a ticket when it arrives (or changes) and performs an action if the conditions are met.

Rules configured under Settings → Rules.
Rules configured under Settings → Rules.

How a rule works#

Every rule is a simple equation: condition → action.

  • Condition — when the rule should fire. E.g. "subject contains invoice", "ticket arrived by email", "sender's domain is @samskip.is", "outside opening hours is yes", or a combination of conditions.
  • Action — what should happen. E.g. assign to a team or person, change status, add or remove tags, or close the ticket.

A single rule can have multiple conditions and multiple actions.

Create a rule#

  1. Open Settings → Rules and click Add rule.
  2. Choose the conditions that trigger the rule.
  3. Choose the actions that should run.
  4. Save. The rule takes effect immediately on new tickets.

Rules are ordered and run top to bottom, so the order can matter.

Useful rule examples#

  • Route by content — tickets containing "order" go automatically to the fulfilment team.
  • Prioritize key customers — tickets from certain domains get a label and move to the front.
  • Close automated notifications — confirmation and system emails are marked read and closed immediately so they don't clutter the inbox.
  • Out-of-hours reply — condition Outside opening hours is Yes, action Send auto-reply. Every email or chat that arrives while you are closed (evenings, weekends, and any gap you have set such as lunch) gets your fixed note about opening hours. The opening hours themselves live under Settings → Organization → Opening hours, where each day can have more than one interval, e.g. 09:00–12:00 and 13:00–17:00 to close the chat over lunch. An organization without opening hours is never "outside" them, so the rule does nothing until hours are set.

Send webhook#

The Send webhook action sends the conversation to a URL you choose whenever the rule matches — for example a make.com scenario, Zapier, or your own script that should only react to group-booking requests rather than every conversation.

  • What is sent: a JSON POST with type: "rule.matched", the rule's id and name, the conversation and the customer message that matched (the same conversation and comment objects as Elvo's API webhooks), and is_new_conversation, which is true when the message started the conversation — use it if you only want to act on first messages.
  • When: on every new message from a customer that the rule matches — the first message and follow-ups — on email, Messenger, Instagram, WhatsApp and other channels, and on the first message of a live chat. Never on your team's own replies, internal notes, auto-responders, spam (yours or the mailbox's spam/junk folder) or imported old mail, and never when you "run on existing conversations". If a message reaches several team mailboxes and each team gets its own conversation, each conversation sends its own webhook.
  • Signature: when you save the rule, Elvo creates a signing secret and shows it on the action, with a copy button. Each request carries Elvo-Webhook-Id, Elvo-Webhook-Timestamp and Elvo-Webhook-Signature headers, signed exactly like Elvo's webhooks — see Verify signatures in the API docs.
  • Retries: your URL must answer with a 2xx status within 10 seconds. Otherwise Elvo tries again, 3 attempts in total; the request id stays the same, so you can ignore duplicates. A 4xx answer (except 408 and 429) is not retried. After 25 failed deliveries in a row the webhook is paused and the rule shows a warning; save the rule to start again.
  • Limits: at most 10 webhooks per hour for the same rule and conversation, and 300 per hour per rule, so a scenario that accidentally feeds back into Elvo cannot loop forever.
  • Only admins can add a webhook or change its URL, and only admins see the signing secret.
  • The URL must be a public https:// address, and a rule can send at most 3 webhooks.

Tip

Start with one or two simple rules and add more as you notice which steps keep repeating.

FAQ#

Can rules send replies to customers? Yes — e.g. an automatic acknowledgement. Use it sparingly so replies don't feel robotic. An auto-reply is sent once per conversation, on the first message only, and never in reply to another auto-responder.

Do rules apply to live chat? Yes. Rules run on the first message of a chat conversation too, with the channel condition set to Chat agent. Actions that make no sense for a visitor who is waiting live (spam, snooze, archive, email forwarding) are skipped for chats; auto-reply, tags, assignment and status apply.

What if two rules conflict? They run in order top to bottom; the top rule wins if they touch the same action.