Run DripTell as an operating system, not another inbox.

These guides explain the decisions behind setup and daily operations so teams can adapt DripTell to a real customer journey.

Run DripTell as an operating system, not another inbox.

Start from the customer moment.

Choose the guide that matches what the customer is trying to do, not the software screen an operator happens to be using.

  • Shared inbox assignment rules
  • Inbox priority queues
  • Inbox service-level management
  • Conversation tags
  • Contact custom fields
  • Duplicate contact management
  • Lead stages and pipeline design
  • Lead source attribution

Make the operating decision explicit.

Each guide defines the trigger, evidence, owner, next action, human boundary and practical measure before discussing automation.

  • WhatsApp template approval operations
  • WhatsApp opt-in management
  • Campaign audience segmentation
  • Campaign delivery failure handling
  • Campaign reply routing
  • Automation trigger design
  • Automation to human handoff
  • Automation loop prevention
  • AI agent knowledge setup

Keep proof and recovery visible.

Use customer state, source events, official platform references and clear exception handling so teams and machines can explain why an action occurred.

  • AI agent confidence thresholds
  • AI agent escalation rules
  • Role-based workspace access
  • Audit log review
  • Webhook retry handling
  • API rate-limit planning
  • Inbox performance reporting
  • Campaign return reporting

Questions teams ask before they connect the workflow.

Are these operations guides product documentation?

They combine DripTell operating guidance with clearly identified third-party and standards references. Current product availability should be confirmed on the relevant product or integration page.

Can the workflows be adapted to different teams?

Yes. The decision model remains useful while fields, owners, timings, permissions and exception rules are adapted to the business.