WhatsApp bot for HR: leave requests and payslips in chat

A WhatsApp bot for HR handles leave requests, payslips, and policy questions in chat. Learn how it cuts HR emails and gives staff faster answers.

Direct answer

A WhatsApp bot for HR is a chat assistant that handles routine staff requests inside WhatsApp. An employee sends a message, asks for leave, downloads a payslip, or checks a policy, and the bot replies in seconds. The HR team sees every request in one place, approves leave with one tap, and spends its time on the cases that need a person. A simple bot can be ready in 3 to 7 days, and it suits any team whose staff already use WhatsApp every day.

What is a WhatsApp bot for HR?

A WhatsApp bot for HR is a chat tool that carries the routine work of a human resources team. It takes leave requests, sends payslips and documents, answers questions about holidays and shifts, and passes the harder cases to HR staff with the full chat history attached. It does not replace HR. It clears the routine so HR can focus on people.

How does requesting leave in chat work?

Requesting leave in chat works when the flow is short and the answer is clear. An employee opens the HR chat and taps request leave. The bot asks for the dates, the type of leave, and one line about the reason if the company asks for it. The employee picks the dates from a simple list, taps send, and gets a confirmation at once.

The bot should show the leave balance before the employee finishes the request. An employee who can see eight days left will pick five days and save the rest. An employee who cannot see the balance will guess, and the request will bounce back.

Approval should be fast and visible. The bot sends the request to the manager, who taps approve or reject with one button. The employee gets a message the moment the manager decides. A request that sits in an inbox for three days feels worse than a request that is rejected in an hour. Speed is part of fairness.

How do staff get payslips and documents?

Payslips work when the employee can get one without asking HR. The employee opens the HR chat, taps payslip, and picks the month. The bot checks who they are, then sends the payslip as a file.

Documents work the same way. A salary certificate or an employment letter can be sent as a file in chat, once HR has approved the request. The bot keeps a record of what was sent and when, so HR can check it later.

Identity checks matter here. A payslip holds personal details, so the bot must confirm who is asking before it sends anything. A simple check, such as a staff number plus a one time code, is enough for most teams. The bot should never send a payslip to a number that has not been verified, and it should never send one person payslip to another person.

How does the bot answer policy questions?

Policy questions are the most common HR messages. How many holidays do I have left? What time does the shift start on Friday? Can I work from home this week? Who do I tell if I am sick? A bot can answer these at once, because the answer is a fact from the company policy. HR writes the answers once, in plain words, and the bot uses them. When the policy changes, HR updates the answer in one place. The same chat pattern works for customer support. The guide to a WhatsApp bot for business support and orders shows how a bot can take requests and send confirmations in chat, and an HR bot follows the same idea for staff.

Some questions need a person. A dispute about pay or a complaint about a manager should go to HR staff, not to a bot. The bot should spot those topics and pass them over fast, with the full chat history attached.

How do you measure HR response time?

Response time is the number HR should track first, because it is the number staff feel. First response time is the time from the employee 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. Staff replies take longer, so HR should set a separate target for those.

Resolution time is the time from the first message to the point where the request is closed. A payslip request resolves in seconds. A leave request resolves when the manager decides. A policy question resolves when the employee has the answer. HR should track these 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 HR should watch it every week. A case that waits two days for a staff reply tells HR something is wrong, even if the bot answered in seconds.

Track these numbers every week. If leave requests take too long, check the manager step. If payslip requests fail, check the identity step. If policy questions pile up, check whether the answer is missing or unclear.

WhatsApp bot vs HR portal vs email vs phone calls

A bot, an HR portal, email, and phone calls can all run HR requests. They work in different ways. The table below shows the main differences for a small or mid sized team.

OptionStrengthsWeaknesses
WhatsApp botStaff already use WhatsApp, answers in seconds, leave and payslips in one chatNeeds setup, sensitive cases still need a person
HR portalOwn screens, can hold full records and reportsStaff forget to open it, needs a password, slow on a phone
EmailGood for long documents, reaches staff without WhatsAppSlow to open, easy to ignore, no instant answer
Phone callsPersonal, good for a staff member who needs to talkStaff time, no written record, no leave tracking

A WhatsApp bot suits a team whose staff already talk on WhatsApp and want leave and payslips without extra calls. An HR portal suits a large company that needs full records and reports. Email suits long documents that need a full page. Phone calls suit a staff member who needs to talk first.

What should an HR bot never do?

An HR bot must never share one employee details with another employee. A payslip goes only to the employee it belongs to. A leave request goes only to the manager and HR. Salary details, leave balances, and personal documents stay inside the HR system.

The bot should also never give legal advice. It can explain what the company policy says in plain terms, and point to the official policy document. It must not tell an employee what their legal rights are, or what action to take in a dispute. That is a job for HR staff or a qualified adviser, in person. The bot should say so in plain words when an employee asks a legal question, and offer the fastest way to reach HR.

What is the risk when AI builds the bot?

AI can build an HR bot in an afternoon. The demo often looks finished, with a leave flow, a payslip download, and a policy answer. The problems show up after launch, when real staff use it. Veracode's 2025 GenAI Code Security Report found AI-generated code introduced a security flaw in 45% of cases tested. Open databases, hardcoded keys, and missing access checks are the kind of flaws that do not show in a demo. They show up when real staff and real data arrive.

An HR bot holds staff names, phone numbers, salary details, leave history, and personal documents. A flaw in that code can expose staff data or let one employee see another employee payslip. Use AI to draft and to learn. For a bot that handles staff data and pay records, have a human review the code and test it with real staff before it goes live.

How can BDBOTS help with an HR bot?

BDBOTS builds WhatsApp bots by hand in Python, with Pyrogram and Telethon, plus React, Node.js, MongoDB, PostgreSQL, and Docker. An HR bot from BDBOTS starts with the team and its staff, not with a template. The team sets up the leave flow, the payslip download, the policy answers, and the handover to HR staff, then tests it with real staff before it goes live. Hiring and HR work often sit side by side. The guide to a Telegram bot for hiring shows how a bot can screen candidates and book interviews, and an HR bot picks up where hiring ends, once the person joins the team.

Every project built by BDBOTS comes with lifetime free support. If something breaks, if WhatsApp updates its rules, or if a leave approval stops working, BDBOTS helps fix it. There is no new support contract to sign, and no surprise bill for basic help. Hosting runs at 99.9% uptime, with auto-restart and monitoring. BDBOTS was founded in 2019, has completed more than 1,000 projects for over 500 clients, and offers a free consultation with a custom-priced quote within 24 hours. To talk through an HR bot, write to contact@bdbots.org or message @bdbots_bot on Telegram, or visit BDBOTS.

FAQ

Can staff request leave without calling HR?

Yes. A staff member who has WhatsApp can open the HR chat, pick the dates, and send the request, all without a phone call. The manager approves it in chat, and the staff member gets the answer at once. Staff who prefer to call can still call.

How does the bot keep payslips private?

The bot checks who is asking before it sends anything. A staff number plus a one time code confirms the identity, and the payslip goes only to that verified number. The bot never sends one person payslip to another person, and HR can see a record of what was sent and when.

Can the bot answer questions about the law?

No. The bot explains company policy in plain terms and points to the official policy document. It does not give legal advice. Questions about legal rights or disputes go to HR staff or a qualified adviser, and the bot passes them over with the full chat history.