Introduction

A Notice to Explain, commonly called an NTE, is a formal written directive from an employer requiring an employee to answer an alleged workplace violation. In business process outsourcing, customer service, sales, collections, technical support, healthcare support, and other call-based industries, one common ground for an NTE is call avoidance.

Call avoidance is treated seriously because call-handling employees are usually paid to be available, ready, and compliant with queue, routing, productivity, and customer interaction rules. When an employer believes an employee intentionally avoided taking calls, prematurely ended calls, manipulated call systems, or failed to follow call-handling procedures, the employee may be required to submit a written explanation.

In the Philippine employment setting, answering an NTE properly matters because it forms part of the employee’s disciplinary record. A careless, emotional, incomplete, or dishonest answer can weaken the employee’s defense. A clear, factual, respectful, and well-supported answer can help show that the alleged act did not happen, was not intentional, was due to a system or operational issue, or does not justify the penalty being considered.

This article discusses how to answer a Notice to Explain for call avoidance under the Philippine workplace context.

What Is a Notice to Explain?

A Notice to Explain is a written notice informing an employee of a charge or accusation and giving the employee an opportunity to respond. It is part of procedural due process in employee discipline.

An NTE usually contains:

the alleged act or omission;
the date, time, or period involved;
the company rule allegedly violated;
the possible penalty;
the deadline for submitting a written explanation; and
sometimes, an invitation to an administrative hearing or conference.

The NTE is not yet a final decision. It is the employer’s way of saying: “There is an allegation against you. Explain your side before we decide.”

An employee should treat the NTE seriously even when the accusation seems minor, mistaken, or unfair.

What Is Call Avoidance?

Call avoidance generally refers to conduct by which an employee intentionally prevents, delays, refuses, evades, mishandles, disconnects, or manipulates calls or call-related systems to avoid performing call-handling duties.

In call center and customer-facing operations, call avoidance may include:

staying in unavailable, auxiliary, after-call work, wrap-up, break, coaching, meeting, or offline status without authorization;
logging in late or logging out early from the phone system;
transferring calls improperly to avoid handling them;
intentionally disconnecting calls;
failing to answer ringing calls;
manipulating the dialer, queue, softphone, headset, or system status;
pretending to experience technical issues;
placing customers on excessive hold without valid reason;
routing customers to the wrong department;
using mute, hold, or release functions improperly;
avoiding difficult customers or difficult call types;
delaying readiness after breaks or lunch;
extending after-call work without legitimate documentation needs;
refusing callbacks or outbound tasks;
failing to take calls while logged in as available;
intentionally lowering productivity or availability metrics; or
engaging in any similar act that reduces call volume handled without authorization.

Not every irregularity is call avoidance. A dropped call, system glitch, headset problem, network issue, power interruption, medical emergency, bathroom need, unclear instruction, or honest mistake may explain the incident. The core issue is often intent.

Why Call Avoidance Is a Serious Workplace Issue

Employers consider call avoidance serious because it affects business operations. In the BPO and contact center industry, call coverage is tied to service level agreements, client commitments, workforce management, customer satisfaction, productivity targets, and revenue.

Call avoidance may be treated as misconduct, neglect of duty, dishonesty, fraud, loss of trust, insubordination, or violation of company policy, depending on the facts and the company code of conduct.

In Philippine labor law, discipline must still be based on both substantive and procedural fairness. The employer must have a valid basis for discipline and must give the employee a fair chance to be heard.

Philippine Legal Context: Due Process in Employee Discipline

In the Philippines, employee discipline involving possible dismissal or serious sanctions generally observes the twin-notice rule:

First notice: the employee is informed of the specific charge and is given an opportunity to explain.
Second notice: after considering the employee’s explanation and evidence, the employer issues a written decision.

The employee must be given a meaningful chance to respond. This does not always require a formal trial-type hearing, but the employee should have the opportunity to submit an explanation, present evidence, and clarify the circumstances.

For lesser penalties, company policy and fairness still require that the employee be informed of the charge and allowed to answer.

An NTE for call avoidance should therefore not be ignored. The written explanation is the employee’s first and often most important opportunity to put the facts on record.

Read the NTE Carefully Before Answering

Before writing a response, the employee should study the NTE closely. The following details are important:

What exact act is being alleged? Is the issue dropped calls, extended after-call work, unauthorized aux use, refusal to answer, incorrect transfer, or system manipulation?
When did it allegedly happen? Note the dates, times, shift, queue, account, call ID, ticket number, or system logs.
What rule was allegedly violated? The NTE should identify the code of conduct, policy, handbook provision, call-handling guideline, client rule, or performance standard.
What penalty is being considered? The possible penalty affects how carefully the employee should prepare the response.
What is the deadline? Missing the deadline may be interpreted as waiver, non-cooperation, or failure to explain.
What evidence is being relied on? The NTE may mention call recordings, system logs, QA findings, workforce reports, screenshots, supervisor observations, or client complaints.
Is the accusation specific or vague? If the NTE lacks enough detail, the employee may respectfully ask for clarification or documents needed to answer properly.

Do Not Ignore the NTE

Ignoring an NTE is risky. Silence may allow the employer to decide based only on available records. Even when the employee believes the accusation is false, exaggerated, or unfair, the proper response is to answer on time.

A simple denial is usually not enough. The employee should provide a factual explanation supported by available evidence.

General Approach to Answering an NTE for Call Avoidance

A strong answer should be:

respectful;
factual;
specific;
complete but concise;
supported by evidence;
non-argumentative;
honest; and
focused on intent, circumstances, and compliance.

The response should not attack the company, insult the supervisor, accuse others without basis, or include irrelevant personal grievances. The goal is to explain what happened and why the allegation is incorrect, incomplete, or not deserving of the contemplated penalty.

Key Defense Themes in Call Avoidance Cases

The appropriate answer depends on the facts. Common defense themes include the following.

1. No Intent to Avoid Calls

Call avoidance often implies deliberate conduct. If there was no intent, say so clearly.

Example:

I respectfully deny that I intentionally avoided calls. I did not manipulate my status or refuse to receive calls. The incident was caused by a technical issue with my softphone, which I immediately reported to my supervisor.

The explanation should then describe what happened, what the employee did, and what evidence supports the lack of intent.

2. Technical or System Issue

Many call irregularities arise from system problems. These may involve softphone malfunction, VPN instability, headset defects, internet disconnection, power interruption, CRM lag, dialer freeze, telephony outage, or queue routing error.

The employee should mention:

the exact issue;
the time it started;
who was informed;
any ticket number or report made;
screenshots, chats, emails, or IT records;
when the issue was resolved; and
whether the employee resumed work afterward.

3. Authorized Status or Instruction

If the employee was in a non-call status because of coaching, meeting, training, bio break, system troubleshooting, supervisor instruction, admin task, documentation, or account activity, the answer should state who authorized it and when.

Example:

At the time mentioned in the NTE, I was placed on coaching by my team leader. I did not independently choose to remain unavailable. The coaching session was work-related and was known to my immediate supervisor.

4. Medical, Emergency, or Health-Related Reason

If the employee had a sudden illness, bathroom emergency, anxiety episode, migraine, asthma attack, dizziness, or other health concern, this may explain temporary unavailability.

The employee should be careful to provide enough detail without oversharing unnecessary private medical information. Medical certificates, clinic logs, nurse records, or supervisor notifications may help.

5. Honest Mistake or Misunderstanding

Sometimes the employee may have misunderstood a procedure, selected the wrong aux code, clicked the wrong status, or believed after-call work was allowed for documentation.

If the issue was a mistake, the answer should acknowledge the mistake, explain that it was not intentional, and state corrective steps.

Example:

I acknowledge that I may have selected the wrong auxiliary code after the call. This was not done to avoid calls. I have since reviewed the proper status usage and will be more careful moving forward.

6. Incomplete or Misread Metrics

Metrics alone may not tell the full story. Low availability, high after-call work, or unusual status duration may require context.

The employee may explain that the record does not account for:

system downtime;
supervisor-directed activities;
long documentation requirements;
customer-specific handling needs;
escalation procedures;
call-back notes;
account tools loading slowly;
queue changes;
split shifts or schedule changes; or
recorded operational incidents.

7. Inconsistent or Unclear Policy

If the employee was not properly informed of the policy, or if the policy was unclear or inconsistently applied, this may be relevant.

However, this should be stated carefully. Instead of saying “The policy is unfair,” say:

I respectfully submit that I was not aware that the specific status usage described in the NTE was prohibited under the circumstances. I had understood from prior practice that the status could be used while completing required documentation. I am willing to comply with any clarification moving forward.

8. First Offense and Proportionality

If the employee has no prior record, good performance, or no previous call avoidance warning, the answer may mention this respectfully. This is especially relevant if the possible penalty is severe.

Example:

I respectfully request that my clean record and the absence of intent be considered in evaluating this matter.

This should not replace the factual defense, but it can support mitigation.

What to Include in the Written Explanation

A well-prepared answer may include the following structure:

1. Heading

Include the employee’s name, position, department, employee ID, date, and subject.

Example:

Subject: Written Explanation in Response to Notice to Explain dated [date]

2. Acknowledgment of the NTE

Start by acknowledging receipt.

Example:

I respectfully submit this written explanation in response to the Notice to Explain dated [date], which I received on [date], regarding the alleged call avoidance incident on [date/time].

3. Clear Position

State whether you deny, admit, partially admit, or clarify the allegation.

Examples:

I respectfully deny that I committed call avoidance.

I respectfully clarify that while I was in unavailable status during the stated period, it was not for the purpose of avoiding calls.

I acknowledge the status discrepancy but respectfully explain that it was due to an honest mistake and not intentional avoidance.

4. Chronology of Events

Provide a timeline. This is very useful in call avoidance cases.

Example:

At approximately 9:15 p.m., my softphone stopped receiving calls. I checked my headset and refreshed the application. At around 9:18 p.m., I informed my team leader through chat. At 9:22 p.m., I restarted the VPN as instructed. I resumed receiving calls shortly after 9:30 p.m.

5. Explanation of the Cause

Explain what caused the incident.

Possible causes include:

technical issue;
supervisor instruction;
after-call documentation;
customer escalation;
emergency;
system downtime;
training or meeting;
misunderstanding;
honest error; or
other legitimate work-related reason.

6. Evidence

Mention attachments or evidence.

Examples:

screenshot of error message;
IT ticket;
chat with supervisor;
email notification;
outage report;
medical certificate;
clinic consultation record;
schedule or meeting invite;
QA notes;
call recording reference;
call ID;
CRM ticket;
workforce management record; or
witness statement.

7. Good Faith and Cooperation

State that you acted in good faith and did not intend to violate company policy.

Example:

I acted in good faith and had no intention to avoid calls or prejudice the account, the client, or the company.

8. Corrective Action

If appropriate, state steps taken to prevent recurrence.

Example:

To avoid a similar incident, I will immediately report any status or system issue, document the report, and confirm with my supervisor before changing or remaining in any non-call status.

9. Request for Fair Consideration

End respectfully.

Example:

In view of the foregoing, I respectfully request that the explanation and attached supporting documents be considered in the evaluation of this matter.

Sample Answer: Denial Due to Technical Issue

Subject: Written Explanation in Response to Notice to Explain dated [date]

Dear [HR/Manager/Team Leader]:

I respectfully submit this written explanation in response to the Notice to Explain dated [date], which I received on [date], regarding the alleged call avoidance incident on [date] at around [time].

I respectfully deny that I intentionally avoided calls. I did not manipulate my phone status, refuse to take calls, or deliberately make myself unavailable. The incident was caused by a technical issue with my [softphone/VPN/headset/system], which affected my ability to receive calls during the period mentioned in the NTE.

At approximately [time], I noticed that [describe issue: the softphone was frozen, calls were not coming through, the VPN disconnected, the headset stopped working, etc.]. I immediately [restarted the application/reconnected to VPN/checked my headset/refreshed the tool] and informed [name of supervisor/team leader/IT] through [chat/email/call]. I also [created an IT ticket/reported the issue/sent a screenshot] at around [time].

I acted in good faith and had no intention to avoid work or calls. After the issue was resolved, I resumed my normal duties and continued taking calls. Attached are [screenshots/chat logs/ticket number/outage notice] showing that the issue was reported and addressed.

In view of the foregoing, I respectfully request that this explanation and the attached supporting documents be considered. I remain committed to complying with company policies and call-handling procedures.

Respectfully, [Name] [Position] [Employee ID]

Sample Answer: Unauthorized Aux Allegation but With Supervisor Instruction

Subject: Written Explanation in Response to Notice to Explain dated [date]

Dear [HR/Manager]:

I respectfully submit this written explanation regarding the Notice to Explain dated [date] concerning my alleged call avoidance due to my auxiliary status on [date/time].

I respectfully clarify that I was not avoiding calls. During the period mentioned, I was in [aux/status] because I was instructed by [name/designation] to [attend coaching/complete documentation/join a meeting/assist with account task/undergo troubleshooting]. I did not independently place myself in that status for the purpose of avoiding calls.

The activity was work-related and known to my immediate supervisor. I returned to available status after the activity was completed. I had no intention to evade calls, reduce my productivity, or violate company policy.

Attached are [chat messages/calendar invite/screenshot/meeting notice] showing the instruction and the reason for my status.

I respectfully request that these circumstances be considered in evaluating the matter.

Respectfully, [Name]

Sample Answer: Honest Mistake in Status Selection

Subject: Written Explanation in Response to Notice to Explain dated [date]

Dear [HR/Manager]:

I respectfully submit this explanation in response to the Notice to Explain regarding the alleged call avoidance incident on [date/time].

I acknowledge that there was a discrepancy in my status during the period mentioned. However, I respectfully explain that this was due to an honest mistake and not an intentional attempt to avoid calls. After completing [call/documentation/task], I mistakenly selected/remained in [status] instead of returning to available status.

I understand the importance of proper status usage and call readiness. I regret the mistake and assure the company that it was not done deliberately. I have reviewed the proper procedure and will be more careful in monitoring my status moving forward.

I respectfully request that my explanation, lack of intent, and record be considered in the evaluation of this matter.

Respectfully, [Name]

Sample Answer: Medical or Emergency Reason

Subject: Written Explanation in Response to Notice to Explain dated [date]

Dear [HR/Manager]:

I respectfully submit this written explanation in response to the Notice to Explain dated [date] regarding my alleged call avoidance on [date/time].

I respectfully clarify that I did not intentionally avoid calls. During the period mentioned, I experienced [briefly state medical or emergency condition], which required me to temporarily step away from taking calls. I informed [name/designation] as soon as I was able to do so.

The situation was unexpected and urgent. My temporary unavailability was not intended to evade work or violate company policy. Attached is [clinic record/medical certificate/chat notification/incident report], which supports my explanation.

I understand the importance of queue coverage and proper reporting. I will ensure that any similar concern is immediately communicated and documented according to company procedure.

Respectfully, [Name]

Sample Answer: Request for Clarification Due to Vague NTE

Subject: Request for Clarification and Written Explanation in Response to Notice to Explain dated [date]

Dear [HR/Manager]:

I respectfully acknowledge receipt of the Notice to Explain dated [date] regarding alleged call avoidance.

I am willing to submit a complete and accurate explanation. However, the notice does not specify the exact call, call ID, time period, system status, recording, or conduct being referred to. To properly respond, I respectfully request clarification of the specific incident, including the date, time, call reference, system log, and policy provision allegedly violated.

Without waiving my right to explain, I respectfully state that I did not intentionally avoid calls or manipulate any system to evade work. I remain ready to provide a more detailed explanation once the specific details of the allegation are provided.

Respectfully, [Name]

What Not to Write in the Answer

An employee should avoid statements that are emotional, hostile, speculative, or self-incriminating.

Avoid writing:

“Everyone does it.”
“My supervisor is targeting me.”
“The company is unfair.”
“I do not care about this NTE.”
“I forgot, but it is not a big deal.”
“I was tired of taking calls.”
“The customer was annoying, so I disconnected.”
“I did not know they were monitoring.”
“You cannot prove anything.”
“I refuse to explain.”

Even if there are issues with management or workplace fairness, the NTE answer should focus on the specific allegation.

Should the Employee Admit the Violation?

The employee should be truthful. If the employee did not commit call avoidance, the answer should deny it. If there was a mistake, the answer may acknowledge the mistake while explaining the absence of intent.

There is a difference between saying:

I intentionally avoided calls.

and saying:

I acknowledge that I remained in after-call work longer than expected, but this was due to required documentation and not an intent to avoid calls.

An admission should not be broader than the facts. Employees should avoid unnecessary self-incrimination.

Importance of Intent

In many call avoidance cases, intent is the central issue. An employee may have low availability or unusual status records, but that does not automatically prove deliberate avoidance.

The employee’s answer should address whether the conduct was intentional, accidental, authorized, justified, or caused by circumstances beyond the employee’s control.

Relevant indicators of lack of intent include:

immediate reporting to supervisor;
IT ticket or system report;
return to available status after resolution;
no pattern of similar incidents;
valid work-related reason;
medical or emergency justification;
clear documentation;
no benefit gained from the incident;
consistent call-taking record; and
cooperation during investigation.

Evidence That Can Help the Employee

The best answer is supported by records. Useful evidence may include:

screenshots of system errors;
softphone logs;
VPN disconnection records;
internet outage notices;
power interruption notices;
IT tickets;
chat messages to supervisor;
call recordings;
CRM notes;
meeting invites;
coaching schedules;
workforce management reports;
medical certificates;
clinic logs;
emails;
QA disputes;
call IDs;
shift schedules;
attendance records;
witness statements.

The employee should attach copies when allowed or refer to them clearly in the explanation.

How to Handle Call Recordings and Logs

If the NTE is based on call recordings or logs, the employee may request access or clarification. The employee can say:

I respectfully request that the relevant call recording, system log, or call ID be considered, as it will show the actual circumstances of the incident.

If the employee has not been shown the recording or log, the response may state:

Based on the limited information available to me, I respectfully deny intentional call avoidance. I am willing to clarify further upon review of the specific call recording or system record relied upon.

This preserves the employee’s position without pretending to know evidence that has not been disclosed.

Answering When There Were Multiple Alleged Incidents

If the NTE lists several dates or events, answer each one separately.

Example structure:

Incident 1: [Date/Time] Explanation: [facts]

Incident 2: [Date/Time] Explanation: [facts]

Incident 3: [Date/Time] Explanation: [facts]

This is better than giving a general denial. It shows organization and credibility.

Answering When the Employee Has No Documents

Not every employee will have screenshots, tickets, or written proof. The explanation can still be factual.

Example:

I no longer have a copy of the chat message, but I reported the issue to [name] at around [time]. I respectfully request that the company check the relevant chat logs, system records, and supervisor notes.

The employee should identify where the evidence may be found.

Should the Employee Apologize?

An apology should be used carefully.

If the employee denies the violation, avoid apologizing for call avoidance. Instead, say:

I regret any operational concern caused by the incident, but I respectfully deny that I intentionally avoided calls.

If there was a genuine mistake, the employee may say:

I apologize for the mistake and assure the company that it was not intentional.

The wording should not accidentally admit deliberate misconduct.

Administrative Hearing or Conference

After submitting the written explanation, the employer may call the employee to an administrative hearing or conference. The employee should prepare by reviewing the NTE, written answer, supporting documents, and timeline.

During the hearing, the employee should:

remain respectful;
answer only what is asked;
avoid guessing;
ask for clarification when needed;
refer to documents;
avoid blaming others without proof;
explain intent clearly;
request that relevant records be reviewed; and
take note of what was discussed.

The hearing is not the time to become argumentative. It is an opportunity to clarify the facts.

Possible Outcomes

After reviewing the explanation, the employer may:

dismiss the charge;
issue coaching or reminder;
give a verbal or written warning;
impose retraining;
issue suspension;
impose final written warning;
terminate employment; or
apply another penalty under the company code of conduct.

The penalty should be proportionate to the offense, the evidence, the employee’s intent, prior record, company policy, and surrounding circumstances.

Substantive Fairness: Is There a Valid Ground?

For discipline to be fair, the employer should have a valid reason. In call avoidance cases, the employer should be able to show that the employee actually committed the alleged conduct and that the conduct violates a known rule or standard.

A serious penalty may be harder to justify where:

the incident was isolated;
the employee had no intent;
there was a technical issue;
the employee reported the problem;
the policy was unclear;
the employee had no prior offense;
the evidence is weak;
the penalty is disproportionate;
the employee was not given a fair chance to explain; or
similarly situated employees were treated differently without justification.

Procedural Fairness: Was the Employee Given Due Process?

The employer should clearly inform the employee of the accusation and give a reasonable opportunity to respond. A vague NTE may be challenged because the employee cannot properly answer an unclear charge.

A procedurally fair NTE should generally identify:

the specific alleged act;
relevant date and time;
policy violated;
possible penalty;
deadline to explain; and
opportunity to submit evidence.

If these are missing, the employee can respectfully raise the issue in the written explanation.

Call Avoidance Versus Poor Performance

Call avoidance and poor performance are not the same.

Call avoidance usually implies intentional evasion of calls or manipulation of systems.

Poor performance may involve low metrics, slow call handling, low productivity, or failure to meet targets without deliberate avoidance.

This distinction matters. If the issue is really performance-related, the employee may argue that it should be treated as coaching, performance management, training, or corrective action rather than misconduct.

Example:

The data may show lower availability during the cited period, but I respectfully submit that this was not due to intentional call avoidance. If there were performance gaps, I am willing to undergo coaching and comply with corrective guidance.

Call Avoidance Versus Negligence

Negligence involves failure to exercise due care. Call avoidance involves intentional evasion. Some cases may fall between the two.

For example, forgetting to return to available status after lunch may be negligence, but not necessarily deliberate call avoidance. Repeatedly using the wrong status after warnings may be treated more seriously.

The employee should explain whether the incident was accidental, isolated, corrected, and not deliberate.

Call Avoidance Versus System Downtime

When systems fail, the employee should not automatically be blamed. However, the employee has a duty to report and follow escalation procedures.

A good answer should show:

the problem was real;
the employee took reasonable steps;
the employee informed the proper person;
the employee did not conceal the issue;
the employee resumed work when able; and
the employee followed instructions.

Call Avoidance Versus Legitimate After-Call Work

After-call work may be legitimate when the employee must complete notes, case documentation, escalation forms, disposition codes, callbacks, or compliance records.

If accused of excessive ACW, the employee should explain:

what documentation was being completed;
why it was necessary;
whether the case was complex;
whether the customer issue required escalation;
whether the system was slow;
whether the employee was following account procedures; and
whether the time spent was reasonable under the circumstances.

The employee should not merely say “I was documenting.” The explanation should be specific.

Call Avoidance Versus Improper Transfer

Improper transfer may be alleged as call avoidance if the employee transferred the customer to avoid handling the issue.

The employee may explain:

the customer’s concern;
why transfer was appropriate;
which department was the correct department;
what procedure authorized the transfer;
whether the employee gave a proper introduction or notes;
whether the transfer was accidental; and
whether there was any intent to evade the call.

Call Avoidance Versus Dropped Call

A dropped call does not automatically mean intentional disconnection. The answer should address:

whether the customer disconnected;
whether the system dropped;
whether the headset or softphone failed;
whether the call recording shows silence or technical failure;
whether the employee attempted a callback;
whether the employee documented the event; and
whether similar drops occurred due to system issues.

Example:

I did not intentionally disconnect the call. The call dropped unexpectedly while I was assisting the customer. I attempted to document the incident and followed the applicable callback procedure.

How to Answer If the Allegation Is True

If the employee did commit the act, the response should still be careful, truthful, and mitigating.

A possible structure:

acknowledge the conduct;
avoid excuses;
explain the circumstances;
express accountability;
show remorse;
state corrective steps;
request consideration of record and proportionality.

Example:

I acknowledge that I failed to return to available status immediately after my break. I take responsibility for this lapse. It was not my intention to avoid calls, and I understand the impact of my action on queue coverage. I have taken steps to monitor my status more carefully and will ensure this does not happen again. I respectfully request consideration of my record and the fact that this was an isolated incident.

Avoid lying. Dishonesty during investigation may become a separate and more serious issue.

How Long Should the Answer Be?

The answer should be long enough to explain the facts but not unnecessarily lengthy. For a simple incident, one page may be enough. For serious allegations or multiple incidents, a longer explanation with attachments may be appropriate.

Quality matters more than length. A good answer is organized, specific, and evidence-based.

Tone of the Answer

The tone should be professional and respectful. Even if the employee feels wronged, the answer should not sound angry or sarcastic.

Use phrases such as:

“I respectfully deny…”
“I respectfully clarify…”
“I submit that…”
“Based on my recollection…”
“Attached are…”
“I acted in good faith…”
“I had no intention to…”
“I respectfully request consideration…”

Avoid hostile phrases such as:

“This is ridiculous.”
“You are accusing me falsely.”
“My supervisor is lying.”
“This company is unfair.”
“I will sue you.”
“Do whatever you want.”

Deadline for Submission

The employee should submit the answer within the deadline stated in the NTE. If more time is needed to gather documents, the employee may request an extension before the deadline.

Example:

I respectfully request an extension until [date] to submit a complete explanation, as I need time to obtain relevant screenshots, system logs, and records necessary to answer the NTE properly.

The request should be reasonable and documented.

Format of the Written Explanation

A clean format helps. Use this basic layout:

Date: [Date] To: [HR/Manager] From: [Employee Name, Position, Employee ID] Subject: Written Explanation in Response to Notice to Explain dated [Date]

Then write the body in short paragraphs. Attach evidence at the end.

Suggested closing:

Respectfully submitted, [Name] [Signature, if printed] [Date]

Checklist Before Submitting

Before submitting, the employee should check:

Did I answer the specific allegation?
Did I state whether I deny, admit, or clarify the charge?
Did I explain the timeline?
Did I address intent?
Did I mention supporting evidence?
Did I attach available documents?
Did I avoid emotional or hostile language?
Did I avoid unnecessary admissions?
Did I keep the tone respectful?
Did I submit before the deadline?
Did I keep a copy for my records?

Common Mistakes Employees Make

1. Submitting a Bare Denial

A response that says only “I did not do it” is weak. Explain why.

2. Being Too Emotional

Anger can distract from the facts.

3. Blaming Others Without Proof

Accusations against supervisors or teammates should be supported by facts.

4. Admitting Intent Carelessly

Do not write statements that suggest deliberate avoidance unless true.

5. Ignoring Evidence

If there are screenshots, chats, or tickets, use them.

6. Missing the Deadline

Late submission can hurt the employee’s position.

7. Copying a Template Without Personalizing It

Templates must be adjusted to the actual facts.

8. Lying

Dishonesty can be worse than the original allegation.

9. Overexplaining Irrelevant Matters

Focus on the incident.

10. Failing to Keep a Copy

The employee should keep the NTE, written answer, attachments, and proof of submission.

Possible Mitigating Factors

Even when there was a lapse, the employee may raise mitigating factors:

first offense;
clean disciplinary record;
good performance history;
lack of intent;
immediate correction;
voluntary reporting;
technical issues;
unclear instruction;
emergency;
minor operational impact;
cooperation with investigation;
willingness to undergo coaching;
no customer harm;
no client escalation;
isolated incident.

Mitigation does not erase the issue, but it may reduce the penalty.

Possible Aggravating Factors

The employer may treat the matter more seriously if there is evidence of:

repeated incidents;
prior warnings;
deliberate manipulation;
dishonesty during investigation;
concealment;
customer complaints;
client escalation;
refusal to follow instructions;
tampering with records;
coordination with others to evade calls;
long periods of unauthorized unavailability;
call disconnections involving customers;
abuse of system status;
failure to report technical issues; or
admission of intentional avoidance.

The answer should address aggravating factors directly when they are raised.

Employee Rights During the Process

An employee subject to an NTE generally has the right to:

know the specific accusation;
be given a reasonable opportunity to explain;
submit evidence;
respond to the charge;
attend an administrative conference when required;
receive a written decision;
be treated fairly and consistently;
question vague or unsupported allegations;
request relevant documents needed to answer; and
seek advice from a lawyer, union representative, or trusted adviser where appropriate.

The employee should exercise these rights professionally.

Employer’s Burden

In disciplinary cases, the employer should have evidence supporting the charge. In call avoidance matters, the evidence may include logs, recordings, reports, supervisor observations, QA findings, and system records.

However, data must be interpreted correctly. A status log may show unavailability, but it may not show why the employee was unavailable. A call may have disconnected, but the recording or system may be needed to determine whether it was intentional.

The employee’s answer should help explain the context behind the data.

When the NTE May Be Defective

An NTE may be questionable if it:

does not state the specific act;
does not identify dates or times;
does not mention the violated rule;
gives no meaningful opportunity to respond;
states a conclusion without facts;
already declares guilt before hearing the employee’s side;
imposes a penalty before explanation;
gives an unreasonably short deadline;
refuses to provide necessary details; or
combines vague allegations without particulars.

The employee may respectfully raise these concerns.

Example:

I respectfully submit that I am unable to fully respond because the NTE does not identify the specific call, time, system status, or policy provision involved. I request these details so I may provide a complete explanation.

Call Avoidance in Work-from-Home Arrangements

Call avoidance allegations are common in remote work because system logs, VPN records, internet stability, and status monitoring are heavily used.

A work-from-home employee should document:

internet outages;
power interruptions;
ISP advisories;
device issues;
VPN disconnections;
screenshots of errors;
messages to supervisors;
IT tickets;
backup internet attempts;
equipment troubleshooting.

If a call issue occurred at home, the answer should show that the employee acted responsibly and promptly reported the problem.

Call Avoidance in Onsite Work

For onsite employees, relevant evidence may include:

station or PC issue reports;
floor support logs;
supervisor observations;
IT assistance records;
headset replacement records;
attendance and break logs;
CCTV, where relevant and lawfully used;
team meeting schedules;
coaching logs;
workforce notes.

The employee should identify who was present or who assisted.

Data Privacy Considerations

Call recordings, customer data, and system logs may involve confidential or personal information. Employees should not improperly copy, download, disclose, or share customer records in violation of company policy or data privacy rules.

When attaching evidence, the employee should avoid exposing customer personal information unless authorized. It is often safer to refer to call IDs, ticket numbers, timestamps, or internal records rather than reproducing sensitive customer data.

Unionized Workplaces

If the employee is part of a union or covered by a collective bargaining agreement, the disciplinary process may include additional rights or procedures. The employee may consult the union representative, especially if the penalty may involve suspension or dismissal.

The written answer should still be timely and factual.

Resignation During an NTE

Some employees consider resigning after receiving an NTE. Resignation does not automatically erase the incident or disciplinary record. Depending on company policy and timing, the employer may still proceed with investigation, affect clearance, or document the matter.

An employee should think carefully before resigning, especially if the accusation is disputed. Submitting a proper explanation may still be important.

Preventing Future Call Avoidance Allegations

Employees in call-handling roles can reduce risk by following these practices:

monitor phone status regularly;
return from break on time;
avoid unauthorized aux use;
report system issues immediately;
take screenshots of errors;
create IT tickets when required;
confirm supervisor instructions in writing;
document long after-call work;
follow transfer procedures;
avoid unnecessary holds;
do not disconnect calls intentionally;
keep customer notes accurate;
clarify unclear procedures;
save relevant work chats when allowed;
comply with queue management rules.

Good documentation is the employee’s protection.

Practical Template

Below is a general template that can be adapted.

Date: [Date] To: [HR/Manager/Team Leader] From: [Employee Name, Position, Employee ID] Subject: Written Explanation in Response to Notice to Explain dated [Date]

Dear [Name/HR/Management]:

I respectfully submit this written explanation in response to the Notice to Explain dated [date], which I received on [date], regarding the alleged call avoidance incident on [date/time].

I respectfully [deny/clarify/acknowledge] the allegation. [State your main position clearly: I did not intentionally avoid calls / the status was authorized / the issue was caused by a system problem / the incident was an honest mistake.]

The relevant circumstances are as follows:

[State what happened first.]
[State what you did next.]
[State who you informed or what report you made.]
[State when you resumed normal work or corrected the issue.]

The incident was not intended to avoid calls or violate company policy. [Explain the cause: technical issue, supervisor instruction, medical concern, documentation requirement, mistake, or other reason.]

Attached are [list documents] in support of this explanation. I respectfully request that these documents and the circumstances stated above be considered in evaluating the matter.

I understand the importance of proper call handling, queue coverage, and compliance with company procedures. I remain committed to following company policies and performing my duties responsibly.

Respectfully submitted, [Name] [Signature] [Date]

Final Thoughts

Answering a Notice to Explain for call avoidance requires more than denial. The employee should respond with a clear timeline, specific facts, supporting evidence, and a respectful explanation addressing intent.

In the Philippine workplace context, the NTE is part of the employee’s opportunity to be heard. It should be treated as a formal document that may affect discipline, employment status, clearance, and future records.

The strongest answer is one that is truthful, organized, calm, and supported by evidence. It should explain what happened, why it was not intentional call avoidance, what records support the explanation, and what steps the employee has taken to prevent recurrence.