CanaricsYour AI assistant can operate your phone system
More and more companies have their own AI assistant: a Claude connected to company tools, a ChatGPT with actions, an internal agent watching operations. Canarics is built so that assistant can work with your phone line directly: read every call result, notice a missed customer the moment it happens, and ask your voice agent to call them back.
What your assistant can do
| Capability | How |
|---|---|
| Check minute usage | Minutes used against the plan this billing cycle, and the cap where calls stop. No surprise invoices. |
| Read call results | AI-written summaries, quality scores, sentiment, and missed or recovered status for every call, human or AI-handled. Transcripts stay private by design. |
| Pull daily statistics | Per-day totals, missed and recovered counts, and score averages for up to 90 days, in your timezone. |
| Look up a caller | Cross-call history for one number: how many touches, the last outcome, recent conversation summaries. |
| React in real time | Canarics pushes signed webhook events to your systems: call.analyzed after every analyzed call, call.missed the moment an inbound customer call goes unanswered. |
| Request a callback | On the outbound plan, with a manager-enabled key, the assistant schedules your Canarics voice agent to call a known customer back, with a reason grounded in what the customer asked. |
The loop nobody else closes
Put the pieces together and two AI systems handle a missed customer with no human in the critical path:
- A customer calls, nobody picks up. Within seconds a call.missed event lands on your endpoint.
- Your assistant looks up the caller's history: four previous conversations, last one about a price quote.
- It requests a callback with that context: "Customer was waiting for the winter tire quote."
- The Canarics voice agent calls the customer back, briefed, in the customer's language.
- The analyzed result returns to your systems as a call.analyzed event, summary and score included.
Your assistant decides; our agent speaks. Each side does what it is good at.
Security is the design, not a setting
Giving an external AI access to call data deserves paranoia, so the defaults are strict. Keys are read-only unless a manager explicitly enables callbacks, scoped to one team, revocable in one click, and stored only as cryptographic hashes. Every response passes a field allowlist: no transcripts, no integration tokens, never another team's data. Callback requests only work toward numbers that have already talked with your team, capped per day, inside calling hours, and the callback reason is treated as data, never as instructions to the voice agent. Everything runs and stays in the EU.
Common questions
Can ChatGPT or Claude access my Canarics account?
Yes. A team manager creates a read-only API key in the dashboard and gives it to the assistant. Any AI tool that can make HTTP requests can then check usage, read call summaries, and pull statistics. Claude connects in one line as a remote MCP server.
Can my AI assistant make calls through Canarics?
It can request a callback to a customer your team already has history with, on the outbound plan and on a key a manager enabled for that. Volume is capped, calling hours are enforced, and the same billing safeguards apply as to every other call. It is never a cold-calling API.
Is it safe to give an AI assistant access to call data?
Keys are read-only by default, team-scoped, revocable, and stored only as hashes. Responses carry no transcripts and no credentials. If a key leaks, the worst case is disclosure of your own team's call summaries until you revoke it, and never an action that costs money.
Where do I start?
Start a free trial, open the Team tab, create an API key, and hand it to your assistant together with the docs link. Assistants also find their way alone: this site describes the API in llms.txt, the format AI tools read.
Paste canarics.com/openapi.json into your assistant and ask it what it could do for your phone line.