BPO Agent Call Avoidance Dismissal: PH Employer Guide

Your WFM analyst flags an agent whose average handle time dropped to 90 seconds overnight, and QA finds dozens of calls released on dead air, customers parked on hold until they hung up, and long stretches in an unauthorized AUX code. The scorecard said top performer. The recordings say otherwise.

This guide is for HR, operations managers and team leads at contact centers and BPO companies deciding whether call avoidance or metrics manipulation justifies dismissal. It covers the right Article 297 ground, the ACD and QA evidence that holds up before a labor arbiter, and the twin-notice steps you still owe the agent.

Direct Answer

A BPO employer may dismiss an agent for deliberate call avoidance or metrics manipulation as serious misconduct under Article 297(a) [282(a)] of the Labor Code, if the act is grave, work-related and done with wrongful intent.^[1][3] Proof must come from call recordings, ACD and AUX logs and QA findings tied to specific calls and dates. Loss of trust under Article 297(c) fits only agents in genuine positions of trust.^[4] A plain failure to hit metrics is a performance case, not misconduct.^[5] Twin notices are mandatory.^[2]

Key Takeaways

Call avoidance and metrics manipulation cover released or parked calls, needless transfers, AUX abuse, false dispositions and survey steering.
Serious misconduct requires gravity, a link to the job and wrongful intent. Recordings that show the agent heard the customer and disconnected anyway prove intent.^[3]
Article 297(c) loss of trust applies to managerial staff and to rank-and-file employees who routinely handle significant money or property. Most voice agents are neither.^[4]
Missing AHT or quality targets without manipulation is gross inefficiency, handled through a PIP and a separate performance case.^[5]
Prior coaching logs, warnings and suspensions for the same behavior count toward the penalty under the totality of infractions rule.^[6]
The NTE must name the specific calls, dates, timestamps and rule violated, with at least five calendar days to answer.^[2]

Legal Basis

Authority	Classification	Rule Supported	Effect
Labor Code Art. 297(a) [282(a)]^[1]	Statute	Serious misconduct in connection with work as a just cause	Dismissal without separation pay if proven
Labor Code Art. 297(c) [282(c)]^[1]	Statute	Fraud or willful breach of trust	Available only where the agent holds a position of trust
Labor Code Art. 292(b) [277(b)]; D.O. 147-15^[1][2]	Statute and implementing rules	Twin notices, five-day answer period, conference, employer burden of proof	Missing steps expose the employer to nominal damages even with a valid cause
Imasen Philippine Manufacturing Corp. v. Alcon (2014)^[3]	Supreme Court decision	Serious misconduct must be grave, work-related and done with wrongful intent	Sets the three elements your evidence must prove
Wesleyan University-Philippines v. Reyes (2014)^[4]	Supreme Court decision	Two classes of positions of trust; breach must be willful and based on clearly established facts	Limits Article 297(c) for ordinary voice agents
Telephilippines, Inc. v. Jacolbe (2019)^[5]	Supreme Court decision	Repeated failure to meet a reasonable AHT metric is gross inefficiency	Separate performance route when no manipulation is proven
Merin v. NLRC (2008)^[6]	Supreme Court decision	Totality of infractions and prior record considered in setting the penalty	Repeated, documented avoidance supports dismissal over suspension

What Counts as Call Avoidance and Metrics Manipulation

Most contact center codes list call avoidance as a major offense. Define the behavior precisely before charging anyone.

Call avoidance

Dead-air releases. The agent answers, hears the customer, then releases the line.
Hold parking until the customer abandons.
Unnecessary transfers of calls the agent could handle, often near end of shift.
AUX abuse. Sitting in a misused aux code, or toggling to not-ready, to stop receiving calls.

Metrics manipulation

False dispositions, such as tagging a real, unresolved concern as a prank call.
Ticket closures without resolution to protect first contact resolution or backlog targets.
Survey steering: surveying only happy customers or coaching scores.
Call splitting to turn one long call into two short ones.

The common thread is deliberate conduct. An agent whose headset failed, whose softphone crashed, or who was simply slow is not avoiding calls. That distinction drives the whole case.

Which Ground to Charge

Serious misconduct under Article 297(a)

This is the primary ground for most voice and chat agents. The Supreme Court requires three elements: the misconduct must be serious, meaning of a grave and aggravated character and not trivial; it must relate to the employee’s duties and show unfitness to continue working; and it must be done with wrongful intent.^[3] Call avoidance fits the second element easily because handling customer contacts is the job itself. Gravity and intent are where cases are won or lost. One released call is rarely grave. A pattern of 40 dead-air disconnects in two weeks, each heard on the recording, shows both. See our serious misconduct dismissal guide.

Fraud or willful breach of trust under Article 297(c)

Many BPO NTEs cite loss of trust by reflex. The Court recognizes only two classes of positions of trust: managerial employees, and fiduciary rank-and-file employees who in the normal course routinely handle significant amounts of money or property, such as cashiers, auditors and property custodians.^[4] A frontline voice agent answering billing questions usually belongs to neither. Article 297(c) is stronger for agents who can issue refunds, account credits or fee waivers, process payments, or access high-value accounts, where manipulated dispositions can hide money moving out of the client’s accounts. Even then, the breach must be willful and founded on clearly established facts.^[4] See the full requirements in our guide to loss of trust and confidence as a just cause.

When it is really a performance case

If QA cannot find deliberate avoidance and the agent simply keeps missing AHT, quality or FCR targets, do not dress it up as misconduct. In Telephilippines v. Jacolbe, the Court upheld the dismissal of a customer service representative who repeatedly failed a 7-minute AHT metric despite step goals and performance improvement plans, treating it as gross inefficiency analogous to gross and habitual neglect.^[5] That route needs reasonable, known standards and documented coaching, not proof of intent. The underperformance and PIP guide walks through it.

Evidence for Call Avoidance Cases

You usually hold a recording of the misconduct itself. Preserve it before platform retention deletes it.

Evidence	Where to get it	What it proves
Call recordings and screen captures of the flagged calls	QA platform, client recording system	The customer was present and audible; the agent released, parked or transferred deliberately
ACD call detail records: answer time, talk time, hold time, release side, transfer destination	Telephony or ACD reports pulled by WFM	Agent-side release seconds after answer, repeated hold abandons, transfer patterns
AUX and agent state logs	WFM real-time adherence reports	Unauthorized aux codes, state toggling, time out of queue versus approved schedule
Disposition and ticket audit trail	CRM or ticketing system logs	Resolved tags that conflict with the recording; closures without action
Code of conduct acknowledgment, client compliance attestations, training and nesting records	201 file, LMS, training team	The agent knew call avoidance and manipulation were prohibited
Coaching logs, prior warnings and suspensions	Team lead files, HR system	Prior notice and the pattern relevant to penalty^[6]
IT incident tickets for the same dates	Service desk	Rules out, or confirms, system or headset issues the agent may raise

Build a call-by-call annex: date, time, call ID, what the recording shows and the rule breached. A WFM “high release rate” summary is a lead, not proof. Use only monitoring the agent was told about at onboarding.

Dismissal or Coaching: The Proportionality Check

Weigh these factors in writing before choosing dismissal:

Volume. One bad shift differs from a pattern across weeks.
Impact. Escalations, repeat callers or SLA penalties.
Concealment. False dispositions that hid the avoidance show intent.
Prior record. The Court allows employers to consider the totality of infractions and the employee’s record in fixing the penalty, and recognizes the right to dismiss a repeat offender as a measure of self-protection.^[6]
Your own code. If your matrix lists first-offense call avoidance as a final written warning, follow it or explain in the decision why the facts justify a heavier penalty.

Our guide to due process and proportionality in disciplinary action covers how arbiters review penalties that look too harsh.

Step-by-Step Procedure

Preserve the data: recordings, ACD records, AUX logs and dispositions, before retention deletes them.
Run a calibrated QA review. Have a second evaluator, not the agent’s team lead alone, listen to the flagged calls and complete the annex.
Rule out system causes using IT tickets and outage reports for the same dates.
Confirm the rule. Pull the signed code of conduct, client compliance training records and any prior coaching on avoidance from the agent’s file and your code of conduct.
Consider preventive suspension only if the agent’s continued access poses a serious and imminent threat, such as access to payment or refund functions. It may not exceed 30 days without paying wages for any extension.^[2] See preventive suspension rules.
Issue the Notice to Explain. Cite Article 297(a), and (c) only if the role is fiduciary. List each call by date, time and call ID, describe what the recording shows, attach or offer the annex, and give at least five calendar days to answer in writing.^[2] Use our Notice to Explain guide for required contents.
Hold an administrative conference. Let the agent listen to the recordings, explain each call and bring a representative.^[2]
Evaluate defenses call by call (system drops, silent or abusive callers, transfer instructions) and remove calls credibly explained.
Apply the proportionality check and record the reasoning.
Serve the written notice of decision stating the facts found, the calls proven, the ground and the penalty, consistent with the twin-notice rule.^[1][2]
Process final pay through the regular release, without unauthorized deductions for client penalties.

Common Employer Mistakes

Charging from a dashboard without listening to the recordings.
Vague NTEs. “You committed call avoidance last month” does not let the agent answer. List the calls.
Reflex loss of trust. Citing Article 297(c) alone for an ordinary voice agent risks a finding that the agent held no position of trust.^[4]
Letting the client decide. A client may ask for an agent’s removal from its program, but only the BPO employer can dismiss, after its own due process.
Mixing misconduct and metrics. Charging an agent with avoidance because AHT is too high or quality scores are low confuses intent-based misconduct with inefficiency.^[5]

Frequently Asked Questions

Can a BPO agent be dismissed for a single instance of call avoidance?

It depends on gravity. One released call, with no concealment and no prior record, will rarely be serious misconduct and is usually handled by coaching or a warning under your code. A single incident can still justify dismissal if it was clearly deliberate and caused serious harm, such as hanging up on an emergency or high-value fraud report.

Is call avoidance serious misconduct or loss of trust?

For most voice and chat agents, serious misconduct under Article 297(a) is the better ground because it focuses on deliberate wrongful conduct. Loss of trust under Article 297(c) requires a position of trust, meaning managerial work or routine handling of significant money or property. Agents who process refunds, credits or payments may qualify, but ordinary agents usually do not.

Can we use call recordings as evidence against the agent?

Yes, when the recordings were made through company or client systems for quality and compliance purposes the agent was informed of, typically in the code of conduct, privacy notice and onboarding. Give the agent a chance to hear the flagged calls during the conference. Keep the files secure and share them only with those handling the case.

What if the agent says the calls dropped because of a system issue?

Check it. Pull IT incident tickets, outage reports and the ACD release-side field for each call, and compare the agent’s drop pattern with others on the same queue and shift. If the recording shows the customer speaking and the agent releasing, the defense weakens. Drop any call the data cannot clearly attribute to the agent.

Is failing AHT or quality targets the same as call avoidance?

No. Missing targets is a performance issue, handled as gross inefficiency with reasonable, known standards and a documented PIP, as in Telephilippines v. Jacolbe. Call avoidance is deliberate misconduct, such as releasing or parking calls to look productive. The evidence, the NTE wording and the legal ground are different, so keep the two cases separate.

Can we deduct client SLA penalties from the agent’s pay?

No. Penalties a client charges the BPO under the service contract are a business cost. Deductions from wages are allowed only in the cases the Labor Code and its rules permit, and client penalties are not among them. Pursue the disciplinary case, but release final pay in full apart from lawful deductions.

What to Do Next

Export recordings and logs today.
Have an independent QA evaluator build a call-by-call annex.
Check the coaching file and your penalty matrix.
Decide whether Article 297(a) alone fits, or whether the agent’s refund or payment access supports adding 297(c).

Use the free Notice to Explain generator to prepare a call avoidance NTE for a BPO agent, with the call IDs, dates, the Article 297(a) ground and the five-day deadline filled in, then download it as a PDF.

Sources and Legal Citations

Labor Code and Implementing Rules

[1] Presidential Decree No. 442, Labor Code of the Philippines, Articles 277(b) and 282 (renumbered Articles 292(b) and 297), LawPhil. Just causes; notice, hearing and employer burden of proof.

[2] DOLE Department Order No. 147-15, Amending the Implementing Rules and Regulations of Book VI of the Labor Code, Supreme Court E-Library. Twin notices, five-day answer period, conference, preventive suspension limits.

Supreme Court Decisions

[3] Imasen Philippine Manufacturing Corporation v. Alcon, G.R. No. 194884, October 22, 2014, Supreme Court E-Library. Serious misconduct must be grave, related to the employee’s duties and committed with wrongful intent.

[4] Wesleyan University-Philippines v. Reyes, G.R. No. 208321, July 30, 2014, Supreme Court E-Library. Two classes of positions of trust; loss of trust must rest on a willful breach founded on clearly established facts.

[5] Telephilippines, Inc. v. Jacolbe, G.R. No. 233999, February 18, 2019, Supreme Court E-Library. Repeated failure to meet a reasonable 7-minute AHT metric despite improvement plans is gross inefficiency; due process observed.

[6] Merin v. National Labor Relations Commission, G.R. No. 171790, October 17, 2008, Supreme Court E-Library. Totality of infractions and the employee’s record are considered in fixing the penalty.

Sources rechecked as of: November 8, 2026

BPO Agent Call Avoidance Dismissal: Employer Rules (PH)

Direct Answer

Key Takeaways

Legal Basis