SMS Consent & Opt-In Documentation

Program overview

Program Name: BuildCrux Contractor Notifications

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

Use Case: Low Volume Mixed (transactional + customer service). Contractors who use BuildCrux send SMS messages to their customers and team members about active projects: invoice ready notifications with secure payment links, change order approval requests requiring electronic signature, project status updates, two-way customer messages tied to a specific project, and team invitations.

Sender: Messages are sent from a BuildCrux-managed 10DLC long code registered with TCR under our brand BN3fa8b61c142c734e577318d79be37c5c. All messages identify the contractor’s business name in the message body.

How end-users opt in

BuildCrux is contractor software. Phone numbers are collected by the contractor at two distinct points, both of which display an explicit consent disclosure:

1. Contractor adds a customer to their workspace

When a contractor invites or adds a customer record in BuildCrux and enters that customer’s mobile phone number, the BuildCrux UI displays the following disclosure directly beneath the phone-number field, before the contractor can save:

By providing this number, the customer agrees to receive SMS notifications about their project. Standard message & data rates may apply. Reply STOP to opt out.

The contractor attests, by saving the form, that the customer has consented to receive SMS messages about their project. BuildCrux logs the timestamp, the contractor’s user ID, and the IP address at which the consent attestation was made. This log is retained for the life of the customer record plus the period required by applicable record-keeping rules.

2. Contractor invites a team member or subcontractor

When a contractor invites a team member or subcontractor and provides that person’s mobile phone number, the BuildCrux UI displays the following disclosure directly beneath the phone-number field, before the contractor can send:

By providing this number, the recipient agrees to receive SMS invitations and team notifications. Standard message & data rates may apply. Reply STOP to opt out.

The recipient receives a single SMS invitation linking to the BuildCrux account acceptance page. Subsequent team-related SMS messages (project assignments, customer messages routed through the team workspace) are sent only after the recipient accepts the invitation, which constitutes additional explicit consent.

3. Contractor account signup

Contractors creating a BuildCrux account provide their own mobile phone number for account verification (SMS one-time-password) and for receiving operational notifications (subscription receipts, security alerts). The BuildCrux signup form displays the following disclosure beneath the phone-number field:

By providing this number, you agree to receive SMS messages from BuildCrux about your account, billing, and security. Standard message & data rates may apply. Reply STOP to opt out at any time.

Message frequency

Frequency depends entirely on the activity of the customer’s project. During active phases of work, customers typically receive several messages per week (invoice ready, change order needs approval, project status update, message from the crew). Between phases, frequency drops to one or two messages per month or none at all. Customers do not receive marketing or promotional messages from BuildCrux through this program.

Sample messages

Sample 1 (invoice ready):

Crestview Builders: Your invoice INV-001 for $4,520.00 is ready. Pay securely: https://buildcrux.com/pay/abc123. Reply STOP to opt out.

Sample 2 (change order approval):

Crestview Builders: Change order CO-001 for the master bath remodel ($1,250) is ready for your approval. Review and sign: https://buildcrux.com/sign/def456. Reply STOP to opt out.

Sample 3 (project update):

Crestview Builders: Tile delivery is scheduled for Tuesday 4/30. Crew arrives 8 AM. Reply with questions or STOP to opt out.

Sample 4 (team invitation):

BuildCrux: Marcus Delgado at Crestview Builders invited you to join the team. Accept: https://buildcrux.com/invite/ghi789. Reply STOP to opt out.

Opt-out and help keywords

Standard A2P 10DLC keywords are honored automatically by the BuildCrux SMS infrastructure (managed via Twilio):

Once a recipient opts out, no further messages are sent from BuildCrux to that phone number unless the recipient explicitly opts in again by replying START. Opt-out is enforced at the messaging-service layer, so the contractor cannot accidentally re-message a recipient who has opted out.

Message and data rates

Standard 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 recipient phone numbers with third parties for marketing purposes. Phone numbers are used solely to deliver messages on behalf of the contractor who collected them. See our Privacy Policy for full data-handling disclosures, including the SMS sub-processors (Twilio, GoHighLevel) 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: end-users 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.