Connect every conversation to the work that follows.
Oduist Connect turns calls, messages, and voice AI agents into structured context inside Odoo. Providers stay a replaceable transport — Odoo remains your system of record.
The product chain
The problem
Communication data ends up everywhere except where the work happens.
Every provider gives you another login and another silo. Scattered history, context rebuilt by hand, and details that slip between sales and support — none of it lands on the record that matters.
Conversations live in provider portals
Calls, SMS, WhatsApp threads, and AI agent transcripts sit in separate dashboards, disconnected from the customer record.
Context is rebuilt by hand
Before every interaction, staff dig through tools to remember who the customer is and what was last agreed.
CRM fills up incompletely
Without an automatic log, records miss recordings, summaries, and the next steps that should follow a conversation.
Information is lost between teams
What sales hears rarely reaches support — and what support learns rarely makes it back to sales.
…where the work actually happens — stays empty.
The solution
One communication journal, built inside Odoo.
Oduist Connect adds a single, structured log across every channel. Each step feeds the same record — one thread that never breaks.
- 01
Identify the customer by number
Incoming and outgoing events are matched to an existing party the moment they start.
- 02
Link the event to a record
Each interaction is attached to the right contact, lead, or ticket automatically.
- 03
Store calls and messages
Calls, SMS, and chat threads are captured as a single communication log.
- 04
Add recordings, transcripts & AI summaries
Recordings, transcripts, and AI-generated summaries are saved alongside the record.
- 05
Carry context into the next process
The captured context flows into the workflows that follow the conversation.
- 06
Run multiple providers in one database
Use several transport providers side by side within the same Odoo instance.
-
One communication journal, in Odoo
Every step above lands in the same record — recording, transcript, summary, and a link to the contact, lead, or ticket.
Provider capability matrix
Who does what — so you pick the right transport.
Providers are interchangeable and mix inside one Odoo database. A check means the capability ships in that provider module today — hover a cell for detail.
The module system
A periodic table of everything you can install.
Every square is one Odoo module from connect_addons_ng. Providers plug in under a technology-agnostic core; agents, apps, and memory sit on top. Click a category to isolate it.
Integrations
Bring your own transport.
Providers are interchangeable. Select a platform to see what it offers and how it is deployed — then mix and match within a single Odoo database.
Twilio
Provider integration
Cloud telephony with a browser phone and rich messaging.
Capabilities
- Cloud telephony
- Browser phone
- IVR flows
- SMS
connect_twilio — what the module offers →
Voice AI agents
Agents that speak with context and log the result.
Voice AI agents receive dynamic context from Odoo before they speak, then return the outcome of the conversation into the same shared journal your team uses.
Odoo provides
Dynamic context
Customer identity, related records, and history are handed to the agent at call time.
Agent returns
Conversation outcome
Transcript, summary, and next steps land back in the shared communication log.
Business outcome
Context that lands where the work already happens.
Because the log lives in Odoo, every conversation becomes usable inside the modules your teams work in daily.
History and next steps beside every lead
Communication history and the follow-up actions sit directly next to the lead, so nothing is rebuilt from memory.
Customer and conversation context inside the ticket
Agents open a ticket and see the customer's context and prior conversation without switching tools.
Commitments and signals for the next move
What was agreed on a call becomes a recorded signal that points to the next step in the deal.
Availability checks and meetings booked by AI
A voice AI agent can check availability and create a meeting while the customer is still on the line.
Customer Memory
Long-term memory of the whole relationship.
Connect Memory uses Hindsight to build durable, long-term memory about each customer. It combines correspondence, sales, invoices, returns, and payment behavior — then returns a shared relationship summary back into Odoo.
Hindsight relationship summary
Returned into Odoo and shared across teams and agents.
Let's design the right configuration for your infrastructure.
There is no one-size-fits-all setup. We start from your infrastructure and map out a deployment together.
- The right mix of communication providers
- The Odoo modules your teams actually use
- Where voice AI agents fit your workflows