Back to all articlesService enquiries

Use customer photos and documents without treating them as proof of diagnosis

Alactic Editorial9 min read

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

In a hypothetical booking scenario, a customer sends a close-up of a damaged fitting. One staff member books a repair as though the cause is settled; another asks for more photographs without explaining what is missing. Both responses confuse collecting evidence with making a decision.

The photos to request before a service visit are those that answer a defined booking question: which service category to select, whether access needs planning, which identifier to record, or whether someone needs to review the enquiry. Documents should support similarly specific choices. Neither a photograph nor paperwork should become proof of a technical diagnosis.

This guide covers booking triage and visit preparation, not technical diagnosis or document-retention policy. Its practical starting point is a filled evidence-request table: what to request, what it supports, where its usefulness ends and what to do instead.

1. Define the booking decision before requesting evidence

Before asking for an attachment, complete this sentence: We need this to decide whether to... Name an operational choice, rather than saying staff need to understand the issue better.

Useful choices include routing an enquiry to a service team, reserving an assessment rather than a confirmed repair, arranging an access-planning conversation, or locating a previous service record.

If staff would make the same booking regardless of what the attachment shows, reconsider the request. It may still help the visiting team prepare, but label it optional preparation rather than a booking requirement.

Classify each request:

  • Required for a defined decision: This booking choice cannot be made until the question is resolved, although another route may resolve it.
  • Helpful for preparation: The submission may be useful, but its absence does not automatically block booking.
  • Not useful at this stage: The material does not change the next action and should not be requested routinely.

This distinction prevents optional photographs from quietly becoming entry requirements. It also helps staff explain why a particular uncertainty matters.

2. Reuse this filled evidence-request table

Hypothetical worksheet: These are fictional worked examples, not Alactic customer results. Adapt the decisions to services your business actually offers. Keep the alternative beside the request so staff do not need a separate exception guide.

Filled evidence-request worksheet for hypothetical service bookings
Booking questionSmallest useful submissionSupported decisionLimitationAlternative or stop rule
Equipment category: Which team should receive this enquiry?An overall photograph of the item and a readable identification-label photograph, if the label is already visible and easily accessible.Select a service category or refer for manual classification.The exterior and label do not establish the cause, internal condition or required repair.Accept brand and model as text, consult an existing record, or arrange a coordinator conversation. Stop collecting images once the category is clear.
Access planning: Does the visit need a planning conversation?An optional wide view of the approach to the work area, taken from a normally accessible position.Flag a conversation about entry, space or access arrangements.Images may omit obstacles or distort scale. They do not establish that a location is safe or suitable for work.Ask focused questions about known restrictions and offer a planning call. Refer uncertainty to a reviewer; do not ask customers to rearrange the area.
Previous job: Which earlier booking does this concern?A typed job reference, or a cropped document section showing it if typing is difficult.Locate a candidate service record for normal verification checks.A reference does not establish identity, permission to access the record or entitlement to service.Use the established lookup and verification process. Do not request a full invoice when the reference is sufficient or disclose details solely because it was supplied.
Assessment or review: Can an assessment be booked?A short description of the customer's observations, with an optional image of the visible condition.Select an assessment route or obtain human review before confirming the appointment type.A mark or damaged surface does not establish its source, severity, timing or repair scope.Offer a coordinator call or assessment visit where available. Do not turn a possible explanation into a confirmed repair description.
Preparation detail: Is an equipment specification available?The relevant field transcribed from existing paperwork, with its source noted.Add a preparation note or send the detail for review.The document may be outdated, incomplete or about a different item; it does not establish current condition.Record the detail as unknown and explain what can be checked during the visit. Request further searching only if it changes a named booking decision.

When adapting a row, assign an owner to its alternative. A planning call is not a usable fallback if nobody accepts those calls. Also distinguish a booking prerequisite from information that can reasonably wait until the visit.

3. Write requests customers can complete without investigating

A useful request explains what to send, why it helps and what happens if it is unavailable. Avoid asking customers to investigate the fault on the business's behalf.

Hypothetical customer message:

To help us route your enquiry, please send an overall photo of the item and a readable photo of its label if it is already visible and easy to reach. These help identify the equipment; they will not confirm the cause or repair needed. Please do not move equipment or remove covers for a photo. If images are not possible, tell us the brand and model if you know them, or ask for a coordinator call.

For documents, name the field needed rather than asking for all available paperwork. Explain that unrelated information can be left out. If an attachment is merely helpful, say so explicitly: customers should not delay a response while searching for optional material.

Offer a text description, telephone conversation or staff-assisted booking where available. If that alternative cannot resolve the question, explain the remaining uncertainty and the next option instead of repeating the upload request.

4. Separate observation, interpretation and decision

Internal notes are where a tentative impression can harden into a supposed fact. Keep the customer's report, the visible information and the booking action in separate fields or clearly labelled lines.

Hypothetical booking note:

  • Customer report: Customer says a mark appeared beneath the unit yesterday.
  • Visible information: Image shows a mark on the surface below the unit; its source is not visible.
  • Booking decision: Assessment requested. Cause and repair scope remain unconfirmed.
  • Open question and owner: Coordinator to confirm the appropriate appointment category.

A note stating that the unit is leaking and needs replacement would add conclusions the attachment cannot support. Those conclusions could influence staff preparation and customer expectations before a visit.

Handle documents the same way. Record that a date appears on supplied paperwork, not that the current equipment's installation date has been independently verified.

Record lookup also needs its own permission checks. OWASP's object-level authorization guidance distinguishes knowing a record identifier from being authorised to access it. Applying that principle here is a recommended design practice, not a claim about a particular product's controls.

5. Recover from missing, unclear or conflicting submissions

Before asking for more material, identify the unresolved booking question. Use the smallest correction that could answer it:

  • Unreadable identifier: Ask for text or consult an existing record. Request another image only if that is practical.
  • Close-up without context: Request an overall view only when identifying the item or location will change routing.
  • Conflicting inputs: Keep both as unverified information and refer the discrepancy to a reviewer. Do not choose whichever makes booking easiest.
  • Inaccessible item: Record the limitation and offer a call or assessment route, where available, rather than encouraging access attempts.
  • Failed upload: Preserve the enquiry and provide a non-upload route instead of requiring a restart.

A practical operating rule is to try a targeted clarification, then choose between escalation, proceeding with an explicit limitation, or explaining why the requested appointment cannot yet be confirmed. Further requests need a new purpose, not simply a repeated demand for clearer photos.

Where no assessment or review alternative exists, say so plainly. Explain which decision remains unresolved without presenting the missing attachment as a customer failure.

6. Work through an assessment booking

Fictional worked example: A customer requests an appliance repair and sends a close-up of a mark beneath it. This hypothetical business offers assessment visits for the relevant category but does not confirm repair scope from customer photographs.

  1. Define the choice. The coordinator needs the service category and an appropriate appointment type.
  2. Identify the gap. The close-up does not identify the appliance. The coordinator requests brand and model as text, offering an accessible label photo as an alternative.
  3. Use the fallback. The customer cannot photograph the label but supplies a model from existing paperwork. The coordinator records that source.
  4. Apply the worksheet. The supplied model supports routing to the assessment team. Another picture of the mark would not change the appointment type.
  5. Confirm the commitment. An authorised coordinator confirms an assessment of the reported issue, with cause, repair scope and parts requirements left unconfirmed.

The hypothetical result is a routed assessment booking, not a proven diagnosis or guaranteed repair. If the model conflicted with the customer's description, manual classification would be needed before confirmation.

The trade-off is practical: some uncertainty can remain for the visit, while additional collection can delay booking without improving the choice. Set the evidence threshold according to the consequences of selecting the wrong appointment.

7. Make the handoff authorisation explicit

Use a short handoff checklist for staff or an automated assistant:

  • Decision owner: Name the role authorised to confirm the appointment type or approve an exception.
  • Decision packet: Include the customer request, material already received, source of key details and unresolved booking question.
  • Status: Distinguish attachment received, reviewed for booking and booking action authorised.
  • Human route: Identify who receives unresolved questions and how the customer can reach a person.

Receipt alone must not trigger an unauthorised booking action. Before implementation, verify that the workspace and current plan support the proposed recordkeeping and handoff process.

8. Check whether each request earns its place

Review a booking category over a defined period using observable outcomes:

  • Did the submission change the booking category, access plan or review route?
  • What remained unresolved after clarification?
  • Could customers actually use the offered alternatives?
  • Did a reviewer correct an unsupported conclusion in the notes?
  • Did optional evidence delay a booking because someone treated it as mandatory?

Hypothetical review exercise: Examine the next ten enquiries in one category. Record each request's intended decision, whether the submission changed it and whether an alternative was needed. Remove or rewrite requests with no clear use. Assign an owner to any fallback that failed in practice.

Keep preparation-only requests when they genuinely help the visiting team, but label them accordingly. The review should improve the worksheet, not reward staff for collecting the largest number of attachments.

Service enquiriesBooking workflowsCustomer evidenceService triage

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