Telehealth Patient Support at Scale: Planning Ticket Volume

This is operator education, not legal advice, and not medical or compliance advice either. Talk to qualified counsel about your own operation.

How many support tickets will your next hundred patients create?

If you cannot answer that within a rough range, you are not ready to double your ad spend. You can double the leads in a week. You cannot double a support team in a week, and patients do not wait politely while you catch up.

How do you model support load per 100 patients?

You model it with three inputs, and you have to get all three from your own data.

The three inputs

1. Contacts per active patient per month. Every message, call, chat or portal ticket, counted.
2. Handle time per contact. The real minutes, including the lookup, the reply and the notes.
3. Mix by category. Order status, refill requests, billing, login problems, pre-purchase questions and clinical questions.

An illustration, with made-up numbers

These numbers are invented to show the arithmetic. Replace every one with your own. Say 100 active patients create 150 contacts a month, and the average takes 8 minutes. That is 1,200 minutes, or 20 hours, a month for each hundred patients. Now say you add 100 new patients a month and keep 80% of your base each month. By month three you have about 244 active patients, which is roughly 49 hours a month before you count the extra onboarding questions.

The point is the shape, not the figure. Support load follows the base, not the signup. Last month's patients are still writing to you this month.

Where the extra load hides

• The first two weeks of a new cohort: login problems, delivery timing, "what happens next?"
• Refill and renewal windows, which arrive in waves.
• Billing questions after a card fails (see Failed Payment Recovery) or a renewal charges.
• Anything where your marketing promised more than your onboarding explained.

That last one is a growth problem as much as a support problem. When ads, pages and onboarding disagree, patients write in to resolve it.

What should AI handle, and what should it never touch?

Draw the line before you buy a tool.

Good fits

Order status, appointment times, how to log in, where to find a form, policy answers, and the first sorting step: "Is this a billing question, a delivery question or a clinical one?" In my own telehealth builds, AI works as an operational layer for leads, intake and booking, and not for medical consults, prescriptions or medical advice.

Never fits

Symptoms, side effects, dosing, whether a medication is right for someone, and anything that reads as advice. These go to licensed staff, with clear handoff rules and response targets.

Two compliance flags worth knowing

First, if a support vendor creates, receives, maintains or transmits protected health information for you, it may fall under HIPAA's definition of a business associate.⁴ Ask your counsel before connecting any tool to patient records.

Second, support replies are marketing-adjacent. In March 2026 the FDA sent 30 warning letters to telehealth companies over how they marketed compounded GLP-1 products, and the examples included claims that implied FDA approval.³ A chatbot or a rushed agent can say things your website was careful not to. Script and review the answers.

Does automating support actually work?

It can, and the same company shows the limits.

In February 2024 Klarna said its AI assistant had handled 2.3 million conversations, two-thirds of its customer service chats, with resolution time down from 11 minutes to under 2 and repeat inquiries down 25%.¹

In May 2025 its CEO told Bloomberg that the AI-heavy approach produced "lower quality" and said the company was hiring human support workers again so customers could always reach a person.² I read that as a design lesson. Automation is a great first line. It is a poor last line. Keep a visible path to a human.

How many people do you actually need?

Here is a data point from my own published work. In my January 2026 telehealth case study, a campaign produced about 48 new leads a day for a single sales rep. I put a well-supported rep's practical limit at around 30 fresh leads a day, which meant that rep ran at roughly 160% capacity. That was sales intake, not support, but the principle carries: capacity is a number, and you can calculate it before the spend, not after. You can read the full story in Part 2.

For support, do the same (provider capacity works the same way, see Provider Capacity): divide expected monthly hours by the productive hours one person can really give, then add a buffer for sick days, spikes and training. Hiring takes weeks, so the lead time matters more than the ratio.

Harvard Business Review's service-profit chain work makes a related point: top service organizations focus on the people who serve customers, through recruiting, training and the tools they get.⁵ The people answering your patients are part of the product.

What is a capacity trigger, and how do you set one?

It is a rule that ties spend to service levels, so the budget cannot outrun the team.

Fix the top ticket categories upstream. A clearer onboarding email removes more tickets than a faster agent ever will.

If you are running a telehealth practice and want to check how your intake, follow-up and support hold up before you scale, start with my telehealth page.

Keep building.Ekai