One of twelve office jobs see them all
Win the work Β· an office job you can pick
Prioritise the leads worth chasing first
Run your open leads against the rules you set, and get back an order with the reason beside every position.
Choose this office job and we build it around your process, systems, permissions and approval steps.
What it costs you now
Once the enquiries are getting answered, the queue stops being the problem and the choice starts being the problem. Forty open leads sit in front of the office with no order to them, so the ones that get chased are the ones that shouted loudest or came in last. The commercial job forty minutes away and the one you have no crew for this month look identical in a list.
What it does
You tell your agent the rules you already sort by: the kind of work you want, how far you will travel, and what you have capacity to start. It runs the open leads against those rules and hands back an ordered queue with the reason written beside every position, so you can see it decided on job type, not on a feeling. Where a lead is missing something the rules need, such as the suburb, it leaves that lead out of the order and drafts the question rather than guessing a place for it. It does not accept, decline or contact anybody.
- You state the rules Job type, distance and the capacity window you are actually working to, in your own words.
- Each lead is checked It reads the lead and the email thread behind it and tests them against your rules, one at a time.
- Gaps get held, not guessed A lead missing something the rules need stays out of the order and gets a drafted question instead.
- The queue comes back with reasons Every position carries the rule that put it there, ready for you to override.
You forward it. It comes back ready to work.
You ask in WhatsApp
Today
It hands back
LEAD QUEUE Β· 3 RANKED
Rule-based lead queue
- βChecked job type against the agreed fit rules
- βChecked location and the current capacity window
- βMarked missing inputs rather than giving them an assumed score
1Warehouse switchboardDandenong Β· commercial$18kβ$24kStrong fit Β· capacity this month
2Factory switchboard upgradeMoorabbin Β· commercial$12kβ$16kWithin 40 km Β· capacity this month
3Office switchboard upgradeAbbotsford Β· commercial$9kβ$13kSite walk complete Β· owner action ready
2 leads held unrankedSite suburb missing
Requests draftedReview before contact
A rule-based lead queue with visible reasons, missing-data holds and no hidden score.
Illustrative example. Names, numbers and records are made up.
What changes for the business
An ordered list of who to get back to first, with the reason beside each one and nothing hidden behind a score.
- The order stops being accidental
Which lead gets chased first is decided by the rules you set, not by whichever enquiry is nearest the top of the inbox.
- Nothing gets ranked on a guess
A lead missing the detail your rules depend on is held and asked about, so it never gets quietly sorted to the bottom.
- The judgement stays yours
The agent applies the filter and shows its reasoning. Accepting, declining and contacting stay with a person.
What it is connected to
Built around whichever of these you run.
These are the systems this office job usually touches, not a required stack. We connect only what your version of it needs, using your own accounts and the smallest set of permissions that does the job.
- ServiceM8 or Simpro The open leads, the job types and what is already booked.
- Your email The source thread behind each lead, and the drafted questions.
- Your calendar The capacity window, read from what is actually booked.
- Your rules, written down with you Job type, distance and capacity. These are yours, not ours.
- WhatsApp Asking the question and getting the queue back.
The boundaries come with the office job
Nothing reaches a customer without your yes.
What starts it, what it may read, what it may write, who approves, and where it stops. Written down before the office job runs.
What it will not doIt does not accept a lead, decline a lead or contact anyone. It only applies the rules you agreed, and where two leads come out equal, or a lead sits outside the rules entirely, it leaves them unranked for a person rather than inventing a tiebreak.
- Trigger
- The lead queue reaches the agreed review point or the office asks for a filtered view.
- Reads
-
- Lead details and source thread
- Current capacity window
- Business-defined fit and location rules
- Writes
-
- Rule-based lead queue
- Reason for each position
- Missing-information request drafts
- Approval
- A person decides which leads to quote, decline or contact; the agent only applies the agreed filter.
- Stops when
- Every in-scope lead is placed by rule or held with the missing input named.
- Exception path
- Missing data, equal outcomes, out-of-rule work and conflicting customer records remain unranked for review.
- Audit evidence
- Each position records the applied rule, source value, missing inputs and any person-led override.