Keeping Customers Informed When the Contractor Arrives

An arrival notification tells the customer that the provider has recorded their arrival. It is a simple update, but it should be tied to a real job action rather than sent merely because the scheduled start time has passed.

Let the owner record the event

In a focused business view, the arrival action should sit near the job details and identify the correct appointment. A progress bar can show status without acting as a series of easy-to-tap state-changing controls.

This matters when a customer has several jobs. Service and date context help the owner avoid updating the wrong visit while working from a phone.

Match the message to the event

Arrived is different from on the way. Do not describe a live location or estimated arrival time unless the system actually provides it. A useful notification can simply tell the customer the contractor has arrived and point them to their appointment information.

The customer portal and owner view should reflect the same recorded state. A message delivery failure should not silently reverse the job action or falsely show that the customer received it.

Test both sides of the update

Use a synthetic booking to mark arrival, inspect the customer's view, and check the relevant notification outcome. Then verify what happens if the action is repeated. The system should not create a confusing stream of duplicate updates.

GoForms connects owner job actions with customer communication. The team can help configure the workflow around the updates your business wants customers to receive.

See GoForms to follow a job from the business portal to the customer's portal.