> For the complete documentation index, see [llms.txt](https://docs.mdintegrations.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mdintegrations.com/changelog/2025/sms-email-opt-in-controls-and-clinician-inbox-overhaul.md).

# SMS/Email Opt-In Controls & Clinician Inbox Overhaul

*Released March 17, 2025*

> **Breaking change:** Two new patient opt-in properties were added for SMS and Email communications, and a corresponding field was added to the Partner API. If you consume or set patient communication preferences via the API, review the API section below.

## \[Features]

* **Email/SMS Opt-in Flag**: two new patient properties controlling whether the patient wants SMS or Email communications, to reduce blacklisting/spam flagging and help you comply with regulations. If you use the white-label intake form or the Shopify integration, you get this automatically.
* **Shopify integration changes**: the existing Registration Form is deprecated. Patient creation moves from the Shopify checkout page to the Intake Form itself, which now pre-fills demographic details the store already collected, avoiding double entry.

## \[Clinicians]

* Changelogs, partner notifications, and global notifications now appear on Inboxes
* DoseSpot error messages from patient syncing now display on the encounter
* "Open Encounter" from inboxes opens in a new tab
* Button to trigger workflows directly from the message sidebar
* SMS message now sent for 2FA when logging into the Clinicians app
* Overweight ICD now added for patients over 25 BMI (was 27)
* Improvements to AI models, AI summary, and translation
* Attachments sent by patients via messages are automatically attached to the most recent encounter
* Added a Help Center with FAQ, Partner Details, and other resources in the Clinicians App
* Encounters (up to 2 at a time) actively worked by a physician now get a 30-minute grace period before reassignment
* Added opt in/out for patient SMS and emails
* Improved performance of flagging users
* Notifications under Partner Support auto-archived after 10 days
* Added a field for W9 form upload
* Added a field for physicians to set a default "thank you" video when no other video is set for a partner
* Added an audit log per prescription
* Added ability to add tags to attachments

## \[API]

* **Breaking:** added opt in/out for patient SMS and emails
* New webhook for Notifications
* New webhook for encounter charges (case completion, SMS submission, Vouched runs, etc.)
* Fixed 2FA codes not appearing over email due to Dark Mode
* Improvements to server infrastructure; introduced a dedicated Staging server
* Fixed HEIC files not processing properly
* New endpoint to mark messages as read
* Encounters from Created can now be moved to Support directly

## \[Website]

* You can customize automatic messages copy from the website
* Added a toggle to disable all AI summaries for a partner's encounters
* Users from a parent company can now manage child company details
* Added statistics for clinician state coverage

## \[Patient App]

* Session now based on browser session (refreshing no longer logs patients out)
* Added opt in/out for patient SMS and emails
* Patients can select which inbox (clinician/support) to send messages to
* Added ability to track intake form abandonment per question

## \[Shopify]

* Improved flow to account for additional products added to cart after the cart screen
* Registration form no longer the default for new stores; patient creation now happens in the white-label Intake Form

## \[WooCommerce]

* Introduced a new WooCommerce plugin — a no-code integration for WordPress-based partners


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.mdintegrations.com/changelog/2025/sms-email-opt-in-controls-and-clinician-inbox-overhaul.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.