When to use conversational vs traditional search
Use conversational search when:- Users need easy-to-read answers to specific questions
- You are handling informational-dense content, such as knowledge bases
- Natural language interaction improves user experience
- Users need to browse multiple options, such as an ecommerce website
- Approximate answers are not acceptable
- Your users need very quick responses
Conversational search is still in early development. Conversational agents may occasionally hallucinate inaccurate and misleading information, so it is important to closely monitor it in production environments.
Conversational search user workflow
Traditional search workflow
- User enters keywords
- Meilisearch returns matching documents
- User reviews results to find answers
Conversational search workflow
- User asks a question in natural language
- Meilisearch retrieves relevant documents
- AI generates a direct answer based on those documents
Implementation strategies
Retrieval Augmented Generation (RAG)
In the majority of cases, you should use the/chats
route to build a Retrieval Augmented Generation (RAG) pipeline. RAGs excel when working with unstructured data and emphasise high-quality responses.
Meilisearch’s chat completions API consolidates RAG creation into a single process:
- Query understanding: automatically transforms questions into search parameters
- Hybrid retrieval: combines keyword and semantic search for better relevancy
- Answer generation: uses your chosen LLM to generate responses
- Context management: maintains conversation history by constantly pushing the full conversation to the dedicated tool