A reminder helps only when it is specific, timely and immediately actionable. Send it because the recipient still has a relevant action, not simply because a calendar date is approaching. Name the record, task, deadline and safe link, and prevent repeats within an agreed cooldown period.
Too many notifications teach clients to ignore portal emails. Too few shift follow-up to phone calls. The right frequency depends on task risk, time remaining and channel preference, rather than one universal setting.
First make recipient selection reliable
Before sending, check that the task remains open, applies to the record and is accessible to the client. Yindle Portal counts only published questionnaires towards progress, does not treat excluded questions as overdue and limits how soon another questionnaire reminder can be sent.
A summary of the previous day can also combine new messages from people, audience-specific documents, updates and approaching deadlines. Project-wide documents are not automatically included in every summary component. Test which events your chosen overview actually covers.
Choose the channel by urgency
Use a daily or periodic digest for information changes that can wait together. Use an immediate notification for a specific, time-critical action or a decision blocking work. A dashboard badge helps when someone returns, but does not reach them outside the portal.
Never send ‘Something is waiting for you’ without context. It forces recipients to log in to discover whether it matters. Include enough to judge priority, but do not place sensitive content in email unnecessarily.
Worked example: fictional handover inspection
In this fictional example, inspection company KijkGoed asks residents to choose a time slot. Seven days before the deadline, only those who have not chosen receive a first reminder. A shorter message follows two days beforehand. Anyone who has since submitted is excluded at each send.
A resident with an exceptional deadline receives messages based on that personal date. The dashboard shows the same date. After the deadline, there is no third threatening email, but an instruction to get in touch. The reminder remains part of the workflow rather than a separate pressure campaign.
Use a reminder canvas
Complete six fields for each reminder:
- Trigger: which open status and which point in time?
- Exclusion: who must not receive this message?
- Subject: which record and which task?
- Action: where does the recipient land after clicking?
- Frequency: minimum time before another notification?
- Escalation: what happens if there is no response?
Have privacy and security colleagues review email content. A safe link and minimal context matter more than a complete record summary in the inbox.
Measure usefulness, not sending volume
A high volume of sent emails is not success. Look at how many recipients then complete the intended task, how many unsubscribe and how many support questions the reminder causes. Never compare audiences without considering difficulty and time remaining.
Experiment with subject lines and timing first, not higher frequency. Ask a small group why they did not act; a document may be missing or the task unclear. Better explanation then helps more than another notification.
Account for several users sharing the same record. Reminding everyone can cause duplicate work. Decide whether the message goes to one primary contact, all authorised users or only the person who started the draft. Show in the portal whether a housemate or colleague has already completed the task.
Channel failure is another edge case. An undelivered email does not make the task disappear. Make delivery problems visible to administrators without placing sensitive content in logs. Use an alternative channel only under prior consent and agreements; automatically trying ever more channels can quickly feel intrusive.
Schedule a quarterly notification review. Compare all active triggers and identify combinations that may occur on the same day. Combine messages where possible, remove outdated notifications and check that every link still opens the intended task. This keeps the policy manageable as new portal components are added.
Read more about the central client environment on Yindle Portal and the broader approach in building a customer portal. To design a notification policy, map one open-action workflow with Yindle.