A customer calls a small glazing business to change the access time for an installation. Later, they send a message asking for a different glass finish. The office updates one note, the installer sees an older job sheet and the invoice is prepared from a third version of the agreement.

Nobody has deliberately ignored the customer. The problem is that the latest commitment is difficult to identify.

This situation is common in trade and field-service businesses. Customer instructions may arrive through phone calls, SMS, email, website forms or conversations with a technician on site. When those changes are not recorded consistently, the business can lose track of what was promised, who approved it and whether the operational team has seen it.

The consequences can include:

  • A technician arriving without the right information or materials
  • Work being repeated because an earlier instruction was missed
  • Disagreements about variations or additional charges
  • Delays while staff search through messages and call histories
  • Customer frustration when different employees provide different answers
  • Invoices that do not reflect the final scope of work

The issue is not simply “poor communication”. It is a process problem: customer commitments are being captured in places that are difficult to connect, verify and share.

The danger of treating every message as an instruction

Not every customer message should automatically change a job.

A customer may ask a question, suggest an option or provide information that still needs checking. A site technician may report that the requested work is not practical. An office employee may need approval before confirming a price or schedule.

If every message is treated as a final instruction, the business can create a different kind of risk. Staff may act on an incomplete request, make an unauthorised commitment or change a job without understanding the impact on materials, capacity or price.

A better process separates:

  1. The customer’s request
  2. The business’s review or decision
  3. The confirmed change
  4. The people and systems that need to know

That distinction can be supported with a relatively modest digital workflow.

A practical change-confirmation workflow

The first step is to identify the types of changes that regularly affect the business. For a trade operator, these might include:

  • Access instructions
  • Site contact details
  • Product or material selections
  • Scope changes
  • Schedule requests
  • Customer-provided measurements or documents
  • Requests that may affect price or completion time

Each request can be linked to the relevant customer and job record. The record should capture the original message, the person who received it, when it was received and its current status.

Useful statuses might include:

  • New request
  • Needs review
  • Waiting for customer information
  • Approved internally
  • Awaiting customer confirmation
  • Confirmed for the job
  • Declined or superseded

This does not need to become a complicated project-management system. The purpose is to make the current position clear and prevent an informal request from quietly becoming an operational commitment.

Confirm the important changes in writing

Once a change has been reviewed, the business can send the customer a concise confirmation. This might state:

  • What has changed
  • What remains unchanged
  • Any price or timing effect
  • What the customer needs to approve
  • When the change will apply

The confirmation can be generated from the job record and sent by email or another agreed channel. The customer’s response can then be attached to the same record rather than left in a separate mailbox.

For changes that do not affect price or scope, the process can be lighter. For changes that affect materials, labour, access or timing, the workflow can require an explicit approval before the job moves forward.

This is an example of exception-based control. Most routine work can continue quickly, while unusual or risky changes receive more attention.

Make the latest approved version visible

A workflow is only useful if the field team can trust what they see.

The job record should distinguish between:

  • Historical messages
  • Proposed changes
  • The latest approved instructions
  • Outstanding questions or conditions

A technician should not have to read a long message thread to work out whether a customer’s request was accepted. A clear “current job instructions” view can show the information needed on site, while preserving the history for reference.

If the business already uses job-management, accounting or scheduling software, the right response may be configuration and integration rather than a new application. Confirmed changes could update selected fields in the existing job record, trigger a revised work order or notify the assigned technician.

Care is needed here. Automatically copying every message into every system can create clutter and increase the chance of conflicting information. Only approved, relevant data should move into operational fields.

Add safeguards for common failure points

A practical implementation should also handle exceptions.

For example:

  • If a customer requests a scope change, notify the person responsible for pricing.
  • If access instructions change close to the appointment, alert the assigned technician.
  • If a required approval has not arrived, flag the job before dispatch.
  • If two staff members record conflicting instructions, ask for review rather than choosing silently.
  • If a change is made after a work order is issued, create a visible revision rather than overwriting history.

These safeguards are more valuable than simply adding another inbox or form. They help the business act on the information at the right time.

Start with the commitments that cause the most rework

A trade business does not need to redesign every customer interaction at once. Start by reviewing recent disputes, revisits and delayed jobs.

Look for patterns:

  • Which changes are most often missed?
  • Where do customer instructions usually arrive?
  • Who decides whether a request is approved?
  • Which updates must reach the field team immediately?
  • Which changes affect price or materials?
  • What information should be retained for invoicing or future support?

The answer may be a better job form, a configured SaaS workflow, an integration between existing tools or a small purpose-built component. In some cases, a documented process and clearer responsibility will solve much of the problem before any development begins.

The central lesson is simple: customer commitments need a controlled path from request to confirmation to action. When the latest approved instruction is visible to the people doing the work, a business can reduce avoidable rework while giving customers clearer answers.

If your business is losing time to unclear customer changes, inconsistent job instructions or scattered approvals, visit Melbourne Digital Solutions. Nate and Ben are available there to answer questions and help you think through practical options.