Docs: Campaign chaining — auto-enroll after completion (BMO-3707)

[haleyserrano]

JIRA

BMO-3707 — Campaign Chaining: Auto-Enroll Completed Recipients into a Follow-Up Campaign (v1)

Classification

• Type: UI/UX change + feature behavior change
• Product impact: Business App (Yesware campaigns)
• Repo(s) targeted: Business App docs only. No Partner Center-facing workflow is affected by this story, so no Partner Center PR was opened.

Summary of documentation updates

Updated docusaurus/docs/yesware/campaigns/creating-campaigns.mdx:

• Added an "After completion" bullet to the Step 2 "Configure campaign settings" list and to the "What's included?" overview list.
• Added a new subsection, "Automatically enroll recipients in a follow-up campaign after completion," covering: how to set the follow-up campaign and delay, that only recipients who complete every touch without replying/connecting/booking a meeting are enrolled, that the follow-up campaign's own touch-1 timing applies on top of the delay, opt-out/bounce suppression, cycle restrictions, and that cloning a campaign does not carry the setting forward.
• Added an FAQ entry for discoverability.

Existing docs updated — no new page created.

Placement reasoning

creating-campaigns.mdx already documents "Configure campaign settings" (Step 2), including the sibling setting "Remove recipients after connection." The new "After completion" setting is part of the same campaign-settings surface, so it was added as a subsection there rather than a new page, consistent with the "prioritize updating existing documentation" rule.

Acceptance criteria coverage

Mapped from the story's functional ACs to end-user-relevant behavior only (internal/implementation ACs — audit rows, metrics, idempotency, availability plumbing — are not user-facing and were intentionally omitted):

AC	Covered
Owner can set/update/clear the follow-up campaign and delay	✅ "To set this up" steps
Enrollment happens only on completion without response, after the delay, with target's touch-1 timing applied on top	✅ Main explanation paragraph
No other exit reason (reply, bounce, call connect, manual removal, opt-out, meeting booked) triggers chaining	✅ "Recipients who reply, connect by phone, or book a meeting..." line
Past opt-out/bounce suppression	✅ Info callout
Cycle protection	✅ "Keep in mind" bullet
Cloning does not carry forward chain config	✅ "Keep in mind" bullet
Re-enrollment allowed	✅ "Keep in mind" bullet

Figma / visual inputs

None were provided with this ticket; documentation was written from the JIRA description, acceptance criteria, and dev comments only. No UI screenshots were available to add, so none were added — flagging this as a limitation if screenshots become available later.

Skills used

• pre-push-validation (frontmatter, tag/callout balance, links — all passed on the single changed file)

Assumptions and limitations

• Rollout status flagged, not blocking: BMO-3707's parent epic (BMO-2571, "Yesware Enhancements (2026)") is still in To Do and labeled Product-Roadmap. Per rollout-verification process, I checked the epic's other open children for gating/eligibility tickets specific to this feature and found none — the other open siblings are unrelated Yesware workstreams (recipient blacklist, sync health check, usage stats, campaign sharing, unsubscribe productization, daily recipient cap, Gmail CRM sync/SF indicator). BMO-3707 itself shows all 26 linked PRs as merged, so proceeding was judged reasonable, but the epic's incomplete status is noted here in case rollout is still pending.
• The story's campaign_chaining availability gating (WAMPA2, enabled per-account) is an internal rollout mechanism and was intentionally not mentioned in the user-facing doc, per the no-internal-references rule.
• No source material described a UI label for the delay input beyond "Wait [N] days before starting the next campaign," which was used almost verbatim.

---

@ahnikakuse @haleyserrano @maryam6samadi

---

Generated by Claude Code

[rileywiebe]

Just a note here, they will not move to the follow up campaign if they've connected and this setting is enabled:

If they disable that setting, they will get added to the follow up campaign even if they've connected.