Client job page overview

Use this guide to understand what your clients see on the Client Job Page so your team can explain each step clearly and troubleshoot portal questions quickly.

Written By Ryan Wagner

Last updated About 1 month ago

Where to find it

  • Open a workorder and use the portal actions (for example Open Client Portal or Open Portal as {role}) to view the same experience your client receives.

  • Clients access this page from their secure job link (usually sent by your team through email or SMS).

When to use this article

  • When a client asks, "What should I do next in my portal?"

  • When a section is missing and staff need to explain why (permissions, feature toggles, or job state).

  • When you want to verify what a buyer/client contact can currently do on a specific job.

Client experience overview

Clients see a job-specific portal page with property/appointment context near the top, followed by action sections. The page is designed as a guided checklist. As items are completed, sections can move into a completed state.

Common client-facing sections include:

  1. View Completed Report

    • If not ready: Reports will appear here when ready

    • If ready: report count/status messaging appears

    • If restricted: no-access messaging appears

  2. Sign Agreement

    • Clients see whether agreements are required, already signed, or not needed

  3. Pay for Your Service

    • Clients see invoice/payment status (due, paid, pending)

    • Pay Now may be disabled depending on job/payment state

    • Some experiences show View Invoice PDF

  4. Create Repair List

    • Clients can start or continue repair-list activity when enabled for the job

  5. Start Your Moving Plan (when enabled)

    • Clients may see HomeBinder moving-assistance entry points and availability messages

How to explain status changes to clients

  • Completed items usually display completion chips/labels (for example Completed or Paid).

  • If the client cannot move forward, have them read the exact message shown in that section; most messages are action-specific and explain what is missing.

  • If a section is not visible at all, it is usually controlled by portal permissions/features or the current job state.

Caveats for internal teams

  • Portal access is contact-specific and token-protected; links should not be reused across contacts.

  • Payment behavior can differ by job type/integration (including Spectora-linked flows).

  • Report availability depends on publication/visibility rules, not just report creation.

Need more help?