Product Update - June 22, 2026

Never-Closing Polls & Manual Close — persistent employee polls with on-demand close control

News Feed polls can now be created without an end date, staying open indefinitely until someone decides to close them. In addition, poll authors and admins can now close any open poll at any time with a single click — a "Close poll now" button appears directly on the poll card. Previously, every poll required a fixed duration between 1 and 30 days, which made ongoing pulse checks and open-ended community votes awkward to manage. This change gives teams full control over poll lifecycle without workarounds.

Use case: An HR team runs a continuous "how are you feeling this week?" pulse poll that stays open all year, then closes it manually at the end of a company all-hands to discuss results live.

Available in: News Feed → Polls → Poll Composer

---

Multiple Team Workload Profiles — role-based workload measurement for customer success teams

CS team leaders can now create named workload profiles — each with its own signal baselines and weighting — and assign individual team members to the profile that reflects their role. Previously, every CSM on the team was scored against a single global model, making it impossible to fairly compare an onboarding-focused CSM with an account expansion manager. The Team Workload view now shows each row's assigned profile alongside its scores, and the Settings panel links directly to the profile editor so there is one place to manage all measurement configurations.

Use case: A CS director creates an "Enterprise Account Manager" profile with higher account-count baselines and zero weight on onboarding signals, then assigns it to the three EAMs on the team — their workload scores now reflect what their role actually demands.

Available in: Mango CS → Team Workload → Workload Profiles

---

Automatic Profile Update Request Expiry — self-cleaning HR queue for stale profile change requests

Employee profile update requests that sit in a pending state for too long now expire automatically. Admins can configure the expiry window (defaulting to 30 days) at the business level; once a request passes that threshold the system marks it expired, notifies the original requester, and removes it from the active queue. This prevents the HR team's review list from filling up with forgotten or outdated change requests that were never acted on.

Use case: An employee submitted a name-change request six weeks ago but left the company before HR reviewed it — the request now expires automatically rather than sitting in the queue indefinitely.

Available in: Employee Data Management → Profile Update Requests → Business Settings