Skip to the page

Solutions · Operations

The routine runs. You decide what goes out.

Ask which open orders are past their due date and get the count, the value and the list. Let a morning flow find them for you, try it first, and decide what goes out on one Waiting page.

Nobody approves their own proposal

Tarnwick Supply Co.WaitingSample data
WaitingWaiting 4
1Everything waiting, on one page
ApprovalsQuestionsFailed runsHanded to me
Select manyOne reason for all
Late-order remindersSend 6 messages? · from a flow, 08:00ApproveDecline
2Read each message before it goes
Supplier invoice checkFlag a mismatch on VT-5512? · proposed by an agentApproveDecline
3Nobody approves their own proposal
Hand late orders to Sales North5 rows handed to you
Morning late-order checkthe run failed: needs a sign-inSign in again
  • 1Everything waiting, on one page
  • 2Read each message before it goes
  • 3Nobody approves their own proposal

Six questions operations leads ask.

  1. 01

    "What is waiting for my yes today?"

    One Waiting page holds the approvals, questions and failed runs from your flows and agents, with a count in the top bar.

  2. 02

    "Which open orders are past their due date, and what are they worth? Show their due dates."

    The count, the value and the list of orders, each with its due date.

  3. 03

    "Which orders are due this week and not yet delivered?"

    The open orders due that week, as a list you can sort and download.

    Built withAI Assistant
  4. 04

    "Which stock isn't moving, and how much money is tied up in it?"

    The ready-made analysis "Stock that isn't moving" shows the money tied up by store and item, each line with what to do: sell it off, stop reordering, check demand or order less.

  5. 05

    "Which runs failed today, and why?"

    The runs page has a "Failed today" view. Failures are sorted by kind (a sign-in, a busy system, refused data, a limit), and a failed run can carry on from the step that failed.

    Built withWorkflows
  6. 06

    "Here is a scanned delivery note. What was delivered, and on what date?"

    It reads the scan and answers.

    Built withAI Assistant

One question, all the way to your yes.

On Tarnwick Supply Co., sample data, with its order system connected through its web API (a flow cannot read a connected database today).

  1. 1

    Ask.

    "Which open orders are past their due date, and what are they worth? Show their due dates." The answer: 37 orders, what they are worth, and the list with each due date. Ask "only the ones for Quellmark Foods" and it carries on.

    AssistantLate ordersSample data
    Which open orders are past their due date, and what are they worth? Show their due dates.
    Assistant

    37 orders, worth $184,920.

    OrderCustomerDue dateValue
    SO-10482Quellmark Foods20 Oct$12,840
    SO-10455Fenwright Builders24 Oct$9,615
    SO-10471Lumora Hotels26 Oct$8,930
    Showing 3 of 37Download to Excel
  2. 2

    Keep it.

    A board "Late orders", by region and by status. A click on a row can open the order in your order system. Make it the page your team opens first.

  3. 3

    Have it checked every morning.

    A company owner builds a flow in the flow designer: every morning at seven it reads the open orders past their due date, writes a message for each one to its customer from that order's own figures, and waits at an "Ask someone first" step. Try it first: nothing is sent and nothing is changed.

    Morning late-order checkFlow designerSample data
    Every morning at 07:00
    Read open orders past due37 rows
    Write a message for each late orderfrom the order's own figures
    Ask someone firstDana Ortiz
    Send the e-mail
    • Try it first: nothing is sent
  4. 4

    Decide on one page.

    The card waits on Waiting. Read each message as it will go out, and fix a line where the step allows. Approve many at once with one reason. Each request runs once, even if two people press together, and nobody approves their own proposal.

    Read each message before it goes

    WaitingMorning late-order checkSample data
    Send 37 messages?Morning late-order check · Ask someone firstWaiting for your yes
    To Quellmark Foods · message 1 of 37

    Dear Quellmark Foods, your order SO-10482, due on 20 October, …

    Edit
    Approve 37Decline
    Read each message before it goes
    • Read each message before it goes

Where wording must never change, a template step writes each message from your own words, with no AI at all.

Runs you can rely on, on a busy day.

  • A flow can start on a schedule, when someone presses Run, or when another system calls its web address.
  • Try a whole flow on your real data first. Each step that would leave the company says what it would have done.
  • Each step can try again 2 to 10 times, with a pause between tries. A busy system is tried again later by itself, after the wait that system asks for.
  • A step about to send or create more than 100 things in one run waits for a person's OK.
  • A run can wait days for an approval or a set time, then carry on where it stopped.
  • When a run fails, gives up or needs a sign-in, the flow shows one notice and its owner gets one e-mail. The next run that ends well clears it.
  • A failed run can undo what it wrote, newest first. What cannot be undone is listed.
  • A calendar shows when each flow runs next, beside your company's holidays and events.
  • Each item is sent or written once, even after a retry, a restart or the next day's run.
Workflows
Morning late-order checkRuns · today 07:00Sample data
Read open orders past due37 rows
37
Write a message for each37 drafts
37
Ask someone firstwaiting
In 37 rows
OrderDue date
SO-1048220 Oct
SO-1045524 Oct
SO-1047126 Oct
Out 37 drafts
ToMessage
Quellmark FoodsDear Quellmark…
Fenwright BuildersDear Fenwright…
Lumora HotelsDear Lumora…
Late-order remindersFailed today at step 4 · a busy systemRetry from the failed step
Carry on from the step that failed
  • Carry on from the step that failed

A routine job for an agent.

  • Your company's owner makes the agent: describe the job in your own words, as you would brief a new colleague, for example "check supplier invoices against their orders".
  • Give it the documents it should know and the flows it may run, each marked "looks things up" or "changes something: asks a person first".
  • Try it on the same page. It looks things up for real and says what it would change, without changing anything.
  • Put it to work in a flow, on a schedule or started by hand. Anything it would change or send waits on your Waiting page. It never approves its own work.
AI Agents
Supplier invoice checkAgents · version 1Sample data
The job
Check supplier invoices against their orders.
Documents it knows
Purchase terms.pdf
Flows it may run
Find the order · looks things upFlag a mismatch · asks a person first
Try
Check invoice VT-5512 from Varnholm Tools against its order.
Supplier invoice check

Order PO-3307 has 40 units at $18.40; the invoice charges for 44. Flag a mismatch? This waits for a person.

  • Never approves its own work

The late list over time, and on a map.

  • Keep a daily copy of the open-orders list from a system with a web API, and a board shows late orders by status, week by week, from the day the copy starts.
  • Each change is kept with when it happened, field by field, such as a due date moved. An order that disappears is marked, not erased.
  • In the designer, put open orders on a map: points, filled areas, bubbles or pies, over built-in base maps or your own map file. Maps are built by hand, not by asking.
  • A board says when it was updated, and Refresh asks again.
Late orders over timeBoardSample data
Late orders over timeUpdated 07:02 · Refresh
Late open orders by status
Waiting for stockPickingReady to ship
0153045Wk 40Wk 41Wk 42Wk 4341Wk 44Wk 4537
Starts the day you turn the copy on
Late order value by regionNorth$71.4kEast$48.2kSouth$38.6kWest$26.7kFrom Tarnwick's own map file
  • Starts the day you turn the copy on

What your team can share.

  • Share a flow with people, roles or the whole company, to view or to edit. Members can see a flow shared with them, and run it when it is shared with Edit. Only owners build and change flows.
  • Choose who decides each approval: a named person, a role or a team.
  • Share a board with your team. People who join the team later get it too.
  • A team lead arranges the team's menu and the page the team opens first.
  • Share an analysis so each person sees only their own rows.

What it does not do yet.

So you know before the demo.

  • A flow cannot read a connected database yet.It reads systems with an API and the ready-made connectors.
  • Flows that start when an e-mail, a form or a file arrives are not ready for customers yet.
  • It does not build a flow from a sentence yet.A company owner builds it in the flow designer.
  • It does not compare two dates on the same row yet, such as orders delivered after their due date.
  • Attached Excel and Word files are not ready yet.PDFs and readable scans are.

The engines behind these answers.

Workflows

Automations you try first, that can ask before they act.

Workflows

Dashboards

Late orders in view, a click from the order itself.

Dashboards

Also behind these answers: AI Agents · History engine.

Bring this morning's exception list.

In the demo we connect one of your systems, and you ask the questions.