Skip to content
Woyce AI
AboutTeamBlogCareersContactStart a project →

OmniAI Chatbot,
Omnichannel AI chatbot deployable across web, WhatsApp, and SMS

OmniAI Chatbot — AI Case Study

Fully customisable omnichannel AI chatbot that deploys across web, WhatsApp, SMS, and email with unified conversation history.

Client
Woyce
AI
Engagement
Design + Build
Full delivery
Year
2024
Delivered
Team
Woyce
5 disciplines
Stack
React.js · Node.js
+ 5 more
Status
● Live
In production
🔒 app.woyce.ai/omni-ai-chatbot
OmniAI Chatbot – 1
OmniAI Chatbot – 2
Omni
01 / 02
The outcomes

Three numbers that
tell the story upfront.

01Channel integrations
8

Channel integrations

Fully customisable omnichannel AI chatbot that deploys across web, WhatsApp, SMS, and email with unified conversation hi…

02Messages handled
200k+

Messages handled monthly

Fully customisable omnichannel AI chatbot that deploys across web, WhatsApp, SMS, and email with unified conversation hi…

03First-bot-resolution rate
65%

First-bot-resolution rate

Fully customisable omnichannel AI chatbot that deploys across web, WhatsApp, SMS, and email with unified conversation hi…

Want the full story? Keep scrolling for the problem we solved, what we built, and the results it delivered.
03 / 05
The problem

Before we got here,
here's what wasn't working.

OmniAI Chatbot is a white-label conversational AI platform that businesses embed across every customer touchpoint. A single bot configuration runs consistently across web widgets, WhatsApp Business, SMS, and email, with all conversations unified in one inbox.

“WhatsApp Business API 24-hour messaging window restrictions”
— A core challenge we solved

We confirmed every challenge with the team before writing a line of production code. The right column lists the pain points we tackled head-on and how we approached each one.

What wasn't working

BEFORE

WhatsApp Business API 24-hour messaging window restrictions

Implemented proactive notification templates pre-approved via Meta Business Manager to re-engage users after the window expires.

#1
What they came to us with“We need this solved. Can you help?”
03b / 05
Our approach

Don't over-engineer.
Solve what matters, ship fast.

The instinct on complex projects is to rebuild everything from scratch. We pushed back. A full rewrite often means months of regressions while engineering rebuilds features that were already working.

We mapped the existing workflow against actual usage. The result was clear: a small set of features accounted for the majority of user time. We rebuilt the core, shipped fast, and extended outward.

Operating principleSolve the highest-leverage problems first. Validate before building. Ship a v1 that proves the concept, then iterate — rather than waiting for a perfect v1 that never ships.

On the technical side, we made clear decisions early and held them. The right column shows what we chose, and why.

4 decisions we made early

CHOSEN / REJECTED
Decision 01

Channel-agnostic Bot Engine — how we built it

Chose

Custom Channel-agnostic Bot Engine — built for this product's exact needs and data model.

Rejected

Generic SaaS tool that would require heavy workarounds and compromise the user experience.

Decision 02

Unified Inbox — how we built it

Chose

Custom Unified Inbox — built for this product's exact needs and data model.

Rejected

Generic SaaS tool that would require heavy workarounds and compromise the user experience.

Decision 03

Bot Builder (No-code) — how we built it

Chose

Custom Bot Builder (No-code) — built for this product's exact needs and data model.

Rejected

Generic SaaS tool that would require heavy workarounds and compromise the user experience.

Decision 04

Live Agent Escalation — how we built it

Chose

Custom Live Agent Escalation — built for this product's exact needs and data model.

Rejected

Generic SaaS tool that would require heavy workarounds and compromise the user experience.

04 / 05
What we built

4 features that
define the product experience.

Every feature was scoped and shipped with the same priorities: speed, reliability, and staying out of the user's way.

AI/Channel-agnostic Bot Engine
Channel-agnostic Bot Engine
Channel-agnosticActive
BotRunning
EngineReady
8 — Channel integrations
FEATURE 01

Channel-agnostic Bot Engine

A single bot logic layer that adapts its output format to the target channel (web, WhatsApp, SMS, email).

8Channel integrations
AI/Unified Inbox
Unified Inbox
UnifiedActive
InboxRunning
LayerReady
200k+ — Messages handled monthly
FEATURE 02

Unified Inbox

All conversations across channels appear in one inbox with full history, labels, and CRM sync.

200k+Messages handled monthly
AI/Bot Builder (No-code)
Bot Builder (No-code)
BotActive
BuilderRunning
(No-code)Ready
65% — First-bot-resolution rate
FEATURE 03

Bot Builder (No-code)

Drag-and-drop flow builder for creating conversation paths with conditional branching.

65%First-bot-resolution rate
AI/Live Agent Escalation
Live Agent Escalation
LiveActive
AgentRunning
EscalationReady
FEATURE 04

Live Agent Escalation

Seamless transfer to a human agent with full bot conversation context.

05 / 05
The outcome

What changed,
measured against the day-one baseline.

We benchmark before we touch anything, logging every metric below against its state before we wrote a line of production code.

Metric
Baseline
After Woyce
Channel integrationsOmniAI Chatbot · AI
Legacy
8
Messages handled monthlyOmniAI Chatbot · AI
Legacy
200k+
First-bot-resolution rateOmniAI Chatbot · AI
Legacy
65%
Start a project

Want to build
something like this?

We ship fast. Talk to us about your product idea and we'll tell you exactly how we'd approach it.

Book a call →See more work