From raw request to confirmed result, in five visible steps.

Incoming work is gathered in one place. Claude prepares each item with its context. You approve the exact version. The system carries it out and names every stage for what it is: a draft is never called sent, and an unknown outcome is checked, not blindly retried.

STEP 01 · SYSTEM

Gather: everything in one place, gaps in plain sight.

✓Employees sign in with their corporate identity and connect the work accounts they are allowed to.
✓Intake decides what to take on: your own and automated emails are filtered out.
✓An incomplete fetch never deletes records. A gap is shown as a gap.
✓What needs action comes first: reply, pick an option, sign off, clarify, defer.
✓Pilot channel: email. Then Slack, followed by Jira, Confluence and Asana.

STEP 02 · CLAUDE

Prepare: a sheet instead of an empty reply box.

Claude gathers who is writing, what was agreed and which documents matter, each with its origin and freshness. Permissions apply before search.

Zone	What it holds
Gist	The bottom line in one sentence.
Why	The reasons, each linked to its source.
Options	Two or three reply options, or a deliberate “no reply needed” with the reason.
Not checked	What the model could not verify, flagged for you.

STEP 03 · YOU

Approve: the exact version, and nothing else.

✓Approval covers the sender, recipients, subject, body, thread and attachments.
✓Change any of them and it becomes a new version that needs a new approval.
✓Approvals expire, can be withdrawn and are used once.
✓Only the employee's own interactive session can approve. The model never can.

STEP 04 · SYSTEM

Carry out: checked again at the moment of action.

✓The employee's permission for this operation is current.
✓The approval is neither withdrawn nor expired, and the account belongs to this employee.
✓Attachments are fixed in advance by a content fingerprint.
✓No emergency stop is active for the organisation, connection or action type.
✓One outbound queue: a second click or a second device does not create a second action.

STEP 05 · SYSTEM

Show: every stage has its own name.

There is no automatic retry. A timeout or restart alone never permits a resend.

Stage	Meaning
Draft	Not approved yet.
Approved	The exact version is approved.
Waiting	Saved and waiting for a connection.
Sent	The service accepted the action.
Confirmed	Confirmed by reading the result back at the service.
Needs checking	The request may have reached the service; the outcome is being checked.
No reply needed	A deliberate outcome, with the reason.

Walk the path on your own scenario.

Describe one request your team handles every day. We reply in writing with how Asedra would prepare it.

Describe a scenario What's inside the platform