How to Test an Email Workflow Before Going Live
Test an email workflow at three levels: the rendered message, one contact’s path, and a representative audience running through the full timing and logic. In SendOps, shadow mode rehearses a workflow on real contacts while recording external effects instead of performing them.
By SendOps · Updated
First, test what arrives in the inbox
Preview each email with representative data, including missing optional values, longer names, and realistic action URLs. Check that the promised next action leads to the correct place in the product.
Send a test to your own team’s inboxes. Confirm the sender identity, links, layout, and personalization. A message preview proves the content, not the audience logic: you still need to test the journey.
Walk through the meaningful paths
List the situations the campaign must handle. For onboarding, that includes a fast activator, someone who never starts, an unsubscribed contact, and a person whose key attribute is missing.
Check entry, waits, branches, and exits for each case. Pay attention to unknown data: a missing value may behave differently from a known value that does not match. Define the intended behavior explicitly.
- A contact who matches the entry trigger.
- A contact who converts before the first follow-up.
- A contact who unsubscribes halfway through.
- A contact subject to a frequency cap.
- A contact with missing personalization or activity data.
Rehearse the webhook paths too
If a journey includes SMS, push, or another external action, test both a successful webhook response and its failed branch. Include contacts without an eligible phone number or registered device, and confirm your service handles channel consent.
Check that a failed call leads to the intended fallback email, and that activities reported by your service reach the right contact. A successful webhook acknowledgement means your service accepted the request; use a recorded activity when the workflow needs to know that someone opened a push or completed a purchase.
Rehearse the audience in shadow mode
SendOps shadow mode runs the actual workflow timing and evaluates branches for enrolled contacts. It records sends and other external effects rather than performing them. The workflow is active and enrolling during rehearsal, even though customers do not receive the emails.
Choose a fixed cohort list to bound the rehearsal. Review enrollments, recorded sends, consent filtering, and the timeline for individual contacts. Compare what the workflow would do with what the team intended.
Treat going live as a separate decision
Review how many contacts match without the rehearsal cohort. Decide whether the real launch should enroll only future matches or include existing contacts. The audience size in your test does not predict the full backfill.
Going live ends the shadow runs and switches to real enrollment. Check approval settings and review the first sends. If the campaign needs to stop progressing, pause it rather than assuming a past rehearsal still protects live contacts.
Keep a record of what changed
Use workflow version history to connect each change with its reason. Existing SendOps journeys remain on the definition version they enrolled under, so inspect that version when investigating an unexpected step.
After a meaningful edit, repeat the checks affected by that edit. A copy adjustment needs a content review; a new branch or entry condition needs a path and audience review too.
Common questions
Does shadow mode send any email?
No. It records what the workflow would do while suppressing external effects. Real contacts can still enroll and move through their rehearsal timelines.
Is a test email enough to validate a workflow?
No. It checks rendering and delivery to the test inbox. It does not verify entry conditions, branching, exits, timing, or the size of the real audience.
Do existing journeys change when I edit a workflow?
SendOps pins each journey to the definition version it enrolled under. Review that version when debugging a contact already in progress.
Keep building
Product references: workflow documentation and shadow mode. The example timing and message ideas are editorial starting points to adapt to your product.