1.0Intake
Turn incoming messages into assigned work
Mail, marketplace messages and stock alerts become board items with a source, status and owner.
Triage12
ORD-4471
Parcel scanned to the wrong postcode
Refund
ORD-4468
Buyer asking to change size before dispatch
SKU-0912
Listing quantity below stock sheet
Stock
ORD-4455
Second chase on a late supplier order
ORD-4449
Address looks wrong, two door numbers
Delivery
Queued34
ORD-4402
Damaged on arrival, photos attached
Returns
SUP-118
Confirm restock date with Kemp & Sons
ORD-4390
Duplicate order placed twice
SKU-0388
Wool throw down to two in stock
Stock
ORD-4377
Buyer wants to combine two orders
Working2
ORD-4463
Drafting the reply about the delay
Draft is 62 words. Not sent.
Mira
SUP-104
Chasing Ardleigh on the late pallet
Third chase written, holds them to a date.
Atlas
Settled61
ORD-4287
Refunded after your approval
Refund
SKU-0771
Reorder raised with the supplier
ORD-4301
Replacement sent, buyer happy
ORD-4295
Partial refund released by you
Refund
Drag a card into Working and an agent picks it up. Or write to the shared inbox below.
d.harper Still nothing on 4471, tracking says delivered. Can someone look?
sanka raise the courier ones and put them in front of me@Hawi
Connectors are set up inside your workspace and never on a public page. Which providers use a native consent flow, which store an encrypted credential and which are still in preview is stated on the connector itself, before you connect it.
Channels
One board for every place work arrives
A small shop's work does not arrive in one place. It arrives in a shared mailbox, in four marketplace message centres, and in a stock sheet nobody has opened since Friday. Intake connects those and puts what comes out of them on a single board.
- 1.1Shared mailboxesGmail and Microsoft 365 connect through their own consent screens; anything else comes in over IMAP with the credential encrypted at rest. The mailbox is connected once, inside your workspace.
- 1.2Marketplace messagesAmazon Seller Central, Etsy, eBay and TikTok Shop. Buyer messages land on the same board as the mail, so a question about an order sits next to the order.
- 1.3Stock signalsA line falling under cover, a listing disagreeing with the sheet, a supplier past their promised date. These open items on their own rather than waiting for someone to notice.
- 1.4Forms and webhooksA returns form on your own site, or anything that can post JSON, becomes an item with the payload attached. No agent required to receive one.
Triage
Routed and labelled before you look at it
The point of intake is not a bigger inbox. Every item that arrives is read once, given a label, and put in front of whichever agent or person owns that kind of work — so the first thing you see in the morning is a queue with owners on it rather than a pile.
- 1.5Rules you can readRouting is a list of conditions in plain language, not a model deciding privately. You can see why an item went where it went, and change it.
- 1.6DuplicatesA buyer who emails and then messages through the marketplace is one item with two sources on it, not two items that get answered twice.
- 1.7Priority and ageItems carry how long they have been open and what happens if they stay that way. Age is a column you sort by, not something you have to remember.
- 1.8Nothing unownedAn item that matches no rule goes to a named fallback rather than an unwatched column. There is no state in which work is in the system and nobody has it.
Boards
A board per job, or one from a template
Order exceptions, returns, supplier chasing and listing quality each want different columns. Build the board you need, or start from one of the templates and change it — the columns are yours, and the items move through them by rule or by hand.
- 1.9TemplatesPre-built boards for the four jobs most shops run, each with its columns, labels and default routing already set up.
- 1.10ViewsThe same items grouped by status, by agent, by age or by marketplace, saved as a view you can return to.
- 1.11The itemEvery item keeps its source, what was read, what was decided and by whom. Opening one tells you the whole story without leaving it.
The rest of the system
- 2.0WatchCover counted against what is selling, so a line that runs out is flagged early.
- 3.0ActNamed agents work the item and hand it between themselves with the evidence attached.
- 4.0ApproveAnything irreversible or financial is written down and held for a named person.
- 5.0MonitorWhat moved, what is stuck, and what is waiting on you — with the numbers behind it.
- 8.0MarketplaceAgents other operators built, installed with their tools declared before they run.
- 9.0LimitsA ceiling on what runs unattended, and the actions no ceiling ever covers.
- 10.0BoardsOne board held by people and agents alike, where the column follows the owner.
- 11.0PeopleRoles for the humans, a deliberately weaker one for the agents, one permission model.
- 12.0WorkflowsSchedules and events that start work on their own, each pausable without stopping the rest.
Start with one agent and one job.