Correct the destination without moving the wrong job

Find the record that produced the mistake

Ask which activity used the address: an invoice, a shipment or a site visit. Locate the address revision or snapshot attached to that activity. The current customer profile may already contain a different value.

Compare the entered components, any provider-normalised result and the final output. A missing unit in the label is an integration defect even if the profile still contains it.

Avoid asking the customer to repeat sensitive access instructions in an ordinary support ticket. Use the application's protected field or an approved channel when those details are necessary.

Confirm the scope of the correction

A customer saying “send it to our office” may mean future invoices rather than all service visits. Confirm the address role and which pending activities should change.

For a synthetic example, a business moves its accounts team while its workshop remains in place. Update the postal contact and relevant future correspondence. Do not move the workshop's maintenance appointments.

If an item has already been dispatched, use the carrier's supported correction or redirection process where available. Editing the local profile does not alter a shipment already in transit.

Apply and verify the change

Save the corrected components with an actor and time. Revalidate the reference association if a matched component changes, and retain the prior revision where required for operational history.

Preview the actual label or job destination after correction. Confirm the unit, locality, postcode and any separate access instructions. A successful database update is only part of the recovery.

For multiple affected jobs, present the proposed set before applying a bulk change. Exclude completed work unless the action is explicitly a historical correction with appropriate audit handling.

Close the cause as well as the ticket

Classify the defect so engineering can distinguish provider coverage, restrictive input rules and downstream formatting loss. Include a sanitised example that reproduces the mechanism.

If autocomplete repeatedly chooses the wrong candidate, preserve the manual-entry path while the issue is investigated. Forcing the customer back through the same failing suggestion is not a resolution.