A service-request note should be easy to scan in the office and useful at the job site. It should not read like a transcript.
The best format separates facts, caller language, urgency, and the agreed next step. That makes the note easier to review before it is entered or synced into Jobber or another field-service system.
Use a fixed note structure
Customer
Include:
- Full name
- Best callback number
- Email, if required
- Owner, tenant, property manager, or other role
Location
Include:
- Full service address
- Unit, suite, or building
- Access instructions
- Parking or site-contact details
Request
Write one sentence in plain language:
Upstairs bathroom drain is backing up when the sink runs; issue began this morning.
Keep the caller’s terminology when it matters. Do not turn a symptom into a diagnosis.
Details
Add only facts that help the next person:
- Equipment or affected area
- Make, model, or age when known
- What the caller can see, hear, or smell
- What has already been shut off, reset, or attempted
- Photos requested or received
Urgency
Use the categories your business defines, such as routine, priority review, or urgent escalation. Include the reason:
Priority review — caller reports no heat and an occupied home.
Avoid labels without context. “Urgent” means little if the team cannot see why.
Next step
End with the action that was actually agreed:
- Office to review estimate request
- On-call contact alerted
- Customer requested Tuesday morning
- Existing customer needs a callback
- Outside service area; no request created
Do not write “scheduled” if the caller only requested a time.
Example: weak note versus useful note
Weak
Customer needs plumber ASAP. Call back.
Useful
Customer: Dana Ruiz, 555-0142, homeowner
Address: 18 Willow Ave, basement entry at rear
Request: Water appears below the water heater; first noticed at 7:30 AM
Details: Caller shut off the nearby supply valve; photo requested by text
Urgency: Priority review — active moisture reported
Next step: Send summary to the on-call plumber; no arrival time promised
The second note gives the reviewer enough information to choose the next action without replaying the entire call.
Keep transcripts separate
A transcript can help with review, but it is not a dispatch note. Store the transcript as supporting context and put the structured summary where the team expects to work.
If a call contains uncertainty, preserve it:
- “Caller believes the unit is electric; not confirmed.”
- “Address repeated back and confirmed.”
- “Photo requested; not received at time of call.”
This is more useful than filling gaps with assumptions.
Create a pre-dispatch quality check
Before the request moves forward, confirm:
- Callback number is present
- Service address is complete
- Request is described without diagnosis
- Urgency includes a reason
- Access details are captured when relevant
- The next step does not overpromise
Use the same check for human and automated intake. Consistency matters more than who answered the phone.
Frequently Asked Questions
Should the full call transcript go into Jobber?
Usually the structured summary should be the primary note, with the transcript available as supporting context if your workflow allows it.
How long should a service-request note be?
Long enough to support prioritization and preparation, but short enough to scan. Use labeled fields instead of a long paragraph.
What if the caller does not know the equipment details?
Record that the detail is unknown. Ask for a photo when appropriate, and avoid guessing from incomplete information.
Turn missed calls into clear job requests.
Alice helps cover calls 24/7, asks your intake questions, and sends your team the details needed for the next step.
