A multi-channel messaging platform on the WhatsApp Business API
The official WhatsApp Business API, Instagram, Telegram and website chat in one shared team inbox — with a REST API and webhooks.
This is our own platform: a product that brings the official WhatsApp Business API, Instagram, Telegram and website chat into one shared inbox, with a REST API and signed webhooks to connect it to your systems. You start on it today; it is not a project built from scratch.
The channels
- WhatsApp Business API (official)
- Meta's official API — not the WhatsApp Business app and not an unofficial workaround. That means one number the whole team uses at once, approved templates, and a conversation history that does not leave when an employee does.
- Instagram messaging
- Direct messages and story replies land in the same inbox, under the same assignment and follow-up rules.
- Telegram business bot
- A bot in your company's name, for customers who prefer Telegram — which is more common in some markets than it is in Egypt.
- Website chat
- A widget on your site that opens a conversation reaching the same team. The visitor does not have to leave the page or sign up.
- REST API + webhooks
- Not a channel — this is how you connect the platform to your own systems: send a message from your ERP, and receive every event on a signed webhook.
One inbox, and a team
- Every channel in one place, with each conversation assigned to a person or a department.
- Internal notes on a conversation that the customer never sees.
- A full record: who replied, when, and with what.
- Campaigns, approved templates, and keyword automations.
What to know before you start
The official API has rules that come from Meta rather than from us, and the best time to know them is before you buy rather than after:
- You need a phone number dedicated to the API. A number currently on the WhatsApp Business app has to be migrated, and migrating it closes the app on that number.
- The business is verified by Meta. That is done with the company's own documents, and the duration is not ours to control or to promise.
- Any message you start has to be a template Meta approved. Replies inside an open conversation do not need one.
- Since 1 July 2025 billing is per delivered message rather than per conversation. The old allowance of 1,000 free conversations no longer exists.
- Service messages — your replies inside the 24-hour window the customer opened — are free until 30 September 2026. From 1 October 2026 each business number's first 1,000 a month are free, and the rest are charged.
We walk you through all of it, and we do not put a duration on anything Meta decides.
What determines the price
No price list is published on this site, because the price is set after we understand your work. What moves it:
- How many channels, and how many numbers.
- Message volume, and category — marketing, service or utility. Meta bills by category.
- How many people are in the team.
- Integrations: ERP, CRM or PBX connections are priced separately.
- The currency you are billed in — any currency agreed in the project scope, stated in the quote.
Meta's per-message fees and the platform subscription are two different things, and the quote separates them so you can see what you are paying for.
Sources
Every figure and rule on this page has its source here, with the date it was read. What is not here is not on the page.
- The WhatsApp Business API rules, with their dates — Coderah's internal records (2026-09-15)
- The channels the platform actually supports — Coderah's internal records (2026-09-15)
- The card from 1 October 2026: 1,000 free service messages a month on each number, and the rest charged — Coderah's internal records (2026-09-26)
Tell us what's holding you up.
No need to write a full brief. Write what you know, we'll ask about the rest.
Tell us what you need