The phone rings and Webex shows a bare number. Sometimes a name that is wrong. Sometimes something that looks like half an e-mail address. The question is always the same: why now of all times?
The answer is in Cisco's own description, and it is more precise than you would expect. It also explains the case nobody suspects: that too much in the address book can lead to nothing at all being shown.
Where Webex Calling takes the name from
The Webex app matches the incoming number against contacts – not against one source, but three, in a fixed order:
- Webex Common Identity – the identities of your own organisation
- Personal and organisation contacts
- The local address book on the computer
Two cases in which nothing at all appears
The first is the expected one: the number is in none of the three sources. Then there is nothing to look up.
The second is a surprise. If the app finds several entries with the same number in one source, it picks none of them. Cisco writes: “In this case no caller ID is displayed.”
What is shown instead
Without a match the app falls back to the display name in the SIP header, if one is sent. If that is empty too, it uses the user name part of the SIP address as a last resort.
That is where those strings come from that look like half an e-mail address. They are not a fault but the last step of a chain that found nothing before.
Where this chain reaches its limit
All three sources are contact lists. A customer base is not a contact list. A trade business with four thousand customers does not keep them in an address book, and it should not: address books are meant for people you speak to regularly.
So “no name” when a customer calls is not the exception but the normal case – regardless of how well your phone system is set up. The chain works exactly as described. It only looks in places where your customers are not.
What we change about it
Haus iT Caller ID puts a fourth source in front: your own CRM or ERP. At the moment the phone rings it is asked with one number and one name comes back – depending on the system with company and customer number. No copy of your customer base is created and no extra entry in the address book.
And the honest limit: whoever is not in your CRM will not be found this way either. For suppliers, tradespeople and public offices no lookup helps, only a directory of your own – or the insight that a bare number is sometimes the right answer.
Frequently asked questions
Why does Webex Calling sometimes show no name?
Because the number is in none of the three sources the Webex app searches: Webex Common Identity, personal and organisation contacts, local address book. A customer base belongs in none of them.
Why does the name disappear when a contact exists twice?
If the app finds several entries with the same number in one source, it picks none and shows no caller ID at all. A duplicate entry is therefore worse than none.
What does the string that looks like an e-mail address mean?
That is the last fallback: the user name part of the SIP address. It appears when neither a contact was found nor a display name came with the SIP header.
Does it help to import all customers into the Webex address book?
Rarely. The data is current on the day of the import and never again, duplicate entries make the display disappear entirely, and a copy of your customer base then sits in a second place.
In which order does the Webex app search?
Webex Common Identity, then personal and organisation contacts, then the local address book. The search stops at the first match.
Does the telephony provider change anything about this chain?
No. The order belongs to the Webex app and applies regardless of who supplies the line.