Everything worth knowing, nothing that isn't.
How replies reach you
When a customer replies, the inbound (mobile-originated) message is delivered to your application through a webhook, so you can process confirmations, keywords, and STOP requests programmatically. See /answers/what-is-mo-vs-mt and /answers/what-is-a-messaging-webhook.
What number you need
Two-way traffic needs a number that can receive: a long code or toll-free number for lower volume, or a short code for high-throughput keyword campaigns. A one-way alphanumeric sender ID cannot receive replies. See /answers/what-is-long-code and /answers/what-is-short-code.
What it enables
Appointment confirmations, delivery rescheduling, fraud-alert YES/NO responses, surveys, and conversational support all depend on two-way messaging. See /answers/sms-for-appointment-reminders and /products/two-way-sms.
Keep it compliant
Always honour STOP and opt-out through the reply channel, and keep records of consent. See /answers/what-is-dnc and /answers/sms-compliance-checklist.