Originally posted by Craig Foley
Hey Guys,
When I use the semantic/embedding search to find jobs with a specific phone number, it hallucinates and returns jobs that appear to have no relationship to the phone number supplied.
There appears to be lots of other search attempts that also return seemingly irrelevant results or a very limited count. (Such as asking for jobs in a particular suburb…you might get back six, when there’s been hundreds in the recent past.)
Not sure what work’s being done on that?
Cheers,
Craig.
Hi Craig,
You’ve identified the issue correctly. The semantic/embedding search functionality is specifically designed for matching jobs with similar context in job descriptions. It’s not intended for matching specific identifiers like phone numbers or customer details, which explains the irrelevant results you’re seeing.
For searching by phone numbers, customer details, or other specific data points, you should use our global search endpoint instead. This will provide accurate results for exact matches like phone numbers and customer information.
For traditional API filtering with exact matches, the ServiceM8 API supports the $filter parameter using operators like eq (equal) for precise field matching. However, for broader search capabilities including phone numbers and customer searches, the global search endpoint is the appropriate tool.
Using the correct search method for your specific use case will resolve the inconsistent results you’ve been experiencing.
Thanks,
Cody