Preferences

Send SMS Notification with Reply requires three inputs, plus at least one Reply Command Exit.

Inputs

Input Field	Description	Required
Outbound SMS number	The provisioned SMS-capable phone number the message is sent from and the reply is received on. Populated from numbers provisioned for Automated Notifications under Admin > Numbers.	Yes
Destination number	The Studio variable holding the recipient's phone number. Example: a variable populated from the Contact Lookup response, e.g. +15551234567.	Yes
SMS content	The text of the outbound message. Supports Studio variables so the content can be personalized with data from the triggering event. Example: "Reply YES to confirm your appointment on {{appointment_date}}, or RESCHEDULE to pick a new time."	Yes

Reply Command Exits

Configure one or more Reply Command Exits to define the keywords a customer can reply with, and where the flow should go for each one.

Each exit accepts one or more keywords. A reply matches an exit if it equals any of that exit's configured keywords (case-insensitive).
At least one Reply Command Exit is required, and Reply Command Exits cannot be disabled.
The following keywords are reserved for carrier-level SMS opt-out/opt-in compliance and cannot be used as a custom keyword: START, YES, STOP, STOPALL, UNSTOP, UNSUBSCRIBE, CANCEL, END, QUIT, HELP, INFO.

Timeout

Configure how long the component should wait for a reply before giving up. The timeout is set in hours, with a minimum of 1 hour and a maximum of 2160 hours (90 days); the default is 24 hours. If the timeout elapses before a matching reply is received, the flow proceeds through the Timeout exit.