FIG 0.1No fixed rosterAtlas, Mira and Vela are examples. Build a specialist for each job you repeat, and keep building.
Give the work a team. Keep the decisions.
Named agents work your orders, stock and customer messages across the systems you already run. You set what each one may do on its own, and route the rest to a person.
NewA voice for each agenthawi.
- Inbox4
- Triage3
- Ask Hawi
Workspace
- Dashboards
- Issues
- Projects
- Agents3
- Insights
- Pulse
- Voice
- Marketplace
- Integrations
Your team
- Members2
Ridgeline SupplyDashboardsNew
4 need attention
Agents ready
3
3 in this workspace
Working now
2
Runs moving through steps
Completed today
18
Recorded outcomes
Waiting
1
External event
Needs approval
3
Explicit sign-off required
Interrupted today
1
Failed or timed out
Currently working
2 visible- Resolve delivery postcode mismatchAtlas · ORD-4471 · started 8 min agoWaiting
- Draft replies for delayed ordersMira · 6 orders · started 3 min agoWorking now
Atlas run recordWAITING
- evri.track ORD-4471 → mismatch on delivery postcode
- evri.claims.open → CLM-88104
- Refund £42.60 held for your approval
Needs your attention
3- ORD-4471Refund £42.60Parcel scanned to the wrong postcode. Courier claim opened.
- SUP-118Reorder 40 unitsCeramic planter runs out in under three weeks.
- ORD-4463Send the delay replyDrafted by Mira. Not sent until you say so.
Release or hold an approval. The count and run record update together.
Every job gets a name on it. Orders, stock questions and customer messages arrive, go to whoever owns that part of the work, and stay on the record until someone signs them off.
- FIG 0.2Shaped around the jobInstructions, model, connected systems, permissions and spending limits are set per agent.
Order exception opened
The source message and customer stay attached.
FIG 0.3Work moves with its evidenceA handoff carries the original item, what the last agent found and the run behind it.- FIG 0.4Routine work routes itselfLabelled, assigned and put on a board as it lands, so people only open the exceptions.
Three worked examples, and the seat after them. Each agent holds one part of the operation, and each is built around that job rather than around a chat box.
- AtlasOrders, stock and suppliers
Counts cover against what is actually selling, raises the gap before a line runs out, and chases a late supplier on the schedule you set.
Your storefront and supplier mailbox connected.
- MiraThe inbox
Reads shared mail and marketplace messages, labels them, routes them to whoever holds that part of the job, and drafts the reply.
A shared mailbox, and each marketplace you sell on.
- VelaThe calls
Takes the call, writes down what was agreed, and opens the item on the board so the outcome is somewhere other than someone's memory.
A telephony provider. Live calling is not wired up yet.
- Your next agentAny recurring job
Describe the work in the Forge, choose its model and tools, then edit the instructions until the role fits your operation.
Whatever that job touches, and nothing else.
This sample alternates between working and paused. Its complete sequence is listed after the diagram.
AGENT PIPELINE / SAMPLE RUN
- Received: "Summarize Q3 performance for the stakeholder report..."
- Chunking input into 6 embeddings
- Vector search returned 5 relevant chunks
- Injecting workspace context into the prompt template
- Model inference dispatched 3 tool calls
- Email draft created and held for review
- CRM record flagged as reviewed
- Report queued for the configured dispatch time
- Workflow complete. 3 sample actions dispatched.
- Paused. Listening for the next trigger event...
Connections and scope
Enter your shop address to identify the platform, choose a connector and review its read and write scope before adding it to a workspace.
Add a connectionRead in your browser
Where do you sell?
Your storefront, your marketplace shop, or the address you print on an invoice.
How access is granted
- Sign in with the providerShopify, Stripe, Google
- Encrypted seller credentialsAmazon, Etsy, eBay
- Verified connector setupGmail, WooCommerce, help desks
Whichever route applies, it is set up once inside your workspace, signed in. Credentials are stored encrypted and never reach a page like this one.
What it would get
Give it an address and it writes out what an agent could read, and what it could only do with your press. Three answers are the same whatever you connect:
- Never, on any setting
- Spend, refund or pay. Governed by the ceiling you set on the agent.
- Give another workspace your credentials. Handoffs carry the work, never the keys.
- Act on a provider it has not been connected to. It says so instead.
Nothing was connected. This page has no signed-in session and no way to reach your shop.
Type your shop's address. It is read here in your browser and never sent anywhere.
202connectors33categoriesMarketplaces, couriers, accounting, support, payments, banking, voice and models.
- FreshBooks
- Google Ads
- Anthropic
- Amplitude
- Make
- GoCardless Bank Data
- Apify
- Adobe Commerce
- Close
- External MCP
- BigQuery
- AWS
- Docusign
- AliExpress
- Amazon SES
- Dynamics 365
- Google Forms
- Airtable
- Brevo
- Amazon Seller Central
- Calendly
- Adyen
- Hawi execution backend
- Google Calendar
- Asana
- Azure AI Search
- AfterShip
- AssemblyAI
- Box
- Freshdesk
- Discord
- Amazon Connect
- QuickBooks Online
- LinkedIn Ads
- AWS Bedrock
- Google Analytics
- n8n
- Plaid
- Bright Data
- BigCommerce
- HubSpot
- REST endpoint
- Databricks
- Azure
- Dropbox Sign
- AutoDS
- Gmail
- NetSuite
- Jotform
Fifty of 202. The rest run past below.
Intake and triage
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.
Shared inbox · orders@2 messages
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
Stock and suppliers
Recalculate stock cover from sales, compare listings with the stock sheet and schedule supplier follow-ups.
Stock coverCoveredThinRuns out
W34W35W36W37W38W39W40W41
Watchlists
AtlasSKU-0912
Ceramic planter, large has 3 weeks of cover at 1.6/day. Kemp & Sons take 7 days, so an order raised today lands with 2 weeks to spare. Raise it now or it goes to zero.
Pick any line and Atlas reads it back. Filter with the watchlists on the right.
Agents and handoffs
Set the model, tools and limits for each agent. Handoffs include the item, evidence and run history.
AtlasORD-4471Idle
- atlas · board: order-exceptions
- Reading ORD-4471 from the board
- shopify.orders.get ORD-4471 → fulfilled, 1 item, £42.60
- evri.track ORD-4471 → delivered 14:06 Tue
- Comparing the scan postcode against the order
- order CB1 2QP
- scanned CB1 2QJ
- Mismatch. This is a courier issue, not a buyer issue.
- evri.claims.open → CLM-88104
- Handing on: reply to the buyer, do not promise the refund
- Refund £42.60 held for approval
Example agents
These are examples. Your workspace roster grows with the jobs you create.
Held for you1
ORD-4471Refund £42.60
Courier scan disagrees with the order.
Financial actions above the ceiling go to the approval queue.
Type an instruction. Scripted responses, composed here — nothing leaves this page.
Approvals and limits
Compare the current record with the proposed change, then release or hold it. The decision keeps your name and timestamp.
ORD-4471 · proposed by Atlas1 action needs you
Now
- order ORD-4471
- buyer d.harper
- value £42.60
- status fulfilled
- courier Evri, delivered Tue
- claim none
- refund none
- buyer_reply none
- stock unchanged
- owner unassigned
- record none
If you release it
- order ORD-4471
- buyer d.harper
- value £42.60
- status exception
- courier Evri, postcode mismatch
- claim CLM-88104, opened 14:02
- refund £42.60 ← waiting on you
- buyer_reply drafted by Mira, not sent
- stock unchanged
- owner you
- record released_by · released_at
Whatever you pick is written on the order: what was asked, who decided, when.
Press either one. Release applies the change and signs it; Hold applies nothing.
Team and decisions
Keep the team conversation in the workspace, with the agents in the room. Turn a message into an assigned board item when it needs an owner, a status or agent work.
Channels
- YouYou
- Priya
- Dan
- Ruth
People only. Agents work the boards, not the channel.
opsAnything that stops an order going out
#ops
The beginning of the channel. Anything that stops an order going out.
Dan09:12
Two of yesterday's orders are still sat unfulfilled — both waiting on the same line.
Priya09:14
That'll be KL-220. The pallet's on the water, ETA's moved twice.
Ruth09:21
One of the buyers has already asked where it is. I've held off replying until we know a date.
Priya09:26
Atlas has drafted the delay email. It's sat waiting — I'd rather one of us read it before it goes to six people.
Dan09:31
I'll take it. If the ETA moves again we should stop promising dates entirely.
Lifted onto a board0
Nothing yet. Lift a message and it lands here with an owner, a board and a date — instead of scrolling out of the channel by Thursday.
Ask the channel for a refund and it becomes a held item, not a payment.
Say something, or lift any message onto a board. Replies are composed here — nothing leaves this page.
Runs and reporting
Open a daily brief, then trace any result through its inputs, tool calls, handoffs and decisions.
Exceptions raised, by weekW41 · 7
W30W41
Time to settle, medianW41
Atlas3h 10m
Mira1h 46m
You3h 52m
Illustrative figures. Your workspace shows its live run data.
Monday brief · W4108:00
This week, so far.
Two lines run out this week
Ceramic planter and wool throw. Reorders drafted, waiting on you.
Courier claims settled
Four closed since Friday. One still open with Evri.
Ardleigh has not confirmed
Third chase sent. Vela has a call prepared if you want it made.
Click any bar to read that week's brief. The tallest one is the week it went wrong.
W41. This week, so far.Dashboards and layout
Start from a ready-made dashboard or design your own. Every widget, chart, colour and typeface stays editable afterwards, and nothing you pick is a mode you get stuck in.
Agents ready
6
8 in this workspace
Working now
3
Runs moving through steps
Completed today
148
Recorded outcomes
Waiting
5
External events or decisions
Needs approval
2
Explicit sign-off required
Interrupted today
0
Failed or timed out
Currently working
3 visible- Resolve delivery postcode mismatchAtlas · ORD-4471Waiting
- Draft replies for delayed ordersMira · 6 ordersWorking now
- Reconcile supplier invoice INV-2210Atlas · accounts@Working now
Needs your attention
2- Refund £142.00ORD-4471Held
- Reorder 40 unitsCeramic planterHeld
Recent activity
Last 20 min- Draft preparedMira · ORD-4468 · replacement offered1m ago
- Stopped for approvalAtlas · refund £142.00 over the limit6m ago
- Handoff acceptedMira → Atlas · needs the order record9m ago
- Run completedSol · stock cover checked on 214 lines14m ago
The default. Dense, ruled, everything running on one screen.
Showing the Operations console dashboard.Calls and follow-up
A call is picked up under your rules, in a voice you pick per agent. What was agreed lands on the order, the calendar and the follow-up before the caller has hung up.
Supplier, restock date
Vela · Ridgeline Supply, this is Vela.
Caller · Calling about the planters — the 40cm ones.
Vela · You have two orders open with us. SUP-118 is the one waiting on a date.
Caller · We can ship the eleventh.
Vela · Eleventh. I'll put that against the order and tell Atlas.
Vela · Anything else changing on the price?
Caller · Same as quoted.
Vela · Noted. I'll confirm in writing.
What the call changed
- Done
Order record
SUP-118 opened
- Done
Order record
Restock date set — 11th
- Done
Handoff
Atlas notified, stock cover recalculating
- Waiting
Draft
Confirmation email drafted
The call ended. What it changed is on the right — the one that costs money is still waiting.
Call with Kemp & Sons ended.The working parts
- CoreBoardsOrder exceptions, returns, supplier chasing, listing quality. Build one or take a template.
- CoreApprovalsThe record as it stands and the change being proposed, side by side, with your name on whichever way it goes.
- CoreVoiceChoose a voice for each agent. Once telephony is configured, that saved voice answers its inbound calls.
- IntegrationsConnectorsGive an agent the inbox, CRM or work queue its job requires. Unavailable providers stay marked unavailable.
- IntegrationsMarketplaceAgents other operators built, installed into your workspace with their tools declared.
- IntegrationsDeveloper APIThree read-only endpoints, two scopes, keys you issue and rotate yourself.
- TeamTeam managementInvite the people who run the shop with you. Their conversation stays out of the agents' record.
- TeamAnalyticsVolume, time to settle and where work is queueing, by agent and by person.
For small retail operations
Marketplace seller
One stock pool across Amazon, Etsy and eBay. A sell-out has to reach the other two before somebody pays.
Direct-to-consumer shop
A storefront, an inbox that is also the support desk, and suppliers chased by hand.
Wholesale and trade
Repeat orders on account, long lead times, and prices that move. Every PO needs a person.
Priced per person, not per action
An agent that works harder should not cost more to keep. The approval gate is on every plan, including the free one — it is how the product is built, not a tier.
Plans and prices are shown on the sign-up page, read live from the billing catalogue so they always match what you would actually be charged.
NoteRuns and voice minutes draw on your plan's allowance. What is left is on the usage screen inside the product, before anything beyond it is charged.
Before you hand work over
Security boundaries
Workspaces are separate in the database
Not by a filter in application code. A query that forgets its clause returns nothing, not somebody else's orders.
Provider secrets never enter a workspace
A provider connects once to your account. The workspace selects that connection; it cannot read the credential.
Sessions are revalidated, not trusted
A suspended or deleted account loses access immediately rather than whenever its token happens to expire.
What shipped
The navigation the product needed
Product, Resources and Company are hover menus rather than flat links, and the footer carries every destination in five columns. Every route those menus name was built rather than linked to and left missing: customers, changelog, about, contact, security, docs and the developer API.
One accent, everywhere
The product accent is a single indigo across every signed-in screen, replacing a teal that read as fluorescent on the dark ground. Two chart series that had been rendering in the same colour are distinct again.
Developer API
Three read-only endpoints under /api/v1, two scopes, and keys you can issue and rotate from the workspace. The backend shipped before the console did; the console is now there.
Controls that stay on
It will not call something connected when it is not. Every provider states which route its access takes before you begin.
Provider states
It will not invent an order number, a policy, a date or an amount. Where a detail is missing it asks you for that one detail.
Drafting rules
Start with one agent and one job.