A2P 10DLC — opt-in workflow documentation

How customers opt in to texts

This page documents, for carrier and campaign review, exactly how end users consent to receive text messages from a business that uses Rally. It is public and requires no login, and the opt-in surface it describes can be reviewed directly at rallyai.net/sms-opt-in.

Declared opt-in methods

Rally collects SMS consent by two methods only. Both are listed below with the evidence for each.

  • Web form (registered as Web Form) — The customer visits a public page, enters their name, the business they are working with, and their mobile number, and checks a consent box that is unchecked by default.
  • Customer texts the business first (registered as Via Text) — The customer sends the first message to the business's own published number. The business's first reply identifies the sender and carries the opt-out instruction.

Rally does not collect SMS consent verbally, and does not collect it on paper, by QR code, or from any purchased, rented, or shared list. No numbers are ever purchased, rented, or shared. Mobile opt-in information is never shared with third parties for marketing purposes.

Consent is optional

SMS consent is optional. It is not bundled into any Terms of Service, and it is not a condition of purchase or of receiving service. A customer who declines still receives the same service from the business. The consent checkbox is a separate, standalone control that is unchecked by default; the page it appears on does nothing except sign a customer up for texts — no account is created and no transaction is completed there.

Sender for the currently registered campaign

The campaign registered against this documentation is operated by M2Innovate LLC, which uses its own Rally software to message its own existing customers about the work it performs for them. M2Innovate is both the registered brand and the sender; it does not send on behalf of any other business under this campaign.

Method 1 — Web form

Public, unauthenticated, no payment required: https://rallyai.net/sms-opt-in

The page's purpose is to send a service request to the business. SMS consent is a separate, optional add-on to that request — it is not bundled into any terms, and it is not a condition of submitting the form, of a purchase, or of receiving service.

The consent checkbox is optional. It is unchecked by default, and the form submits either way: a customer who leaves it unchecked still has their service request delivered to the business and simply receives no text messages. Consent gates nothing except texting. Figures 4 and 5 below show that path end to end. The label reads, verbatim (consent wording version 2026-09-08.v1):

I agree to receive text messages from my service provider via Rally about my job — appointment confirmations, quotes and quote follow-ups, arrival times, and answers to my questions. Message frequency varies. Msg & data rates may apply. Reply STOP to opt out, HELP for help. Consent is not a condition of purchase.

Links to SMS Terms and Privacy Policy sit directly beneath the checkbox, at the point of collection. Every submission is recorded with the customer's name, mobile number, the business named, the exact wording agreed to, the wording version, and a timestamp.

The Rally service request form at rest, showing empty fields and the SMS consent checkbox unchecked by default, above a Send request button.
1. The form at rest. The consent checkbox is unchecked by default, and the line above it reads: “Text updates are optional. Leave this unchecked and we'll still get your request — we just won't text you.”
The service request form completed, with the SMS consent checkbox deliberately checked by the user.
2. The same form completed with the checkbox checked by the user — consent is an affirmative act, never a default.
The confirmation after submitting with consent, reading Request sent and you are signed up for text updates.
3. Submitted WITH consent: the request is sent and text updates begin, restating STOP and HELP.
The service request form completed with the SMS consent checkbox left unchecked, ready to submit.
4. The same completed form with consent DECLINED — the checkbox left unchecked. The Send request button is active; consent does not gate submission.
The confirmation after submitting without consent, reading Request sent and you will not receive text messages.
5. Submitted WITHOUT consent: “Request sent… You will not receive text messages — you didn't ask for them, and that doesn't affect your request.” This is the proof that the checkbox is optional and that declining still lets the customer proceed.
A stored Rally consent record showing name, redacted mobile number, business, consent method, timestamp, source URL, wording version, and the exact wording agreed to.
6. The stored record for a consented submission: name, mobile number (redacted here for publication), business, how consent was given, timestamp, source URL, wording version, and the exact wording agreed to.

Method 2 — Customer texts the business first

The customer sends the first message to the business's own published number. This is the most common path: most messages on this campaign are replies within a conversation the customer started. The business's first reply identifies the sender and carries the opt-out instruction.

Where the number and opt-in instructions are published: see rallyai.net/text-us, which shows the business number alongside the same disclosures as the form above.

Every message sent on this path carries a sender-attribution and opt-out block appended by the system. On this campaign's number type it reads, verbatim:

Via Rally · text STOP to opt out

Why there is no screenshot for this method. Producing a real first reply requires sending an application-to-person message, which requires an approved campaign — circular for a sender awaiting first approval. The workflow and the exact appended text are documented above instead. We will not submit a simulated message image, because a mocked-up screenshot is not evidence of anything.

Required disclosures

Every opt-in path discloses all of the following before or at the moment consent is given:

  • who is sending (the business the customer hired, using Rally)
  • what the messages are about (appointments, quotes and follow-ups, arrival times, replies)
  • that message frequency varies
  • that Msg & data rates may apply
  • that consent is not a condition of purchase
  • the STOP and HELP keywords

How to stop

Reply STOP (or STOPALL, UNSUBSCRIBE, CANCEL, QUIT, END) to any message to stop receiving texts. The customer receives one confirmation and nothing after that. Reply START, UNSTOP, or YES to opt back in. These keywords are honored both at the carrier layer and in Rally itself, which records the opt-out against the customer and blocks further sends.

How to get help

Reply HELP to any message. HELP is answered through the messaging provider's standard keyword handling on the Messaging Service carrying this campaign. For anything further, or to reach a person directly, email info@rallyai.net.

Policies

SMS Terms · Privacy Policy · Opt-in form