Customer support
Voice AI for
customer support.
The questions your help centre already answers, handled on the phone and in web chat. Everything else reaches a person with the transcript already written.
Coverage
The calls it takes off your team.
The same questions make up most of the queue, and your help centre already answers them. Callspace reads your site, your PDFs, and your policies, then answers those on the phone and in chat. What is left reaches your team with the caller’s name, account, and problem already written down. Nobody has to repeat themselves.
- 01
Answers from your help centre
Point it at your docs, upload the PDFs, write the policies in plain English. It answers hours, billing terms, how-to, what is included. When the material does not cover the question, it takes a message.
- 02
One agent on the phone and in chat
Your published number and a script tag on your site run the same agent on the same knowledge. A customer who calls, then chats, is one thread in one inbox.
- 03
Writes down the whole problem
Name, account, what broke, what they already tried. Written to the contact and posted to your helpdesk over webhook, so it lands in the queue your team already works.
- 04
Escalates on your rules
You decide what always goes to a person: billing disputes, cancellations, anyone who sounds upset. The agent rings that department and connects only when someone picks up. Otherwise it books a callback.
Boundaries
What it will not do
- It does not promise refunds, credits, or exceptions to policy. Those are yours to grant.
- It does not guess at an answer your documentation does not contain.
- It does not talk a customer out of asking for a person.
Integrations
Connects to what you already run.
Live integrations are the ones the agent can act through today. The rest are on the way, and anything not listed reaches us through webhooks or a custom integration.
- Avaros EMR Soon
- Attio Soon
- Salesforce Soon
- HubSpot Soon
- Slack Soon
- Pipedrive Soon
- Zapier Soon
- Stripe Soon
- n8n Soon
Trust
Built to a healthcare standard.
Support calls carry account numbers, addresses, and billing details. These are the controls we built for our healthcare customers, running on the same platform your calls run on. A SOC 2 Type II audit is underway, and the report goes to every customer before they go live.
- 01
Compliance mode, one way only
PHIPA/HIPAA compliance mode is set per organization and cannot be turned back off. Behaviour that depends on it cannot be relaxed later, by your team or by ours.
- 02
Notifications carry no PHI
With compliance mode on, email and SMS call summaries carry a link and nothing else, and push notifications drop the preview entirely. Lock screens and inboxes are the two places this data most often leaks, so it never goes there.
- 03
Every access recorded
Reads of PHI-bearing records are written to an access log with actor, action, resource, request id, IP address, and timestamp — built to the content specification in PHIPA s. 10.1(4). Owner and admin only, viewable in the app and exportable as CSV.
- 04
Diagnostics log field names only
Field names carry no caller data, so they are logged everywhere. Values are never written to a log line under compliance mode.
Compared
Against what you have now.
A phone tree is cheap and everyone hates it. An answering service is human and stops at taking a message. Here is where the agent lands.
| Capability | Phone tree | Answering service | Callspace |
|---|---|---|---|
| Caller says what they need in their own words | Press 1 for… | Yes | Yes |
| Answers every line at once during a spike | Queues | Depends on staffing | Yes |
| Books into your calendar on the call | No | Sometimes, at extra cost | Yes |
| Looks up an order or a record mid-call | No | Rarely | Shopify, calendar, CRM, webhooks |
| Transfers with the context already gathered | Cold transfer | Message only | Warm, with transcript |
| Recording and transcript of every call | Sometimes | Rarely shared | Yes, searchable |
| Keeps PHI out of notifications and logs | N/A | Your problem | Compliance mode, one-way |
| Tells the caller what it is when asked | Obvious | Human | Yes, and transfers on request |
Rollout
Live on one line before it is live on all of them.
No big-bang cutover. You hear how it handles your actual callers on a narrow scope, then decide how far to take it.
- Step 01
Scope the calls
We go through the calls you actually get, decide which ones the agent should own, and agree what it must always hand to a person.
- Step 02
Build and connect
Your script, your escalation rules, your calendar, CRM, or store. If you need compliance mode, it is switched on here, before any real call is answered.
- Step 03
Test on real scenarios
We run the edge cases — the angry caller, the wrong number, the emergency, the caller who asks whether it is a person — and adjust until it holds up.
- Step 04
Go live on one line
Forward one number or one after-hours branch. You listen to a week of real calls, then widen the scope with evidence rather than optimism.
FAQ
Questions we get asked.
How does it learn our product?
It reads your website on setup. After that you add help pages by URL, PDF and Word files, or plain text. It answers from that material and the instructions you write.
Does it create tickets in our helpdesk?
Over webhook. Every call and chat posts its summary, transcript, and contact details to an endpoint you control, which is how teams feed Zendesk, Intercom, or an internal queue. Tell us what you run and we will connect it.
Can it handle web chat as well as calls?
Yes. One script tag on your site, the same agent, the same knowledge, the same inbox as the phone calls.
What if a customer is angry?
You write the escalation rules. A caller who asks for a person is transferred. If nobody answers, the agent takes a message and books a callback, and the transcript is waiting for whoever picks it up.
Bring us the calls you were told needed a person.
We will go through your actual call volume, agree what the agent should never touch, and put it live on one line so you hear it on your own callers. A BAA is in place first if you need one.