Skip to main content
SwiftCase
PlatformForward-deployedSwitchboardFeaturesSolutionsCase StudiesFree ToolsPricingAbout
Book a Discovery Call
SwiftCase

Workflow automation for UK service businesses. Created in the UK.

A Livepoint Solution

Platform

  • Platform Overview
  • Workflow Engine
  • Case Management
  • CRM
  • Document Generation
  • Document Extraction
  • Context Graph
  • Data Model
  • Integrations
  • Analytics

Switchboard

  • Switchboard Overview
  • Voice AI
  • Chat
  • Email
  • SMS
  • WhatsApp

Features

  • All Features
  • Claims Operations
  • High-Volume Operations
  • Multi-Party Collaboration
  • Contract Renewals
  • Compliance & Audit
  • Pricing
  • Case Studies
  • Customers
  • Why SwiftCase

Company

  • About
  • What is SwiftCase
  • Our Team
  • Adam Sykes
  • Nik Ellis
  • Implementation
  • 30-Day Pilot
  • Operations Pressure Map
  • For Your Role
  • Peer Clusters
  • Engineering
  • Careers
  • Partners
  • Press
  • Research
  • Tech Radar
  • Blog
  • Contact
  • SwiftCase Signal

Resources

  • Use Cases
  • Software
  • ROI Calculator
  • Pressure Diagnostic
  • Pilot Scope Estimator
  • Board Case Builder
  • Free Tools
  • Guides & Templates
  • FAQ
  • Compare
  • Best Practices
  • Changelog
  • Documentation
  • Help Centre

Legal

  • Privacy
  • Terms
  • Cookies
  • Accessibility

Stay in the loop

Cyber Essentials CertifiedGDPR CompliantUK Data Centres

The screenshots on this page are SwiftCase's own screens, filled with made-up firms, cases and people, so no client's data is on show.

© 2026 SwiftCase. All rights reserved.

Switchboard

Wantaperson?
You'reputthrough.

Switchboard puts callers through to your team when they ask for a person, or when the call goes beyond what you've told it to handle. It's a straight transfer to the number you've set, and anything it has already changed is on the case.

When it puts callers through
Where people decide

When

Three reasons it hands a call over.

All three come down to the rules you give it, so you decide where its job stops.

They ask for a person

Someone who wants a person should get one. Its rules can tell it to put them straight through, without arguing or asking why.

For example

  • “Can I speak to someone?”
  • “Put me through to the office”
  • “I want to talk to a manager”

Your rules say so

You write, in plain English, the calls it should hand over. It follows them on each call. It's the language model's judgement against your instructions, so write them the way you'd brief a new starter.

For example

  • A complaint
  • A caller who sounds distressed or vulnerable
  • Anything about a value or a cover decision

It can't help

When the caller can't be verified, the case can't be found or the question needs something it hasn't been given a tool for, it can put them through instead of going round in circles.

For example

  • Details that don't match the case
  • A case it can't find
  • A request it has no tool for

What happens

Four steps, and the caller is talking to your team.

1

The agent decides to transfer

Because the caller asked, or because your rules say this call should go to a person.

2

The call goes to your number

Twilio dials the transfer number you've set for that agent, or your default number, and connects the caller.

3

Your team answers

It's a straight transfer, so the person who answers hears the story from the caller. Anything the agent changed is already on the case.

4

The transcript follows

When the call ends, Switchboard can email the transcript to your team, so whoever took it can check what was said before they picked up.

Not yet

What a transfer doesn't do today.

Better you hear it from us than find out on your first busy Monday.

  • A briefing on screen
    The person who answers gets nothing from Switchboard on their screen. They have the case in SwiftCase.
  • A warm handover
    The agent doesn't introduce the caller to the person picking up. It connects the call.
  • Transfers marked as transfers
    Switchboard's call list doesn't yet show that a call ended in a transfer.

How it's set up

A person is never more than a sentence away.

No dead ends

A caller can always get to a person. An agent that keeps someone talking when they've asked for a human does more damage than no agent at all.

One number per agent

Each agent has its own transfer number. Calls that should reach different teams can come in on different agents, each putting callers through to its own team.

You write the rules

When to hand over is in the agent's instructions, in plain English. Change them in Switchboard and the next call follows the new ones.

On the record

Calls can be recorded, and each change the agent made before the transfer is logged on the case.

FAQ

The questions about transfers.

How quickly does the transfer happen?

As soon as the agent decides to transfer, the call is dialled through to your number. How fast it's answered is down to your phones and your team.

Can we choose when it puts callers through?

Yes. You write it in the agent's rules: the kinds of call it should hand over, and anything it must never handle itself. A caller who asks for a person can always be put through.

What does the person who answers see?

Nothing from Switchboard on screen yet. They have the case in SwiftCase, with anything the agent changed already on it, and the transcript can be emailed to the team when the call ends.

Can it spot a vulnerable customer?

Only as far as your rules tell it to listen for one. It's a language model following instructions, so tell it to put such callers straight through and treat it as a first line. It supports your vulnerable-customer process; it doesn't replace it.

Can it send calls to different people?

Each agent has one transfer number. Calls for different teams can come in on different agents, each with its own number.

Try it on your own calls.

Pilot Switchboard on one line, listen to the calls it puts through, and adjust its rules until it hands over at the right moments.

Scope a 30-day pilot
How SwiftCase keeps the record