Field Service Customer Portal Development

What customers expect from a field service portal

Homeowners and facility managers want different things from a portal, and Tepia designs for both. A homeowner with a noisy furnace wants to book a visit tonight, know who is coming, and approve the repair without a phone call. A facility manager responsible for 60 restaurants wants to submit a walk in cooler issue with photos, see which locations have open work, and download every completed report before an audit.

Both groups share one expectation: the portal must reflect reality. If the portal says a technician is on the way while dispatch has reassigned the job, trust disappears in a single visit. Tepia builds portals on the same live data your dispatchers see, so the arrival window, technician details and job status are always current.

The portal also becomes the place where your company shows its work. Photos of the cleaned coil, readings from the tune up and the technician’s notes turn an invisible service into something the customer can see, which is what keeps them booking with you instead of the next search result.

Portal capabilities for homeowners and commercial clients

Tepia scopes the portal by audience. Most field service companies need some version of this matrix:

Tepia usually launches the homeowner side first, because it reaches the most people, then adds commercial roles once the core data flows are proven.

Building the portal on your existing field service data

A portal is only as good as the data behind it. Tepia connects it to your field service management system, whether a platform such as ServiceTitan or Jobber or a system we built, through APIs and webhooks so status changes appear within seconds. Arrival estimates come from the technician app’s location while the job is active, and stop when the job closes.

Security is designed in from the first wireframe. Homeowners sign in with a one time link sent by text or email, avoiding forgotten passwords. Commercial users can use single sign on through Microsoft Entra ID or Google. Payments run through Stripe or Square so card numbers never touch your servers, and every page is built to WCAG 2.1 AA so customers using screen readers can book and pay. Tepia can deliver the portal as a responsive web app, a progressive web app, or native iOS and Android apps under your brand.

How Tepia approaches field service customer portals

Tepia follows the same six phases on every portal project, and a US based project manager owns the timeline.

1. Discovery: analysis of a month of inbound calls by reason, interviews with CSRs and a few loyal customers, and a review of the APIs your platform exposes. Deliverables are an Investigation Summary, an Interview Summary and User Stories such as a property manager approving a repair for a tenant’s unit from her phone.
2. Design: a design questionnaire, moodboards and a style guide matched to your brand, then wireframes and sample designs of booking, tracking and history screens, tested with real customers.
3. Development and Testing: an Alpha with staff acting as customers and a Beta with a small group of members, covering functional, accessibility, load and user acceptance testing.
4. Training: remote sessions for CSRs and dispatchers on how portal requests reach them, plus help content for customers.
5. Launch: import of customer accounts and history, invitations sent in waves, and support reps watching the first requests come in.
6. Support: quick issue response, bug tracking and feature requests such as adding membership upgrades to the portal.

Discovery typically runs 1 to 3 months and development and QA 2 to 6 months, with roughly a month to launch. Read our process for detail.

How to tell whether the portal is working

Tepia defines success measures in Discovery and builds them into the admin dashboard from day one. The useful ones are the share of bookings made online, inbound calls per completed job, the time from completed work to payment, how often commercial users download reports, and the percentage of customers who open the arrival link. If calls asking where the technician is do not fall within a few months, something in the experience needs work, and Tepia treats that as a support priority rather than a future idea.

Adoption also depends on small moments outside the portal. A confirmation text with a tracking link, a post visit message with photos and the report, and a reminder that an included tune up is due all pull customers back in. Tepia designs those messages together with the portal screens so the first visit feels like the start of a relationship, not a one time transaction.

Platform portal or a custom one

Many field service platforms include a basic customer portal, and for a residential company with simple needs it can be enough. Tepia recommends a custom portal when you serve commercial clients with many locations, need approval flows tied to purchase orders, want a branded app in the stores, or run several systems that customers should see as one. A hybrid that keeps your platform as the system of record and adds a custom portal on its API is the most common path. Learn more about our general customer portal development, see our work, or talk to Tepia.

Frequently asked questions