Resend a real message to test a fix, without touching the source system
Samples allow you to resend on demand. They run through the exact same flow as the original, so you can test a template change, chase down an error, or hand support something concrete to work with.
Not every test needs a brand-new email
Building an email with several variables costs time and effort to get right. Spotler SendPro fixes this by capturing a real message once, so anyone can resend it as often as testing needs.
A snapshot of a real message
A Sample captures the data, content and headers of a message you’ve already sent.
Two ways to create one
Pin an archived message and give it a description, or capture one straight from a message that came back in error status.
Resent through the same flow
Sending a Sample triggers it as a new message from its original source with the same logic applied.
Experience Spotler SendPro in a free 30-day trial
Get started today
A real snapshot, captured two ways
A Sample preserves the exact data, content and headers of a message as it was originally sent. Pin one from an archived message and give it a recognisable description, or capture one directly from a message that came back in error status.
Resent through the exact same flow
Sending a Sample triggers it as if it were a new message from its source, so it’s picked up by the corresponding flow and treated like any other message. That’s what makes it a genuine test, not a simulation.
Other great features in Spotler SendPro
Message Archive
Pull an archived message back up and send it again, without rebuilding it from scratch.
Flows & Flowsteps
A resent Sample runs through the same flow, flowsteps and conditions as the original message.
Dynamic Templates & Attachments
Resend a Sample against an updated attachment template to confirm the fix before it goes live.
Frequently asked questions
What exactly is a Sample?
A message you’ve already sent, captured as a snapshot: its data, content and headers at the moment you create it. It can be resent as a new message from its original source whenever you need to test against it again.
How do I create a Sample?
Two ways. Find an archived message, click the pin icon in the message preview, and give it a recognisable description such as “Webshop Order.” Or take one from a message that came back in error status, which captures the problematic data for analysis.
Do I need the Archive flowstep for this to work?
To create a Sample from an archived message, yes. The Archive flowstep on that flow is what preserves the message data until the moment you pin it. Without an archived copy, there’s nothing to sample from that route (though a message in error status can still be captured directly).
What happens when I resend a Sample?
It’s triggered as if it were a brand-new message from its original source, so it’s picked up by the corresponding flow and treated like any other message. Flowsteps, flow types and conditions all activate normally, unless you’ve deliberately changed something in the meantime.
Do I need to be a developer to use Samples?
No. Samples are built so that anyone can test an email’s behaviour, including marketing or support colleagues who wouldn’t otherwise have a way to reproduce a specific case.
How does this help with support?
A Sample gives support something concrete to work with instead of asking you to trigger your source system again every time it needs testing. That means issues get diagnosed and resolved faster.