How to set up inbound rules and outgoing replies for your SMS number
Every message a customer sends to your connected SMS number runs through your rules. A rule has two parts: a trigger (what to match) and an action (what to do).
Portal → Auto-reply rules → + Add rule.
Sign in to the portal and click Auto-reply rules in the left menu.
Give the rule a name, pick how to match, and type the keyword.
Use From filter to run the rule only for specific numbers (a number, part of one, or a pattern). Leave blank for everyone.
In the same rule, turn on Send reply and write the message. It goes straight back as an SMS to the same number.
Use {{variables}} to personalise (see the cheat-sheet below).
The reply is automatic — sent within a second of the customer's message.
Two ways to get inbound SMS out of the gateway and into your systems.
Turn on Send email inside a rule to get notified whenever it matches.
Push every inbound message to your own URL as JSON. Set this under Settings → Forward all inbound, or per-rule. We sign each request with HMAC so you can verify it's really us.
Your endpoint receives:
At the top of the Rules page is the Auto-reply engine panel.
Drop these into any reply, email subject/body — they're filled in live.
| {{from}} | Sender's number — e.g. 919876543210 (example) |
| {{text}} | The exact message the customer sent |
| {{ref}} | Reference id, if the message carried one |
| {{now}} | Current date & time (ISO) |
| {{tenantName}} | Your account / company name |
| {{deviceId}} | Which connection received it |
Reply: "Thanks {{from}}! We're open Mon–Sat 9–6. We'll get back to you soon."
Make one rule per keyword (1, 2, 3…). Give them low priority numbers so they're checked first.
Reply to the customer and POST the message to your CRM webhook at the same time.