One place to check the job, grab the report, and stop asking where it has got to.
It is part of the service. The point is shared visibility, predictable report delivery, and cleaner handover between office, design, and installation teams.
If you’re a homeowner, the best next step is the homeowner guide (what to expect + privacy + preparation).
Less chasing. Fewer lost files. One place to see the job. The platform is not a separate product you need to adopt before using Vertex; it is the operating layer that keeps survey bookings, delivery status, report files, and team access in one record.
The platform exists because survey work has a lot of moving parts. A job may start with sales, move to an office coordinator, then pass to design, installation, and sometimes customer support. If every team is chasing a different file or update, the survey has not really solved the process problem.
A booking needs enough detail for the survey to be useful: service type, postcode, property size, known constraints, and expected outputs. Keeping those details beside the status and final report reduces the risk of teams working from partial information.
When the report is delivered, the platform gives the team a clear place to retrieve the latest output. That matters when sales, design, and install all need the same evidence but do not all sit in the same inbox.
Installer master, admin, rep, and design-style processes are easier when access is organised around the account rather than a chain of forwarded emails.
Most teams start with the portal because it solves the immediate problem: live status and report delivery. For higher-volume installers, integration support can help connect Vertex job updates back into an existing CRM, job board, or internal tracker.
Webhook routes make sense when your team already tracks jobs somewhere else and wants booking or delivery updates mirrored into that system.
A first live job can run through the normal portal flow. That is the right starting point if you want to judge report quality, turnaround, and status visibility before changing internal processes.
If integration support is needed, we define the fields, events, and expected behaviour first. That keeps the platform useful rather than creating another source of unclear status updates.
The practical route is simple: price one live job, review the report, check the portal handover, and decide whether the standard flow is enough. If your volume grows, team access and webhook support can be configured around the way your installer business already works.