Blog
One reminder is enough
Pro can send one nudge if they do not tap. It stops when they reply or tap.
3 minute read
Do this
Keep the change small enough to test from a second account the same day.
- Set the delay from 30 minutes to 20 hours.
- The nudge still has to fit the messaging window.
- Do not add a second nag. The product sends one.
A reminder should rescue a request, not create a sequence
The purpose of a nudge is to help someone finish the action they already requested. It is not a license to keep pitching after they disengage. DripDM’s Pro reminder is one configured follow-up with a bounded delay and cancellation behavior for replies or taps. Keep the reminder directly related to the opening message. If the resource was already useful and clear, the reminder can be shorter rather than adding a new offer.
A workflow to try
Write a gentle follow-up that names the requested resource and the next action without assuming a purchase. Configure the delay, then test three cases: no response, a recipient reply, and a tracked tap. Inspect whether the nudge remains eligible at dispatch. In a comment-led flow, the first private reply alone does not open the general messaging window; without a recipient response, ordinary follow-up permission may not exist. A timer setting cannot repair that missing permission.
Checks before you change the setup
Measure whether people use the destination and whether the wording feels appropriate when read alongside the opening message. A cancelled nudge can be the correct outcome, and WINDOW_LAPSED should not be treated as a copy failure. Do not extend the campaign by adding overlapping reminder rules or moving the send to another account. If the person wants more help, their response is the useful signal to continue a conversation within the active window.
Review the reminder as part of the original exchange
Read the opening message and nudge consecutively to check whether the second adds useful context or merely repeats pressure. A person who already replied should not receive an unrelated automated pitch because an operator ignored the cancellation outcome. Keep the promised resource available and the wording modest. If the reminder was held, preserve the reason and inspect the inbound clock instead of bypassing the hold with another rule. The relevant success is that the customer can finish a requested action comfortably; delivering a second message at all costs is not a meaningful campaign objective.
Questions
Set the delay from 30 minutes to 20 hours. The nudge still has to fit the messaging window. Do not add a second nag. The product sends one.
No. A click can cancel the existing nudge where configured, but it is not a new inbound message. Check the actual conversation window before any later send. Do not confuse stopping a reminder with granting permission for an additional promotional message.
Not necessarily. A reply, tap, or ineligible messaging window can correctly prevent it. Inspect the cancellation or hold reason before changing the message. The goal is a useful requested handoff, not sending at every possible opportunity.