Answers
Find a person sits at the top of the sidebar, so it is there on every page, and on a phone it is the magnifier in the bar at the top of the screen. Press it and the search opens over whatever you were reading. Type at least two characters of a name or an email, or at least four digits of a phone number, in any format your fingers produce. (727) 555-0142, 727 555 0142, and 5550142 all find the same person, because we match on the digits and ignore the decoration. The last seven digits work on their own, since the country code is the part everybody leaves off when typing from memory.
People. Up to twelve of them, each with the detail that matched underneath the name, so you can see why a result is there rather than guess. Name matches come first, then email, then phone, because somebody typing letters is looking for a person and an email that happens to contain those letters is the weaker answer.
It reads your contacts, all of them, not only the ones inside the date range you happened to be looking at. That is the part worth knowing: a customer who last bought in 2019 is still two characters away.
A result opens that person's own page. Overview first, then Journey and Attribution, then Revenue, Calls and Meetings when there is something in them. An empty tab would only teach you that the tabs here are decoration, so they do not appear empty.
The Journey is the one with no equivalent anywhere else. First touch, the moment they became a contact in your CRM, every call, every meeting, every payment, and the conversion we reported back to Google or Meta, all merged into one list with the newest at the top and the gap between each step written beside it. Where that gap cannot honestly be known, because one end has a date and no clock, it says days rather than inventing hours.
And it still ends at ids. The contact id sits on the page with a button to copy it, every payment carries the record id of the order behind it, and every call carries the id you can paste into your call platform. Every trail ends at something you can look up in the system that owns it, which is the difference between us asserting a number and you being able to check it.
Two contact records sharing an email or a phone number are probably one human wearing two records, and we say so where we can see it. Open a record from a dashboard drill down and a Possible duplicates section lists the siblings, what they share, and which one to keep (the one holding the money, or failing that the older one). Ask the AI about the person and it reports the same thing, with the ids. The search box itself does not flag them, so a name appearing twice in the results is worth a second look.
What we will not do is pretend to merge them. No CRM exposes a merge API, and we checked rather than assumed, so the merge happens inside your CRM's own screens. We hand you the ids, the recommendation, and the reason; your CRM does the surgery it alone is allowed to do, and the next data refresh picks up the result. Detection sticks to email and phone on purpose: two different people really are named John Smith, and a wrong duplicate flag on a real customer is worse than a missed one on a messy record.
It searches people: every contact we hold for you, by name, by email address, and by phone number. It does not search your orders, your call log, or your meetings, so you cannot reach somebody by invoice number here. Open the person and their calls, meetings and payments are all on their page. The box is just not the door into them.
The honest gap is a caller your CRM has never heard of. They really did phone you, and until a contact record carries that number the search will not find them. If you run Call Tracking, that call is still on your Call Tracking page with the number on it, which is where to look until they become a contact.
Ask the assistant about the same person and you get more than the box gives you: their calls, their bookings, what they have paid, and any contact records that look like duplicates of them. The two read different things on purpose. The box reads your contact store, so it reaches everybody, including the customer who last bought years ago. The assistant reads your built report, so it reaches those other systems but only as far back as that report goes. If the two ever disagree about whether somebody exists, that is why, and the person's own page is the one to trust for who they are.