Contextual Reminders

Why It Matters

A follow-up is easiest to understand while you are looking at the candidate conversation or security report that created it. Contextual reminders keep that link: Kit records what needs to happen, when it is due, and which teammates need the prompt without copying the work into a separate task system.

Reminders are internal. Candidates and security researchers cannot be selected and never receive them.

These are reminders your team creates for itself. They are separate from Kit’s automatic candidate anti-stall emails, interview notices, training deadlines, and security escalation schedules.

Set a Reminder from Your Current Work

Open an identified Hiring application or an accessible Security report, then:

1. Open the quick menu with Cmd+K or Ctrl+K.
2. Search for reminder and choose Add reminder.
3. Write one concrete next action, or choose Draft reminder with AI.
4. Set the due date and time.
5. Select the teammates who should receive it.
6. Leave Also send email off for an in-app reminder only, or turn it on for both channels.
7. Choose Set reminder.

The action appears only when you can still use reminders for that record. For example, an anonymized application does not offer it.

Let AI Draft the Whole Reminder

Draft reminder with AI can propose all three parts of the reminder:

• The short reminder text
• A future local date and time
• The teammates who should be included

For a Hiring application, Kit supplies the candidate, role, stage, and recent email conversation as context. For a Security report, it supplies the report and recent conversation. The model may select only teammates who can access that record, and the creator is always included.

The result is a draft, not an automatic save. Review or undo the proposed wording, date, and people, then choose the email setting yourself. Reminder text is plain text and limited to 280 characters. Drafting uses your account’s configured AI provider and credit limit.

Choose Who Gets It

Open People to select eligible teammates. You can also type @ followed by a teammate’s name or email and choose Add. Mentioning someone selects them as a recipient and inserts the mention into the reminder text.

Only teammates who can currently open the candidate or report are available. Restricted-record access and vertical membership are enforced both when you save and when Kit delivers the reminder.

Delivery Choices

Choice	What happens when it is due
In-app	Always enabled. Every selected teammate gets one notification linked to the exact reminder.
Email	Optional. Sends one internal email and follows Hiring activity or Security program activity, plus Holiday Mode and weekend rules.
Download .ics	Manual five-minute private calendar snapshot. It is not attached or sent automatically and does not invite attendees.

Email preferences, Holiday Mode, and weekend notification rules are checked at delivery time. Turning off email does not turn off the in-app reminder. If a module subscription temporarily lapses, Kit keeps the reminder and checks again later; it does not discard the selected people.

Calendar Copy

From Reminders, choose Download .ics to add a private calendar copy. The event contains the reminder text, due time, context label, and a sign-in-protected link back to the exact reminder. It does not add attendees or send calendar invitations to the selected teammates.

The .ics file is a snapshot. Editing or completing the Kit reminder does not update an event already imported into another calendar.

Edit and Complete

The Reminders page separates upcoming work from completed history. From there you can:

• Mark a reminder done or reopen it
• Edit the wording, people, or email choice
• Reschedule it to a future local time
• Delete a reminder you created
• Download its calendar copy

Any participant can mark a reminder done or reopen it. Only its creator can change or delete it. Moving the due time starts a new delivery occurrence. Once a reminder is overdue, the creator can still correct its wording, people, or email choice without changing the original due time; choosing a new time still requires a future value. Kit rechecks record access before delivery and withholds the reminder from anyone whose access has been revoked.

Use Reminders through MCP

Connected AI assistants use the same account, permission, recipient, and subscription boundaries as the web app. Each vertical exposes three tools:

Hiring	Security	Purpose
hiring_list_reminders	csirt_list_reminders	Find visible reminders and eligible teammates
hiring_create_reminder	csirt_create_reminder	Create a reminder with explicit text, local time, people, and email choice
hiring_update_reminder	csirt_update_reminder	Edit creator-owned fields or complete and reopen as a participant

Have the assistant list reminders for the application or report first. That response supplies the eligible user_... IDs, current time, and suggested IANA time zone needed for a safe create call. See the MCP Tools Reference for the full contracts.

For example:

• “List the eligible people for this application, then propose a reminder to contact the candidate Friday. Show me the text, local time, people, and email choice before creating it.”
• “For report rpt_..., propose a reminder for the assignee to review the researcher reply tomorrow. Create it only after I approve, then list it again to verify.”

Quick Checklist

• Start from the candidate or report so the reminder keeps its context
• Review the AI-proposed wording, local time, and recipients
• Keep email off unless the reminder should also reach inboxes
• Select only teammates who own the next action
• Download .ics only when you want a separate calendar snapshot
• Read the reminder back after an MCP create or update