Recurring answers, with review.
Arcus automation workflows are being scoped for launch pilots. The current goal is simple: rerun approved questions, surface changes, and keep the reasoning trail visible before anyone acts.
The Friday brief, reviewed.
Take an approved question, rerun it against fresh data, and review the prose, chart, and source trail before it becomes a decision artifact.
- From approved threads. Recurrence starts from a question your team already trusts.
- Reviewable prose. Arcus keeps recommendations tied to the data that produced them.
- Scoped routing. Delivery channels are enabled by pilot configuration and workspace permissions.
Watch items when reality changes.
Set a threshold on modeled data and review the change before acting. Automatic anomaly detection and escalation remain preview scope unless enabled for a pilot.
- Thresholds in plain language. "If revenue dips below forecast by 5%." Done.
- Anomaly mode. Preview only, scoped to the data and baselines your team approves.
- Snooze + escalate. Routing rules are enabled only when configured in the workspace.
Plug into approved workflows.
Webhook, Slack, email, ticketing, and CRM actions are enabled only when the integration, permission model, and approval gates are scoped for the customer.
- Webhooks by request. Send reviewed payloads to approved endpoints.
- Native integrations. Scoped case by case for launch pilots.
- Approval gates. Any action outside Arcus requires explicit customer approval.
POST https://hooks.client.example/arcusAuthorization: Bearer ***{"alert": "cac_drift_15","severity": "warn","thread_id": "thr_q3paid","recommendation": "shift_180k_to_android","sources": ["warehouse.ads_daily", "warehouse.revenue"],"sql": "https://arcus.ai/sql/q_8a2f"}
Scope your first recurring answer.
Bring the question you want reviewed every week. Arcus will help decide what can safely run in the background.