Automated Marketing for Your Slowest Day
Ask a merchant if they market on their slowest day and most will say yes, meaning they mean to. Tuesday's the quiet one, they know it, and they have a vague plan to post something or send an email that morning. What actually happens most weeks is nothing — the day arrives, the counter's quiet, and the reminder that was supposed to go out competes with restocking, a scheduling problem, or just not thinking of it until the slow day is already over. That's not a discipline failure specific to any one owner. It's what happens to any task whose entire trigger is "remember to do this, on your own, every single week, forever," with no system enforcing it.
The manual version basically doesn't happen
Write it out and the manual version is genuinely three separate habits stacked on top of each other: notice which day is quietest, remember it's that day again this week, and actually write and send something before the day's over. Any one of those slipping breaks the whole chain, and for a small independent business already running the counter, the schedule, and the ordering, a self-imposed weekly marketing task is exactly the kind of thing that survives for two or three weeks and then quietly stops. Nobody decides to abandon it. It just loses to whatever's more urgent that particular Tuesday, and by the fourth week there's no reminder happening at all — the slow day is still slow, and now it's also not being addressed.
What Ruffus does instead
The part that has to be a merchant's judgment call — which day is actually slow — stays a merchant's judgment call. There's a simple picker in the dashboard: pick one day of the week that's reliably quiet for your business. Ruffus doesn't infer this from your sales data or try to detect a pattern on its own; you're telling it something you already know about your own business, once. From that point forward, on that day of the week, Ruffus automatically sends every consented, active-membership customer an email and a push notification — something in the spirit of "today's a quiet one, it's a good day to stop by and keep collecting stamps." The writing, the remembering, and the sending are the part that gets automated. The one input a merchant supplies is a single decision, made once, not a weekly action item that has to survive an entire year of Tuesdays.
A broad nudge, not a targeted one
It's worth being precise about what this send is and isn't. It goes to the merchant's whole active, consented customer base for that day — not a segment picked by recent activity, spend, or anything else. That's a different shape than the two other automated touchpoints Ruffus runs: a win-back message triggers off a specific customer having gone quiet, and a birthday message triggers off a specific date tied to a specific person. Both of those are behavior- or identity-driven — they exist because of something true about one customer. The slow-day send is calendar-driven instead: it doesn't ask what any individual customer has been doing, only what day it is and whether it's the merchant's chosen day. It's a broad, light-touch nudge aimed at smoothing out a predictable dip in foot traffic, sitting alongside the narrower, individually-targeted messages rather than replacing them.
Why it won't fire every week regardless
The cadence has a floor built in: once a slow-day send goes out, it won't fire again for at least six days. Practically, that keeps it to a weekly rhythm at most, tied to whichever day the merchant picked — a customer isn't getting a "come by" nudge twice in the same week just because a merchant reconfigured something or a schedule shifted oddly. It's meant to read as a single, predictable weekly touchpoint, not a channel that can be triggered repeatedly. A café with a dead Monday morning and a barbershop with a dead Wednesday afternoon both get exactly one shot at this per week, on the day each of them chose — not a lever either one could lean on harder.
Setting it up
There's no separate onboarding step for this and nothing to configure beyond the one choice. It lives in the same dashboard as the rest of a merchant's loyalty program — the pricing page covers what's included at each plan tier, but the slow-day picker itself is just a setting, not an add-on with its own signup. Once it's set, it runs without anyone needing to log in and trigger it that week, or any week after. A merchant can change the day later if their slow day moves — a new competitor opens, a delivery-app promotion shifts the traffic pattern, whatever it is — but there's no ongoing task to keep the thing running once it's configured.
What it doesn't try to be
This isn't a replacement for actually understanding your customers, and it isn't pretending to know something about your business that you haven't told it. It doesn't analyze your point-of-sale data, doesn't guess which day is slow from stamp-collection patterns, and doesn't try to get cleverer than "the merchant said Tuesday, so send it on Tuesday." That's a deliberate scope decision, not a missing feature: a slow day is something an owner already knows, usually within the first month of being open, and building a detection system to rediscover what they'd tell you in one sentence would just be a slower, less reliable way of asking. The automation is entirely in the remembering and the sending — the two things that actually fail when this is done by hand.
The short version
Nothing about a merchant's slowest day is hard to identify — most owners can name it without thinking. What's hard is doing something about it every single week, indefinitely, with no system backing up the memory. Ruffus turns that one identification into a one-time setting: pick the day, and from then on every consented, active customer gets an email and a push nudge on that day, automatically, at least six days apart from the last one. It's not trying to read your sales data or replace the win-back and birthday messages that respond to what one customer is actually doing — it's the calendar-driven counterpart to both, aimed at a predictable dip rather than any one person's behavior, running on a day the merchant chose and never has to remember again.