Feature Guide · Messaging

Send the useful text.
Respect the channel.

Valet depends on timely communication, but a phone number is not a blank check. Valletto uses SMS for transactional parking and account messages, documents guest consent, honors opt-out commands, and supports the business-registration work U.S. carriers expect.

Three layers

Law, industry practice, and carrier registration are different things.

The Telephone Consumer Protection Act and FCC rules are law and regulation. CTIA publishes voluntary messaging principles and best practices used across the carrier ecosystem. The Campaign Registry is industry registration infrastructure for 10DLC brands and campaigns, not a government agency. A responsible messaging program accounts for all three without describing them as one rulebook.

01

What it is

Valletto sends automated transactional messages tied to a service or account relationship. Guest messages can cover vehicle check-in, parking and retrieval status, payment links, receipts, or support. Staff messages can include account invitations, sign-in links, and operational notices. Partner contacts can receive account setup and payment-onboarding messages. These programs are not a marketing blast list.

02

Who uses it

Guest

Consents directly

Enters their own mobile number and checks the guest-messaging consent box during digital check-in.

Employee

Receives work messages

Uses the number supplied for an employment-related account and can still opt out.

Partner contact

Receives setup messages

Uses the designated business number for account and payment-onboarding communication.

03

The setup order

Define the transactional use cases and consent language first. Publish SMS terms and a privacy explanation. For U.S. application-to-person traffic over a ten-digit number, provide the legal business name and nine-digit EIN exactly as they appear on tax records, then complete profile, brand, campaign, and number registration. Test opt-in, HELP, STOP, UNSTOP, and delivery-status handling before depending on the channel.

Sanitized staged transactional SMS thread with STOP and opt-out confirmation beside consent, registration, opt-out, and delivery-monitoring checks

The thread contains no phone number, customer, employee, vehicle, or property data. It mirrors the published STOP and UNSTOP behavior.

04

The daily loop

The product sends an expected transactional update, records provider delivery status, and uses push before SMS for selected person-addressed notifications when a live app can receive the push. A recipient can reply HELP for support, STOP to opt out, and UNSTOP to resume. After STOP, Valletto's published terms say an opt-out confirmation is sent and further messages stop.

05

The edge cases

Registration can be pending or rejected when business details do not match authoritative records. A registered campaign can still face filtering, rate limits, device problems, or carrier delay. Valletto therefore does not promise a fixed registration time, one universal messages-per-second limit, or guaranteed delivery. Those conditions vary by provider, carrier, brand, campaign, and registration status.

The product does not publish a universal SMS quiet-hours schedule. Operators should send only timely service messages, avoid unnecessary overnight traffic, and review legal requirements for their audience and use case rather than assuming a software default settles the question.

06

What it deliberately does not do

Valletto does not use these transactional numbers for third-party marketing, let an attendant opt a guest in, guarantee carrier delivery, or treat 10DLC registration as permission to send anything. It also does not postpone a clear STOP request. The FCC's current delay concerns a narrower cross-topic revocation rule, not a license to ignore ordinary opt-out methods.

07

What it connects to

Messaging connects guest check-in, parking and retrieval state, receipts, account invitations, partner onboarding, push reachability, provider delivery records, and company-linked 10DLC numbers. The authoritative product terms are the Valletto SMS Terms, Consent & Privacy. External references include the CTIA messaging principles, The Campaign Registry resources, and the FCC's January 2026 order.

Put it into practice

Write the smallest useful message.

A transactional text should tell the recipient what happened, what they can do next, and how to stop or get help - without borrowing the channel for promotion.

Concrete next step: audit every message against the published SMS terms, its consent source, its opt-out path, and the registered campaign purpose before enabling it.

Keep reading.

Feature GuidesIntegrations

Explore Valletto API Access

Discuss how your application could connect with the valet operation through Valletto’s private API preview.

Nov 26, 2025 · 3 min readRead
Feature GuidesIntegrations

Integrations: Four Ways a Property Can Hand You Its Guests

A current-state comparison of OPERA Cloud events, nightly reservation email, spreadsheet imports, and reviewed private API access.

Nov 8, 2025 · 9 min readRead
Feature GuidesIntegrations

Reservation Imports Without Repeated Uploads

Bring scheduled reservation reports into Valletto so your team can spend less time copying arrivals.

Nov 5, 2025 · 3 min readRead

When reading is not enough

See it on your drive.

Twenty minutes on your own property, with your own volumes. We would rather show you the parts an article can only describe.

or keep reading the journal