Operations

Telehealth support load per hundred encounters

Support headcount grows with volume unless something removes the reason for the ticket. Most tickets in a telehealth program exist because a patient didn’t know something the system already knew. This post models the ticket mix per hundred encounters and what takes each category off the queue.

TL;DR

Plan telehealth support staffing from tickets per 100 encounters, by category, and remove categories at the source. In our illustrative model, a mail-order program with no proactive messaging generates 50 tickets per 100 encounters. Messages triggered by encounter, order and refill events, a pre-charge billing notice and clinical triage to the care team cut that to 18. At 5,000 encounters a month, that’s about 1.5 support agents instead of 4.2.

Plan support from tickets per 100 encounters

Plan telehealth support staffing from tickets per 100 encounters, by category, and remove each category at its source. In our model, messages triggered by encounter, order and refill events cut 50 tickets per 100 encounters to 18. At 5,000 encounters a month, that’s 1.5 support agents instead of 4.2.

The ratio scales with the work and tells you what to fix. Hiring against total ticket count only tells you how far behind you are. For running the logistics and clinical queues day to day, see patient support for telehealth programs.

Where 50 tickets per 100 encounters come from

This is an illustrative model, not a benchmark. Assume a cash-pay, mail-order program; email at checkout and at shipping, silence in between; refills renewed when the patient asks; one inbox for everything. Count a month of your own tickets and replace every number.

CategoryWhat patients askTickets per 100 encounters
Status“Has a provider looked at my intake?”15
Pharmacy and shipping“Where’s my package?”10
Refills“When’s my next refill?”8
Billing“Why was I charged?”7
Clinical questionsSide effects, symptoms, “should I keep taking it?”6
Account and otherLogin, address changes, documents4
Total50

The three biggest categories ask about events the system already recorded. Clinical questions are a small share, but only a licensed provider can answer them, so they must route correctly.

What removes each category

Status, 15 to 3: message every encounter event

On Lithos, an encounter moves pending_review → in_review → completed, and each step fires a webhook (encounter.created, encounter.in_review, encounter.escalated, encounter.completed). Map each to a patient message such as “a provider is reviewing your intake now.”

An encounter paused at escalated with patient_information_required is waiting on the patient. Say exactly what’s needed and link to it. Webhooks arrive at least once, in no guaranteed order, so fetch the resource and message its current state; see event-driven telehealth with webhooks.

Shipping, 10 to 5: send tracking before they ask

Orders move pending → processing → placed → completed, each emitting an order.* event. For mail orders, fulfillment carries carrier and tracking once the pharmacy reports them. Send tracking the moment it appears, and message the patient if it’s late. What remains, delays and damaged packages, deserves a person.

Refills, 8 to 2: start from the refill date

On Lithos, care_plan.refill_due fires when a treatment line’s refill_due_at passes, and the renewal is a follow_up encounter. Start the check-in before supply runs out. The AI Care Coordinator add-on can run that outreach and escalate to a licensed provider when something clinical comes up. The refill lapse problem covers timing.

Billing, 7 to 4: notice before you charge

Send a notice before each renewal charge, use a recognizable statement descriptor and offer self-serve pause and cancel. This category is yours end to end, because patients pay you through your own merchant account.

Clinical, 6 to 1: route to the care team

Clinical questions should move, not disappear. A support agent or AI triage step recognizes them and sends them to the care team as an inquiry, a patient-to-care-team thread with inquiry.created, inquiry.message_added and inquiry.resolved events. A licensed provider answers. About 5 per 100 land with the care team; 1 stays in support as misroutes and follow-ups.

Account and other, 4 to 3

Address changes and document requests become self-serve screens in your product.

The result: 50 tickets become 18

CategoryBeforeAfter, support queueAfter, care team
Status153
Pharmacy and shipping105
Refills82
Billing74
Clinical questions615
Account and other43
Total per 100 encounters50185

How many support agents does a telehealth program need?

Assume 9 minutes per ticket (1.5 touches of 6 minutes), 7,560 productive minutes per agent a month (6 hours × 21 days), a 1.4 coverage factor and $5,000 a month per agent. Replace each.

Encounters a monthTickets beforeAgents beforeTickets afterAgents after
1,0005000.81800.3
2,0001,0001.73600.6
5,0002,5004.29001.5
10,0005,0008.31,8003.0

The formula is tickets × 9 ÷ 7,560 × 1.4. At 5,000 encounters, 2,500 tickets need 4.2 agents and 900 need 1.5. Support cost falls from about $4.17 per encounter to $1.50.

Headcount comes in whole people, so prevention shows up as hires you don’t make. A team at 2,000 encounters that has done this work can grow to 5,000 with its two agents. One that hasn’t will more than double.

Two cautions. Clinical questions now land with the care team, so plan that capacity. And fewer tickets only count if satisfaction and refill retention hold.

Send us one month of ticket counts by category and your encounter volume, and we’ll rebuild this model with your numbers on a call and show which events would remove each category. Book a call.

Start with your biggest category

Sort last month’s tickets into these six categories and work down by volume:

  1. Map every encounter webhook to a patient message.
  2. Send tracking when the pharmacy reports it, and a note when it’s late.
  3. Start refill check-ins from care_plan.refill_due.
  4. Add a pre-charge notice and self-serve pause.
  5. Route clinical questions to the care team in one step.
  6. Recount next month.
EVENTPATIENT MESSAGE OR ROUTEPER 100encounter.in_review“A provider is reviewing your intake”Status15 → 3encounter.escalated“We need one thing from you” + linkStatusorder fulfillmentTracking as soon as the pharmacy reports itShipping10 → 5care_plan.refill_dueShort check-in before supply runs outRefills8 → 2your billing systemNotice before each renewal chargeBilling7 → 4inquiry.createdClinical question goes to the care teamClinical6 → 1fetch the resource on receipt · at-least-once delivery, no ordering guarantee
Each category shrinks when an event the system already records becomes a message the patient receives before asking. Billing is the one you trigger from your own billing system; clinical questions move to the care team instead of disappearing.

Tag each ticket when it’s closed, not opened. “Quick question about my order” often turns out to be a refill question or a side effect. To push the same events into your help desk, Slack and CRM, see wiring clinical events into Slack, your CRM and your support desk.

Lithos sends the events this model runs on: signed encounter, order, care plan, appointment and inquiry webhooks, so your product can tell patients what’s happening before they ask, while licensed providers handle care-team questions. Build your own care experience on licensed infrastructure. Bring your current volume and we’ll price it against the per-visit bands and plan which events to wire first. See how it fits a live program on adding services, or book a call.

Frequently asked questions

How many support tickets does a telehealth program generate?

Build your own baseline: last month’s tickets divided by last month’s encounters. Our illustrative model starts at 50 tickets per 100 encounters for a mail-order program with no proactive messaging, and falls to 18 when status, shipping, billing and refill messages go out automatically.

What is the most common telehealth support ticket?

Usually some version of “where is it”: has a provider reviewed my intake, was the prescription sent, where is the package. The system already knows each answer, so messages triggered by status events remove these first.

Should telehealth support agents answer clinical questions?

No. Questions about side effects, symptoms or medication changes belong with the licensed care team; a support agent’s job is to recognize and route them fast. AI can help triage, but a licensed provider answers and makes any clinical decision.

How do I calculate support staffing for a telehealth program?

Multiply monthly tickets by handle time, divide by one agent’s productive minutes a month, then multiply by a coverage factor for weekends, time off and response targets. With 9 minutes per ticket, 7,560 productive minutes and a 1.4 factor, that’s about one agent per 600 monthly tickets.

Does reducing support tickets hurt patient experience?

Not when tickets fall because patients already have the answer. Track contact rate alongside satisfaction and refill retention to confirm the drop comes from prevention, not from support being harder to reach.

Get started

Put a medical practice behind your product

Book a call and we'll scope your program together, or get free sandbox access and start building.

Book a call Get sandbox access

Free to startNo setup or platform fees