Your Field Service Software Has a Customer Portal. Use It.

Go into Jobber right now. Client Hub settings. Take a look at what's actually turned on.

If you've never been to that page — and most of you haven't — you're going to find a portal that's been sitting there, partially configured, since the day you signed up. Generic confirmation email with your company name and nothing else. Estimate approval: off. Automated appointment reminder: off. Post-job review request: off. Payment link exists, but nobody's ever told a customer it exists.

You're paying somewhere between $99 and $249 a month for this software. The portal is in the price. It's sitting at factory settings while your customers wonder what's happening with their job.

---

The Default Setting Nobody Changes

Jobber and Service Fusion both ship with a client-facing portal. Not a great portal. Not a custom portal. A functional one — customers can view their appointment, approve an estimate, pay an invoice, see their job history. Most of those features require someone to go into settings and flip switches.

Nobody flips the switches.

Every 3-to-7-truck residential shop I've talked to runs the same pattern. Owner signed up, got the scheduling working, figured out invoicing, and stopped. The portal got deferred during migration chaos and never came back up. That's it. That's the whole story.

I did the same thing with intake in 2022 — not the portal, but the same failure mode. The phone system was set up. The script existed. The process was broken and I didn't know it because I wasn't listening to the recordings. My NPS in month two was a 4. Not because the electrical work was bad. Because the customer experience between booking and invoice was a black box and customers were filling that black box with anxiety.

The portal problem is structurally identical: the software is there, the configuration isn't, and nobody's noticed yet because the consequences don't show up anywhere visible.

---

What Your Competitor Who Isn't Better Than You Is Actually Doing

This isn't about some better-capitalized outfit running circles around you. This is the shop two zip codes over — same truck count, roughly the same pricing, probably the same Google rating. They're winning some jobs you're not, and it's not because their guys are better.

They set up their portal.

When that shop books a customer, the customer gets an automated confirmation with the appointment time, the tech's name, and a link to approve the estimate. Two hours before the job, a text reminder goes out. After the job closes, a payment link and a review request. The whole sequence runs without anyone touching it.

I record every call. When I listen back to calls where we quoted a job and didn't get it, a few times I've heard the customer say, almost in passing, that the other shop sent something right away — that it felt more put-together, that they knew exactly what was happening. The work hadn't even started. We lost the job at the confirmation step.

If your booking confirmation is blank or generic, you're telling the customer something about how their job is going to go — and they're making decisions based on it.

If your portal isn't configured, you also have no data on whether customers who receive an online estimate close at a higher rate than customers who get a PDF. In my shop they do — meaningfully. But I only know that because the flow is running and I can see the numbers. If yours isn't set up, you're choosing not to know.

---

The Real Reason You Haven't Set It Up (It's Not Time)

Most of the time it's not that you didn't have time. It's that you don't believe your customers actually want a portal. Homeowners, probably 40 to 65, calling about a breaker or a bathroom exhaust fan — they want someone to show up and fix the thing, not a client dashboard.

That instinct isn't crazy. It's just not data.

Your gut after 4,000 service calls is data. After 80, it's hope. If you've run 300 jobs without a configured portal, you have zero information on how your customers would respond to one, because you never gave them the option. You have data on how they respond to the current experience. That's a different question.

The features I see shops skip most consistently: online estimate approval, automated appointment reminders, post-job review requests. All in Jobber. All in Service Fusion. All requiring someone to turn them on.

Here's the one that bothers me most. Shops spending $150 a month on NiceJob or Podium to generate reviews — but the job experience was opaque. Customer didn't get a reminder. Didn't have an easy way to pay. Had to call the office to find out when the tech was showing up. The review request goes out after all that. You're running a review tool on top of a customer experience that hasn't been finished. The review is supposed to be the output of a good experience, not a patch over the absence of one.

---

The Ninety Days That Actually Moved the Number

In month two of Reeves Electric, I started answering every call myself. Not because I planned to — because I listened to the recordings and realized I had no idea what was actually happening between ring and booked job. I'd assumed my dispatcher had it handled. The recordings said otherwise.

For ninety days I took notes. Not on what I thought was breaking. On what was actually breaking, based on what customers said, what confused them, where they dropped off. NPS went from a 4 in month two to an 81 by month nine.

What I learned wasn't only about the intake script. It was that I had to sit in the customer seat personally until I understood where the experience was failing. You can't fix what you haven't seen.

Same thing applies here. You have to run a test job through your own system and watch exactly what lands. Not what the help docs say the customer receives. What actually shows up — the confirmation email, the reminder text, the portal page, the payment screen — on a phone, with two bars of signal, while someone's at work.

Go create a fake customer in your system with your own cell number and email. Book a test job. Send yourself an estimate. Approve it. Close the job. Send the invoice. Pay it. Write down every point where the experience was confusing, missing, or embarrassing. That list is your configuration checklist.

---

When to Actually Build Something Custom (and When That's a Distraction)

There are real scenarios where off-the-shelf portals don't get you there. Multi-phase commercial service agreements with milestone sign-offs. A commissioning checklist that requires photo uploads at each stage. For those workflows, a Zapier-to-Airtable setup or a form tool like Jotform can handle the gap without a full custom build. I've done this for a couple of commercial clients — it works, it's cheap to build, and it doesn't take six months.

Residential service is not that workflow. A homeowner booking an EV charger install or a panel upgrade needs a confirmation, a reminder, a way to pay, and a review request. Jobber and Service Fusion do all four.

A custom portal project for a shop under $3M is a six-month detour. Real money on a developer or consultant, delayed twice, and you end up with something that covers 80% of what your existing software already does if you'd just configured it. I know two shops in Austin who went down this road — one came back to Jobber, the other is still maintaining custom code that nobody on the team can fully explain or update without breaking something.

My stack hasn't moved: Jobber or Service Fusion at the core, CallRail for tracking, Zapier or Make for the connective tissue, QuickBooks Online for accounting, one review tool (NiceJob or Podium, pick one). Everything beyond that is overhead, and a custom portal is well beyond that.

One real exception: if you're running a chunk of light commercial work with recurring service agreements and customers need to see contract status, upcoming visits, and invoice history in one place — a tool like HubSpot's client portal or even a structured Notion page can do real work there. That's not residential service. If that's your situation, you already know it.

---

What to Actually Do Monday Morning

This week:

Open Jobber or Service Fusion today. Client Hub settings in Jobber, Customer Portal in Service Fusion. Take a screenshot of what's currently enabled. That's your before photo.

Then run the test-customer exercise I described above — fake customer, your cell and email, full job flow from booking to paid invoice. Write down everything that was broken or missing.

Next week:

Work through that list in order: appointment confirmation first, estimate approval second, payment link third, review request fourth. One per day, test each one before moving to the next. Don't do all four on the same afternoon — you'll rush it and misconfigure something.

The finish line is specific: one real customer job runs through the complete portal flow by end of week two. Not mostly configured. Not "I think the reminders are on." One real job, full flow, you confirmed it worked.

After that, put a 30-minute calendar block on the same week as your monthly P&L close — every quarter — to re-run the test-customer exercise. The software updates, defaults change, automations break quietly. I've caught two broken flows in the last 18 months doing exactly this that I would not have found any other way.

---

FAQ

Do I need a customer portal if most of my jobs come from repeat customers who already trust me?

Yes, and the trust is exactly why. Repeat customers are your highest-margin work and your best review source. A portal makes the experience cleaner for people who are already inclined to book you — easier approval, faster payment, automated reminders so they're not waiting by the phone. The fact that they trust you doesn't mean they don't notice the difference between a smooth experience and one where they have to chase you for an invoice.

What's the actual difference between a portal in Jobber versus Service Fusion?

The core functionality is similar. Both handle appointment confirmation, estimate approval, online payment, and job history. Jobber's Client Hub has a cleaner customer-facing interface in my experience — the mobile view holds up better. Service Fusion's portal has more backend configuration options, which matters if you've already built out their workflow features. But the software choice matters a lot less than whether you've actually turned anything on. If you're already on one of them, don't switch to get a marginally better portal.

My customers are older homeowners. Are they actually going to use an online portal?

In my market — East Austin, mostly 40- to 65-year-old homeowners — portal adoption surprised me. The review request and the payment link get used consistently. Estimate approval is lower but not zero. The appointment reminder gets used regardless of age. Customers who won't use any of it aren't hurt by its existence — they still call, you still book them. But you're not running the shop exclusively for the least tech-forward person on your list.

If my CSR doesn't know how to walk customers through the portal, does the setup matter?

Yes, it matters. A configured portal that nobody on your team can explain is better than no portal, but it's not the full picture. Your CSR should know what the customer receives at each stage and be able to answer "what does that link do?" without guessing. One Google Doc with screenshots of the customer flow and a sentence explaining each step. Walk your CSR through it once. That's the training.

When does building something custom — Airtable, a client-facing dashboard — actually make sense?

When your workflow has a specific handoff that no standard portal handles and you can describe exactly what that handoff is. Multi-phase commercial service agreements with milestone approvals are a real example. A complex onboarding checklist requiring photos or signatures at multiple stages is another. Standard residential service — book, confirm, do the work, invoice, review — is not that case. If you're under $3M and primarily residential, a custom build is usually an expensive way to avoid configuring what you already have.

How do I know if the portal is actually working?

Two numbers to start: estimate approval rate (what percentage of estimates sent through the portal get approved online versus needing a follow-up call) and average days from invoice to payment. Both are in Jobber and Service Fusion reporting. A working portal should move payment time down and reduce the number of "did you get my estimate" calls your CSR is fielding. If neither number changes after 60 days, run the test-customer exercise again. Something in the flow is breaking before customers finish it.