Guest messaging integration
Twilio
Send restaurant text messages from your own Twilio number and keep replies and delivery updates connected to Trellis.
- Category
- Guest messaging
- Best for
- Restaurant text messaging
- Setup
- Guided by Trellis
How it helps
Less switching.
Fewer handoffs.
- Text from your restaurant number
Use a verified Twilio sender for reservation messages, receipts, gift cards, Text to Pay, and approved marketing.
- Follow message delivery
Keep accepted, sent, delivered, failed, and undelivered updates attached to the Trellis message.
- Route guest replies correctly
Bring signed inbound replies back to the restaurant and reservation conversation that owns them.
- Keep each account separate
Verify and encrypt each restaurant group’s Twilio account, token, and sender before activation.
How it fits
One connected
workflow.
Trellis checks the Twilio account and exact SMS-capable sender before saving the connection.
Restaurant messages go through that verified account with the correct guest and workflow context.
Delivery updates and inbound replies return to the right restaurant in Trellis.
Getting started
A clear path
to launch.
- Prepare your Twilio sender
Choose an SMS-capable number and complete any required A2P, toll-free, or local registration.
- Connect Twilio in Trellis
Enter the Account SID, Auth Token, and sender number in the Trellis Integrations workspace.
- Choose the messaging workflows
Confirm which reservation, receipt, payment, gift-card, and marketing messages should use Twilio.
- Send and reply to a test message
Verify delivery updates and one inbound reply before turning the connection on for guests.