Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.encoreos.io/llms.txt

Use this file to discover all available pages before exploring further.

Overview

Automated follow-up sequences let CE teams enroll leads into a timed set of email, SMS, and task steps. Sequences can be manually triggered from a lead record or automatically enrolled when sequence criteria match.

Permissions

  • ce.sequences.view: view sequence list and detail pages
  • ce.sequences.create: create and clone sequences
  • ce.sequences.edit: edit sequence settings and steps
  • ce.sequences.delete: archive sequences
  • ce.enrollments.view: view enrollment status and progression
  • ce.enrollments.create: enroll leads and bulk enroll
  • ce.enrollments.edit: pause/resume/exit active enrollments

Build a Sequence

  1. Open Community Engagement -> Sequences.
  2. Select Create Sequence.
  3. Configure:
    • Sequence details (name, description, exit behavior)
    • Step timeline (email/SMS/task order and delays)
    • Analytics and enrollment settings
  4. Save the sequence, then activate it when ready.

Enroll Leads

  • From a lead detail: use the Enroll in Sequence action in Sequence Status.
  • Bulk enrollment: select leads and use the bulk enrollment dialog.
  • Auto-enrollment: set auto_enroll and enrollment_criteria on the sequence.
sequence_batch_limit in CE module settings limits bulk enrollment size.

Runtime Behavior

  • Executor runs every 15 minutes (pg_cron) and processes due active enrollments.
  • Idempotency is enforced with ce_sequence_outbound_executions.
  • CE-16 suppression checks are mandatory before outbound sends.
  • If suppression data is unavailable, executor fails closed and logs compliance_unavailable_stub.

Exit Conditions

Enrollments can exit automatically or manually:
  • Reply
  • Call
  • Conversion
  • Opt out
  • Manual exit
  • Suppressed
  • Completed

Troubleshooting

  • If steps are skipped with compliance_unavailable_stub, verify CE-16 suppression availability.
  • If bulk enrollment fails, reduce selection to the configured sequence_batch_limit.
  • If no sends occur, confirm:
    • sequence status is active,
    • enrollment status is active,
    • next_step_at is due,
    • required contact channel data exists.