Call Routing Blueprint
Decide which Weave calls forward to Katie, which ring your desk, and which reach a person. A routing plan built around the calls a medical office gets.
Two routing layers with two owners
Routing on a Weave practice happens in two places. The first is your Weave phone system, which decides whether a call rings the desk or forwards to MedReception AI. The second is the set of rules you give MedReception AI, which decides what Katie does once she has the caller. Keeping those layers separate in your head is most of the work.
Weave owns the first decision. Your office manager, or whoever administers your Weave phones, sets the forwarding: overflow, lunch, after hours or all calls. MedReception AI owns the second, and it follows rules your practice writes: which calls go to a person, who gets transfers and how urgent calls are escalated. MedReception AI syncs with your Weave phone system, and the forwarded call itself is the handoff between the two.
Sorting by what the caller needs
A routing plan should start from the calls you actually receive, not from the phone menu someone recorded years ago. For a typical medical office the categories look like this:
- Scheduling, rescheduling and cancellations, captured against the visit types you define
- Refill requests, passed to clinical staff and never approved or changed by the AI
- Questions about symptoms, results or medications, handled under your clinical escalation rules
- Billing and balance questions, pointed to your billing line or payment link
- Records requests, referral questions and forms, summarized for whoever owns that work
- Calls from hospitals, pharmacies and other offices, sent where your rules say
Calls that belong with a person
Some callers are better served by your own staff while the office is open: a hospital discharge planner arranging follow-up, a pharmacist with a question about a script, a patient upset about a bill who has already called twice. You decide that list. During open hours Katie transfers those calls to the staff you name, and everything else ends in a summary staff can work through between patients.
On Weave, choose transfer destinations with the forwarding in mind. If Katie transfers to a line that is itself set to forward to MedReception AI, the caller can land back with her. A direct extension, or a line reserved for transfers, keeps the path clean.
Testing the plan before patients hear it
Before launch, call your own number from a mobile phone the way a patient would. Try it at lunch, try it when every line is busy and try it after closing. Confirm each call reaches the right place and that the summary describes what you actually said.
Then read the first weeks of summaries closely. If too many calls are being transferred, or too few, adjust the rules you gave MedReception AI rather than the Weave forwarding. Forwarding decides when Katie answers. The rules decide what happens next.
Frequently asked questions
- Can our Weave system forward only certain kinds of calls?
- The usual approach is to forward by timing, such as overflow, lunch, after hours or every call, and let Katie sort by need once she answers. Ask whoever manages your Weave phones which forwarding options your setup supports.
- What happens to a call Katie cannot resolve?
- It ends in a structured summary for your staff: who called, why, what they need and how urgent it is. If the office is open and your rules say the call needs a person, Katie transfers it instead.
- Who decides which calls count as urgent?
- Your practice does. Urgent and clinical calls follow the escalation rules you set, and Katie makes no clinical decisions of her own.
- Do we need to rebuild our Weave phone tree?
- Usually not. The forwarding rule can sit alongside your existing greetings and extensions. Whoever manages your Weave phones can confirm how it fits your particular setup.
Ready to answer these calls beside Weave?
Book a demo to see how Katie answers scheduling, referral and new patient calls forwarded from your Weave phones.
Book a Demo →