heydiga

Identify

Recognises the caller and pulls up their history before saying anything.

"Could you tell me your name again?"

A customer of ten years who has to explain who they are does not feel like a customer of ten years.

Whoever answers does not know who they are talking to until they ask, and by then half a minute and some goodwill are gone. Finding the record takes a while longer: you have to leave the phone, open the software, type the surname and choose between three that look alike. Meanwhile the customer repeats a history that is already written on the screen.

It knows who it is talking to before saying hello

The phone number is already a piece of information. It just has to be used before the first sentence.

  • It recognises the incoming number and finds the customer's record.
  • It brings up their history: last visit, last purchase, what is outstanding.
  • It greets them by name instead of asking them to introduce themselves.
  • It asks about what they have open, with no need to explain it.
  • It checks with a second detail when what is asked for is sensitive.
  • It treats a first-time caller as exactly that: somebody new.

Where the customer record lives

No database has to be built: the one you have is the one it uses. What gets defined is how far what can be said over the phone goes.

What it needs
The databaseThe software where customers and their phone numbers already live: CRM, records or calendar.
The historyWhat is worth recalling on a call: last visit, purchase, open ticket.
The verificationWhich second detail is asked for when what is being looked up is personal.
The limitWhat can be said over the phone and what only in person.

A conversation that starts halfway through

Recognising someone is not a courtesy: it saves the usual minute and gets things right more often.

  • The customer recognised before the first sentence.
  • Their history at hand, without them having to tell it.
  • The appointment or the open ticket, on the table from the start.
  • The details that already exist, neither asked for nor typed again.
  • Personal information that only comes out after checking who is on the line.

Right at the beginning

Identify is not visible on the page: it shows in the rest of the conversation going faster.

It recognises the patient and offers a time with their usual professional.
It knows which appointment is open for whoever calls back.
It tells a long-standing customer from a new enquiry, and does not mix them up.
It passes the call with the record in front of whoever takes it.
It knows what they bought and when before they say it.

Where the limits are

We say it here so nobody discovers it in a demo. Recognising a number is not the same as assuming who is calling.

  • It does not hand over anything personal on the number alone. If the matter is sensitive, it checks first.
  • It does not recognise who is not there. If the number is not on file, it treats them as somebody new.
  • It does not know who is holding the phone. A shared mobile at home belongs to the household, not to one person.
  • It does not fix your database. If there are two records for the same customer, it will see two.
  • It does not decide what can be said. You set that limit and it respects it.

What everybody asks

The five doubts of anyone handling customer data over the phone.

Try it with your own database

It connects to the software you already use and the next call starts with a name.

Servers in the European UnionGDPR complianceENS medium category (RD 311/2022)ISO 27001Data encryption and anonymisation

© 2026 heydiga · Barcelona · Madrid