Public websiteCustomer conversation platform
DripTell brings WhatsApp, Instagram, Messenger, Telegram and web chat into one workspace, with shared ownership, customer context, automation and AI assistance.
You are viewing the compatibility version because this browser does not support the modern website presentation. This is the public DripTell website; no customer workspace or account data is shown.
المنتج
مساحة عمل واحدة لكل محادثة وخطوة تالية مع العميل.
المنتج
مساحة عمل واحدة لكل محادثة وخطوة تالية مع العميل.
الحلول
ابدأ بالنتيجة التي يعمل فريقك على تحقيقها للعميل.
الحلول
ابدأ بالنتيجة التي يعمل فريقك على تحقيقها للعميل.
القطاعات
اكتشف دريب تيل من خلال محادثات العملاء في قطاعك.
القطاعات
اكتشف دريب تيل من خلال محادثات العملاء في قطاعك.
This guide takes an administrator from the Meta connection through the first verified conversation, then explains the daily rules that keep replies, templates and customer context reliable.
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.
Confirm the legal business details used in Meta Business Manager.
Choose a number that is not actively attached to an unsupported WhatsApp setup.
Decide who owns templates, opt-in evidence, quality monitoring and billing.
01. Prepare the business before connecting
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.
Start from channel settings: Choose WhatsApp and begin the official Meta connection flow.
Select the business assets: Use the correct portfolio, account and phone number rather than the first available option.
Confirm the connection: Check the connected number, quality state and workspace before inviting the wider team.
02. Connect WhatsApp to the correct workspace
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.
Complete one inbound reply test and one approved-template test with a real test number. Record the outcome in the workspace launch checklist.
03. Prove the full message loop
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.
Keep one accountable owner visible on every active conversation.
Pause automated follow-up when a teammate takes over.
Review failed, undelivered and low-quality messages as operational work, not vanity metrics.
04. Set ownership before volume arrives
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.
Meta changes WhatsApp service and utility message charging on 1 October 2026. Read the DripTell update before forecasting message cost.
05. Treat templates and consent as living controls
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.
Do not disconnect a working number as the first troubleshooting step.
Compare the DripTell event with Meta Manager before retrying repeatedly.
Send the exact IDs and timestamps to support when escalation is needed.
06. Troubleshoot from the first broken state
The connection is designed for conversations handled through the connected business channel. Historical availability depends on the source and connection method; confirm the expected history during the controlled launch test.
Yes. DripTell gives the team a shared inbox with ownership and conversation context, subject to the workspace roles you configure.
No. Template approval and customer permission are separate controls. Keep evidence of the customer action or relationship that permits the message.
Send support the workspace, channel, expected result and the exact step or provider state you are seeing.
