Unify website chat, Telegram personal accounts and bots in a single realtime workspace. An AI assistant powered by OpenAI API supports knowledge-grounded responses, while your team takes over complex conversations instantly.
Combining OpenAI API-powered customer assistance and RAG with distributed .NET 10 services, Redis caching, MongoDB and real-time messaging infrastructure.
Single unified inbox for Web Embed Widgets, Telegram Personal accounts (MTProto worker with gap-filling & rate-limit auto-healing), and official Telegram Bots.
The current AI assistant uses OpenAI API with RAG-based knowledge retrieval and structured tool actions. Grounded context and review controls help reduce unsupported answers.
Seamless transition between AI and human agents. CAS distributed locks prevent race conditions, with least-busy & random tie-break distribution.
Two-way voice message transcoding (OGG/Opus <-> MP3/WAV), progressive high-res photos, video streaming with HTTP byte-range forwarders.
On-demand summaries of long threads, intent extraction, sentiment analysis and shift-handover briefs using the current AI assistant integration.
Full-featured management portal with live heartbeat tracking, dynamic department filtering, real-time audio waveform visualizer, and audit logs.
OmniPulse currently uses OpenAI API for its AI Assistant and RAG-powered knowledge retrieval. The surrounding routing, persistence, media and human-handoff infrastructure is operated by our own services. We are evaluating Claude API as a potential future integration.
High-performance distributed system engineered for low latency, zero data loss, and seamless AI-to-human workflows.
Web Widget (iframe), Telegram MTProto workers, and Telegram Cloud Bot ingest conversations.
Distributed .NET 10 WebSockets gateway parses intents, checks RBAC, and applies Redis locks.
The OpenAI API-based assistant uses retrieved knowledge, streams replies, and may request the handoff_to_staff action.
Atomic CAS updates in MongoDB, MinIO media object stores, and automated summary generators.
Compare the OmniPulse workflow with fragmented manual processes and basic rule-driven automation.
| Core Capability | OmniPulse AI | Fragmented support setup | Basic rule-based bot |
|---|---|---|---|
| AI Engine & Reasoning | ✓ OpenAI API assistant + RAG | AI available via separate integrations | Fixed conversational rules |
| Telegram Integration | ✓ MTProto Personal Accounts + Official Bots | Channel support depends on integrations | Channel-dependent |
| Human-AI Handoff | ✓ Zero-wait CAS atomic handoff + Stream cancel | Often requires separate escalation tools | Escalation requires explicit setup |
| Rich Multimodal Media | ✓ Two-way voice transcoding, video byte-range | Media flows vary by tool | Often limited by bot implementation |
| Vietnamese & Asian Language Nuance | ✓ AI-assisted multilingual replies | Translation is tool-dependent | Intent handling depends on rules |
| Architecture Ownership & On-Prem | ✓ Full Docker/K8s deployment ready | Deployment depends on vendor | Varies |
See how OmniPulse combines web chat, Telegram, AI-assisted replies and seamless human takeover. Contact the LongKhang team to discuss an integration, deployment or product walkthrough.
Everything you need to know about our technical setup and roadmap.
OmniPulse currently runs its RAG-powered AI Assistant on OpenAI API. We are exploring an optional Claude API integration for future workflows; the current website does not represent Claude as deployed.
Our Telegram worker implements durable state tracking with exponential backoff and randomized jitter (FLOOD_WAIT 420 handler) persisted directly in MongoDB and RAM to reduce flood-limit disruptions and protect account sessions.
When the AI Assistant identifies a request needing a human, it invokes the structured handoff action. Our CAS distribution algorithm assigns the ticket to the least-busy active staff member while instantly terminating active AI token streams.
Yes. All backend services (.NET 10 API, SignalR nodes, worker daemons, React frontends) are containerized with Docker and deployable onto private Kubernetes clusters with MinIO and Redis caching.