Proactive messages are one of the clearest ways an AI companion can feel present outside the chat window. They are also one of the fastest ways to make the product feel annoying if the system reaches out too often, at the wrong time or for weak reasons.
The core problem is timing. A proactive companion needs to decide not only what to say, but whether this is a good moment to say anything at all.
Start with user-defined quiet hours
No timing model should override explicit user boundaries. Quiet hours, sleep schedules and temporary pause modes should be checked before any proactive message is generated.
These controls create a simple outer boundary that reduces the chance of late-night or contextually inappropriate outreach.
Use event relevance rather than fixed schedules alone
A daily 9 a.m. message is easy to implement but often generic. More useful triggers are tied to meaningful context: a meeting the user mentioned, a goal due today, a trip starting tomorrow or a conversation that ended with an unresolved task.
Event relevance gives the user a clear reason for the AI to appear.
Recency should affect whether the AI speaks
If the user just had a long conversation with the companion, another proactive message an hour later may feel excessive. If the relationship has been quiet for several days, a low-pressure check-in may be appropriate.
Timing models can consider time since last interaction alongside the importance of the trigger.
Frequency caps protect against engagement over-optimization
Even relevant triggers can pile up. A user might have several reminders, content suggestions and relationship events in one day. The system should rank them and respect a daily or weekly cap.
This prevents multiple internal systems from independently deciding to contact the same user.
User response history can tune timing
If a user consistently opens morning messages and ignores evening messages, the system can learn a preferred window. This adaptation should stay within explicit user settings and should not silently increase the overall number of messages.
Response history is a timing signal, not permission for unlimited outreach.
Message importance should affect urgency
A reminder about a user-created task can justify different timing from a casual relationship check-in. Product teams can classify proactive messages by importance and allow urgent user-requested reminders to bypass lower-priority engagement messages.
Commercial promotions should generally remain separate from relationship logic.
Avoid guilt-based re-engagement
Messages such as “Why are you ignoring me?” can create pressure rather than companionship. Re-engagement should be low-pressure and easy to ignore.
After repeated non-response, the companion should reduce frequency rather than escalating emotional language.
Explain the trigger when useful
“You mentioned your interview was today—how did it go?” feels more natural than a generic “I miss you.” Trigger-aware language also helps users understand why the AI initiated the conversation.
This improves both trust and perceived relevance.
Evaluate timing with long-term metrics
Open rate can reward aggressive messaging. Better measures include mute rate, notification opt-out, return conversation quality and whether users keep proactive messaging enabled after several weeks.
Our article on AI companion re-engagement discusses how proactive messages can avoid feeling spammy.
Use a priority queue when several triggers fire together
A mature companion may receive many possible triggers at once: a reminder, a relationship check-in, a content suggestion and a follow-up on yesterday’s conversation. Sending all of them would feel chaotic. The system should rank candidate messages by user importance, urgency, recency and previous response history, then choose only the best one within the frequency budget.
Lower-priority triggers can expire rather than waiting indefinitely. This avoids the unpleasant experience of opening the app and receiving several stale “proactive” messages that were relevant hours ago but no longer fit the user’s current context.
Proactive timing should consider competing real-world contexts
A reminder can be relevant yet still arrive at a bad moment. If the user is in a meeting, traveling, sleeping or already active inside another task, the system should delay non-urgent outreach. Device state, calendar context and recent app activity can help when the user has explicitly authorized those signals.
The important design principle is restraint. More context should help the companion suppress unnecessary messages, not justify more surveillance. Good proactive systems use additional signals primarily to avoid bad timing and to choose fewer, better moments to speak first.
The best proactive message has a reason and a boundary
A companion should reach out when the context is meaningful, the timing fits the user and frequency remains controlled. Proactivity becomes valuable when it strengthens continuity without making the user feel monitored or obligated to respond.