Sequences and automated follow‑ups

Purpose

Fulreach sequences deliver timed multi‑step outbound once a prospect qualifies—classic pattern: invitation accepted → paced voice note / nurture messages → richer media follow-ups configurable per tenant.

Architecturally Fulreach merges PostgreSQL-scheduled authoritative rows (when each attempt may fire & deduplication uniqueness) plus workers guaranteeing attempts with backoff & observability—not something you tune directly, but it explains pacing latency (poll intervals, queue depth).

Sequences respect campaign send windows and capacity math (campaign-wide throughput while maintaining per-sequence lanes so two templates don’t stampede the exact same timestamps).

Only certain automated formats historically ship end-to-end in workers (automated AI audio path matured first); text/visual sequence types beyond audio may remain planned—verify tenant feature flags/UI.

Catch-up weekdays

Fulreach optionally widens allowable weekdays for sequence follow‑ups separately from rigid invite weekday windows (“catch‑up days” JSON). Saturdays often implicitly allowed for backlog catch-up legacy behaviour—consult campaign JSON if diagnosing weekend sends unexpectedly.

Stop-on-reply safeguards

Fulreach monitors LinkedIn conversational webhooks cancelling pending automated steps intelligently depending on funnel Stage A/B/C:

• Prospect truly replies inbound → queued/sending future automation for incompatible stages cancels to avoid blasting someone mid-conversation.
• Outbound manual message from seat owner can preempt automation for that participant.

Edge nuance documented internally: distinguishing automated outbound identifiers vs manual ones prevents cancelling the wrong branch (e.g. Stage B thumbs-up triggered first video step must persist until delivered).

Operational takeaway: unexpected silence after prospect engagement often means safeguards tripped deliberately—inspect sequence row states & cancellation reasons surfaced in dashboards / support tooling.

Retries vs terminal failure

Retries apply for flaky provider outages; deterministic profile issues mark failure without endless loops.