Demo, Runs in this browser only, Fictional data
Sort a day’s inquiries into one review queue
Edit a fictional day of customer inquiries and set your follow-up limit. See which ones need an owner, a next step or a reply first, and the reason for each.
One check a first Build process could run, here on invented records. It sorts and explains; it does not draft or send replies, and it does not measure time saved.
01 The inquiries
Seven inquiries from a fictional heating and plumbing company. Invented records. Use made-up IDs and roles, never real customer names or contact details.
Turn on JavaScript to edit this sample and run the check yourself. The result below was computed from this sample by the same rules when the page was built.
- Follow-up limit (hours)
- 24
| Inquiry ID | Inquiry | Channel | Waiting (hours) | Owner | Next action | Status |
|---|---|---|---|---|---|---|
| Q-2041 | Boiler service, repeat customer | Web form | 3 | Office manager | Send quote from the price list | New |
| Q-2042 | Leaking pipe, new customer | Missed call | 30 | — | Call back | New |
| Q-2043 | Full system replacement | 26 | Owner | Book a site visit | Quoted | |
| Q-2044 | Asks for 15% off a service | 5 | Owner | — | New | |
| Q-2043 | Full system replacement, second email | 2 | Office manager | Reply with visit times | New | |
| Q-2039 | Quote sent last week, no reply | 52 | Office manager | Send a short follow-up | Waiting on customer | |
| Q-2035 | Radiator bleed | Phone | 70 | Office manager | Visit booked for Thursday | Booked |
Inquiries
| Row | Inquiry ID | Inquiry | Channel | Waiting (hours) | Owner | Next action | Status | Remove |
|---|---|---|---|---|---|---|---|---|
| Row 1 | ||||||||
| Row 2 | ||||||||
| Row 3 | ||||||||
| Row 4 | ||||||||
| Row 5 | ||||||||
| Row 6 | ||||||||
| Row 7 |
Up to 12.
02 The result
FIX FIRST Fix 2 records before anyone replies
Fix 2 records before anyone replies. Queue of 6: 2 to fix first, 2 to act on now, 1 to check, 1 on track. 1 booked or closed left out. Nothing was drafted or sent.
- In the queue
- 6
- Fix first
- 2
- Act now
- 2
- Overdue
- 3
- Booked or closed
- 1
Review queue, in order
- Fix first1. Q-2043 · Full system replacement
- Duplicate ID: rows 3 and 5 all use Q-2043. Merge or renumber them so one customer does not get two replies.
- Overdue: waiting 26 h, at or past your 24 h follow-up limit.
- Fix first2. Q-2043 · Full system replacement, second email
- Duplicate ID: rows 3 and 5 all use Q-2043. Merge or renumber them so one customer does not get two replies.
- Act now3. Q-2039 · Quote sent last week, no reply
- Waiting on the customer for 52 h, at or past your 24 h limit: a follow-up is due.
- Act now4. Q-2042 · Leaking pipe, new customer
- No owner. Nobody is responsible for the reply.
- Overdue: waiting 30 h, at or past your 24 h follow-up limit.
- Check5. Q-2044 · Asks for 15% off a service
- No next action written down.
- On track6. Q-2041 · Boiler service, repeat customer
- Owner and next action set; waiting 3 h of your 24 h limit.
Left out of the queue
- Q-2035 · Radiator bleed: Booked: no action needed.
Each download is labelled as a demo export of fictional data checked in a browser, with the rules version and an input fingerprint. Entries that start like a spreadsheet formula are saved as plain text.
03 The rules
This is the whole check, with your current settings filled in. Nothing else is weighed, and the same entries always give the same result.
- Booked and closed inquiries leave the queue, unless their ID is missing or repeated.
- Fix first: a missing or repeated inquiry ID, or no record of how long it has waited. These are how a customer gets two replies, or none.
- Act now: no owner, or waiting 24 hours or more, your follow-up limit. For “Waiting on customer”, reaching the limit means a follow-up is due.
- Check: an owner, but no next action written down.
- On track: an owner, a next action and time left before the limit.
- Within each group the longest wait comes first; ties keep your row order.
- Nothing is drafted or sent. The queue is a list for a person to work through.
04 What this shows
What it proves
- The rules are written out in full, and every inquiry shows which rule placed it.
- Missing or repeated records are caught before anyone replies, and nothing counts as on track without an owner and a next step.
- The same entries always give the same queue.
What it does not
- It is not your inbox, CRM or phone system, and it has not been connected to one.
- It does not draft, send or book anything, and it is not evidence of time or money saved.
- Real volumes, rules and approval limits would come from your business when we scope the work.
A demonstration of the method on fictional data, run entirely in this browser tab. It is not an AI model, not a customer implementation, not proof of delivered savings, and not a substitute for your own procurement or security review.
Want a check like this built on your own work?
Is this a fit? → Ask about a Consult block See the worked example
Consult: $2,000 for 5 hours. Build: $45,000 minimum over 3 months, from $15,000 a month. The fit guide explains which, if either, suits your work.