Public website

Customer conversation platform

Every conversation. One clear next step.

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.

DripTell

Give Facebook Page conversations an accountable owner.

Connect the intended Page, prove two-way delivery and define when automation should respond, wait or hand the conversation to a person.

Give Facebook Page conversations an accountable owner.

Confirm Page ownership and access

Use a business-controlled Facebook Page and an administrator who can authorize messaging access. Review Page roles before connecting so the channel does not depend on one former employee or agency login.

Record the exact Page name and URL.

Keep at least two current business administrators.

Remove stale access before launch.

01. Confirm Page ownership and access

Connect the Page from DripTell

Begin in DripTell channel settings, authorize Meta and select the intended Page. If several Pages appear, verify the Page ID rather than relying only on a similar display name.

Authorize the business: Approve the permissions needed for the Page conversation.

Choose the Page: Match the Page ID and public identity.

Confirm in DripTell: Check the connected Page before enabling routing or automation.

02. Connect the Page from DripTell

Verify the real reply path

Send a message from a test customer profile, reply in DripTell and confirm the message appears in Messenger with the expected sender identity. Assign the thread to another teammate and make sure history stays intact.

The minimum launch test is inbound message, assigned owner, human reply and visible delivery state.

03. Verify the real reply path

Make automation stop cleanly

Use automation for immediate acknowledgement, intent capture and routing, but define the moment a human becomes responsible. When a teammate replies, automated follow-up should pause so the customer does not receive overlapping answers.

Tell the customer when the conversation has moved to a person.

Keep the original question visible during handoff.

Review repeated fallback responses as a workflow defect.

04. Make automation stop cleanly

Recheck access after Meta changes

Page access can be affected by role, password, security and business-asset changes. If delivery stops, inspect the Meta asset and permission state before rebuilding the DripTell workflow.

Save the conversation ID, time and provider error when contacting support.

05. Recheck access after Meta changes

Need help applying this to your workspace?

Send support the workspace, channel, expected result and the exact step or provider state you are seeing.