DripTell GuidesChannel guidesProvider updatesDeveloper API

DripTell Guides

Turn website questions into owned conversations without blocking the page.

Install the approved snippet, test it across devices and preserve the page and customer context an agent needs to answer well.

Last verified
August 24, 2026
For
Website owners, support leads and growth teams
In this guide
  • Install the approved snippet
  • Test across breakpoints
  • Preserve page and customer context

01

Decide where chat should help

Choose the pages, operating hours and customer intents the team can support. Chat should not cover important controls, primary calls to action or mobile browser chrome.

  • Name the team that owns new chats.
  • Define online and offline behavior.
  • Choose the page context agents need to see.

02

Install the approved workspace snippet

Copy the web-chat configuration from the intended DripTell workspace and install it through the website deployment process. Restrict changes to authorized website administrators and keep environment-specific identifiers out of public documentation.

03

Test real pages on real screen sizes

Open the site on mobile and desktop, expand the widget, send a message and verify the DripTell reply. Check cookie banners, sticky navigation, audio players, safe-area insets and checkout controls for overlap.

  1. 1

    Open

    Test the pages where the widget is enabled.

  2. 2

    Talk

    Verify inbound, assignment and agent reply.

  3. 3

    Resize

    Check keyboard, orientation and desktop breakpoints.

04

Carry the page context into the inbox

Show the agent the originating page and available session context, then capture only what is needed to continue the conversation. If the visitor provides an email or phone number, apply the workspace consent and identity rules.

  • Keep the source URL visible.
  • Set response expectations when offline.
  • Avoid asking for information already available in the conversation.

05

Protect page speed and accessibility

Load the widget without blocking the main page, expose an accessible control and respect keyboard navigation and reduced-motion preferences. Review Core Web Vitals after deployment.