Treat each promising email as an intake record, not a message to remember. Capture the customer, service address, requested outcome, constraints, source material, status, and one named next action before the thread leaves your screen.
What to carry into the work
- Separate genuine work requests from administration before doing anything else.
- Record facts from the email and mark missing details as questions—never guesses.
- Give every request one owner, one status, and one next action.
- Reuse the same intake record for the quote, appointment, job, and invoice.
1. Decide what kind of message you received
A busy inbox mixes new leads with supplier notices, receipts, newsletters, customer replies, and ongoing jobs. Starting by drafting a response is tempting, but the first useful decision is classification: is this a new opportunity, a reply about existing work, an administrative item, or noise?
That first label determines what happens next. A new opportunity needs intake. A reply should be attached to the current job. A receipt belongs with a purchase or expense. Noise needs no business workflow at all. Classification keeps the pipeline honest and prevents a friendly email from being mistaken for confirmed work.
- New opportunity: a customer asks about availability, price, or a service.
- Existing work: the message changes scope, timing, access, or approval.
- Administration: receipts, account notices, supplier updates, and documents.
- No action: newsletters, automated promotions, and unrelated mail.
2. Capture facts once
A customer request often contains more operational detail than it appears to. Pull out the customer name, reply address, phone number if supplied, service address, requested work, desired timing, access notes, and any photos or files. Preserve the original message so the summary can always be checked.
Keep facts and assumptions separate. If the customer says “the back tap is leaking,” that is a reported symptom—not a diagnosis and not permission to replace a fixture. Write unknown details as questions for follow-up. This small discipline prevents inaccurate quotes and promises.
Reported leak at rear exterior tap; began Saturday; customer is available after 3 p.m.; photo attached. Need service address, shutoff access, and confirmation of whether the line is still leaking.
3. Qualify the work before pricing it
Not every request is ready for a quote. Confirm that the service falls inside your area, capability, schedule, and minimum job size. Identify safety, permit, material, weather, or access issues that could change how the work must be assessed.
Use the fewest questions that can materially change the next decision. A short call or site visit is better than a long email chain when the diagnosis is uncertain. The goal is not to collect every possible detail; it is to collect enough reliable detail to choose between declining, visiting, estimating, or quoting.
- Where exactly will the work happen?
- What outcome does the customer want—not only what symptom do they see?
- Is there a deadline, access window, or dependency on another trade?
- Can photos, dimensions, model numbers, or a site visit reduce uncertainty?
4. Assign a visible next action
“Open” is not a next action. Use a specific instruction such as “call for measurements,” “prepare site-visit options,” or “draft quote after supplier price arrives.” Add an owner and a due time when more than one person can touch the request.
Statuses should describe where the opportunity is, while next actions describe what moves it. A lead can be “awaiting customer” with the next action “follow up Thursday.” That distinction makes the work understandable to someone who did not read the original thread.
5. Move the record forward instead of rebuilding it
When the opportunity becomes real work, carry the same customer, address, scope, notes, and source message into the job. The approved scope should feed the quote; the confirmed work should feed the schedule; the accepted line items should feed the invoice.
Re-entering details at every stage creates spelling errors, missed exclusions, incorrect addresses, and inconsistent totals. One connected record also preserves why a price or promise was made, which helps when a customer calls weeks later.
A two-minute intake review
Before leaving the request, verify that another person could understand it without opening Gmail. They should know who asked, what they want, where the work is, what is still unknown, and what happens next.
Automation can summarize and suggest, but a person should confirm customer identity, scope, pricing assumptions, availability, and anything that will be communicated as a commitment.
- Customer and service location are attached.
- The request is written as an observable need or desired result.
- Unknown details are listed as questions.
- Attachments and the original email remain available.
- Status, owner, and next action are visible.