KIBI HELP & SETUP

Connect WhatsApp through Twilio

Bring your existing Twilio WhatsApp sender into Kibi, with messages beside the enquiry, its owner and the next action.

WhatsAppAvailable
Business textingAvailable

Before you start

Have a WhatsApp sender already set up in the Twilio account you want to connect, permission to manage it, its Account SID and Auth token. This connects an existing sender; plan any move between providers separately before changing a live number.

Set up, step by step

  1. Sign in to the Twilio Console. Find the Account SID and Auth token for the account that owns your WhatsApp sender.
  2. In Kibi’s WhatsApp page, choose ‘Through Twilio or MSG91’, then Twilio.
  3. Paste the Account SID and Auth token into the matching fields. Enter the WhatsApp number with its country code.
  4. Choose ‘Connect my account’. Kibi checks the credentials and sender before saving. If it reports a mismatch, check that detail before trying again.
  5. Send a new message from another phone to the connected sender. Find it in the Kibi enquiry, then test a reply if the composer permits it.

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

Kibi Twilio setup fields for account SID, auth token 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 their wording and provider status before sending, and review Twilio’s current charges and sending requirements before increasing use.

If you get stuck

Keys rejected? Check that the SID, Auth token and sender belong to the same account. No incoming message? Check the tested number, sender readiness and incoming-message setup. Token changed? Update Kibi and repeat the test. Keep tokens out of support tickets, screenshots, email and chat.

Related guides

Choose your provider

Connect your existing Twilio sender

Use this route for a WhatsApp sender already set up in your Twilio account. Registration and number migration are separate tasks. WhatsApp.

Twilio bills messages directly; Kibi never charges your credits for WhatsApp. Confirm the intended production sender and its provider requirements before connecting.

  • Know which Twilio account owns the sender.
  • Use the Account SID and Auth token Kibi requests.
  • Keep provider onboarding or number migration as a separate task.
Before you start

Match the account, token and sender

In the official Twilio console, find the account or subaccount that owns the sender. Copy its Account SID, Auth token and WhatsApp number.

The SID identifies the account. Use the credential types Kibi requests. If your access cannot view them, ask the authorised account owner to complete setup.

Credential safety

Keep the Auth token private

Enter the Auth token only in Kibi’s connection form. Hide it completely in screenshots and keep it out of messages and notes.

If exposed, ask the account owner to follow Twilio’s replacement process. Check other integrations using the token, update Kibi and test again afterward.

Connection check

Enter the connection details

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

Kibi checks credentials and sender before saving. Correct the specific error shown. If the sender is not ready in Twilio, resolve that with its administrator.

  • Match the account selected in Twilio.
  • Confirm the complete sender number and country code.
  • Enter each credential in its corresponding field.
  • Read the connection result before testing delivery.
Expected result

Test an incoming message and reply

Send a new message from another phone to the connected sender. Find it in the intended Kibi enquiry and check its content and contact.

If sending is permitted, reply and check the receiving phone. Then confirm the owner and next action. Note the test time if either direction fails.

If something fails

Find the failed check

Use the branches below to separate authentication, sender readiness, incoming delivery and replies. A successful connection still needs a fresh message test.

For a failed reply, read the composer and provider error for template or other requirements. Share the masked sender, test time and error without the Auth token.

  • Credentials rejected → verify the account and current token.
  • Sender rejected → match the sender to that account.
  • Incoming absent → check the tested number and provider readiness.
  • Reply restricted → follow the stated sending requirement.
After connection

Sync the templates you need

Use Sync to refresh templates from the connected Twilio account. Check their wording and provider status before sending; Sync does not approve a draft.

Choose a template suited to the enquiry and check Twilio’s charges before wider use. Template sync does not resolve billing or sender problems.

Keep it working

Update Kibi when credentials change

Kibi encrypts checked keys and does not show them again. Keep credential management with the Twilio account owner.

When credentials change, replace them in Kibi’s readiness checklist and test incoming delivery and a permitted reply. Record the administrator and last successful test without storing secrets.

A FEW MORE ANSWERS

Still wondering?

Can I send the Auth token to support for checking?

No. Enter it only in the authorised connection form. Support diagnostics should contain masked values, the error, the time and the relevant account or sender context without exposing a credential.

Does connecting Twilio move my WhatsApp number?

This guide connects an existing eligible sender. Number registration and migration between providers are separate tasks. Confirm the current sender setup before making changes to a live business number.