Mango Signal App Overview

Mango Signal

1. What it is

Mango Signal is a workforce-engagement intelligence layer. It reads signals from apps your organization already uses — Surveys, Shift Feedback, Leader Rounds, Recognitions, Performance, Communications, Ideas, Ballots and more — blends them into a single engagement health score, clusters the recurring themes behind that number, and flags the locations or segments that have dropped below a risk threshold. Managers then create actions against those risks, and the app measures whether the score actually improved after the action was completed.

• Enablement: Mango Signal requires a license and is disabled by default. An administrator enables it from Admin → Apps → All Apps.
• What it is not: Mango Signal is not a survey tool. It sits on top of Surveys (and several other apps) and interprets the cross-signal context. It does not replace any source app — it reads their data as inputs.

2. Standing it up

1. Go to Admin → Apps → All Apps and enable Mango Signal. The app appears in the sidebar once enabled.
2. Open Mango Signal → Settings and confirm the defaults are acceptable. The engagement score, risk alerts, close-the-loop flow, action reminders and the AI features are all on by default. The weekly engagement digest is off by default. Under Tuning, check who receives risk alerts — with no group chosen they go to this app’s designated admins, or to every company admin if none are designated.
3. Click Backfill last 90 days in Settings to populate the last 90 days of historical signals. Without this step the dashboard starts empty and only fills as new upstream events arrive.
4. Verify that at least one app whose signals feed the score (Surveys, Shift Feedback, Leader Rounds, Recognitions, Performance, Communications, Ideas, or Ballots) is also enabled. Mango Signal works with whatever subset you have, but with zero source apps there are no signals to score.
5. Confirm the result: open the Mango Signal dashboard and check that an engagement score and at least one theme appear. Managers should see risk segments and recommended actions if any segment is below the threshold.

Silent-until-paired: The backfill step is the most common miss. Without it, a freshly enabled Mango Signal shows no data until enough new upstream events accumulate — which can take days if survey or feedback volume is low. The backfill sweeps Surveys, Recognitions, Performance, Communications, Shift Feedback, Attendance, Leave, Ideas, Ballots, Leader Rounds and Frontline Execution activity from the last 90 days and is safe to re-run (it deduplicates on the source record).

3. How it fits together

Signals

A signal is a single normalized event from an upstream app: a survey analysis, a recognition post, a performance review, a shift-feedback submission, a reaction or comment on a Communications post. Each signal carries a type, a numeric score, and exactly one subject — a user, a location, or a named segment. Sentiment, recognition, performance, engagement and theme signals count toward the score; attendance, burnout, churn-risk and risk signals are recorded but not scored. Mango Signal does not invent signals: they come from the source apps, or from a CSV an admin imports.

Eight source apps feed the weighted engagement score today: Surveys, Shift Feedback, Leader Rounds, Recognitions, Performance, Communications, Ideas, and Ballots. Three more — Time & Attendance, Leave Management, and Frontline Execution — ingest signals that appear in the signal browse and export but do not factor into the score.

Individual employee sentiment is never surfaced in dashboards, analytics, or the AI assistant. Every score and theme stays aggregated to the company, a location, or a segment. The only places individual signals are visible are the Signals tab, its CSV/XLSX export and the same feed over the token API — restricted to business admins and Mango Signal app admins, plus any specific groups an admin grants access to in Settings.

Engagement health score

A 0-to-1 number (higher is healthier) computed from the rolling window of signals. The score blends five signal types with fixed weights:

• Sentiment — 40%
• Recognition — 20%
• Performance — 15%
• Passive engagement — 15%
• Themes — 10%

The score is computed for the company as a whole and separately for every location and segment. Scores are recomputed nightly. If the nightly run has not yet produced a score (for example, on a freshly enabled tenant), the dashboard computes one on demand so it is never blank. When the newest nightly score is older than the score window (no run has written one since), the dashboard, phone, home card and digest say so and show it as the last score, with its date, rather than as today’s.

Example: A company with three locations — Warehouse A, Office B, and Field Crew C — gets four scores: one company-wide and one per location. If Warehouse A’s 30-day sentiment average drops while its recognition volume stays flat, Warehouse A’s score falls below the threshold and appears in the risk panel, while the other two stay healthy.

Themes

Recurring concepts extracted from signals by a nightly clustering pipeline. Each theme has a label, a polarity (positive, neutral, or negative), a signal count, and an average score. The dashboard surfaces the top five themes over the last 30 days so managers can see what is driving the number, not just the number itself. A theme is shown only when at least the minimum group size of distinct people are behind it.

Risk segments

Any location or named segment whose rolling engagement score falls below the configured threshold (default 0.40). The dashboard sorts them worst-first. Segments backed by fewer signals than the minimum group size (default 5) are excluded entirely — they are not shown anonymized, they are simply not reported.

Actions

A manager-owned work item created in response to a risk. Each action has an owner, an assignee, a due date, a status (Open, In Progress, Complete, or Dismissed), and optionally a scope (the whole company, a location, or a segment) and a set of linked source signals. Action titles are limited to 200 characters.

When a manager sees a risk segment on the dashboard, the app recommends one to three concrete next actions. On the initial page load these are heuristic (instant); clicking Refresh with AI replaces them with AI-written recommendations when the AI-written action recommendations setting is on (with it off, the built-in recommender answers instead).

Close-the-loop

When an action is marked complete and the close-the-loop flow is on, three things happen:

1. A baseline engagement score for the action’s scope is captured — the score over the 30 days before completion.
2. A “you said, we did” update is published to the people the action is about. A company-scoped action goes out as a company Broadcast to everyone in the business. An action with no scope is posted to the Communications feed for everyone. A location action is posted to the Communications feed for the people at that location and the locations under it. A segment action has no people of its own, so its update is posted only if whoever completes it ticks Also post this update to everyone. (Feed posts are skipped if Mango Signal’s posts are switched off in the Communications settings.)
3. The people whose feedback the action was raised from receive an email.

The baseline triggers a follow-up measurement after 30 days to compute the real delta. With the close-the-loop toggle off, completing an action sends no update or emails and starts no impact measurement — completed actions still appear in the What Changed archive.

Impact measurement

Each action completed while the close-the-loop flow is on gets a baseline score and a re-measurement 30 days after completion (a fixed window). The Impact tab shows per-action delta, delta percentage, and a status: pending, measured, inconclusive, or failed. It also rolls up measured, pending, positive and negative counts and the average delta across measured actions. A result needs at least 5 post-action signals, from enough people to clear the anonymity floor; otherwise it is inconclusive.

Role-based access

Mango Signal has three access tiers. What each role sees in the sidebar:

Role	Tabs visible
All users	Dashboard, What Changed, Actions (the actions they own or are assigned)
Manager or above (and app admins)	Dashboard, What Changed, Actions (every action), Impact, Analytics
Admin or above (and app admins)	All of the above plus Signals and Settings

App admin status can be granted per user, giving them the same access as a full administrator within Mango Signal without elevating their platform-wide role. The Signals tab also appears for anyone in a group an admin adds under Who can read individual signal detail? in Settings.

4. Running it

Reviewing the dashboard

The dashboard is the landing page. It shows the current company-wide engagement score, the top five themes, and (for managers) the worst three risk segments with recommended actions. Below the risk panel, the current user’s open actions appear in due-date order (up to 5). A sample-data banner appears when demo signals are loaded.

Creating and managing actions

1. On the dashboard, click a recommended action or go to Actions → New.
2. The form opens in a drawer. Fill in the title, description, assignee, due date, and optionally the scope (company, location, or segment) and linked signals.
3. Save the action. The assignee receives an email notification if they are not the owner.
4. When the work is done, the owner or the assignee clicks Mark complete. This fires the close-the-loop flow.

Open actions with a due date trigger reminders: the assignee (or the owner, if the assignee is no longer active) is reminded when the action comes within 3 days of its due date (usually 3 days and again 1 day before), then the assignee and owner are reminded every 3 days while it is overdue, stopping 60 days past due. These are automatic; an admin can switch both off with Action reminders (due soon and overdue) in Settings.

Viewing impact

Go to Impact. Each row shows a completed action, its baseline and post-action scores, and the delta. The summary bar at the top shows counts of measured, pending, positive, and negative outcomes plus the average delta. Sample-data rows are labeled and excluded from the summary averages.

Reviewing what changed (all employees)

The What Changed tab is visible to all users, not just managers. It lists completed actions with their title, description, completion date, and impact direction — but omits the owner and assignee names. This is the employee-facing “you said, we did” archive.

Browsing raw signals (admins and granted groups)

Signals shows every individual ingested signal with its source app, type, score, and date. Because it exposes individual named sentiment, it is restricted to business admins and Mango Signal app admins by default; an admin can add specific groups (for example People Ops) under Who can read individual signal detail? in Settings. Filter by source app, signal type, segment, or time window.

Using analytics

Go to Analytics. The page shows the current engagement score, total signal volume, at-risk segment count, open action count, and a daily signal-volume trend chart. Use the window selector to switch between 7, 30, 90, or 180 days. Analytics is available to managers and above.

Exporting and importing data

People who can read individual signal detail (business admins and Mango Signal app admins, plus any group granted in Settings) can export raw signals to CSV or XLSX — from the Analytics page over its selected window (7, 30, 90, or 180 days), or from the Signals tab (the last 30 days). Other managers see the aggregate Analytics page without the export buttons. Admins can also import signals from a CSV file using a downloadable template — useful for backfilling from a retired feedback tool.

Notifications

Mango Signal sends seven types of notifications. Each is delivered by email and in-app bell. Users can mute them from their notification preferences under two categories: Mango Signal (risk alerts and the weekly digest) and Mango Signal · Your Actions (assigned, due-soon, overdue, completed and close-the-loop notices).

Notification	Who receives it	Frequency
Risk alert	The group chosen under Settings → Tuning (only its managers, admins and app admins); with no group chosen, this app’s designated admins, or every company admin if none are designated	At most once every 7 days per recipient while the same segments stay at risk; a change in which segments are at risk can alert again the next day
Action assigned	The assignee (when different from the owner)	One-time on creation
Action due soon	The assignee — or the owner, if the assignee is no longer active	When the action comes within 3 days of its due date — usually 3 days and 1 day before
Action overdue	The assignee and owner	Every 3 days while overdue, stops 60 days past due
Action completed	The owner, when someone else completes it	One-time per completion
Close-the-loop update	The people whose feedback the action was raised from	One-time on completion
Weekly digest	Managers and admins, plus anyone who owns or is assigned an open action	Every Monday (opt-in; off by default)

Mobile

Mango Signal has a mobile dashboard at /m/apps/mango-signal. It shows the engagement score, top themes, and open actions assigned to the current user, and the What Changed archive. From an action’s phone page, its owner or assignee can mark it in progress or complete it. Opening Mango Signal on a phone redirects to the phone view automatically; the “open on desktop” link (?desktop=1) keeps that phone on Mango Signal’s desktop pages until it opens a phone page again.

5. Settings

Setting	Where	Default	What it changes
Engagement health score	Settings	On	Turns the nightly score computation on or off. Switching it off also stops risk alerts; signals, themes, actions and the dashboard’s risk-segments panel keep working.
Risk alerts	Settings	On	Emails one alert naming every location or segment below the risk threshold. Who receives it is set under Tuning. Needs the engagement health score on.
Close-the-loop “you said, we did” flow	Settings	On	Controls whether completing an action publishes the update, emails the people whose feedback fed it, and starts impact measurement. Completed actions still appear in What Changed even when this is off.
Weekly engagement digest email	Settings	Off	Every Monday, emails managers and admins — plus anyone who owns or is assigned an open action — the company score and its week-on-week change, the top themes, and their own open and overdue action counts.
Action reminders (due soon and overdue)	Settings	On	The due-soon and overdue reminders. The one-time “action assigned” email is not affected.
AI theme extraction (nightly)	Settings	On	Once a night, AI clusters the phrases attached to the last 30 days of signals into themes. Off: no phrases are sent to the AI provider and existing themes stop refreshing.
AI-written action recommendations	Settings	On	Lets AI write the recommendations behind Refresh with AI and the assistant’s suggestions. Off: the built-in recommender is used.
Mango Signal AI assistant in Ask AI	Settings	On	Enables or disables the Mango Signal assistant in Ask AI.
Engagement score window (days)	Settings	30	The rolling window of signals used to compute the engagement score — and with it the risk-segments list, the risk-alert email and the weekly digest. Top Themes always covers 30 days.
Risk alert threshold (0–1, higher = more alerts)	Settings	0.40	Locations and segments scoring below this value appear as at-risk, so a higher threshold flags more of them. At 0, nothing is ever at risk.
Minimum group size for reporting	Settings	5	The anonymity floor. A location or segment is shown or alerted on only when at least this many signals were filed about it, and a theme only when at least this many distinct people are behind it. It can’t go below the company-wide smallest group (5 unless raised under Retention & Legal Holds); maximum 50.
Route risk alerts to this group	Settings	None	Sends risk alerts to this group instead of this app’s admins; only its managers, admins and app admins receive them.
Who can read individual signal detail?	Settings	Admins only	Who can open the Signals tab and export raw signals. Business admins and Mango Signal app admins always can; you can add specific groups.

6. More help

• Mango Signal FAQ — specific setup and operating questions, limits, and troubleshooting.
• REST API — a scoped read/write API is available at /api/v1/mango_signal for native mobile and external integrators, tenant-scoped and role-gated to match the web surface.
• Ask AI — the assistant answers questions about Mango Signal from these articles.