Receive replies to your SMS sends on a short code or long code, and route them into your support desk or CRM.
SMS
02Live example
This is what two-way & inbound sms looks like when it lands on a customer’s phone.
Reply YES to confirm your appointment on Friday at 4 PM, or NO to reschedule.
9:41✓
03The API call
One request. Copy it, drop in your key, and send.
curl https://api.msgbridge.in/v1/sms/inbound/webhook-config \ -H "Authorization: Bearer $API_KEY" \ -d number="56070" \ -d webhook_url="https://yourapp.com/sms/inbound"04When to use it
- Appointment confirmations with a YES/NO reply
- Support requests started over SMS
- Keyword-based opt-in campaigns
- Survey responses collected by reply
05What's required
- Short code or long code allocationTimelines vary by number type and operator
- Inbound webhook endpointSet up on your side before go-live
06How to go live
Choose a number
Pick a short code or long code depending on volume and budget.
Configure
Point your inbound webhook at the number.
Test
Send a reply and confirm it reaches your endpoint.
Launch
Route inbound replies into your support desk or CRM.
07Related channels
08FAQ
Short codes suit high-volume, consumer-facing campaigns; long codes suit lower-volume or support-style two-way conversations. We'll help you pick based on your use case.
Replies are posted to a webhook URL you configure, in near real time.
In most cases you can port an existing number, subject to operator processes.
This page describes the intended shape of the product. Confirm current availability and lead times with our team before committing to a launch date.
Ready to send with Two-Way & Inbound SMS?
Talk to us, or start building against the sandbox today.