The receiver for texts sent to any number the platform holds. It verifies the provider signature, resolves the destination number through the number inventory, rewrites media URLs to the platform's own authenticated proxy, and stores the message against the right account and rep.
Also called: receive texts · customer texted back · sms webhook
- 1Signature is HMAC-SHA1 over the full public URL plus every sorted POST parameter, compared in constant time
- 2The signed URL is reconstructed from proxy headers — behind a proxy it is NOT the request URL, and getting that wrong is the classic reason a correct implementation rejects everything
- 3The number is resolved on a unique index in the number inventory, with a legacy fallback to the older single-number binding
- 4Media URLs are rewritten to /api/comms/mms/<messageSid>/<mediaSid>
- 5The rep who holds the receiving number is snapshotted onto the message
A reply from a customer is only useful if it reaches the person who was talking to them, and a shared pile means whoever opens it first has to work out whose it is. Inbound texts are verified, resolved to the account that owns the number they were sent to, and where that line belongs to a rep, to that rep. A customer replying to a rep's own number lands with that rep.
- Inbound texts with no receiver
- Provider-hosted media unusable in the browser
- Replies not attributed to the rep who owns the line
See it on your own jobs
Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.
or keep browsing features →