A dental call and text opt-out workflow

Recognize the request in ordinary language

Patients do not always use the word opt-out. They may say, “Please stop texting me,” “Do not call this number,” “Use email instead,” or “I only want appointment messages.” The first operational rule is to listen for the patient’s meaning instead of requiring a special phrase or form.

The American Dental Association advises practices that patients may revoke consent to calls or texts by reasonable oral or written means. Its guidance tells staff to stay alert to those requests, record them promptly, and stop the affected calls or texts immediately. A clear request should therefore create an action during the conversation, not a note for someone to interpret later.

• Confirm which number or channel the patient wants stopped when the request is specific
• Do not require the patient to repeat a clear request through another form or department
• Avoid asking for a reason as a condition of honoring the request
• Separate a full stop request from a preference for another permitted channel
• Escalate uncertainty without continuing the disputed outreach in the meantime

Create one authoritative suppression record

The greatest risk is not failing to hear the request. It is recording the request in one place while another system keeps working from an older list. A note in the PMS may not reach the texting platform. A reply of STOP may not update a manual call sheet. A receptionist may know the patient’s preference while a vendor queue still shows the number as eligible.

Choose one record that every workflow treats as authoritative, then define how updates reach the PMS or CRM, calling and texting tools, recall lists, appointment-confirmation queues, missed-call callbacks, unscheduled-treatment follow-up, and any outside vendor. The record should be specific enough to prevent accidental suppression of a channel the patient still wants to use.

• Patient and phone number or address affected
• Channel stopped, such as calls, texts, or both
• Scope understood from the patient’s request
• Date, time, source, and exact wording or a faithful summary
• System and person responsible for propagation
• Confirmation that active queues and scheduled messages were checked

Propagate the stop before another attempt

An opt-out workflow is complete only when the request reaches every place capable of contacting the patient. Operationally, the safest standard is to suppress the affected channel immediately, remove or pause the patient in active queues, cancel scheduled messages where possible, and update any vendor or integration that holds its own contact state.

The FCC’s current rule recognizes several reasonable methods for revoking consent, including common text keywords and other language that a reasonable person would understand as a request to stop. For covered calls and texts, the rule generally requires requests to be honored as soon as practicable and no later than 10 business days. ADA guidance for dental practices is more conservative operationally and says to stop immediately. Practices should use qualified legal guidance for their exact technology, message type, exemptions, and jurisdiction.

• Suppress the affected channel in the source patient record
• Remove the patient from open recall and reactivation queues
• Cancel queued texts or calls that have not yet been sent
• Update confirmation, no-show, cancellation, and treatment follow-up workflows
• Notify vendors or connected systems that do not sync automatically
• Keep an audit trail showing when each system accepted the update

Test the workflow and keep the legal nuance visible

Do not assume that a saved preference has reached the whole operating stack. Run a controlled test from each intake path: a spoken request during a call, a standard text keyword, an ordinary-language text, a voicemail, a front-desk note, and a vendor-managed conversation. Confirm that each path updates the authoritative record and blocks the next affected attempt.

One FCC requirement needs careful wording. In January 2026, the FCC extended a waiver until January 31, 2027 for the narrow rule that would apply a revocation made in response to one type of informational message across unrelated future robocalls and robotexts from the same caller. The order says that extension does not change other existing revocation rules. Do not turn that narrow delay into permission to ignore a clear request, and do not assume one request has the same legal scope in every workflow.

Contact preference, confidential-communication requests, and TCPA revocation are related but not identical. ADA HIPAA guidance says covered dental practices should accommodate reasonable requests to communicate by alternative means or at alternative locations. Your workflow should preserve those distinctions while giving staff one clear next action. This is operational guidance, not legal advice.

• Sample recent opt-outs and confirm no later affected outreach occurred
• Review delayed syncs, failed vendor updates, and duplicate patient records
• Train staff with realistic phrases instead of one approved keyword
• Assign an owner for exceptions, complaints, and ambiguous scope
• Recheck the workflow whenever a PMS, CRM, phone, or texting integration changes
• Document which policies and jurisdictions qualified counsel reviewed