DripTell GuidesChannel guidesProvider updatesDeveloper API

DripTell Guides

Move Snapchat interest into a customer record with a next step.

Verify the supported account connection, test the available customer path and define how the team owns a conversation after it leaves a short-lived social moment.

Last verified
August 24, 2026
For
Social commerce and customer experience teams
In this guide
  • Verify business identity
  • Test supported interactions
  • Assign the next action

01

Confirm the account and operating use case

Use a business-controlled identity and decide which customer interaction should enter DripTell. Supported access depends on provider account eligibility and permissions; use the live connection state as the authority for the account.

  • Confirm current administrators.
  • Document the supported interaction type.
  • Name the team that owns the first response.

02

Authorize the correct business identity

Begin from DripTell channel settings, review the provider permissions and select the intended Snapchat business identity. Confirm the account details after returning to DripTell.

  1. 1

    Authorize

    Use a business administrator and review access.

  2. 2

    Select

    Match the public identity and provider identifier.

  3. 3

    Confirm

    Verify the account displayed in the workspace.

03

Prove the supported customer journey

Create the supported interaction from a test account, confirm it reaches the right workspace and complete the available response or follow-up path. Record any account-specific limitations for agents.

04

Turn a short social moment into durable context

Capture the customer need, available identity, owner and next action in DripTell. If the conversation moves to another channel, keep permission and source context attached so the customer is not asked to start again.

  • Assign ownership before follow-up.
  • Keep the source visible.
  • Use only the customer details needed for the next action.

05

Review access after provider or account changes

Recheck the integration when business roles, authentication or provider permissions change. Preserve timestamps and provider identifiers before reconnecting.