Two products that share one set of foundations
Retrieval, connectors, tenancy, access control and deployment are built once and used by both modules. This page is the part that does not change when you switch channels.
Two front doors, one engine room.
Whichever module you start with, the knowledge, connectors, tenancy and governance underneath are the same. Adding the second channel is configuration, not a second integration project.
AI voice agents + customer CRM
AI chat + ticketing tool
One retrieval layer
Both modules index documents into the same search layer, partitioned by tenant. Upload once, ground answers on the phone and in chat.
Your systems, called live
Voice tools and chat data endpoints are the same idea in two channels: you register an API, the AI decides when to call it, and the response comes back fresh.
Multi-tenant to the row
Every query, cache key, search filter and API key is scoped to an organisation or project. There is no unfiltered fallback path in either module.
Governed by default
Role-based access, audit logging, encrypted secrets and per-key scoping ship with the platform rather than as an enterprise add-on.
Containers you can host
Every service is a container. Run it on our managed cloud or inside your own — the deployment topology is the same either way.
Adopt one, add the other
The modules are independent products with their own dashboards. Start with the channel that hurts most and turn the second one on later.
Same platform, different jobs.
If you are trying to work out which module you need — or whether you need both — this is the honest comparison.
| Dimension | Intelina VoicePhone | Intelina DeskWeb chat |
|---|---|---|
| Channel | Inbound phone calls | Chat widget on your website |
| How customers reach it | They dial your number | One script tag, no rebuild |
| What the AI is | Speech-to-speech agent with a persona, voice and tone | Text agent governed by a per-project AI policy |
| Identifying the customer | Caller ID matched against your imported records | Your own site tells the widget who is signed in |
| Where customer data lives | Imported into the platform as customer records | Fetched live from your APIs, cached briefly, never stored |
| Knowledge | Documents indexed and retrieved per organisation | Documents indexed per project, tagged by category |
| Taking action | Tools you define: webhook, lookup, escalate, end call | Registered data endpoints the model calls when relevant |
| Human handoff | Escalation tool invoked mid-call | Conversation becomes a ticket with the full thread attached |
| Work management | Call logs, transcripts, detected intents, recordings | Tickets, queues, SLA tracking, approvals |
| Team roles | Organisation members with shared agent configuration | Super admin, project admin, supervisor, support agent |
| Real-time transport | Telephony media stream bridged to the model socket | Live updates pushed to agents and customers |
| Priced on | Monthly call volume | Free tier, then plans by team and volume |
Running both? Knowledge uploaded for one module can be reused by the other.
What actually happens between the question and the answer.
No hand-waving: this is the sequence each module runs, in order, on every conversation.
What happens when the phone rings
- 01
Call arrives
The telephony provider posts the dialled number to the orchestrator, which resolves it to your organisation.
- 02
Context assembled
Agent persona, the caller's customer record and the relevant knowledge chunks are fetched in parallel and composed into one prompt.
- 03
Agent connects
The speech model opens with your persona, voice and the caller's real data already loaded.
- 04
Conversation runs
Audio is bridged both ways while transcripts are scanned for actionable intent.
- 05
Actions execute
A detected intent dispatches your tool, and the result is folded back into the agent's context.
- 06
Call closes
Remaining actions run, the transcript and recording are logged, and the caller receives an SMS confirmation.
Run it our way, or entirely your own.
The reason the voice module runs its own speech model rather than renting one is exactly this: self-hosting has to remain a real option, not a slide.
Managed cloud
We run it. You get dashboards, a phone number or a script tag, and an onboarding session. Fastest path to a working agent.
- No infrastructure work
- Rolling updates
- Shortest time to live
Your cloud
Every service is a container with an explicit configuration surface, so the same topology deploys into your own project or account.
- Data stays in your perimeter
- Your networking and IAM
- Same services, same versions
Hybrid
Keep the parts that touch customer data inside your boundary and let us operate the rest — common where the voice module needs hardware you would rather not manage.
- Split by sensitivity
- Bring your own search index
- Bring your own telephony account