01↘
KnowledgeRetrievalDiagnostics
Answers grounded in approved knowledge
Bring together text, files and website material so the assistant can retrieve tenant-scoped facts instead of improvising business answers.
Knowledge ingestion, crawling and retrieval diagnostics help the team see what was found, where coverage is thin and when the assistant should fall back.
In practiceAn accounting practice can answer questions about its services, price ranges and contact details from approved material, while a tax-advice request moves to an accountant.
Control pointLow-confidence or unsupported business facts should trigger clarification or human handoff, not a confident invention.
See the complete use case02↘
Flow BuilderToolsSimulation
Guided journeys and controlled tools
Use Flow Builder for predictable conversation paths and connect approved tools when a customer needs an action, not only an answer.
Teams can design, simulate and publish deterministic flows, then define which tools are required, recommended or unavailable for a given intent.
In practiceA consultation request can collect the right details, check availability through a configured calendar and prepare a booking without letting the model invent the process.
Control pointSensitive or consequential actions stay behind explicit tool rules, approvals and tested fallback paths.
See the complete use case03↘
WebchatTelegramWhatsApp
One service logic across supported channels
Webchat, Telegram and WhatsApp can use the same approved knowledge, flows and handoff rules while respecting the language of the latest customer question.
Channel adapters keep the tenant and bot context attached to each inbound message, while localized bot-authored replies and visible controls follow the customer language.
In practiceA multi-location service business can answer opening-hours questions on webchat and continue the same service approach on an approved messaging channel.
Control pointA channel is presented as live only after its tenant configuration and provider-acceptance checks are complete.
See the complete use case04↘
Live ChatQueueHandoff
Human handoff with the conversation intact
Move exceptions into Live Chat so an operator can take ownership without asking the customer to start again.
The operational workspace supports a queue, assignment, transfer, internal notes, conversation summaries, presence and follow-up.
In practiceA retailer can let Zbori handle product discovery, then transfer a complaint or uncertain stock question to the right person with the preceding context.
Control pointProfessional advice, complaints and ambiguous requests can be routed to a person according to tenant-specific handoff rules.
See the complete use case05↘
CatalogHybrid searchRetail Launch
Catalog-aware product discovery
When a catalog is configured, Zbori can search structured product data alongside business knowledge and guide a more useful shopping conversation.
Catalog CRUD, file or feed imports, hybrid search, comparisons, readiness checks, product gaps and Retail Launch support a focused retail setup.
In practiceA customer can ask for a laptop by use case and budget, compare suitable products, or receive a useful fallback when the catalog has no confident result.
Control pointPrices, availability and product facts are only as current as the approved catalog source and should be qualified or handed off when uncertain.
See the complete use case06↘
BranchesDirectionsLocal context
Local branch and direction assistance
Help customers find the nearest suitable location from an address, street or familiar landmark when branch data and mapping are configured.
Zbori can resolve a typed customer origin, use known conversation locality when needed and return a route only when a viable map match exists.
In practiceA visitor can ask which branch is closest to a Podgorica landmark and receive a practical route to the configured location.
Control pointLive directions remain conditional on valid branch data, one confident map match and completed mapping-provider acceptance.
See the complete use case07↘
CalendarEmailApproved actions
Integrations that serve a real workflow
Connect calendar, email, Sheets, payments, social or growth tooling only when the tenant journey has a clear operational reason for it.
Configured integrations and tool health surfaces let administrators connect actions to flows while keeping external credentials and approvals outside the public experience.
In practiceA service team can offer an available consultation slot, prepare a follow-up email or record an approved lead step after the customer has chosen to continue.
Control pointExternal actions depend on tenant configuration, provider readiness and any required human or spend approval.
See the complete use case08↘
SessionsAnalyticsReliability
Conversation insight and reliability signals
Use sessions, analytics, reliability and usage views to see where customers get stuck and which knowledge or flow deserves attention.
Conversation logs, handoff patterns, retrieval diagnostics, quality signals and product gaps turn real questions into a focused improvement queue.
In practiceA retailer can spot repeated no-result searches, while a professional-services team can find questions that regularly need a person or a better source.
Control pointOperational dashboards guide review; they do not replace provider acceptance, professional judgment or evidence for public outcome claims.
See the complete use case