Phone System and Call Routing

The phone system turns the account into a telephone network. You provision numbers, decide what happens when each one rings, decide who it reaches and in what order, and decide what the platform does when nobody answers. Every call (connected, abandoned, voicemail or missed) is written to the contact record, so the telephone stops being the one channel the business cannot see.

The useful mental model is a chain of decisions between a ringing number and a human voice. The number receives the call. A greeting or menu may answer it. A routing rule picks who should take it. A ring group rings them, in order or all at once, for a set time. If nobody picks up, a fallback catches the call: voicemail, another group, an AI voice agent, or an automatic text back. Every link in that chain is configurable, and a call that goes wrong went wrong at one identifiable link.

The second thing to hold onto is that the call is data. Direction, duration, outcome, recording, transcript and the number dialled all become fields that workflows can branch on and reports can count. That is what makes the missed call a trigger rather than a lost opportunity, and what lets an operator prove how many inquiries the phone actually produced.

Numbers

• Local, national, toll-free and cell numbers where the country supports them, provisioned inside the account
• Porting an existing business number in, and the verification the carrier requires before it moves
• Separate numbers per location, per service line or per marketing source, so the number dialled identifies the campaign
• Caller ID name presentation, and the registration or verification each country demands before calls connect cleanly
• Which number is used for outbound calls and texts by default, per user and per workflow

Inbound routing

• Greeting audio: uploaded recordings, text read aloud, or no greeting at all for a straight ring
• IVR menus with numbered options, each option routing to a group, a person, a voicemail box, a submenu or an AI voice agent
• Ring groups with simultaneous ringing, sequential ringing in a set order, or round-robin distribution
• Ring duration per stage, and the fallback when the stage times out
• Business-hours and after-hours routing as two separate paths, plus holiday overrides
• Forwarding to external numbers such as a mobile or an answering service
• Call screening, so the person answering hears who is calling and why before accepting

During the call

• Call recording, on for everything or conditional, with an announcement where consent requires one
• Transcription and AI summaries written back to the contact timeline
• Whisper messages that tell the answering user the source or campaign before they speak
• Hold music, queue position announcements and queue timeout behavior
• Call transfer, warm or cold, between users and groups
• Softphone use in the browser, the mobile app, or a forwarded handset

When nobody answers

• Voicemail boxes per number, per group or per user, each with its own greeting
• Voicemail transcription and notification by email, SMS or internal alert
• Missed-call text back, sent automatically from the number that was dialled
• Voicemail drop on outbound calls, leaving a pre-recorded message without waiting
• Handover to an AI voice agent as the fallback rather than voicemail

Outbound and reporting

• Click-to-call from the contact record and the inbox, with the call logged automatically
• Call outcome and disposition tagging by the user after the call ends
• Workflow triggers on inbound call, missed call, call completed, outcome set and voicemail left
• Reporting by number, by user, by time of day and by outcome, with recordings attached
• Attribution of calls to the campaign or source that produced the number dialled

1. Map the call flow on paper first, as a chain: number, greeting, menu, group, ring time, fallback. Do it for business hours and again for after hours, because they are two different flows.
2. Decide the number plan before provisioning. One main number the client advertises, plus a separate number per marketing source or location if attribution matters. Numbers are cheap to add and painful to rearrange later.
3. Provision the numbers and complete whatever caller-identity registration the country requires. Skipping this is why calls get labeled as spam and never connect.
4. If an existing number is being ported, start the port early and keep the old service live until it completes. Build the new flow on a temporary number in the meantime.
5. Create the users who will answer, confirm each can take a call on the device they will actually use, and check audio both ways before anyone depends on it.
6. Build the ring groups next, and choose the ring style deliberately: simultaneous for a small front desk that must not miss anything, sequential when seniority or specialism matters, round-robin when load should be shared.
7. Set the ring duration honestly. Long enough that someone can reach the phone, short enough that the caller is not abandoned listening to ringing. Then set what happens when it times out.
8. Record the greeting and, if you are using one, the menu. Keep the menu to a few options, say the option number after the description, and never bury the route to a human.
9. Configure business hours and build the after-hours path as its own flow: a different greeting, voicemail or an AI voice agent, and an immediate text back so the caller knows they were heard.
10. Turn on missed-call text back from the dialled number, and write the message to say who it is from and ask one specific question. This single setting recovers more inquiries than most workflows.
11. Set up voicemail boxes with greetings that tell the caller when to expect a reply, enable transcription, and route the notification to a person rather than a shared address nobody opens.
12. Decide on recording explicitly with the client, confirm the legal position in every jurisdiction they take calls from, and enable the announcement if consent requires it.
13. Add whisper so the answering user hears the source or service before they speak. Being told "website inquiry, knee clinic" changes the first sentence of the call.
14. Attach the workflows: missed call to text back and task, voicemail left to notification and follow-up, call completed to outcome logging, and inbound call from an unknown number to contact creation.
15. Agree the disposition list with the team and keep it short. Outcomes nobody sets are worse than no outcomes, because the reporting looks complete and is not.
16. Test the whole chain from an outside handset: in hours, out of hours, every menu option, nobody answering, and a transfer. Then check that each of those calls appears correctly on the contact record.
17. Watch the call reports for the first two weeks and look specifically at missed and abandoned calls by time of day. That is where the routing is wrong, and it is always fixable.

The phone system is the bridge between offline intent and the rest of the build. It feeds the unified inbox with calls, recordings and transcripts; it hands callers to the voice AI agent when no human is free; it triggers workflows on every outcome; it supplies the source numbers that make reporting and attribution honest; and it gives pipelines a stage change that reflects a real conversation rather than a click.

Missed call to booked appointment

A caller rings the advertised number during a busy hour and nobody answers. The missed-call trigger sends an immediate text from the same number, the reply lands in the inbox, and the front desk sends a booking link for the short-notice calendar. An opportunity is created at an inquiry stage so the recovered call is visible in the pipeline rather than lost in a call log.

Multi-location routing with attribution

Each clinic advertises its own number. The IVR offers the service lines, the ring group for that site rings in order, and whisper tells the receptionist which site and service the caller chose. Because the number dialled is recorded, reporting shows which location and which campaign the calls came from, and the ad manager can be judged on calls rather than clicks.

After-hours cover without an answering service

Outside business hours the flow routes to the voice AI agent, which answers from the knowledge base, captures the caller's details and books into the overnight calendar where appropriate. Anything it cannot handle goes to voicemail with transcription, and a workflow creates a task for the morning with the transcript attached, so the first hour of the day starts with context.

• Caller-identity registration is not optional in practice. An unregistered or unverified number increasingly gets flagged, labeled or blocked by the receiving carrier. The platform will let you dial; the network decides whether the phone rings.
• Porting takes longer than anyone plans for. It depends on the losing carrier, not on you. Never schedule a go-live on the assumption a port lands on a given day, and never cancel the old service early.
• Ring time and voicemail fight each other. If the forwarded mobile's own voicemail answers before the platform's fallback, the call leaves the system and the recording, transcript and trigger never happen. Set the handset voicemail longer than the platform ring time.
• Simultaneous ringing on mobiles is unreliable. Poor signal, do-not-disturb and screen-lock behavior all mean a group can look answered when nobody heard it. Test on the actual devices.
• IVR menus lose callers. Every option is a chance to hang up. For small businesses a straight ring with a good fallback usually outperforms a menu.
• Recording law varies by jurisdiction and by party. One-party and all-party consent rules differ, and calls crossing borders may need announcements. This is the client's legal exposure; get their written decision before enabling it.
• Transcription is approximate. Accents, crosstalk and background noise degrade it, and an AI summary built on a poor transcript will be confidently wrong. Treat it as a prompt to listen, not as the record.
• Missed-call text back can text the wrong people. Wrong numbers, withheld numbers and existing customers calling about something unrelated all receive it. Condition it where you can, and keep the wording neutral.
• Outbound calls from the wrong number break attribution and trust. If a rep calls back from a different number than the one advertised, the contact does not recognize it and the campaign loses the call.
• Call outcomes are manual. Nothing sets a disposition for you, so reporting on call outcomes is only as honest as the team's discipline on the day.
• Voicemail notifications sent to a shared mailbox get ignored. Route them to a named person and pair them with a task, or they become an archive nobody opens.
• Number-level routing changes apply immediately and live. Editing a flow mid-day can drop calls that are in progress or send them somewhere unmanned. Change routing out of hours.
• Deleting or releasing a number is irreversible. The number usually cannot be recovered, and anything advertising it (signage, directories, ad accounts) keeps sending callers to a dead line.
• Calls and minutes consume account usage. Long hold times, voicemail transcription and always-on recording all add up, and nothing warns the client before the usage does.