Product Update - May 23, 2026

Recurring Calendar Events — Repeating events and recurring meeting schedules

Team calendars now support fully recurring events. When creating or editing an event, authors can set a recurrence rule — daily, weekly, monthly, or custom — with configurable intervals and end conditions. A nightly materialization job pre-generates upcoming occurrences so they appear reliably in team views and iCal feeds. When editing a recurring event, authors choose whether to update just the current occurrence, all future events, or the entire series, keeping one-off exceptions separate from the recurring pattern.

Use case: An HR coordinator sets up a recurring weekly all-hands every Monday at 10 AM — it appears across all employees' calendars automatically, and they can reschedule a single occurrence for a holiday without affecting the rest of the series.

Available in: Calendar → Events → Recurrence

---

Broadcast Scheduling, Templates & A/B Variants — Schedule broadcasts, reuse templates, test message variants

Broadcasts now support three capabilities that were previously unavailable: scheduled delivery, saved templates, and A/B variant testing. Authors can set a future date and time for a broadcast to publish automatically, save any broadcast as a reusable template (with preview and duplicate flows for compose-only users), and create multiple message variants to test different content across audience segments. Delivery is tracked per channel, recipient counts are shown before publishing, and scheduled broadcasts remain fully editable until they go out. A quiet-hours setting ensures messages respect employee availability windows.

Use case: A communications manager prepares two versions of an open enrollment announcement, schedules them to go out Monday morning, and uses the variant feature to test which message drives higher acknowledgement before rolling out company-wide.

Available in: Broadcasts & Alerts → Compose → Schedule / Templates / Variants

---

Custom Employee ID Patterns — Configurable Mango ID format with custom tokens and bulk backfill

Admins can now define a custom employee ID format using configurable tokens — such as the last four digits of a phone number and a sequential counter — alongside the existing auto-generated and employment-type modes. A chip-based pattern composer in the admin settings panel lets admins build the format visually with a live example preview. Once the pattern is saved, admins can run a preview-only collision check across all existing employees before applying the backfill via a background job tracked through the standard task progress UI.

Use case: A retail operations team standardizes employee IDs to include the last four digits of each employee's phone number followed by a three-digit sequence number, then runs the backfill to align all existing records without manual data entry.

Available in: Employee Data Management → Admin → Settings → Employee ID Format