Loading…
Topic
3 posts about RCS. Every summary links to the original.
See the idea
The Branded Calling trust chain, layer by layer: how identity, STIR/SHAKEN attestation, Rich Call Data, and carrier delivery combine so a verified brand name reaches the recipient's screen.
The Good Stuff
Paid picks we use ourselves. Links carry a referral code — a subscription through one earns us a commission at no extra cost to you.
Newest first
Twilio’s tutorial explains how to build an RCS Business Messaging campaign in PHP, reusing the same Programmable Messaging API used for SMS. RCS turns standard text messages into branded conversations with images, carousels, verified sender logos, suggested replies, and read receipts delivered through the recipient’s default messaging app. The walkthrough covers registering an RCS Sender, attaching it to a Messaging Service, and designing a rich card template in the Twilio Content Template Builder. It then shows how to broadcast the campaign to a recipient list, track delivery status via a status callback webhook, and capture replies through an inbound webhook. Troubleshooting guidance addresses common issues such as messages falling back to SMS, senders pending approval, and missing status callbacks.
RCS Business Messaging upgrades SMS with branded conversations featuring images, suggested replies, and read receipts delivered natively on the recipient’s phone. Twilio Programmable Messaging supports RCS via the same API used for SMS, allowing reuse of existing integrations. This tutorial teaches building an RCS campaign in .NET 10, requiring a Twilio account, registered RCS Sender, Messaging Service, ngrok, and a code editor. The process includes creating a rich card template with hero image, dynamic placeholders, and three buttons (Shop the sale, Send promo code, Unsubscribe), then broadcasting personalized messages via the Twilio helper library while capturing status and replies through webhooks exposed by ngrok. Test devices receive messages without waiting for full RCS sender approval, and the server terminal outputs inbound replies and status callbacks in real time.
Twilio has scheduled two 2026 Heightened Awareness Periods (HAPs) to manage messaging throughput during U.S. midterm election traffic and the Black Friday/Cyber Monday and holiday shopping surge. During these windows, high-volume short code and toll-free traffic shifts temporarily to Market Throughput, while 10DLC remains on Account-Based Throughput and RCS uses standard per-sender limits; contracted limits are honored. Most users need no action, but election senders should contact their account team by October 1, 2026, and holiday senders face deadlines for RCS approval, throughput review, A2P 10DLC requests, and supplementary orders. The election HAP runs November 2–4, 2026, while the holiday HAP runs November 19, 2026, through January 4, 2027; capacity is limited and allocated first come, first served.
The best engineering reads, once a week.
