KIBI HELP & SETUP

Connect WhatsApp through MSG91

Connect your MSG91 account, add the webhook for incoming chats, then send a test message to check both parts.

WhatsAppAvailable
Business textingAvailable

Before you start

Have a WhatsApp number connected to MSG91 and access to its Authkey and WhatsApp settings. The key needs WhatsApp permission. Ask the account administrator about any access restrictions, and keep the full Kibi webhook URL private if it contains a token.

Set up, step by step

  1. In MSG91, open Authkey and choose an active key with permission for this WhatsApp account.
  2. In Kibi’s WhatsApp page, choose ‘Through Twilio or MSG91’, then MSG91.
  3. Paste the key, enter the WhatsApp number with its country code and choose ‘Connect my account’.
  4. Copy the webhook URL from ‘Getting WhatsApp ready’. Add it to this number’s incoming-message settings in MSG91 and save.
  5. Send a new message from another phone. Check the message in Kibi and look for the webhook step’s readiness tick.

MSG91 keeps billing you for messages. Kibi never charges your credits for WhatsApp.

Kibi MSG91 setup fields for auth key and the WhatsApp number.
Actual Kibi screen from a demo workspace. Use your own account details during setup.

After setup

Use Sync to bring the connected account’s templates into Kibi. Check the wording and provider status before using one. The incoming webhook, templates and provider billing are separate parts of the setup.

If you get stuck

Key rejected? Check its status and WhatsApp permission. No chat? Check the number and full webhook URL, including its token, in the incoming-message settings. A delivery-report webhook is a different event. After a key change, update Kibi and test again. Hide keys and tokens in anything you share with support.

Related guides

Choose your provider

Connect the account, then the webhook

MSG91 needs two checks: accepted account details and a webhook delivering incoming chats. Start with an existing MSG91 number and access to its settings. WhatsApp.

MSG91 bills messages directly; Kibi never charges your credits for WhatsApp. Sender registration and number migration need separate preparation.

  • Account accepted: the credential check passed.
  • Fresh incoming message visible: the webhook path passed.
  • Owner and next action clear: the enquiry is ready for the team.
Before you start

Find an active WhatsApp Authkey

In the official MSG91 panel, find Authkey for the account owning your number. Check it is active and allows the required WhatsApp service.

For network or other restrictions, ask the administrator to review the connection requirements. Keep existing controls in place and do not guess an allowlist address.

Keep secrets private

Keep the key and webhook private

Copy the Authkey directly into Kibi’s connection form. Hide it in screenshots. Treat a token-bearing webhook URL as private too.

Paste the complete destination only into the intended MSG91 setting. If either secret was exposed, ask the account owner to follow the supported replacement process.

Account connection

Connect the MSG91 account

In WhatsApp, choose “Through Twilio or MSG91”, then MSG91. Enter the Auth key and number with country code; choose “Connect my account”.

Kibi checks and encrypts the key. Correct any reported account or sender error, then continue to the webhook task in “Getting WhatsApp ready”.

  • Confirm that the key is active.
  • Confirm its WhatsApp permission for the intended account.
  • Check the number and country code.
  • Continue to the webhook task after the account check.
Webhook setup

Add the incoming-message webhook

Copy Kibi’s webhook URL from “Getting WhatsApp ready” into MSG91’s incoming-message configuration for the intended number. Use this source’s exact destination.

Delivery-report callbacks are a separate webhook flow. If you cannot find incoming-message settings, ask the MSG91 administrator. Save, then test a new chat.

Expected result

Check the first incoming chat

Send a new message from another phone. Find it in the intended enquiry and workspace. The webhook item is ticked after the first message reaches Kibi.

Check the owner and next action. If the composer permits a reply, send one in the test conversation and inspect its result.

If a check fails

Check the failed part of the path

Use the branches below. A saved account does not prove incoming delivery, and a delivery-status callback does not prove customer text reached Kibi.

If it stopped after a change, check the key, number, webhook or access that changed. Record the last success, masked number, test time and error; hide secrets.

  • Key rejected → check status, account and allowed service.
  • No incoming chat → check number, destination and inbound event.
  • Worked before a change → inspect that change first.
  • Incoming succeeds, reply fails → read the sending restriction separately.
After setup

Keep keys and templates current

Use Sync to refresh MSG91 templates. Check wording and provider status before choosing one. For restricted replies, follow the composer rather than replacing a working webhook.

When MSG91 keys change, replace them in Kibi and test incoming delivery again. Keep the administrator and destination owner in a setup note without the secrets.

A FEW MORE ANSWERS

Still wondering?

Why can the account connect while no chats arrive?

The credential check and incoming webhook are different parts of setup. Check the intended number, complete private destination and incoming-message configuration, then send a fresh message from another phone.

Can I use a webhook URL copied from another guide?

No. Use the exact destination Kibi provides for this connection. Keep its token private. A delivery-report endpoint or another workspace’s URL is not a substitute for the incoming-chat route.