WhatsApp bot for banks: balance alerts and customer help

A WhatsApp bot for banks sends balance alerts, answers common questions, and passes complex cases to staff. Here is how it works in practice.

Direct answer

A WhatsApp bot for banks is a chat service inside WhatsApp that lets a customer check a balance, get a transaction alert, and ask a common question without calling the bank or visiting a branch. The customer sends a message, the bot checks the request, and it replies in seconds with the right information or the next step. When the request needs a person, the bot passes the full chat history to staff so the customer does not have to start again.

Routine questions get answered at once, staff time goes to cases that need judgment, and customers get a reply on an app they already open every day.

What does a WhatsApp bot do for a bank?

A bank bot handles the requests that repeat every day. It can show an account balance after the customer confirms their identity, list recent transactions, explain a charge, help reset a password, and point to the nearest branch or ATM. Answers come from live account data.

The bot also works outside office hours. A customer who checks a balance at 10 pm gets the same answer as a customer who checks at 10 am, which helps people who bank in the evening and customers whose card is declined and who want to know what happened right away. The bot cannot fix every problem at night, and it should say so plainly when a case needs a staff member in the morning. A WhatsApp bot for business support and orders shows the same idea in another setting, and the guide at https://bdbots.org/blog/whatsapp-bot-for-business-support-orders covers it in detail.

How do balance and transaction alerts work?

Balance alerts start with a trigger. A salary comes in, a bill goes out, a card payment clears, or the balance drops below a limit the customer set. The bank system sends that event to the bot, and the bot sends a short WhatsApp message with the amount, the date, and the new balance. A good alert answers three questions in the first two lines: what happened, how much was involved, and what is the balance now. The bot should use the same wording each time so customers learn to read the alerts fast.

Security shapes every part of this. An alert should never include a full account number, a card number, a PIN, or a password. The bot should never ask for a PIN or a password in chat, and it should warn customers that the bank will never ask for those details on WhatsApp. If a customer reports a transaction they do not recognise, the bot should offer to freeze the card or pass the case to the fraud team at once, and confirm the time the report was made. Banks should also let each customer choose which alerts they want. Many customers in Bangladesh already expect a confirmation message after money moves, and the guide at https://bdbots.org/blog/whatsapp-bot-bangladesh-bkash-orders-support looks at how bKash, orders, and support fit together on WhatsApp.

What questions can the bot answer on its own?

The bot can answer questions where the answer is a fact from the bank's systems or a fixed policy. A customer asks for the balance, the bot shows it. A customer asks when a cheque will clear, the bot gives the standard timing. A customer asks for branch hours, the bot lists them. A customer asks how to block a lost card, the bot starts that process and confirms it.

The bot should also answer questions about fees in general terms, such as where to find the fee list, without inventing a number. If the fee depends on the account type, the bot should say that and show the customer where to check the exact figure for their account. No invented fees or interest rates belong in a bank bot. There is one clear limit every bank bot must keep. The bot must never suggest investments or loans. It must never recommend a fund, a deposit plan, a loan amount, or a repayment term. It can explain what a product is in plain terms, point to the official product page, and offer to connect the customer to a licensed adviser or a staff member. Financial advice needs a full view of the customer's income, debts, and goals, and a chat bot does not have that view.

When should the bot hand over to staff?

Handover is the part of a bank bot that decides whether customers trust it. A bot that tries to handle a fraud report, a disputed payment, or an angry customer on its own will make the case worse. Those cases need a person. The bot should hand those cases over fast, with the full chat history attached, so the staff member does not ask the customer to repeat everything.

A good handover tells the customer why a person is needed, gives a time for the reply, and confirms what happens next. A message that says a staff member will reply within one working day, and that the customer will get a message on WhatsApp when the reply is ready, gives the customer something to hold on to. The bot should tag each handover with the topic and urgency, so staff answer urgent cases first. The customer should always have a way to ask for a person, through a menu option or words such as agent or staff, at any point in the chat.

How do you measure response time?

Response time is the number a bank should track first, because it is the number customers feel. First response time is the time from the customer's message to the first reply from the bot or from staff. A bot answers in seconds, so first response time for routine questions should stay under a minute at almost any hour. Staff replies take longer, so the bank should set a separate target for those.

Resolution time is the time from the first message to the point where the customer's issue is closed. A balance check resolves in seconds. A disputed payment may take days, because it needs checks with other banks or card networks, so the bank should track those two types apart, or the long cases will hide the fast ones in the average. Handover time is the time from the bot passing a case to staff to the first staff reply, and the bank should watch it every week.

ChannelFirst replyAvailableBest for
WhatsApp botSecondsDay and nightBalance checks, alerts, common questions
Phone callMinutes in a queueOffice hoursUrgent cases, long explanations
Branch visitAfter travel and waitingOffice hoursIdentity checks, signed forms
EmailHours to a dayDay and nightDocuments, detailed records

The table shows why the bot fits routine banking. It answers at once, at any hour, for questions that need a fact. Phone calls and branch visits still have a place for cases that need a voice or a signature.

How long does it take to build a bank bot?

A simple bank bot that handles balance checks, alerts, and common questions can take 3 to 7 days to build when the bank's systems already expose the data the bot needs. A larger bot that connects to several systems, handles statements and requests, and adds staff handover with tagging and reports takes longer, and a full platform with several services can take 2 to 6 weeks.

BDBOTS has built bots and web platforms since 2019, with more than 5 years of work, over 1000 projects, and over 500 clients. The team builds with Python, Pyrogram, and Telethon for Telegram bots, and with React, Node.js, MongoDB, PostgreSQL, and Docker for web platforms. A bank that wants a WhatsApp bot can start with a free consultation and a custom-priced quote within 24 hours, and the typical first reply comes within 24 hours. Hosting runs at 99.9% uptime, with monitoring and auto-restart. Every project built by BDBOTS comes with lifetime free support for the life of the project, which means help when something breaks, when an API changes, or when a payment flow stops working, without a new support contract for basic help. The WhatsApp service page at https://bdbots.org/services/whatsapp lists the service in full, and the team can be reached at contact@bdbots.org or on Telegram at @bdbots_bot. More detail about BDBOTS is on the homepage at https://bdbots.org/.

What can go wrong when AI writes the code?

AI tools can draft bot code fast, and that speed hides a risk that banks cannot ignore. The Veracode 2025 GenAI Code Security Report found that AI-generated code introduced a security flaw in 45% of cases tested. For a bank bot, a security flaw is not a small bug. It can expose account data, leak a balance to the wrong person, or leave a door open for fraud. A bot that handles money needs code that a person has reviewed line by line, with tests for identity checks, for wrong inputs, and for attempts to reach data that belongs to another customer.

FAQ

Can a WhatsApp bot show my bank balance?

Yes, after the bank confirms your identity. The bot checks who you are, then shows the balance from the bank's live system. It should never show a balance without that check, and it should never ask for your PIN or password in chat.

Will the bot send me an alert for every payment?

That depends on the alerts you turn on. You can ask for an alert for every transaction, or only for large payments and low balances. You can change those settings at any time, and the bot should confirm each change.

Can the bot suggest a loan or an investment for me?

No. The bot must never suggest investments or loans. It can explain a product in plain terms and connect you to a staff member who can discuss it with you. That limit keeps financial advice with people who can see your full situation.

A WhatsApp bot for banks works when it stays close to what it does best. It sends short alerts with exact amounts and balances, it answers common questions from live data, and it hands complex cases to staff with the full chat history attached. It never gives financial advice. A bank that tracks first response time, resolution time, and handover time each week will see where the bot helps and where staff cover needs to grow. The next step is a free consultation to map the alerts, questions, and handover flow for one bank.