<aside> 📱
CANDID uses Twilio’s A2P 10DLC framework for application-to-person SMS and MMS sent from U.S. ten-digit long-code numbers. Registration identifies the sending business, documents the messaging purpose and consent flow, and links approved phone numbers to the appropriate Twilio Messaging Service.
</aside>
This page explains the information represented during Twilio A2P 10DLC registration for CANDID-powered mortgage communications. It is intended for prospective and existing customer compliance, legal, operations, and technology teams.
A2P 10DLC registration supports carrier trust, deliverability, sender identification, and transparent opt-in and opt-out practices. It does not independently establish TCPA consent or authorize content outside the registered use case.
CANDID supports customer-specific Twilio configuration. The registered brand, campaign, Messaging Service, phone numbers, disclosures, and consent evidence must match the organization actually sending the messages.
| Registration element | Information represented |
|---|---|
| Brand | The customer’s legal business name, entity type, tax identifier, address, website, industry, and authorized representative |
| Brand relationship | Direct customer or applicable software-provider relationship, based on the customer’s Twilio architecture |
| Campaign type | Customer Care or another Twilio-approved use case that accurately reflects the organization’s traffic |
| Direct lending designation | The campaign description identifies the sender as a first-party direct lender when applicable |
| Recipients | Existing applicants, borrowers, customers, and other recipients who have provided the required consent or are receiving a permitted account-related communication |
| Messaging Service | The Twilio Messaging Service connected to the approved campaign |
| Sending numbers | The customer’s registered 10DLC phone numbers assigned to the approved Messaging Service |
| Consent flow | Each enabled method through which a recipient receives the disclosure and affirmatively agrees to SMS |
| Opt-out handling | Supported keywords and confirmation language used to stop later messages |
| Help handling | Supported HELP or INFO response language |
| Sample messages | Representative examples that identify the sender, match the declared use case, and include appropriate opt-out language |
Customer-specific Brand SIDs, Campaign SIDs, Messaging Service SIDs, phone numbers, and registration status are maintained in the customer’s Twilio Console. They should be shared with compliance reviewers through the customer’s approved secure process, not published in general product documentation.
The campaign is structured for first-party mortgage customer care and account-related communications, not unsolicited third-party lead generation or direct loan marketing.
A representative registration description is:
The organization sends first-party mortgage communications to applicants, borrowers, and existing customers who have provided the required consent or are receiving permitted account-related communications. Messages support loan processing, document collection, disclosures, closing coordination, time-sensitive servicing or account notices, and pre- or post-closing mortgage relationship communications. Messages may contain links and telephone numbers. This campaign is not used for unsolicited mortgage offers, purchased lead marketing, or third-party lead generation.
The final description submitted to Twilio must identify the actual customer and precisely match its traffic.
Messages communicate meaningful changes in the recipient’s application or loan process, such as: