HR attendance and dialer login are two different records
The dialer or chat tool records when an agent is logged in and available; that data belongs to operations and the client. HR attendance records when the agent arrived for the shift, took breaks and left, and it drives pay, leave and incentives. The two should agree, but they answer different questions. Keep ZeniaHR as the record of presence and hours, and let the MIS team compare it with login reports when a gap appears, for example an agent who punched in at 6:55 pm but logged in at 7:25.
Punch at the floor door
Place a biometric device at the entry to the production floor, not at the building gate, so the punch reflects arrival at the seat. Devices that push punches over ADMS feed the same punch stream as the mobile app and kiosks, and duplicate punches within 60 seconds are dropped. On clean-desk floors where phones stay in lockers, the biometric is the main source. A smaller site can use a kiosk tablet at the floor door instead, with a QR code that changes every 30 seconds. When a device is down, HR can record or void a punch with a reason.
Breaks counted in minutes
A typical 9-hour voice shift carries two 15-minute breaks and a 30-minute meal break, one hour in all. Agents punch break start and break end, and ZeniaHR separates effective hours from gross hours. Set the paid break allowance in attendance rules to match your policy, so anything beyond it stands out. Attendance Analytics lists breaks by department and over-break days, which lets a team leader see that the same five agents overrun their breaks most evenings and coach them directly, rather than lecturing the whole floor.
Worked example: late marks on a US process
Suppose the rules allow a 5-minute grace and two free late marks a month, deduct half a day for every two late marks after that, and treat lateness beyond 30 minutes as a half day on its own. Sana is on the 6:30 pm US shift and punches in at 6:42 pm, 12 minutes late, so it is a late mark but not a half day. By the 20th she has four late marks: the first two are free, and the third and fourth together cost half a day. A fifth mark that month would start the next pair. The monthly penalty cap stops one bad week from wiping out the month, and HR can waive a penalty with a reason, for example when the cab arrived late.
How to set it up in ZeniaHR
- Create each client process as a department and each site as a location, so the live board can be filtered by process and shift.
- Connect floor-entry biometric devices over ADMS, or place a kiosk tablet at the floor door where phones are not allowed.
- Add every log-in shift with its timing, break and grace, and flag the night shifts that cross midnight.
- Choose the Strict preset or set grace, free late marks, the half-day step and a monthly penalty cap, then dry-run it on last month.
- Set the paid break allowance and correction limits, and keep attendance alerts on for late arrival and missed punch-out.
- Close the attendance month before incentives and payroll are calculated, reopening it only with a written reason.
Read more about attendance in ZeniaHR.
Roles this applies to
See attendance for bpos and call centres in a demo
We set up your locations, shifts and rules on a video call and show it running for your team. Free for your first 50 employees.
Book a free demoSee pricingFrequently asked questions
How do call centres track agent attendance?
BPOs usually use a biometric or kiosk punch at the production floor, judged against each agent's rostered log-in time, with break punches in between. The dialer's login report is kept separately for operations. In ZeniaHR, punches from biometric devices, kiosks and the app flow into one punch stream, and attendance rules apply grace, late marks and half days per shift.
What is the difference between login hours and attendance in a BPO?
Login hours come from the dialer or chat platform and show when an agent was available to take contacts. Attendance shows when the agent arrived, took breaks and left the shift. Attendance drives pay, leave and late marks, while login hours drive productivity and client reporting. Comparing the two every week shows agents who punch in on time but log in late.
How many breaks do BPO employees get?
It depends on the company and the client, but a common pattern for a 9-hour shift is two 15-minute breaks and a 30-minute meal break. Rest intervals must also meet the limits notified under the OSH Code. Whatever the policy, apply it the same way to every agent; in ZeniaHR, break punches separate effective from gross hours and over-break days show in Attendance Analytics.