# Workflow Inbox — planning brief

Status: planned product; software not released. Version 1.0, 2026-09-29.

People copy the same details between tools, chase incomplete requests and lose track of who approved an action. Fully autonomous agents can make these failures harder to see.

## First workflow

A request enters one intake channel, is classified and summarized, then appears in a review queue. A person approves the proposed CRM update; the system records the result and offers a retry when the destination is unavailable.

## Proposed first release

- [ ] One inbound connector and one destination system
- [ ] Structured extraction, routing rules and an approval queue
- [ ] Idempotent action execution with retries and a visible exception inbox
- [ ] Execution history showing input, decision, approver and result

## Extension points

- [ ] Keep connectors separate from routing rules and screen components
- [ ] Add task types with explicit input/output schemas
- [ ] Reuse the approval queue for lead intake, onboarding or support operations

## Acceptance checks

- [ ] A duplicate inbound event does not create duplicate CRM records
- [ ] An external write cannot run before the required approval
- [ ] A timed-out request can be retried without repeating a completed action
- [ ] The operator can inspect and correct an incorrectly routed item

## Boundaries

Mass unsolicited outreach, unrestricted agent tool access and an all-purpose autonomous employee are outside this first release.

## Decisions to fill in

- Business owner:
- Intended users:
- Data sources and retention:
- Existing systems:
- Integrations:
- First release exclusions:
- Deployment owner:
- Acceptance owner and evidence:

## Reuse

You may copy and adapt this planning document for your own or client projects. It contains no software license or promise of implementation.

Discuss a custom build: https://fone.cc/contact/