Location Based Attendance for Pharmacy Staff on WhatsApp
See how location based attendance for pharmacy staff works on WhatsApp - check-in with GPS, auto shift alerts, and a monthly sheet. Setup in 48 hours.

Location Based Attendance for Pharmacy Staff on WhatsApp
It's 9:10 AM and the shutter at your pharmacy is still down. The morning shift pharmacist was supposed to open at 9, but you're standing in the WhatsApp group asking "kaun aaya, kaun nahi" while a customer waits outside for their BP medicine refill. By the time someone replies, you've lost ten minutes and a bit of trust with a regular customer. This happens more often than owners like to admit, especially across multiple counters or a second branch.
The actual cost isn't just the late opening. It's the biometric machine that only works if someone remembers to punch in, the register that gets filled in after the fact ("update kar denge shaam ko"), and the awkward conversation at month-end when a staff member disputes their attendance and you have no proof either way. For a pharmacy where even 15 minutes of a closed shop means a lost sale to the medical store next door, this is a real leak, not a small annoyance.
This guide walks through how location based attendance for pharmacy teams works on WhatsApp — no app to download, no separate hardware — and what it takes to get it running. If you want to see the exact setup, it's here: Staff Attendance & Shift Bot for Pharmacys.
What a Attendance Bot actually does for a Pharmacy
Think of it as a WhatsApp number your staff already have saved, that does four things without you chasing anyone:
- Location-verified check-in: staff sends "in" or shares their location when they arrive; the bot confirms they're actually at the shop (not phoning it in from home) before marking attendance.
- Shift broadcast: instead of you typing out "kal 3 log morning, 2 evening" in a group every night, the bot sends the next day's shift to each person directly, so there's no confusion about who's on counter duty vs who's on delivery.
- Leave request flow: a staff member texts "leave kal" or "sick today" and it's logged with a timestamp and reason, so you're not relying on memory when payroll time comes.
- Monthly attendance export: at month-end, you get a sheet with check-in times, locations, late arrivals, and leaves — the kind of record you'd want if a salary dispute or a labour inspection ever comes up.
None of this needs a biometric machine, a new device at the counter, or staff learning a new app. It rides entirely on WhatsApp, which pharmacy staff — from the senior pharmacist to the delivery boy — are already using.
How it works, step by step
- Staff save your pharmacy's WhatsApp business number (the same one, or a dedicated one for staff use).
- Each morning, or the night before, the bot sends that day's shift assignment to each staff member individually.
- When a staff member arrives, they type "in" or tap the location-share option the bot prompts for.
- The bot checks the shared location against your shop's coordinates (with a small radius, since GPS on phones isn't pinpoint-accurate) and confirms check-in.
- If someone can't come in, they message the bot with a leave reason; it's logged and you get notified.
- Through the day, if a shift change is needed (someone leaves early, a backup is called in), you update it once and the bot handles the announcement.
- At the end of the month, you receive an attendance export — check-in times, late flags, leave days — ready for salary calculation.
Customer: Bhaiya crocin available hai kya, aur bhi kuch cold ke liye chahiye Bot: Haan available hai, aap store pe aa sakte hain ya delivery chahiye?
That's the customer-facing side of your WhatsApp number, which is separate — but it shows why you don't want your staff attendance chatter mixed into the same thread customers are messaging on. Here's what the internal staff flow looks like:
Customer: in Bot: Please share your location to confirm check-in for today's morning shift. Customer: [shares location] Bot: Check-in confirmed at 9:04 AM, morning shift, counter 1.
And a Hinglish version with a leave request:
Customer: Sir aaj thoda late aaunga, bike kharab ho gayi Bot: Noted, aap kitne baje tak pahunch payenge? Shift start 9 AM hai. Customer: 9:30 tak aa jaunga Bot: Theek hai, late arrival note kar diya gaya hai. Please "in" type karke location share karein jab pahunchein.
A typical week, before and after
| Situation | Before | After |
|---|---|---|
| Morning opening | You call around to check who's on the way | Bot shows who's checked in by 9:05 AM automatically |
| Staff calls in sick | Verbal message to one person, easy to forget by evening | Logged with time and reason, visible to you instantly |
| Second branch coverage | You physically visit or call to confirm someone showed up | Location check confirms presence without a call |
| Month-end salary | Register cross-checked against memory, disputes take time to resolve | Exported sheet with timestamps settles disputes in minutes |
| Delivery staff timing | No record of when they left or returned | Check-in/out timestamps show actual working windows |
| New hire during festival rush | Verbal instructions, easy to miss shift timing | Shift broadcast reaches them directly, same as regular staff |
What it costs and what is included
| Item | Price | Notes |
|---|---|---|
| One-time setup | ₹8,000 | Location-verified check-in, shift broadcast, leave flow, monthly export configured for your shop |
| Monthly care plan | ₹1,500/month | Ongoing monitoring, fixes, and adjustments as your staff or shift pattern changes |
| Platform charges (Meta/WhatsApp/telecom) | Billed separately | Usage-based, paid directly to the platform, not marked up by us |
| Lock-in | None | You can stop the care plan anytime; the setup keeps working, support just isn't included |
The way to think about payback: if this setup helps you avoid even one salary dispute, one missed opening, or one instance of "we don't have proof of who came in," it's usually already worth the monthly cost. It's not about big numbers — it's about not losing time and trust over something this basic.
Setup timeline
Day 0
You have a 20-minute call with us. We ask about your shift pattern, how many staff, whether you have a second branch, and what your current attendance process looks like (register, biometric, verbal). No technical prep needed on your end for this call.
Day 1
We configure the bot with your shop's location, set up shift templates based on what you described, and test the check-in flow with a sample location share. You review the shift broadcast message wording and approve it.
Day 2
The bot goes live. Your staff get an introductory message explaining how to check in, and we do a live test with 2-3 staff members to confirm the location radius and shift timing are correct.
What you need to have ready
- A WhatsApp Business number (existing or new) for this to run on
- A list of current staff with their phone numbers
- Your shop's shift timings (morning/evening, or single shift)
- If you have multiple branches, the address/location of each one
- Someone (you or a senior staff member) who can approve the shift broadcast wording before it goes live
Doing it yourself vs done-for-you
| Approach | Time cost | Common failure point | This setup |
|---|---|---|---|
| Biometric machine | Upfront purchase + installation | Breaks down, staff forget to punch, no remote/delivery staff coverage | Works for staff at the counter or making deliveries, no hardware |
| Manual register | Low upfront cost | Filled in after the fact, no location proof, disputes hard to settle | Timestamped and location-verified automatically |
| Free chatbot builder tools | A few hours to a weekend to configure | Location verification and WhatsApp Business API integration are the hard parts; most free tools don't do both well | Configured and tested for your specific shop layout in 48 hours |
| Google Form + WhatsApp group | Free, quick to start | No location check, easy to fill in from anywhere, no automated shift reminders | Genuine location check tied to check-in |
DIY is genuinely fine if you have one or two staff and trust is not an issue — a WhatsApp group and a verbal understanding works. This setup earns its cost once you have 3+ staff, a second branch, or delivery staff where "were they actually there" matters.
Mistakes pharmacies make with this
- Setting the location radius too tight: GPS on budget phones can be off by 20-30 meters indoors; too strict a radius causes false "not at location" flags. Fix: we set a reasonable radius during setup and adjust after the first week's real data.
- Not distinguishing delivery staff from counter staff: delivery staff aren't at the shop's location for most of the day. Fix: delivery roles get a different check-in flow tied to delivery start/end, not the shop's GPS.
- Ignoring the leave flow and still calling staff for leave requests: this defeats the point of having a logged record. Fix: tell staff clearly from day one that leave requests only count if sent through the bot.
- Not reviewing the monthly export: some owners let it pile up and only look at it when there's a dispute, missing patterns like chronic lateness. Fix: a five-minute monthly review catches this early.
- Assuming it replaces supervision entirely: the bot tells you who checked in and where, not whether they're actually working the counter well. Fix: use it for attendance record-keeping, not as a substitute for actually managing your team.
FAQ
Does this work if my staff don't have smartphones?
Location sharing needs a smartphone with WhatsApp, which is standard for most pharmacy staff today. If someone genuinely only has a basic phone, we can set up a manual fallback for that individual while everyone else uses location check-in.
What if a staff member's GPS is inaccurate?
GPS accuracy varies by phone and network signal. We set a reasonable radius around your shop during setup, and if false flags happen in the first week, we adjust it as part of the care plan.
Can this handle two branches with different staff?
Yes. Each branch gets its own location reference, and shift broadcasts are configured per branch so staff at one location aren't confused by the other branch's shift times.
Will my customers see any of this attendance activity?
No. This runs on a separate flow from customer-facing messages. If you use the same WhatsApp number for both, we structure the bot so customer queries and staff attendance don't interfere with each other.
What happens if I stop the monthly care plan?
The setup keeps functioning as configured. You lose ongoing support, adjustments, and fixes if something changes (new staff, shift pattern change), but there's no lock-in or penalty for stopping.
How is this different from a biometric attendance machine?
A biometric machine only works for staff physically punching in at one fixed device, and does nothing for delivery staff or a second branch. This works over WhatsApp from wherever staff are, with location verification instead of a fingerprint scan.
Next step
Send us a WhatsApp message with your pharmacy's city, how many staff you have, and what's currently leaking — late openings, register disputes, or delivery staff tracking. Message us here: WhatsApp.
See the full setup details at Staff Attendance & Shift Bot for Pharmacys, or understand our process first at How we work.
Staff Attendance & Shift Bot for pharmacies
Platform charges billed to you directly. No lock-in. Live within 48 hours once your platform access and Meta verification are complete (Meta verification typically takes 3 to 10 business days). Global systems: 2 to 14 days.