n **omnichannel messaging platform** is one workspace and one API for every customer channel: WhatsApp, SMS, RCS, Messenger, Instagram, Telegram and email. It joins a shared inbox, campaign sending, chatbots and AI agents that hand over to a person. To choose one, check three things. Does it follow each channel's rules? Do bots and agents share one customer thread? Is the per-message cost clear? OmniChannels.ai is BroadNet's platform built on this model.
Facts checked at their sources on 22 October 2026. Channel rules come from Meta, Google, Apple, Telegram and the UK ICO, and each one is linked inline. Facts about OmniChannels.ai come from its own website. Platform rules change often, so check the linked source before you sign a contract.
| Channel | Who starts the conversation | Reply window | Outside the window | Key 2026 rule |
|---|---|---|---|---|
| Business (opted-in users, approved template) or user | 24-hour customer service window from the user's last message | Approved template only (marketing, utility or authentication) | Per-message pricing since 1 July 2025; service messages charged from 1 October 2026 after 1,000 free per number per month | |
| Messenger | User, by messaging the Page | 24 hours for most user actions | Approved message tags only, including a 7-day human agent window | Window length depends on the user action that opened it |
| User only | 24 hours for most user actions | Human agent window of 7 days | Your app cannot start the conversation | |
| RCS | Business, after brand verification and launch approval | No Meta-style window | Not applicable | iPhone needs iOS 18 and a carrier that supports RCS |
| Telegram | User only (message the bot or add it to a group) | Bot rules apply | Bot cannot message first | Bots are registered through @BotFather |
| SMS | Business | None | Not applicable | Sender ID rules vary by market; marketing texts need consent and an opt-out |
What an omnichannel messaging platform actually does
Most companies start with one channel per team. Marketing sends SMS. Support answers WhatsApp in a separate app. Social replies live inside each network's own tools. Each tool keeps its own contact list, its own reports and its own opt-outs. Customers then get the same promotion twice, or a reply that ignores yesterday's chat.
An omnichannel platform fixes this with four layers that share one customer record:
- **Shared inbox.** Every reply from every conversational channel lands in one thread per customer. Agents assign, tag and answer from one screen.
- **Campaigns.** Bulk, personalised and scheduled sends on each channel, with each channel's template and consent rules applied.
- **Automation.** Rule-based chatbots for routine questions and AI agents for open questions. Both hand over to a person when needed.
- **API and webhooks.** Your own systems send messages and receive delivery and reply events through one interface.
This guide is about choosing and running the platform. For journey design in retail and delivery (channel waterfalls, consent ledgers, re-engagement), read our omnichannel strategy for ecommerce and logistics. For BroadNet's own channel stack, see omnichannel messaging.
How a shared inbox should work
The inbox is where most of the daily work happens, so test it first. A good inbox keeps one thread per customer across channels. An agent should see the WhatsApp question, the earlier SMS delivery alert and the bot's answers in order.
- **Assignment and tags.** Conversations go to a person or a team, and tags show topic and status.
- **Window awareness.** The agent should see when a WhatsApp, Messenger or Instagram reply window is about to close. After that, the only option is an approved template or tag.
- **Templates and media.** Approved WhatsApp templates, images, documents and attachments are available inside the reply box.
- **Seats.** Check how agent seats are priced. Inbox cost usually scales with team size, not message volume.
- **Reporting.** Response time, volume per channel and agent, and an export you can feed into your own BI tools.
Chatbots, AI agents and human handover
Automation now comes in two forms. **Flow chatbots** follow menus, keywords and lookups. They are predictable, cheap to run and easy to audit. **AI agents** answer open questions from a knowledge base and can call tools such as an order lookup. They cover more ground, but only as well as the content behind them.
Human handover is not optional on WhatsApp. The WhatsApp Business Messaging Policy says automated experiences must have "prompt, clear, and direct escalation paths", and lists in-chat human agent transfer as one of them. The same policy requires opt-in before you message someone and requires you to respect every request to stop, on or off WhatsApp.
When you test handover, check these points:
- The customer can ask for a person in plain words, not only through a menu button.
- The agent receives the full bot or AI transcript, not a blank thread.
- The bot stops replying once a person takes over.
- Handover outside business hours sets a clear expectation and does not leave the customer waiting with no answer.
- The reply window is still open when the agent picks up. If not, the agent needs a template (WhatsApp) or the human agent tag (Messenger and Instagram).
On BroadNet's side, enterprise AI agents run on BroadNet AI.
WhatsApp rules that shape the platform in 2026
WhatsApp is the channel with the most rules, and they change the economics of every inbox. According to Meta's WhatsApp pricing documentation, a 24-hour **customer service window** starts when a user messages or calls the business. Inside it, you can reply with free-form (non-template) messages. Outside it, you can only send an approved template in one of three categories: **marketing**, **utility** or **authentication**.
Meta has charged per message since **1 July 2025**, replacing conversation-based pricing. Its pricing updates page lists two changes from **1 October 2026**. First, service messages are charged again, after a free tier of 1,000 delivered service messages per business phone number per month. Second, utility templates sent in reply inside an open window, free since July 2025, are charged again. Unused free messages do not carry over.
- **Keep conversations in one window.** Fast first replies and single-window resolution now matter for cost, not only for customer satisfaction.
- **Watch the free tier per number.** If you run several numbers, each has its own 1,000-message tier.
- **Categorise templates correctly.** The category decides the rate, so review template wording before submission.
- **Ask for pass-through pricing.** Meta's charge should appear as its own line, separate from platform and seat fees.
We cover the October change in detail in WhatsApp service message pricing from October 2026, and compare OTP costs in WhatsApp vs SMS OTP cost by country. For access to the API itself, see WhatsApp Business API.
Instagram, Messenger and Telegram: user-first channels
These three channels are mainly for replying, not outbound campaigns. Plan your inbox and staffing around that.
- **Messenger.** Meta's Messenger Platform policy sets a standard messaging window that lasts 24 hours for most user actions. Outside it, only approved message tags are allowed. The human agent tag lets a business reply manually within a separate 7-day period. A Click-to-Messenger ad can keep the window open for up to 7 days.
- **Instagram.** The Instagram messaging API only lets your app message someone after they have messaged your professional account. The window lasts 24 hours for most actions. Replies can be tagged to use a separate 7-day human agent window.
- **Telegram.** Telegram's bot documentation says bots cannot start conversations. A user must message the bot or add it to a group first. Bots are registered by messaging @BotFather.
In practice, the 7-day human agent windows are for people, not bots. A platform should tag those replies correctly and not let automation use them.
RCS and SMS: business-initiated channels
RCS and SMS let the business message first, which makes them the main channels for alerts, OTPs and campaigns to people who have not chatted with you.
**RCS.** Before an RCS agent can send, Google's verify and launch guide requires brand verification and launch approval by Google, carriers or both. The agent then reaches RCS-capable users only on the carrier networks that approved it. Some carriers need a direct contract. Google's capability check lets you test whether a device can receive RCS and, if not, reach the user through SMS or MMS instead. On iPhone, Apple's support page says RCS needs iOS 18 and a carrier that supports RCS on iPhone. More detail is in RCS Business Messaging in 2026 and on our RCS messaging page.
**SMS.** SMS reaches any mobile phone, but sender ID rules vary by market, so check them before launch (OmniChannels.ai lists sender ID rules by market). Consent rules also apply. For example, the UK ICO's PECR guidance treats marketing texts as electronic mail. It requires consent that covers the specific channel, a sender who does not hide their identity, and a chance to opt out in every message, such as a STOP reply to a code. See our SMS API for routes and sender ID handling.
A checklist for choosing an omnichannel messaging platform
| Area | What to ask | Why it matters |
|---|---|---|
| Channels | Which channels are live today, and which are on a roadmap? | A roadmap channel cannot carry this quarter's traffic |
| Inbox | One thread per customer across channels? Assignment, tags, templates, media? | Split threads mean repeated questions and slower replies |
| Windows | Does the inbox show WhatsApp, Messenger and Instagram window status? | Missed windows force paid templates or tags |
| Automation | Flow bots and AI agents? Which languages? How is handover tested? | WhatsApp policy requires a clear escalation path |
| Fallback | Can you set a channel order per use case, such as WhatsApp, then RCS, then SMS? | Critical alerts must arrive even when one channel fails |
| Consent | Are opt-ins stored per channel, and do opt-outs apply at once? | Late opt-outs create regulatory and policy risk |
| Pricing | Platform fee, seats, per-message rates and Meta's charge on separate lines? | Bundled pricing hides what each channel really costs |
| Developers | REST API, webhooks, SDK, SMPP for high-volume SMS? | Your systems need to send and listen, not only agents |
| Reporting | Filters and CSV export of delivery and conversation data? | You need your own data to tune journeys |
| Security | Which certifications does the provider hold? | Customer messages contain personal data |
How OmniChannels.ai fits
OmniChannels.ai is BroadNet's omnichannel messaging platform. BroadNet was founded in Beirut, Lebanon in 2003, is headquartered in Dubai, and is an official Meta Business Solution Provider. It runs 1,000+ direct operator connections, reaches 200+ countries, and handles 300M+ messages a day for 60,000+ enterprises. Here is what the OmniChannels.ai site states about the product:
- **Nine channels** from one workspace and one API: WhatsApp Business API, SMS, RCS, voice, Facebook Messenger, Instagram, Telegram, email and push notifications.
- **Omni Inbox.** One thread per customer, with agent assignment, tagging, media, templates and attachments.
- **Campaigns.** Quick send, bulk, personalised and auto-schedule on every channel, with Excel or CSV upload, preview and duplicate filtering.
- **Automation.** Flow chatbots with menus, keywords and lookups. AI agents powered by BroadNet AI answer in English and Arabic from your knowledge base and tools, and hand over to a person in the inbox. Voice AI agents are also available.
- **Fallback** order set per use case, for example WhatsApp, then RCS, then SMS.
- **Developers.** A REST API with an OpenAPI spec and a TypeScript SDK, delivery webhooks in one format, SMPP 3.4 over TLS, and an MCP server for AI agents.
- **Reporting.** Summary and advanced reports with filters and CSV export.
- **WhatsApp onboarding** through Meta's Embedded Signup, so the business connects its own WhatsApp Business account.
- **White-label** option with multi-tenant sub-accounts for resellers.
On pricing, the site lists no setup fee and no monthly minimum. There is a recurring platform licence, a seat for each person who answers in the inbox, and usage drawn from a prepaid wallet. WhatsApp messages are charged at Meta's own rate with zero markup, and sender ID registration is passed through at cost. There is no self-serve trial. The team runs a live demo for your use case instead, because WhatsApp, RCS and sender IDs need verification before production sending.
BroadNet holds ISO 27001, ISO 27018, ISO 9001 and ISO 22301 certifications and a SOC 2 Type II report, is GDPR compliant, and offers a 99.99% SLA.
Frequently asked questions
What is an omnichannel messaging platform?
An omnichannel messaging platform is software that runs customer messaging on several channels from one workspace and one API. It usually combines a shared inbox, campaign sending, chatbots and AI agents. Typical channels are WhatsApp, SMS, RCS, Messenger, Instagram, Telegram and email. The goal is one customer thread and one set of consent records, instead of separate tools per channel.
What is the difference between multichannel and omnichannel messaging?
Multichannel means a business uses several channels, often through separate tools that do not share data. Omnichannel means those channels share one customer record, one inbox thread and one set of opt-ins. In an omnichannel setup, an agent can see an SMS alert and a WhatsApp reply in the same history. Campaigns can also skip people who already opted out elsewhere.
How long is the WhatsApp customer service window?
The WhatsApp customer service window lasts 24 hours. According to Meta, it starts when a user messages or calls the business. Inside the window, the business can send free-form replies. Outside it, the business can only send an approved template in the marketing, utility or authentication category. If the user messages or calls again before it expires, the timer resets to 24 hours.
Are WhatsApp service messages free in 2026?
Not fully. Meta made service messages free from 1 November 2024, but resumed per-message charges on 1 October 2026. Each business phone number now gets 1,000 free delivered service messages per month, and messages beyond that are charged. Utility templates sent in reply inside an open window are also charged again from the same date.
Can a business message customers first on Instagram or Telegram?
No. Instagram's messaging API only lets a business app reply after a person has messaged the professional account. The standard window lasts 24 hours for most actions, with a separate 7-day human agent window. Telegram bots cannot start conversations either. A user must message the bot or add it to a group first. For outbound reach, use WhatsApp templates, RCS or SMS.
Does RCS work on iPhone?
Yes, with conditions. Apple says RCS on iPhone needs iOS 18 and a carrier that supports RCS on iPhone. For businesses, an RCS agent also needs brand verification and launch approval from Google, carriers or both, and reaches only approved networks. Google's capability check lets you fall back to SMS when a device cannot receive RCS.
Do AI agents in a messaging platform need human handover?
Yes, on WhatsApp it is a policy requirement. The WhatsApp Business Messaging Policy says automated experiences must offer prompt, clear and direct escalation paths, such as an in-chat transfer to a human agent. Good handover passes the full transcript to the agent, stops the bot from replying, and keeps the reply window in mind so the agent can still answer.
How is an omnichannel messaging platform usually priced?
Most pricing has three parts. There is a platform or workspace fee, a seat fee for each agent who works in the inbox, and per-message or per-minute charges that vary by channel and country. WhatsApp also carries Meta's own per-message charge. Ask for each part on a separate line so you can compare channels and see Meta's charge without a markup.
To see a shared inbox, campaigns and AI agents working on your own channels, book a live OmniChannels.ai demo. For direct operator routes, sender ID registration or an enterprise agreement, contact BroadNet.