Separate direction from ownership
A commitment can be outgoing, incoming, or mutual. “I will send it” and “You will send it” lead to different follow-ups. Verify the speaker and recipient before relying on an extracted action.
Check the date
A due date makes a promise actionable, but relative phrases need the conversation date. Review “tomorrow,” “next week,” and tentative dates before accepting them. A task’s planned date and its deadline are different concepts.
Reminders depend on configuration
The follow-up scheduler supports local notifications for pending commitments and escalation of overdue items. Notification permission, available dates, and app execution affect what appears. A past reminder time does not become a guaranteed new notification.
Suggestions still need judgment
The app can suggest re-engagement for stale contacts. Decide whether that is appropriate to the relationship and context. A reminder is an invitation to act, not proof that an action has been completed or a message has been sent.
Close the loop
Mark completed work accurately and review open commitments. Apple Reminders integration is a separate configured path; creating a local task does not universally imply that an Apple Reminders item was created.
Try it with a sample
- Review the extracted owner, recipient, and due date.
- Check notification permissions for the reminder you want.
- Complete the item only after the real task is finished.
About this explanation
Reviewed against Modules/Assistant/Shared/Services/FollowUpScheduler.swift. Examples use fictional people and content. Availability depends on the build, edition, permissions, and selected services. Source changes trigger a review notice and removal from website AI retrieval until reviewed.