A2P 10DLC Documentation

SMS Consent & Opt-In Documentation

How BuildCrux account holders opt into transactional SMS notifications about their own account.

CTIA Best Practices & A2P 10DLC CompliantUnited StatesLast updated May 16, 2026
Scope of this campaign: This page documents the Account Notification SMS campaign only. Customer-facing project messages and team-invitation SMS are not part of this campaign and are not currently sent via this brand. They will be submitted under separate campaigns if and when SMS support is added for those flows.

Program overview

Program name: BuildCrux Account Notifications

Operator: TackOn Labs LLC, doing business as BuildCrux. Federal EIN on file with TCR (The Campaign Registry).

Use case: Account Notification. The BuildCrux platform sends low-volume transactional SMS messages to its own contractor account holders, regarding their own BuildCrux account: subscription renewals, plan changes, payment-failure alerts, password-change confirmations, and new-sign-in security alerts.

Sender: Messages are sent from a BuildCrux-managed 10DLC long code registered with TCR under our brand BN3fa8b61c142c734e577318d79be37c5c. Every message identifies BuildCrux as the sender in the message body.

Out of scope (separate campaigns or not yet enabled): customer-facing project messages (invoice ready, change order, schedule update, payment receipt), workspace team and subcontractor invitations, two-factor authentication codes, marketing or promotional content. None of these are sent under this campaign.

How end-users opt in

BuildCrux is contractor software. The end-user of this SMS campaign is the contractor who holds a BuildCrux account. There is no third-party consent flow in this campaign — the recipient is always the same person who personally checked the consent box on the BuildCrux website.

Opt-in flow

URL (behind login): https://buildcrux.com/dashboard/settings

  1. The contractor signs into their BuildCrux account and navigates to Settings > Business Info.
  2. The Phone field is optional. A contractor can create an account, subscribe to a paid plan, and use BuildCrux fully without ever providing a phone number. Phone collection and SMS consent are never a condition of service.
  3. When the contractor types a phone number into the field, an unchecked SMS consent checkbox appears directly beneath the input, with the verbatim disclosure shown below.
  4. The checkbox is unchecked by default. The contractor must manually click the checkbox to opt in. Saving the form without checking the box is permitted and creates no SMS enrollment.
  5. When the contractor checks the box and presses Save, the server records the consent timestamp on the workspace record (workspaces.sms_consented_at). This timestamp is the affirmative opt-in evidence we retain.
  6. The contractor can unsubscribe at any time by unchecking the box and pressing Save, or by replying STOP to any received message. Either action clears the opt-in timestamp and stops all future sends to that phone number.
Screenshot of the BuildCrux /dashboard/settings page showing the optional phone field with an unchecked SMS consent checkbox and the verbatim disclosure beneath it.
The Business Info section at /dashboard/settings. The phone field is optional. When a phone number is typed, an unchecked checkbox appears with the SMS consent disclosure. The checkbox is never pre-checked. The user must manually select the checkbox to opt in; saving without checking creates no SMS enrollment.

Verbatim disclosure text shown to users

The following text is shown next to the unchecked checkbox on the Settings page. The checkbox label is the consent statement; the user must affirmatively check it before any SMS is sent.

I agree to receive transactional SMS notifications from BuildCrux regarding account activity, billing, and security alerts to the number above. Message frequency varies. Message and data rates may apply. Reply HELP for help and STOP to opt out. Consent is not a condition of purchase. See our SMS terms and Privacy Policy.

Confirmation message after opt-in

Immediately after the contractor saves their consent, the system sends a single welcome message to confirm enrollment:

BuildCrux: You are opted in to transactional account, billing, and security SMS alerts. Msg frequency varies. Msg & data rates may apply. Reply HELP for help, STOP to opt out.

Message frequency

Low volume. A typical contractor receives 0–3 messages per month from this campaign — only when an actual account event occurs (subscription renewal, plan change, payment failure, password reset, new sign-in). Contractors with no plan changes and no payment issues may receive zero messages from this campaign in a given month. No promotional or marketing messages are sent under this campaign.

Sample messages

Sample 1 (subscription renewal):

BuildCrux: Your Crew subscription renewed for $149 on 06/01/2026. View receipt at https://buildcrux.com/dashboard/billing Reply STOP to opt out.

Sample 2 (payment failure):

BuildCrux: Payment failed for your Office subscription ($349). Update your payment method to avoid interruption: https://buildcrux.com/dashboard/billing Reply STOP to opt out.

Sample 3 (new sign-in security alert):

BuildCrux: New sign-in to your account from Dallas, TX on 06/01/2026. Not you? Secure your account at https://buildcrux.com/dashboard/settings Reply STOP to opt out.

Opt-out and help keywords

The full A2P 10DLC keyword set is honored automatically by the BuildCrux SMS infrastructure:

Keyword typeRecognized wordsSystem response
Opt-outSTOP, OPTOUT, CANCEL, END, QUIT, UNSUBSCRIBE, REVOKE, STOPALL“You have successfully been unsubscribed. You will not receive any more messages from this number. Reply START to resubscribe.”
HelpHELP, INFO“Reply STOP to unsubscribe. Msg&Data Rates May Apply. Support: support@buildcrux.com”
Opt-in (resubscribe)START, UNSTOP“You are now opted in to BuildCrux account notifications. Reply STOP at any time to unsubscribe.”

Once a recipient opts out, no further messages are sent from BuildCrux to that phone number unless the recipient explicitly opts in again by either replying START or re-checking the consent box on the Settings page.

Message and data rates

Message and data rates from the recipient’s wireless carrier may apply to each message. BuildCrux does not charge recipients for messages. Recipients should check their carrier plan for SMS rate details.

Supported carriers

AT&T, T-Mobile, Verizon, US Cellular, and other major US wireless carriers. Carriers are not liable for delayed or undelivered messages.

Privacy

BuildCrux does not share phone numbers with third parties for marketing or promotional purposes. Mobile information and SMS opt-in consent are not transferred to any third parties or affiliates for marketing or promotional purposes. See our Privacy Policy for full data-handling disclosures, including the SMS sub-processors we use for message delivery.

Terms

The complete SMS Messaging Program Terms are available in our Terms of Service, Section: SMS Messaging Program Terms (A2P 10DLC).

Questions or complaints

For questions about the BuildCrux SMS program, opt-out issues, or to report a complaint, contact us:

  • Email: support@buildcrux.com
  • Reply HELP to any message you receive from us
  • Mail: TackOn Labs LLC (DBA BuildCrux) — address available on request to support@buildcrux.com

This page exists for two audiences: BuildCrux account holders who want to know how their phone number will be used, and TCR (The Campaign Registry) reviewers verifying our A2P 10DLC campaign registration. The opt-in flow described above matches the production BuildCrux application as of the “Last updated” date above. Customer-facing project messages and team-invitation SMS are not part of this campaign.