Phones that hold upto professional indemnity.
Matter-tagged recordings, OOH cover, no-overflow lines.
Built for UK law firms: every inbound call recorded, transcribed, and tagged against the matter. After-hours rotas without a separate answering service. The cost per fee-earner stays flat whether you've got 5 staff or 50.
- High-street family firm
- Conveyancing volume practice
- In-house corporate legal
- Barrister's chambers
- 100%Inbound calls recordable
- Per callAI transcript + summary
- 99.95%Uptime SLA
What you actually get.
Features tuned to solicitors & legal — included on every seat, no upsells.
Caller-ID popping for your CMS
VoiceCloud exposes a WebSocket presence API + click-to-dial via tel: links. Case-management systems that can consume them (Clio + Leap natively, Proclaim via middleware) pop the matter when the matching client rings in. Your CMS does the matching — we feed it the call.
Recording that holds up at PI
Inbound + outbound recording with the standard 'this call may be recorded' announcement, in-portal playback, per-call tagging + notes, and CSV / PDF transcript export for the file. Pair it with your firm's data-retention schedule documented in the privacy notice.
Overflow without overflow staff
Calls land in a queue with on-hold messaging, then route to whoever's free. AI receptionist takes the message + emails the matter clerk if every extension is busy. Caller never hits voicemail unprompted.
On-call rota that works
Time-of-day + day-of-week routing sends OOH calls to the duty partner's mobile via the VoiceCloud app — same number, no separate on-call line. Rota changes via portal, not a manual diversion.
AI summary on every call card
Every recorded call ends with a structured AI summary in the portal — caller, topic, action items, agreed next step. The fee-earner pastes the summary into the matter note rather than typing it from memory. Direct CMS push is on the platform-integrations roadmap.
Confidential outbound dialling
Per-extension caller-ID — appear from chambers' main number for client work, withhold number for sensitive outbound calls. One app, one click.
Three days in the life of a solicitors & legal.
Concrete moments — what triggers a call, the features that handle it, the outcome. These are scenarios you'll recognise; map them onto your own week.
- 01Scenario4 features
Conveyancing exchange-day call
The triggerClient rings the firm's main number on completion day to confirm funds have moved.
What happensInbound number hits the VoiceCloud presence API. The CMS subscribes and pops the matching matter on the fee-earner's screen before they pick up — they greet by name.
Call recorded with in-portal playback. Per-call tagging marks it 'exchange day · funds confirmation' so it's findable months later.
Two-line summary appears on the call card: 'Client confirmed funds received 14:22. Agreed completion call back at 16:00.' Fee-earner pastes it into the matter note in the CMS.
Fee-earner fires a Business SMS from chambers' Giant mobile line: 'Funds confirmed received, ringing you back at 16:00.' Client gets a written record they can point to weeks later — and can reply for straightforward questions without a phone call.
OutcomeIndemnity-grade evidence trail with minimal admin. Conveyancing volume scales without scaling the secretary headcount.
- 02Scenario4 features
Complaint dispute — pulling the audio
The triggerSix weeks after a contentious call, the client complains in writing about what was 'promised'.
What happensFilter the recordings by the matter tag the fee-earner set at the time. Six weeks of unrelated calls drop away; the relevant ones surface.
Search the transcript for the disputed phrase. Found in the 14-minute call from 6 weeks ago — jump straight to the timestamp.
The AI summary written when the call ended is still attached: caller, topic, action agreed. Partner cross-checks it against what the complaint alleges in 30 seconds.
Export the recording + the AI transcript as a PDF, attach to the complaint response. Documented evidence, ready in 5 minutes.
OutcomeComplaint resolved on the call recording, not on word-against-word. PI insurer happy; complaint closes without escalation.
- 03Scenario3 features
Out-of-hours duty partner rota
The triggerSaturday evening — urgent client query from someone arrested.
What happensChambers' main number routes outside Mon-Fri 9-6 to the duty partner's rota number — different rota slot each weekend, no need to publish a separate OOH line.
Call arrives as a push notification on the duty partner's phone via the app — answers from the kitchen with the chambers caller-ID showing the client.
Partner dials the holding-cell number back — caller-ID presents as chambers, not her personal mobile. Client never gets her number; rota stays clean.
OutcomeNo separate OOH agency contract, no 'duty mobile' device to pass between partners. Every weekend swap is a portal toggle.
Talk to the UK team about solicitors & legal.