When someone rings about a booking they made three weeks ago, the AI can now find their record from the number they are calling on and answer from it, rather than telling a regular customer it has nothing on file. It only ever discusses the caller’s own records.
What changed
Caller history lets the receptionist answer an enquiry using the customer records already held. A returning caller asking about an earlier booking should not have to be treated as though the business has never heard from them.
The phone number supplied with the incoming call helps locate the customer and their related activity. This makes the stored history useful during a conversation rather than only to a staff member searching the dashboard.
Before and after
Before this update: A regular customer could be told that no record was available even when the business already held the relevant booking or enquiry.
With this update: The receptionist can find a customer from the number they call on and use the matching history to help with their enquiry.
What it means for you
Keep customer phone numbers and records up to date, then review transcripts for returning-customer enquiries. The useful comparison is whether the answer reflects the correct stored record, not simply whether the caller is greeted warmly.
The assistant should discuss only the caller’s own records, with the required identity checks. A recognised number helps locate context; it does not justify reading another customer’s details.