Skip to content
Skip to content

Practical trade business guide · By Yes AI

Use repeat-customer job history without assuming the new request

A returning customer may expect the business to remember their last job, but the next request can involve a different property or problem. Useful history should help the conversation without deciding the new job in advance. This guide covers administrative access to earlier work and a clear handover for the current enquiry.

Start with the current request

Ask what the customer needs now and which property or job they mean. In a fictional business, a returning customer called Jordan previously arranged work at a rental property but now calls about their home. Using the old address without checking would send the team to the wrong place. Capture the current request before filling gaps from history. Do not turn a familiar phone number into proof that the caller is asking about the same job or can authorise a new one.

Find history through the approved process

Decide which staff may look up previous work and what checks apply before details are discussed. Use the business’s approved customer and job references where available. Similar names can belong to different people, and one contact may manage several properties. If the match is uncertain, record the new enquiry for staff review rather than joining records automatically. Ask the implementation team to demonstrate how the lookup works in the actual job system, including a search that returns more than one possible match.

Show only relevant previous information

Give the receiving person enough context to locate the earlier work: the job reference, property and administrative status, for example. Avoid copying a customer’s entire history into every message. Distinguish a completed job, an open enquiry and a cancelled booking so old activity is not presented as current work. Staff should be able to open the original record where their access permits. Keep technical assessments and any decisions about further work with the business’s appropriate personnel.

Record changes instead of silently overwriting

If the caller supplies a different address or contact number, show the difference and follow the business’s correction process. A new property may need a separate job rather than a changed customer record. Preserve the relevant earlier details until an authorised person decides the relationship. For fictional customer Jordan, the handover should state that this is a new address, not quietly replace the rental property in the old job. Record who approved any update and what was actually changed.

Avoid promises based on an earlier job

Previous pricing, attendance or availability does not automatically apply to the next request. Tell the caller which details have been recorded and what staff still need to review. Do not describe the work as a warranty visit, an included return or a confirmed booking simply because a previous job exists. Those are business decisions outside the history lookup. If the caller expects a particular arrangement, capture that expectation accurately and pass it to the person authorised to respond.

Test returning callers with different situations

Use fictional records for a repeat enquiry, a new property, similar customer names and an old job that is still open. Confirm that the current request reaches its owner with the correct reference and without exposing another customer’s details. Include an uncertain match and check that staff can resolve it. Review whether the history shortened the handover or merely added irrelevant text. The process is working when the team has useful context while still checking what the customer needs this time.

Before you approve the workflow

  • The current property and request are checked.
  • Uncertain customer matches go to staff.
  • Old jobs remain distinct from new enquiries.
  • Earlier prices and arrangements are not promised automatically.

Continue planning

Plan how job information reaches your team

Describe how enquiries and job updates reach your team. We can discuss intake, staff handovers and the checks needed before changing your process. Use a fictional example and leave customer addresses, access codes and passwords out of this enquiry.