One request. A clear path to done.

FOLLOW ONE REQUEST, ALL THE WAY THROUGH.

Two documents.
One less thing
to keep in your head.

You need Priya’s bank statement and receipts. Follow that single request from the first instruction to the final check.

Illustrative workflow · Synthetic client · No emails sent

October bookkeepingStatement + receipts

An email workflow connects the request, recipient, schedule and completion criteria.
Here’s what that looks like in practice.

1. START WITH THE JOB TO BE DONE

   Put the request into words.

   Say what you need, choose the recipient and define what “done” means. Review the proposed wording, dates and required items. You can edit every part before submitting.

   Offline templates work without AI. Optional AI drafting needs provider setup.
   01

   Request composerDraft

   YOUR INSTRUCTION

   “Ask Priya for her October bank statement and receipts. Follow up after five working days.”

   Turn the request into a plan

   CHOSEN RECIPIENTPPriya · Example client

   WHAT YOU NEED BACK Bank statement Expense receipts

   Nothing is scheduled until approval.

2. A PERSON MAKES THE DECISION

   Give the plan a human yes.

   Check who will receive the message, what it says and when it will run. Only an approved plan creates scheduled sends. Require a different reviewer when your workspace policy calls for one.

   A draft is a proposal. It is never permission to send.
   02

   Plan reviewHuman checkpoint

   REVIEW THE EXACT MESSAGE

   Your October bookkeeping documents

   Hi Priya, could you send your October bank statement and expense receipts? Thank you.

   Recipient Wording Timing

   Your reviewer gives the go-ahead.A different approver can be required.

   Approved

3. LET THE CALENDAR CARRY THE PLAN

   Follow up on working days.

   Set the first request and a sensible follow-up. The scheduler respects timezones, business hours, configured holidays, suppression and daily limits. If the first send is delayed, the follow-up moves with it.

   Sandbox simulates due sends. Live email needs explicit provider setup.
   03

   Working-day scheduleApproved plan

   FIRST REQUESTTuesday · 09:00

   Europe/London

   WED1THU2FRI3SAT—SUN—MON4TUE5

   Follow-up: the following Tuesday5 working days after the actual first send

   Business hours, configured holidays and send limits apply.

4. A RESPONSE CHANGES THE PATH

   A reply arrives. The chase stops.

   Priya’s reply is matched through a linked mailbox or recorded by your team. Pending sends stop and the request moves to human review. Mark the statement as received, record the evidence, and keep the missing receipts visible.

   Reply text is untrusted content; it cannot approve actions or change permissions.Still missing something?Propose a follow-up for just the missing items, then return to approval.
   04

   Request reviewReply recorded

   PPriya · Example reply

   “Here’s the bank statement.
   I’ll send the receipts shortly.”

   RECORDED MANUALLY BY YOUR TEAM

   Future sends stopped.Review before the next step.

   Statement receivedReceipts still needed

5. FINISH THE WORK, NOT JUST THE EMAIL

   Close the loop with evidence.

   When the receipts arrive, review them and save an evidence note. Complete the request only when every required item is supported. The saved activity history shows who did what and when.

   A sent email is a step. A completed request is the outcome.
   05

   October bookkeepingRequest complete

   Everything received.

   Two required items. Both supported by evidence.

   Bank statementReviewed by your team · Evidence note saved

   Expense receiptsReviewed by your team · Evidence note saved

   2 of 2 items checked. Request closed.

A CLEAR END TO THE CONVERSATION.

Less chasing.
More room for the work.

One saved plan. A visible next step. An outcome your team can account for.

Explore another example