Insurers and TPAs as a growth channel
The first time I pulled the payer split on our web enquiries, I expected insurance to be a footnote. It was not. In two metro units, more than half of the enquiries that turned into admissions had asked one question before anything clinical: “Do you take my insurance, and is it cashless?” We had built the site, the contact centre scripts and the CRM around specialities and doctors. The patient was choosing on the payer.
Insurers and third-party administrators are usually treated as a finance-and-billing matter in a hospital group. Empanelment sits with the corporate relations team, tariffs sit with finance, the TPA desk sits with operations, and nobody in growth owns any of it. That is a mistake, because to the insured patient the payer is not a back-office arrangement. It is the first filter in the funnel, and it is applied before your brand gets a chance to speak.
I am not writing about claims operations or tariff negotiation. Those belong to people who do them well. I am writing about what the growth-and-digital function owns in this channel: whether the insured patient can find you, whether the experience you promise survives the pre-authorisation desk, and what your CRM knows about every patient’s payer before the first call is over.
What the insured patient actually searches for
Read the search queries that land on your site and you will find a pattern that speciality-led content ignores. “Cashless hospital near me” followed by an insurer’s name. “Hospitals in network” with a TPA’s name. The name of a corporate group policy. Sometimes the query is the insurer’s name and a city and nothing else. These people are not browsing. They have a diagnosis or a planned procedure, a policy card in hand, and they need to know which hospitals will let them walk out without paying first.
Most hospital websites answer this badly. There is a page called something like “Insurance and TPA” with a list of logos that was last updated when someone remembered, no indication of which unit is empanelled with which payer, and no path to an enquiry. The patient does the sensible thing and calls the insurer’s helpline instead, and now the insurer’s list is choosing your competitor for you.
The fix is not clever. It is a payer page per unit that is accurate, indexed, and ends in a form or a number. The hard part is the word “accurate”, and that is where the real work is.
The empanelment data nobody owns
Ask for a single list of every payer each of your units is empanelled with, and the room-rent categories, the excluded procedures and the date the agreement was last renewed. In every group I have worked with, this took weeks to assemble and was wrong in places when it arrived. The corporate relations team had one version. The TPA desk at each unit had another, often in a notebook. Finance had a third, organised by tariff rather than by payer name.
This matters to growth because every listing you publish, every contact-centre answer and every chatbot response depends on that list being right. Tell a patient you are cashless with their insurer, have them turn up, and discover at the desk that the empanelment lapsed or that this unit was never on it, and you have manufactured a one-star review and a lost admission in the same hour.
The operator’s move is to make the empanelment register a digital asset with an owner, a review cadence and a change log. Not a spreadsheet emailed around, but a source of truth that the website, the contact centre knowledge base and the CRM all read from. When an agreement is renewed, added or dropped, one person updates one place, and every channel changes with it. This is unglamorous product work. It is also the foundation for everything else in this article, and I would do it before spending a rupee on insured-patient acquisition.
Listings inside the insurer’s own products
The insured patient increasingly finds a hospital inside the insurer’s app or the TPA’s network locator, not on a search engine. Those listings are your storefront in that channel, and most groups have never looked at them.
Look. You will find a unit listed under an old name, a wrong pin code that puts you in a different part of the city, a speciality list that stops at what the hospital did five years ago, and a phone number that rings in a department that no longer exists. None of this is malicious. It was entered once by someone at the insurer from whatever the empanelment form said, and nobody has revisited it since.
Treat this the way you treat map listings and doctor aggregators: an inventory to be audited and corrected unit by unit, payer by payer. Get the contact at each insurer who can edit the network record. Send them the corrected details in the format they need. Check again in ninety days, because these records regress. It does not show up in a campaign report, and it is one of the highest-return pieces of listing hygiene a hospital group can do, because the patient reading that record has already decided to be admitted somewhere.
Pre-authorisation turnaround is a conversion metric
Here is the thing operations knows and growth usually does not measure. An insured patient with a planned procedure very often has two or three hospitals in play. They have visited the doctor, they have an estimate, and they have submitted, or the hospital has submitted, a pre-authorisation request. Whichever hospital comes back first with an approved amount is the one they are admitted to. Not the one with the better brand. The one with the faster desk.
I learnt this when a unit head showed me the number of planned surgeries that were “approved but not admitted” in a month. The patients had gone elsewhere. When we traced a sample, the competitor’s pre-auth had come through a day earlier. In the funnel, this shows up as a leak between consultation and admission that nobody attributes to anything, because the CRM has no field for it.
The growth function cannot run the pre-auth desk. It can do three things. It can put the time from estimate to pre-auth submission and from submission to approval on the same dashboard as enquiry-to-appointment, so that it is seen as a conversion step rather than a billing step. It can make sure the patient hears from the hospital during the wait, because silence for forty-eight hours is what sends them to the other hospital. And it can build the case, with that data, for the unit to staff and tool the desk properly. That case is far easier to win when it is expressed as admissions lost rather than as a service complaint.
The TPA desk is a brand touchpoint
The brand the group spends money to build is tested at the insurance desk more than anywhere else in the hospital. A patient who chose you for your reputation meets a counter with a queue, a form, a request for documents they were not told to bring and a wait for the TPA to respond. At discharge, the same desk tells them the insurer has deducted an amount for consumables and they will have to pay it before they leave. Every promise in the campaign is being renegotiated at that counter.
You do not own the desk. You do own the experience design around it. What documents will be needed, sent to the patient by message the day before admission. The likely deductions, explained at the estimate stage rather than at discharge. A status update when the pre-auth is submitted and when it is approved, so the family is not asking the ward nurse. A named person at the unit the patient can reach, rather than a counter. None of this changes the insurer’s rules. All of it changes whether the patient blames you for them.
The reviews tell you where this is failing. Search your unit’s reviews for the words “insurance”, “discharge” and “TPA”. In most units those three words attract a disproportionate share of the worst ratings, and those ratings are read by cash patients too.
What the CRM should know about every patient’s payer
A hospital CRM that does not carry the payer on every enquiry is missing the single field that most changes what happens next. Payer determines whether the patient can be admitted at this unit, which room categories are viable, what the estimate should look like, how long collection will take and, frankly, whether the unit head wants the admission at all this month.
At minimum, the contact centre should capture, on the first call, whether the patient is cash, insured, corporate or scheme, and if insured, the insurer and the TPA. That takes one question and thirty seconds. It should then be able to answer, from the empanelment register, whether that patient is cashless at the unit they are asking about, and route them to a unit where they are if not. The number of patients lost because the contact centre said “please check with the TPA desk” is not small.
Beyond that, the CRM should let you see the funnel by payer. Enquiry to appointment, appointment to admission, estimate to pre-auth, pre-auth to admission, by insurer and by unit. When you have this, you can see which insurers’ patients drop out at the pre-auth step, which units lose insured patients between consultation and admission, and which campaigns are bringing in payers the unit is not empanelled with. That last one is common and expensive. A campaign for a procedure in a city where the unit is not on the network of the two largest insurers is buying enquiries you will have to turn away.
The mix conversation with the CFO
Everything above brings more insured patients. That is not automatically good, and you should say so before finance does.
Insured admissions realise less than cash at the same tariff, because of negotiated package rates, and they take longer to collect, because the money comes from the TPA on its own timetable. A unit that shifts its mix hard toward insurance can grow occupancy while its realisation per occupied bed falls and its receivable days rise. The monthly pack will show that before you do, and the question will come back to growth: what did you bring us?
Have the answer ready. The case for the insured channel is incremental volume in beds that would otherwise be empty, in specialities where the package rates are acceptable, at units where the pre-auth process is fast enough to actually convert. It is not a case for insurance everywhere. I have sat in unit reviews where the right decision was to stop promoting a speciality to insured patients at one unit because the package rate made every admission a marginal loss, while the same speciality at another unit, under a different agreement, was the most profitable line they had. The empanelment register, joined to the funnel and the realisation data, is what lets growth participate in that decision instead of being told the result.
What I got wrong
I spent a year treating the insurer channel as a listings problem and a website problem, and got the listings and the pages right. Enquiries from insured patients went up. Admissions from them did not go up in proportion, and it took too long to find out why, because I had not put the pre-auth step into the funnel. I was measuring the top and the bottom and assuming the middle.
The other mistake was pushing the empanelment register as a digital project when it needed to be a governance decision first. Nobody would maintain a register they did not own, and nobody owned it until a group-level head agreed it was theirs. The tooling was easy. Getting someone to sign for its accuracy took an executive-committee conversation, and I should have started there.
If you’re starting this next quarter
- Weeks one to three: pull the payer split on enquiries, appointments and admissions for every unit, however rough. Read the search queries and the reviews. Establish, with numbers, that this channel is large enough to matter.
- Weeks three to six: assemble the empanelment register. Get a named owner and a monthly review agreed at group level. Make it the single source the website, contact centre and CRM read from.
- Weeks six to nine: audit your units’ records inside the top insurer and TPA network locators. Correct them. Diarise a re-check.
- Weeks nine to twelve: add payer capture to the contact-centre script and the CRM. Add pre-auth submission and approval timestamps to the funnel dashboard, even if they are entered by hand at first.
- By the end of the quarter: take the funnel by payer and by unit to the CFO and the unit heads, and let the mix conversation happen with growth in the room.
The insured patient has already decided to be admitted. The only question is whether your hospital was findable, fast and honest enough to be the one.
Questions people ask
Because to the insured patient the payer is the first filter in the funnel, applied before your brand gets to speak. In metro units a large share of enquiries that become admissions ask one question first: do you take my insurance, and is it cashless? Empanelment sits with corporate relations, tariffs with finance and the TPA desk with operations, so nobody in growth owns whether the insured patient can find you and convert.
Cashless hospital near me followed by an insurer’s name. Hospitals in network with a TPA’s name. A corporate policy name. Sometimes just the insurer and a city. These people are not browsing — they have a diagnosis or a planned procedure and a policy card, and they need to know which hospitals let them leave without paying first. Most hospital sites answer with a stale logo page, so the patient calls the insurer’s helpline instead.
It is a single source of truth listing every payer each unit is empanelled with, the room-rent categories, excluded procedures and the renewal date of each agreement. In most groups it takes weeks to assemble and is wrong when it arrives, because corporate relations, the TPA desk and finance each hold a different version. It needs a named group-level owner, a monthly review and a change log, and the website, contact centre and CRM should all read from it.
Treat it like map listings and doctor aggregators: an inventory to audit and correct unit by unit, payer by payer. You will find old names, wrong pin codes, specialty lists five years out of date and phone numbers that ring nowhere. Get the contact at each insurer who can edit the network record, send corrected details in their format, and re-check in ninety days because records regress. The patient reading that record has already decided to be admitted somewhere.
Because an insured patient with a planned procedure usually has two or three hospitals in play, and whichever returns an approved amount first gets the admission — not the better brand, the faster desk. A unit head once showed me the planned surgeries that were approved but not admitted; the competitor’s pre-auth had come through a day earlier. Growth cannot run the desk, but it can put pre-auth timestamps on the funnel dashboard and keep the patient informed during the wait.
Whether the patient is cash, insured, corporate or scheme, and if insured, the insurer and the TPA. That is one question and thirty seconds. The contact centre should then answer from the empanelment register whether the patient is cashless at that unit, and route them to a unit where they are if not. Beyond that, the CRM should show the funnel by payer, insurer and unit — enquiry to appointment, estimate to pre-auth, pre-auth to admission.
Because every promise in the campaign is renegotiated at that counter — the queue, the form, the documents nobody mentioned, the deduction announced at discharge. You do not own the desk but you own the experience around it: documents needed sent by message before admission, likely deductions explained at the estimate stage, status updates when pre-auth is submitted and approved, a named person to reach. Search your reviews for insurance, discharge and TPA to see where it fails.
No, and growth should say so before finance does. Insured admissions realise less than cash at the same tariff because of negotiated package rates, and collect slower because the TPA pays on its own timetable. A unit that shifts hard toward insurance can grow occupancy while realisation per bed falls and receivable days rise. The case is incremental volume in beds otherwise empty, in specialties where package rates are acceptable, at units where pre-auth is fast enough to convert.
I spent a year treating it as a listings and website problem, and got those right. Enquiries from insured patients rose; admissions did not rise in proportion, and it took too long to see why because pre-auth was not in the funnel. I was measuring the top and bottom and assuming the middle. The second mistake was pushing the empanelment register as a digital project when it needed a governance owner first. Nobody maintains a register they do not own.
About a quarter to get the foundations in place. Weeks one to three: pull the payer split on enquiries, appointments and admissions, read the search queries and reviews, and establish the channel is large enough to matter. Weeks three to six: assemble the empanelment register with a named owner. Weeks six to nine: audit and correct insurer and TPA locator records. Weeks nine to twelve: add payer capture to the script and pre-auth timestamps to the dashboard.
One empanelment register as the source of truth, with a named owner, a change log and a review cadence, that the website payer pages, the contact-centre knowledge base and the CRM all read from rather than copy. When an agreement is renewed, added or dropped, one person updates one place and every channel changes. The tooling is easy. The hard part is getting a group-level head to sign for the register’s accuracy, which took an executive-committee conversation.
A single hospital can, and the payer mix in its city decides how much it matters. Start with the payer split on enquiries and admissions; if insured patients are a meaningful share, the same moves apply — an accurate payer page, corrected insurer and TPA locator records, payer capture on the first call and pre-auth timestamps on the funnel. In a largely cash and scheme town the channel is smaller, and the register still prevents the manufactured one-star review.
Running a campaign for a procedure in a city where the unit is not on the network of the two largest insurers. It buys enquiries the contact centre has to turn away, which is common and expensive. The CRM funnel by payer exposes this quickly — which campaigns bring in payers the unit is not empanelled with, which insurers’ patients drop at pre-auth, and which units lose insured patients between consultation and admission.
