Artera positions its platform around a single communications backbone called Artera Harmony, which the vendor says powers patient calls, texts, and notifications while connecting to an organization's EHR. The knowledge base describes a Patient Channel interface where staff review inbound and outbound messages, event notifications, and internal escalation tools. This profile separates vendor marketing claims from documented product workflows and notes where implementation scope depends on EHR configuration. [1][2][3][4]
Patient Channel Structure and Message Types
The Patient Channel is opened by selecting a patient from the All Messages view. Conversation history combines inbound messages from patients and outbound messages to patients, organized by date, with each message showing a timestamp, sender name, and whether it was sent securely. Outbound messages appear in black on the right side of the channel, with icons indicating delivery by call, text, or email. [1][3]
Outbound messages can originate through Bulk Messages, AI Agents, Conversation Flows, Send Message API, Campaigns, or manual user action. The knowledge base assigns labels to indicate the sending mechanism, including Trigger, AI Agent, Artera, and Outbound via API. Vendor documentation states that the Artera label also appears for non-manual messages sent before 2024, which suggests that message labeling has changed over time. [1][3]
Event Messages and Internal Mentions
Event Messages appear in the center of the Patient Channel and are not visible to patients. They are time-stamped and indicate that an action has occurred, such as a patient taking action on an appointment, demographic information changing in the EMR, a channel status change, multiple patients sharing a phone verification, message delivery failure, or Conversation Flows activity. [1][3]
Internal Mentions let staff tag a user or User Group directly within a Patient Channel. The knowledge base describes this as useful for escalating a patient conversation to a teammate. Internal Mentions are not sent to patients and appear in red. Staff can locate channels where they are tagged from the Activity view. [1][3]
MAPI Setup and Operational Decisions
MAPI setup begins with a Customer Success Representative. Artera works with the organization to understand desired use cases, scope workflows, set up a technical scoping conversation, and authorize the EMR to send messages through Artera. At a high level, the organization provides IP addresses, procures API keys, and makes operational decisions before connecting to Artera's API Demo and Production endpoints. [5]
The documentation notes that if a patient opts out of messaging, they would be opting out of all messaging from that line, including appointment reminders. It also states that MAPI may not be best suited for enterprises that use a call center to support this type of messaging. For one-way messaging practices, the documentation recommends configuring Practice Hours so all seven days are included with open and close times set from 1:00 AM to 1:01 AM. [5]
Lines, Channel Status, and Manual Messaging
A Patient Channel shows only the conversation history for the line currently being viewed. If a practice has multiple lines, or if a patient has communicated with different practices, conversations are spread across separate Patient Channels. The documentation notes that practices often use different lines for different purposes, such as one for scheduling and another for other functions. [1][3]
Staff can manually change a Patient Channel status to Open, Close, or Needs Action from the top-right corner of the channel. When manually messaging a patient, the message composer defaults to the same sending method as the last outbound message in that channel. For example, if the most recent outbound message was a phone call, the composer defaults to Call. [1][3]
AI Agents and Omnichannel Capabilities
Artera's marketing materials describe Artera Harmony as an agentic platform that plugs directly into an EHR and manages conversations across channels. The vendor lists voice, RCS/SMS, and branded calling and text capabilities, including inbound and outbound voice, two-way texting, rich media messaging, verified sender branding, interactive scheduling, and live transfer. [4][6]
The knowledge base describes AI Agents for scheduling, intake, referrals, payments, care gaps, and more, with options to deploy standard solutions or build custom solutions through AI Service Squads. Patients can reach AI agents through an existing phone number integrated into a phone tree or through a dedicated AI agent line. The documentation states that AI Agents can transfer a patient to a live representative in several situations. [7]
Conversation Flows and Messaging API
Conversation Flows use natural language understanding so patients can respond in their own way rather than following structured prompts. The documentation gives the example of a thumbs-up emoji being recognized as a yes intent. Flows can be created from pre-built templates in the Conversation Flows Library or built from scratch, with branching logic that can send follow-up messages, update appointment status, automatically mention a user or User Group, or change the Patient Channel status. [8]
The Messaging API, or MAPI, delivers text messages to patients that are generated from an organization's EMR or a Marketplace vendor. The EMR determines which patients qualify, when messages are sent, which triggers qualify, and what information messages contain. MAPI inserts messages into existing patient conversations on familiar phone numbers, and the documentation states that it includes an option for a Deliverability Webhook, unlike the Send Message API. [5]