Shopping

A complaint call log: reference numbers, dates and promises

A customer complaint call log template with one line per contact: date, channel, person, reference number, promise made and next date, plus an example.

Editorial illustration for A complaint call log: reference numbers, dates and promises

A good complaint call log has one line per contact and six columns: date, channel, who you spoke to, the reference number, what they promised, and the date you will check again. Fill it in during the call or straight after. When a complaint drags on for weeks, this single page is what lets you say 'on the 12th, Priya on chat promised a call back by the 15th' instead of 'I have been calling forever'.

What columns does the log need?

  • Date and time of the contact.
  • Channel: phone, chat, email, app, in person or post.
  • Person: the name or agent ID they gave you, or 'did not say'.
  • Reference number: the ticket or complaint number, written exactly as given.
  • What was promised, in their words, with the timeline they named.
  • Next date: the day you will check or escalate if nothing has happened.

Add a seventh column called Proof if you like, where you note which screenshot, email or recording holds the evidence for that line.

What does a filled-in log look like?

Say you booked a washing machine repair, the technician never came, and you have been in touch four times. Here is the log, with made-up names and numbers.

DateChannelPersonReferencePromisedNext date
3 OctPhoneAgent NehaTicket 48213Technician visit within 2 days6 Oct
6 OctChatAgent ID 207Same ticketVisit rescheduled to 8 Oct9 Oct
9 OctEmailSupport teamTicket 48213Manager to call within 24 hours10 Oct
11 OctPhoneSupervisor AnilEscalation 5530Visit on 13 Oct, morning slot13 Oct

How should you word the 'promised' column?

Write what was said, not what you hoped it meant. 'Technician within 2 days' is useful. 'Sorted soon' is not, so ask the agent to give a day or a time frame and note it. If they will not give one, write that too: 'no date given'. Quoting a promise back on the next call is surprisingly effective, as in 'I was told on 6 October that the visit would be on 8 October'.

Do you need a reference number for every call?

Ask for one at the start of every contact. Some companies give a new number per call and a separate one for the underlying complaint, so note both and mark which is which. If no number is offered, ask for the agent's name or ID, and for an email or message that confirms what was said. If you get none of these, a note of the time and the number you called from is still better than nothing.

When should you escalate?

Your 'next date' column decides this. When the date passes and the promise has not been kept, the next line in the log is the escalation: say what was promised, when, and with which reference number. Many companies publish an escalation route on their help page or in their terms. Look for it, copy the exact name or email into your log, and use it. Official consumer channels exist too, but rules and contact details change, so check the current ones from an official source instead of relying on a forwarded message.

Where does the log live next to your money records?

If the complaint is about a payment, tie the log to that payment so the whole story is in one place. In a sheet, add a link or a note on the payment row. In SpendixAI you can attach screenshots or emails as receipts to the related transaction, which keeps the evidence beside the amount you are disputing; the call log itself can stay in a note or a separate sheet.

A short routine for every complaint

  1. Open the log before you dial, and write the date and channel.
  2. Ask for a reference number first and the agent's name second.
  3. Ask for a date for the next step and write it down as said.
  4. Read your note back to the agent to check you heard it right.
  5. Set the next date as a reminder and keep the screenshot.
SPENDIXAI JOURNAL

Useful ideas start with a clearer picture of your own spending.

Explore your reports