Most calls to a service business are not problems. They are people asking where things stand. A portal answers that question without a phone ringing.
TL;DR Start with progress photos, documents and rescheduling. Skip everything else. If it needs a password reset to check a photo, nobody uses it. Push updates out as well as hosting them.
What actually gets used
Portals fail by including too much. Four features carry nearly all the value.
Progress photos and video. The single most-used feature in any service portal. People want to see the work, especially when they are not on site.
Documents. Quote, contract, invoices, warranty, certificates. One place, always accessible, no digging through email.
Messaging. A single thread per job, so the conversation is not split across text, email and voicemail.
Rescheduling. Let them move an appointment without calling. This removes the single most common inbound call.
Everything else is optional. Dashboards, project timelines with percentage bars, resource views, notification preference centres. All of it adds build cost and reduces the chance anyone logs in.
The login problem
A password is the reason portals go unused.
Better options
- Magic link. They click a link in an email or text and they are in. No password, no reset flow.
- Unique unguessable URL per job, with no login at all. Appropriate for non-sensitive content like photos and schedule.
- Phone number plus one-time code, if you need more security.
Judge the sensitivity honestly. Progress photos of a driveway do not need bank-level authentication. Invoices and contracts do warrant a magic link at least.
Push, do not just host
A portal nobody visits is a filing cabinet.
Every meaningful update should also go out as a message.
Day 2 update: old unit out, new one in, testing tomorrow. Three photos here: [link]
The link takes them to the portal. The message is what makes them look. Without the push, only the most anxious clients ever log in.
Frequency for a multi-day job: one update per working day, at the end of the day. More than that is noise, less than that is silence.
Photo discipline
The photos are the product. Treat them accordingly.
- Before, during, after. Always all three.
- Same angle each time, so progress is obvious.
- Good light, or use the flash. Dark photos read as hiding something.
- Include the difficult bits. Showing the mess mid-job then showing it resolved builds more trust than only showing the tidy end result.
- Caption them. One line each. “Old pipework removed, you can see the corrosion at the joint.”
Photos with captions are how you justify your price without talking about price.
Reduce the calls it was built to reduce
Map your inbound calls for two weeks. You will find the same handful.
| Call | Portal answer |
|---|---|
| “How is it going?” | Daily photo update |
| “When are you coming?” | Schedule view plus pre-visit text |
| “Can you resend the invoice?” | Documents section |
| “Can we move Thursday?” | Rescheduling |
| “What did you say the warranty was?” | Documents section |
Build for those five. Anything not on that list is speculative.
Build or buy
Buy, almost always. Most field service and job management platforms include a client portal, and building one is a software project you did not intend to start.
Check before committing
- Can clients access it without creating an account?
- Does it work properly on a phone? Test it, do not trust the screenshot.
- Can you push a notification when something updates?
- Can you upload photos from the field in a few taps?
- What does it look like with your logo?
If the technician workflow is awkward, the portal will be empty. Adoption fails on the field side more often than the client side.
The lightweight version
If a full portal is not justified, most of the benefit is available cheaply.
- A shared cloud folder per job, link sent at booking. Photos and documents dropped in.
- A single text thread kept open for the duration of the job.
- A booking link for rescheduling.
This covers three of the four features for essentially nothing and is the right starting point for most small operators.
Measure it
- Inbound “how is it going” calls, before and after.
- Portal open rate per update sent.
- Rescheduling done self-serve versus by phone.
- Reviews mentioning communication. This is where the effect shows up most clearly.
What to avoid
- Making it the only channel. Some clients will always phone. Let them.
- Stale content. A portal last updated four days ago is worse than none.
- Requiring an app download. Web link or nothing.
- Hiding the invoice behind the portal as a payment tactic. Send the invoice by email too.
Start with a shared photo folder and a daily update text on your next multi-day job. If the calls drop, you have proved the case before spending anything on software.
Need a pro to set it up? [BOOK A CALL]