The current Day-1 OwnerSwitch app does not send texts or place calls. Messaging-program guidance and opt-out help apply only to a separately activated future pilot.

OwnerSwitch
Compliance controls & trust

Controls that support a reviewed messaging program.

Texting customers with AI comes with legal and carrier obligations. OwnerSwitch provides controls and records; it does not provide legal advice or make a business compliant by itself.

Consent on file
OwnerSwitch can record approved consent basis and revocations when a messaging channel is later enabled. Day-1 keeps you on your existing business phone; each business remains responsible for a lawful consent path.
A2P 10DLC stays off in Day-1
Day-1 does not run live 10DLC or provision a per-shop Twilio number. Carrier Brand / Campaign work is not part of this founding-partner binary; keep using your existing business phone.
AI disclosure built in
OwnerSwitch supports approved business-identity and AI-assistance disclosure copy. The exact disclosure remains subject to the business's reviewed legal requirements.
STOP means stop
When a messaging channel is later enabled, the pilot must recognize listed carrier STOP keywords, suppress future messages, record the event, and provide the required bounded confirmation. Day-1 does not transmit customer SMS.
Data rights need an operator
Pilot privacy, access, export, deletion, and retention requests go through a monitored human process documented in the signed pilot terms.
You're the sender of record
OwnerSwitch shows existing drafts for the business to review. You stay the sender on your existing business phone in Day-1.

Human approval boundary: every substantive customer-facing business send requires an authorized person's approval. Only narrow, fixed consent and opt-out confirmations are excepted; an approval authorizes queueing, not delivery.

How SMS consent works, start to finish

STEP 1
One mobile number, one named business
The SMS form collects a business code and mobile number only. It does not offer email consent or treat an inbound event as blanket consent.
STEP 2
The request must be accepted
We must verify the business code and accept the request. The form alone never turns texting on, and an unavailable request changes nothing.
STEP 3
The phone confirms
If a fixed confirmation text actually arrives, the recipient replies YES or START. A public follow-up page cannot confirm that the text was sent or delivered.
STEP 4
STOP is the direct opt-out path
Replying STOP goes through the carrier. A web opt-out or preference request takes effect only after we verify the business code and accept the request.

Four different message states

  • Approved means an authorized person approved the exact message.
  • Queued means the approved message is waiting to be sent.
  • Provider accepted means the provider accepted the send request; it does not prove delivery.
  • Delivered is shown only after a later verified delivery receipt.
SMS & AI policy Privacy policy Terms of service Trust & safety

This isn't legal advice. OwnerSwitch gives you the tools, disclosures, and records - you own the customer relationship and your compliance obligations. Confirm your requirements with your own counsel.

Getting messages from a business using OwnerSwitch? See what that means or stop messages any time.