Help customers find their service information and next step

WorkOrderPro product guide · Updated 12 September 2026.

What a service customer portal should make easier

A customer portal gives an invited customer a place to inspect the service information your business makes available to them. Its value is practical: finding a job reference, checking the recorded appointment, looking up previous work or reaching the correct next action. It should help the customer answer a recognisable question without needing an employee to read the same record over the phone.

WorkOrderPro's portal includes customer job history, job details and a service-request workflow. Relevant screens also cover invoice information, equipment and maintenance records, subject to the enabled product features and customer access. The portal is part of the service operation, so its usefulness depends on the office and field team maintaining clear, current work records.

Start by choosing which customer task you want to improve. A facilities contact may need history across repeated visits. A household customer may mainly want to recognise an appointment and understand the outcome. An accounts contact may need a customer document. These are different journeys, and a good rollout demonstrates the intended journey instead of assuming that sending a login invitation creates value by itself.

Distinguish customer access from staff access

A customer should use the customer portal for the information and actions intended for that relationship. Staff use the operational system to organise customers, assignments, quotations and work. These account types serve different purposes. Do not issue an ordinary staff login merely because someone needs to inspect their own service history or receive a customer document.

WorkOrderPro maintains portal users associated with a customer and tenant. The invitation process creates the customer access and sends a password-setup link to the intended email address. Before inviting somebody, check that the contact is attached to the correct customer record. A familiar personal name is not enough when the person manages several businesses or properties.

Write down who is authorised to request access and who in your team approves it. A clear access owner is useful when an employee leaves a customer organisation or responsibility for a property changes. The operational goal is to keep access aligned with the current business relationship, rather than accumulating old accounts that nobody reviews.

Choose a first customer journey

A focused initial rollout is easier to evaluate than inviting every customer at once. Select a customer whose service pattern you understand and agree the task they should complete. For example, ask them to locate a recently completed job, identify the work reference and find the relevant follow-up information. Observe whether the page answers their actual question.

Prepare the underlying record before the exercise. The customer name, site, appointment and resolution note should be clear. If the work record contains abbreviations only the technician understands, the portal will expose that confusion to the customer. Improving the source information often matters more than adding another navigation link.

Define success in observable terms. The customer found the correct job, understood the recorded state and knew how to proceed. Avoid declaring success merely because the invitation email was sent. Invitation delivery, successful sign-in and completion of a useful customer task are separate stages, each with its own possible friction.

Make the invitation understandable

An invitation should be expected and recognisable. Tell the customer what the portal is for, which service business is inviting them and what they will be able to do after setting up access. Use the intended email address and confirm it belongs to the right person. Sending a correct invitation to an outdated address still leaves the customer unable to use the service.

The existing setup uses an email invitation with a password-setup link. Demonstrate that complete path during configuration: send to a controlled recipient, inspect arrival, open the link and complete sign-in. A saved portal account does not establish that the email reached the inbox. Delivery configuration and recipient behaviour need their own verification.

Give the customer a clear support route if the link cannot be used or their expected information is missing. The office should inspect the account and customer association before repeatedly sending invitations. Keep access troubleshooting separate from ordinary service questions so the customer does not have to explain a login problem to several people before receiving help.

Use job history as a readable service record

Job history helps customers reconnect with work that has already been requested or performed. WorkOrderPro's history presents job references, recorded statuses and appointment information for the relevant customer relationship. A recognisable reference is useful when a customer phones about a previous visit or an accounts colleague needs to identify what a document relates to.

The quality of the history depends on the quality of each job. Use descriptions that distinguish one visit from another, particularly for repeat work at the same property. A series of entries all described as “service” gives the customer little help in finding the right attendance. Specific but concise descriptions improve both customer navigation and the office's ability to answer follow-up questions.

History should also preserve the distinction between an initial problem and the recorded outcome. A customer may return months later to understand what was addressed. The record should not require them to interpret an internal code or remember a conversation with a technician who is no longer assigned to their work.

Explain status without overstating what it means

A status is a summary of the recorded workflow stage. It can help the customer understand whether work is scheduled, being assessed or completed, but it is not a substitute for the details of their appointment or agreement. Internally, the team must keep status and work notes consistent so the customer does not see a completed label beside an unresolved next step.

WorkOrderPro's job detail view includes the job reference, status, relevant appointment information, assigned technician name and a timeline derived from the record. Explain those items using the language your customer understands. A scheduled appointment is a planned arrangement; it should not be presented as proof that a technician has already arrived or that all work is finished.

Avoid making blanket promises about live location, exact arrival estimates or automatic notifications. Demonstrate any tracking or message feature you intend to use under its actual configuration. A customer who knows what a screen represents can use it confidently. A customer who expects a continuously updated arrival guarantee may be frustrated by information that was only intended to describe the job's current recorded stage.

Prepare a useful service request

A portal service request should help the customer explain what they need and connect that request to the appropriate site. WorkOrderPro includes a request-service path with customer and site context. The office should still review the submission before making operational promises. A request records demand; it does not by itself establish an agreed attendance time or a confirmed diagnosis.

Help the customer provide the reported problem, relevant location and useful contact information. Ask for observations they can safely make rather than technical conclusions. If images are part of the chosen request process, explain what would help the reviewer understand the issue. Avoid requesting unnecessary personal or sensitive information in a general problem description.

Decide who reviews incoming requests and how the customer learns the next step. Self-service can reduce repeated data entry, but an unattended request queue simply moves the waiting from the telephone to a screen. The callout management guide explains how the office turns a request into a prepared visit and a clear assessment workflow.

Set expectations for appointment changes

Online rescheduling is most useful when the customer understands when it is available. WorkOrderPro's current rescheduling eligibility covers scheduled or dispatched jobs with an appointment more than twenty-four hours away. Jobs outside the eligible state or time window are directed to contact the office. This preserves a route for discussing changes when the self-service action is unavailable.

Available appointment choices also need to fit the actual scheduling process. Demonstrate the customer's selection and the resulting office record during your trial. Check what happens to the assigned person and the appointment details after the change. The important outcome is a coherent new arrangement understood by both the customer and the dispatcher.

Keep urgent changes on a clear human contact path. A customer facing an unexpected access problem should know how to reach the office without repeatedly searching for a disabled reschedule action. The portal should explain the available next step, while your team remains responsible for resolving cases that require judgement or changes to the day's existing work.

Give customer documents the right context

An invoice is easier to understand when the customer can identify the job, the work performed and the basis of the charge. The portal includes invoice information and document routes within the relevant customer workflow. Access should be configured and checked for the intended recipient before rollout, particularly where the site contact and accounts contact have different responsibilities.

Do not assume that portal access means every customer user should receive the same commercial information. Review the available permissions with your business's access owner and demonstrate the resulting experience for each intended role. A customer who only coordinates access may have a different need from the person reviewing invoices.

Treat payments as a configured commercial workflow

Some customers expect to pay from a service portal, while others use a purchase order or established accounts process. Determine the journey your business intends to offer and verify the applicable product and payment configuration. A portal screen containing a financial amount is not evidence that a payment provider is connected or that every payment method is available.

During evaluation, follow the chosen process from the customer view to the office's recorded outcome. Understand what confirms a payment, what remains pending and who handles questions. Keep the customer document, payment event and account balance distinct so an employee can explain an apparent difference without guessing.

Avoid promising instant settlement, automatic reconciliation or universal payment support unless those specific behaviours have been demonstrated in the intended setup. The useful buying question is whether your actual customer payment process is understandable and manageable. For a business operating on account, reliable document access and a clear accounts contact may be the more important initial portal task.

Decide what belongs in customer-facing notes

Write resolution notes for a reader who was not standing beside the technician. Explain the work performed and any meaningful next step using clear terms. Internal shorthand can create unnecessary follow-up questions. Equally, copying every internal observation into a customer-facing field can expose information that was never intended as part of the service explanation.

Teach staff which fields and views are used by customers. During the trial, enter sample content and inspect the portal as the intended customer user. This is more reliable than assuming that a field is private because it appears inside the staff system. Use deliberately neutral sample data while learning the presentation boundaries.

Photographs require the same care. WorkOrderPro's photo workflow has a customer-visibility setting, with uploads defaulting to not customer visible. That does not mean every photo is automatically presented in every portal screen. Demonstrate the particular sharing path you intend to use, and review images for relevance before making them available. A useful service image explains the job without unnecessarily showing unrelated people, documents or belongings.

Support customers with several sites

A customer managing multiple properties needs to distinguish the billing relationship from the physical place where work occurs. Use the correct site for each work order and keep site names meaningful. “Main building” may make sense to one person but become ambiguous when the customer operates several premises with similar layouts.

Before rollout, inspect the customer association of representative jobs and sites. Ask the customer contact to find work for two different locations and explain which is which. This exposes naming problems early. If the contact's responsibilities change, review access through the authorised account process instead of assuming that historic access remains appropriate.

Where equipment or maintenance records form part of the enabled workflow, use consistent identifiers and site context. A customer looking for a recurring visit should not have to guess which similarly named asset the record describes. The portal can make a well-organised service history easier to reach, but it cannot repair ambiguous source records on its own.

Run an access and customer-task acceptance check

Test with the intended customer account, not only an administrator looking at staff screens. Confirm that the correct customer information appears and that the person can complete the agreed task. Review the experience on a phone as well as the office's usual device, because customers may open an invitation or appointment detail while away from their desks.

Include an exception, such as an expired setup link or a job that cannot be rescheduled online. The customer should receive a useful next step rather than being left to infer what failed. Record issues as specific tasks so the office can distinguish configuration problems from missing content or training.

Measure adoption through completed tasks

Portal adoption is more informative when measured by useful customer activity than by the number of invitations alone. Choose a small set of tasks that matter to your business, such as finding a job, submitting a well-described request or retrieving the intended document. Use observed customer feedback and your available reporting to understand whether those tasks are becoming easier.

Do not claim that the portal will remove a particular percentage of calls without evidence from your own operation. Some calls involve judgement, reassurance or urgent changes that a self-service view cannot resolve. A more defensible goal is to reduce avoidable information searches while making the remaining conversations better informed.

Review the first rollout with both customers and staff. Which questions were answered? Where did the customer still need help? Did the office receive better information or simply another queue to watch? Use those findings to improve the records, instructions and ownership before inviting a wider group of customers.

Choose the plan around the complete service relationship

Review current pricing and confirm customer-portal availability in the selected plan. Count active administrators, dispatchers and field users for staff billing; disabled team accounts are excluded. Customer portal access is a different account workflow from an ordinary team login, so demonstrate the intended customer setup rather than creating staff users as a workaround.

Start a WorkOrderPro trial with one customer relationship and a few representative jobs. Prepare the source records, send the invitation, complete a customer task and inspect the office handover. That sequence gives you a concrete basis for deciding whether the portal supports your service model. Expand access after the first customer journey is understandable, repeatable and owned by the people who will operate it.