OyeChats
Start free
FeaturesSolutionsIntegrationsPricingDocsCase studiesBlogContact us
Sign inStart free

What's new in OyeChats.

Product updates for the OyeChats platform, widget, and dashboard: new features, improvements, and fixes as they ship.

FixedAnswer quality

Fixed: answers could come back empty on small knowledge bases

A chatbot could reply that it did not know something while the answer sat in its knowledge base. The cause was our shared vector index: as the total number of customers grew, searches scoped to one workspace were drawn from a candidate set dominated by everyone else’s content and discarded, returning nothing. Silently, with no error to alert us. Smaller knowledge bases were hit hardest, which is most of them. Retrieval now runs an exact, workspace-scoped search: every matching passage is found, every time, and it is faster at today’s sizes. A 5,000-chunk knowledge base searches in under 8ms. No action needed, and nothing was lost; the content was always there.

Updated byGauravGaurav
#retrieval-recall-fix
ImprovedPerformance

Chat stays responsive when a lot of visitors arrive at once

Two changes to how a chat request uses the database. Billing and subscription checks no longer block while they run, and a database connection is now released for the whole time we are searching your knowledge base and generating a reply rather than being held end to end. Together they take the ceiling off how many conversations can be in flight at the same time, so a traffic spike on one site no longer slows replies for everyone. Nothing to configure.

Updated bySteveSteve
#chat-concurrency
New featureLeads

OyeChats now knows the company behind every conversation

Visitor & Company Intelligence resolves the business behind a chat from the visitor’s own domain, resolving it once per session and caching it across the platform so repeat lookups are free. Company details appear right in the lead record, kept separate from network context we never mistake for the company itself. Turn it on per agent, and you’re only charged when we actually return a match.

Updated bySteveSteve&GauravGaurav
#company-intelligence
New featureLead capture

Verified email capture keeps junk leads out of your CRM

Every email a visitor submits is now verified in real time before the lead is saved, so mistyped and disposable addresses never reach your pipeline. Deliverability checks run server-side at the moment of capture on Standard and Professional plans, keeping your lead list clean and your follow-ups landing.

Updated byGauravGaurav
#verified-email-capture
New featureKnowledge base

Auto-recrawl keeps your knowledge base fresh, automatically

Standard-tier bots now refresh their knowledge base on a schedule. Point OyeChats at a URL once and we re-crawl it in the background whenever your docs, product pages, or pricing change. No more stale answers, no more manual re-uploads.

Updated bySteveSteve
#auto-recrawl
ImprovedCrawler

The crawler now understands YouTube and linked downloadables

Point OyeChats at any page and it pulls in YouTube transcripts and linked PDFs, DOCX, and TXT files inline with the source. One URL, one crawl, richer context, more accurate answers.

Updated byGauravGaurav
#crawler-youtube-docs
New featureBilling

Billing moves into its own tab, with the right currency from day one

Billing is now a dedicated tab, decoupled from account settings. We capture your billing country at signup and every price you see (seats, plans, top-ups, invoices) renders in your local currency from the very first load.

Updated byGauravGaurav
#billing-tab
ImprovedBilling

A global currency context, everywhere at once

The seat modal, plan picker, top-up flow, and invoices all read from a single CurrencyContext now. Switch billing country and every price in the app updates instantly. No reloads, no mismatched totals at checkout.

Updated bySteveSteve
#currency-context
SecurityImproved

A quiet security pass across the whole platform

Centralized SSRF guard on the crawler and demo preview. Non-root systemd services with unit-level sandboxing. CI actions pinned to commit SHAs. API docs gated in production, WebSocket file events rate-limited, and web push with a hard timeout. Nothing you have to configure. It just runs safer.

Updated byGauravGaurav
#security-hardening
FixedSecurity

Strict auth on every account-credential endpoint

The /settings, /upload-logo, and account-credential endpoints now require a valid X-API-Key. No more soft auth paths. Live-chat sessions restored from the database are correctly tenant-scoped on reconnect, and operator presence has a database fallback when Redis is down.

Updated byGauravGaurav
#auth-hardening
New featureLive chat

Live chat handoff, now generally available

Visitors can hand off from the bot to a real human at any point, with department routing, canned responses, and a post-chat rating. Operator presence is Redis-backed with automatic database fallback, so nobody drops off the queue when infrastructure hiccups.

Updated bySteveSteve
#live-chat-ga
ImprovedInfrastructure

Auto-rollback on failed post-deploy health checks

A bad release no longer needs a human in the loop. If a deploy fails its health check, the API rolls back to the previous known-good release automatically. Renewal cron and invoice-email workers isolate per-record failures so one bad account never stalls the batch.

Updated byGauravGaurav
#auto-rollback
New featureAnalytics

BANT scoring, built into every conversation

OyeChats now scores every conversation on Budget, Authority, Need, and Timeline, automatically. Combined with visitor context (pages viewed, return visits, UTM, device), sales sees a qualified lead the moment intent shows up, without asking a single form question.

Updated byGauravGaurav
#bant-scoring