Skip to content
VooHr Support Contact Sign in

Acting on it

Commitments and reminders

VooHr has stored commitment and follow-up records and a meeting reminder delivery workflow. These are distinct from the nonfunctional Set reminder control shown in the Analysis View.

Commitments and follow-ups #

Conversation memory can store an HR-confirmed commitment or follow-up linked to an employee and, where supplied, a session. Records can include content, due date, priority, owner, and status. Newly created trackable items begin pending; overdue is derived when a pending or in-progress item's due date has passed.

The model does not create these records automatically. Confirm the promise or task with the people involved, then save an accurate summary. Update status when work changes; do not assume a saved item has been completed.

  1. Confirm the commitment or follow-up with the people involved.
  2. Save an accurate summary and add an owner and due date where supplied.
  3. Check the stored item and update its status when work changes.
  4. Use the dedicated meeting reminder workflow when a meeting reminder is needed.

Meeting reminders #

A separate reminder service can surface reminders for scheduled meetings and open follow-ups. Depending on configured account destinations and service settings, it can create in-app notifications and attempt email or WhatsApp delivery; external delivery can fail and is retried with bounded backoff.

Users can opt out of meeting email/WhatsApp reminders. In-app reminders are not gated by that preference. Do not assume every channel is configured or that a sent notification guarantees the recipient read it.

Important interface distinction #

The Set reminder button in the five-step Analysis View is explicitly visual-only. Clicking it toggles its label and pressed state in the browser; it does not call a reminder API, create a calendar event, or persist the setting.

For an actual follow-up, use the supported meeting/reminder flow and confirm the saved item in the appropriate list.

Use this guidance thoughtfully

This page describes the current product workflow; it is not an HR policy or a promise about every deployment. Before acting on information about an employee, verify the source record, consider context the system cannot see, and use your organization's process. If a control behaves differently from this guide, check the current workspace UI and confirm the saved result rather than assuming an action completed.