Right now we can use the quick search to search for contacts, companies, orders opportunities, tasks, subscriptions and affiliates. For contacts it’s super helpful that you can send just a partial contact name to search to pull up a list of contacts starting with that name. Phone numbers also work better in the quick search. Right now unless you’re going to expand all the filters or search abilities to not force a equals for the searching right now you have to type the entire first name. Also on the phone fields searching this is another thing that is frustrating that we have to query the whole phone number and have it formatted however it might be inside Keap which could be many different ways. Why can’t we just pass the E.164 formatted number and on your end you query the potential formats?
Mainly wondering if either the quick search is coming in V2 or search with wildcards is coming?
Hi @Dustin_Lunt. Really appreciate you sharing this.
I’ll make sure to bring this feedback up internally. We’re currently working on expanding filtering capabilities across most of our list endpoints, including adding support for more flexible options like wildcard filtering wherever it’s feasible.
Your points about partial name matching and phone number normalization (like accepting E.164 format regardless of how it’s stored) are spot on, and I’ll make sure those are included in the conversation.
I don’t have a specific timeline to share yet around a Quick Search V2, but this is something the team is looking into.