Answer the jobs worth answering.
Two scores on every quote request: what the job is worth, and whether it is right for your shop.
Fit
Opportunity
Who to call
16 this week- 01
Hot water tank leaking, basement, need someone today
7986
- 02
Burst pipe under the kitchen sink, water everywhere
8874
- 03
Sump pump failed, water in the basement
7483
- 04
Quote for rough-in, 14 unit build, Oakville
9258
- 05
Frozen pipe, no water to the kitchen
6978
- “Hot water tank leaking, basement, need someone today”
- “Quote for rough-in, 14 unit build, Oakville”
- “Toilet running, can wait”
Every request lands in the same queue.
- Forward the emails you already get
- Your own request page, on your own link
- A spreadsheet, imported
- Zapier or your CRM, through the API
- Phone calls and walk-ins, typed in
- 01
Scored on arrival
Two numbers and the signals behind them, in seconds. The queue reorders itself.
- 02
A reply is drafted
Written from the request and from what your shop actually does.
- 03
A person approves it
Held for approvalNothing sends until someone on your team has read it and said yes.
“Burst pipe under the kitchen sink, water everywhere. Shut the main off. Need someone today.”
88Opportunity
- emergency language
- “water everywhere”, “need someone today”
- same-day intent
- Asked for today
- in service area
- 6 km from your shop
- repeat customer
- Second request in 14 months
- unknown access
- No mention of who lets you in
- no photos
- Nothing attached to size the job
Emergency water damage in your service area, from a customer you have served before.
Every score shows its work.
Illustrative. Weights are the model's account of what moved a score, not a sum that adds up to it.
Nothing reaches a homeowner without a person.
- 01
The send gate is in the database, not the interface
There is no setting that turns it off. A draft cannot become a sent message without a person on your team approving it.
- 02
Your requests are yours alone
Every query is scoped to your company. No shared pool, no lead marketplace, and nobody else ever sees a request that came to you.
- 03
Homeowner details are treated as personal information
From the moment they arrive, with PIPEDA obligations designed in rather than bolted on afterwards.
Priced by your team, not by how busy you are.
Stop answering in the order they arrived.
Score the requests you already get, and answer the ones worth answering first.
Create your account