Pilot live: ACP for AI commerce.Explore ACP
Delivery & alerts agent

Where insights land. Slack, Sheets, Slides, Docs, Notion.

Dex carries every other agent's output to the surface that needs it, formatted for that surface. Anomaly alerts fire within 5 minutes; weekly recaps land Monday at 8 AM.

Why this exists

Intelligence without delivery is noise. Most reporting dies in the dashboard.

Reports nobody reads.

Friday afternoons rebuilding the same weekly deck from four platforms. By the time the file lands, the data is stale and the decision has already been made without it.

Format mismatched to surface.

A Slack channel does not want a Slides deck. A CFO does not want a CSV. Same insight, five surfaces, five formats. Most teams ship one format and lose four audiences.

Alert fatigue, then alert blindness.

Channels flooded with every metric movement until the team mutes the channel. Real anomalies arrive in the same firehose as weekend noise. Nothing gets caught in time.

Copy-paste from analyst to Slack.

Numbers leave the BI tool, get massaged in a Doc, get pasted into Slack with manual commentary, get forwarded to a Sheet. Ten hours a week moving bytes between surfaces.

What Dex ships

Five capabilities. One delivery layer.

Each capability maps to a specific job: route the output, alert on the anomaly, recap the week, hold the brand voice, and stay aware of every other agent's work.

Routes to five surfaces

Slack, Sheets, Slides, Docs, Notion. Same underlying insight, formatted per surface. No copy-paste, no duplicate work.

  • Slides decks for leadership reviews
  • Sheets tables for growth-team granularity
  • Slack messages with one decision per post

Example. Felix's forecast lands as a Slides deck and a Sheets tab in the same run

Anomaly alerts inside 5 minutes

Spend, CAC, ROAS, and pacing breaches surface to Slack within five minutes of the data tick that triggered them.

  • Confidence-band breaches from Felix
  • Tracking glitches cross-checked with Dana
  • Suggested action attached to every alert

Example. CPA crossed the 7-day ceiling at 9:14 AM; alert in #performance at 9:18 AM

Weekly recaps that get read

Monday-morning recap in Slack: three forecasts, two anomalies, one decision pending. One screen, no scroll, no fluff.

  • Decision-led, not metric-led
  • Open-rate tracked per surface
  • Long form parked in Notion for those who want it

Example. Average recap length 142 words; open rate above 80% across pilots

Per-brand voice and format

Maya holds the style guide; Dex applies it. Brand-specific tone, abbreviations, and chart conventions per company.

  • Tone learned from past approved messages
  • Format preferences set once, never re-asked
  • Maya updates the rule, every recap inherits it

Example. Brand A gets percentage points; Brand B gets basis points

Workforce-aware

Every other agent's output routes through Dex. Forecasts, attribution, scenarios, creative briefs, reconciled data, brand context.

  • Felix's forecasts to leadership
  • Parker's incremental ROAS to growth
  • Olivia's fatigue briefs to creative

Example. All 6 other agents pipe outputs through Dex

A typical week

What Dex does while the team sleeps.

One workweek, hour by hour. Specific timing varies by account.

Mon · 6:02 AM
Formatted

Felix posts the weekly forecast. Dex packages it as a Slides deck for the CMO and a Sheets tab for the growth lead in the same run.

Mon · 8:00 AM
Recapped

Weekly recap lands in #growth. Three forecasts, two anomalies, one decision pending. 142 words, no scroll.

Tue · 9:18 AM
Alerted

CPA crossed the 7-day ceiling on Campaign 14. Alert in #performance four minutes later with the campaign linked and the action suggested.

Wed · 11:44 AM
Routed

Parker finishes the lift validation on Meta. Dex routes the summary to growth in Slack, the full table to the shared Sheet, the long form to Notion.

Thu · 2:30 PM
Surfaced

Olivia flags Hook_v4 entering decay. Dex sends the refresh brief to the creative lead via Slack DM with a 5-day action window.

Fri · 7:55 AM
Delivered

Sam's scenario completes. Dex delivers recommendations and confidence scores to the strategy Notion page; one-line summary to the CFO.

Fri · 5:00 PM
Delivered

Friday close: the weekly Slides deck is already done. Was built Monday morning. Nobody spent Friday on reporting.

What's underneath

Real delivery infrastructure. Not a Zapier flow.

Dex runs on a purpose-built delivery layer: per-surface formatters, sub-5-minute alert latency, brand-voice memory, and shared context across the workforce.

Reads from

Every other agent's output. Forecasts from Felix, attribution from Parker, scenarios from Sam, creative briefs from Olivia, reconciled data from Dana, brand context from Maya.

All 6 other agents pipe outputs through Dex

Reports to

Slack for alerts and recaps, Sheets for tables, Slides for leadership decks, Docs for long form, Notion for the workspace of record. Format adapted per surface.

SlackGoogle SheetsGoogle SlidesGoogle DocsNotion

Anomaly alerts within 5 minutes of breach

Collaborates with

Maya supplies brand voice and format preferences. Dana confirms tracking before alerts fire. Felix triggers anomaly routing. Parker, Sam, and Olivia ship outputs through this layer.

Shared memory, one delivery contract per agent

Built on

Twelve delivery integrations, one router. Per-surface formatters, brand-voice templates held by Maya, anomaly thresholds tuned per account, and audit trail per delivery.

Per-surface formatters, brand-voice templates held by Maya

Ready when you are

See Dex deliver against your stack, or talk to us about your reporting cadence.

The pilot connects your accounts to all seven agents. Dex's first recap lands in Slack inside 24 hours.

Looking for something specific? Felix delivers forecasts, Parker delivers attribution or Sam delivers scenarios.