Member-only story
A Siebel developer’s honest walkthrough of Retrieval-Augmented Generation in service request search — what it fixes, how the OpenSearch vector pipeline works, and where the gaps still are. #
Here’s a scenario every Siebel-supported help desk has lived through. A customer types: “the app freezes right after I log in.” Three months earlier, a different customer typed: “system hangs before the dashboard loads.” Same root cause. Same fix, probably. And under the keyword search that most of us have relied on for two decades, these two service requests never meet each other. One rep solves the problem, writes it up, closes the ticket — and the next rep starts from zero, because the search box only understands the words you typed, not what you meant.
I’ve spent enough time inside Siebel service request queues to know how much of a support rep’s day actually goes into re-solving problems that were already solved, just phrased differently. It’s not a training issue. It’s not a documentation issue. It’s a search issue — and it’s exactly the kind of problem I flagged when Siebel 26.6 dropped as the release worth paying attention to. One of the headline…