Run WhatsApp as a team operation, not a collection of phones.

Use a Meta Business Portfolio that the operating company controls. The person completing the connection should have the necessary Meta access and should know which WhatsApp Business Account and phone number belong to the workspace.

Open the WhatsApp channel settings in DripTell, begin the Meta connection and select the intended business portfolio, WhatsApp Business Account and number. Read every Meta permission screen before approving it. Return to DripTell and confirm that the number and display name are the ones your team expects.

A connected badge is not the end of the test. Send an inbound customer message, reply from DripTell and confirm that delivery state, customer identity, channel, owner and timestamps remain attached. Then test one approved template outside the customer service window.

Define who receives new conversations, how unanswered items escalate and what happens when a person replies during an automation. Use groups and assignment rules that match the real team, then give agents saved replies without removing the judgment needed for unusual cases.

Use the template category that matches the actual message purpose and keep proof of the customer action that created permission to contact them. A template approval does not replace consent, and an old opt-in does not justify an unrelated campaign.

Provider pricing and policy can change independently of DripTell. Review the provider updates area before major sends and whenever Meta announces a new effective date.

If a message does not arrive, identify whether the problem is connection, template approval, recipient eligibility, customer-service-window state, provider delivery or a DripTell workflow rule. Save the message ID, time, sender, recipient and error before reconnecting anything.