The product goal
The platform needed to turn WhatsApp into a structured customer-engagement channel without losing the speed and familiarity of a normal conversation.
It also needed an operator-facing product around the conversation layer: authentication, role-based access, templates, analytics, payments, rate limiting, and administrative controls.
Platform architecture
- Next.js and TypeScript application layer with PostgreSQL, Prisma, Supabase, and Redis.
- Meta Cloud API integration with HMAC-validated webhooks, message templates, and interactive replies.
- Role-based access control for administrative and operational workflows.
- Rate limiting, spam detection, analytics, and payment-related application flows.
AI concierge
The concierge combined Gemini with search grounding and vision input. Requests were classified into more than forty intent categories so the system could select an appropriate structured flow instead of treating every message as an open-ended prompt.
English and Arabic experiences were designed together, including right-to-left interface behaviour and location-aware recommendations.
Risk controls
- Webhook signatures are validated before events enter the application workflow.
- Rate limits and spam checks protect the conversation layer from uncontrolled traffic.
- Structured flows handle deterministic actions; model responses are used where interpretation adds value.
- Administrative permissions are separated through role-based access control.
Result
The result was a working end-to-end product rather than a standalone chatbot: inbound WhatsApp events, application logic, AI interpretation, bilingual user experience, administration, and operational safeguards were designed as one system.
Technology
- Next.js
- TypeScript
- PostgreSQL
- Prisma
- Supabase
- Redis
- Meta Cloud API
- Google Gemini
- Vision AI
Last updated