How to Create, Edit & Delete Relays
Build reliable automations with a clear flow: Trigger → Conditions → Actions. This guide shows you how to configure, test, and troubleshoot Relays.Permissions required: By default, only Admin users can access Relays. If you don’t see the Relays module, ask your workspace admin to grant you Relay Management permissions via Settings → Team Management. Learn more: Team Management.
How to Create or Edit a Relay
1. Visit the Relays module
When you first visit Relays, you’ll see templates you can use as a starting point, just click Add Relay to start building.
By default, new Relays are paused. Toggle them On when you’re ready.

2. Name and describe your Relay
Click the vertical ⋯ (three dots) next to a Relay to Rename, Edit description, or Delete.
3. Set a Trigger
Current supported trigger: Message Received (fires when a new inbound SMS arrives).Note: Templates include the message received trigger by default.

4. Add Conditions
Conditions control where/when a Relay runs. You can combine multiple conditions with AND or OR. Available conditions:- Message contains text — match keywords like
SUPPORT,HELP - My phone number equals — run only on a specific outbound line
- Is anonymous conversation — no saved contact yet
- Is new conversation — first inbound in a thread
- Active hours — restrict to a daily time window

5. Add Actions
Actions run when the conditions match. You can add one or many in the order you want them to execute.- Reply to message — send an SMS/MMS (supports templates, tags, and media)
- Assign teammates to the conversation — pick one or more users
- Add labels to the conversation — apply one or more labels
- Add a Delay to Reply to message to wait minutes/hours before sending.
- Delays help prevent duplicate auto-replies if a message was sent recently.

6. Activate your Relay
Use the toggle to turn the Relay On. You can pause anytime without losing your setup.
Managing Relays
Pause / resume
- From the list: toggle On/Off
- From details: use the status toggle at the top
Delete
Open the Relay → ⋯ → Delete.Starter Relay Templates (Copy & Adapt)
Keyword responder
Trigger: Message ReceivedConditions: Message contains
SUPPORTActions: Reply →
“Thanks for reaching out to support. Please share any extra details, and we’ll jump in.”
Identify unknown contacts
Trigger: Message ReceivedConditions: Is anonymous conversation
Actions: Reply →
“Thanks for texting us! What’s your first and last name so we know who to help?”
Assign new conversations
Trigger: Message ReceivedConditions: Is new conversation
Actions: Assign teammates → pick your queue owner(s)
Auto-label new threads
Trigger: Message ReceivedConditions: Is new conversation
Actions: Add labels → e.g.,
Support, Lead, Region: West
After-hours auto-reply
Trigger: Message ReceivedConditions: Active hours (inverted for after-hours)
Actions: Reply →
“Thanks for texting! We’re away right now. We’ll reply at 8am PT. Reply STOP to opt out.”
Technical Notes & Behavior
- Action order: Actions execute top-to-bottom in the order you add them.
- Delays: Units include minutes/hours. Use to prevent duplicate “fast follow” replies.
- Active hours: Configure daily windows; invert to run only outside business hours.
- Permissions aware: Assign/Label actions respect Roles & Permissions.
- Testing tip: Start with a single condition/action, confirm it fires, then layer on complexity.
Frequetly Asked Relay Questions
Do Relays respect roles & permissions?Yes. Assign/Label actions follow your Roles & Permissions settings. Can multiple Relays run on one inbound message?
Yes. If conditions match for more than one Relay, each eligible Relay can run. Can I include media in auto-replies?
Yes. Keep each file ≤ 10 MB (files > 500 KB are sent as links). See Media. Can I pause without losing my setup?
Yes—toggle Off to pause. Toggle On to resume. How do I avoid duplicate automated replies?
Add a Delay to the Reply action, or narrow conditions (e.g., “Is new conversation”).
Troubleshooting
A Relay didn’t fire- Confirm it’s On (not paused).
- Verify the Trigger is “Message Received”.
- Temporarily loosen Conditions (switch
ANDtoOR, remove a filter) to test.
- Add a Delay to your Reply action so back-to-back messages don’t both trigger an instant response.
- Check the target user/label permissions.
- Remove long Delays while testing to see results immediately.
- Review Active hours and the invert setting.
- Check your workspace timezone.
Best Practices
- Be explicit: Name Relays clearly (e.g., “After-hours reply — Support line”).
- Document ownership: Add who maintains the Relay to the description.
- Start simple: One trigger → one condition → one action. Expand gradually.
- Stay compliant: Include opt-out language (e.g., “Reply STOP to opt out”) where appropriate.

