For organizations whose calls don’t fit one front desk. We build the receptionist around your locations, queues and systems — and run it where your data rules say it must: Canada-only, in your own cloud or on your own servers.
Head office · 4 locations
Illustrative · deployment options vary by plan
Organizations whose calls don’t fit a single front desk: groups with many locations, teams running a call centre or overflow line, and practices where privacy rules decide where data can go.
One receptionist that knows every location — or one per site. Each keeps its own hours, services, prices and on-call people, and head office sees everything in one report.
Takes the calls your queue can’t: after hours, at peaks or a whole line. It follows your agents’ scripts and passes anything it can’t finish to a person, with the caller’s details.
Intake, scheduling and routing only. Advice stays with your licensed people, and you choose where data lives — up to Canada-only processing or your own servers.
Running one location? The standard receptionist is built for you — see how Infold works and plan pricing.
Choose how far inside your own walls the receptionist runs. Every level answers calls the same way; what changes is where data is stored, where it’s processed and whose infrastructure it runs on.
Recordings, transcripts and summaries are stored in Canada as standard. Every provider in the live call path will be named, with its region, on our trust page before launch.
What changes
Usually chosen by Most single-location businesses
Every live step — phone line, speech recognition, the AI model, the voice and storage — runs in Canada. The providers and their regions are written into your agreement.
What changes
Usually chosen by Health, legal and financial practices
Infold runs inside your organization’s cloud account, in the region you choose, under your security policies. Your team controls access, keys and logs.
What changes
Usually chosen by Groups with their own cloud team and data policies
Speech recognition, the model and storage run on servers you own, in your building or your colocation. Calls arrive through your phone system.
What changes
Usually chosen by Call centres and organizations with their own data centre
| Compared | Level 1 Standard | Level 2 Canada-only processing | Level 3 Your cloud | Level 4 On-premise |
|---|---|---|---|---|
| Call records kept in | Canada | Canada | Your cloud account | Your servers |
| Live processing runs in | Providers and regions to be named on our trust page before launch | Canada, at every step | Your cloud account, plus any provider you approve | Your servers |
| Infrastructure belongs to | Infold | Infold | You | You |
| Operated by | Infold | Infold | Infold, through access you grant | Your IT team, with Infold |
| Pricing | Published plan pricing | Quoted after discovery | Quoted after discovery | Quoted after discovery |
| Usually chosen by | Most single-location businesses | Health, legal and financial practices | Groups with their own cloud team and data policies | Call centres and organizations with their own data centre |
Level 1 is how every Infold receptionist runs. Levels 2–4 are set up with you and written into your agreement, with every provider in the call path named. Our subprocessor list will name the standard providers and their regions before launch.
Through six steps from your phone line to your systems, with the reply spoken back and the records kept for the period you set. Pick a level to see where the boundary sits — and what stays inside it.
Level 1 · Standard
Hosted in Canada by default
Level 2 · Canada-only processing
Canada-only processing, end to end
Level 3 · Your cloud
Deployed in your own cloud account
Level 4 · On-premise
On your own servers
Every Infold receptionist stores call data in Canada as standard. When your policies go further, so do we — and we put it in writing.
Illustrative. English-language service across Canada; the dots aren’t offices or data centres.
We adapt the AI to your organization using material you approve — your scripts, your knowledge and, with consent, past calls you choose — and the result is used only by your receptionist. Your data never trains models shared with anyone else.
On every call, the receptionist answers from your approved knowledge — services, prices, hours, policies. Every Infold receptionist works this way. It isn’t training: nothing about the model changes.
For larger deployments we fine-tune a model on your approved scripts and on past calls you select. It picks up your terms, your products and how your best people handle difficult calls.
Before a new version answers your phones, we run it against your hardest past calls and agreed scenarios, and you sign off on the results.
Yes. If a system has an API, we can connect it — we build the integration during setup, as part of your project. Five connect today.
Connects today
Google Calendar 
Microsoft 365 
Open Dental 
Shopmonkey 
HubSpot Connected during setup
Third-party names are trademarks of their owners and are used only to say what Infold connects to.
Examples of workflows we build
Every action still passes your rules first — the receptionist can only do what you’ve approved.
Each location keeps its own rules — hours, services, prices and on-call people — while callers reach the right site and head office sees one report across all of them.
One number or one per site. It works out which location the caller needs — by what they say, their postal code or the number they dialled — and books with that team.
Caller
Hi — I’m in Barrhaven. Can someone come out Thursday morning?
Matched to Barrhaven by postal code
Infold
The Barrhaven team has 10:30 on Thursday. Shall I book that for you?
Booked with the Barrhaven team
How it picks a location
Each site keeps its own hours, services, prices and on-call people. Change one without touching the others.
Every location in one view: what callers wanted, what was booked, what needed a person.
Booked Message taken Transferred
Sample · fictional locations and caller, real workflow
Nothing goes live everywhere until it has handled your real calls in a pilot. Each stage ends with something you sign off.
We map your call types, locations, queues, systems and data rules with your operations, IT and privacy leads.
A written design: deployment level, reference architecture, integrations, call flows, rules and a dated plan. Nothing is built until you approve it.
One location, line or queue goes first. Your team tries to break it; we tune it on real calls until it handles the hardest ones.
Location by location or queue by queue, with shared reporting from day one and ongoing tuning after launch.
Straight answers on data, deployment, models and price. Anything else, ask us on the call.
We adapt a model to your organization using material you approve: your scripts, your knowledge and past calls you select, only where callers were told how recordings are used. The tuned model is kept separate for you and used only by your receptionist. Your data is never used to train models shared with other customers. Separately, every receptionist looks up your approved answers on each call — that is grounding, not training.
No. By default, Infold stores call data in Canada: recordings, transcripts and summaries. Canada-only processing — where every live step, from the phone line to the AI model and the voice, runs in Canada — is an option we set up and write into your agreement.
Yes. We can deploy into your organization’s cloud account, in the region you choose, or on servers you own. We review the reference architecture with your IT and security team during design, and nothing goes live until a pilot has handled your real calls.
Yes. Each location keeps its own rules — hours, services, prices and on-call people. Callers are routed to the right site by what they say, their postal code or the number they dialled, and head office gets one report across every location.
Yes. It can answer after hours, at peaks or on a whole line, following the same scripts and rules as your agents, and transfer to a person when one is needed.
Google Calendar, Microsoft 365, Open Dental, Shopmonkey and HubSpot connect today. Other systems with an API — practice management, field service, CRM, ticketing, phone systems — are connected during setup as part of your project.
No. For health, legal and financial practices it handles intake, scheduling and routing only. Anything that needs professional judgment goes to your people, by your rules.
Standard receptionists use our published plan pricing. Canada-only processing, your-cloud and on-premise deployments, private models and custom integrations are quoted after discovery, with scope and costs in writing before any work starts.
It depends on the deployment level and the systems involved; you get a dated plan at the end of the design stage. A standard receptionist is live in 2 business days once we have access and your approvals.
Thirty minutes with the people who would build it. Bring your call volumes, locations, systems and data rules — we’ll come back with a deployment level, an architecture and a written plan.
Prefer email? hi@infold.ai
Picking a time here needs JavaScript. Email hi@infold.ai with two or three times that suit you and we’ll confirm one by email.
Times shown in Eastern Time.
We’ll confirm your time by email and text.
Infold: you’re booked for a 30-minute build call by video or phone.
Want to hear it first? Hear sample calls.