Messaging Channels
Connect WhatsApp Business, Instagram DMs and Facebook Messenger — one agent, one knowledge base, one message quota.
Channels let the same AI agent that runs on your website answer customers in the messaging apps they already use. WhatsApp Business, Instagram DMs and Facebook Messenger are supported; each can be connected once we have opened it (see Availability below). Your website and your channels share one knowledge base, one set of capabilities, one CRM and one message quota.
You manage channels in Dashboard → Channels. Only the workspace owner can use it: invited operators don't see it in their sidebar, an operator who opens its address gets the notice "Channels are managed by the website owner", and the server refuses an operator's changes to channels as well. A partner does not see it either, and the server refuses a partner's changes to channels too.
Availability. We open these channels one at a time. A channel not open yet still has a card, marked Coming soon, with no Connect button. Until one channel is open, the Channels page shows No channels available yet in place of the cards; this is not a fault on your account. This guide covers incoming customer conversations. Outbound WhatsApp appointment reminders use a separate automation feature on eligible plans; WhatsApp is not available for lead-status follow-ups, which go out by email only.
Plan availability
Messaging channels are included on Pro and Business, not on Starter.
The workspace has to be paid as well: open Channels on one that isn't, and you get the same lock screen Integrations shows — "This workspace isn't active yet" — until payment completes.
| Channel | Starter | Pro | Business |
|---|---|---|---|
| WhatsApp Business | — | ✓ | ✓ |
| Instagram DMs | — | ✓ | ✓ |
| Facebook Messenger | — | ✓ | ✓ |
On a paid workspace whose plan has no channels, the Channels page still lists the three cards, but Connect is replaced by an upgrade strip, and a note above the cards reads "Your current plan does not include messaging channels, so connecting one is locked." A connect attempt made anyway — say, because the plan changed after the page loaded — is refused with "Your plan does not include messaging channels. Upgrade it to connect one." Upgrade to a plan that includes channels to lift the lock; see Billing & plans. If a plan change takes channels away from a workspace that already has accounts connected, the agent stops answering on them; you can still pause or disconnect each one.
A workspace with no website — say, one created from a channel — is offered only plans that include channels, so it does not pay for a workspace that has no channel to answer on.
The same monthly AI-message allowance that applies to your website widget applies to channel replies. There is no separate NovixAgent channel charge or per-plan connection cap. See Billing & plans for the message allowance on each plan.
Before you connect
What you need to connect, most of it required by Meta:
- A Facebook account with access to the business assets you want to connect (a WhatsApp Business number, an Instagram professional account, or a Facebook Page).
- WhatsApp: a phone number that is not currently registered in the WhatsApp consumer app or the WhatsApp Business app. If your number is already in use in either app, delete that account first or use a dedicated number.
- Instagram: a professional account (Business or Creator) that is linked to a Facebook Page. Personal Instagram accounts can't receive automated replies.
- Messenger: a Facebook Page you admin.
Connecting WhatsApp Business
WhatsApp connects through Meta's login popup. Instagram and Messenger use the same flow and the same steps below, each asking for its own account type (a WhatsApp Business number, an Instagram professional account linked to a Facebook Page, or a Facebook Page you admin).
- Go to Dashboard → Channels and click Connect WhatsApp. The button switches to "Waiting for authorization…" while the popup is open.
- A Meta (Facebook) login popup opens. Log in with the Facebook account that has access to your business.
- Follow Meta's guided setup, choose an existing WhatsApp Business number or register a new one, and confirm the business details Meta asks for.
- Finish the popup. The card refreshes and the account appears as a connected row — a masked account id, the date you connected it, and a green Active status. Your agent starts answering that channel right away.
Instagram and Messenger: share one. Facebook's window asks which Pages, and for Instagram which Instagram account, to share with NovixAgent. Share only the one this workspace should answer, and leave the messaging permission on. We connect only what you share; without the messaging permission the connection fails; and if you share several, only one of them is connected, not necessarily the one you meant.
One account per channel for now: once a channel is connected there's no "add another account" button on its card. To move a channel to a different account, disconnect the current one first.
If the popup is blocked by your browser, a notification appears reading "Popup blocked. Allow popups for this site to connect." — allow popups and click Connect again. Other connect, pause or disconnect failures appear the same way, as a notification rather than as text on the card.
Pausing and resuming a channel
Each connected account has a live Active / Paused toggle — no save button, the change takes effect instantly.
- Active (green dot) — the agent answers on this channel. Meta accepts a free-form reply only within 24 hours of the customer's last message; past that, Meta rejects the send.
- Paused (gray dot) — the agent stops answering messages to this account. The connection stays in place; flip it back to Active to resume.
Pause when you want to mute the agent for a while (say, over a holiday) but keep the connection ready to flip back on. Disconnect removes the connection entirely (see Disconnecting below); use it when you're done with an account for good.
On a plan without channels you can still pause an account or disconnect it. Flipping a paused account back to Active is refused there, with the same message a connect attempt gets, until the plan includes channels again.
How conversations work
A connected channel runs the same AI agent as the web widget, just through a different front door:
- Same knowledge base — the agent answers from your crawled pages, your typed notes, and your uploaded files.
No website? Give it something to learn from. If this workspace is connected only through a channel, there are no crawled pages, so until you add content the agent has no material to answer questions from; it can still take a message and pass it to your team. A few lines in Dashboard → Knowledge Base → "Anything we missed" — your hours, prices, what you do and don't offer — are enough to make it useful, and take a minute. See Adding content.
- Same behavior — your AI template, guardrails, tone, and capabilities apply unchanged.
- Same CRM — leads captured in a channel land in your Leads dashboard alongside widget leads (see Capturing Leads).
- Same notifications — email and Slack alerts fire the same way (see Integrations).
- Memory resets after a long silence. A messaging thread has no natural end: the same phone number or handle keeps writing into one conversation. So the agent treats six hours of silence as the end of one exchange: after that gap it answers fresh rather than carrying yesterday's context into today's question. This is what stops a thread that started in one language months ago from pulling a reply back into it.
The channel agent is reactive: it replies when a customer writes first. Meta's 24-hour service window applies to those replies, and it is Meta that enforces it — a reply attempted after the window closes is rejected at their end, and when that happens to an operator's reply, the operator is told it was not delivered. It does not launch campaigns or broadcasts from the Channels screen. Outbound WhatsApp appointment reminders are configured separately, under AI Assistant, and use an approved Meta template. Lead-status follow-ups are email-only, and a lead that arrived over a channel usually has no email address, so it usually gets no status follow-up. Incoming conversations are text only for now. A customer who sends a file, photo, video or voice note isn't left hanging: the agent replies with a short line saying it can't open that yet and asking them to describe what they need, or to use your website chat instead. Nothing is read from the attachment itself. Those lines are sent in your site's chat language (in English when that language has no version of them) — an attachment carries no text to detect the customer's own language from.
When the agent doesn't answer. Sometimes a message gets no AI answer: your message quota is used up, the knowledge base is unreachable, the answer breaks off before it's complete, or the customer asks for a person while Live Agent is on but no operator is available. The customer still isn't left in silence. Their message is copied into Dashboard → Live Chat → Inbox, where your operators can reply to it in the same thread; you and the operators who have access to the site get an email about it; and the customer gets one automatic reply saying their message arrived and a person from your team will reply there. That reply is marked as automatic and written in the customer's language when their message shows it, otherwise in your site's chat language (in English when that language has no version of it). It goes out at most once in six hours for each conversation, and the email normally follows the same limit — so a customer who writes ten times in a row gets one automatic reply and you get one email, while each of the ten messages reaches the inbox. Rarely, for example when a server restarts just as the email is sent, a second email about the same conversation arrives within those six hours: we send it again rather than risk the message going unnoticed. The conversation stays with the AI: once the cause is gone, the next message is answered as usual. The one exception is a sender cut off by the anti-abuse rate limits — those messages get no automatic reply and are not copied to the inbox.
Handing off a WhatsApp conversation to a human
WhatsApp also lets a real person take over a customer thread from the AI, using the same Live Agent inbox you use for website live chat.
Here's the shape of it:
- One inbox. A handed-off WhatsApp conversation lands in Dashboard → Live Chat → Inbox, right next to your website live chats. Your operators answer from the same place, with the same saved replies, assignment, and transcript tools.
- One availability setting. The same Live Chat presence controls both surfaces — you set your working hours and go online once, and it governs the website widget and your channels. A channel conversation is only offered a human when Live Agent is on, you're inside your working hours, and an operator is actually online; otherwise the AI keeps handling it. What happens when the customer asks for a person at such a moment depends on why no human is offered. If Live Agent is on but you're outside your working hours or no operator is online, the AI passes the request on once it recognises it: their message still goes to the inbox, you get the email, and they get the automatic reply described under When the agent doesn't answer. If Live Agent is off — not on your plan, or not yet enabled — the AI has no way to call a person and keeps answering on its own, so asking for one does not copy the message to the inbox or send the automatic reply.
- The operator gets recent available context. On handoff, the operator can see up to the 20 most recent AI turns retained for the conversation; verbatim text is shown only where retained. Some grounded turns may not include that text, so this context is a concise aid rather than a guaranteed full transcript.
- The AI steps aside, then comes back. While a human is handling the thread the AI stays quiet on it. When an operator clicks Resolve, the AI resumes for later messages. A thread left idle is also closed automatically after a period of silence, and that closure hands the AI back too — so a forgotten handoff doesn't leave a silent thread permanently mute. A thread the customer keeps writing to is not closed this way: it stays with your operators until one of them clicks Resolve.
Requirements. Handoff needs Live Agent on your plan in addition to the channel itself (see Live Agent and Team & Operators).
Live Agent is included on Pro and Business, not on Starter.
Known limits. Operator replies into WhatsApp are text only — file attachments are not delivered back over the channel yet, and the operator is told when a reply could not be delivered. Replies also have to fall inside Meta's 24-hour customer-service window; a reply sent after that window closes may be rejected by the channel.
Quota and billing — two separate counters
It helps to keep two counters apart:
- AI answers — counted by NovixAgent AI. AI answers in a channel count against the same monthly plan quota as the widget, one message per answer. There is no separate channel quota. When the quota is used up, the AI stops answering in your channels until the quota refills (monthly, on your billing-cycle anniversary, also on a yearly plan), you upgrade, or you add a message pack. Customers aren't met with silence in the meantime: each message goes to your Live Chat inbox, you get an email, and the customer gets an automatic reply that a person will answer — see When the agent doesn't answer. (On your website the widget stays on the page and switches to collecting contacts instead — see What happens when you run out.) See Billing & plans for how quotas and resets work.
- Message delivery — billed by Meta, not by us. For WhatsApp, Meta charges message delivery directly to your own Meta billing account, and reactive customer-service replies normally fall inside Meta's 24-hour service window, where Meta does not charge for them; Meta charges for delivered template messages, such as appointment reminders, except a utility template delivered while the customer's service window is open. On our side, AI answers count against your plan's message quota, and WhatsApp appointment reminders against their own monthly allowance.
Meta redeliveries are de-duplicated before they reach your quota, so a message Meta sends twice is only answered — and only counted — once.
Disconnecting
On a connected account row, click Disconnect. You'll get a confirmation dialog headed "Disconnect <masked account id>?", saying the agent will stop answering that account's messages and that you can reconnect it later. Confirm it and the agent stops answering that account immediately. Your knowledge base, leads, and widget are unaffected, and you can connect the same or a different account later.
Privacy and retention
- Masked ids in the channel list — on the Channels screen, each connected account row shows a masked id, never the full number or handle. A workspace created from a channel, with no website, is named after the number or Page it connected first.
- Visitor identifiers are kept out of analytics — the channel identity of a visitor (for example a WhatsApp number) is replaced by a one-way keyed digest before anything is written to the analytics tables, which have the longest retention, the widest read audience and an export path. The number itself is still held in the channel records, because it is what routes the conversation back to the right person; it is not hidden from us, it is kept out of the place it would travel furthest from.
- Message history is pruned automatically — a channel conversation is deleted once it has gone without a new message from the customer for the period in the Data Retention Policy, and its messages go with it. The clock runs from the customer's last message rather than from when the conversation started. A thread a human operator is actively handling, meaning an open live chat on it with a message inside that period, is not pruned; once that chat has been quiet for the full period, the thread is pruned like the others, even if the handover was left open. Leads captured during a channel conversation are kept independently under your normal data-retention settings.
- Tokens are encrypted at rest — the access tokens Meta issues for your connected accounts are stored encrypted. The dashboard shows only a masked account id, and the fields that carry the tokens are redacted from our logs.
Troubleshooting & FAQ
"This phone number is already in use" when connecting WhatsApp. Meta doesn't allow a number that's active in the WhatsApp consumer or WhatsApp Business app to be used with the API. Delete the WhatsApp account in that app (Settings → Account → Delete account — this removes the app registration, not your business) or use a dedicated number, then reconnect.
A channel won't connect because it is already connected to a workspace. The dashboard names what you were connecting: "This WhatsApp number is already connected to a workspace", "This Instagram account is already connected to a workspace" or "This Facebook Page is already connected to a workspace". The login popup may show a similar sentence for a few seconds before it closes. A WhatsApp number, Instagram account or Facebook Page can be connected to one workspace at a time, and another workspace of your own counts. Disconnect it where it is connected — disconnecting releases it — then connect it here, or connect a different number, account or Page.
A customer wrote to us but got no answer. Check, in order: (1) the account row shows a green Active dot — if it's paused, flip the toggle back to Active; (2) your monthly message quota isn't exhausted (Dashboard → Analytics → Overview, or the Payment & billing panel on the website card in Dashboard → Workspaces) — when it is, the customer gets an automatic reply rather than an answer, and their message is waiting in Dashboard → Live Chat → Inbox; (3) they sent plain text — an attachment or voice note gets a short reply asking for text instead of a real answer, so check whether that's what they received rather than silence.
What's the difference between Pause and Disconnect? Pause mutes the agent for that account temporarily but keeps the connection — the account stays in your list, ready to flip back to Active. Disconnect removes the connection entirely. Use Pause for a short break, Disconnect when you're done with an account.
Who pays Meta for WhatsApp messages? You do, on your own Meta billing — but reactive customer-service replies normally fall inside Meta's 24-hour service window, where Meta does not charge for them; Meta charges for delivered template messages, such as appointment reminders, except a utility template delivered while the customer's service window is open. On our side, AI answers count against your plan's message quota, and WhatsApp appointment reminders against their own monthly allowance.
Why does Instagram require a Facebook Page? That's how Meta's API works for the way we connect Instagram, through Facebook Login: it serves only professional accounts linked to a Facebook Page. Link one in Instagram → Settings → Business tools and controls, then reconnect.
Why doesn't my operator see the Channels page? By design — Channels is owner-only. Operators handle live conversations; connecting or disconnecting business accounts stays with the owner. See Team & Operators for what operators can access. The same goes for a partner: channel connections stay with the owner.
We hit our message quota mid-month. What happens in channels? The AI stops answering in your connected channels until the quota resets on your billing-cycle anniversary, you upgrade, or you add a message pack. Until then each customer message is copied into your Live Chat inbox for an operator to answer, you get an email, and the customer gets one automatic reply that a person will reply — at most once in six hours for each conversation, as described under When the agent doesn't answer. Upgrading takes effect immediately and AI replies resume with the new quota. Your website widget behaves differently — it stays on the page and switches to collecting contacts; see What happens when you run out.
Can the agent send promotions or message customers first? The Channels connection itself is for inbound customer service: the agent replies when a customer writes first, and the Channels screen does not send campaigns or broadcasts. We do not send promotions. The one message the agent starts on WhatsApp is an appointment reminder for a booking the customer made — a separate automation feature on eligible plans, configured under AI Assistant, sent as an approved Meta utility template because it falls outside the customer-service window. Automatic follow-ups on a lead's status are a different thing again, and they go out by email only — WhatsApp is not an option there. Since a customer who reached you over WhatsApp normally leaves a number rather than an email address, a WhatsApp-sourced lead usually gets no status follow-up. Work those from the Leads list by hand, or reply in the thread itself.
Can I connect Instagram or Messenger? Yes, once we have opened them (see Availability at the top of this page) — both are supported alongside WhatsApp Business on the plans that include channels (see Plan availability). Instagram needs a professional account linked to a Facebook Page and Messenger needs a Page you admin; those are Meta's requirements, listed under Before you connect.
Stuck on a WhatsApp setup step? Email support@novixagent.ai — connection questions are usually resolved in one round trip.