Not a feature catalogue, but the sequence: what your team sees, and what happens in the background at the very same moment. From the first ring to the retention deadline.
Forty seconds from the first ring to a finished call record. Nobody types anything up.
The phone in the browser rings — whichever Odoo screen they happen to be on. The call card shows the customer's name, not just the number. They answer, type two lines into the notes field during the call and hang up. Afterwards the call sits in the customer's history: direction, duration, contact, note.
No second window, no second passwordThe number dialled belongs to exactly one company — in a multi-company setup a call cannot end up in the wrong one. The server holds the state of the call, not the browser: ringing, active, on hold, ended. Every step is checked against a fixed transition matrix, and every event lands in a log that can only grow.
The browser reports, the server decidesThe call card pulls in the contact, the history and the company the dialled number belongs to — before anyone picks up. If the number is not unambiguous, the field stays empty rather than wrong. For your working day that means you greet people by name and see the previous calls, without having to ask a colleague first what last time was about.
If several companies share one Odoo database, the dialled number decides which company the call belongs to. A call cannot end up in the wrong file. The server holds the state of the call, not the browser — reload the page by accident and the call is still there. Voice quality and packet loss are written onto the record as well.
The number is already in the record. So that is where it gets dialled — not typed into a desk phone.
Next to every phone number in Odoo there is a handset — on the contact, the lead, the ticket, the quotation. One click and the call is running. Anyone who prefers to search types the name into the phone's contact search or dials on the keypad. If the caller is unknown, they create the contact straight from the phone.
One click instead of twelve digitsThe browser sets the call up itself, straight to the PBX. No Odoo server process sits in the voice path — that is why a call does not slow your business application down. Each member of staff gets their own credentials, stored encrypted; the password is never shown to them.
Separate paths for voice and business dataEveryone sees their own calls with direction, duration, contact and note — and jumps from there back into the Odoo record.
The header of the phone shows whether the seat is really registered with the PBX. If audio drops in one direction, the interface says so instead of keeping quiet.
Put the caller on hold, speak to a colleague, then transfer — server-side, from a desk phone as well. Bringing several people into one call likewise. Both are switched on at commissioning.
It rings at twenty past six in the evening. Instead of an answering machine, a voice replies that listens, asks and takes notes.
A greeting you wrote yourself — with placeholders for company and time of day. After that, a normal conversation: the AI asks follow-up questions, remembers what was said before, and starts speaking before it has thought the sentence through to the end. That is why it sounds like a conversation and not like an announcement.
Greeting freely configurable per companyAudio runs fifty times a second in both directions through a service of its own: detect pauses in speech, recognise the sentence, formulate the answer, speak the answer. Speech recognition, language model and voice are preset to local services in the product; on the PhoneDesk Box they run on your own machine. The AI only listens again once it has finished speaking — otherwise it would transcribe itself.
Its own service, its own timing — not inside OdooThe AI greets, asks, summarises and hands over. It does not know your catalogue — and does not claim to.
The caller has hung up. A few seconds later the customer record says what it was about.
There is a card in the customer's history: three sentences on what the call was about, and below it the full transcript to expand. Next to it, sentiment, urgency and the topics detected. Anyone opening the record in the morning knows where things stand in ten seconds, without asking anybody.
On the contact, not in a log fileThe voice service sends exactly one message to Odoo — transcript, summary, both numbers — and identifies itself with a shared key. Odoo writes transcript and summary into encrypted columns and attaches the card to the history exactly once, even if the message were to arrive twice. Only people in the group intended for it may read it.
Stored encrypted, read behind a groupPlainly worded, without embellishment. It is produced after every AI call, not at the press of a button.
Every call gets an assessment and topic keywords — useful for follow-up and prioritisation. Switched on at commissioning.
If recognition mangled a name, the member of staff corrects it. Who changed what and when is in the audit trail, with a before and after checksum.
A transcript is produced where the AI took part in the conversation. For human-to-human calls it stays at note, duration and contact — we do not write down what we do not hear.
Every recognised sentence appears as a line in the call window, and on certain keywords PhoneDesk shows a hint. Both are off out of the box, are switched on at commissioning, and depend on the consent that is granted or withdrawn from the call window.
Day to day this takes away the pressure of writing while listening. The hint comes from a fixed keyword list, not from the language model: it reminds you to pin down the next step, and you either take it over or dismiss it. Consultation, transfer and conference stay reachable in the same window, even when the colleague is at a desk phone.
One record, one click, and the PBX knows about it. If it doesn't, the change rolls itself back.
The person responsible for IT creates a seat in Odoo: employee, extension, login name. One click generates the dialplan entry, a second deploys the device configuration to the PBX. After that the new colleague can be reached — with no ticket to a service provider and no session on the PBX server.
Minutes instead of daysA deployment is a fixed chain: generate, dry-run, write, reload — and then ask the running PBX what it actually holds. A success message on its own does not count as proof. If what is read back differs, PhoneDesk restores the previous state and marks the deployment as rolled back.
Half-deployed PBXs are not allowedIf the PBX has been rebuilt after an outage, PhoneDesk pulls its own configuration files back into Odoo records character for character. Device passwords are excluded — those are deliberately issued anew.
The supervisory authority asks about last year's calls. The appointment takes half an hour, not a week.
A menu of its own for consent: who agreed, refused or withdrew, and when, line by line. The company record holds the retention periods for calls, transcripts and recordings. The event log can be opened, filtered, exported — and not deleted.
Show it, don't describe itAccess to a recording is blocked as long as no consent decision exists. The event log refuses deletion even with administrator rights — the only exception is the retention run itself. Numbers and secrets are stripped out of log lines before they are written.
Refusing is the default, not the exceptionIn a multi-company setup each company is cleanly separated: one company's calls, consent records and logs are not visible to the other — not even through a number that belongs to both.
Summary, transcript, topics and sentiment hang in the contact’s history — stored encrypted, readable only with content rights and correctable with an audit trail. Anyone opening the record in the morning knows where things stand in ten seconds, without asking anybody.
The summary is three plain sentences, with the full transcript to expand below it — both are produced for a call the AI handled. Sentiment, urgency and topics come on top, once they are switched on at commissioning. If recognition mangled a name, a member of staff corrects it; who changed what and when stays as a line that cannot be deleted.
Six scenes are six scenes — not a complete telephony suite. What is missing today is stated here and not in the small print. Some of it is coming, some of it is not planned; we say both before the contract is signed.
The number is resolved to a contact, the card opens, the call history sits alongside it.
Recognise, understand, answer — and hand over to a human when needed.
Summary, topics, sentiment and duration — on the right record, with no typing.
A paid pilot with a fixed scope and a fixed end: one number for the AI, one deploy-and-rollback cycle, seats for your team — and a written list of what is still missing.