Three things before coffee

AI voices perform a script reviewed by Mata.Works. Landon and Tam are the illustrated hosts. The business scenario is an example.

Landon: The owner opens a dashboard, then the inbox, then a text thread. By nine, she has found an old quote, a parts delay, and a customer waiting on a return call. What would a useful morning brief say?

Tam: Three lines, each with a reason and a link. "This quote has waited four days for approval." "This delayed job has no customer update." "This repeat complaint has no owner." She can see the original record and make a decision.

Landon: That sounds simple. Why doesn't every dashboard do it?

Tam: Because the hard part is deciding what deserves attention. An old quote might be deliberately on hold. A callback could already be assigned. We need rules the owner and the office agree on, not a machine that declares every aging record an emergency.

Landon: Where would the information come from?

Tam: From the systems the team already uses, starting with one or two sources. Railway can run a scheduled check. Supabase can keep a small exception list and record what happened. Gemini can shorten a long note after the rule has found an item, but the brief needs to link back to the source.

Landon: What if one system fails to update overnight?

Tam: The brief needs to say that. A blank list could mean nothing needs attention, or it could mean the connection broke. The owner should not have to guess which.

Landon: And the tool doesn't make the decisions?

Tam: Correct. It doesn't approve refunds, move appointments, or send a promise to a customer. It points the owner at the work that needs judgment. I would start with two rules and ask after a week: which alerts led to action, and which ones were noise?

Landon: So the first step is to name the interruptions that should have reached her sooner?

Tam: Exactly. Start with those real cases. Then write a brief short enough she will actually read with her coffee.