/brief still works.
How it’s generated
Each brief is built from your live numbers (the eight signals on the Watchlist, your team list, your platform) fed to a Forepost-tuned Anthropic Claude prompt. The prompt has explicit voice rules: direct, commercially sharp, no padding, no greetings, no emojis, no exclamation marks. Read the voice doc. When a helpdesk is connected (currently Intercom), the prompt also receives a small ticket context block: the five worst-CSAT conversations from the last 7 days, summarised as one-line topic + tone reads (“billing portal access lost — frustrated”). Grounds the brief in real customer language rather than aggregate-only direction. The block is illustrative — the brief is told to paraphrase, not quote, and to treat the sample as a starting point for a pattern rather than a complete picture. (Intercom integration.) Briefs are cached by metric fingerprint. If your numbers haven’t moved since the last brief, you see the cached version. No extra AI call. No charge. Click Regenerate to force a fresh read.What you can do with a brief
Read it
The headline of the page is the first sentence, your read on today, at a glance.
Forward it
Edit the brief, add your own intro, send it to your CEO. Forepost equips; you speak.
Regenerate it
Same numbers, new prose. Useful when the read needs a different framing.
Find it later
Every emailed brief is stored on the Archive tab. Click any row to expand.
What changed since yesterday
Above the brief sits a small What changed strip — 2 to 3 short lines computed frommetrics_history plus your recent actions. Examples:
- CSAT down 1.4pp (79% → 77%).
- Volume up 22 tickets (847 → 869).
- 3 actions taken · 1 dismissed since yesterday.
Action follow-through
Every brief ends with 1–3 specific actions, queued for you to mark taken or dismissed. Tomorrow’s brief receives that history and references it directly: “Monday’s coaching for Sarah hasn’t moved her CSAT yet; second pass needed.” The action list shows beneath the prose in-app, in a “Today’s actions” block in email, and as a footer section in Slack. Each action carries a kebab Send to… menu — Draft Slack DM, Draft email, File to Linear, Schedule in Calendar, Assign to teammate. The two primary affordances stay inline: a check-circle for Mark taken and a small Dismiss link.Bulk dismiss
When two or more pending actions are in the brief, a small Dismiss all (N) affordance appears in the actions header. Click it, type one optional reason (“addressed yesterday in the 1:1”), and every pending action is dismissed in one sweep. The reason is captured per-action and feeds Decisions, so future briefs see the rationale.Delegation timeline
Assignments to teammates render a Sent → Opened → Responded timeline inline. Sent fires when the email goes out; Opened fires when the assignee first clicks the magic link (or runs/forepost respond in Slack); Responded fires on accept/decline. Each dot fills with a tone-coded fill and the timestamp.
If you reassign the same action to a different teammate, the prior assignee gets a follow-up email explaining their link is void.
Outcome attribution
Seven days after an action is created, Forepost measures what actually happened to the metric it targeted and stamps the outcome on the action: ”→ +4pp CSAT in 7d (worked)”. The next brief sees that outcome in its history block and is told to reference real movements in prose. Outcome attribution is honest about no-movement and regressions too. Full mechanics, status semantics, and API in Action follow-through.Email delivery
Daily Briefs land in your inbox at the hour you set in Settings → Delivery → Daily Brief by email. They’re sent fromnoreply@forepost.ai via Resend with full SPF/DKIM/DMARC alignment, a one-click List-Unsubscribe header, and a footer unsubscribe link.
If your numbers aren’t complete enough on a given morning, no email is sent. Forepost would rather be silent than guess. See Honest “I don’t know”.