Skip to content
MSO CloudDocumentation

Signals and the morning brief

On this page

In short. The morning brief is a short note on what needs attention, written for each person at 07:00 Vietnam time. Its alerts come only from Alerts rules and alert workflows that an admin has switched on for the organization.

An enabled rule or workflow is evaluated, the result goes into the daily, weekly or monthly brief, and the brief is delivered in the app and, where linked, by email, Telegram, Zalo or push

How it works#

A signal is one evaluation of a rule over the organization's own data. Each evaluation is recorded as fired, quiet or could not be evaluated, so "why did the brief say nothing about stock today" has an answer on file.

  • Source of alerts. The brief shows an alert only while it is open or seen, and only when an enabled, organization-visible Alerts rule or workflow raised it. It runs no detections of its own outside the demo organization. Facts such as yesterday's GMV and the media headline are not alerts and stay.
  • One alert per finding. A rule raises one alert per brand and item. While the condition holds, the same alert is updated instead of raised again; once the value is back inside the rule's clear band, the alert closes and members get one notice that it ended.
  • Nothing runs until an admin configures it. Rules that nobody switched on are off, and the system no longer creates organization rules by itself. Admins turn rules on or off in Settings > Alerts & brief ("Cài đặt > Cảnh báo & bản tin"); other members open the same page to set their own mute and snooze. See Configure the morning brief and alerts.
  • Closed days only. The brief compares the last closed day in Vietnam time with earlier full days, never a day still in progress. Order value (AOV) is NMV divided by confirmed orders.
  • Order of the run. At 07:00 the workflows are evaluated first, then the brief is written from the same data day.
  • One brief per person per cadence. Each member gets one brief document and one notification per cadence per day, written for the member's role. A member limited to some brands sees the alerts of those brands plus organization-wide ones.
Cadence Runs Frames the brief over
Daily Every day, 07:00 The latest closed data day
Weekly Every Monday, 07:00 The week that just closed
Monthly The 1st of the month, 07:00 The month that just closed

What a brief contains#

A one-line summary from the headline measures of the role, then at most four bullets. Each bullet names the rule that fired, the measured numbers, an action verb and a link to the screen to check; a GMV, return-rate or contribution-margin alert opens the commerce report on the day it read. A quiet day gets one bullet saying so.

Withheld from the bullets as Meaning
Dismissed Someone dismissed it and its 30-day window is still open
Cooling down The same signal fired recently; repeating it would be noise
Covered A higher-ranked signal in the same run already covers it

Bullets are ranked by measured impact, the weight of the rule, its severity and past feedback. Two dismissals within 90 days halve a signal's weight; one "acted" mark restores it.

What you can do with an alert#

The same buttons sit under an alert in the bell and on the Morning brief page.

Button Who Effect
Seen Owner, admin Marks the alert as seen for everyone
Handled Owner, admin Closes the alert for everyone
Snooze 1 day, Snooze 7 days Any member Hides the alert from you only for that long
Mute rule Any member Stops that rule's alerts for you only
Done on a signal line Owner, admin Records that the signal was acted on, so its rank weight returns to full

Who a brief is written for#

Each activated domain declares its readers.

Domain Written for Headline leads with
eCom (marketplace orders) Owner and Ops Owner: yesterday's GMV, its change, contribution margin. Ops: shift signals
Marketing Marketing Spend against its own baseline, leads, cost per lead, pacing against plan
HR HR Headcount, hiring and cost
Warehouse Ops Stock on hand, on-time delivery, backorders
Market data, CRM, finance nobody No reader declared, so no brief

When the brief says it does not know#

Case The brief
A rule reads a measure the organization does not have Skips it, without an error or a guess
Below a rule's minimum evidence (spend, days) Records "not enough data", not "fine"
One input unknown and none failed Treats the whole condition as unknown; unknown never fires
A selling day has no cost of goods Leaves contribution margin out
One data plane fails to load Continues without that plane
No brief was written for you The Morning brief page says why, with the date of the last run

The brief never reads compensation-sensitive fields and never states a third-party estimate as fact. Platform alerts (failed sync, webhook lag) go to super admins only.

Where it stops#

  • The brief is in-app. Email, Telegram, Zalo and push copies are sent only for a channel the platform has configured and the member has linked; with no preference set, a member gets the in-app copy only. See Notifications.
  • A signal line cannot be dismissed from the Morning brief page; dismissals arrive through the platform console or the API. Where this stands is dated on Project status.
  • The weekly and monthly briefs reframe the same alerts over the closed period; they compute no extra comparison of their own.