AGGELOS PLATIKOSTAS

Back to Home

Reminders that can't break the rules

Reminders that can't break the rules

The problem

The problem

Campaigns needed a way to follow up. If someone reads a message but doesn't reply, the agent should send a reminder after a chosen time. The catch is compliance: you can send at most three reminders in a week, so the design had to keep people inside that limit.

Campaigns needed a way to follow up. If someone reads a message but doesn't reply, the agent should send a reminder after a chosen time. The catch is compliance: you can send at most three reminders in a week, so the design had to keep people inside that limit.

The solution

The solution

I built reminder setup into the agent's settings. You pick how long to wait and which message to trigger, and you can stack up to three. Once you hit the limit, the option to add another disappears, so the rule is impossible to break.

I built reminder setup into the agent's settings. You pick how long to wait and which message to trigger, and you can stack up to three. Once you hit the limit, the option to add another disappears, so the rule is impossible to break.

Two choices make a reminder

Each reminder is two decisions: how long to wait after the last message, and which message to send. You pick a delay from ten seconds up to a day, then choose the node that gets triggered.

Add another for a longer nudge

One reminder is rarely enough, so you can add another and set a longer delay. A plain line under each row spells out what will happen, and small preview and delete controls sit on every row.

Compliance caps reminders at three in a week. Rather than letting someone add a fourth and blocking it with an error, the Add another button simply disappears once the third reminder is set. Two reminders still show the button; the third removes it, so the limit lives in the layout with nothing to get wrong.

AGGELOS PLATIKOSTAS

Back to Home

AGGELOS PLATIKOSTAS

Back to Home