Every lodge that sends a text message to a guest — confirming a reservation, delivering a mobile check-in link, promoting a seasonal rate package, or requesting a post-stay review — is transmitting an A2P message across a carrier network that requires prior registration. 10DLC for lodges is not a category exception to A2P compliance; it is the required framework for every lodge operating any business-to-guest SMS channel in the United States. Carriers AT&T, T-Mobile, and Verizon enforce this standard: unregistered A2P traffic from standard 10-digit long-code numbers is subject to filtering and blocking, regardless of message intent, guest relationship, or property size. The compliance structure is the same for a twelve-room mountain lodge as it is for a national branded property.
What A2P Compliance Means for Lodge SMS Operations
10DLC — ten-digit long code — is the standard number format for business A2P messaging in the United States. The A2P designation applies whenever a business application, platform, or property management system sends a message to a consumer’s mobile number on a scheduled or automated basis. For lodge operations, that definition covers a wide set of communication channels: automated reservation confirmations sent from a PMS, pre-arrival check-in links pushed via guest communication software, service request responses from a front desk messaging platform, and bulk promotional texts sent to an opted-in guest list.
The Campaign Registry (TCR) administers the registration infrastructure for all 10DLC messaging. Each lodge sending A2P messages must register a Brand — a verified record of the lodge’s legal entity — and one or more Campaigns that describe each distinct messaging use case. Registration fees apply at both levels: $4–$5 per month for brand maintenance, and $10–$15 per campaign registration plus approximately $10 monthly per campaign for standard use cases. Carrier enforcement of unregistered A2P traffic became mandatory in late 2024, and any A2P message sent through an unregistered 10-digit long code is now subject to filtering or blocking by all three major U.S. carriers. For lodges, a blocked confirmation text or filtered promotional message is a direct operational and revenue failure that registration prevents.
The Hospitality & Travel Messaging Compliance Playbook on MyTCRPlus covers the full consent architecture, use-case mapping, and carrier-specific content standards that apply to hospitality operators — including how to structure registrations for properties that send multiple distinct message types.
Lodge SMS Use Cases and How They Map to TCR Campaign Types
Most lodge properties operate more than one type of guest-facing SMS communication, and TCR treats each distinct use case as a separate campaign registration. Bundling different message types under a single campaign description is a common source of TCR campaign rejection for hospitality operators: the sample messages provided in the registration must accurately represent all content transmitted under that campaign. Promotional content submitted under a Customer Care registration will generate a campaign denial.
The standard lodge SMS use cases and their TCR campaign type mapping:
Reservation confirmations and reminders are transactional messages — booking dates, confirmation numbers, arrival instructions, and cancellation policies. They register under Notifications/Alerts or Account Notifications and require that the guest provided their mobile number during the reservation process. How to register 10DLC for a lodge business begins by identifying each distinct communication touchpoint and confirming which platform sends each type of message.
Pre-arrival and mobile check-in messages — room-ready notifications, check-in link delivery, arrival instruction texts — are transactional service messages. They can share a campaign with reservation confirmations if the content and opt-in mechanism are consistently described in the registration, or register as a separate campaign if a different platform or number delivers them.
Guest services and amenity communications — concierge request responses, spa booking confirmations, restaurant reminder texts — register under Customer Care if response-based, or Notifications if automated by a platform.
Promotional and marketing messages — seasonal package offers, loyalty program communications, post-stay promotional outreach, and rate promotions — require a Marketing use-case registration, explicit advance opt-in distinct from the transactional booking consent, and stricter content standards than transactional campaigns. These cannot share a registration with any transactional use case.
Brand Registration for Your Lodge Property
Brand registration is the foundation of 10DLC for lodges. Every lodge registering its own messaging must submit a brand record that reflects the legal entity operating the property. For a lodge operating under a registered LLC, the brand name, EIN, and address entered in TCR must match IRS records exactly — no abbreviations, no trade name substitutions. A property operating as “Ridgeline Lodge LLC” cannot register under a shortened marketing name without generating an identity mismatch that triggers a brand denial.
Brand data requirements include the legal entity name as filed with the IRS, a valid EIN, the business address on IRS record, an active and operational website with accessible contact information, and a compliant privacy policy. The privacy policy must include an SMS-specific section confirming that subscriber mobile data is not shared with third parties for marketing purposes and describing how opt-out requests are processed.
Sole proprietors — a structure common among independent lodge operators — face an additional verification step. Sole proprietor brand registrations in TCR require a mobile phone number capable of receiving a one-time password for identity confirmation. Without OTP completion, the registration will not advance regardless of all other submitted data. Independent lodges operating under a sole proprietor structure should ensure the registering individual’s mobile number is accessible during the submission process.
Lodge properties within a larger ownership group face a structural decision: register each property as a separate brand entity, or consolidate under a parent company brand. Parent-brand registration simplifies trust score management and reduces the brand vetting overhead, but requires that all property-level messaging accurately reflects the parent entity’s legal identity. Separate brand registration per property provides cleaner campaign isolation at the cost of multiplied registration fees and vetting cycles.
The TCR Readiness Assessment maps a lodge’s current compliance posture — brand verification status, website and privacy policy compliance, and potential registration gaps — against TCR’s current vetting standards before any submission fee is committed. The broader hospitality SMS compliance solution on MyTCRPlus covers the full registration and ongoing compliance infrastructure for lodge and hospitality operators.
Opt-In Consent for Lodge Guest SMS
Lodge SMS consent requirements follow CTIA Messaging Principles and, for marketing messages, TCPA. The consent architecture differs by message type, and conflating the two most common categories — transactional and promotional — is the single most frequent compliance error among lodge operators launching SMS programs.
Lodge SMS reservation confirmations compliance: transactional messages sent to a guest who provided their mobile number during booking are permissible with basic disclosure at the point of collection. The booking form or confirmation page must carry a visible statement that by providing their phone number, the guest agrees to receive SMS messages related to their reservation, including message frequency disclosure and “message and data rates may apply.” A pre-checked consent box without clear disclosure language does not satisfy this standard.
Marketing and promotional messages require separate express written consent. A guest who confirmed a reservation did not opt in to receive seasonal package offers or loyalty program promotions. 10DLC opt-in consent for lodge guests collected for marketing purposes must be captured on a dedicated form, a keyword opt-in, or a clearly distinguished checkbox that explicitly describes the marketing content to be sent — including message type, frequency, brand name, and opt-out instructions.
The consent record for every opt-in — the timestamp, the submission source, and the exact disclosure language displayed — must be stored and retrievable. In a TCPA enforcement context, the burden of proof falls on the sending party, not the recipient. A lodge that cannot produce the original consent record for a guest messaging complaint faces the same liability exposure as a lodge that never captured consent at all.
Carrier Content Standards for Lodge SMS Messages
Every message transmitted under a registered 10DLC lodge campaign must comply with content standards enforced in real time by AT&T, T-Mobile, and Verizon. Carrier filtering systems evaluate outbound messages against registered campaign parameters continuously — registration approval does not immunize messages from filtering if the content deviates from declared standards.
Lodge text messaging TCPA compliance requirements at the content level include: no SHAFT-C content (Sex, Hate, Alcohol, Firearms, Tobacco, Cannabis) in any message or on the brand’s associated website. A lodge that sells alcohol at a bar or in room service must ensure that neither the A2P messages nor the TCR-registered website links include alcohol promotion — carrier policy applies to the registered brand, not just the message text.
Every marketing message must include the STOP keyword mechanism and a brand identifier in the message. Every promotional campaign must transmit at a frequency consistent with the disclosure made during opt-in. Public URL shorteners — bit.ly, tinyurl, and comparable services — are prohibited in all 10DLC messages; lodges using SMS to deliver booking links, mobile check-in portals, or landing pages must use branded short domains or full destination URLs.
Compliance for separate TCR campaigns lodge use cases means that the content of each message must match the sample messages and use-case description registered in TCR. A lodge that registers a Customer Care campaign and then routes a seasonal rate promotion through the same number will generate carrier violations that can result in campaign suspension without formal advance notice.
10DLC for Independent Lodges and Multi-Property Groups
10DLC for small independent lodge operators involves the same registration structure as larger properties, with one size-specific consideration: sole proprietor and single-employee entity brand registrations typically receive lower automated trust scores than established multi-year entities with verifiable credit and business history. Lower trust scores reduce throughput capacity — the number of messages per second and the daily message volume permitted under the campaign. For a lodge sending modest transactional volumes, standard trust tiers are sufficient. For a lodge running seasonal promotional campaigns to a large opted-in guest database, a suppressed trust score creates a practical throughput ceiling that limits campaign execution.
Enhanced brand vetting — available through TCR’s authorized external vetting partners at a fee between $40 and $110 depending on vetting depth — replaces the automated trust score algorithm with an independently reviewed compliance standing. For independent lodges with limited business history or new EINs, enhanced vetting is the mechanism for unlocking standard or elevated throughput tiers without waiting for the business profile to age naturally.
Multi-property lodge groups face a compound compliance challenge: each property may operate different reservation platforms, different opt-in workflows, and different guest communication systems. But TCR and carrier compliance operates at the brand and campaign level, not the platform level. A consent or content violation at one property’s number pool can affect brand trust scores across the full registration. Centralized compliance management — standardized opt-in language, uniform privacy policy language, and consistent campaign descriptions across all properties — prevents a single property from generating a compliance liability for the group.
The provider-specific 10DLC registration checklists on MyTCRPlus cover the registration workflows and required fields by connectivity provider — Twilio, RingCentral, Vonage, Telnyx, and others — so lodge operators know exactly which platform-specific steps and approval processes apply to their messaging infrastructure before they begin.
10DLC for lodges is a straightforward compliance framework once operators understand its structure: brand registration establishes the legal entity, campaign registration defines each distinct use case, and carrier content standards applied in real time ensure that guest messages are delivered and not filtered. The operational risk of skipping registration — blocked confirmations, failed promotional sends, and the fee cost of resubmissions after rejection — exceeds the one-time administrative investment of getting it right. Lodge operators who map their use cases before submitting, build consent architecture appropriate to each message type, and verify carrier content requirements before the first campaign goes live reach compliant, operational 10DLC channels without the iterative failure cycle that characterizes underprepared registrations.
Access the Hospitality SMS Compliance Solution on MyTCRPlus. Review the 10DLC registration requirements specific to lodge and hospitality properties, map your use cases to the correct TCR campaign types, and verify that your opt-in architecture meets carrier standards before your first brand or campaign submission.
