Before sending more email, test whether a different delay would make the message more useful. Prepare one approved creative in Migma, keep it consistent across the timing paths, and ask the Klaviyo journey owner to define a controlled comparison.
This guide is published by Migma for lifecycle teams that want a practical test brief, rather than a universal frequency rule. Official guidance was checked on October 15, 2026. The sample experiment is a planning example, not a measured result or a promise that fewer messages will increase revenue.
Define the decision before choosing a schedule
Write down what the team needs to learn. “Should the second setup reminder arrive sooner?” is more useful than “How often should we email everyone?” The first question identifies a message, a customer state, and a change that can be reviewed.
Klaviyo's recent Criquet Shirts interview offers a timely reason to question send volume. Treat the brand's experience as a prompt for your own investigation, not a forecast for your account. Its reported results do not establish the right schedule for a different audience.
For the proposed test, choose a setup reminder for people who have started an account but have not completed one defined task. Record the task, the current delay, the proposed alternative, and the reason the alternative might help. Avoid changing the offer and the delay together; the result would be difficult to interpret.
Approve one message in Migma
Start with the reviewed brand context, then give Migma the task, approved product facts, and next action. Ask for a short reminder that helps the reader resume work. Do not assume that a person who has paused setup needs a discount or a stronger sales pitch.
A useful brief might say: “The reader has created an account but has not finished the workspace setup. Explain the next step, link to the correct setup destination, and offer a support route. Do not claim that the team has already joined.” These are example instructions; the data owner must confirm the actual eligibility rule.
Keep the creative version stable across both timing paths. Review the subject, preview text, action label, layout, and optional-name fallback together. If the design changes halfway through the test, log the change and decide whether the comparison is still meaningful.
Run Email Preflight, fix relevant warnings, and rerun it. The check helps with creative quality and common sending risks. It does not prove that the selected audience is correct or that the timing experiment is valid.
Separate delay testing from frequency limits
Klaviyo's official flow-frequency guidance describes testing branches with different delays while keeping the message content identical. It also explains Smart Sending as a limit on how many messages a person can receive within a period. Those controls answer different questions.
A delay test asks which timing works better for this flow. A frequency limit can cause an otherwise eligible message to be skipped because another message was sent recently. If one path encounters more skips, the team needs that context when reading the result.
Have the journey owner record the actual settings on every affected message. Do not assume that all prebuilt flows use the same defaults. Preserve the existing campaign and flow safeguards unless the responsible owner explicitly changes them for a documented reason.
Use a brief that both owners can sign off
| Test element | Record before activation |
|---|---|
| Reader state | The unfinished task and entry rule |
| Change | Current delay versus one alternative |
| Creative | One approved Migma version used in both paths |
| Exit | What happens when the task is completed |
| Other exposure | Relevant campaigns, flows, and frequency limits |
| Evaluation | Outcome, observation period, and review owner |
Let the Klaviyo owner configure the test using the current account controls. The designer's responsibility is to supply the same reviewed message and identify any content that becomes inaccurate after a longer wait. “Finish today's setup” may no longer make sense several days later.
Use Migma's export workflow to hand over the approved creative, then check the destination version. Template export and audience selection are separate actions. Confirm the actual subject, variables, sender, and timing where the message will run.
Test people who should leave the flow
The important edge case is someone who completes the task during the wait. Decide whether that person should receive a different message or no reminder at all. Then have the journey owner test the configured behavior with controlled profiles.
Also review a repeat entry, missing optional data, and a person who recently received a separate campaign. These scenarios can reveal that the observed difference comes from routing or suppression rather than the delay itself.
Record both expected and observed behavior. A good-looking preview cannot show whether the wrong people were selected. A correct branch split cannot show whether the email's action works after it arrives.
Read the result before creating the next version
Compare the agreed outcome over the agreed observation window. Include actual sends and skips, relevant engagement, completed tasks, and negative signals that your team can reliably measure. Avoid selecting a winner from the first encouraging movement in an open-rate chart.
If the evidence is inconclusive, say so and decide whether another test is worth the audience exposure. Do not turn a small or noisy result into a company-wide frequency rule.
Bring the reviewed finding back into the next Migma brief. Migma's results documentation describes a human-reviewed improvement loop and explicitly says Migma does not choose an A/B winner automatically. Keep the final timing decision with the team responsible for the journey.
Frequently Asked Questions
Is a delay test the same as Smart Sending?
No. A delay test compares when a flow message is sent. Smart Sending limits message exposure within a period and may cause skips. Review both when interpreting a test.
Should the design change between timing paths?
Keep the reviewed creative identical when the question is timing. If the copy or offer changes too, you cannot confidently attribute the observed difference to the delay alone.
What if a person completes setup during the wait?
Define the intended exit behavior before activation, then test it with controlled profiles. A reminder should remain appropriate when the person's state changes.
Does Migma automatically decide the winner?
No. Current Migma results documentation says a person chooses the A/B winner. In this workflow, the journey owner also retains responsibility for Klaviyo timing decisions.