Daily operations
The approval pass
Every action your agents propose lands in the approval inbox first. Nothing is sent, published, or recorded without your review. The daily pass takes under 10 minutes once your agents are calibrated.
When to do it
Once a day, in the morning. Your agents run overnight and early morning, so the inbox is usually full by the time you start your day. The Analyst report arrives Monday at 07:00 in your business timezone. Content drafts from the Marketer arrive every morning at 06:00. Support replies and Bookkeeper flags arrive within their run windows.
If you are on the Core or Pro tier, urgent items send a phone notification via ntfy as soon as they are created. You do not need to wait for the morning pass to handle those.
The workflow
- 1
Open the inbox
Go to app.flostackos.com/dashboard/approvals. Urgent items are pinned at the top with a red indicator. Work through urgent items first.
- 2
Read the title
Each card has a two-second-judgable title written by the agent: what it is, and one key fact. If the title tells you enough to decide, act without expanding.
- 3
Expand if needed
Tap the card to see the full draft. Support replies show the customer message and the draft reply side by side. Content drafts show the full text. Analyst reports show the full report.
- 4
Approve, edit, or reject
Approve: the action is queued for execution. Edit: change only what you need, then approve. Reject: the draft is discarded and an event is logged.
- 5
Handle escalation cards last
Escalation cards do not have a draft to approve. They are the Operator flagging something that needs your attention. Read the card, take the action it describes, then close it.
What the three actions do
Approve
The draft is marked approved and queued for the next agent action. For support replies, the reply is sent via Gmail (or your configured channel). For content, the post is pushed to your CMS as a published draft. For Bookkeeper journal entries, the entry is queued for your accountant. For the Analyst report, the report is published to your dashboard.
Edit then approve
Your edited version is saved and used instead of the original draft. The event log records that this was an edited approval. Your agents read approved-edit outcomes to calibrate future drafts.
Reject
The draft is discarded. Nothing is sent or published. The event log records the rejection. You can optionally note why. The agent does not automatically retry; the next run will produce a new draft based on current conditions.
Stale approvals
Drafts expire after 7 days by default. Expired drafts are removed from the inbox and logged as expired. The draft content is preserved in the event log for reference.
Support reply drafts have a shorter TTL by default because customer context changes quickly. If you see a reply draft for an old message, check whether the customer already resolved the issue before approving.