Platform / Alerts · preview

Reachout

Gate held, run failed, invoice posted — someone is told, and you can see that they were.

Console preview — the Reachout module is not in the console yet. Synthetic events.

reachout · console preview
Rules · trigger → destination
gate held > $10k→ email approvals@acme.com
run failed→ slack #ops
invoice posted→ webhook → erp
error rate > 2%→ sms on-call
Deliveries
12:41email approvals@ · gate held · INV-20841✓ delivered
12:39webhook erp · payload · 214 rows✓ delivered
12:36slack #ops · error rate 2.1%✓ delivered
12:31sms on-call · gate pending > $10k⏸ queued

What it is

Reachout is the outbound notice. A workflow can already commit through a declared webhook — that is agentOS, and it is the write. Reachout is the separate question: who should be told that the gate is holding, that the run failed, or that the post succeeded.

The console module is not shipped yet. The screen on this page is a preview of the rules and the delivery log: a trigger, a destination, and a status of delivered or queued. Treat it as the shape of the product, on synthetic events, not as a switch you can turn on today.

What it is not

Reachout is not the commit. Sending an email that an invoice posted is not the same as posting the invoice. The post is a webhook capability on the pipeline, signed by the runtime. A notice is a notice.

Who it is for

The approver who should not have to poll a queue, and the on-call who wants a failed run to arrive somewhere other than a log line.

Where you get it

Designed to sit on Platform beside the workflows you already run. The preview is public. The live console module is not on a tier yet.

Pricing →

The $10,000 hold

Synthetic example. Not a customer.

Invoice 20841 waits on review because the amount tripped the filter. A rule matches “gate held over $10,000” and addresses the approvals list. The delivery row says queued, then delivered. The approver opens Review, not their inbox search. The invoice is still unposted until they approve and agentOS commits.

What changes when you have it

A trigger you can point at

Held gates, failures, completions, thresholds.

People and systems

A human-readable note and a structured payload from the same event.

A delivery row

Delivered or queued, so “did anyone hear?” is a status, not a guess.

Inside Reachout

  • Rules from a workflow decision to a destination
  • Email and webhooks first; chat and SMS are on the preview, not a live console
  • A human note and a structured payload from one event
  • Per-event status: delivered or queued

How it works

1

Pick the decision

The workflow events worth interrupting someone for.

2

Pick who hears it

A person, a channel, or a webhook that is a notification — not the system-of-record write.

3

Write it twice if you need to

Plain language for the approver. A payload for whatever consumes events.

4

Keep the log

Each event keeps its delivery status.

Reachout. Outbound notices are not a side door around the manifest. The commit stays on agentOS.

The names next to it

See it on your workflow

Platform Start is the self-serve canvas. A first pipeline we stand up with you is delivery, priced apart from the subscription.