Mansfield, TX
AI Patient Intake Voice Routing in Mansfield TX
Voice is a difficult channel and most intake designs are written as though it were an easy one. They are written the way a form is written, question after question, and then they meet a caller who is driving on Highway 287 with the window down and two children in the back.
Book a Demo
The gap between how a script reads on paper and how it performs on a phone call is where nearly every intake automation disappoints. Not because the technology failed, but because the script was written for a reader rather than for a listener.
This page is about that gap. Cleod9 provides the AI Voice Concierge as part of its cloud platform for Dallas-Fort Worth businesses. It answers, asks the questions the practice defined, books where the practice's rules allow, captures what was said, and transfers to a person. It sorts and routes; clinical staff decide.
Listeners hold about one question at a time
A reader can scan a question, look away, think, and come back to it. A listener cannot. Whatever was said is gone, and if it contained two requests, one of them is gone entirely.
So every question on a voice path asks for exactly one thing. Not name and date of birth. Not the reason for the call and how soon they need to be seen. One thing, then a pause, then the next thing.
This makes scripts longer to read and shorter to complete, which is the opposite of what people expect. A six-question path with single-item questions finishes faster than a four-question path where two questions have to be repeated.
The same principle governs how choices are offered. Three options is the practical ceiling for anything a caller has to hold in mind, and the option they are most likely to want goes first, because a caller who hears their answer early stops listening to the rest and that is a good outcome rather than a problem.
The four things that are genuinely hard to capture by voice
Names, numbers, spellings and dates. Almost every intake failure traces to one of these, and each has a specific fix.
Phone numbers need a read-back. Every time, without exception. A wrong callback number turns every subsequent step into guesswork, and the four seconds a read-back costs is the highest-return four seconds in the entire script.
Names should be captured and then confirmed rather than spelled out letter by letter, which is slow and which people resent. Where the exact spelling matters, sending a text with what was captured and asking the person to correct it works better than trying to resolve it on the call.
Dates are ambiguous in speech more often than anyone expects. The second of March and March the second are the same date; the third of the month and Thursday are frequently confused when both are said quickly. Confirm dates by repeating them in full, including the day of the week for appointments.
Insurance carrier names are worth treating as a fifth hard case. Captured by ear they are wrong often enough to matter, and the correction happens at the front desk on arrival, which is the most expensive place for it to happen.
Writing for the ear
Read every line of the script out loud before it goes live. This single practice catches more problems than any amount of review on screen, and it takes about ten minutes.
Sentences that are fine to read are frequently unsayable. Anything with a subordinate clause in the middle loses the listener. Anything over about fifteen words needs to become two sentences. Anything with a word the practice uses internally but patients do not needs replacing.
Contractions matter more than they seem to. A script that says do not and cannot sounds stilted in a way that makes people less forthcoming, and a caller who is put slightly on guard gives shorter answers.
Numbers should be written in the script the way they should be spoken. Two thirty rather than 2:30, since the second form is read several different ways.
And every question should be answerable in under ten words. If it cannot be, it is really two questions, or it is a question that belongs on the forms rather than on the call.
The caller who is not sitting still
A meaningful share of Mansfield intake calls come from a car, a parking lot, a break room, or a hallway. Design for that rather than for someone at a desk with a pen.
That means never asking a caller to look something up. Policy numbers, previous appointment dates, medication names and doses all require the caller to have something in front of them, and asking for them on a call sets up a failure that gets recorded as a bad answer rather than as a bad question.
It also means the path has to survive an interruption. A caller who says hold on, or who goes quiet for ten seconds, should not be treated as having hung up or as having answered. Silence needs its own handling, and the handling is patience followed by a single repeat, not escalation.
Background noise is the other reality. Where the audio is genuinely unusable, the right move is a transfer to a person or a text follow-up, not a third attempt at the same question. Three failed attempts at one question is the point at which a caller decides the whole thing is broken.
When voice is the wrong channel
Some intake information should not be collected by voice at all, and recognizing that early makes the voice path better rather than weaker.
Anything long, anything requiring a lookup, anything the patient will want to correct, and anything sensitive enough that people do not want to say it aloud in a waiting room or a shared office. Policy numbers, medication lists, history, and detailed descriptions all belong on forms.
Business texting is available on the Cleod9 platform, and the handoff from a call to a text is where a lot of intake friction disappears. Confirm the appointment on the call, then send the forms link within minutes while the call is still recent. Completion rates for a link sent immediately are not comparable to one sent the following morning.
Texting has its own rules. Consent governs, and a request to stop must be honored promptly, so build the consent step into the call rather than assuming it. Treat texting as a separate workflow with its own requirements rather than as an extension of the phone.
The clinical boundary
A voice path in a medical setting has one absolute rule and it should be configured as a prohibition rather than assumed.
No assessment of symptoms, no advice about medications, no view on whether something can wait, and no attempt to sort by severity. The greeting opens by telling anyone facing an emergency to hang up and dial 911, before any other question, on every path the practice configures.
Where urgency has to be established for scheduling, the question is how soon the patient feels they need to be seen. It asks the patient to report their own sense of things rather than asking a call path to interpret anything, and it produces something the schedule can act on.
Anything that sounds clinical is a transfer trigger rather than something to answer carefully. Have a clinician review the finished script line by line before it goes live. This page is operational guidance and not medical advice.
Deciding what the call may collect
Write two lists before configuring anything: what the call may collect, and what it may not. The second list is the one that gets skipped and it is the one that matters.
Then settle the handling questions with Cleod9. Where captured call content, recordings and transcripts are stored. What the default retention period is and whether the practice can set its own. Whether a specific record can be deleted on request. Who can listen, which is governed by the access control list and should be configured deliberately rather than left at whatever the default is.
Call recording runs automatically on the platform, so these are not hypothetical questions. A practice subject to health information rules should have its own compliance advisor review both the collection list and the vendor's answers before go-live.
Getting to a person
Every voice path needs an exit that works, and it needs to work without the caller having to find it.
A caller who asks for a person gets one. A caller who sounds distressed gets one. A caller who has failed the same question twice gets one. A caller with a question the script has no branch for gets one. None of these should require a particular phrase.
Decide where those transfers land, and make sure it is not the same busy desk that could not take the original call. Then decide what happens when that destination is also unavailable, which is the fallback most practices never define. Test both paths monthly by actually calling them, because a destination that rings out looks perfectly healthy on an administration screen.
What to measure, and what to listen to
- Completion rate per question, which shows exactly where callers stall. One question is usually responsible for most of the drop.
- Repeat rate per question, meaning how often the path had to ask again. This is a wording problem every time.
- Transfers to a person, broken down by whether the caller asked or the script decided.
- Average call length, which should fall as the script improves rather than rise.
- Abandoned calls by hour, meaning calls that ended before reaching anyone at all.
Numbers point at the problem; recordings explain it. x-bees is included with Cleod9 and its AI transcription and summaries work on voice calls as well as chat, which makes reading a week of calls a realistic Tuesday afternoon rather than a project. Read the first two weeks in full. The fixes are usually single words.
Common questions
How long should an intake call take?
Under three minutes for a new patient, under one for an established patient rescheduling. If either runs long, the script is asking for something that belongs on the forms.
Can we change wording after launch?
Yes, in a browser, by practice staff, in minutes. Plan on rewriting several questions after the first week, since that is normal rather than a sign something went wrong.
What about callers who prefer Spanish?
Ask Cleod9 to confirm current language support for the Concierge in a live configuration before planning around it. Mansfield practices with a bilingual patient base should treat this as a requirement to verify rather than assume.
Do we keep our existing number?
Yes. Number portability is a federal requirement, so everything attaches to the number already on the practice's cards, listings and signage.
The opening fifteen seconds
More intake calls are lost in the first fifteen seconds than anywhere else in the script, and those seconds are usually the least carefully written part of the whole design.
Three things have to happen in them. The caller has to know they reached the right practice, they have to hear the emergency instruction, and they have to be asked something useful. Anything else in that window is competing with those three.
What does not belong: an explanation of what the system is, an apology for the wait, a description of how the call will proceed, or a menu of six options. Callers do not need to be told the architecture. They need to be moved forward.
The first real question should be the branch that shortens everything downstream, which in a medical practice is whether the caller has been seen before. It is easy to answer, nobody has to think about it, and the answer changes which of two very different paths the call takes.
Order matters within those seconds as well. The practice name first, because a caller who dialed the wrong number should find out immediately rather than after answering two questions. The emergency line next, before anything that invites the caller to describe why they are calling. Then the branch question.
Testing before real patients hear it
Configuration is not the last step before go-live. Testing is, and skipping it is how a practice discovers a broken question in front of forty patients instead of in front of four staff members.
Run the script against five deliberately awkward callers before anyone real hears it. Have colleagues play each one, and use their real speaking voices rather than a careful reading.
The person who answers a different question than the one asked, which is what most people do when a question is ambiguous. The person who volunteers everything at once, name, reason, insurance and history in a single breath. The person who says almost nothing and waits. The person calling on behalf of a parent or a child, which changes who the patient is and which the script frequently does not account for. And the person who wants a human immediately and says so in the first three seconds.
Each of these exposes a different weakness, and all five are ordinary rather than exceptional. A script that handles them handles most of what real callers do.
Then call the number yourself at three different times of day, including once from a car, and once with a television on in the background. What sounds fine in a quiet office frequently does not survive either.
Write down every place the script asked again, every place a tester paused, and every place the answer went somewhere the script did not expect. Those notes are the first revision, and doing that revision before launch rather than after is the difference between a two-week rollout and a two-month one.
The questions to ask any provider, and Cleod9's answers
A practice comparing providers should ask the same short set of questions of each and keep the answers in writing. Cleod9 has answered them as follows.
Will you sign a business associate agreement? Yes, through Wildix, the platform the service runs on. Which services does it cover? Voice, voicemail, video, call recording and transcription. What is excluded? SMS text messaging. Where do recordings live and for how long? In the platform's AWS environment, for a period the practice selects, from one week up to ten years. What independent audits do you hold? SOC 2 Type 1 and Type 2. How is call audio protected in transit? DTLS-SRTP for media, with TLS for signaling and web traffic.
Those answers are the vendor's half of the arrangement. The other half is the practice's own configuration, access decisions, training and documentation, and whether all of that meets the practice's obligations is a matter for its own privacy officer or counsel rather than for any vendor to assert.
Talking to Cleod9
Cleod9 is a Dallas-Fort Worth provider supporting its own customers, so a Mansfield practice deals with someone in the same metro rather than a distant queue. The platform is described on the Cleod9 services page.
Do one thing first. Write the intake questions the practice wants asked, then read them aloud to a colleague and have them answer as a patient would. The questions that need rewriting will announce themselves in about four minutes, and fixing them before configuration is far cheaper than fixing them afterward.