Overview
Subscription management is configured per brand by our Customer Success team. Each configuration includes:- Short codes or long codes for receiving opt-out requests
- Callback URL for receiving subscription events
- Custom messages for STOP, START, and HELP responses (optional)
Contact us to set up subscription management for your brand.
How it works
User sends keyword
Recipients can send one of the following keywords to your configured phone number:
Keywords are case-insensitive and must appear at the start of the message.
| Keyword | Action |
|---|---|
STOP | Unsubscribe from marketing messages |
START | Resubscribe to marketing messages |
HELP | Request information about the service |
Prelude processes the request
When a user sends a keyword:
- The subscription status is automatically updated in Prelude’s system
- A confirmation message is sent back to the user
- A webhook event is sent to your callback URL (if configured)
Webhook events
You’ll receive webhook events for all subscription changes. See the Webhook documentation for details. Example STOP event:Carrier disconnects
Phone numbers that are detected as disconnected by the carrier are automatically unsubscribed from all subscription management configs. Amarketing.subscription.carrier_disconnect event is sent to each config’s callback URL. See the Webhook documentation for the event payload and handling guidance.
Confirmation messages
When a user sends a keyword, they automatically receive a confirmation message.Default messages
If you don’t configure custom messages, Prelude uses standard defaults: STOP response:You have been unsubscribed and will not receive further messages. Reply START to resubscribe.START response:
You have been resubscribed and will receive messages again. Reply STOP to unsubscribe.HELP response:
Reply STOP to unsubscribe or START to resubscribe.