Skip to content
Sign in
EN

Integrations in detail Odoo

Odoo: see who is calling before you pick up

The phone rings, a number appears, and the question is always the same: who is this? Your Odoo holds the answer — but in Odoo, not where the call is happening.

Haus iT Caller ID looks the number up in your company’s Odoo and shows company, contact person and customer number in the sidebar of your Webex client, while it is still ringing. One click opens the record in Odoo.

  1. The phone rings Incoming call
  2. Webex reports the number
  3. Haus iT Caller ID standardises it
  4. Your Odoo looks it up Your customer data stays here
  5. The sidebar names the caller
About 250 milliseconds from ring to name, measured on 03/09/2026 across 25 numbers that had never been looked up before. Not a single lookup took more than 400 milliseconds – the threshold at which a person starts waiting.
63 %
of incoming calls were identified. Measured at one customer over 30 days, counted per call rather than per number — the same situation gives only 33 % when counted per number.

What the tile shows

  • Company and contact person from the Odoo record
  • The customer number, where one is stored
  • The photo held in Odoo — in a measured set of 1,030 contacts, 478 had one (46.4 %); the rest get a circle with their initials
  • How often this number has been spoken to before
  • Where the answer came from — every hit states “Source: Odoo”

How fast

250 ms
from ring to name. Measured on 03.09.2026 across 25 numbers, none of which were in the cache — the worst case. Server-side median 223 ms, slowest 242 ms, none above 400 ms.

Those 400 milliseconds are not an arbitrary line: it is the Doherty threshold, beyond which a person stops experiencing a response as immediate. Until 03.09.2026 the same case cost 1,027 ms, because the Outlook address book lookup sat inside the ringing moment; it now happens afterwards and adds the name.

What Odoo has to provide

  • An Odoo account with read access to contacts. A dedicated service account is advisable — then the Odoo log shows the query came from us and not from an employee.
  • Phone numbers on the contacts. Odoo keeps several number fields; we query all of them.
  • Reachability from outside — the query goes to your Odoo address, at the moment of the call.

What it cannot do

This belongs here just as much, and most articles on the subject leave it out:

  • Anyone not in Odoo will not be found through Odoo. A CRM knows customers — not suppliers, authorities, or the tradesman calling for the third time.
  • A withheld number cannot be looked up. Nothing is broken; there was simply nothing to search for.
  • A contact without a number in the record cannot be found by number — even though it is in Odoo.
  • Odoo changes its fields between versions. An outdated field once brought our entire contact search to a halt; the adapter therefore asks the system which fields it has, rather than assuming it knows.

When Odoo does not know the caller

That is what the number book is for. Whatever no CRM holds you enter once yourself — and on the next call the name is there, for everyone in the house.

+28.6 points
is how far the recognition rate rose in one measurement after twenty number book entries had been created. Twenty lines, once.

After the call: the note back into Odoo

When you hang up, a field appears in the tile. What you write goes into Odoo — on the contact, the lead or the ticket, together with the duration and outcome of the call. No button needed; write nothing and nothing happens.

22 notes
have gone from the tile into one customer’s Odoo since 30.08.2026. Not a test run — ordinary calls.

What setting it up needs

Odoo address, database name and the credentials of the service account — stored once in the portal. The portal checks the login immediately and tells you whether it works, instead of you finding out on the first call.

The portal itself — overview, call list and number book — is free, with no limit on the number of workplaces. The Webex tile is billed per user.

Frequently asked questions

How do I see who is calling in Odoo?

Haus iT Caller ID looks the number up in your Odoo while the phone rings and shows company, contact person and customer number in the Webex sidebar. One click opens the record in Odoo. Measured: 250 milliseconds from ring to name.

How many callers are identified?

Measured at one customer over 30 days: 63 per cent of incoming calls. Counted per call rather than per number – per number it would be 33 per cent.

What does Odoo need to provide?

An Odoo account with read access to contacts, phone numbers on those contacts, and reachability from outside. A dedicated service account is advisable so the Odoo log shows the query came from the portal.

Is my customer data copied?

No. The question goes straight to your Odoo at the moment of the call. No copy is created on the operator side, and no call content is processed.

What happens when the caller is not in Odoo?

Then Odoo will not find them – a CRM knows customers, not suppliers or authorities. That is what the number book is for: in one measurement twenty entries raised the recognition rate by 28.6 percentage points.

What does it cost?

The portal with overview, call list and number book is free, with no limit on workplaces. The Webex tile is billed per user per month.

How the tile works All connectors

Talk to us

You will not get an off-the-shelf answer but a clear assessment: whether the effort is worth it for your company, what your system needs to be capable of – and what it costs. If it is not a fit, we say so.