Answer every channel. Automate any of it.

No. Connecting a WhatsApp number is a code you scan from the phone, and connecting a Facebook Page or an Instagram account is a button and a list of the Pages you already run. Nothing asks you for a token, an app id or a webhook address. The API is there for the businesses that want their own system sending messages, and it is one of four ways a message can start rather than the only one.

Yes. A connected Page's Messenger conversations and a connected Instagram account's direct messages arrive in the same list as WhatsApp, each marked with the channel it came from, and a reply typed in Njiwa goes back out on that channel. Facebook and Instagram are opening account by account while Meta completes its review of our app; until yours is switched on, the Channels screen says so rather than starting something it cannot finish.

Yes, and they get a screen of their own rather than being mixed into the conversations. Comments on your Facebook and Instagram posts arrive grouped by the post they are on, because three comments under one photograph is one job. You reply in public as the Page, and you can hide a comment that is spam or abuse, which takes it off the post for everybody but its author and can be undone. Njiwa will not delete somebody else's comment at all, only your own replies.

The Desk splits itself into what is unanswered and what has been answered, and a conversation moves between them on its own. A reply that failed to send does not count as an answer, and neither does an auto-reply, so nothing is marked dealt with because a machine said something. A conversation that needs no reply can be settled, which clears it without anybody pretending to have answered, and if that person writes again it is waiting again. Opened conversations stop being unread for the whole team rather than for one person.

Yes, into your own Google Calendar. A button in the reply box opens a month rather than a date field, their email address is already filled in from the last meeting somebody booked with them or from their contact record, and you can add a Google Meet link and other guests. Google emails them the invitation from your address, and what was booked drops into the reply box as a message for you to send. The calendar belongs to the person, not to the account: a colleague connects their own, nobody else on the account can see or use it, and Njiwa asks Google only for permission to create events.

Nothing on its own - they are part of the package. Growth includes one, Scale includes three, Team includes five, Business includes ten, and the high volume packages put no ceiling on them at all. Starter includes none, so connecting your first one is the reason to move to Growth. A Page and the Instagram account attached to it count as two, because they are two inboxes. Past what your package includes, connecting another is refused rather than billed, and the refusal names the package that would carry it. Disconnecting one frees the place immediately and keeps every conversation it brought in.

One message you send to one recipient. It counts the same whether it started from the API, the shared inbox, an auto-reply or a campaign, and a message to a group counts once. Messages arriving from other people are never counted, however many there are - so a busy month of customers writing to you costs nothing. Sends on a test key are not counted either, because they are not delivered to anybody, and neither is a message that failed to send.

Sending pauses. Nothing else does. Messages coming in still arrive, the shared inbox still works, and anybody mid-conversation with you can still reach you - it is only your outbound sending that waits for the cycle to reset or for you to move up a tier. We warn you in the console and by email at eighty percent and again at a hundred, so the first you hear of it is not a message that would not send. There is no charge for going over: the ceiling is a stop rather than a meter, and there is no overage billing on any package. The first time an account ever runs out we add twenty percent on top, once, and tell you it was one-time - nobody's first meeting with a limit should be a customer left waiting.

Uploading a file is refused and everything else carries on. Messages coming in still arrive, photographs customers send are still stored and still shown, and nothing already in a conversation is touched. We write at eighty percent and again when it is full, saying where the space went, because an account fills this by receiving photographs rather than by doing anything - and the alternative is finding out weeks later when an upload fails. Deleting a conversation gives its space back. Photographs are also re-encoded on the way in to something nearer the size anybody looks at, which makes the allowance go several times further without anybody being asked to do anything.

From the console, and it applies the moment it goes through. You are charged for the rest of the cycle only, not another full month, and the larger message allowance applies at once - so an account that has run out can be sending again in about a minute. Moving down is the other way round: it takes effect at your next renewal rather than mid-cycle, so you keep what you have already paid for, and we will not let you move down to a package smaller than what you are currently using without telling you what has to come off first.

Because of what is at stake by then. Connecting your own number is the fastest way to start and WhatsApp can restrict a number at any time, without warning and without appeal - at a few hundred messages a month that is a bad afternoon, and at a hundred thousand it is a business off the air. The Cloud API is the rail with an agreement behind it, so from the Volume tier upwards it is the only one we will run, and we ask for your Meta business verification before switching the tier on rather than after.

Only on the high volume packages, because they are the only ones where Meta charges per conversation. What Meta charges for your conversations is passed through at cost plus fifteen percent and itemised on your invoice, so what we add is a line you can read rather than a margin hidden inside a price. It is the only charge anywhere that sits outside a package price. On every other package there is no per conversation fee at all.

No. They see your business name and number, exactly as they did before. If you would rather they knew who they were talking to, you can switch signatures on and each reply carries the name of the person who sent it, but that is off unless you choose it.

The Cloud rail is the official WhatsApp Business Cloud API from Meta: it needs business verification and a dedicated number, and Meta charges per conversation. The Web rail uses the multi-device protocol that WhatsApp Web speaks, needs no approval and works with a number you already own, and you can be sending in about five minutes. Njiwa labels which rail every number is on, in the console and in the API.

Behave like a person. Pace your sends, which Njiwa does for you by default. Message people who are expecting to hear from you rather than a bought list. Let them reply, and answer when they do. Warm a new number up over a few days instead of opening at full volume. Keep your contacts in Njiwa rather than only on the phone, so that changing number is an afternoon rather than a disaster.

About five minutes. Create an account, and you get a live key straight away; a test key is one click away on the API keys screen. Link your own WhatsApp number, then send with the test key first: it validates every request, stores every message and fires real webhooks, and delivers nothing to WhatsApp. The live key sends from the same number, so nothing changes but the key.

Confirm two things within 72 hours: the email address you signed up with, by clicking a link, and a WhatsApp number, by messaging us from it. We never message you first for this, because sending codes to numbers that did not ask is how a number gets banned. An account that confirms neither is locked at 72 hours and removed at 96, which is what keeps this from being a free service for people signing up with throwaway addresses. Nothing is ever deleted from an account that has paid us or that has real customer traffic on it.

An owner can read it back by typing their password. It is a handful of attempts and then a wait, it is refused while somebody from Njiwa is supporting your account, and every reveal is written into your audit log with who did it and when. The key is stored sealed with a secret that is not in the database, so a stolen copy of the database opens nothing on its own. The webhook signing secret works the same way. Some older keys are stored only as a hash and can never be shown, because we do not know them either - the console marks which, and those have to be replaced.

No. It is an HTTP API, so curl, PHP, Python, Node, Go or whatever you already use will do. There are thin SDKs for PHP, Node and Python if you would rather not write the HTTP yourself.

Yes. Everybody gets their own login and one of four roles: an owner runs the account including the plan, an admin does everything except change the plan, an agent reads conversations and replies, and a viewer reads without sending. An agent and a viewer never see your API keys or your billing, so somebody answering customers all day cannot revoke the key your website sends on. You can also restrict somebody to particular numbers, so a business with a sales number and an HR number can keep each team to its own. Each package includes people - two on Starter, four on Growth, eight on Scale, fifteen on Team, thirty on Business and more above that - and that number is the limit: an invitation past it is refused rather than accepted and billed, and the refusal names the package that would carry them. Nobody is charged per person.

No, unless you decide they should. WhatsApp shows the recipient your business number and there is no per agent identity on a shared number, so who replied is something your console knows and your customer does not. If you would rather they knew, one setting puts the sender's name in front of the message. It is off until you turn it on, and it is never applied to messages your own code sends or to auto-replies, where a person's name would be a lie about who wrote it.

The message waits and goes when the number reconnects. Nothing is thrown away for being early. The same is true of a send that fails for a moment: it is retried, with a widening gap, rather than given up on. A message that genuinely cannot be sent is marked failed with a reason you can read, because the one thing worse than a message that did not go is a message that did not go and said nothing.

On a server we run, and we can tell you which one. Media files are stored on disk and served through signed, expiring links rather than left readable to anyone who guesses a filename. Messages are stored so that you can see what happened to them.

UPEO.AI. Message 0116888777 on WhatsApp and you reach a person, not a queue.