AI and MCP

Prompt to draft an email to your bank about a wrong charge

A fill-in prompt that drafts a polite, factual email to your bank about a debit you question, with a checklist of details to confirm before you send it.

Editorial illustration for Prompt to draft an email to your bank about a wrong charge

To draft an email to your bank about a wrong charge, give an AI assistant the date, amount, narration, what you expected and what evidence you hold, and ask for a short factual email that states those and asks the bank to look into it. Check every detail against your statement before you send. The email should report what happened and ask a question; it should not argue a legal case.

What should you gather before you write anything?

A bank can act on a precise description far faster than on a general complaint. Collect the facts first, so the prompt has something solid to work with.

  • The date and exact amount of the debit, as printed on your statement.
  • The narration text, copied exactly, including any reference number in it.
  • The last four digits of the account or card only, never the full number.
  • What you expected: no charge at all, a single charge, a refund after a cancelled order.
  • Proof: order confirmation, cancellation email, a screenshot of the merchant page, a credit that never arrived.
  • Anything you have already tried, with dates, such as writing to the merchant.

What is the prompt to use?

Fill in the brackets and paste the whole thing. The last two lines keep the assistant from adding claims you did not make.

'Draft a short, polite email to my bank's customer care. On [date] my account ending [last four digits] was debited ₹[amount] with the narration [exact narration]. I expected [what you expected] because [one-line reason]. I have [list of evidence]. I contacted [merchant or nobody] on [date] and [outcome]. Ask the bank to investigate and tell me the next steps and a reference number. Use plain, courteous language, under 150 words. Do not quote any law, rule or deadline, do not threaten action, and do not include any detail I did not give you.'

What does a draft look like?

Here is an invented example of what comes back, for a charge of ₹1,499 taken after a cancelled subscription.

Which details must you confirm before sending?

CheckWhy it matters
Date and amount match the statementA wrong digit makes the bank search for the wrong item
Narration copied exactlyIt is how their system finds the transaction
Only the last four digits of the accountFull numbers do not belong in an email
Evidence listed is actually attachedA promised attachment that is missing causes a delay
Nothing claims more than you knowSay 'I did not recognise' rather than 'this is fraud'

Should you use email at all?

Banks usually offer several routes: a customer-care email, a helpline, a form in the app and a branch. Look on your own statement, card or banking app for the official ones. Use whichever lets you attach evidence and get a reference number, and write down the number. If you are unsure whether an email address is genuine, type it in from the bank's own printed material, not from a message or search advert.

What if you get no reply?

Note the date you sent it and the reference number, and follow up through the same route after a reasonable wait. Rules and timelines for complaints change, so confirm the current position on your bank's website or with its helpline. For anything involving a large sum or suspected fraud, speak to the bank by phone straight away rather than waiting on an email.

If you track your spending in SpendixAI, the receipt can sit with the transaction in the app, which makes the evidence easy to find when a query comes up months later.

SPENDIXAI JOURNAL

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

Explore your reports