Should customers see a live crew location?

Only if you can sustain it. A tracking view that is right 70% of the time creates more calls than it prevents.

Can customers reschedule from the portal?

Not in URBLD's current customer portal. Rescheduling runs through the business so capacity and crew constraints are respected.

What about jobs that are on hold?

Show the hold. Hiding it turns a known delay into a surprise, which costs far more goodwill than the delay itself.

Knowledge · Customer Experience

Appointment and Job Visibility

Customers mostly want three answers: what is happening, when, and what is next. Learn what job and appointment detail to expose in a portal, and what to withhold.

What job information should a customer be able to see?

Enough to answer three questions without calling: what work is on their account, what state it is in, and what the next dated event is. That means job title, current status, the scheduled date and the expected completion date — not internal stages, crew notes or cost detail.

Key takeaways

Three answers cover most status calls: what, what state, and when next.
Customer-facing status is a translation of internal status, not a copy.
Dates should be the ones you are willing to be held to.
Internal production detail stays internal.
Visibility only helps if someone keeps the underlying record current.

The three questions customers actually ask

'Is my job still on?' — the job exists and has a state.
'When are you coming?' — a scheduled date they can read themselves.
'When will it be done?' — an expected completion date, honestly set.

Translate status, do not export it

Internal status values exist for dispatchers: they encode readiness, sequencing and blockers. Exposed raw, they generate questions instead of answering them. A customer reading 'pending materials reconciliation' learns nothing except that something is wrong.

Maintain a short customer-facing vocabulary — scheduled, in progress, completed, on hold — and map internal states onto it. Fewer words, each of which means something a homeowner can act on.

Dates are promises

The moment a date appears on a customer-visible page it becomes a commitment. That is a feature: it forces the date on the record to be a real one rather than an optimistic placeholder held in someone's head.

If the date moves, move it in the record and say so. A portal that quietly changes a date is worse than a phone call that explains why.

What to hold back

Crew assignments and internal scheduling logic.
Job costing, margin and supplier detail.
Internal notes, punch-list arguments and unresolved blockers.
Stage-level production detail the customer cannot act on.

Where URBLD fits

The URBLD customer portal lists that customer's jobs with the job title, a customer-facing status label, the scheduled date and the expected completion date. Archived jobs are excluded. Internal production detail stays on the job record inside the platform.

Client Portal Scheduling

Principles reinforced

This page rests on the following foundational ideas.

Businesses Run on Processes, Not Memory

FAQ

Frequently Asked Questions

Straight answers about how URBLD runs the business end-to-end.

Related knowledge

What Is a Client Portal?

Customer Messages and Updates

The Job Lifecycle