When searching for contacts, phone numbers, etc. the exact entry does not necessarily need to be made (phone can be 1234567890 not 123-456-7890). For exampe, obrien finds O’Brien and O’Brian except it seems “o” anything else does not work (oconnor, olaughlin, odonnel, osullivan, etc. find nobody). O’Connor finds them along wtih O’Donnel, O’Sullivan, and so on. Odly enough O’Maley finds O’Laughlin (we don’t have an O’Maley) but olaughlin finds nothing. If O’Maley can find O’Laughlin then certianly the search engine can be tweaked so that olaughlin finds O’Laughlin.
Agree with @MMahan - We need to have a fuzzy search as we have phone numbers in multiple formats, only current workaround is to skip some numbers.
i.e. Contact record contains number as +61 412 345 678, and if you search 0412 345 678 it will yeild no results, however if you search 412 345 678 it will find the contact record
Our sales reps are asking for a fuzzier search as well. They find the existing search to be too exacting with its results. In particular, they would like to be able to copy/paste a website domain into the search to see if we already have a company in our database. But if they include a slash character at the end of the domain or if they include the “https://” at the beginning, the search returns nothing. If they exclude the slash, they get a result back. It would be helpful if the search was a little bit smarter and could make some educated guesses in these kinds of situations.
Hi @MMahan , are you searching in the Contacts page or in the Global Search (Search icon in the top right)?
I second the issue and have the same question: what are ways to fuzzy search over multiple HubDB columns?
@MMahan This sounds like a search normalization issue. The search should ideally treat names consistently whether the apostrophe is included or not, so entries like “olaughlin” and “O’Laughlin” return the same results. Several lead to account matching tools like LeadAngel, Chili Piper could potentially help with this by handling name variations and matching logic more consistently, depending on where the current search is being performed.