A consent and records checklist for member text messages

Published November 6, 2026

A studio texts a member about a cancelled class, then adds a promotional line about a new package. A week later the same number receives a re-engagement message because the member has not booked in a month. Each message feels small and routine, but together they form a record that the studio may need to explain later. The record is easier to defend when the studio decides in advance what it will keep and who may send it.

Text messaging sits at the intersection of operations, marketing, and privacy. A booking reminder has a different purpose from a discount offer, and the consent needed for each is not identical. The Federal Communications Commission explains that text messages are covered by consumer protections against unwanted calls and texts. The FTC's CAN-SPAM guidance covers commercial email and offers a useful contrast for how commercial messages are regulated.

Every reminder and re-engagement text is a records decision

A text message leaves several traces. The platform stores the outbound message, the delivery status, and sometimes the reply. The member's consent may live in the booking platform, the waiver, or a separate marketing tool. The studio may also keep a spreadsheet of people who asked not to be contacted.

Those traces rarely sit in one place. A front-desk assistant may send a reminder from the scheduling tool while a marketing vendor sends a promotion from another system. The member experiences one relationship, but the studio manages three record sets. A consent decision in one system does not automatically reach the others, so the first step is to name the owner of each record.

Separate transactional messages from marketing

A transactional message supports a transaction the member already requested. A class confirmation, a schedule change, a receipt, and a waitlist notice are common examples. A marketing message promotes something the member has not specifically asked to receive, such as a new package or a seasonal offer. The distinction matters because consent and opt-out expectations differ.

Marketing messages usually need a clearer, more specific permission, and they need an easy way to stop receiving them. Transactional messages still need accurate contact details and a way to reach the studio, but they serve a different purpose. Do not blend the two in one message to avoid the rules. Adding a promotion to a class reminder can turn a service message into a commercial one.

Record consent with enough detail to defend it

A checkbox is not a complete consent record. The studio should capture who consented, what they consented to, when, and through which channel. It should also capture the exact wording the member saw at the time. Store the consent event with the member identifier and the source.

Keep the version of the form or script that was in use on that date. Wording changes over time, and a later reviewer needs to know what the member actually agreed to. Record the scope in plain language, such as marketing texts about offers and events, rather than a vague phrase like promotional communications. The assistant can then check whether a proposed message falls inside the scope before sending it.

Keep the opt-out path inside the same system

An opt-out is only effective if it reaches every system that sends messages. A member who replies stop to one vendor may still receive messages from the booking platform and the front desk. That gap is one of the most common causes of a complaint. Give members a single, visible way to stop marketing texts, and honor it across tools.

The reply keyword is useful, but it should not be the only path. A link in the message footer and a front-desk request should feed the same suppression list. Test the opt-out path before a campaign by sending a test message, replying with the stop keyword, and confirming that the suppression reaches each sender. Review the suppression list monthly for duplicates and stale numbers.

Give the front desk a short script for a verbal opt-out. The staff member should confirm the request, record the date and channel, and tell the member which messages will stop. Do not ask the member to repeat the request through a different tool just to satisfy a form. The script should also say what still counts as a service message, so the member is not surprised by a class cancellation notice.

Define what a VA may send and what needs approval

A virtual assistant can do useful messaging work without owning the policy. The assistant can send approved templates, confirm delivery, record replies, and route an opt-out to the right owner. The assistant should not invent a new campaign, change the consent language, or decide that a member's objection is unimportant. That boundary protects the member and the studio.

Write a short authority list with three levels. Level one covers routine transactional templates that the assistant may send without review. Level two covers messages that need a manager's approval before sending. Level three covers anything involving a complaint, a legal threat, a health concern, or a refund request, which goes to the owner immediately. Attach examples to each level so the boundary is concrete.

Retain the consent record and the message log

Keep the consent record for as long as the studio relies on it, and keep the message log long enough to answer a question about what was sent. The exact period depends on the studio's legal and operational obligations, so the owner should confirm it with counsel and record the answer. Write the chosen period beside the record type so the assistant does not have to guess. The message log should include the member identifier, the template or campaign, the send time, and the delivery status.

It should also include the suppression state at the time of sending. That field lets a reviewer see whether the message was sent before or after an opt-out. Do not keep unnecessary personal data in the log. A message identifier and a member reference are often enough, while the full message body may not be needed after a short operational window.

Recheck templates when the program changes

Templates drift. A manager adds a promotional line, a vendor updates a footer, or a new hire copies an old message from a personal phone. Each change can alter the message category and the consent requirement, even when the intent stays the same. A review before any template goes live and after any edit keeps the program aligned.

The review should confirm the category, the consent scope, the opt-out language, and the sender identity. Record the reviewer and the date in the template library. Run a quarterly sample of live messages and compare them with the approved templates. Look for missing opt-out language, unapproved offers, and messages sent outside the member's stated scope.

Keep a simple change log for the messaging program. Note the template name, the change, the reviewer, and the date, and link the entry to the approved copy. The log makes it possible to answer a question about an older message without reconstructing the program from memory. It also shows whether a new vendor or channel was ever reviewed.

Limits and sources

This checklist is a local operating aid, not a legal opinion. The FCC's consumer guidance describes the rules for unwanted calls and texts, and the FTC's CAN-SPAM guide explains the separate commercial email rules. Neither source replaces advice from counsel who knows the studio's jurisdiction, contracts, and message practices. The owner should document the retention period it chooses and the reason behind it.

The NIST Privacy Framework treats data minimization and retention as risk-management choices. The SBA cybersecurity guidance recommends limiting access to sensitive business data and keeping software current. Apply those habits to the messaging tools as well, because a shared login that nobody owns is a weak link in the consent record. A fitness virtual assistant can maintain the record and send approved messages, but the owner keeps the policy decision.

For related reading, see a retention schedule for fitness studio attendance and billing exports and reconciling a member freeze across billing, access, and the class roster. Both methods depend on records that are complete enough to answer a member's question. A messaging checklist works best when it points to the same source of truth. The assistant prepares the evidence, and the owner decides the policy.