Solutions
Before the customer calls. See what is late, every morning.
Ask which open orders are past their due date and get the count, the value and the list. Keep it on a board, and let a morning flow tell each account manager, with any message to a customer held until a person says yes.
| Customer | Value | |
|---|---|---|
| Quellmark Foods | $12,840 | Open in Orders |
| Fenwright Builders | $9,615 | Open in Orders |
| Lumora Hotels | $8,930 | Open in Orders |
Open the order in
your own system
- 1Count, value and the list
- 2Waits for a person’s yes
Sounds familiar?
In the words operations teams use:
A late order surfaces when the customer calls.
The morning list is built by hand.
Nothing warns anyone when an order goes late.
How it works at Tarnwick.
On Tarnwick Supply Co., sample data.
- 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.
AI Assistant - 2
Narrow it. “Now only the ones in the North region.” It carries on from the last answer: 14 orders and their value.
AI Assistant - 3
Keep it on a board. Ask for the board, or build it in the designer. Click a region to filter the rest, drill from region to customer, and open any order in your order system. The board says when it was updated, and Refresh asks again. Make it the page your team opens first.
Dashboards - 4
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 and sends each account manager one message with their own orders.
Workflows - 5
Draft the customer messages, and wait. A step can write a message to each customer from that order’s own figures, and stops rather than send one with a required field missing. An “Ask someone first” step holds them all until a person says yes.
Workflows - 6
Try it, then read each run. Try the flow first: nothing is sent and nothing is changed. Each morning’s run shows on the flow’s page, under Runs: what each step did, and the rows it found.
Workflows
12Ask, then narrow it
37 orders, worth $184,920.
| Customer | Due date | Value |
|---|---|---|
| Quellmark Foods | 20 Oct | $12,840 |
| Fenwright Builders | 24 Oct | $9,615 |
| Lumora Hotels | 27 Oct | $8,930 |
14 orders, worth $71,400.
45The morning flow
6Read each run
Is it getting better?
Your order system shows which orders are late today. It may not show how many were late last month.
- Keep a daily copy of the open orders list with the history engine, counted by a field such as status or region.
- From the day the copy starts, a board can draw those counts week by week. If your system marks late orders in a field, late orders get their own column.
- Each change is kept with when it happened: “status: Open → Delivered”.
Starts the day you
turn the copy on
What you get.
The late list as an answer, with each due date, ready for Excel.
A board of late orders your team opens first, a click away from each order.
A morning flow that tells each account manager, and holds customer messages for a yes.
Open orders week by week, by status, from the day the copy starts.
Before you start.
- The flow reads orders from a system with an API, or from a ready-made connector. It cannot read a connected database today.
- The history copy works on systems with a web API and the ready-made connectors, and it starts on the day you turn it on.
- A flow does what its steps say. Put the “Ask someone first” step before anything that goes to a customer.
- A company owner builds the flow. Members can see it, and run it when it is shared with Edit.
What it does not do yet.
So you know before the demo.
- It does not compare two dates on the same row yet,such as orders delivered after their due date.
- It does not build the flow from a sentence yet.A company owner builds it in the flow designer.
- In the chat, it does not rank what rose or fell.Draw it on a board instead.
For everything operations runs, see Operations. Operations
Bring this morning’s exception list.
In the demo we connect one of your systems, and you ask the questions.