SMS Consent Disclosure Example

This page is a production-equivalent consent example for Ops Current service-business notification workflows. It reproduces the SMS consent disclosure a customer sees when a service business using Ops Current asks permission to send transactional service notifications.

This is an example, not a live form. Nothing on this page is submitted, stored, or sent. The mobile number field is inactive and collects nothing. To actually opt out of messages you already receive, reply STOP to any message, or use the Ops Current opt-out page.

Example consent disclosure

Mobile number

Inactive in this example. A live form would accept the customer’s own number here.

How this consent works

This example reflects the SMS consent disclosure used by service businesses that use Ops Current for transactional service notifications. A customer must affirmatively select an unchecked consent checkbox before receiving text messages. Entering a mobile number alone does not constitute consent.

Messages may include appointment confirmations and reminders, schedule changes, technician arrival notices, service-request updates, and customer-support communications. The service business named in each message is the customer-facing sender; Ops Current provides the communications platform.

Shared-number limitations

Some service notifications may be sent from a shared Ops Current platform number. That number is used for automated notifications and is not monitored for two-way replies. Recipients can reply STOP to opt out or HELP for help, and should contact the service business named in the message for appointment or service assistance.

Program documents

The messaging program described here is the Ops Current Service Notifications Program, operated by Ops Current, a field-service software platform operated by BetterData LLC. Full terms and privacy disclosures:

Questions about the messaging program: support@opscurrent.com