Skip to main content

​
What it is

Playbooks are Sippet’s structured automation layer for operational support work. Use them to:
  • follow up after conversations
  • run callback or reminder flows
  • target contacts or groups with repeatable logic
  • track run outcomes and failures over time

​
In the console

The Playbooks area includes:
  • draft, running, paused, and archived playbooks
  • run history and status details
  • target selection by contact or group
  • reviewed launch batches with a contact limit or all eligible contacts
  • a batch workspace with per-contact enrollment and live outreach results
  • batch pause, resume, and cancellation controls
  • failure and outcome review

​
Key concepts

  • Playbook status: whether the automation is editable, active, paused, or retired
  • Run history: the execution record for each contact or target
  • Launch batch: a frozen cohort and published version, with a durable enrollment result for every reviewed contact
  • Enrollment progress: whether selected contacts have been enrolled, skipped, failed, or cancelled; outreach may continue after enrollment completes
  • Cadence: how often or when a playbook should run
  • Outcome tracking: the final state or result captured by the workflow

​
When to use it

  • repeated outreach after calls
  • structured callback commitments
  • nurture, reminder, or re-engagement sequences