All articles

How-to

How to Write Down a Customer Request Without Losing the Details

A customer calls while you are serving someone else. You remember that they need help, but later cannot tell whether they asked for a repair or a replacement. A short, accurate request note gives you a reliable starting point for the next conversation.

This guide is for small-business owners and their teams. The examples are fictional. A recorded request is not a confirmed booking, accepted order or agreed price.

Before you start

Choose one place your team is authorised to use, such as a shared notebook, spreadsheet or customer system. Decide who can read it, who can correct it and how long you need to keep each note. Use made-up details while practising. Collect only what you need; do not put payment details or sensitive information into a general-purpose note.

The UK Information Commissioner's Office recommends that small organisations collect only the personal information they need and distinguish required from optional information. Its small-business self-assessment provides a starting point; local rules may differ.

Capture the request in six parts

  • Received: Record the date and channel, such as a call or a message.
  • Contact: Record the name and a suitable reply method only when needed for follow-up.
  • Request: Summarise what the customer actually asked for. Keep their wording for any detail that might change the meaning.
  • Known and unknown: Separate confirmed facts from assumptions and list questions you still need answered.
  • Next step: Name the person responsible and the date they intend to follow up.
  • Status: Mark the note New, Waiting for details, Ready for review or Closed. Explain what Closed means for your team.

If the customer asks for Tuesday, write “Tuesday requested” until you have checked availability and confirmed a time. If a detail is unclear, write “not confirmed” instead of filling the gap from memory.

Use this simple note template

  • Received: Date and channel
  • Request: Customer's request in one or two sentences
  • Confirmed: Relevant facts the customer or team has checked
  • To clarify: Missing details and who will ask
  • Next action: Owner, action and planned date
  • Status: New, Waiting for details, Ready for review or Closed

For a real note, add the minimum contact information needed to reply in your approved system. Do not paste the example into an external AI tool with real customer details unless your organisation has approved that use.

Try three fictional requests

Bicycle repair: A caller says a bicycle's back wheel makes a sound and asks whether someone can look at it on Tuesday. Write “inspection requested; Tuesday preferred.” The wheel's condition and an appointment time remain unknown. Assign a colleague to check availability and call back.

Cleaning service: A customer asks for a one-time clean before a move. Record the requested service and preferred date. The property size and final scope need confirmation; the next action is to ask those questions before preparing a quote.

Local bakery: A customer asks about a cake for a celebration. Record the requested date and approximate number of portions. Mark flavour, price and collection time as unconfirmed until the bakery checks and replies. An enquiry is not an order.

Review before sharing

Read the note back to the customer when practical: “Have I understood that you would like an inspection and prefer Tuesday?” Correct errors, then hand it to the person responsible. If the customer adds a detail later, record the update and date so the team can see what changed. Keep access limited to the people who need the note.

To plan follow-up across several requests, see the customer enquiry tracker guide. Before offering a price, use the questions before a quote checklist.

Turn the note into an app brief

I run a small service business. I need a private list of customer request notes with a received date, channel, request summary, confirmed details, questions to clarify, next action, owner and status. Show requests waiting for details. Do not treat a request as a confirmed booking, final price or completed action.

Create a free KernelApps account to explore building an app around this brief. KernelApps is in beta; manual editing and an included AI allowance are available, subject to your account's current limits. Creating an account does not contact a customer or confirm a booking.

Ready to Try Your First Business App?

KernelApps is open in beta. Create a free account to build apps for ChatGPT and Claude. No card to sign up. Build with your included AI allowance. Manual editing is included.

Create free account