Customer Management

What Belongs in a Customer Record for a Service Business?

Use four simple record cards to separate the customer, contacts, service location, and visit history, with a fictional example and a practical update check.

One customer name can hide several different questions

A repeat customer calls about another property. The office finds the familiar name, copies the last appointment, and sends the new visit to the old address. The history was available; the problem was that the record did not make the customer, location, and current request easy to distinguish.

A useful customer record answers four separate questions: Who is the customer? Who should we contact for this task? Where will the work happen? What happened on this particular visit? Keeping those answers distinct makes it easier to check what can be reused and what must be confirmed again.

The four cards below are a suggested information layout. They are not a description of Worganizer fields or a requirement to change software. Use them to review the records your team already maintains.

Separate the customer, people, place, and visit

Microsoft's Field Service documentation distinguishes the account receiving service from the account receiving invoices. Its work order form also separates contacts, location, and the work details. Those examples support a useful distinction: a customer's identity does not establish the service address or the right person for every conversation.

Give each card a reference that colleagues can recognize. A reference can be an existing record number or a clear label in your current system. The important check is whether the visit points to the correct customer, people, and place.

  • Customer: the person or organization your team is serving, plus the relevant billing recipient when separately confirmed.
  • Contact: a person and the role they have for this request, such as arranging access or receiving booking updates. Confirm roles rather than inferring them from a job title.
  • Location: the service address and enough building, unit, or room detail to identify the worksite.
  • Visit: the dated request, agreed purpose, appointment details, outcome, and unresolved actions for that occasion.

References: Microsoft Learn: service and billing accounts · Microsoft Learn: separate contacts, location, and work details

Copy this four-card worksheet

Fill this out for one repeat customer before applying it to a larger set of records. Use only details needed for the service process. Mark unknown information explicitly, with a person responsible for confirming it.

  • Customer card — Reference: _____. Customer name: _____. Related locations: _____. Billing recipient or record reference, if relevant and confirmed: _____. Last checked by whom and when: _____.
  • Contact card — Name/reference: _____. Role for this customer or location: _____. Contact method needed for that role: _____. Source and date of confirmation: _____. Question still open and owner: _____.
  • Location card — Reference: _____. Linked customer: _____. Service address: _____. Building/unit/room: _____. Relevant equipment identifier, if needed: _____. Access contact reference: _____. Details needing reconfirmation for the next visit: _____.
  • Visit card — Reference and date: _____. Customer and location references: _____. Purpose and current agreed arrangement: _____. Contacts for this visit: _____. Relevant earlier visit/document references: _____. Outcome, open action, owner, and next update: _____.

Fictional example: one customer, two locations

This example is fictional. Cedar Studio has a main office and a separate workshop. Sam arranges bookings for both. Lee provides access at the workshop. A previous visit record concerns the main office, while the new request concerns Item B in the workshop's rear room.

A single note reading 'Cedar, call Sam, same as before' hides which address and contact apply. In the four-card layout, the customer card identifies Cedar Studio. Two location cards distinguish Main Office from Workshop. Sam's contact card identifies the booking role, while Lee's identifies workshop access. The new visit references Workshop and Item B; it links the earlier visit only if its information is relevant.

Before confirming the appointment, coordinator Morgan checks the workshop address and current access arrangement. If Sam says Lee no longer handles access, Morgan records that change and leaves the new access contact unconfirmed until it is supplied. Morgan also checks any open workshop appointments that might still rely on Lee's details.

The older visit remains a record of what was arranged at the time. The next visit uses the newly confirmed arrangement. The team can follow the history without treating every old contact detail as current.

Check reusable details when something changes

A service address is more than a customer name. Microsoft's functional-location documentation describes identifying a worksite down to a building or room. Apply that level of detail when it is needed to distinguish the actual destination; do not add extra location information without a purpose.

When a contact, address, or arrangement changes, record who supplied the update and when. Check open visits that depend on it. Do not assume that changing a reusable record has also changed every existing appointment. Microsoft explicitly notes that changing an account's summary information does not update existing work orders in its product; behavior in your own tools must be checked separately.

If the existing record and the caller disagree, keep the discrepancy visible and assign its confirmation. Avoid overwriting a known address with a new one until you understand whether the customer moved, added another location, or is describing a different visit.

References: Microsoft Learn: buildings, rooms, and functional locations · Microsoft Learn: account updates and existing work orders

Keep useful context without collecting a life story

The FTC advises businesses to collect only personal information they need. For this worksheet, ask what decision each detail supports. A contact method for arranging a visit has a clear purpose; unrelated personal information does not belong in the service narrative.

Use fictional information when testing the layout. The cards are an organizational aid, not a complete privacy, retention, or access-control policy. Follow the business's approved process for handling customer information rather than using this checklist to decide who may access records or when records should be deleted.

References: FTC: collect needed information and use fictional training data

Test whether a colleague can find the right answer

Ask a colleague to read one completed set of cards and identify the destination, booking contact, access contact, and next action without reopening the original conversation. Adjust anything that leaves them guessing. Use the intake guide to collect a new request and the job-notes template to record the visit itself.

  • The customer reference leads to the right service location.
  • Each person has an explicit, confirmed role for this request.
  • Current arrangements are distinguishable from historical visit details.
  • A changed detail has been checked against affected open visits.
  • Every unresolved question has a named owner and next action.

References: For the next request: service call intake questions · For the visit record: service job notes template

Less juggling.
More getting things done.

Bring your team, your customers, and your work together.

Start your free trial