Blog

A call log checklist for every conversation with your card issuer

What to write down before, during and after every call, chat and letter with a card issuer, how to get reference numbers and how to store the record.

When a card problem drags on, the issuer's records show what its side recorded, and yours show nothing unless you kept them. A call log fixes that. It is a simple list of every contact, written as it happens: when, who, what was said and what was promised. The log turns "I called a bunch of times and nobody helped" into "I called on these four dates, spoke to these people and was promised these things on these dates," which is the version that gets attention from a supervisor, an executive office or a regulator.

This is a checklist, and you can use it as written. It covers what to prepare before a contact, what to write during it and right after, how to get a reference number, how to handle chats, letters and secure messages, how to store the record and how to use it in an escalation. A worked example shows a filled log. Nothing here requires special software. A notebook, a notes app or a spreadsheet works.

Why a log matters more than memory

Three reasons make the log worth the effort.

  1. Promises get lost. A phone agent says "a supervisor will call you within five days." Five days later no one has called. Without the date and the name, you cannot say who promised it.
  2. Accounts of conversations differ. The issuer's notes may say "customer was informed" where you remember "the agent said it would be reversed." A contemporaneous note from you is far stronger than a recollection weeks later.
  3. Deadlines are dates. Some, such as the 60-day window for a written billing-error notice under the Fair Credit Billing Act and the statutory acknowledgment and resolution periods, are measured from specific events. A log tells you when each event happened.

A log does not guarantee a result. It makes sure that you do not lose a right or a fix because you cannot show what happened.

Before the call

Do these in a few minutes.

  • [ ] Write the problem in one dated sentence. "A $38 late fee on October 14 for a payment I submitted on the due date." Everything else attaches to it.
  • [ ] Write the outcome you want. A specific result: reverse the fee, restore the limit, post the credit.
  • [ ] Have the account identifiers ready. The card number or account number, the last four of your Social Security number if asked, and the statement or transaction in question. Keep the cardholder agreement handy if the question is about terms, and keep full numbers out of your notes (see the section on privacy).
  • [ ] Find the right number. The number on the back of your card, or the issuer's own app or website. Never a number from a message. Which department do I call about my card problem? helps you pick the team.
  • [ ] Open the log and write the date and time. Start the entry before you dial, so the call time is accurate.
  • [ ] Check your phone settings. If you may need to switch lines, write down the number you dialed from.
  • [ ] Know the call recording situation. Most issuers say that calls may be recorded. Rules on recording a call yourself differ by state, and some states require all parties to agree. Unless you are sure, do not record, and rely on notes. If you want to record, say so at the start and ask for agreement.

During the call

Write as you go, even if only shorthand. Capture these fields.

  • [ ] Date and time, and the length of the call.
  • [ ] The number you called, and the menu option you chose.
  • [ ] The agent's first name and agent ID. If they decline to give an ID, write down that they declined, with the time.
  • [ ] The department or team. "General service," "disputes," "fraud," "supervisor."
  • [ ] The reference number or case number. Ask: "Can I have a reference number for this call?" If there is none, ask whether a note was added to the account and write down the answer.
  • [ ] What you asked. One line.
  • [ ] What they said. Facts, in their words where you can: "Said payment posted Oct 13, 12:04 a.m." Not your interpretation.
  • [ ] What they promised, and by when. "Supervisor callback by Oct 22." If they give no date, ask: "By what date should I expect that?" and write the answer.
  • [ ] What they asked of you. Documents to send, forms to complete, deadlines.
  • [ ] The next step, and who owns it. Yours or theirs.
  • [ ] Any transfer. The name of the team, and whether the new agent saw the earlier notes.

Two phrases help during the call. "Let me read back what I wrote, to be sure I have it right" lets you check a promise. "Can you note the account that I called about this?" asks the agent to add the case to the file.

Right after the call

Do this in the next five minutes, while the call is fresh.

  • [ ] Add a two-line summary at the top of the entry: what you asked for, what the outcome was.
  • [ ] Put the follow-up date on a calendar. If a callback is promised for the 22nd, set a reminder for the 23rd.
  • [ ] Note what you must do. If the agent asked you to send a document, write the deadline.
  • [ ] Save any email or text that arrived during or after the call. Take a screenshot if it is only in an app.
  • [ ] Decide the next channel. If a fix needs a written record, plan the letter. For a billing error, plan the written notice, which does not wait for the issuer's form.

Chats, messages and letters

Chats, secure messages and apps

Written channels leave a record automatically, but the record belongs to the issuer unless you save it.

  • [ ] Save the transcript. Many chat tools offer an emailed copy at the end. If not, copy the text and paste it into a document with the date and time, or take dated screenshots.
  • [ ] Note the agent's name if the chat shows one, and the case number if given.
  • [ ] Screenshot secure messages from the issuer's inbox and your own messages, because inboxes can be changed or archived.
  • [ ] Record the status in the app. A dispute status screen showing "in review" with a date is evidence.
  • [ ] Keep the confirmation when you submit a form or an upload.

Letters and mail

  • [ ] Keep a copy of every letter you send, with the date.
  • [ ] Use proof of delivery for anything that matters, such as certified mail with return receipt, and note the tracking number in the log.
  • [ ] Log letters you receive, with the date they arrived, and keep the envelope if the postmark matters.
  • [ ] Number enclosures in the same order as in your letter.

how to write an executive resolution letter to a card issuer covers a letter that escalates, and the billing dispute letter builder on this site helps assemble a billing-error notice.

A filled log

This example is invented. It shows what a few entries look like in a simple table.

Date and time Channel and team Agent and ID Reference What I asked What I was told or promised Next step and date
Oct 15, 4:10 p.m. (12 min) Phone, general service, number on back of card "Alex," ID 3340 5521 Reverse $35 late fee on Oct 14 Payment posted Oct 13; fee stands; supervisor to call within 7 days Wait to Oct 22
Oct 24, 6:30 p.m. (18 min) Phone, supervisor "Chris," ID 9910 5598 Same request, plus review of reporting Fee cannot be reversed; cutoff is 9 p.m.; I said I paid at 8:40 p.m.; asked to review; no answer Send written request by Oct 28
Oct 26 Secure message none MSG-88 Written request with payment confirmation Auto-reply: reply in 5 to 7 business days Check Nov 4
Nov 5 Secure message reply not named MSG-88 n/a Declined; cites posted date Send executive letter by Nov 12

The log is plain, and it carries what an executive office needs: dates, who, reference numbers, the issuer's stated reasons and the gap between the call and the response. The example also shows a fact the caller can check: whether the 8:40 p.m. submission was before the cutoff in the agreement.

Reading your own log

Once you have a few entries, read them as an investigator would. Count the days between each promise and the next event, and look for gaps.

In the filled example above, the supervisor callback was promised within 7 days of October 15, which makes October 22 the due date. The next contact in the log is October 24, which is 9 days after the first call and 2 days after the promised date. The log shows that the issuer missed the date, and it shows that the caller waited until the date passed before calling. Both facts are useful in a letter: "The callback promised for October 22 did not occur; I called on October 24."

Now look at the written request. It was sent October 26 and answered November 5, which is 10 days later. The auto-reply had promised 5 to 7 business days. Whether 10 calendar days fits depends on the weekends in between, and the log lets you check it against a calendar instead of guessing. If you find that the issuer met its own stated windows, the log tells you the delay was not the problem, and the substance is. If the issuer missed its windows repeatedly, the pattern is evidence of poor service.

Three questions to ask your own log:

  1. Where is the first date on which the problem was reported? That is the start of your timeline.
  2. Which promises have no follow-through? List them with their dates.
  3. What is the one fact the issuer can verify that supports my request? Put it at the top of the next letter.

A template you can copy

Paste this into a notes app and fill it in for each contact. The labels are plain so you can keep it in a spreadsheet too.

  • Date and time, and length:
  • Channel (phone, chat, message, letter, in person):
  • Number or address used:
  • Team or department:
  • Agent name and ID:
  • Reference or case number:
  • What I asked:
  • What I was told:
  • What was promised, and by when:
  • What I need to do, and by when:
  • Documents sent or received:
  • Next step, owner and date:

A filled entry takes two or three minutes. Over the life of a dispute that is a small price for a complete record.

How to ask for a reference number

Some agents give one without being asked. Others do not. The phrase that works is simple.

  • "Is there a reference or case number for this call?"
  • If the answer is no: "Is a note being added to the account that describes this call? Can you read me the note?"
  • If the agent cannot give a number: "Please note that I asked for a reference number and was told none exists." Then write down the agent's name and the time.

A missing reference number is not a failure on your part. It is a fact that you record. If the issuer later says there is no record of your call, your log is the record that you called.

Privacy: what not to write in the log

A log has personal details, so protect it.

  • Do not write full card numbers, security codes or online passwords. Use the last four digits.
  • Do not keep the log in a shared document that others can read.
  • If a person on the phone asks for a one-time passcode that the issuer texted, do not read it to them and do not log it. A legitimate agent does not need it for a call you made. A call that asks for one is a reason to hang up and call the number on the back of your card.
  • Do not log calls from strangers claiming to be from the bank as if they were issuer contacts. Note them as suspicious and report the scam through the number on the back of your card, and consider the CFPB complaint process.

Storing it

A log is useful only if you can find it. A few simple rules.

  1. One folder per problem. Put the log, statements, letters, receipts and screenshots together. Name files with the date first, for example "2026-10-15 call 5521."
  2. Keep a copy outside your phone. A cloud folder or a paper binder. If the phone is lost, the record survives.
  3. Keep it until the problem is closed and afterward. A credit report error or a late-fee dispute can return months later. Keep the file for at least as long as the issue could resurface, and ask a tax professional about any item that affects your taxes.
  4. Back up the transcript screenshots, because app histories can disappear after an update.

Using the log in an escalation

When you escalate, the log supplies the timeline. The steps are in escalating a card problem that is not getting fixed, week by week. A good escalation letter lists the dated contacts from the log, in order, with reference numbers and the issuer's own words. A CFPB complaint form has a place for the timeline, and the steps are in How to file a CFPB complaint about a credit card, step by step. If you file a complaint, the issuer's response will be compared against your dates.

Common log mistakes

  • Writing it later. A note written the next day is weaker than one written during the call.
  • Writing opinions. "The agent was rude" tells the reader nothing. "Agent said, 'I can't help you with that' and ended the call at 4:22 p.m." does.
  • Not logging the failures. A call that ends in a hang-up or a long hold is part of the story.
  • Skipping the promise. The date and the promised action are the most useful fields.
  • Not logging the good calls. A call that fixed part of the problem is part of the record too.

Key takeaways

  • Start a log before the first call and write the date, time, team, agent name or ID, reference number, what you asked and what was promised by when.
  • Ask for a reference number every time, and if none exists, record that you asked and what you were told.
  • Save chat transcripts, secure messages and letters with delivery proof; screenshots count when nothing else is available.
  • Keep full card numbers and passcodes out of the log, and never log or read out a one-time passcode to a caller.
  • Store one folder per problem with a backup outside your phone, and use the log to build the timeline for any escalation or CFPB complaint.

Terms used in this article

Related tools

Latest on this topic