Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

  • WEBINARS
  • ARTERA ACADEMY
  • SUPPORT
  • RELEASES
  • STATUS PAGE
  • Home
  • Add-Ons

Branded Messaging | Available Experiences

Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

  • Get Started
    Getting Help Post-Implementation
  • Troubleshooting and FAQ
  • Release Notes
    Release Notes: Artera Harmony Federal Edition
  • AI Agents
  • Patient Channel
    Managing Appointments
  • Triggers
    Appointment Triggers Inbound Message Triggers Recall Triggers Referral Triggers
  • Technical Specifications
    Artera Foundation Artera-Specific Features EMR Specifications
  • Patient Facesheet
  • Insights & Analytics
    Insights Analytics Plus Self Service Analytics
  • Conversation Flows
  • Campaigns
  • SMS Basics
  • Inbox
  • Lines & Resources Requests
  • Lines, Events, Resources
  • Referrals
  • Add-Ons
    Call-To-Text/Abandoned Calls Community Outreach Intake
  • Users and Groups
  • Platform Settings and Configuration
    Settings
  • Self-Rescheduling
  • Recalls
  • Artera Harmony Federal Edition
    Conversation Flows | AHFE Triggers | AHFE Platform Settings & Configuration | AHFE Users and Groups | AHFE Patient Channel | AHFE Troubleshooting and FAQ | AHFE Patient Facesheet | AHFE Campaigns | AHFE Lines, Events, Resources | AHFE Get Started | AHFE Inbox | AHFE Release Notes | AHFE Analytics | AHFE
  • Marketplace
+ More

Table of Contents

What Patients Receive in Each Branded Messaging Experience Android and Apple Differences Standard RCSRCS WebviewsFAQs

Artera offers two Branded Messaging experiences. Both display your organization's branding. They differ in where the patient reads the message sent to them.


Your Customer Success Representative will work with you to determine which experience to enable for your organization as this experience is set for the whole Enterprise, not per Practice or per line. The experience applies to every branded line in your Enterprise and both experiences require a branded line. You choose which lines to onboard for Branded Messaging, but not which experience each line uses. 


A Practice line must be onboarded to support Branded Messaging before patients receive either experience on that line. Lines that have not been onboarded continue to send regular SMS text messages without branding. For what onboarding a line involves, click here.

What Patients Receive in Each Branded Messaging Experience

Experience

Secure Message

Unsecure Message (Plain Text)

Standard RCS

Authenticated webview card, within patient’s messaging app

Displayed in patient’s messaging app

RCS Webviews

Authenticated webview card, within patient’s messaging app

Webview card, within patient’s messaging app

Android and Apple Differences

Some Branded Messaging features are supported differently depending on whether the patient uses an Android or an Apple device. This applies to both experiences.


Android

Apple

Banner Image

Supported

Not Supported

Brand Color

Supported in Light Mode

Not Supported

Quick Links

Supported

Not Supported

Info Tab

Supported

Supported

Options Tab

Supported

Not Supported

Tap Back Reactions

Not Supported

Supported

Multiple Phone Numbers Displayed in Contact Information

Supported

Not Supported

Standard RCS

A patient receives a text message with your organization's branding for the line that was used to send the message. 

NOTE: Branded Messaging appearance may vary slightly between Android devices. The feature is visible on "light mode" and "dark mode" enabled devices.

Standard RCS: Android Devices



Standard RCS: iPhone

Standard RCS: Files and Attachments

Which file types are supported when an RCS message is sent to a patient?

JPEG, PNG, MP3, MP4, DOC, DOCX, XLS, XLSX, and TXT file types are supported.

NOTE: PDFs are not supported with RCS messages but are supported with SMS/MMS messaging.


Which file types are supported when a patient sends in an RCS message?

JPEG, PNG, MP3, MP4, DOC, DOCX, XLS, XLSX, and TXT file types are supported.

NOTE: JPEG files are not supported with RCS messages for Apple devices, only Android. PDFs are not supported with RCS messages for either device type but are supported with SMS/MMS messaging.


How large can a file be?

Patients and Artera users can send files as large as 16 MB. However, if the patient is not using an RCS-enabled device, the file can be no larger than 5 MB. For this reason, we do not recommend creating files larger than 5 MB. Additionally, ensure that file names do not include a space, are fewer than 20 characters, and avoid special characters.

RCS Webviews

With the RCS Webviews experience, the patient receives a webview card in their messaging app instead of the message sent to them. The webview card displays your RCS Secure Message Copy, an optional logo, and a View Message button. 


Selecting the button opens the message within an authenticated webview directly inside the patient’s messaging app, allowing the patient to verify their identity, review the message, and reply without leaving their app. 


The View Message button is labeled in the patient’s language, when that language is supported. The rest of the webview appears in that language as well. If no translation is available, the View Message button and the webview appear in English. Click here to learn more about available languages. 

How a Patient Accesses a Message via RCS Webviews

  1. The patient receives a webview card in their messaging app and selects View Message. 

  2. The patient verifies their identity and selects View Secure Message. NOTE: What the patient enters to verify their identity depends on your Patient Sign-in Security Criteria Default Setting. 

  3. The conversation opens in an authenticated webview inside the patient’s messaging app.

The patient does not leave the conversation at any point. From the authenticated webview, they can read and reply to the message sent to them.


NOTE: For security, the patient has 60 minutes from when the webview card arrives to open the message. After that, selecting View Message opens a screen with a Send me a new link button. When the patient selects that, a new webview card arrives in the same conversation. The patient then selects View Message on the new card to read the message.


When a Message is Sent as a Text Message Instead

In the RCS Webviews experience, a patient receives a standard text message rather than a webview card when: 

  • The Customize RCS Secure Message Default Setting has no saved message copy. This field is empty until an Enterprise User adds a copy and saves it, so an organization set to RCS Webviews sends standard text messages until that happens. If the copy is later removed, no webview card is sent. 
  • The webview card cannot be delivered. It is re-sent as a standard SMS. Images and videos are then sent as MMS and other file types are replaced with a link. 
  • The patient is not matched to a patient record in your Enterprise. This includes a patient who texted into the Practice from a number Artera does not recognize and a patient a user added manually in Artera. Artera cannot send a Secure Message to these patients, so they receive a standard text message. Once an EHR feed matches them to a patient record, they can receive the webview card. Click here to learn more about Unverified Patients. These are Unverified Patient types 3 and 4. 

Privacy Timeout

Since the authenticated webview opens inside the patient's messaging app, it can stay open in the background while the patient uses their mobile device on other tasks. After 15 minutes without activity, the conversation is hidden and the patient is prompted to close the window and select View Message again to continue.

Customize the RCS Webview Card

Four Default Settings control how the webview card looks for the patient.

NOTE: These Default Settings only appear once Artera has enabled RCS Webviews for your organization.


Customize RCS Secure Message

On RCS lines, these messages are sent as a webview card with this copy and a View Message button. Only Practice, Enterprise, and Line Smart Phrases can be used here. This means no patient details appear on the webview card. This field is empty until an Enterprise User adds a copy and saves the Default Settings page. No webview card is sent until the copy is saved. 


RCS Webview Size

How much of the patient’s screen the webview card opens in when the patient selects View Message. Choose Three quarters of the screen (default) or Full screen.

RCS Card Logo

An optional .png or .jpeg image, typically your organization’s logo, shown above the webview card copy. Without a logo, the webview card displays the RCS Secure Message copy only. Artera does not enforce a maximum file size or maximum dimensions. Test your logo on a mobile device in both the Vertical and Horizontal layouts to confirm it displays the way you expect.


RCS Card Layout

Choose Vertical (default) to display the logo above the message copy or Horizontal to show it as a small image next to the copy.

FAQs

Both experiences


Which experience does my organization have?

If you are unsure, connect with your Customer Success Representative.


Is Branded Messaging viewable on a device's light and dark modes?

Yes, Branded Messaging is viewable on a patient's light or dark-mode enabled devices.


Will Artera users know that they may be sending RCS messages?

No, users will not know whether they are sending RCS or SMS/MMS messages to patients as the user experience does not change.


Standard RCS

Will patients know that they are texting into an RCS-supported line?

If a patient texts into a line enabled to support RCS and the patient has a device and carrier that is also RCS-supported, their message will be sent to the line as an RCS message. Patients will know that they are sending an RCS message because of the visual assets associated with the message itself. Another indicator is that the text box within the message will read as "RCS message" for Android devices and "Text Message - RCS" for iPhones.

RCS Webviews

Do users need to mark messages as secure for patients to receive a webview card?

No. In RCS Webviews, both secure and unsecure messages are sent as webview cards when the branded line is being used to send the message.


Does the patient need to download anything?

No. The webviews experience opens inside the patient's messaging app as an authenticated web page.


Do Unverified Patients receive webview cards?

Some do. It depends on whether the patient is matched to a patient record in your Enterprise. 


A patient who has a record in your Enterprise but is not assigned to a Practice is labeled Unverified and these patients do receive webview cards. These are Unverified Patient types 1 and 2 here. NOTE: If your EHR never sent the detail that your Enterprise's Patient Sign-in Security Criteria setting requires, the patient cannot open the message.


A patient who is not matched to a record in your Enterprise always receives a standard text message. This includes a patient that a user manually added in Artera and a patient who texted into the Practice from a number Artera does not recognize. These are Unverified Patient types 3 and 4 here. Once an EHR feed matches the patient to a record, they receive webview cards. 


What does "read" mean for a webview card?

In the RCS Webviews experience, “read” means the patient saw the webview card in their messaging app. It does not mean they opened the message in the Secure Message Portal. For what the Branded Messaging dashboard reports, see Branded Messaging

unlabeled unnamed rcs webview webviews branded messaging card view message tap to view file types

Was this article helpful?

Yes
No
Give feedback about this article

Related Articles

  • Message Formatting Guidelines
  • Conversation Flows FAQ | AHFE
  • Patient Communication Settings
© 2026 Artera. All Rights Reserved.
Artera.io | Privacy Policy | Terms of Service | Cookie Policy | Do Not Sell My Personal Information

Knowledge Base Software powered by Helpjuice

Expand