The desk phone is gone from most offices and nobody misses it. What teams still need is everything the phone system behind it did: a main number with a menu, calls that ring the right group, hold and transfer that work, recording, and a way for a manager to listen in. Here is the checklist for a phone system that runs from a browser and your team's own cells, and what changes when the system also handles what happens after the call.
The parts you still need
- An attendant menu. "Press 1 for scheduling, 2 for billing." Routes callers before a human picks up.
- Ring groups. A front-desk group, a dispatch group, a sales group. The call rings the team, and whoever is free answers.
- Direct numbers. Some people need to be reachable directly without the menu.
- A browser softphone. Make and take calls from the browser, from any computer. Existing cell phones should also be able to ring as part of a line, so nobody has to install hardware.
- Hold, park and transfer without conference-bridge gymnastics.
- Listen, whisper, barge. A manager hears a live call (listen), speaks only to the rep (whisper), or joins (barge), for coaching and quality review.
- Recording with an announcement you control. Recording is only useful if it is lawful; the system should play the notice for you. See our guide to recording consent.
- Presence and reports. Who's on a call right now, and call-volume and handling reports afterwards.
- Texting from the same number, where a workspace has it turned on, including an automatic text back to a known contact who didn't get through. Unknown numbers and anyone who replied STOP should never get one.
That is a complete small-business phone system, and it needs no hardware PBX. Quill Hound Voice covers each item above.
What happens after the call is the new part
The call ends and the rep has a choice: write the note now, or do it later. Later usually means never, and the CRM record goes quiet. The useful AI feature in a phone system is not a chatbot; it is doing the after-call work automatically and leaving the rep in control:
- Transcribe every recorded call once it ends.
- Summarise: an overview and key points written to the call record, so the next person reads it instead of relistening.
- Draft the follow-up: a text and an email drafted from what was actually said. The rep reviews, edits or dismisses it. Nothing sends on its own.
- Save it to the CRM. Connected to Salesforce or Bullhorn, the call, its summary and the follow-up task save back to the right record, with a visible saved-or-failed status and automatic retries. A write-back that fails silently is worse than none.
Who this fits
- Home services. Route to the right dispatcher, record for quality, and hand reps a ready-made follow-up after every estimate call.
- Medical and dental front desks. Ring groups, recording, and a summary attached to every call instead of a handwritten note.
- Staffing and recruiting. Bullhorn write-back keeps the call, the note and the follow-up task on the right candidate or client record automatically.
- Anyone else on the phone all day. Attendant menu, ring groups and monitoring work the same regardless of industry.
Questions to ask a provider
- Can reps work from a browser and have their cell ring on a line?
- Can a manager listen, whisper and barge?
- Does recording play an announcement, and can I control it?
- Is the follow-up always a draft, or does anything send automatically?
- Which CRMs are supported, and what happens when a write-back fails?
- Can I see which marketing made the phone ring? That is call tracking, a separate thing; Quill Calls does it and is sold with Quill Hound Voice as a bundle so the campaign and the call sit together.
Quick answers
Do we need desk phones for a business phone system?
No. Reps call and answer from a browser softphone, and existing cell phones can also ring as part of a line.
Can the system send follow-ups for us automatically?
In Quill Hound Voice, no, on purpose. The follow-up text and email are always drafts that the rep reviews, edits or dismisses.
Which CRMs connect?
Salesforce and Bullhorn today, with click-to-dial and an embedded call panel, plus a generic webhook for anything else.
What if a CRM write-back fails?
It is never silent: every write-back shows saved or failed on the call, and failures retry automatically.