Personalized for selling Artera's patient communication platform into health systems, specialty groups, FQHCs, and federal agencies. AI prompts, persona playbooks, sequence frameworks, daily workflow, and FAQ.
Six sections covering everything from "find me the right CDO at a 300-bed health system" to "my mailbox is bouncing, what now." Everything here is tuned for Artera's motion: healthcare buyers, patient-experience pain, and AI-powered virtual agents as the value prop.
Numbers you'll cite in outreach. Sourced from artera.io and recent funding announcements.
Artera Harmony fixes patient communication by combining human and AI agent intelligence. Self-scheduling, intake, forms, billing, and follow-up all flow through one platform connected to the EHR. The result: less staff load, fewer no-shows, more patient access.
Three account flavors. Each one has slightly different decision-makers and slightly different pain. The personas tab breaks it down.
Each prompt is ready to copy into Apollo's AI Assistant or AI Research. Replace the variables in blue with your specifics. Filter by type below.
Each persona has a quick-reference card: who they are, what keeps them up, what Artera does for them, and a tested opening line. Lead with the pain that maps to their role, not Artera's feature list.
The end-to-end patient journey: scheduling, intake, communication, follow-up, satisfaction scores. Reports to COO or directly to CEO at larger systems.
Direct line to their KPIs: no-show reduction, NPS lift, call center deflection, staff load reduction. The pitch is operational, not technical.
Specific to their announced initiative or recent score. Generic "improve patient experience" gets ignored. "Saw your team rolling out X" gets read.
Digital strategy across the system: patient-facing tech, AI initiatives, vendor consolidation, modernization roadmap. Often a board-level conversation. Reports to CEO.
The consolidation play. One platform replaces a stack of point solutions. AI agents are real and deployed, not roadmap. Proof at scale (1,000+ orgs) reduces board risk.
Reference their digital agenda or a recent announcement. They get pitched constantly; specifics beat features.
System-wide operations and the P&L. Patient flow, staffing efficiency, revenue cycle, vendor budgets. Has final sign-off on contracts above a threshold.
The cost / capacity equation. AI agents pick up the work staff can't get to. Quantifiable: fewer FTEs at the front desk, more revenue from filled slots, faster collections.
Lead with the financial outcome. Operational specifics. Avoid technology language.
Everything at the group: operations, hiring, vendor selection, finance, patient relations. Often plays both clinical and operational roles. Decision speed is faster than health systems; budget is smaller and more personal.
Real reduction in front-desk load. Tangible patient experience improvement. Quick to deploy. Concrete ROI inside a quarter.
Plain language. Skip the platform vocabulary. Reference a peer group they'd recognize.
The technology stack and how it holds together. EHR roadmap, integrations, security, HIPAA compliance, vendor management. Reports to CEO or COO. Their veto kills deals; their endorsement accelerates them.
Certified EHR integrations (Epic, Cerner, athenahealth, others). HITRUST and SOC 2. SSO support. One platform replacing a sprawl of comm tools is an IT win.
Lead with integration and security. Avoid "AI" as the first word; CIOs hear it 50 times a day.
Healthcare buyers respond slower than B2B software. Plan a 14-day cadence with mixed channels. Subject lines and openers below have all been pressure-tested against the personas in the previous tab.
Healthcare titles flip past anything that sounds like marketing. These five patterns get opens.
Not prescriptive. A pattern that works for most SDRs on this team. Adjust the times to your own rhythm; keep the structure.
Best dial window for healthcare execs is between rounds and the start of the clinical day.
Always leave a voicemail. Always log the dial. Always move the contact to the next sequence step or close the loop.
Not a joke. SDRs who skip lunch tank their afternoon dial energy. Step away from the screen. The pipeline doesn't move while you're chained to the desk.
Numbers you should be hitting once the mailboxes are warmed. Adjust down during the first 4-6 weeks of warmup.
Sorted by category. Click a question to expand the answer.
Three things in order:
1. Email verification. Apollo verifies emails at enrollment, but lists pulled from less trusted sources can carry stale addresses. Re-verify the whole sequence and pause any address that comes back catch-all or invalid.
2. Mailbox warmup status. If you're early in warmup and pushed volume past the daily ramp, bounce rate spikes. Drop your daily send by 50% for 5 days, watch bounce rate recover, then ramp again.
3. Recipient quality. Generic role addresses (info@, contact@) bounce or filter at higher rates. Stick to named individuals.
If all three check out and bounces stay high, pause the mailbox and ping the GTM engineer. There's likely a domain reputation issue that needs a fresh look.
No. The primary domain is reserved for customer communications: support, contracts, billing, renewals. All prospecting runs on secondary domains.
If your prospecting domain gets flagged or burned, the cost is contained to that domain. Customers still get through. If you mix the two, one bad sequence can damage deliverability for the whole company.
You'll have your-name@get-artera-domain.com mailboxes for outbound. Apollo routes replies back to a unified inbox view.
The sequence rule set is firing. The contact's account is in an active opportunity stage (or some other blocked stage). This is intentional and prevents the team from prospecting accounts already in a deal.
Options: (1) move to a different contact at a different account, (2) check whether the deal is actually still live and have the AE close it if not, (3) if you believe the block is in error, ping the GTM engineer.
This pairs with the backfill workflow that runs daily and removes contacts mid-sequence when their account opens an opp. See the Workflow Guide artifact for the full picture.
AI Assistant: for building a list, drafting copy, taking an action. "Find me 100 CDOs at health systems in TX." "Draft a cold email to this contact." It's the action-taker.
AI Research: for understanding an account or contact before you act. "Tell me about this organization's patient access initiatives." "What has this CDO said publicly in the last 12 months?" It's the briefing tool.
Pattern: Research the account, then use Assistant to draft against that research. Don't draft cold without research; the copy reads generic.
Trust it as a starting point. Verify before you cite it in outreach.
Always check: did the AI include source citations? If yes, click through and confirm the claim. If no, treat the claim as a hypothesis, not a fact.
Especially careful with: regulatory claims, financial figures, recent funding amounts, leadership names that might have changed, EHR vendor relationships. Healthcare info gets stale fast.
No. Never. Apollo and external LLMs are not covered entities under HIPAA. Putting any PHI (patient names, conditions, identifiers, dates of service) into a prompt is a HIPAA violation.
Stick to organization-level and contact-level information: hospitals, executives, public initiatives, public stats. Never patients.
This includes "anecdotal" examples ("a patient at Acme Health had X happen"). Even anonymized, it's not worth the risk.
Short answer: "Artera is HITRUST certified and SOC 2 Type II. We sign BAAs with every customer. The platform was built for healthcare from day one. I can connect you with our security team for the full deck."
Don't try to answer technical compliance questions yourself. Get the security team involved early. CIOs and compliance officers will ask detailed questions; the AE handles them with security backup.
Common objection. The honest counter: EHR-native tools handle basic appointment reminders well. They don't handle AI-driven virtual agents, intake forms, billing comms, or cross-EHR workflows. They also don't connect to the patient when they're not in your system already.
Ask: "Are you happy with how the EHR handles intake and forms specifically? And new patient acquisition before they're in your system?" That's where the gap usually is.
Don't fight the EHR. Position alongside it.
Apollo's industry filter alone is too coarse. Use the AI Assistant prompts in the AI Prompts tab. The prompts include specific qualifiers: bed count for hospitals, provider count for specialty groups, clinic-site count for FQHCs.
You can also layer in: SIC/NAICS codes (621111 for offices of physicians, 622110 for general hospitals, 621498 for ambulatory health centers), funding signals (federal grants for FQHCs), and announced acquisitions for health systems.
The handoff criteria for this team:
When you book the meeting, attach a one-paragraph handoff note: who the contact is, what triggered the meeting, what pain they mentioned, what they're using today. The AE will love you for it.
Three knobs in order:
1. Subject line. The pattern matters most. If you're using generic "improve patient experience" subjects, swap to the patterns in the Sequences tab. Question-based and peer-reference subjects open 2-3x higher.
2. Sender name. First name only. Your full name + title in the from field reads corporate.
3. Preview text. Apollo shows the first line as preview. Make it specific and earn the open. "Hi [name], saw your team announce X" beats "Hope this finds you well."
Use the "send me information" handler prompt in the AI Prompts tab. Converts the passive request into a 15-min qualifying call without being pushy.
If you just send the deck, 80% chance you never hear back. The deck answers no specific question and starts no specific conversation. Worse, it gives them a reason to feel they've already seen Artera and move on.
Ping Tyler for sequence and territory questions. Ping your GTM engineer for Apollo deliverability, workflow, or integration issues. Use the #sdr-help channel for anything that other reps would benefit from seeing.