Skip to main content

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 agent
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

  • delivery.events.read ORD-4471 → mismatch on delivery postcode
  • delivery.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.

  1. FIG 0.1No fixed rosterAtlas, Mira and Vela are examples. Build a specialist for each job you repeat, and keep building.
  2. FIG 0.2Shaped around the jobInstructions, model, connected systems, permissions and spending limits are set per agent.
  3. 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.
  4. 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.

Team agents

Drag to reorder. Click one to open it.

AtlasOrders, stock and suppliers

Hold cover against what is selling, and chase the supplier who is late.

WorkingSupervisedConfigured modelHeartbeat 12s ago

Runs today

34

Since 00:00

Settled

29

No person needed

Held for you

2

Waiting on a decision

Median run

1m 12s

Start to outcome

Handed on

3

To Mira or a person

Spend today

£0.94

Against your ceiling

Working nowSUP-118
  • atlas · cover check: ceramics
  • inventory.snapshot.read SKU-0912 → 6 on hand
  • orders.velocity.read SKU-0912 → 2.4/day over 14 days
  • Cover is under three weeks and the reorder lead time is four.
  • suppliers.read Kemp & Sons → SUP-118 open, no date
  • Drafting the chase, second one on this order
  • Reorder 40 units — £612.00 held for your approval
Watching
  • Storefront · orderslive

    Webhook, this storefront · Healthy

  • Stock levelsin 4m

    Every 15 minutes · Healthy

  • suppliers@ mailboxretrying

    Shared inbox, IMAP · Retrying

What it may touch
Read ordersRead stockDraft mailOpen a board itemRaise a PO
Needs you2
  • SUP-118Reorder 40 units · £612.00

    Above the £250 ceiling you set for purchase orders.

  • SUP-104Accept the revised price

    Ardleigh moved the unit price up 8%.

Handing on

Mira — Tell the two buyers waiting on SKU-0912

Voice · AtlasSpeech only. No call is placed.

“Kemp and Sons still have not given us a restock date on the large planters. That is the second chase, and cover runs out in under three weeks.”

Real speech, generated when you press it.

Reorder the team, open another agent, pause what it is watching, release what it held, or hear it speak.

Atlas — 2 waiting on you.

Connections and scope

Browse the providers Hawi currently makes available to customers. Availability comes from the connector registry, not from a marketing list.

  • AmplitudeAnalytics

    projects, events, retention

  • MakeAutomation

    scenarios, executions, webhooks

  • Magento / Adobe CommerceCommerce

    products, orders, customers

  • CloseCRM

    leads, contacts, activities

  • External MCP ConnectorsCustom

    initialize, tools list, tools call

  • BigQueryData

    datasets, read only query

  • AWSDeveloper

    sts, cloudwatch logs, lambda allowlist

  • Dropbox SignDocument Signature

    signature requests, signers, status

  • CJdropshippingDropshipping

    products, inventory, orders

  • MailgunEmail

    transactional email, delivery events

  • Oracle ERPERP

    ledgers, invoices, suppliers

  • JotformForms

    forms, submissions, webhooks

47available connectors16categories

Intake and triage

Mail, marketplace messages and stock alerts become board items with a source, status and owner.

1.0Intake

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.

2.0Watch

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.

3.0Act

AtlasIdle
  • atlas · board: order-exceptions
  • Reading ORD-4471 from the board
  • orders.record.read ORD-4471 → fulfilled, 1 item, £42.60
  • delivery.events.read 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.
  • delivery.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.

4.0Approve

ORD-4471 · proposed by Atlas1 action needs you

Now

  • order ORD-4471
  • buyer d.harper
  • value £42.60
  • status fulfilled
  • carrier network, delivered Tue
  • claim none
  • refund none
  • buyer_reply none
  • stock unchanged
  • owner unassigned
  • record none

If you approve it

  • order ORD-4471
  • buyer d.harper
  • value £42.60
  • status exception
  • carrier network, 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. Approve applies the change and signs it; Reject 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.

5.0Collaborate

ops

#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.

6.0Monitor

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 is still open with the carrier.

  • 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 mismatchWaiting
  • Draft replies for delayed ordersWorking now
  • Reconcile supplier invoice INV-2210Working now

Needs your attention

2
  • Refund £142.00Held
  • Reorder 40 unitsHeld

Recent activity

Last 20 min
  • Draft prepared1m ago
  • Stopped for approval6m ago
  • Handoff accepted9m ago
  • Run completed14m ago

The default. Dense, ruled, everything running on one screen.

Dashboard: Operations console.

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.

7.0Voice

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

  • Order record

    SUP-118 opened

    Done
  • Order record

    Restock date set — 11th

    Done
  • Handoff

    Atlas notified, stock cover recalculating

    Done
  • Draft

    Confirmation email drafted

    Waiting

The call ended. What it changed is on the right — the one that costs money is still waiting.

Call with Kemp & Sons ended.
0

is the spending ceiling you start on

Raise it per agent when you are ready. Anything above it goes to the approval queue.

Recorded before it is sent

Hawi writes the event first, then tells whoever else needs to know. If the message out fails, the record stays.

One trail, not two

Work started by a person, by an arriving message or by a schedule all land in the same history. Two logs that can disagree is one you cannot trust.

Anything that costs waits

A refund, a purchase, a message leaving the building. You see what it was about to do, in full, before it does it.

  • Refund ORD-4471Waiting
  • Reorder 40 unitsWaiting
  • Reply to a delayed orderWaiting
  • Stock cover recalculatedDone

Three waiting on a person. Nothing moved.

People and agents, one list

Same workspace, same permission model. So there is one answer to who can spend money here, not two.

Sam · ownerS
AAtlas · agent
Priya · operatorP

For small retail operations

All profiles
  • Marketplace seller

    One stock pool across connected marketplaces. A sell-out has to reach the other channels 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.

Questions and answers

What operators usually ask before they connect their systems, set an approval policy, and hand work to an agent.

Read the docs

Security boundaries

Read security details
  • Workspaces are separate in the database

    Database row-level security rejects records outside the active workspace.

  • 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

    A suspended or deleted account loses access on its next request.

What shipped

All releases
  1. Monochrome, everywhere

    The indigo accent is gone as well. The product is near-black, near-white and one neutral ramp; outside charts, amber, red and green appear only where they mean waiting, failed or settled.

  2. 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.

  3. 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.