The launch-month contact centre: scripts, routing and cover
A hospital launch contact centre faces its hardest month with the least information: no call history, a changing doctor roster and unfamiliar questions. Build a question bank before writing scripts, write honest answers for what the hospital cannot do yet, keep routing short with emergencies first, plan surge cover against the marketing calendar, and review calls, callbacks and conversion every day.
For the first month after a hospital opens, the phone is the hospital. Most people have never walked through the doors. They have seen a hoarding, heard from a neighbour, found a listing on maps, and now they are calling to ask whether a particular doctor sits on Tuesdays, whether their insurance works, and whether the emergency is really open at night. Whatever they hear on that call becomes their view of the hospital.
The hospital launch contact centre is usually planned as an extension of an existing one, or as a small team hired late and trained on a generic script. Both approaches underestimate the launch month. Call volumes are unpredictable, the questions are unfamiliar, the answers keep changing as doctors join and services go live, and there is no history to plan from. It is the hardest month the contact centre will ever have, staffed by people who have the least information.
This piece covers the three things I would get right before the lines go live: the scripts, the routing and the cover. None of it is glamorous. All of it shows up in the first reviews.
What makes a hospital launch contact centre different
A mature contact centre handles known demand. It has call patterns by hour and day, a stable doctor roster, a knowledge base built over years and agents who know which consultant runs late. A launch contact centre has none of that. It is also dealing with an unusual mix of calls.
In my experience the launch month brings a wave of curiosity calls (is it open, where is it, what does it have), a smaller but valuable stream of real appointment requests, a steady trickle of job seekers and vendors who found the only published number, emergency and ambulance calls that must never wait, and insurer or corporate queries that nobody has prepared for. On top of that come the calls you create yourself: pre-launch registrations to follow up, health check bookings from an opening offer, invitations for community events.
Each of these needs a different response, and the agent has seconds to recognise which one they are handling. That is why a launch contact centre needs its own design rather than a copy of the group’s standard setup. The group’s scripts are written for a hospital patients already know. Yours is not that hospital yet.
Build the question bank before the scripts
Most launch scripts are written by someone imagining what callers will ask. A better starting point is to collect what callers actually ask, before the first call. You can do more of this than people expect.
Pull the enquiries from any pre-launch activity: website forms, WhatsApp messages, comments on social posts, calls to the project office. Ask the group’s other contact centres which questions dominate a new unit’s first weeks, if the group has opened before. Sit with the front office team and the insurance desk and list what they expect to be asked. Ask doctors joining the hospital what their existing patients will want to know when they follow them.
Group the questions into a small number of intents, and for each one write the correct answer, who owns it and when it might change. Doctor schedules, empanelled insurers and TPAs, available services, package prices where the hospital publishes them, and directions will change during the launch month. Mark them as live facts with a named owner who updates them daily.
This question bank is the real asset. The scripts are just the spoken version of it. I would keep it in one shared place that every agent, supervisor and front desk colleague reads from, rather than in printed sheets that go stale by the second week.
Scripts that sound like people
A launch script should be short, warm and honest. Callers can tell when they are being read to, and they forgive a new hospital a lot more if the agent sounds like a person who wants to help.
The opening
Keep the greeting brief: the hospital name, the agent’s first name and an offer to help. Skip the long welcome and the promotional line. If the hospital has just opened, a simple acknowledgement that it is new sets the tone and makes the next part easier.
The “not yet” answer
The most important script in the launch month is the one for things the hospital cannot do yet. A specialty not started, a doctor not joined, an insurer not yet empanelled, a procedure planned for later. Agents under pressure either make something up or say a flat no, and both lose the patient. Write a clear, honest answer for each known gap: what is available now, when the gap is expected to close if you know, and an offer to call back when it does. Then actually log the callback and make it.
The handover
Every script should say when to stop scripting. Anything that sounds clinical, urgent or distressed goes to a trained person immediately. Agents should never give clinical advice, and they should know exactly who to transfer to and how. Rehearse this with real examples until it is automatic.
Translate the core scripts into the main languages of the catchment, and let agents switch languages freely. A caller who is answered in their own language is already halfway to booking.
Routing: fewer options, clearer owners
Launch IVRs tend to be overbuilt. Someone lists every department and gives each a number to press, so the caller hears a long menu before reaching anyone. In the launch month, when most callers do not know how the hospital is organised, a long menu mainly produces wrong choices and hang-ups.
I prefer a very short menu: emergency and ambulance first, then appointments and enquiries, then everything else. Emergency calls should bypass the queue entirely and ring at a staffed point that is tested daily. Appointment calls go to the main team. Everything else, including vendors, job seekers and media, goes to a separate queue with its own callback promise so it does not block patients.
Behind the menu, decide who owns each type of call and what happens when they are not available. Unanswered calls should become callback tasks in the CRM, with an owner and a time limit, not a missed call report someone reads the next morning. If you are thinking about adding automation to the front of the line during launch, read when automation should not answer the phone first. A new hospital’s callers usually need a human more, not less.
Treat WhatsApp and web chat as part of the same front door, not a side channel run by the social media team. In a launch month, a large share of first contact arrives as a message rather than a call, often late in the evening. The same question bank should drive both, the same agents or a clearly linked team should answer, and a message that asks for an appointment should become a CRM task exactly as a call would. Publish realistic reply times for messages. A message answered the next morning with a clear, useful reply does less harm than one left unread for two days because nobody knew it was theirs.
Finally, list every published number. Hoardings, flyers, listings, the website, doctor visiting cards, the press release. Make sure each one routes somewhere sensible. Old numbers from the project office have a habit of staying on maps listings for months.
Cover: hours, surge and the backup plan
You cannot forecast launch volume with confidence, so plan cover as a range rather than a single number. Staff for a reasonable base, then decide in advance where the surge capacity will come from: agents borrowed from another unit, trained front office staff who can take calls at peak, a supervisor who picks up the phone, or a partner team briefed on the question bank.
The peaks are predictable even when the totals are not. They follow the opening announcement, any press coverage, newspaper inserts, the first weekend and every campaign flight. Put the marketing calendar and the contact centre roster side by side, and do not let marketing launch anything the phones cannot answer. This is where launch teams most often fail each other.
Decide the hours honestly. If the contact centre will not run through the night, say so on the IVR and in the listings, and make sure emergency calls still reach a person. A promise of round-the-clock help that ends in an unanswered phone at night does lasting damage.
Have a backup plan for the technical failures that always happen in the first weeks: the telephony line dropping, the CRM slowing down, the hospital information system not showing doctor slots. Agents should know how to take a booking on paper and reconcile it later, without telling the caller there is a problem.
When the doctor roster keeps changing
The single biggest source of launch-month frustration is doctor availability. Doctors join in phases, schedules shift as they settle in, some start with limited OPD days, and a few announced names are delayed. Callers ask for specific doctors, often because the doctor has followed them from another hospital or because they saw the name in an advertisement.
Give one person the job of maintaining the live roster and publishing changes to agents at a fixed time every day. Agents should see not just who is available but how to describe a doctor who has not started: when they are expected, who covers the specialty meanwhile, and whether the caller can be put on a notify list.
Be careful with advertising named doctors before their schedules are confirmed. Every ad that names a doctor who is not yet seeing patients generates calls that end in disappointment. The problem of marketing before your doctors are in place is covered in pre-launch demand when you have no doctors to name, and the contact centre is where those decisions get tested.
Measuring the launch month every day
In business as usual, contact centre reports are often weekly. In the launch month, look at them daily, together with the unit head and marketing, in a short stand-up.
The measures that matter are simple: calls offered and answered, how long callers waited, calls abandoned, callbacks due and completed, and the share of appointment calls that became a booked appointment. Add a quick read of the top reasons for calls and the top questions agents could not answer. The logic of enquiry to appointment applies from day one, and a new hospital should know its conversion rate early rather than discovering it in the quarterly review.
Listen to a handful of recorded calls every day. Reports tell you what happened. Recordings tell you why. The most useful launch-month changes I have seen came from a supervisor noticing that callers kept misunderstanding one line of the script.
Record every call in the CRM with a source and an outcome, even the ones that do not book. The launch month is the only time you will see a clean, unprompted picture of what a catchment wants from a new hospital. What a hospital CRM is actually for makes the case for why that record matters long after the opening.
The week before the lines go live
In the final week, I would run the contact centre as if it were already open. Make test calls from outside the hospital, on different networks and at different hours, to every published number. Have people who do not work on the project call with realistic questions, in different languages, and score the answers. Test the emergency route several times a day.
Walk every agent through the question bank and the “not yet” answers, and quiz them. Confirm the roster owner, the daily update time and the stand-up slot. Check that callbacks create tasks with owners. Put the marketing calendar next to the roster one more time and move anything that lands on a thin shift.
Agree when the launch setup ends and business as usual begins, usually when volumes and questions settle and the roster stops changing daily. The broader transition is covered in the first ninety days after opening, and the contact centre items are part of the hospital launch checklist. The contact centre will never be this important again. Staff and prepare it that way.
Questions people ask
A hospital launch contact centre is the phone and messaging team set up to handle enquiries in the weeks before and after a new hospital opens. It answers curiosity calls, books appointments, routes emergencies, handles insurer and corporate questions and follows up pre-launch registrations. It differs from a mature contact centre because it has no call history, a changing doctor roster and an unfamiliar mix of questions to answer.
Because most people will experience the hospital on the phone before they ever visit. A caller who gets a clear, warm and accurate answer is likely to book and to speak well of the hospital. A caller who waits, gets a wrong answer or never gets a callback forms an opinion that is hard to change. The first reviews and word of mouth depend heavily on those calls.
There is no reliable formula without call history. Staff for a reasonable base drawn from pre-launch enquiry levels and the experience of similar openings, then plan surge capacity in advance from other units, trained front office staff or supervisors. Align the roster with the marketing calendar, since peaks follow announcements and campaigns. Review the daily numbers and adjust staffing weekly during the launch month.
A launch setup is mostly about design and preparation rather than large new spending. Much of it uses existing agents, borrowed capacity and a well-run question bank. The cost of getting it wrong is lost appointments and poor early reviews, which are expensive to recover. Treat the extra cover as a temporary launch cost with a clear end point, not a permanent addition to headcount.
Keep it very short. Emergency and ambulance first, then appointments and enquiries, then everything else. Emergency calls should bypass the queue and reach a staffed point that is tested daily. Non-patient calls such as vendors, job seekers and media go to a separate queue with a callback promise. Long department menus mostly confuse first-time callers who do not know how the hospital is organised.
I would be cautious. Launch callers are unfamiliar with the hospital, often anxious and asking questions whose answers are still changing. Automation works best on stable, repetitive questions with known answers, which the launch month rarely has. Simple automation for directions, timings or callback requests can help, but the main line should reach a trained person quickly, especially for anything that sounds urgent or clinical.
Agents need an accurate, current doctor roster, clear descriptions of which services are live, and a firm escalation route for anything clinical or urgent. They must never give clinical advice. The medical director’s office should review scripts that mention services or doctors, approve the wording of the not yet answers for clinical gaps and name who agents transfer to when a caller describes symptoms.
Give one person ownership of the live roster and publish changes at a fixed time daily. Agents should be able to say when a doctor is expected, who covers the specialty meanwhile and offer to add the caller to a notify list. Then make those callbacks. Avoid advertising named doctors before their schedules are confirmed, because each such ad produces calls that end in disappointment.
Telephony with tested routing for every published number, a CRM where every call is logged with source and outcome, callback tasks with owners and time limits, and a live link to doctor schedules in the hospital information system. IT should also support a paper fallback for bookings when systems slow down, and fix known issues quickly during the daily stand-up in the launch month.
HR recruits and onboards agents early enough for proper training, arranges surge support from other units or trained front office staff, and ensures agents in the catchment’s main languages are available. HR can also help set expectations about launch-month intensity and support supervisors who will be handling long days. Late hiring is one of the most common reasons launch contact centres struggle.
Share the full campaign calendar, every published number and every offer before it goes live. Do not launch activity the phones cannot answer. Brief agents on each campaign’s message and what callers will ask. Agree how each campaign is tagged in the CRM so enquiries and bookings can be traced back. After launch, use the call reasons and unanswered questions to improve pages and messaging.
Give them the question bank, scripts, escalation routes, roster update process, language requirements and callback rules, and ask them to attend the daily stand-up during the launch month. Be clear that emergency routing and clinical escalation are non-negotiable. Share the measures you will review daily, and agree how quickly script changes will be reflected on their floor after you send them.
Until call volumes and questions settle and the doctor roster stops changing daily. For most openings that happens within the first few months. Agree the criteria for moving to business as usual in advance, so the launch setup does not end abruptly before things stabilise or linger on after it is needed. Keep the question bank and daily habits that proved useful.
A short daily or weekly view of calls answered, wait times, abandoned calls, callbacks completed and conversion from appointment calls into bookings, plus the top call reasons and unanswered questions. This tells leadership how the catchment is responding and whether the front door is working. It is one of the earliest honest signals of demand a new hospital gets.
