When the logged-in user is not the assigned agent
Proxy work happens when the person at the workstation is not the employee assigned to the shift. Clients pay for certified agents; operations teams discover billing leakage only during audits or spot checks.
A Gurgaon BPO with 500+ agents flagged proxy patterns when attendance showed login but application usage matched a different skill profile. Client billing and data access rules both broke at once.
Key Takeaway: Proxy work is fraud and a data breach. Treat it as both, not an HR attendance issue alone.
Why it persists in remote and hybrid BPO
Distributed sites, shared credentials, and weak physical access controls make impersonation easy. Traditional attendance systems prove someone punched in, not who is at the keyboard.
Hybrid KPO models made it worse: agents share flats, swap shifts informally, and clients never see the floor. EnDetect login logs without identity checks tell you a session existed, not who typed.
Key Takeaway: Login events are not identity proof. BPOs need verification layered on attendance.
Business impact in rupees and SLAs
Revenue leakage, SLA penalties, and client churn follow repeated incidents. HR investigations without technical evidence rarely hold up in disputes.
One proxy agent on a billed seat for six months at ₹280 PRO plus client rate leakage can cost more than a year of identity verification controls across the team.
Key Takeaway: Finance should model proxy leakage as a line item, not an ops anecdote.
Identity verification as a control
Scheduled, random, and on-demand photo verification matched to HR profile images, plus on-demand checks during sensitive tasks and alerts on mismatches, give operations defensible identity proof alongside live screen monitoring when needed.
Pair identity checks with attendance, idle timer, and screenshots, the same baseline most EnDetect BPO customers already run. Live view stays for escalations, not every seat.
Key Takeaway: Scheduled, random, and on-demand photo capture gives BPO teams identity proof alongside live screen monitoring.
Your next step
Pick one client campaign with strict agent certification rules. Enable identity verification on that pod only for 30 days. Compare mismatch alerts to manual spot-check results. Present findings to the client success team before you scale floor-wide.
Key Takeaway: One certified campaign, one measured month. Client proof beats internal debate.