In the app: Settings → WhatsApp
Needs the 'View WhatsApp Config' permission.
Connect a WhatsApp Business number to a store, so customers can message you on WhatsApp and the AI and your team can answer from the inbox. You bring your own number and your own Meta app; the page walks you through five steps. One number belongs to one store, and one store has one number. WhatsApp tickets are answered with the same AI settings as live chat.
Store and availability
The store picker at the top chooses which store you are setting up. Everything below it belongs to that store only. Without any store, the page asks you to create one first.
If the page says "WhatsApp is not enabled for this workspace yet", the WhatsApp channel is switched off on Squid's side. It is one switch for all of Squid, not a setting of your organization, although the notice speaks of your workspace. Nothing can be set up until Squid switches it on; ask your Squid contact.
When no SLA policy covers WhatsApp, a notice offers "Add WhatsApp to a policy". Without one, WhatsApp tickets have no response-time target. Policies are under Settings → SLA Policies.
Seeing this page needs the 'View WhatsApp Config' permission. Every change on it, including testing the connection, needs 'Edit WhatsApp Config'. Without it, change buttons are disabled and say so. "Test connection" remains clickable, but the server refuses it.
Until a number is fully connected, the page shows the five setup steps. When the first two or more steps are done, they fold away into a line such as "Steps 1–2 done"; click it to open them again.
Create your Meta app
Needs the 'Edit WhatsApp Config' permission.
Step 1 is done outside Squid, on Meta's developer site:
- Create an app of the type "Business".
- Add the "WhatsApp" product to it and connect the WhatsApp Business account that holds your number.
- Under the business settings, create a system user with the "Admin" role, give it access to the app and to the WhatsApp Business account, and generate a token that never expires with the two WhatsApp permissions (messaging and management). Copy the token; Meta shows it once.
- Under the app's basic settings, copy the "App Secret". Squid uses it to check that incoming messages really come from Meta.
A number that is in use in the WhatsApp Business app on a phone cannot be used until it is migrated off that app in WhatsApp Manager. Do that first, or Meta refuses to register the number.
Paste your credentials
Needs the 'Edit WhatsApp Config' permission.
Step 2 takes four values from your Meta app:
- "Phone number ID" and "WhatsApp Business account ID";
- "System User access token";
- "App Secret".
All four are required. The token and the secret are stored encrypted and are never shown again. Saving checks the access token and number with Meta and tries to subscribe Squid to your WhatsApp account. If that subscription fails, the credentials are still saved; "Test connection" retries it. Saving does not register an unregistered number: use the PIN form below. The App Secret is stored for checking incoming messages, rather than validated with Meta at this step.
If Meta has not registered the number yet, the step asks for the "2-step PIN": the six-digit PIN of the number's two-step verification. Enter it to register the number.
A number that is already connected to another store is refused: "This WhatsApp number is already connected to another store." The same refusal applies to a number that was connected to another store and disconnected there since, because a disconnected number stays tied to its store.
Point Meta at us
Needs the 'Edit WhatsApp Config' permission.
Step 3 tells Meta where to send messages. The step shows two values with copy buttons:
- "Callback URL": Meta calls it once to verify it, and then for every message.
- "Verify token": Meta sends it back on the verification call. It is not a password for anything else.
In your Meta app, open the WhatsApp configuration, edit the webhook, paste both values and save. Then subscribe to the "messages" field. Without that subscription, nothing your customers send reaches Squid.
The step checks every 5 seconds whether Meta's call has arrived; you do not need to reload the page. The two values only exist after step 2 is saved.
Add a payment method
Needs the 'Edit WhatsApp Config' permission.
Step 4 is a confirmation. The step says that Meta charges for every message it delivers from 1 October 2026, including replies from your team and the AI. A WhatsApp Business account without a payment method does not deliver billable messages: the customer gets nothing and no error is shown.
Add a payment method in WhatsApp Manager, under the billing settings of the same business account, then tick "I have added a payment method to this WhatsApp Business account". Squid cannot check this with Meta; the tick is your own confirmation. Squid counts the messages Meta reports as delivered, for the table under "Delivered messages", and does not bill you for those deliveries; Meta does. Your Squid plan is a separate matter: a new WhatsApp ticket counts as a ticket in your plan's usage, like an email.
Create the re-engagement template
Needs the 'Edit WhatsApp Config' permission.
When 24 hours have passed since a customer's last message, Meta blocks free replies. The only way back into the conversation is an approved template message. For an AI answer, Squid queues the template and holds the answer until the customer replies, for up to 7 days; after that the held answer expires and is not sent. A ticket gets no second template while an earlier one is pending or has been sent successfully. A failed or cancelled template can be replaced. Squid treats the last minute of the 24-hour window as closed to allow for delivery time.
Step 5 gives a "Suggested body" to copy. It has two placeholders: the customer's first name and the ticket number. In WhatsApp Manager, create a message template in the "Utility" category with that body, keep both placeholders, and submit it for Meta's review.
When Meta has approved it, fill in "Template name" and "Template language" (for example "en") and click "Save template". Squid reads the template from Meta and saves it even when it is unapproved or in another category. It can be sent only when it is approved, in the utility category and has exactly two body placeholders. A template that Meta cannot find is refused. A box under the button shows whether the template is usable, with the status and category Meta reports. Before every send Squid checks the status and category it last read from Meta. It reads them from Meta again when you save the template and when you click "Test connection", so after Meta changes a template, run that test.
Without a usable template, a ticket whose 24-hour window has closed cannot be answered until the customer writes again.
The connected number
Once all five steps are complete, the page shows the number's card instead of the steps: the phone number, the display name Meta approved ("Awaiting Meta's display name review" until then) and a status badge:
- "Connected": messages arrive and can be sent.
- "Needs your 2-step PIN" and "Waiting for Meta": Meta's side of the setup is not finished.
- "Token rejected": Meta refused the access token. The card is shown in this state even when a setup step is still open. Customer messages still arrive, but nothing can be sent until you click "Update token" and paste a new one.
- "Switched off": you disabled the channel for this store.
A disconnected number has no card: the page shows the five steps again.
The card also shows Meta's "Quality rating" and "Meta phone status", when the last message from Meta was received, when the webhook was verified, and the last error if there was one.
"Health" lists six checks with a tick or the reason it fails: "Credentials accepted by Meta", "Number registered", "Subscribed to your WhatsApp account", "Webhook verified", "Payment method added" and "Re-engagement template approved".
"Webhook settings" opens the callback URL and the verify token again.
Test, switch off and disconnect
Needs the 'Edit WhatsApp Config' permission.
- "Test connection" asks Meta for the number's current state and refreshes the health checks. It also tries again to subscribe Squid to your WhatsApp account when that had failed, and reads the re-engagement template's status from Meta again. It changes none of your settings.
- "Regenerate verify token" creates a new verify token after you confirm. The old one stops working at once. Messages keep arriving, but Meta's next verification fails until you paste the new token into your Meta app.
- "Disable" switches WhatsApp off for this store without removing the connection. While it is off, incoming messages are dropped and nothing is sent. "Enable" switches it back on. Both only work on a number whose setup is finished.
- "Disconnect" removes the connection after you confirm. Every WhatsApp ticket stays where it is and stays readable. Nothing new arrives, anything waiting to be sent is cancelled, and the stored token and secret are destroyed. Connecting the same number again later continues the same conversations; you have to paste the credentials again.
Delivered messages
A table of this store’s WhatsApp counts for today and the preceding 29 days, using UTC dates, per day and in total: messages sent by the "AI", by an "Agent", "Template" messages, and "Failed" ones.
These are counts, not costs: Meta charges per delivered message and bills you directly. Squid only uses these counts for this table and for Reports; they are not part of your Squid invoice. Successful deliveries are counted on the UTC date Meta says they were delivered, including when a read confirmation arrives first. "Failed" counts failures instead of deliveries, on the day Squid processes the failure. Counts are per message part, so a reply split into several parts can count more than once. If the counters cannot be loaded, the rest of the page still works.