- Shipped
- September 7, 2026 at 12:06 AM UTC
- Author
- Kamo
- Commit
- 1133ce0
Adding a text provider covers sending. Receiving needs the carrier told where to deliver, which happens in the carrier's own console — and the form never said what to paste there. Skipping it has no symptom on the side anybody tests first: messages send normally and every reply is dropped at the edge. The card appears on both text-provider screens: the new-provider form, where an administrator is already looking at the field for the key that verifies those same posts, and the existing provider's overview, so it can be checked after the fact. Fetched, never hardcoded. It is derived from a deployment property and is the same string the server writes into Telnyx's messaging profile; a second copy here is a copy that can be wrong, which is why RingCentral's redirect URI is served the same way. A failed lookup hides the card rather than showing a guess — half a setup instruction is worse than none, because somebody would paste whatever was on screen and believe they were finished. It also warns when a carrier's inbound is not wired at all, rather than handing over a URL that would then refuse every message. Reuses CopyableIdField, which already existed for the phone-server id.