Auto Responder

The Auto Responder automatically replies to incoming messages based on rules you create. Each rule pairs one or more trigger messages with a single response that gets sent back to the sender.

How it works

When someone sends you a message, the app checks it against every auto response you've set up. For each rule that matches, the response is sent back to the sender.

A rule can have more than one trigger message. If any of them match, the response is sent.
More than one rule can fire for the same incoming message. If two rules both match, the sender will receive two replies.
You can pause a rule at any time by turning Enabled off.

Adding an auto response

Click Add on the Auto Responder page and fill in:

Field	What to enter
Messages	The trigger(s) that should fire this rule. Use the + button to add more than one.
Response	The reply that gets sent back to the sender.
Type	`SMS` for a plain text reply, or `MMS` to include attachments.
Attachments	(MMS only) Images, audio, video, `.txt`, or `.vcf` files to send along with the reply.
Criterion	How each trigger is compared to the incoming message. See below.
Enabled	Turn off to pause the rule without deleting it.

Choosing a criterion

The Criterion controls how triggers are matched against the incoming message. Pick the one that best fits what you need.

Match

The incoming message must be exactly the trigger, but capitalization doesn't matter.

Trigger hello fires for hello, HELLO, or Hello.
It does not fire for hello there or say hello.

Match Case

The incoming message must be exactly the trigger, including capitalization.

Trigger STOP fires for STOP only.
It does not fire for stop or Stop.

Contains

The trigger must appear somewhere inside the incoming message. Capitalization matters.

Trigger price fires for what's the price? and price list.
It does not fire for Price list (different capitalization).

Regex

The most flexible option. A regex (short for "regular expression") is a small pattern language that lets you describe the shape of a message instead of typing it out word for word. Use it when a simple Match or Contains isn't enough. For example, when you want to match any 6-digit code, any phone number, or any message that starts with "yes".

A few things to keep in mind:

The pattern has to describe the whole message, not just part of it. If you want a keyword anywhere in the message, wrap it like .*keyword.* (or just use the Contains criterion instead).
Capitalization matters by default. Put (?i) at the start of your pattern to make it case-insensitive.
A plain . doesn't match line breaks. If an incoming message might span multiple lines, use [\s\S] in place of ., or put (?s) at the start.
If your pattern has a typo or isn't valid, the rule simply won't fire, but it won't crash anything. Test your pattern before relying on it.

Regex examples

All examples below assume you've selected the Regex criterion.

Match anything

Goal	Pattern
Any message (single line)	`.*`
Any message, even one with line breaks	`[\s\S]*`
Any non-empty message	`.+`
Any non-empty message, even with line breaks	`[\s\S]+`

Keywords

Goal	Pattern
Just the word `hello`, any capitalisation	`(?i)hello`
Any message that contains `stop`, any capitalisation	`(?i).stop.`
Any message that starts with `hi`	`(?i)hi.*`
Any message that ends with `bye`	`(?i).*bye`
Any of several keywords	`(?i)(stop\\|unsubscribe\\|cancel)`
`YES` followed by anything	`(?i)yes.*`
A plain yes or no reply	`(?i)(yes\\|y\\|no\\|n)`

Numbers and codes

Goal	Pattern
A message that's all digits	`\d+`
A 6-digit code (e.g. OTP)	`\d{6}`
A US phone number	`\+?1?\s*\(?\d{3}\)?[\s-]?\d{3}[\s-]?\d{4}`
An email address	`[^\s@]+@[^\s@]+\.[^\s@]+`

Tips

If you just want to check for a keyword anywhere in the message, the Contains criterion is simpler than writing a regex.
Instead of one big complicated pattern, add several triggers to the Messages list. Each one is tested separately, and a match on any of them fires the rule.
You can prototype patterns on a site like regex101.com (choose the PCRE flavor). Don't include the surrounding /…/ slashes when you paste the pattern back here.

30 April 2026