Product knowledge alone doesn’t prepare reps for the moments that make or break an HCP conversation—reading hesitation, handling objections, and responding confidently under pressure.
Rapport’s lifelike AI-powered HCP avatars react in real time with facial expressions and nonverbal cues, creating realistic practice that goes far beyond a chatbot with a headshot.
See why life sciences teams train with Rapport.
In this webinar, you will see Rapport's demo of:
Scenario creation - new drug, "analytical' HP profile
Watch a customized HCP scenario built from scratch, tailored to a meeting your reps face
Live roleplay with Dr. Reyes, Endocrinologist
See live conversation with an AI avatar that reacts in real time. Not just a chatbot.
The cohort dashboard to analyze team performance
See instant, team-level readiness data pulled from learner data
AI roleplay for HCP conversations is simulation-based practice in which a rep holds a live, unscripted spoken conversation with an AI healthcare provider persona that objects, hesitates, and reacts in real time. Because the persona is not following a branching script, the rep has to read the reaction and adapt. Each attempt is scored against the organization's own rubric, producing skill-level coaching feedback for the rep and competency data for the training team.
The reason this format matters more every year is that the practice reps used to get on low-stakes calls no longer exists. Veeva's Pulse Field Trends data put US healthcare provider access at 45%, down from 60% over roughly eighteen months, with half of still-accessible HCPs limiting engagement to three or fewer companies. In oncology it is tighter still: ZS reports that only 32% of oncologists are fully accessible, and oncology reps average 2.6 calls a day.
When a rep gets a handful of real conversations a week, none of them can be the one where they learn. The practice has to happen somewhere else.
Scenario authoring in Rapport has three parts, and a trainer completes all three without opening a vendor ticket.
A plain-language description of the situation plus the physical setting. Real HCP meetings happen in hallways and cramped offices, not conference rooms, so the environment is part of the simulation rather than decoration.
The knowledge base the avatar will reason against. For this demo it was a fictional oral dual agonist:
| Attribute | Zolta (fictional) |
|---|---|
| Class | Oral GLP-1 and GIP dual agonist |
| Efficacy in trial | 1.8% A1C reduction, non-inferior to Injexta at 1.9% |
| Dosing | 3 mg for month one, escalating to 7 mg then 14 mg over 58 days |
| Administration | Once daily oral, 30-minute fast after dosing, minimal water |
| Tolerability | 5% discontinued for gastrointestinal reasons in trial |
| Comparator | Oralin GT, an oral GLP-1 mono agonist, single pathway |
Name, specialty, and a personality profile set by percentage. This run used Dr. Reyes, an endocrinologist, dialed to be analytical, detail-hungry, time-pressured, and openly skeptical. That combination is what makes the scenario hard: the persona keeps asking for the specific thing the rep did not prepare.
The rep opened well enough, acknowledging the physician's limited time, stating a purpose, and asking a discovery question about metformin plateau patients avoiding injectables. Then Dr. Reyes started asking follow-up questions, and the conversation turned into a series of small failures that each looked survivable in isolation.
| What Dr. Reyes pushed on | What the rep gave | Why it cost the rep |
|---|---|---|
| Head-to-head efficacy | 1.8% versus 1.9% A1C reduction, stated flatly | Correct number, no framing. Dr. Reyes supplied the interpretation instead: "that is a close margin, but Injexta is a high bar." |
| Patient profile in the trial | "Adults who had issues with metformin" | Too broad to act on. The physician flagged it as vague and asked again, which burns the meeting's most valuable asset: time. |
| Administration requirements | The 30-minute fast, but only after being asked twice | The physician surfaced the objection for the rep. Information a rep is dragged into giving reads as something they were hoping to avoid. |
| GI tolerability | "Only 5% were not able to continue" | Answered discontinuation, not the actual question. Dr. Reyes wanted incidence of mild to moderate nausea during dose escalation, which is a different number. |
| The close | "I'll leave that with your team, how about we set up some time" | No summary, no agreed next step, no commitment. The physician's parting line was "I'll look over the data," which is a polite nothing. |
One moment is worth isolating. When the rep finally confirmed the fasting requirement, the physician's reaction was blunt: so they offer the GLP-1s in a pill now, but you have to fast with them. The rep had just converted the product's biggest convenience advantage into a compliance burden, because the physician was allowed to frame it first.
Sit on the other side of this conversation
Run a live HCP scenario against a busy physician avatar, take about three minutes, and get your own performance insights before you ask your field team to.
Try a medical sales scenario →When the run ended, the transcript went through the scoring engine attached to that scenario. The output is not a grade. It is an overall score against the company's expectation, a per-criterion breakdown, and, for a new rep, a written instruction for what to do differently on the next attempt.
This demo rubric used five criteria. Production rubrics at life sciences companies commonly run 10 to 15, because the criteria are whatever that organization certifies on: compliance behaviors, required discovery questions, approved messaging sequence, and so on.
| Criterion | What the rubric checks | What the report said |
|---|---|---|
| Product mastery | Depth and accuracy of clinical detail: indications, contraindications, adverse reactions | Partial credit. Facts were correct but stayed top level. Therapeutic specifics were left out entirely for a physician who kept asking for them. |
| Alignment | Whether the rep uncovered what this physician cares about and tied messaging to it | Partial credit. Acknowledged the time constraint and asked about patient population, then never connected Zolta's benefits to the goals the physician stated. |
| Objection handling | Use of the trained framework: acknowledge the concern, provide evidence, reinforce confidence | Scored low. The framework was never used. Objections were answered as trivia questions instead of worked through. |
| Summarization | A closing recap of the key benefits discussed, as company standards require | Scored low. No summary attempted. The rep offered to leave materials and book time instead. |
The distinction between a grade and this is the whole argument for rubric-based scoring. A sentiment score tells a rep the call felt bad. This tells the rep exactly which sequence was skipped: acknowledge, evidence, reinforce, when the GI question came up, which is a specific, repeatable, coachable thing.
The same five moments, rewritten the way the rubric would reward:
| What the rep said | What scores well |
|---|---|
| "1.8 versus 1.9% reduction." | "Non-inferior to Injexta at 1.8 versus 1.9, and it gets there orally. For a patient refusing injectables, that is the trade you are actually making." |
| "Adults who had issues with metformin." | Names the inclusion criteria, baseline A1C range, and duration, then asks how closely that maps to the physician's panel. |
| Discloses the fast only when asked twice. | Leads with it: "It is once daily with a 30-minute fast, so it fits patients with a stable morning routine. Let me tell you who that has worked well for." |
| "Only 5% were not able to continue." | Acknowledge: "Escalation tolerability is the right question." Evidence: discontinuation plus the incidence data actually requested. Reinforce: how the titration schedule is designed around it. |
| "I'll leave that with your team." | Recaps the three things that mattered to this physician, then asks for one specific next step tied to a named patient type. |
Individual reports are useful to the rep. The dashboard is what a training leader takes to a commercial meeting. Every learner's per-criterion scores roll up, so a scenario view answers three questions at a glance: how is the team doing, how much are they actually practicing, and which skill would produce the biggest lift if we fixed it.
A 50% team average looks like a capability problem. Read alongside 2.5 attempts per person, it is closer to a volume problem. The same dashboard showed that when one learner kept going, their score doubled between first and best attempt. Drill-down by learner is what separates "this team is weak" from "this team has barely started."
Where the cohort is losing points
Relative strength across the demo rubric, first-pitch scenario
That is the operational payoff. A trainer looking at this does not schedule more clinical training. They assign two more runs of the same scenario and tell the district managers to coach the close.
Five runs of a seven-minute scenario is roughly 35 minutes. That is the unit of work being proposed here, and there is a large evidence base explaining why it outperforms rereading the detail aid for the same 35 minutes.
The classic demonstration is Roediger and Karpicke's test-enhanced learning study, published in Psychological Science in 2006. Groups either restudied material repeatedly or practiced retrieving it. On an immediate test, the restudy group won. A week later, the result flipped hard.
Cramming wins the quiz. Practice wins the week.
Percent of material recalled, repeated study versus repeated retrieval practice
Two more findings support the same design:
Gartner has since put a number on the commercial side of the same shift, predicting that AI-driven sales enablement will deliver 40% faster sales stage velocity than traditional enablement methods by 2029.
No. Scoring is based on the content and structure of what the rep says. Tone is not scored, but it is not inert either: the learner's delivery influences the avatar's facial expression and reaction in real time, so a rushed or combative delivery visibly changes how the physician persona responds mid-conversation.
Typically two to five seconds while the avatar processes what the rep said. Enough to feel like a person thinking, not enough to break the conversation.
Both, and the second use case tends to surprise people. Examples:
Not if you do not want them to. Scenarios embed directly into an existing LMS, so reps reach assigned roleplays through the system they already use, with existing single sign-on. Learners can also be invited into Rapport directly.
Less than most teams expect, because the inputs already exist. A company hands over the product information, training materials, and the objections its reps actually hear. Rapport builds the initial knowledge base and scenarios. The training team edits and builds from there.
Three commitments worth putting in front of an IT reviewer early:
Simulation-based practice in which a rep holds a live, unscripted spoken conversation with an AI healthcare provider persona that objects, hesitates, and reacts in real time. The persona is not following a branching script, so the rep has to read the reaction and adapt. Each attempt is scored against your rubric, producing coaching feedback for the rep and competency data for the training team.
The transcript runs through a scoring engine built on your own rubric. Each criterion gets a score plus a written explanation of what the rep did and what to change next time. Demo rubrics typically use five criteria. Production rubrics commonly run 10 to 15.
Scoring is based on what the rep says, not vocal tone. Tone still influences the avatar's facial expression and reaction during the conversation.
About seven minutes per run, so five scored attempts fit in roughly 35 minutes. In-conversation response latency is typically two to five seconds.
Both. New hires build baseline skills before their first real call. Experienced reps use it to prepare for specific upcoming conversations, rehearse a newly approved indication, or enter a new market.
Yes. Scenarios embed into an existing learning management system with existing single sign-on, so reps do not learn a second platform. Direct invitations into Rapport are also available.
Audio is processed to produce the performance report and is not stored afterward. Your product and scientific information sits in a secure knowledge base, and customer data is not shared with third-party AI model providers for training.
Most inputs already exist: product information, approved training materials, and the objections reps hear in the field. Rapport builds the initial knowledge base and scenarios, then your team edits and creates new ones directly.
If you are earlier in the evaluation, our guide to AI roleplay platforms for pharmaceutical and life sciences sales teams covers the buyer-side criteria worth pressure-testing, and the AI role play training pillar covers the fundamentals of the format. Teams selling into hospitals rather than clinics should start with medical device sales training, where the committee dynamics change the scenario design.
Your reps get minutes with a physician. Make sure they have already had the conversation.
Run a live medical sales scenario, get the scored report, and see exactly where a rubric would dock your team before the real call happens.
Try a medical sales scenario → Explore Rapport