Running One Call Script Across Several Medspa Locations
A medspa group with several locations usually has one brand, one set of treatments and one clinical team. What differs is the price list, the calendar and the staff at each site. The phone system should reflect that: one script, with the local details filled in. This post explains how to set it up.
What stays the same across every site
The approved answers to common questions, such as what a consult includes.
The escalation rules: which calls go to a clinician, and how quickly.
The tone and the booking process.
The data protection set-up, including the Business Associate Agreement and call logging.
Keeping these the same means a patient gets the same answer whichever location they call.
What changes by location
Prices, where a location runs its own offers.
Availability: open consult slots and the clinicians working each day.
Address, parking and directions.
Local services, where a site does not offer every treatment.
Each location's details come from its own team. The agent reads them from the approved location details, so a price change at one site does not require a change to the whole script.
Set it up once, then review monthly
We set up the shared script and the location details during the sprint. Then each month a human reviewer checks results, compares them against the agreed numbers, and updates the agent. A site that is booking fewer consults is looked at first.
Who owns what
Name one person at group level who approves the shared answers and price changes. Each location manager confirms their local details, such as availability and offers. This avoids one site quoting an old price while another has already changed it.
Reporting across sites
Weekly reports cover calls, consults booked and escalations, so you can compare results across the group. We confirm during the sprint how the numbers are split by location for your group.
Read how the agent works: https://www.dezyit.com/24-7-ai-voice-agent
Plan the rollout for your group: https://cal.com/explore-diva/diva360-demo
.png){kind=small}