Detection is only the first decision
An agent can notice a finished task, an upcoming date, or something waiting for a review. That does not mean every event deserves an immediate call. Write down what is worth interrupting for, what can wait, and who is responsible for the next action.
Make the message useful without the session
“The job finished” is less helpful than a task name and one clear next step. Include enough context for a person who is away from the conversation. Keep secrets, credentials, and private logs out of message bodies.
Give escalation a stopping condition
A sensible plan names its first channel, the wait before the next step, and the acknowledgement that stops it. Avoid an open-ended series of interruptions. Decide whether a quiet message is enough before planning a call.
Give your agent a clear next step
Use the MCP tools with your Clerk session to turn context into a reminder proposal. Review the timing, recipients, and message before saving your plan. Simpler agent connections and automated delivery are available soon for paid users.
Start with a reviewable example
Use the reminder workspace to sketch one sequence, then inspect it before building the automation around it. Use the workspace to plan your reminders and export dates to your calendar. Automatic follow-ups are available soon for paid users.