Skip to content

Your channels without connecting them

Connecting Messenger, Instagram or WhatsApp to the Inbox goes through Meta, which asks a lot of a small business. You can reach the people who message you there without it, two ways:

  • The link kit: ready messages, with your contact page’s link, for the replies those apps send by themselves. Whoever writes to you gets your page, where your assistant answers, your products show, and their order or message comes to you here. On every plan.
  • A custom channel: a tool that already answers your page, like ManyChat, passes each customer’s message to us, and your assistant’s reply goes back through it. On plans with inbox channels. For WhatsApp, the AutoResponder app on your Android phone, or a QR code link on a server of your own, can do the same, as trials with a risk you should read first.

Open Inbox channels. Under Link kit, choose the language of the messages, then copy each one where it goes:

  • WhatsApp Business app: under Business tools, the Greeting message (sent the first time someone writes) and the Away message (sent while you’re closed).
  • Messenger and Instagram: the instant reply in Meta Business Suite’s inbox automations.
  • Common questions: each as a question with its answer in the same automations. Customers tap one to start a chat: how to order, your prices (it opens your products) and asking a question (it opens your assistant), when you have those on.
  • Your bio on Instagram, Facebook or TikTok.

Each link says where it was shared (whatsapp, instagram, messenger, bio, faq), so a lead or an order that came from it shows it. For a flyer or your shop window, print your contact page’s QR code from Install.

Your contact page has to be on: it is unless you switched it off under Install.

A custom channel

A custom channel takes a customer’s message from any tool that can send a web request, puts it in your Inbox as that channel’s conversation (Instagram or Messenger), and lets your assistant answer it as it answers the rest.

  1. Open Inbox channels, and under Custom channel press Add a custom channel.
  2. Choose where its messages come from (Instagram or Messenger) and give it a name, like Instagram via ManyChat.
  3. Leave Reply address empty for a tool like ManyChat. Copy the Key now: it’s shown only once.
  4. In your tool, send each customer’s message to the Address for your tool, as below.

What your tool sends

A POST to the address, with the key in the X-Reachly-Key header (or ?key= at the end of the address, for a tool that can’t set headers), and this JSON:

{ "sender": { "id": "the customer's id in your tool", "name": "their name" }, "text": "what they wrote" }

The same sender.id keeps them in one conversation. Add "id" with the message’s own id, and a message sent twice is taken once.

What comes back

  • Without a reply address, the answer is {"reply": "…"}: the assistant’s answer, and a welcome message when you have one on. Send that text to the customer. It comes within 10 seconds; when it’s empty, there’s nothing to say yet. Your team sees the conversation in the Inbox, and answers in your tool.
  • With a reply address, the answer is {"ok": true}, and each reply, the assistant’s and your team’s, is posted to that address as {"conversation", "to", "text", "at"}. to is the sender.id it was for. Check it’s from us: X-Reachly-Signature is the HMAC-SHA256, in hex, of the X-Reachly-Time header, a dot, and the body, with your key.

Instagram and Messenger let a business reply for 24 hours after the customer’s last message, through any tool, and the Inbox keeps to that.

With ManyChat

ManyChat already answers Instagram and Messenger for your page. Its External Request action, in its Dev Tools, sends the message to your custom channel; its help says the action is on its paid plans, and that it waits 10 seconds at most.

  1. Add a custom channel without a reply address, and copy its key and address.
  2. In ManyChat, make the flow that answers any message your customers send (its default reply).
  3. Add an External Request action: POST to the address, a header X-Reachly-Key with your key, and a JSON body with the subscriber’s id and name and their last text input, as above.
  4. In Response mapping, save $.reply into a custom field.
  5. Add a Send message step with that custom field, for when it isn’t empty.

We haven’t tried this with a ManyChat account of our own; ManyChat’s pricing page didn’t open for us to read. If a step looks different in your account, the request and the answer above stay the same.

Make isn’t a fit for now: its Instagram for Business and Facebook Pages apps don’t have direct messages, by Make’s own documentation (November 2026).

AutoResponder on WhatsApp (a trial)

AutoResponder is an Android app that replies to WhatsApp messages through your phone’s notifications. It can pass each message to a web address and send back what the address answers, so your assistant can answer your WhatsApp without your number being connected to Meta.

Read this first. It isn’t an official WhatsApp API. WhatsApp’s Terms of Service count auto-messaging among the messages they don’t allow, and the terms for the WhatsApp Business app forbid using apps that work with it without WhatsApp’s written consent. WhatsApp may limit, suspend or close an account that breaks them, and a business whose account was closed can’t open another without its permission (WhatsApp’s terms as of November 2026). Try it on a number you can afford to lose. The official way is to connect your number under Inbox channels.

Set it up

  1. Open Inbox channels, and under Custom channel press Add a custom channel.
  2. Choose AutoResponder, for WhatsApp, give it a name, and press Add it. Copy the Key now: it’s shown only once.
  3. On the Android phone your WhatsApp is on, install AutoResponder for WhatsApp (or for WhatsApp Business), and give it notification access when it asks.
  4. In AutoResponder, add a rule for all the messages you receive, turn on Connect your web server, and paste the Address for AutoResponder into URL.
  5. Under Headers, add X-Reachly-Key with your key as its value. If you can’t add a header, end the address with ?key= and your key instead.
  6. Save the rule, and send a message in AutoResponder’s test chat. It comes into your Inbox and gets the answer a customer would; when nothing answers it, a line comes back saying it arrived.

What happens then

  • Each message comes into your Inbox as a WhatsApp conversation. Your assistant’s answer, your welcome message and keyword replies go back to AutoResponder, which sends them, each as a message of its own, within seconds.
  • A customer is known by the name or number their notification shows. A number becomes the contact’s phone, so their orders and other conversations join up. If you later save their number under a name, their next messages start a new conversation.
  • Group chats are left alone, and aren’t kept.
  • You answer customers yourself, in WhatsApp on your phone. AutoResponder can’t be sent a message later, so the Inbox doesn’t send your replies to these conversations, and follow-ups, broadcasts and news about orders and bookings don’t go to them either.
  • When your assistant hands a customer to you, it stays quiet with them until you close their conversation in the Inbox. Closing quiet conversations, under Automations, does that by itself.
  • If your WhatsApp Business app also sends its own greeting or away message, turn one of them off, here or there, so customers don’t get two.
  • Pictures and voice notes arrive as the words the notification shows, like “📷 Photo”: the assistant can’t see or hear them.
  • The phone has to stay on and online, with AutoResponder allowed to run.
  • If AutoResponder shows an error, forbidden means the key is wrong, plan_channels that your plan doesn’t include inbox channels, and not_found that the custom channel was removed.

We haven’t tried this on a phone of our own: it follows the request and the answer AutoResponder’s own pages describe. If a step looks different in your version of the app, the address and the key stay the same.

WhatsApp by QR code, on your own server (a trial)

Like WhatsApp Web, this links your WhatsApp to a server as one of its linked devices, by scanning a QR code. The server is yours, running Evolution API, an open-source WhatsApp Web client; we never run one. Your assistant answers through it, your team replies from the Inbox at any time, and what you send from your phone shows in the Inbox too.

Read this first. It isn’t an official WhatsApp API. WhatsApp’s Messaging Guidelines count using unofficial clients as adversarial behavior, its Terms of Service count auto-messaging among the messages they don’t allow, and the terms for the WhatsApp Business app forbid using apps that work with it without WhatsApp’s written consent. WhatsApp may limit, suspend or close an account that breaks them (WhatsApp’s terms as of November 2026). Try it on a number you can afford to lose. The official way is to connect your number under Inbox channels.

What you need

  • A server of your own running Evolution API, version 2.1.1 or later, reachable on https at port 443 or 8443. Evolution API’s own documentation says how to install it.
  • Its API key: the AUTHENTICATION_API_KEY it was started with. We use it once, to make the link, and don’t keep it.
  • A plan with inbox channels.
  1. Open Inbox channels, and under Custom channel press Add a custom channel.
  2. Choose WhatsApp by QR code, on your Evolution API server, enter your server’s address and its API key, and press Show the QR code.
  3. On your phone, open WhatsApp, then Linked devices, and press Link a device. Scan the code on your screen; a new one comes every few seconds until you do.

We make an instance for this channel on your server, and point its messages at the channel’s address with a key of its own.

What happens then

  • Customers’ messages come into your Inbox as WhatsApp conversations, with their number and WhatsApp name, and your assistant answers them through your server, as on any channel.
  • Your team can reply from the Inbox at any time: WhatsApp’s own app has no 24-hour window. Follow-ups and news about orders and bookings go to these conversations too.
  • What you send from your phone, or from WhatsApp on a computer, shows in the conversation, and your assistant leaves that customer to you for a while, as after any reply from your team.
  • Group chats, statuses and channels are left alone.
  • Pictures, voice notes and files show as a line saying what came, with its caption: the files stay on your phone and your server.
  • Broadcasts and WhatsApp templates don’t go through it: they need a number on the WhatsApp Cloud API.
  • If WhatsApp unlinks it (you logged it out on your phone, say), the channel shows as disconnected, and an alert goes to the devices you get alerts on. Press Show the QR code to link it again.
  • Removing the channel removes its instance from your server, which unlinks it from WhatsApp.

We haven’t tried this with a server and a phone of our own: it follows Evolution API’s own code (version 2.3.7), which differs from its documentation in places.

What it doesn’t do

  • Other tools carry Instagram and Messenger. WhatsApp comes through AutoResponder or a QR code link, above, or connect your number under Inbox channels, or use the link kit’s messages in the WhatsApp Business app.
  • It takes text: pictures and voice notes your tool sends aren’t passed on.