A user asks, 'How do I return an item?' — but the database says 'Refund.' Without semantics, the system stays silent. Our solution: an embedding-based FAQ bot that finds answers even with rephrasing. Over 10 years, we've deployed such bots in 50+ projects — from fintech to e-commerce — and found that embedding search improves accuracy by 40% compared to LIKE queries. If you want similar results, contact us for a consultation.
Why Semantic Search Beats Exact Match
The simple approach: user types keywords, system searches the database via LIKE or Elasticsearch. It works when users know the exact terms. But in reality, people phrase things differently. For natural language questions, you need embedding search. Each FAQ question and each user query is turned into a vector, and we find the nearest neighbor by cosine distance.
from openai import OpenAI import numpy as np client = OpenAI() def embed(text: str) -> list[float]: response = client.embeddings.create( model="text-embedding-3-small", input=text ) return response.data[0].embedding def find_best_faq(query: str, faq_embeddings: dict) -> tuple[str, float]: query_vec = np.array(embed(query)) best_score = -1 best_key = None for key, vec in faq_embeddings.items(): score = np.dot(query_vec, np.array(vec)) / ( np.linalg.norm(query_vec) * np.linalg.norm(np.array(vec)) ) if score > best_score: best_score = score best_key = key return best_key, best_score A threshold of score < 0.75 means the bot responds: "Couldn't find a suitable answer; please clarify." Without a threshold, the bot confidently returns irrelevant answers.
How We Build a High-Accuracy FAQ Base
Each record includes: question (or multiple phrasings), answer, category, tags. Multiple phrasings for one question improve recall during search. Embeddings for the FAQ are computed once on load and cached in Redis. When the database is updated, we invalidate the cache and recalculate. This reduces API load and speeds up responses to 50 ms.
Caching Architecture
Redis stores precomputed embeddings and hot queries. We set a TTL for each key — typically 24 hours. When the database changes, keys are invalidated via publish/subscribe. This keeps data fresh without server restarts. For the embedding model, we use OpenAI's text-embedding-3-small with dimension 1536. Experimentally, a cosine distance threshold of 0.75 gives the best precision/recall balance for typical FAQs.
Comparison of Search Approaches
| Method | Precision | Speed | Implementation Complexity |
|---|---|---|---|
| LIKE queries | 30–50% | ~10 ms | Low |
| Elasticsearch (full-text) | 60–70% | ~20 ms | Medium |
| Embedding (semantic) | 85–95% | ~50–100 ms | High |
Embedding search delivers 40% more relevant answers than LIKE and 25% better than Elasticsearch. For a business, this means 40% faster response times and reduced support load, yielding up to 30% operational cost savings. We recommend it for any bot with more than 50 questions.
Want to implement semantic search? Write to us, and we'll find the optimal solution for your business.
Mobile UI: Categories and Free Input
An effective FAQ bot combines category buttons at the start of the conversation with free input. User opens the chat → sees 4–6 categories ("Delivery", "Payment", "Returns", "Account") → taps one → bot offers top 3 questions in that category as chips. If none fits, the user types their own words.
This UX reduces NLP load and gives the user structure. In practice, 70% of users find an answer in 2–3 taps without typing a word. A "Was this helpful?" button below each answer is mandatory. Negative feedback forms a list for database refinement.
FAQ Bot Development Stages
| Stage | Duration | What We Do |
|---|---|---|
| Analytics | 1–2 days | Collect real user questions from support tickets, categorize, prioritize |
| Design | 1 day | Data architecture, embedding model selection, relevance threshold tuning |
| Development | 2–4 days | Server side (Python API), mobile UI with categories and chips, Redis cache integration |
| Testing | 1–2 days | A/B test with real users, measure answer hit rate |
| Deployment | 1 day | Publish to App Store and Google Play, configure analytics (Firebase) |
What's Included?
We provide full integration documentation, training for your team, and 3 months of warranty support. This ensures a quick launch and minimized risks. Ultimately, you get:
- FAQ database formation (up to 200 questions)
- Embedding model and threshold configuration
- UI development (categories, chips, history)
- Redis caching integration
- Unanswered query analytics
- Documentation and team training
Timelines and Cost
FAQ bot with semantic search on an existing base — 2–4 days. With database structure development, categorization, and analytics — up to 1 week. Our team has 10+ years of mobile development experience and has completed over 50 chatbot projects. We guarantee quality and post-launch support. Every project is unique: final timeline and cost are determined after auditing your data. Get a consultation — write to us, and we'll assess your project end to end.