Omnichannel
Unified messaging inbox
2026 — present
MENA
React • TypeScript • Tailwind CSS

A messaging workspace that brings website chat, WhatsApp, Instagram and Messenger into one inbox, and connects those conversations to CRM records and Desk tickets.
Ressan's role
Full-stack product engineering
Capabilities
Industry
SaaS & StartupsSystem state
In production · running now
What was built
- A shared inbox with conversation history, internal notes and bulk actions
- A website chat widget and integrations for WhatsApp, Instagram and Messenger
- Agent availability, skills-based routing and queue management
- Visitor and company profiles with identity matching and scoring
- WhatsApp templates, broadcasts and campaign-management flows
- CRM record linking and conversion of conversations into Desk tickets
Evidence
No sourced metric on this project.
We shipped this system, but we do not have a measurement we can attribute to it. Rather than estimate a percentage, here is the scope in full — which is a claim you can check with the client.
Delivered
2026 — present
Engagement window recorded for this system.
Surface area
6 modules
Distinct things built, listed on this page.
Stack
15 technologies
Taken from the project's own dependency manifest.
01
The problem
Customer conversations arrive on several channels, so context, ownership and the path into sales or support are easy to lose.
02
The approach
Brought the channels into one conversation system with real-time updates, shared customer profiles and configurable routing.
03
The outcome
One inbox for website chat, WhatsApp, Instagram and Messenger, with a path from a conversation into a CRM record or a Desk ticket.
Technology
The stack as shipped.
- React
- TypeScript
- Tailwind CSS
- TanStack Query
- Zustand
- Nx
- Vite
- C#
- .NET 10
- PostgreSQL
- Redis
- Kafka
- SignalR
- Meta messaging APIs
- Docker
Related