Back to all articlesService enquiries

Resolve conflicting requirements before confirming the visit

Alactic Editorial10 min read

Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.

The request says to use the front entrance. A later message says the front entrance is closed. One person wants a fault assessed; another expects the equipment replaced during the same visit. Confirming an appointment now would turn unresolved requirements into commitments that neither the customer nor the service team has agreed.

When you find conflicting information in a service request, record both statements, identify what each would change about the appointment, and ask an appropriate customer contact to resolve the specific difference. Confirm the visit only when booking-critical requirements are agreed. If something remains uncertain but does not prevent the visit, state the assumption and its limits explicitly.

The aim is not to make every detail certain. It is to prevent hidden disagreement about where the team is going, what it will do and whether it can gain access.

1. Separate contradictions from missing detail

A missing detail needs a question. A contradiction needs a question that acknowledges competing answers. Treating both as ordinary blank fields makes it easy to overwrite useful evidence.

For example, an absent loading entrance is incomplete information. Two different loading entrances, each described as the only permitted route, are conflicting requirements. Asking only “Which entrance?” may get another answer without revealing that the earlier instruction has been superseded.

Sort incoming differences into three practical categories:

  • Equivalent descriptions: Two names appear to describe the same location or task. Record the agreed wording after checking any meaningful ambiguity.
  • Compatible additions: One message adds detail without changing the earlier requirement, such as a reception check-in step after a parking instruction.
  • Incompatible requirements: Following one instruction would prevent or materially change compliance with another.

Do not assume the latest message wins. It may come from someone who knows the equipment but not the building arrangements. Equally, an older instruction may no longer apply. Preserve when and where each statement arrived, but use recency as context rather than as a decision rule.

2. Decide which conflicts block the booking

A contradiction matters when resolving it differently would change the appointment you can responsibly offer. Assess the booking consequence before sending a clarification request.

  • Location: Would the answer change the property, unit, floor, asset location or travel plan?
  • Scope: Would it change the task, required skills, equipment, materials or preparation?
  • Access: Would it change whether the team can enter, reach the work area or start during the proposed slot?
  • Timing: Would it change the arrival window or the time available to complete the agreed task?
  • Customer expectation: Would one version lead the customer to expect work that the appointment does not include?

Use three working statuses: hold confirmation, confirm with an explicit condition, and resolved. These are recommended operating labels, not assumed software features.

Hold confirmation when the uncertainty changes the destination, feasibility or core scope. A conditional confirmation can be reasonable when the remaining uncertainty has a bounded consequence and both sides understand it. For instance, a diagnostic visit might proceed without knowing which component has failed, provided nobody has promised a replacement during that visit.

Do not use conditional wording to disguise a blocker. “Subject to access” is not a useful condition if nobody knows whether anyone will be present to open the building.

3. Keep a conflict log that preserves both versions

A useful log does more than list questions. It connects each disagreement to a booking decision and records what finally replaced it. Keep it with the service request so the person confirming the appointment and the person attending can work from the same record.

For each conflict, capture:

  • Requirement: The particular location, scope or access detail in dispute.
  • Competing statements: Each version, its source and when it was received.
  • Booking consequence: What changes if either version is correct.
  • Clarification request: The exact question, the intended customer contact and the internal person following it up.
  • Current status: Whether confirmation is held, conditional or ready.
  • Confirmed outcome: The agreed requirement, who confirmed it and any remaining limits.

Do not delete the losing version. Mark it as superseded so another colleague does not reintroduce it from an older message. Keep observations distinct from assumptions: “Customer has not confirmed the gate arrangement” is an observation; “the gate will probably be open” is an assumption.

4. Fictional worked example: a filled requirements conflict log

The following service request, people, times and outcomes are hypothetical. This is a fictional worked example, not an Alactic customer result.

A service business receives a request to attend a ventilation unit at Cedar Workshop. Maya, the office coordinator, submits the enquiry. Ellis, the site contact, later sends access and equipment notes. The booking coordinator notices three disagreements before confirming a proposed Thursday visit.

Conflict A: Which part of the site?

Competing statements: Maya’s Monday enquiry places the unit in the main building, first-floor store. Ellis’s Tuesday note places it in the rear annex, ground-floor plant room.

Booking consequence: The team could prepare for the wrong work area and unload at the wrong building. Confirmation is held until the destination is clear.

Clarification request: The booking coordinator asks Ellis to confirm which unit needs attention and whether the first-floor store is a separate or outdated location. Maya is included in the clarification so the enquiry record can be corrected consistently.

Confirmed outcome: Ellis confirms that the requested unit is in the rear annex plant room. Maya confirms that the enquiry reused an old location description. The main-building instruction is marked superseded.

Conflict B: Assessment or replacement?

Competing statements: Maya requests fault diagnosis. Ellis asks the visiting team to bring a replacement unit and finish the change during the visit.

Booking consequence: Diagnosis and replacement require different preparation and may need different appointment lengths. The business cannot treat the existing request as agreement to a replacement visit.

Clarification request: The booking coordinator asks Maya to confirm the requested outcome and explains that the currently proposed appointment is for diagnosis only. Ellis is asked whether that scope still makes the visit useful.

Confirmed outcome: Maya and Ellis agree to a diagnostic visit. No replacement unit will be brought. Any subsequent replacement work requires a separate scope and booking discussion. The replacement expectation is recorded as excluded from this appointment, not silently removed.

Conflict C: When can the team enter?

Competing statements: Maya says reception is staffed from 08:00. Ellis says the annex gate stays locked until 09:30 and that reception cannot open it.

Booking consequence: An 08:30 arrival at reception would not provide access to the agreed work area. The early slot cannot be confirmed on the existing instructions.

Clarification request: The booking coordinator asks Ellis whether the annex gate can be opened for an earlier arrival or whether the appointment must start after 09:30.

Confirmed outcome: Ellis confirms that access cannot be arranged earlier. The coordinator offers a 10:00–11:00 arrival window, which Maya accepts. Ellis will meet the team at the annex gate.

Remaining assumption: the fault may not be present

Known uncertainty: The customer reports an intermittent fault, but neither contact can confirm whether it will occur during the visit.

Booking consequence: This does not prevent an agreed diagnostic appointment, but it limits what the team may be able to establish.

Explicit condition: The booking summary states that the visit is diagnostic and that a definitive diagnosis may not be possible if the reported fault cannot be reproduced or otherwise established. The customer accepts this limit. The uncertainty stays visible rather than being labelled resolved.

5. Ask someone who can settle the particular requirement

The appropriate customer contact depends on the question. A site contact may know the access route; the person coordinating the service request may need to confirm whether a narrower scope still meets the customer’s need. One person does not necessarily have every answer.

This is a requirements workflow, not a method for determining legal authority, account permissions or whether two contact records belong to the same person. If those issues arise, handle them through the relevant separate process.

Make clarification messages narrow enough to answer but complete enough to expose the consequence. In the hypothetical example, the access question could read:

We have two access instructions for the proposed visit: reception from 08:00, and the annex gate from 09:30. The work is now confirmed for the annex, so reception access alone would not let the team start. Can someone open the annex gate for the proposed 08:30 arrival, or should we arrange an arrival after 09:30? We have not yet confirmed the appointment.

When several contacts need to contribute, nominate one internal coordinator to assemble the final answer. Avoid separate conversations in which each person receives a different partial summary.

If the response is “yes” to a message containing several alternatives, clarify again. If it introduces a third location or scope, add that version to the log instead of forcing it into the earlier choices.

6. Confirm one coherent visit, not a collection of replies

Once the blockers are resolved, send a consolidated booking summary. The customer should not have to reconstruct the agreement from a chain of corrections.

For the hypothetical example, that summary could be:

The diagnostic visit is confirmed for Thursday, with arrival between 10:00 and 11:00, at the rear annex plant room at Cedar Workshop. Ellis will meet the team at the annex gate. This replaces the earlier main-building location and reception access instructions.

The appointment is for diagnosis only. No replacement unit will be brought or installed during this visit. The reported fault is intermittent, so a definitive diagnosis may not be possible if it cannot be reproduced or otherwise established. Please tell us before the visit if the location, access arrangement or requested scope changes.

Ensure the internal work instructions match this summary. A correct customer message does not repair an outdated job note that still sends the team to reception.

If automation helps prepare a summary, have a person review the competing statements and the proposed resolution before confirmation is sent. A fluent summary can conceal an unsupported choice just as easily as a handwritten note can.

7. Recover when an answer is late or the agreement changes

Waiting indefinitely for perfect information wastes scheduling capacity. Confirming despite a critical gap creates a different problem. Use an internal decision deadline tied to the preparation the visit requires, and tell the customer what remains unconfirmed.

  • No reply: Follow up with the specific unresolved question. If a booking-critical answer is still missing at the decision point, release or reschedule any provisional slot according to your operating process. Do not present silence as acceptance.
  • Customer contacts still disagree: State the practical consequence neutrally and ask them to return one agreed instruction. Do not choose whichever answer is easier to schedule.
  • A late change arrives: Reassess the affected requirement. A different entrance may be manageable; a different property or replacement scope may require a new booking decision.
  • The visit is already confirmed: Contact the customer promptly, identify what has changed and explain whether the appointment can remain confirmed. Update the work instructions and notify whoever is preparing or attending.

The trade-off should remain visible. Holding a visit may delay service, while proceeding may waste travel or create an unmet expectation. Record why a bounded uncertainty was accepted or why a blocker required postponement.

8. Check whether the process prevents avoidable surprises

Start with the next service request that contains incompatible instructions. Create a conflict entry before sending confirmation, assign a follow-up owner and write the booking consequence in plain language.

For an initial review, inspect a small batch of completed requests and ask:

  • Did every booking-critical contradiction have a recorded outcome before confirmation?
  • Did each conditional booking state the remaining uncertainty and its consequence?
  • Did the customer summary and attending team’s instructions agree?
  • Did any visit require a location correction, access delay or scope reset caused by information already present before booking?

Track unresolved blockers at confirmation separately from uncertainties that were explicitly accepted. Combining them would hide the difference between an overlooked problem and a deliberate, bounded decision.

The immediate next action is simple: take one live request, compare the location, scope and access statements across its messages, and log any contradiction before offering a confirmed visit.

Service enquiriesAppointment bookingRequirements managementCustomer communication

Put the next conversation to work.

Explore Alactic Communications for WhatsApp conversations, campaigns and AI-assisted workflows. Choose the product and plan that fit your team.

Explore Communications