If your briefing looks wrong
Briefings get sharper when you correct them. Herald stores every correction as a semantic annotation scoped to your Product, and the annotations feed straight into next Monday’s prompt. “Charges under $1 are test runs, not MRR” applied once becomes “Herald filters test charges out of revenue math” forever.
If something is wrong this week, it’s worth 60 seconds to fix — that’s ten weeks of accuracy saved.
Revenue math looks off
Section titled “Revenue math looks off”Open chat and ask the specific question: “Why is MRR $4,200 this week? I thought it was closer to $4,800.”
Herald explains what it included and what it excluded. The reply usually points at one of three things:
- A test charge that should be filtered. Say “treat charges under $2 as test runs, not revenue” and Herald adds that rule.
- A refund or dispute Herald missed. Ask it to recompute; the rule lives forever.
- A subscription plan Herald classified wrong (usage-based when you bill flat, or the reverse). Say “the
pro_usageprice is actually flat-rate” and the briefing math updates.
Revenue rules are the most-load-bearing annotations — they change MRR, ARR, churn, and the forecast. Fix them first.
A “person to talk to” shouldn’t be there
Section titled “A “person to talk to” shouldn’t be there”Some people Herald surfaces shouldn’t be there: your cofounder, a QA account, a customer you already spoke to. Open the briefing, click the person, and hit Hide (one-time) or Exclude from future briefings (permanent). Hidden accounts are still queryable in chat; they just stop surfacing unprompted.
If Herald keeps suggesting someone you’ve already handled, correct it in chat: “I already spoke to Bob at Acme about the import issue. Don’t re-surface him unless something new happens.” That’s an annotation; Herald respects it.
A feedback theme is mislabeled
Section titled “A feedback theme is mislabeled”If Herald clustered “payment declined” and “my card was charged twice” into one cluster, split them: open the cluster, click Re-cluster, and label the two halves. The label is the annotation — Herald uses your labels to cluster next week.
If a theme is entirely bogus — one customer mentioned something and Herald turned it into a trend — mark the cluster Singleton and it stops surfacing.
An anomaly isn’t actually an anomaly
Section titled “An anomaly isn’t actually an anomaly”Anomalies are flagged when a metric moves more than one standard deviation from its 28-day baseline. Sometimes that’s a seasonality you already knew about — a pricing-page A/B test, a launch week, a known churn cohort. Dismiss the anomaly and tell Herald why: “signups drop every Friday, not an anomaly.” The window calibration updates.
The whole briefing feels off
Section titled “The whole briefing feels off”If the voice, the section length, or the section order is wrong for you, change it in Settings → Briefing → Voice. Herald composes the briefing using your last four editions as reference; three or four edits worth of corrections recalibrate the voice by next Monday.
When to email us
Section titled “When to email us”If the fix isn’t chat-correctable — a persistent numerical bug, a missing integration event, or a repeatable misreading — email help@withherald.co with the briefing date and the passage that’s wrong. We read every one.