Follow-Ups That Send Themselves
Automation sequences in Muin: a thank-you now, an impact note in a week, an invitation next month, with every queued send visible and stoppable in one place.
Most organizations know what the follow-up should be. A first-time donor should hear thank you today, see what their gift did in a week, and get an invitation next month. A new volunteer should get a welcome, then the orientation details two days before they turn up.
The problem is never the plan. It is that step three happens when somebody remembers, which is to say it mostly does not happen.
Automation sequences in Muin exist to take that off a person. You set the steps and the gaps between them once, and anyone enrolled moves through them on schedule.
Building one
The fastest route is the broadcast composer. Write the first message as you would any broadcast, pick the audience and the channel, then choose Drip sequence under Send Options. That first message becomes step 1 and goes out on enrollment.
Each follow-up below it takes three things: a channel (email, SMS or WhatsApp), a delay in hours or days, and the message itself. Click Launch Sequence and Muin tells you how many people were enrolled across how many steps.
A sequence sends on a single channel per step, which is why the drip option is unavailable while more than one channel is selected. You can still mix channels across steps: an email today, an SMS in three days.
For something more structured, the sequence editor has the full set of step types: Send Message, Send Template, Delay, Condition, and Wait for Reply. A Wait for Reply step holds the sequence until the person answers, which is the difference between a sequence and a schedule.
Two defaults worth keeping
Every sequence carries two switches that are on by default, and both are there because of how follow-ups go wrong.
Stop on reply. The moment someone answers, they drop out of the sequence. Nothing is worse than a donor writing back with a question and receiving step 3 of the drip the next morning as though nobody read it.
Respect business hours. A step due at 3 a.m. waits for your business hours instead. A reminder that lands in the middle of the night reads as a machine, because it is one.
A new sequence also starts switched off, so building it and launching it are separate decisions.
Templates, so the wording is reviewed once
A Send Template step pulls from your message template library: the thank-you, the event reminder, the volunteer welcome, written once and reused. Variables go in double curly braces, and the editor lists every variable it finds in your subject and body so you can see what the template expects before you activate it.
If you have fewer than three templates, Muin offers starter kits matched to your organization type. Each one is created as a draft so you edit the wording before it ever sends.
One thing to know: a template is read at send time. Editing it changes what every live sequence step will send from that moment on, which is usually what you want and occasionally a surprise.
The part that matters most: you can stop it
Automation is only comfortable if you can see what it is about to do. Communications → Scheduled Messages lists everything queued to go out in your organization’s name, with the recipient, the kind of message, the channel, when it sends, and a status. Each queued row has a Stop this message button.
Muin checks the queue every five minutes, so a message scheduled for 10:00 goes out between 10:00 and 10:05. That is your window: once a pass picks it up the row reads Sent, and a sent message cannot be unsent.
Rows settle into one of five states, and the distinction between two of them is worth learning. Failed means the send was attempted and rejected, with the reason on the row. Skipped means Muin chose not to send: the person has opted out of marketing and announcement emails, or their address is suppressed after a hard bounce. A skipped row is the consent machinery working, not an error.
To take one person out of a sequence entirely, open its Enrollments tab. Pause holds their next send only. Stop removes them permanently, and re-enrolling them later starts at step 1.
Who gets enrolled
Sequences are pointed at audiences. An audience is a saved group built from a rule: “donors in Texas who gave last year”, described in plain language and turned into conditions you can inspect. You see exactly who matches before you save it, and Muin recalculates a rule-based audience every night, so the list your next send reaches is current rather than one somebody assembled by hand in March.
That matters more than it sounds. The reason follow-up series decay is that the list goes stale while the sequence stays live.
What it is not
A sequence is not a broadcast. A broadcast is one send to many people, tracked, with unsubscribe handling. A sequence is a series over time, and it drops people as they reply, unsubscribe, or are stopped by someone on your team.
It is also not a replacement for a conversation. If a donor asks you something, answer it from the inbox. The sequence steps out of the way as soon as they do.
Where to start
- Automation Sequences for the steps, triggers and enrollment controls
- Message Templates for the wording a step sends
- Scheduled Messages for what is queued, and how to stop it
- Audiences and Segments for choosing who gets enrolled