![]() ![]() If the request to your primary webhook fails, Twilio tries the fallback webhook. Twilio stores the message up to six hours for disaster recovery purposes while it attempts to pass along the message information in the form of an HTTP request to your customer-defined A message comes in webhook. Twilio receives an inbound SMS/MMS message from the carrier/provider. ![]() In the Post-transit stage, the message with redacted information is held for long-term storage, billing, and debugger notification purposes. Once the provider acknowledges receipt of the message, Twilio stores the sensitive information for up to six hours before redaction. Once an outbound SMS/MMS message is sent via Twilio’s API, it will be retained in the queue for up to four hours, depending on message volume.ĭuring the In-transit phase, Twilio sends the message to the carrier/provider and waits for an acknowledgment before redacting the message body and phone number. For more information about WhatsApp message redaction, please continue to the next section. SMS/MMS and WhatsApp redaction vary slightly in implementation. Phone number redaction will obfuscate the last four digits of the non-Twilio phone number in the message request. With message body redaction, you ensure that Twilio never retains message bodies that may contain sensitive information. This guide shows you how to set up your Twilio account correctly for content and phone number redaction, and includes code samples that retain this information at an individual message level. Privacy and anonymous communications may also be a value proposition for your application. If you are building for highly regulated industries, such as health care, financial services, and education, content redaction may be required to ensure your application’s regulatory compliance. You can enable this privacy feature at the account level so that Twilio does not retain sensitive customer information by default. With Twilio’s Message Redaction feature, you protect customers’ messaging privacy by redacting the message body and phone number. Protect Communication Content and User Identity with Message Redaction Verify: user verification and one-time passwords ISV Sole Proprietor Registration: API OnboardingĬonvert a Sole Proprietor Brand to a Standard BrandĮvent Streams Setup and Notifications for A2P Brands and CampaignsĬreate Mock US A2P 10DLC Brands and CampaignsĬontent Editor: message templates for any messaging channel ISV Standard and Low Volume Standard Registration: API Onboarding How to Optimize Message Deliverability with Message Feedbackĭirect Standard and Low Volume Standard Registrationĭirect Brand Registration for Government and Non-Profit Agencies Track the Message Status of Outbound Messagesīest Practices for Messaging Delivery Status Logging Outbound Message Status in Status Callbacks What to Know Before Sending International SMS Messages (US A2P 10DLC Registration) Use Case Resourceīest Practices for Scaling with Messaging Services (US A2P 10DLC Registration) Campaign Resource ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |