Skip to main content
 

1.4.18 Electronic Products and Services Support (EPSS) Managers Guide

Manual Transmittal

July 15, 2026

Purpose

(1) This transmits revised IRM 1.4.18, Resource Guide for Managers, Electronic Products and Services Support (EPSS) Managers Guide.

Material Changes

(1) IRM 1.4.18.1, Programs Scope and Objectives - In (5), converted bullet points to a table to support readability. Updated the content to reflect the most current programs supported in EPSS. In (6), removed the words ‘Online Registration’ from bullet labeled FATCA Users, also converted all bullet points into a table to support readability.

(2) IRM 1.4.18.1.1, Background - In (1), added the words ‘electronic work lists, Live Chat assistance’ to the sentence.

(3) IRM 1.4.18.1.2, Authority - In (1) second bullet, added the title name to the IRM referenced.

(4) IRM 1.4.18.1.3, Roles and Responsibilities - added new subsection between ‘Authority’ and ‘Program Management and Review’ per IRM 1.11.2.2.4 (4) and (5) to address internal controls.

(5) IRM 1.4.18.1.6, Terms and Acronyms - Updated the title to the section to include the word ‘terms’. In (1), Added IRIS (Information Return Intake System) and IRIS TCC (Information Return Intake System Transmitter Control Code) to the table list.

(6) IRM 1.4.18.1.7, Related Resources - In (1), updated wording to better clarity the EPSS intranet site. In (2), updated wording and removed bullets as they are no longer valid on the website listed. Added another paragraph (4) to add the link and info about the Manager Advantage site.

(7) IRM 1.4.18.1.8, Help Desk Support - In (2)a, incorporated the note into the paragraph for better readability.

(8) IRM 1.4.18.2, EPSS Business Measures - In (1), removed the first sentence as the second sentence conveys the idea while making it specific to EPSS. Reworded the last sentence for better clarity. In (2), the wording has been updated, and the Customer Satisfaction paragraph- (formerly letter a) has been removed because it is no longer offered. The contract terminated April 2025, the survey will be maintained in-house by JOC. In (3)a, added the words ‘and TSO Phones’ to the paragraph. In (3)f and g, added the names of the forms referenced after each form.

(9) IRM 1.4.18.4, Leadership - In (2), incorporated the note from paragraph number one into a new paragraph for better clarity.

(10) IRM 1.4.18.5, Administrative Guidelines - In (3), added the name of the IRM referenced. Added Federal Taxpayer Information (FTI) as an importance in protecting sensitive data and referenced IRM 10.5.5 for UNAX policy guidance. In (4), convert the list into a table for ease of reading.

(11) IRM 1.4.18.5.1, Recurring Duties of the EPSS Manager - In (3), removed mention of the National Agreement as it is no longer applicable.

(12) IRM 1.4.18.5.1.1, Daily Duties - IPU 24U1145 dated 11/19/2024. In (1)h, added Live Chats into the wording, as the new Live Chat system is now in effect. In (1)j, added the words Live Chat to the sentence and changed the end of the sentence to say, ‘review needed staffing’. In (1), convert alpha list into a table.

(13) IRM 1.4.18.5.1.2, Weekly Duties - In (1)d, removed the last two sentences as both overtime and compensatory time are reported on the same Form 2787 and do not need to be reported separately. Converted the list into a table for ease of reading.

(14) IRM 1.4.18.5.1.3, Monthly Duties - In (1)b, removed the reference and mention of the National Agreement due to the Executive Order 14251, Exclusions from Federal Labor-Management Relations Programs dated March 27, 2025. In (1)c, removed the reference and mention of the National Agreement and changed the word in the sentence from ‘must’ to ‘should’. In (1)d, added parenthesis and the words ‘chat and inventory’ after non-phone, for better clarity. Converted the list into a table for ease of reading.

(15) IRM 1.4.18.5.1.4, Periodic Duties - In (1)c, reworded the sentence and removed the word ‘department manager’ and added the ‘Operations/TSO Senior Manager’ for better readability. Removed the reference to the National Agreement. In (1)d, removed the reference to the National Agreement. Converted list into a table for ease of reading.

(16) IRM 1.4.18.5.1.5, Annual Duties - In (1)a, removed the sentence regarding the need to notify NTEU. In (1) b, incorporated the note into the paragraph for better readability. In (1)c, removed the reference and mention of the National Agreement, also updated the list of the mandatory briefings to be the most current. Converted list into a table for ease of reading. In (2), removed the reference and mention of the National Agreement and updated wording in the bullets to reflect the updated teleworking policies to reflect current criteria and forms found in IRM 6.800.2, Telework Program. Also changed the last sentence into a bullet point.

(17) IRM 1.4.18.5.2, Leave Administration - In (2), converted last two sentences into bullet points to improve the ease of reading.

(18) IRM 1.4.18.5.2.1, Leave Scheduling Process - In (2), added letter -e to the list and verbiage that 25% of a site’s phone assistors may be granted leave per day, etc. Also incorporated the reminder note into the alpha list (f) for better readability. In (3), removed reference and mention of the National Agreement.

(19) IRM 1.4.18.5.2.2, Leave Counseling - In (1), removed the sentence that references and mentions the National Agreement. In (2), converted the number list to an alpha list for better clarity. In (2)a, removed the reference and mention of the National Agreement and added the words ‘Employee Expectations document’ to the sentence. In (2)b, reworded to address using the memorandum to explain how the employee is not in compliance. In (2)c, changed Labor Relations to now be Employee Relations. Incorporated the reminder note into the paragraph for better readability. In (3), changed LR to ER as it is now employee relations not labor relations.

(20) IRM 1.4.18.5.3, Conduct Counseling - In (3), removed the sentences about contacting the LR specialist and having the right to a union representation, also removed the note about requesting a steward. In (5), incorporated the note into alpha list (f) for better readability. In (6), incorporated the note into a new paragraph (8) for better readability. Changed LR to ER as it is now employee relations not labor relations. In (7), changed LR to ER.

(21) IRM 1.4.18.5.4.1, Monitoring and Reviews - IPU 24U1145 dated 11/19/2024. In (3), added Live Chats. In (4) added Live Chats. In (5) added Live Chats. In (6), removed references to the National Agreement. In (7) added Live Chats . Revised ‘paper case reviews’ to ‘inventory case reviews’. In (7)a, clarified review requirements. Managers must conduct two to four reviews per month. Leads may conduct one of the reviews per month. In (7)b, incorporated the note into the paragraph for better readability. In (7)c, removed the reference to the exhibit for the review waiver memorandum as it is now published as form 15727 in the product catalog. Reworded the sentence to cite the new form. In (9), removed the reference to the National Agreement. Incorporated the note into a bullet point and formatted in bold for emphasis due to the timeframe. In (11), incorporated the note and last sentence into bullet points for better readability. All changes are to improve IRM accuracy.

(22) IRM 1.4.18.5.4.2, Managers - In (4), updated wording to be more generic as the number of reviews can change, removed the note as it is not needed. In (5), added the words ‘chat, inventory case’ to the parenthesis in the sentence. In (6), removed this whole paragraph as it was a duplicate of IRM 1.4.18.5.4.1 (7)c.

(23) IRM 1.4.18.5.4.3, Telephone/Paper Monitoring - In (1) reworded the sentence to reflect the IRM referenced based on the policy statement. In (2), replaced the word ‘Telephone/Paper’ to ‘Performance’.

(24) IRM 1.4.18.5.4.5, Sharing Reviews - In (1), incorporated the note that was after the table into the paragraph before the table for better readability. In (2), replaced the words ‘phone monitoring’ with ‘the review’.

(25) IRM 1.4.18.5.4.6, Verint - In (5), incorporated the note into a new paragraph.

(26) IRM 1.4.18.5.4.7, Access to Recorded Calls - In (2), reworded the last sentence to follow plain language guidelines. In (3), removed this whole paragraph as it references NTEU, which terminated as of March 27, 2025, Executive order 14251, Exclusions from Federal Labor-Management Relations programs signed by the President, this includes the 2022 National Agreement and the 2025 Addendum.

(27) IRM 1.4.18.5.4.8, Centralized Quality Review System (CQRS) - In (1), edited the sentences for better readability. In (2)a, updated the name of the IRM referenced.

(28) IRM 1.4.18.6, Non-Evaluative or Coaching Reviews - In (1), changed the second bullet point from ‘paper inventory reviews’ to ‘inventory case reviews’ for better clarity.

(29) IRM 1.4.18.6.3, EPSS Phone Certification Plan - In (3) and (4), reworded the sentences for better clarity.

(30) IRM 1.4.18.6.4, EPSS Paper Certification Process - Changed all instances of ‘paper’ to ‘inventory case’ for each mention throughout section, including the title, for better clarity.

(31) IRM 1.4.18.6.5, EPSS Live Chat Assistance Certification Process - IPU 24U1145 dated 11/19/2024. Added new IRM section (one through seven), because of the new Live Chat system process is now in effect.

(32) IRM 1.4.18.7.1, Operations Support Staff Conducting Reviews - In (3), removed the bullet for the National Agreement. In (5), converted the bullet points into a table for better readability. In (6), incorporated the note into the paragraph for better readability. In (7), incorporated the note into the paragraph for better readability. In (9), incorporated the note into the paragraph for better readability.

(33) IRM 1.4.18.7.2, Department, Operation or Front-Line Manager - Changed the title order to be Operation, Department or Front-Line Manager for clarity. In (2), converted the bullet points into a table for better readability. In (3), added chat and inventory cases to the parenthesis in the first bullet. Also incorporated the note into a new paragraph (6).

(34) IRM 1.4.18.8, E-help Support System (EHSS) Guidelines - In (2), changed the wording ‘e-services Level 2’ to ‘Product & Services Support’ in the second sentence. Also, in the first bullet point removed the wording ‘Third Party Data Store (TPDS)’ and added ‘External Customer Data Store (ECDS)’. In the last bullet added the names of the forms.

(35) IRM 1.4.18.8.1.1, Systems Used by EPSS Assistors - In (1)c, separated the topics into FIRE and Online Fillable Forms. Then converted the list into a table for better readability.

(36) IRM 1.4.18.8.1.2, Roles in the Employee User Portal (EUP) - In (1), removed the table and re-worded the sentence to be more generic for EPSS. In (2), removed the table and re-worded the sentence to be more generic by adding e-help and TSO.

(37) IRM 1.4.18.8.4, Monitoring E-mail in EHSS - In (4), incorporated the reminder note into a bullet point for better readability.

(38) IRM 1.4.18.9.2, Unified Contact Center Environment (UCCE) Supervisor Features - In (1)d, changed the wording to replace telephone jack with Teams and share screen/audio for monitoring as this is now in Teams. In (2), incorporated the reminder note into paragraph 1a for better readability. In (4), incorporated the note into the paragraph for better readability.

(39) IRM 1.4.18.9.2.1, Managing Features - In (3), incorporated the note into the paragraph for better readability.

(40) IRM 1.4.18.9.3, Staffing Requirements - In (1), incorporated the note into the paragraph for better readability. In (4), incorporated the note into the paragraph for better readability. In (5), incorporated the note into a bullet point for better readability.

(41) IRM 1.4.18.9.3.1, Adherence - In (2)b, removed the title ‘exception’ from the table for better clarity.

(42) IRM 1.4.18.9.3.5, Idle Reason Codes - In (4), incorporated the caution note into the paragraph for better readability.

(43) IRM 1.4.18.9.3.6, Scheduling Employees on the Telephones - In (3), incorporated the note into the paragraph for better readability.

(44) IRM 1.4.18.9.3.8, Aceyus Reports - In (5), incorporated the note into a bullet point for better readability.

(45) IRM 1.4.18.10.1, EHSS Reports - In (1), convert the list into a table. In (2), convert the list into a table. For ease of readability.

(46) IRM 1.4.18.10.2, Infrastructure Update Project (Finesse / CTIOS / IPBlue Desktop application) Reports - In (3), incorporated the note into the second bullet for better readability.

(47) IRM 1.4.18.11, EHSS Business Continuance and Disaster Recovery - In (2), changed the number list to an alpha list for better readability. In (3), changed the number list to an alpha list for better readability. In (4), changed the number list into an alpha list for better readability. In (5), removed the chart and reworded the sentence. Incorporated the note into the paragraph for better readability. In (6), incorporated the reminder note into the paragraph for better readability.

(48) IRM 1.4.18.12.4, Personally Identifiable Information (PII) - In (1), added name titles to the IRM references. In (5), added the name title to the IRM referenced.

(49) IRM 1.4.18.12.5.1, Business Requirements - In (1), incorporated the first note into the fourth bullet and incorporated the second note into the sixth bullet for better readability. Also removed the fifth bullet about the negotiated agreements with the NTEU as it no longer applies.

(50) IRM 1.4.18.12.5.4, The Process - In (1), incorporated the note into the paragraph for better readability.

(51) IRM 1.4.18.13, eGain Live Chat System Guidelines - IPU 24U1145 dated 11/19/2024. Added new IRM section for the new eGain program (one through eight), for the new Live Chat system and process that is now in effect.

(52) IRM 1.4.18-1, Exhibit - Removed the exhibit for the EPSS Review Waiver Memorandum. The review waiver was created as a form 15727 and published in the catalog, under catalog number 96283B.

(53) Updated various links as well as minor grammatical and editorial changes throughout the IRM for better readability in plain language.

Effect on Other Documents

IRM 1.4.18 dated 07-30-2024 (effective 07-30-2024) is superseded. The following IRM Procedural Update (IPU) 24U1145, issued 11/19/2024, has been incorporated into this IRM.

Audience

Managers of Electronic Products and Services Support employees

Effective Date

(07-15-2026)

Related Resources

Managers will use this IRM in conjunction with IRM 3.42.4, IRS e-file for Business Tax Returns, IRM 3.42.5, IRS e-file of Individual Income Tax Returns, IRM 3.42.7, EPSS Help Desk Support, IRM 3.42.8, E-Services Procedures for Electronic Products and Services Support, IRM 3.42.9, IRS e-file of Information Returns, IRM 3.42.10, Authorized IRS e-file Providers, IRM 3.42.20, Preparer e-file Hardship Waiver Requests, and IRM 21.3.11, Information Returns Reporting Procedures, which provide policies and procedures for Electronic Products and Services Support assistors and other users.

Jason Romero-Stephens
Director, Electronic Products and Services Support (EPSS)
Taxpayer Services Division

Programs Scope and Objectives

  1. Purpose: To provide managers with techniques and guidelines for managing employees in Electronic Products & Services Support (EPSS). EPSS is a stand-alone organization reporting to the Director, Customer Accounts Services (CAS) in the Taxpayer Services (TS) Division. EPSS is a centralized office for the management of the Internal Revenue Service (IRS) electronic products and services within TS CAS. The EPSS vision is: Advance IRS electronic business opportunities to meet the changing demands of the future while delivering a positive customer experience. The mission statement is: Support customer-valued e-solutions for Service-wide electronic products and services. Visit the EPSS intranet site at EPSS

  2. Audience: Managers in Electronic Products & Services Support located in Andover, Atlanta, Austin, Cincinnati, Lanham/Seabrook, Martinsburg, and Ogden.

  3. Policy Owner: Director, Electronic Products and Services Support (EPSS).

  4. Program Owner: Operations Support, Electronic Products and Services Support, Taxpayer Services (TS).

  5. EPSS supports the following programs:

    EPSS Support Programs
    Affordable Care Act (ACA) Information Returns (AIR) System
    Affordable Care Act (ACA) Information Returns - Form 1094-B / Form 1095-B and Form 1094-C / Form 1095-C
    Business Tax Account (BTA)
    Electronic Federal Tax Payment System (EFTPS)
    Electronic filing of tax returns and information returns
    E-Services, this includes the IRS e-file Application, Secure Object Repository (SOR) mailbox, Transcript Delivery System (TDS), and Taxpayer Identification Number (TIN) Matching
    Filing Information Returns Electronically (FIRE)
    Foreign Account Taxpayer Compliance Act (FATCA) online registration and International Compliance Management Module (ICMM) Error Notifications
    Information Return Intake System (IRIS)
    Modernized e-File (MeF) for Tax Returns
    System for Award Management (SAM)
    Transmittal Control Code applications to file information returns
  6. Below is a list of EPSS customers:

    EPSS Customers
    Affordable Care Act (ACA) Providers
    Circular 230 Practitioners
    Electronic Return Originators
    Employers
    Enrolled Agents
    FATCA Users
    Financial Institutions
    Government Agencies
    Government Contractors
    Income Verification Express Service (IVES) Users
    Intermediate Service Providers
    Large Corporations
    Low Income Tax Clinics (LITC)
    Payers or Issuers
    Registered Return Preparers
    Reporting Agents
    Software Developers
    State Tax Administration Agencies
    Tax Assistance Centers (TAC)
    Tax Counseling for Elderly (TCE) Offices
    Transmitters
    Volunteer Income Tax Assistance (VITA) Sites

Background

  1. Electronic Products and Services Support (EPSS) managers provide leadership and direction to employees responsible for inquiries received via telephone, correspondence (paper), electronic worklists, Live Chat assistance, and e-mail.

Authority

  1. The following legal and regulatory authorities guide Electronic Products and Services Support (EPSS).

    • IRC 7803(a)(3), Taxpayer Bill of Rights. Additional information found on the IRS.gov website at Taxpayer Bill of Rights.

    • Policy Statement 1-236 Fairness and Integrity in Enforcement Selection. See IRM 1.2.1.2.36, Policy Statement 1-236, Fairness and Integrity in Enforcement Selection.

Roles and Responsibilities

  1. Designated roles are responsible for creating, updating, and maintaining documentation in coordination with other IRS entities. When changes occur, the party responsible must notify all impacted stakeholders to ensure a smooth transition for both internal and external parties.

  2. All assignments executed in accordance with the Taxpayer Bill of Rights as listed in IRC 7803(a)(3).

  3. The Director of EPSS is responsible for supporting customer-valued e-solutions for IRS electronic products and services.

  4. EPSS Program Management is responsible for the policy and procedures contained in this IRM.

  5. Team Managers are responsible for understanding the content of this IRM and to ensure the employees adhere to the procedures contained in the IRM. When updates are identified, they must review and approve prior to submission to the IRM author.

Program Management and Review

  1. Managers manage work programs and ensure completed EPSS work, according to procedural guidelines contained in applicable IRMs.

  2. Managers refer to guidelines outlined in other IRMs such as:

    • Part 1, Organization, Finance and Management

    • IRM 3.42.4, IRS e-file for Business Tax Returns

    • IRM 3.42.5, IRS e-file of Individual Income Tax Returns

    • IRM 3.42.7, EPSS Help Desk Support

    • IRM 3.42.8, E-Services Procedures for Electronic Products and Services Support

    • IRM 3.42.9, IRS e-file of Information Returns

    • IRM 3.42.10, Authorized IRS e-file Providers

    • IRM 3.42.20, Preparer e-file Hardship Waiver Requests

    • IRM 21.3.11, Information Returns Reporting Procedures

  3. Managers are knowledgeable in the use of various tools/resources used by EPSS employees. Examples of these tools/resources include:

    • e-help Support System (EHSS)

    • Servicewide Electronic Research Program (SERP)

    • SERP Job Aids

Program Controls

  1. The IRS uses access control measures to provide protection from unauthorized alteration, loss, unavailability, or disclosure of information. Access control will follow the principle of least privilege and separation of duties. This IRM provides guidance for managing access to protected data and for reviewing adherence to data security and procedural guidelines.

  2. Managers must review administrative, privacy, security, and safety practices according to the responsibilities outlined in this IRM in conjunction with other applicable IRMs and IRS guidance.

Terms and Acronyms

  1. Acronyms identified in specific subsections of this IRM. See some of the most common or frequently used acronyms listed below.

    Acronym Definition
    ACA Affordable Care Act
    Aceyus Aceyus provides and displays team, site, and enterprise level of information on the telephone traffic, ready agents, level of service (LOS), abandoned calls and VCR busy.
    BEARS Business Entitlement Access Request System
    BTA Business Tax Account
    CCB Change Control Board
    CJE Critical Job Elements
    CQRS Centralized Quality Review System
    DM Department Manager
    eEPF electronic Employee Performance File
    EFTPS Electronic Federal Tax Payment System
    EHSS e-help Support System
    EQRS Embedded Quality Review System
    ESAM External Services Authorization Management
    EUP Employee User Portal
    FATCA Foreign Account Taxpayer Compliance Act
    Finesse / CTIOS / IPBlue Desktop application Infrastructure Update Project
    FIRE Filing Information Returns Electronically
    IEP Integrated Enterprise Portal
    IR TCC Information Return (IR) Application for Transmitter Control Code (TCC)
    IRIS Information Return Intake System
    IRIS TCC Information Return Intake System (IRIS) Transmitter Control Code (TCC)
    ITM Integrated Talent Management
    SADI Secure Access Digital Identity
    SEID Standard Employee Identifier
    SERP Servicewide Electronic Research Program
    SETR Single Entry Time Reporting
    SPRG Specialized Product Review Group
    TDS Transcript Delivery System
    TM Team Manager

Related Resources

  1. An excellent resource for EPSS managers is the EPSS intranet.

  2. The Human Capital Office (HCO) offers a wealth of managerial tools and information via their share point page (under Services/Support), found at: Human Capital Office (HCO)

  3. Another excellent managerial tool is iManage, iManage Home page. iManage is a virtual community for IRS managers. It contains targeted information, advice and interactive features to help you work more efficiently. The iManage site automatically grants access to employees coded as managers in HRConnect. You cannot access the site if you are not a manager.

  4. Another self-service resource is the Manager Advantage share point that all IRS Managers can access to obtain real-time HR guidance, solutions, and training.

Help Desk Support

  1. EPSS employees have extensive knowledge of IRS electronic products. Some tasks performed in the position require a very specialized skill set.

  2. EPSS escalation path for assistance is as follows:

    1. Level 1 - The assistor is the first point of contact for customer issues. The Level 1 assistor maintains contact directly with the customer and interfaces with internal support groups as necessary. Level 1 handles all issues within the scope of their training and authority. They are responsible for documenting the Interaction in a detailed and complete manner. Typical issues include, but not limited to, failed transmissions, rejected returns, and assistance with Internet-based applications. Transfer or escalate the Interaction to Level 2 or as instructed in the solution, if the issue is beyond the scope of Level 1. Once an Interaction is escalated it becomes an Incident.

    2. Level 2 - The employee has more experience, knowledge and training needed for resolution of an issue. Level 2 personnel include, but not limited to, Information Technology (IT) specialists, leads, managers, business analysts, etc. Level 2 resolves issues and follows up with the customer to ensure all issues have been resolved to the customer's satisfaction. Typical issues include, but not limited to, error code issues resulting from web products, e-services trouble shooting, and communication and connectivity issues not resolved at Level 1. Level 2 will engage Level 3 as necessary.

    3. Level 3 - Personnel interfaces with internal groups, not external customers. System administrators and developers handle issues which may include, but not limited to, web server availability, undocumented hard code errors, etc.

  3. EHSS is the primary tool for recording customer interaction and trouble-ticketing. With e-mail EPSS manager can track communication with customers, from arrival through resolution. The e-mail function provides intelligent routing, service-level management, and reporting, and allows for content analysis techniques and keyword searches to automate problem identification. EPSS is a full-service support network skilled in providing technical assistance to external customers who encounter problems using IRS electronic products.

EPSS Business Measures

  1. EPSS has established measures to support and reinforce the achievement of the IRS mission statement and strategic goals. These measures align with the IRS balanced measures framework.

  2. The areas of measurement are:

    1. Employee Satisfaction – EPSS uses the IRS Workgroup Questionnaire to identify successes and improvement opportunities to increase employee satisfaction and employee engagement while achieving higher productivity through a quality work environment.

    2. Business Results – EPSS developed and implemented business measures to provide information on current performance, determine goals met, and identify improvement opportunities. Communicate the results from the measures to customers, stakeholders, and other interested parties.

  3. The EPSS business measures and their definitions are below. EPSS Business Measure Goals are in the annual program letter.

    1. Customer Accuracy - Giving the correct answer with the correct resolution. This measure is a weighted score to reflect the relative volume of the e-help Phones and TSO Phones Specialized Product Review Group (SPRG).

    2. First Contact Resolution (FCR) – The percentage of customer interactions resolved on first contact.

    3. Level of Service – The relative success rate of tax professionals who call seeking assistance from an e-help Desk or Technical Services Operation (TSO) employee.

    4. Average Speed of Answer – A measure of the average number of seconds customers waited in an assistor queue seeking assistance from the e-help Desk or TSO.

    5. Third Party and Business e-Transactions - The sum of all e-services transactions processed through the Integrated Enterprise Portal (IEP) by third parties.

    6. Number of Information Returns Filed Electronically - Total number of information returns processed electronically – includes Form 1098, Mortgage Interest Statement, Form 1099, U.S. Information Return for Calendar Year 1971, Form 5498, IRA Contribution Information, Form W-2G, Certain Gambling Winnings Form 1042-S, Foreign Person’s U.S. Source income Subject to Withholding, and Schedule K-1, Beneficiary’s Share of Income, Deductions, Credits, etc. (excludes Form W-2, Wage and Tax Statement and Form 1099-SSA / RRB received from SSA).

    7. Percent of Information Returns Filed Electronically - The percent of information returns processed and electronically filed – includes Form 1098, Mortgage Interest Statement, Form 1099, U.S. Information Return for Calendar Year 1971, Form 5498, IRA Contribution Information, Form W-2G, Certain Gambling Winnings, Form 1042-S, Foreign Person’s U.S. Source Income Subject to Withholding, and Schedule K-1, Beneficiary’s Share of Income, Deductions, Credits, etc. (excludes Form W-2, Wage and Tax Statement, and Form 1099-SSA / RRB received from SSA).

The Manager's Roles

  1. EPSS managers fulfill three broad roles:

    1. Leading employees to achieve a goal

    2. Executing administrative responsibilities

    3. Scheduling and controlling the assigned workload

Leadership

  1. Leadership is the art of motivating a group of people to act towards achieving a common goal. As a team leader in the EPSS organization, your role significantly impacts the achievement of the program objectives. Take ownership of all program assignments and be knowledgeable of all policies and procedures outlined within this IRM as well as other applicable IRM references.

  2. Managers must be knowledgeable in the electronic products (e.g., e-file, e-services, EFTPS, FIRE, IRIS, and SAM) worked by their site. If a site has more than one manager, the managers will share responsibilities.

  3. It is important you lead by example. The work group will follow your leadership when they view you modeling what you communicate. Leadership requires that you model the highest standards of ethics and integrity. A workgroup is reflective of its leadership. A positive attitude will influence your employees and their contributions.

  4. Leadership involves coaching and mentoring your employees. As you identify opportunities for performance improvement, it is your role as a leader to assist employees in improving performance through coaching, mentoring, and providing timely feedback. As a leader at the IRS, you are to lead using the balanced measures framework approach by considering customer satisfaction, employee satisfaction, and business results. See IRM 1.4.18.2, EPSS Business Measures.

  5. A major objective of IRS Leadership Development is promoting and supporting continuous learning. See the following share point for information on leadership development: Leadership Readiness Programs.

Administrative Guidelines

  1. General administrative guidelines for all IRS managers found in IRM 1.4.4, Resource Guide for Managers.

  2. In the event employees need to take equipment out of the building to work from a telework location (e.g., their home), the manager must keep a record of all removed equipment for telework use. As part of this record and when available, managers must record the barcodes of the laptop, monitor(s) and the serial number of the lock for the laptop. Notate if the employee has an extra monitor that they are keeping at the telework location.

  3. Managers are responsible for following and ensuring employees adhere to the Clean Desk Policy, as outlined in IRM 10.5.1.5.1, Clean Desk Policy. Managers must be continually alert and proactive in protecting sensitive but unclassified data which includes personally identifiable information (PII), Federal Taxpayer Information (FTI), and tax information. Refer to IRM 10.5.5 , IRS Unauthorized Access, Attempted Access or Inspection of Taxpayer Records (UNAX) Program Policy, Guidance, and Requirements. Managers must secure and lock all sensitive employee personnel and taxpayer data in cabinets or drawers.

  4. Internet and intranet web sites contain the most up-to-date information. There are also sites designed to assist with the development of managers and their employees. Shown below are a few helpful sites.

    Website Explanation
    Enterprise Telephone Data (ETD) Reporting Provides links to reports to assess business and employee performance.
    IRS Intranet Home Page Default intranet home page for all employees. Provides the starting point for research.
    Joint Operations Center (JOC) Provides links to service, support, and technology for all telephone, correspondence, and electronic media for Joint Operations Center customers.
    Mandatory Briefings - Home (sharepoint.com) Provides information on the delivery of mandatory employee briefings. Employees utilize the Integrated Talent Management (ITM) system to take the briefings. The ITM system automatically updates their learning history as they finish each briefing and tracks their progress.
    SERP - Emergency Procedures - AM Research Portal Provides information regarding assault and threat incidents, bribery attempts, Potentially Dangerous Taxpayer (PDT), significant incidents, sexual harassment, bomb threats card, personal safety, safety and security overview, and suicide threats.

Recurring Duties of the EPSS Manager

  1. Work in EPSS is often fast-paced and intense. Managers must continually be cognizant of the conduct and performance of permanent and returning seasonal employees, as well as the progress of any new hires. At the same time, managers must provide an acceptable level of service to customers and maintain an acceptable level of inventory.

  2. Implement procedures timely so resources can be best utilized. Thus, it is critical that managers are alert to tasks that occur at regular intervals.

  3. The following sections provide a breakdown of some of those tasks and the intervals at which they should be performed. Though not all inclusive, it serves as a quick reference guide to managerial duties. For detailed instructions, refer to other appropriate resource materials.

Daily Duties
  1. Perform the following duties daily:

    Daily Duties Action
    Attend conference calls Because EPSS sites are in different locations around the country, conference calls are one of the primary means of communication. Attend calls promptly and submit agenda items when appropriate prior to the meeting.
    Check e-mail Check e-mail throughout your shift. You may wish to set up Microsoft Outlook to notify you of received messages.
    Check voice mail Check personal voice mail for important messages. This is important at the beginning of the shift when employees may call in if they are unable to come to work.
    Counsel employees Complete performance and conduct counseling as required. See IRM 1.4.18.5.3, Conduct Counseling, and IRM 1.4.18.5.4, Employee Performance.
    Escalate program issues Escalate program issues to the appropriate Operations Support (OS) analyst for research and resolution. Do not send technical program issues directly to an external analyst or to the Quality Team, EHSS Solutions Lead, etc., as this will delay the response.
    Evaluative review Review and complete documentation for interactions and telephone calls and Live Chats for each employee. You may wish to complete some each day. See IRM 1.4.18.5.4.1 , Monitoring and Reviews.
    Maintain attendance roster Record attendance and leave usage daily to help identify developing issues. When detecting a leave issue problem, initiate counseling, and document the issue.
    Monitor Aceyus reports Use this tool to manage lunches, breaks, confirm the number of assistors on the telephone and Live Chat, and review the staffing needed. Inform any obstacle to upper management and the operation's telephone system analyst that will prevent adherence to the telephone schedule. The operations telephone analyst will notify the program analyst if needed. See IRM 1.4.18.9.3.8, Aceyus Reports.
    Monitor EHSS Monitor EHSS for open Interactions/Incidents and new Contribute Knowledge Article requests. Ensure timely assignment and to resolve elevated issues from the EHSS worklist and leads worklist items. Respond to escalation emails. Ensure to return Contribute Knowledge Articles to the assistor when appropriate or submitted to the EHSS Solutions Lead (in EHSS) for consideration.
    Records management Before destroying documents, ensure IRS records are appropriately managed, retained, and archived in accordance with IRM 1.55.6.19 , Records and Information Management, series for records retention and disposition requirements. Refer to Document 12990, Records Control Schedules (RCS) for the National Archives and Records Administration (NARA) approved records disposition to prevent unauthorized and unlawful destruction of records. Refer to Document 12829, General Records Schedules (GRS), for the NARA issued disposal authorizations for temporary administrative records common to all Federal agencies.
    Reply timely to items requiring a response Receiving items requiring a response may come in meetings or more frequently by e-mail. Respond within the requested time frame, even if the response is none, NA, no comment, or negative.
    Review and share Centralized Quality Review System (CQRS) defects If you disagree with the defect charged, ensure to submit your rebuttal to the Quality Team no later than ten business days from the CQRS review date of the call. If you agree with the defect, share the review with the employee. Refer to IRM 1.4.18.5.4.8 , Centralized Quality Review System (CQRS).
    Review daily Aceyus Reports Use these tools to identify and address areas of concern, such as extended or frequent idle periods and excessive wrap times. See IRM 1.4.18.10.2 , Infrastructure Update Project (Finesse / CTIOS / IPBlue Desktop application) Reports.
    Sign BEARS requests Employees can request access to a system, have a profile unlocked, or a password reset through the Business Entitlement Access Request System (BEARS). When an employee makes a request, you will receive an e-mail notification. Signing these requests is a priority.
Weekly Duties
  1. Perform the following duties weekly:

    Weekly Duties Action
    Aged Interactions/Incidents Review aged case reports for closures or updates.
    IDRS Online Reports Services (IORS) Managers must access the Integrated Data Retrieval System (IDRS) Online Reports Services (IORS) system at IDRS Online Reports Services (IORS) on a weekly and monthly basis to perform required electronic security reviews for employees with access to the IDRS system.
    Perform auto 2787 overtime reconciliation Request, authorize, and approve funds in advance for overtime, compensation, and holiday hours worked. After working the hours, submit Form 2787-A Authorization and Report of Overtime Worked to the appropriate managers for signature. In put the report and completed no later than COB Tuesday following the end of the pay period.
    Review forecast staffing requirements Review the forecast upon receipt and daily, if necessary, to ensure adherence. Inform your department manager (DM) of any obstacles that will prevent you from meeting the schedule, such as scheduled meetings or training, or completing paper inventories.
    Review Verint in-box Review the Verint in-box to ensure all employees appear on the list of team members and calls are populating for each employee.
    Security Audit & Analysis System (SAAS) The Security Audit and Analysis System (SAAS) implement a data warehousing solution to provide on-line analytical processing of audit trail data. The system enables IRS and Treasury Inspector General for Tax Administration (TIGTA) to detect potential unauthorized access to IRS systems and will provide analysis capabilities and reporting on data for all modernized and some current processing environment applications.
    SETR records Ensure employees entered their time and Organization Function Program (OFP) code correctly into Single Entry Time Reporting (SETR). Managers are responsible for validating their employees’ SETR Time and Attendance records. Sign changes by Close of Business (COB) Friday of each pay period. Enter, final validation, and SETR signed again no later than 10:00 a.m. Local Standard Time on Monday after the pay period has closed.
Monthly Duties
  1. Perform the following duties monthly:

    Monthly Duties Action
    Create weekly/bi-weekly phone schedules Use the Forecast Staffing Requirements to create an employee phone schedule that incorporates phone, non-phone (chat and inventory), meetings, training, breaks, and lunches.
    Consider employees for career ladder promotions Promote employees in career ladder positions in the first pay period after they become minimally eligible and they are capable of satisfactorily performing at the next higher level. It is the manager's responsibility to track career ladder promotions and ensure to complete personnel actions timely. IRS Source has a link to a Career Ladder Promotion Calculator at Career Ladder Promotion Calculator to help identify when the promotion is due. Notify the employee 60 days prior to the eligibility date of the career ladder promotion if the employee is not fully successful. Place a signed copy of the documentation in the electronic Employee Performance File (eEPF) or mail to an employee in non-work status.
    Prepare annual evaluations Annual ratings must be issued monthly between October and June. The due date is determined by the last digit of the employee's social security number (SSN). Develop a listing of all team employees based on their SSNs to ensure no employee is omitted.
    Prepare progress reviews All employees must receive at least one progress review, at least 60 days before the end of the rating cycle.
Periodic Duties
  1. Perform the following duties periodically:

    Periodic Duties Action
    Correct personnel/payroll problems Promptly address any employee concerns regarding personnel or payroll. Employees may initiate an inquiry themselves or contact you for assistance. Diligently track contacts (calls or online requests through Internal Revenue Workflow Optimization, Request, and Knowledge System (IRWorks) to the ERC). Provide detailed information on the service ticket to better assist the Human Resources technician who will respond to your inquiry.
    Direct travel The Operation Support manager is responsible for directing travel, approving travel expense estimates, and the expenses incurred. Official travel must be consistent with the assignment and not for personal preference or convenience. Resolve travel questions and concerns prior to beginning a trip. See IRM 1.32.1 , IRS Local Travel Guide and IRM 1.32.11 , IRS City-to-City Travel Guide.
    Prepare commitments and self-assessments Prepare commitments at the beginning of the rating period. Keep a drop file of achievements. Prepare a self-assessment based on the Performance Management System's critical performance expectations for your mid-year and annual evaluations. Your manager will provide guidance as needed.
    Preparing for an operational review Conduct operational reviews any time during the year. Ensure record keeping is up-to-date and employee’s eEPFs and drop folders contain current documentation.
    Request vacation schedules Request vacation schedules quarterly from all employees, however, deny requests if approval would cause a severe workload interruption. See IRM 1.4.18.5.2.1, Leave Scheduling Process.
    Submit Release/Recall schedules The Operations and TSO Senior Managers will facilitate the release/recall schedule of seasonal employees.
Annual Duties
  1. Perform the following duties annually:

    Annual Duties Action
    Assign employees to a performance plan Provide employees with a copy of their performance plan, which includes the Retention Standard and CJEs, annually. Share this during Expectation Meetings. Employees must receive their CJEs within 30 days of their last annual rating. Share in an Expectations Meeting, for new employees. Ensure to sign Form 6774 , Receipt of Critical Job Elements and Fair and Equitable Treatment of Taxpayers Retention Standard, and keep in the employee's eEPF. Meet individually with leads to communicate additional expectations for them. Provide training on managerial duties so they can act for you in your absence. Place performance related documents in the eEPF Employee Performance File.
    Complete Mandatory Employee Briefings The IRS uses online delivery tools and offers mandatory briefings for managers and employees. See the Mandatory Briefings website for a list of the managers and employees’ briefings.
    Conduct Critical Job Elements (CJEs) Meeting Meet with employees annually to share your expectations. Communicating your expectations helps build trust with your workgroup and helps them work cooperatively with you and with one another. As the manager you will determine what the content of the meeting should be. Suggested topics may include: CJEs, submit leave requests, time reporting, work procedures, important deadlines, and communication channels or protocols. Ask what’s working and what should change. Solicit their ideas and let them know as the manager you value their opinions. Place a signed receipt for the CJEs in the employee's drop file, along with other conduct documentation.
  2. Telework - Managers and employees have equal responsibility for ensuring a successful telework program. Managers are responsible for understanding and following telework policies as outlined in IRM 6.800.2, Telework Program, including IRM 6.800.2.5, Preparing for Weather or Other Safety-Related Conditions. Managers should:

    • Know the rules for IRS telework employees.

    • Ensure all teleworking employees have signed Form 11386-B, IRS Telework Agreement for non-Bargaining Unit, prior to commencing telework.

    • Review all telework agreements every year.

    • Ensure employees report to their official Post of Duty (POD) (official duty station). Exclude this requirement during emergency conditions, such as building closures due to weather, pandemic, etc.

    • Certify time and attendance of teleworking employees, which includes the telework indicator in SETR and the number of telework hours routinely worked match the type of telework (Ad Hoc, Restricted Full-Time, or Telework Approved Exception) listed on the telework agreement. Also, correctly mark the telework exception code in SETR.

    • Managers must refer to IRM 6.800.2, Telework Program to obtain all telework guidelines, procedures, and manager’s responsibilities.

    • Visit the IRS Telework Portal share point site for more updated information.

Leave Administration

  1. Managers must consider the enterprise workload and staffing needs by application prior to planning, scheduling, and approving annual leave.

  2. Managers must balance the need to accomplish the work of the organization by accommodating employees who want to use leave.

    • Grant or deny annual leave depending on the workload of the unit.

    • Use sick leave according to its intended purpose.

  3. It is important to address leave issues early and consistently. A leave problem results whenever an employee fails to meet or follow the manager's expectations regarding leave.

Leave Scheduling Process
  1. Schedule employee vacations and leave in such a way as to minimize the effect on the accomplishment of the work. When there are conflicts, grant preference to employees with the most service as determined by enter on duty (EOD) date. When anticipating call volumes will be greater than usual, use discretion when granting leave.

  2. Review and approve leave using either a yearly or quarterly calendar following these general guidelines:

    1. If using a yearly calendar, request employees submit completed calendars no later than February first.

    2. If using a quarterly calendar (January – March, April – June, July – September, October – December), request employees complete the quarterly calendar 60 days before the quarter begins. Approve or deny all leave 30 days before the beginning of each quarter.

    3. Consider atypical conditions on a case-by-case basis no matter the method used.

    4. Schedule leave based on adherence.

    5. Grant up to 25% of a site’s phone assistors leave per day. This percentage includes those on Alternate Work Schedule (AWS) and Regular Day Off (RDO).

    6. Be sure to have enough employees on board so you can staff according to schedule during the holiday periods.

  3. For additional policies on leave issues, the following resources are available:

    • Office of Personnel Management (OPM) – Leave Home Page – OPM Leave Home Page

    • IRM 6.630.1, Absence and Leave

Leave Counseling
  1. Monitor leave usage frequently. Counsel employees with leave issues as problems occur.

  2. Take the following steps to address a leave problem:

    1. Leave Reminders – After recognizing a problem exists, bring the problem to the employee's attention in an informal discussion. Use a memorandum to ensure the employee understands leave guidelines as noted in the Employee Expectations document. Encourage the employee to participate in developing a solution to the problem.

    2. Memorandum for the Record – If the employee does not improve, counsel them again. In a memorandum, explain how the employee is not in compliance.

    3. Leave Restrictions – If the problem continues, discuss the situation with your DM and contact your Employee Relations (ER) specialist for guidance. A "Leave Restriction" letter may be necessary. Probationary employees are not issued Leave Restriction letters.

  3. Follow the directions of your manager and ER specialist regarding issuing any counseling memorandums.

Conduct Counseling

  1. Most employees report to work on time, adhere to office rules, and have a positive attitude. Sometimes, however, there are exceptions. On these occasions, managers must take steps to address the problems.

  2. The three rules for effective conduct counseling and documentation are to be fair, consistent, and specific. Address conduct issues immediately and document your counseling sessions.

  3. Always make sure you provide the necessary details: who, what, where, when, why, and how. Make your documentation clear and concise.

  4. To plan your counseling session, ask yourself the following questions:

    1. What is the situation? Be very specific and look for facts.

    2. What do I know about the employee?

    3. What do I hope to accomplish in this discussion?

    4. How will I open the session, ask questions, discuss follow-up plans, and conclude the discussion?

  5. The following steps may be helpful when counseling employees about their conduct:

    1. Describe the situation in detail. Use specific, observable facts to describe exactly what the employee did.

    2. Explain what the employee should have done.

    3. Refer to guidance such as Operations Expectations or Document 12011, Internal Revenue Service Ethics Handbook.

    4. Ask for the employees’ assistance. This should be very clear. For example, "I need your help in resolving this."

    5. Discuss a specific action plan for follow-up.

    6. Sign and date the documentation. The employee will also sign. The employee's signature only indicates receipt, not agreement, with the documentation. If the employee refuses to sign, annotate this on the document.

    7. Provide the employee with a copy and place the original in the employee's "drop" file.

  6. Follow the directions of your DM or ER specialist regarding the issues below:

    • Designated Duty Hours

    • Excessive Talking

    • Excessive Telephone Usage

    • Lunch and Breaks Schedules

    • Sleeping on the Job

  7. Forward employee counseling memos on conduct issues to your DM and ER specialist, when appropriate, for review prior to sharing them with employees.

  8. Remember to provide employees with a "Pat-on-the-Back" when you observe positive conduct or performance.

Employee Performance

  1. As the leader of your workgroup, you are responsible for the development of your employees. Be clear, fair, and consistent with communication. What you say, or do not say, impacts your employees' performance, which in turn impacts business results. Ensure you provide consistent communication to your employees on their performance. Employees want and need to know how they are doing so they can learn and grow.

Monitoring and Reviews
  1. As a part of the IRS Performance Management System, supervisors must continuously monitor employees' progress against critical job elements, identify deficiencies, and initiate corrective actions. Document observations throughout the performance period. This will aid you when completing the mandatory mid-year progress reviews and annual evaluations. See IRM 1.4.18.5.1.3, Monthly Duties section for evaluations and progress reviews.

  2. Employee performance while on the phone has two components: reviewing the call audio and screens, if available, through Verint and capturing review documentation in an Embedded Quality Data Collection Instrument (DCI). Evaluating an employee's performance has three components: reviewing documentation made in appropriate systems (e.g., EHSS), monitoring Live Chat conversations, and monitoring telephone calls on Verint. For additional information on the use of Verint see IRM 1.4.16.5.3.2, Contact Recording.

  3. EPSS managers conduct the following types of review:

    • Telephone reviews

    • Live Chat reviews

    • Case (paper, e-mail) reviews

    • IDRS (Security)

    • Clerical reviews (Form 3210, Acknowledgement and Follow-Up, mail receipt, distribution etc.)

    • Non-evaluative reviews

  4. Perform telephone reviews, Live Chat reviews, case reviews, and reviewing documentation for the following reasons:

    • To make an objective assessment of an employee’s performance on an ongoing basis and to ensure adequate information is available for mid-year and annual appraisals.

    • To protect the rights of customers.

    • To identify training needs.

  5. You must document all reviews in writing and shared with the employee. Focus performance reviews on effective case and call resolution according to IRM guidelines. Emphasize the importance of quality service as well as the efficiency of case work, telephone calls, and Live Chats. For telephone calls and Live Chats, managers will determine whether the handle time is appropriate to the call reviewed, considering hold time, wrap time, and talk time. Review calls and chats to assess professionalism. Always provide IRM references to assist with training needs and IRM clarification. When reviewing phone calls and Live Chats, Timeliness and Professionalism attributes are subjective; managers must consider the situation and complexity of the call when making determinations.

  6. A manager narrates the review using enough detail to support their assessment. Clearly identify to the employee, actions taken (or not taken) to accomplish the CJEs. Use Embedded Quality Review System DCI to identify the CJE for each action the employee addressed during the call. Provide examples of the employees’ original statements and possible improved statement alternatives.

  7. Perform the required monitoring and inventory case reviews each month. Department managers and operations managers must set review requirements for their call sites. Conduct a balance or mix of these reviews (telephone, Live Chats, and inventory case reviews) throughout the year relative to an employee's work assignments. When necessary, conduct side-by-side non-evaluative reviews for skill development.

    1. E-help and TSO Customer Service Section management will conduct a minimum of four telephone reviews per employee per month: two telephone reviews, one Live Chat review, and one inventory case review. Conduct an additional review for each disclosure error received. Leads may perform one of the required quality reviews per employee per month.

    2. All managers will conduct monthly reviews of all employees and document the date conducted. Employees will not be reviewed on the same date each month.

    3. If you cannot conduct a review of an employee, fill out Form 15727 , Exception from Evaluative Monitoring review waiver found in the product catalog. The front-line manager, second level manager, and employee must sign the form. Place the signed waiver in the Employee's eEPF.

    4. Retain and file review sheets in each employee's contact monitoring folder for operational reviews. Refer to Document 12990, Records Control Schedules (RCS) for records retention and disposition requirements in paper and electronic format.

  8. Evaluative telephone monitoring will focus on whether the assistor handled the call and documented the case according to IRM guidelines (e.g., provided sufficient detail in the description or used Knowledge Management to determine the correct solution). Directly link the review results to the employees’ CJEs. Use the appropriate Specialized Product Review Group (SPRG), in EQRS to record results of a review.

  9. Time frames for sharing feedback. Share evaluative records with the employee within 15 workdays of the time the supervisor becomes aware, or should have been aware, of the event which it addresses. If the employee has provided incorrect information to a taxpayer, the Employer will inform the employee as soon as possible.

    • Make every effort to share employee feedback within two to three business days from the date the manager reviews the call. This ensures the call is fresh in everyone's mind and limits the amount of time an employee could potentially continue to make the same mistake.

  10. Managers or an individual in an official acting manager capacity, must conduct evaluative reviews. Leads may provide supplemental evaluative recordation; however, the manager must share the review with the employee. Leads must sign the documentation as the reviewer and the manager must concur with and sign the review prior to sharing with the employee.

  11. Obtain the employee's signature on the Embedded Quality Review System DCI. Allow the employee to make a copy and file the original copy in the employee's contact monitoring folder. When it is time for a progress review or the employee's annual appraisal utilize EQRS to compile data for a specific period. Refer to Document 12829, General Records Schedules (GRS) for guidance on records retention and disposition of electronic Employee Personnel File (eEPF).

    • EQRS is a standardized data repository with trend analysis capabilities and reporting capabilities to use for employee evaluations.

    • Always sign and date the documentation before sharing it with the employee. Your documentation is only valid if you have signed it. The employee's signature only indicates receipt, not agreement, with the document. If the employee refuses to sign, indicate Employee Refused to Sign on the signature line.

Managers
  1. Department/Operations managers must ensure team managers conduct sufficient telephone monitoring and case reviews to provide employees with a well-documented evaluation. An EQRS Report is available for this purpose.

  2. Managers must use the approved EQRS DCI for each applicable SPRG.

  3. Develop a method for recording the pertinent facts of the call. Ensure you capture all information needed to determine if a call/case is correct or incorrect.

  4. Conduct the required evaluative reviews per month for each employee.

  5. Department/Operations managers provide monthly feedback to front line managers regarding adherence to the review requirement. This feedback addresses number of reviews conducted for each employee, type of review (phones, chat, inventory case) and types of errors identified.

Telephone/Paper Monitoring
  1. Per IRM 1.2.1.2.9, Policy Statement 1-44 (Revoked), Monitoring of Employee Telephone Conversations, since approximately 2004, the IRS has been using a telephone software system for recording interactions between IRS customer service personnel and taxpayers or their representatives.

  2. Performance monitoring is an important review within the EPSS organization. When monitoring, managers can determine whether the employee:

    • Addressed disclosure issues

    • Treated the customer with respect, courtesy, and fairness

    • Followed EHSS procedures

    • Resolved the call/case by IRM guidelines

    • Provided an accurate answer

    • Applied appropriate communication skills

Feedback and Follow-Up
  1. Managers must consistently identify problems during the monitoring/reviewing process and determine the best course of action (e.g., On-the-Job Instruction (OJI), IRM review, on-line courses, etc.).

  2. Review results may reveal strengths and weaknesses of employees and identify the need for additional managerial monitoring to evaluate employee performance. Perform managerial monitoring independently from Product Reviews. Do not use Product Review results to evaluate employees.

  3. Be sure to use Product Review data to identify trends, problem areas, and overall site quality.

Sharing Reviews
  1. Sharing monitoring results is a two-way communication. Use the available Employee Feedback Report or Verint Evaluation for this purpose. When sharing the review, managers must determine if the employee agrees with their assessment. Always ensure the employee understands the EPSS measures and goals and how they relate to the CJEs of their position description. Use the If/Then chart below if the employee agrees or disagrees.

    If an employee ... Then ...
    Agrees
    • Comment on the positive aspects of the performance.

    • Discuss areas for improvement.

    Disagrees
    • Obtain the cause of disagreement.

    • Comment on the positive aspects of the performance.

    • Discuss openly to resolve disputed issues.

    • Discuss areas for improvement.

    • Develop a plan to improve performance.

  2. Share results of the review within three workdays. Share the results as soon as possible if there is incorrect information. If you do not meet these time frames, (e.g., due to unexpected leave, etc.), notate the reason on the review sheet.

  3. Obtain the employee's acknowledgment on the designated form. Allow the employee to make a copy and file the original copy in the Employee's eEPF. Remove all taxpayer data containing an SSN or name.

  4. Management may request to download a recorded contact. Requestors must clearly state the reason for download on Form 13817, Request for Downloaded Contact. In general, requests for downloads are to retain the call for a period longer than the system retention period (60 days) or to provide a copy of the call to another party, when necessary (TIGTA, Employee Relations, etc.). Download the call when the employee disagrees over the content of the contact and the manager and employee cannot reach an agreement.

Verint
  1. Verint is a system that captures and stores incoming toll-free telephone contact with customers for the purpose of possible subsequent review; known as contact recording. It is used to perform required random reviews (performance and product) of incoming telephone contacts. Screen capture is available for 10% of all calls. When screen capture is available, it shows the case research and actions taken in online systems simultaneously with voice recording. The data is stored by employee Agent Number for a maximum of 60 days.

  2. Review the inbox for your team each week and ensure recorded calls for each employee are present. If calls for an employee actively taking calls are not present in the in box, notify your Business Application Administrator (BAA) immediately. Choose the most current calls in your in box for review. Give feedback quickly, especially if the employee gave the caller wrong information.

  3. Use the EQRS e-help/TSO Phone (SPRG) Data Collection Instrument (DCI) to prepare written recordation of all calls reviewed for evaluative purposes. The performance aspects of each tool align with the employee's performance plan. After listening to the call, complete the DCI or Verint and enter any necessary remarks. During evaluative feedback sessions, employees will be able to review the entire conversation and see their on-screen actions.

  4. If the caller says they don’t want to be recorded, the assistor must stop the recording using the Verint Agent Monitoring icon on the start task bar and select Stop Monitoring. These calls won’t be reviewed. To ensure assistors are not abusing this feature to prevent their contacts from being recorded, managers can search Verint under the "Intelliquality" field by taking the following steps:

    1. Under "Data Range" select the dates or the number of days to be searched.

    2. Under the "Contact Data Section" go to the "StopOnDemand" box and highlight StopOnDemand.

    3. Under "Site," select the desired site.

    4. Click on Search.

  5. Managers and reviewers requiring access to Verint must submit a BEARS request to access their site or the site they will be reviewing. The Business Application Administrator (BAA) in the site will approve the form and add the manager/reviewer to the Verint database. For the BAA to do this, an e-mail identifying the group number and members is necessary.

  6. Cisco Unified Intelligence Center (CUIC) contains information on each manager and assistor in a site and identifies the group to which they belong. It’s very important to update the CUIC database whenever there are changes to managers or assistors, such as if they move to a different group or leave IRS. Send an e-mail to the BAA with the name, login name, SEID, Finesse / CTIOS / IPBlue Desktop application Login Number, group number, and manager’s name to have the change implemented.

Access to Recorded Calls
  1. Employees may request access to a recorded call used for evaluative purposes and may listen to the call on official time.

  2. At an employee's request, the manager will meet within two business days to listen to and discuss a recorded call together.

Centralized Quality Review System (CQRS)
  1. The Centralized Quality Review System (CQRS) staff performs non-evaluative product reviews of e-help and TSO telephone operations. Reviews address five quality measures:

    • Customer Accuracy – Giving the correct answer with the correct resolution. "Correct" is measured by providing the customer with a correct response or resolution to the case or issue, with the necessary actions or case disposition taken. This measures accuracy from the "customer's point of view."

    • Regulatory Accuracy – Adhering to statutory/regulatory process requirements when deciding on taxpayer accounts/cases.

    • Procedural Accuracy – Adhering to non-statutory/non-regulatory internal processing requirements when deciding on taxpayer accounts/cases.

    • Professionalism – Promoting a positive image of the IRS by using effective communication techniques.

    • Timeliness – Resolving an issue in the most efficient manner using proper workload management and time utilization techniques.

  2. Perform CQRS reviews using the Specialized Product Review Group (SPRG) for e-help Telephones or TSO Telephones.

    1. Managers will receive a spreadsheet showing all reviews performed by CQRS. Managers who disagree with a defect will complete the attached rebuttal sheet and adhere to the due dates provided in the e-mail with the daily DCIs from Workforce Planning, Training and Quality (WPTQ). Ensure to forward rebuttals to CQRS timely. Find more guidance regarding rebuttals to CQRS in IRM 21.10.1.8.7, EQRS / NQRS Remarks Section.

    2. The manager will share the review with or without defects with the employee. When sharing reviews with employees it is good to have e-help Telephones or TSO Telephones Master Attribute Job Aid (MAJA) available.

Training
  1. Find EPSS training requirements on the EPSS Training SharePoint at EPSS Training SharePoint. Each site has a Training Coordinator who must complete the following:

    1. Complete the site training plan by the date set by the WPTQ analyst.

    2. Notify WPTQ analysts of any changes to the plan.

    3. Verifying all required listed courses as completed in their employees’ training history on the Integrated Talent Management (ITM) system.

  2. The WPTQ Analyst will monitor the training schedule to completion.

  3. Managers must provide training on time so EPSS assistors can do their job well and be proficient.

  4. All front-line managers must take all courses with employees. Attending the training on an annual basis will ensure you are proficient and will enable you to coach and monitor employees, handle elevated customer issues, and address problems that may develop.

Non-Evaluative or Coaching Reviews

  1. Managers, technical leads, or a skilled journey-level employee can perform non-evaluative monitoring on the following:

    • Telephone calls

    • Inventory case reviews

    • Specific issues (e.g., disclosure)

  2. The primary purpose of a non-evaluative review is to help the employee develop and enhance their job skills. Effective non-evaluative reviews foster open lines of communication between the employee, the manager, and the technical lead. This enables the manager or their lead to receive or provide employee feedback and transfer operational goals informally.

  3. Non-evaluative or coaching reviews do not contain a written rating. Share the results orally. Some documentation is appropriate to establish whether it occurred. Use EQRS or Verint to track employee development for this purpose. Have the employee initial and date the document. Allow the employee to make a copy and file the original copy in the employee's eEPF file per Employee Personal File.

Non-Evaluative Monitoring

  1. Conduct non-evaluative reviews for several reasons (e.g., to identify training needs, improve performance, etc.).

  2. Non-evaluative target reviews help focus on issues causing high error rates.

  3. When implementing major procedural revisions, non-evaluative reviews can help managers determine if there is a need for additional procedural reviews, discussion during team meetings, or additional training.

  4. Non-evaluative reviews can assist the manager and employee determine progress from training and coaching.

  5. When an employee is having difficulty dealing with a caller, non-evaluative monitoring allows the manager to assist the employee, if needed.

Side-by-Side Monitoring

  1. You can accomplish non-evaluative monitoring by utilizing periodic side-by-side reviews, when deemed appropriate, or requested by an employee. Apply this technique when circumstances merit an in-depth discussion for training purposes.

  2. You may delegate this non-evaluative review to your technical lead or an On-the-Job Instructor (OJI). Periodically, delegate this non-evaluative review to an experienced assistor to foster an inclusive environment.

EPSS Phone Certification Plan

  1. The intention of the certification plan is to provide EPSS Managers with a process to document their employees’ performance. Following the goals and objectives of the outlined plan below will provide consistency throughout the enterprise. As stated in IRM 1.4.18.4, Leadership; "Leadership involves coaching and mentoring your employees. As you identify opportunities for performance improvement, it is your role as a leader to assist employees in improving performance through coaching, mentoring, and providing timely feedback. As a leader at the IRS, you are to lead by using the balanced measures framework by considering customer satisfaction, employee satisfaction, and business results" .

  2. After completion of Recruit Training, employees will receive an On-the-Job Instructor (OJI) Period which consists of the following:

    • New employee double plugs with an experienced assistor (half of course length time recorded under OFP 990-59250).

    • Experienced assistor double plugs with the new employee while they take calls (time recorded under OFP code 750-42730 for e-help and OFP code 750-12730 for TSO).

    • On the Job Instructors (one to five ratio).

    • Certification.

  3. During the OJI period, the coach must complete at least two OJI Phone Feedback Forms for each employee and provide them to the manager. These forms identifies training deficiencies and opportunities for improvement. The coach must share each form with the employee to provide feedback on progress.

  4. After the completion of the OJI process, the manager and lead must review three calls (three calls = one attempt) for each assistor. The calls should be three different types of calls in Verint. Enter the reviews into EQRS as non-evaluative with a comment in the Remarks/Feedback section as Certification Process.

  5. A successful certification is based on the following guidelines: the assistor works independently and achieves Customer Accuracy (100%, no errors), Regulatory Accuracy (100%, no errors), and Procedural Accuracy (85%).

  6. If the assistor is unsuccessful after three attempts (a total of nine calls), the manager will develop a performance improvement plan (action plan) based on the manager’s assessment, training needs, and the employee’s feedback. If after 90 days the assistor is unsuccessful, the manager will contact the Department Manager to make them aware of the progress the assistor has made and provide any extenuating circumstances.

  7. Future attempts to certify the assistor will now be evaluative in EQRS. Monitor the employees’ progress by observation, feedback, and EQ reports. Frequent meetings and written documentation are critical at this point in providing the employees with feedback on their performance.

EPSS Inventory Case Certification Process

  1. After completion of inventory case training, employees will receive an OJI Period which will consist of:

    • Working live cases with an OJI coach available to assist with questions (half of course length time recorded under OFP Code 990-59250)

    • Coaching

    • Certification

  2. During the OJI period, the coach will be available to help assistors while working cases. The number of cases will be contingent upon the program volumes. The cases worked during the OJI period will be 100% reviewed by coaches/leads.

  3. Review each assistor’s cases, after the completion of inventory case training and OJI. The number of cases reviewed depends on workload volumes, but you will need to complete at least 10 reviews. The manager or lead will perform the review and complete the Email and Inventory Case Review Template. Managers will meet with the assistor to review the Email and Inventory Case Review Template and provide feedback.

  4. A successful certification is based on these guidelines: the assistor works cases independently and achieves an 85% overall accuracy rate.

  5. Unsuccessful Certification - If the assistor is unsuccessful after three attempts to certify, the manager will develop a performance improvement plan (action plan) based on the manager’s assessment, training needs, and the employees’ feedback. If after 90 days the assistor is unsuccessful, the manager will contact their Department Manager, make them aware of the progress the assistor has made and provide any extenuating circumstances.

  6. Future attempts to certify the assistor will need to be evaluative in EQRS. Monitor the employees’ progress by observation, feedback, and EQ reports. Frequent face-to-face meetings and written documentation are critical at this point in providing the employees with feedback on their performance.

  7. Phone/inventory case- contact ER for guidance on the proper procedures for corrective action concerning probationary and non-probationary employees. Managers should keep their Department Managers aware of the certification process and the progress of assistors.

EPSS Live Chat Assistance Certification Process

  1. The intention of the certification plan is to provide EPSS Managers with a process of documenting their employees’ performance. Following the goals and objectives of the outlined plan below will provide consistency throughout the enterprise. As stated in IRM 1.4.18.4, Leadership; leadership involves coaching and mentoring your employees. As you identify opportunities for performance improvement, it is your role as a leader to assist employees in improving performance through coaching, mentoring, and providing timely feedback. As a leader at the IRS, you are to lead using the balanced measures framework by considering customer satisfaction, employee satisfaction, and business results.

  2. After completion of Recruit Training, employees will receive an On-the-Job Instructor (OJI) Period which consists of the following:

    • New employees double plug with an experienced assistor (half of course length time recorded under OFP 990-59250).

    • Experienced assistor double plugs with new employees while they take Live Chats (time recorded under OFP code 750-36800 for e-help and TSO).

    • On the Job Instructors (one to five ratio).

    • Certification.

  3. During the OJI period the coach will complete the minimum of two OJI Live Chat Feedback Forms for each employee and provide the completed forms to the manager, to identify training deficiencies and recognize opportunities for improvement. Share the OJI Live Chat Feedback Form with the employees to provide feedback on their progress.

  4. At the completion of the OJI process, perform a review of three chats (three chats = one attempt) for each assistor and the manager/lead should perform reviews on three different types of chats in E-Gain. Enter the reviews into EQRS as non-evaluative with a comment in the Remarks/Feedback section as Certification Process.

  5. A successful certification is based on the following guidelines: the assistor works independently and achieves Customer Accuracy (100%, no errors), Regulatory Accuracy (100%, no errors), and Procedural Accuracy (85%).

  6. If the assistor is unsuccessful after three attempts (a total of nine chats) the manager will develop a performance improvement plan (action plan) based on the manager’s assessment, training needs, and the employee’s feedback. If after 90 days the assistor is unsuccessful, the manager will contact their department manager to make them aware of the progress the assistor has made and provide any extenuating circumstances.

  7. Future attempts to certify the assistor will now be evaluative in EQRS. Monitor the employees’ progress by observation, feedback, and EQ reports. Frequent meetings and written documentation are critical at this point in providing the employees with feedback on their performance.

Operational Review Overview

  1. An Operational Review is an in-depth review and analysis of a particular program or function.

  2. The Operation Support staff (analyst) conducts reviews.

Operations Support Staff Conducting Reviews

  1. Operations Support Staff (analyst) conducting reviews will:

    • Evaluate and assess

    • Identify areas to improve

    • Establish target dates for improvement

    • Identify and praise accomplishments

    • Provide a follow-up on action items

  2. The review will address:

    • Workload management practices

    • Personnel management practices

    • Administrative practices

  3. Compare the above practices to the following:

    • Mission statement

    • Policies and regulations

    • Memos of Understanding (MOUs)

    • Program letters

    • Business measures and goals

  4. Prepare a schedule of planned reviews at the beginning of each fiscal year and no later than November first. Provide the schedule with the operations manager, or director, as appropriate.

  5. Request the information needed from the manager 30 days in advance, so all information is available at the start of the review. This may include the following list of items:

    Information needed from the manager
    Aceyus reports
    Adherence reports
    Aged case listings
    Average handle time reports
    Drop Files (including meeting minutes)
    electronic Employee Performance Files (eEPF)
    Employee Survey Satisfaction results
    Engagement Plans/Activities
    Evaluation/Mid-year tracking
    Leave tracking
    Personnel Files
    Quality/Productivity/Improvement Initiatives
    Sample of closed cases
    Sample of open cases
    Security reviews
    Totally Automated Personnel System (TAPS) data
    Training Files
    Transfer reports
    Work Planning and Control (WP&C) data
  6. When reviewing a Team Manager (TM) you review a minimum of six eEPFs- a technical lead, one team clerk/management and program assistant and four assistors, if applicable. Try to review eEPFs of employees with different levels of experience. Generally, Department Managers (DM) schedule one or two eEPF reviews a month.

  7. When reviewing a DM, you review at least half of all eEPFs of those who directly report to the DM, plus samples of employees' eEPFs from teams within that department. A review of a DM may take about two weeks.

  8. When completing technical portions of the review such as the closed case reviews, obtain assistance if needed. Operations managers may also obtain assistance from the Operation Support staff to assist with department reviews.

  9. Allow enough time to perform the review, write the report, and share feedback from the final report to the manager or director as appropriate. The feedback will follow the responsibilities (i.e., leadership, employee satisfaction, customer satisfaction, business results) and specified items reviewed.

  10. Promptly document the operation review in a memorandum to the appropriate manager or department head. Include the following in the memorandum:

    • Summary of the observations (positive and negative)

    • Recommendations and action items

    • Follow-up dates

  11. Maintain a copy of the memorandum in the office files and one in the manager's eEPF. Be sure to follow up timely with the manager on action items. Document all follow-up actions.

Operation, Department or Front Line-Manager

  1. The Operational Review will cover the following:

    • Personnel management practices

    • Workload management, administrative, privacy, security, and safety practices

    • Manager's organization

  2. Review personnel management practices of maintaining electronic Employee Personnel Files (eEPF), Drop files and Personal/Training files for the following items listed below:

    Review eEPF for the following:
    Awards
    Communication including team meetings
    Critical Job Elements (CJEs) and Form 6774, "Receipt of Critical Job Elements and Fair and Equitable Treatment of Taxpayers Retention Standard"
    Employee development
    Employee satisfaction
    Evaluations
    Evaluative reviews, including content, scope, and amounts (front line manager)
    Leave administration
    Mid-year progress reviews (front line manager)
    Non-evaluative reviews and coaching
    Operation reviews (department and operations manager)
    Performance reviews (department manager)
    Poor performance handling
    Position management
    Seasonal agreements (if applicable)
    Training and OJT documentation
  3. Review Workload Management Practices for the following:

    • Quality of work performed in function (phones, chat, and inventory cases). For example, acknowledgement and follow-up of Form 3210, Document Transmittal.

    • Timeliness of work performed in function (paper)

    • Expectations for phone functions

    • Utilization of lead employee

  4. Review Administrative, Privacy, Security, and Safety Practices, including the following:

    • Time reporting

    • UNAX completed or scheduled for all employees

    • Prevention of Sexual Harassment (POSH) completed or scheduled for all employees

    • Release/Recall correctly updated

    • Rules of Conduct meetings held

    • Security reviews

    • Correctness of TAPS information

  5. Review Manager's organization effectiveness:

    • Timeliness of controlled responses

    • Effectiveness of method for managing tasks or assignments

    • Completeness, thoroughness, timeliness of reviews, projects, etc.

  6. Document all reviews in writing.

E-help Support System (EHSS) Guidelines

  1. The primary tool for documenting customer contacts is the e-help Support System (EHSS). Contacts documented as Interactions and used to capture and track information such as who is reporting the problem, the nature of the problem, and the solution to the problem (including failed solutions). This provides a consolidated and synchronized view of the customer’s contact history with EPSS.

  2. EHSS is a tailored version of HP Service Manager software. The e-help Desk, Product & Services Support, TSO, various internal policy owners, and other support personnel utilize it. The system contains:

    • Downloaded select customer data from External Customer Data Store (ECDS)

    • All electronic product types supported by the e-help Desk and TSO

    • Problem types associated with each electronic product

    • A knowledge database to guide an assistor through issue identification and resolution

    • Formal tracking and reporting of issues (providing information about the customer, problem, and resolutions -both successful and unsuccessful attempts).

    • Downloaded select customer data (Form 1099, U.S. Information Return for Calendar Year 1971 data) from Transmitter Control Database (TCB) and Special Projects database (Form 8027, Employer’s Annual Information Return of Tip Income and Allocated Tips and Form 1042-S, Foreign person’s U.S. Source Income Subject to Withholding).

  3. EHSS allows for:

    • Documented completion of issues

    • Analysis of documented issue type to improve offerings and service

    • Alternative communication methods (i.e., e-mail for external customers)

  4. The configured system has multiple web and application servers. If an application or web server fails, the system will continue to operate without interruption. If the production system fails, there is a stand-by system that is available for use. If the production system becomes non-operational, EPSS Communication will notify users.

Business Entitlement Access Request System (BEARS)

  1. BEARS is an automated way to request access to Information Technology (IT) systems and applications. It provides faster access and automates the process of re-certification annually. To access BEARS, click on the BEARS link on the IRS intranet home page under Administrative Sites. View the Online User Guides. If you have questions, call the Help Desk at 866-743-5748.

  2. Managers will ensure compliance with Federal Information Systems Management (FISMA) and IRS policy related to systems security and will ensure the timely removal of employees from IRS systems/applications when they no longer require access.

Systems Used by EPSS Assistors
  1. To provide support for electronic product users, the assistors use the following systems:

    System Definition
    E-help Support System (EHSS) The tool for customer interaction and ticketing.
    Employee User Portal (EUP) EUP is a Web hosting infrastructure. It supports an Intranet portal allowing IRS employees to access business applications and data (e.g., e-services, and Modernized e-file (MeF)). The employee must register and authenticate. The EUP communicates with back-end application systems (modernization and legacy) via Application Message and Data Access Service (AMDAS). The EUP infrastructure is located on the IRS Intranet.
    External Customer Data Store (ECDS) Use ECDS to record and monitor the information about electronic return originators, transmitters, software developers, and Intermediate Service Providers, who have applied to participate in e-file.
    Filing Information Returns Electronically (FIRE) System The FIRE system is how transmitters can file information returns electronically with the IRS.
    Information Returns Intake System (IRIS) Issuers or transmitters may use IRIS to submit Form 1099 series information returns to the IRS. Filers can use the platform to create, upload, edit, and view information, and download completed copies of 1099 series forms for distribution and verification.
    Infrastructure Update Project (Finesse / CTIOS / IPBlue Desktop application) Telephone System The method of delivery for phone calls to EPSS functions.
    Integrated Data Retrieval System (IDRS) IDRS is in Real Time processing that uses various command codes, and daily, weekly, and periodic support processing for various systems, such as Centralized Authorization File (CAF), Fact of Filing (FOF).
    Online Fillable Forms Transmitters can file Form 8809 , Application for Extension of Time to File Information Returns.
    Preparer Waiver Database (PWR) PWR database is a data input system which stores the information contained on Form 8944 , Preparer e-file Hardship Waiver Request.
    Tax Return Data Base (TRDB) TRDB contains tax return source information for electronically filed tax returns. It also contains electronically filed tax forms. It is the legal repository for all electronically filed returns for Tax Year 1998 and beyond. Beginning with Tax Year 2002, it also contains transcribed portions of paper returns. Returns filed through the Modernized e-file (MeF) system may not show on TRDB. To see them, you need to use EUP instead.
    Transmitter Control Database (TCB) The TCB contains data for transmitters/payers of information returns filed electronically.
  2. TSO assistors use various menus on the IRP Home Page system.

BEARS Roles in the Employee User Portal (EUP)
  1. Managers will determine which BEARS roles the employee will need for EUP and ensure the employees have the appropriate roles needed to perform the work in EPSS.

  2. In addition to the BEARS EUP roles, managers must ensure the employees have any other appropriate EPSS e-help and TSO related roles to perform the work.

Creating and Updating Interactions/Incidents

  1. EPSS assistors use EHSS as a tool for customer interaction and ticketing. EHSS allows EPSS to develop a complete view of a customer’s contact history. EPSS policy requires to capture each contact with the customer in a new or existing Interaction/Incident. This policy is necessary for the following reasons:

    • Provide efficient customer service.

    • The number of electronic products continues to grow.

    • Establish documented history for e-services.

  2. Efficient customer service: Interactions/Incidents are as significant to contact management as audit trails are to tax case management. If resolutions are not successful, it would be inefficient to start over with the customer to resolve the issue. You must give attention to the way we handle each contact (i.e., opening and documenting the Interaction/Incident with the caller on the line versus entering the data after the caller has hung up). We must work toward increased efficiency.

  3. Growth of electronic products: The implementation of e-services was the primary driver for the design of the e-help Desk. As e-services and e-file continue to grow, issue tracking will become increasingly important. Tracked duplicate issues or contacts made to the e-help Desk, are easy to resolve simultaneously because of the many products now available. For example: One customer can make separate contacts to resolve both an e-file issue and an e-services issue. Resolve both issues with the same contact when following up with the customer.

  4. Documented history for e-services and other new products: New products, specifically e-services, depend solely on information created from Interactions/Incidents. Documented history for e-services do not exist as it does for e-file. Capture issues in an Interaction as customers call in with problems. The documented resolutions for the Interactions/Incidents are captured in the Knowledge Management database.

Managing Your Worklist

  1. If there is an Interaction/Incident on your worklist, either work it or transfer it to a technical lead or an assistor.

  2. Follow-up to ensure the worked Interaction/Incident

  3. Once a week, you will receive the Weekly Aged Report. This allows you to ensure open cases worked. In addition, this will help you identify employees needing assistance with their assigned cases. See IRM 3.42.7.12.1, Reviewing the Worklist, for assistor instructions.

Monitoring E-mail in EHSS

  1. E-mail is an additional channel for communicating with the e-help Desk and TSO. There is a mailbox on EHSS, and an e-mail address provided to the following external customers, among others:

    • Foreign Account Taxpayer Compliance Act (FATCA)

    • States

    • Software Developers

    • Free File Fillable Forms

  2. Employees in Stakeholder Partnerships, Education and Communication (SPEC) are internal users. They send e-mail inquiries on behalf of external customers.

  3. TSO assistors utilize the e-mail function to resolve electronic filing questions and problems.

  4. Customers will receive confirmation advising them on the receipt of their email by EPSS. They are looking for an acknowledgement e-mail containing an Interaction/Incident number within 30 minutes. A contact will also come within 48 hours regarding their issue or question.

    • The e-help Desk has an internal goal of responding to the customers' e-mail within two hours of receipt.

  5. Appointing members of the workgroup to be responsible for reviewing the worklist and working e-mail cases. Review the e-mail worklist at least every hour to ensure timely worked cases. Work cases resulting from e-mail within two hours of receipt.

  6. See IRM 3.42.7.12.2, E-mail Function, for assistor instructions.

  7. Records created within e-mail systems, which meet the criteria of a federal record, are subject to the same retention periods as the paper or hard-copy versions. Therefore, retain these records electronically according to the NARA-approved disposition authority or printed and associated with the appropriate record keeping system. Refer to IRM 1.15.6, Managing Electronic Records, for guidance on managing all e-mail records in an appropriate electronic system that supports records management and litigation requirements, including the capability to identify, retrieve, and retain the records for as long as needed.

EHSS Change Control Board

  1. The mission of the Change Control Board (CCB) is to review, plan, assess, prioritize, and disposition Change Requests (CRs) for the e-help Support System (EHSS). The CCB is a committee that reviews, approves, or rejects changes impacting policy, system, and processes initiated by EHSS stakeholders. The CCB includes representatives from the e-help Desk and Technical Services Operation (TSO).

  2. Submit CRs to the CCB on Form 14507, EHSS Change Request, with adequate justification/documentation. The originator’s manager must review the request for accuracy, content, and completeness and complete the “Manager of Originator” section of the CR form. The manager will approve or disapprove the request. For a not approved CR, the manager will document the reason and return to the originator. For an approved CR, the manager will e-mail the completed CR to the CCB Coordinator and the Products and Services Support Manager.

  3. The CCB will ascertain the benefits and impacts of proposed changes. The quorum of CCB members will vote to approve/disapprove the recommendation. The CCB Chairperson will sign the approved requests, while the CCB Coordinator will maintain them. Closing steps may include giving instructions, carrying out required actions, or forwarding recommendations to the appropriate functions.

EHSS Solutions

  1. EPSS is responsible for managing the content of the solutions database. For each of the products, the e-help Desk and TSO support, they have several associated solutions. Operations Support (OS) Analysts have ownership of solutions associated with their assigned programs. The OS analyst may coordinate new solution content with the Policy Owner.

  2. Managers/leads must follow all guidance in IRM 3.42.7.10.1, Contribute Knowledge. It is critical to review Contribute Knowledge Articles, and return the request to the assistor, or submit to the Solutions Lead (in EHSS) for consideration in a timely manner.

  3. To maintain the solution database, EPSS has established Solutions Subject Matter Experts (SMEs). TSO and E-help Operations Chiefs provide SMEs identified by specialized technical skills. Analysts can solicit SMEs for assistance with solution updates that contain significant program changes.

  4. The Solutions lead is an analyst from the Program Management (PM) staff. The Solutions lead coordinates with Policy Owners to ensure products supported by EPSS have accurate and valid solutions in EHSS.

  5. The responsibilities of the Solutions SMEs include:

    • Coordinating time off assigned duties with their manager when contacted by an analyst for assistance.

    • Reviewing and editing of provided Word files for the solution.

    • Responding via reply e-mail to the analyst with the updated Word file attached.

    • Copying their manager on the e-mail.

  6. The responsibilities of the Solutions lead include:

    • Assigning contribute knowledge action for follow-up to responsible analyst.

    • Providing Word file(s) for solution(s).

    • Updating EHSS with analyst edits and requesting analyst review in EHSS.

    • Working with OS analysts and Policy Owners to certify active solutions.

    • Monitoring the status of all developed and revised solutions.

    • Returning or assigning Contribute Knowledge articles.

    • Making the final determination on whether there is a need for an update or new solution.

    • Notifying the assistor of the final disposition (e.g., rejected with reason for rejection, adopted, referred, etc.).

    • Providing quality control to ensure the input of solutions are correctly updated.

  7. New or revised solutions are necessary for various reasons:

    • A user determines EHSS does not contain an appropriate solution, or the need to revise an existing one.

    • A Policy Owner makes program changes during the year.

    • Adds a new product to those supported by EPSS.

    • Makes an internal procedural change.

  8. EPSS analyst with solution responsibility determines when an EPSS Communication associated with solution update is necessary. The analyst follows procedures found at the SERP EPSS Research Portal.

Solutions Due to Program Changes
  1. The Policy Owner must notify the program analyst when making changes to an existing product. Use a new e-help Solution Template if making a substantial number of changes. Annual IRM updates can also result in necessary changes.

  2. OS analysts may contact the policy owner of the product or service supported by a solution for additional or updated information. Contact may also occur to gain the Policy Owners’ concurrence with changes.

Solutions for New Products
  1. When adding a new product to EPSS, the Policy Owner will follow the procedures in the Customer Engagement Document and submit all necessary documents. See IRM 1.4.18.12.5, Customer Engagement for more information.

  2. Create, review, and approve new solutions with the Policy Owner who will then submit to the Solutions lead.

  3. Create new solutions as needed by following the procedures in IRM 3.42.7.10.1, Contribute Knowledge, when determining the types of calls for new products.

Infrastructure Update Project (Finesse / CTIOS / IPBlue Desktop application) Telephone System Guidelines

  1. EPSS uses the Finesse / CTIOS / IPBlue Desktop Application and software which provides monitoring capabilities, database records, and management information. The Infrastructure Update Project (IUP) TeleSet Supervisor key provides managers with access to expanded features such as:

    1. Leaving messages for employees (each site will have its own policies based on voice port availability)

    2. Monitoring agents (listening in on calls in progress)

    3. Notifying agents (notifying an agent whom you are monitoring to call you)

    4. Monitoring trunks (monitoring conversations on specific trunks)

    5. Monitoring specific IUP application groupings

    6. Determining the availability of agents

  2. The manager will have permission on Finesse / CTIOS / IPBlue Desktop to access abilities using the Supervisor button. Using the Supervisor button allows you to monitor telephone calls and trunk lines.

Infrastructure Update Project (Finesse / CTIOS / IPBlue Desktop) Assistance

  1. The system administrator/telephone analyst (SA / TA) is a valuable resource person regarding the features of the IUP system.

  2. Managers must coordinate with their SA / TA on any activity limiting the site's ability to deliver its commitment to scheduled Automated Call Distributor (ACD).

  3. The SA / TA assists on the following:

    • Information about system operations and call routing

    • Explanation of various Finesse / CTIOS / IPBlue Desktop reports

    • Identification of data availability and creating reports

    • Assessment of current call site performance

    • Networking information

    • Monitoring procedures

    • Assistance with Enterprise Telephone Data (ETD)

    • IUP equipment repair

    • Database changes

Unified Contact Center Environment (UCCE) Supervisor Features

  1. Supervisors use the Finesse / CTIOS / IPBlue Desktop TeleSet to perform the following tasks:

    1. Monitoring – Monitor a live conversation for review purposes. (Verint is the preferred method of telephone monitoring.)

    2. Notifying – Alert an employee to a problem during a live conversation.

    3. Making an agent available – Although this feature is available, managers should not place an employee into AVAILABLE state.

    4. Performing side-by side-monitoring – Utilize TEAMS and share screen/audio for monitoring.

  2. To monitor a call through Finesse / CTIOS / IPBlue Desktop application, sign on to your TeleSet and perform the following steps:

    1. Press "SUPERVISOR" key.

    2. Enter the extension of the assistor you are monitoring.

    3. Press "ENTER." The display on TeleSet LCD will show "Monitoring Extension 5555 NOTIFY."

    4. Press the "RELEASE" key to end the monitoring session.

  3. Manager monitoring. The manager must monitor available systems to see if an employee is scheduled on the phone but in an unavailable state (i.e., idle, long wrap, etc.) are on.

  4. Side-by-side monitoring, also known as "double plugging," used to review telephone calls for training purposes. Also used to improve work processes or as coaching conducted as part of a performance improvement plan. It is an excellent introduction to the job for new assistors working with experienced employees. Side-by-side monitoring is non–evaluative and not formally documented. Delegated to leads or experienced assistors.

Managing Features
  1. The manager plays a key role in maintaining the accuracy of the Finesse / CTIOS / IPBlue Desktop application database. Managers will remain in contact with their respective EPSS telephone systems analyst (SA) or headquarters telephone analyst (TA) for any changes needed

  2. E-help and TSO managers will communicate employee changes to the SA staff by updating the e-help TSO staff list. Submit changes to the SA staff using the "Employee Change Request" form located on the e-help Operation Share Point site. Complete all required fields. Complete optional fields for team moves, extension additions or deletions, and tour of duty (TOD) changes. Submit the form using the e-mail button located on the form.

  3. The site SA communicates the changes to JOC through the WPTQ analyst. Be sure to allow enough time for the SA to communicate this information to the JOC. The JOC timelines are as follows:

    • 1 - 5 Changes – Request completed within one business day

    • 6 - 25 Changes – Request completed within five business days

    • 26 - 100 Changes – Request completed within ten business days

  4. Notate any expedite requests on the change form with an explanation so the SA can coordinate the request with the WPTQ analyst.

Staffing Requirements

  1. WPTQ staff analysts for e-help and TSO develop weekly call demand projections at an enterprise level during the Work Planning phase for the fiscal year. Adjust projections to allow for seasonal changes, as well as holidays and other factors affecting call demand. The telephone system analyst will use the following factors to segment work to the various sites. Required staffing for each site is determined by taking into consideration factors such as:

    • Call volumes

    • Average handle times

    • Abandon rate

    • Slippage

  2. In generating staffing requirements for EPSS, the WPTQ analyst considers the requirements from an enterprise perspective. The adherence of each individual site to the schedule is important and impacts the performance of the e-help Desk Operation and TSO.

  3. The system administrator/telephone analyst creates a projected forecast for each site. The projected site forecast is a half-hour tool which is a Microsoft Excel spreadsheet providing staffing requirements.

  4. Management will use the half-hour forecast to create individual phone schedules for their employees. Assign the appropriate number of assistors to the telephones. Requirements for each half-hour do not consider scheduled off-phone activity (i.e., breaks, lunch, etc.).

  5. Skill Groups are the skilled groups of assistors providing service to the customer. Applications are the services we provide. The JOC uses an Intelligent Call Router to distribute calls to appropriate skill groups (agent groups) to provide services (applications) to the customer.

    • Agent Groups should not be confused with Applications. Also, Application numbers and Agent Group numbers and descriptions do not correspond one-for-one.

Adherence
  1. Use adherence to identify if the number of agents required by the e-help operation and TSO are available for the time periods specified in the schedule. Also use it to identify if the call site meets the overall telephone schedule provided to them. Measure adherence by the number of ready assistors signed on to the Finesse / CTIOS / IPBlue Desktop application system, either taking a call or involved in the completion of a call. Do not include assistors in IDLE status when adherence is determined.

  2. Managers are responsible for ensuring the required number of assistors sign on the telephones to meet adherence.

    1. Assistors will sign on when their tour of duty (TOD) begins and remain signed on until their TOD ends.

    2. Assistors must use the correct idle reason codes, when temporarily away from their work areas. They can use the following exception If-Then chart:

      If ... Then ...
      An employee is in an all-day training session They will not sign on at all.
      An employee assigned to non-phone duty at their workstations Assistors will remain signed on to their assigned extension and use reason code 3.
      An employee assigned to non-phone duties after signing on at the beginning of their TOD which will result in an absence from their workstation for remainder of their TOD They will sign off the telephone.
  3. The telephone schedule allows the team manager to monitor and maintain team adherence. Each assistor will get their own individual schedule so they know when they must be on the telephones.

  4. Individual adherence impacts the entire enterprise adherence. Recognize employees with good adherence. Promptly address employees with adherence problems.

  5. When an employee is not meeting their assigned telephone schedule, take the following steps:

    1. Remember to look at each situation individually

    2. Address the problem directly with the employee

    3. Use results of your personal observations to validate your assessment

    4. Offer guidance in how to correct the problem

  6. If the problem continues, take these steps:

    1. Prepare a written assessment of the problem

    2. Describe exactly how the employee is failing to meet a specific CJE or conduct expectation

    3. Refer to prior verbal discussions in the documentation

    4. Offer guidance in how to correct the problem

  7. Make a determination to counsel verbally or with documentation on a case-by-case basis. Factors to consider include whether the employee has displayed the behavior before and whether you observed the behavior. Failure to adhere to the schedule may be either a performance problem or a conduct problem. Contact your DM or ER specialist for guidance.

Availability and Efficiency
  1. Regardless of the type of equipment in your area, there is data to assist you in evaluating the service provided to customers and to determine the availability and efficiency of the telephone staff.

  2. Managers and systems analysts (SA) must determine if the staff is available as scheduled.

  3. Managers must ensure their employees sign onto the telephone system and take calls when scheduled. This improves level of service (LOS) and customer satisfaction.

  4. Affected Level of Service by one or more issues, such as:

    • Extended read and meet times

    • Tardiness

    • Leaving early

    • Higher than expected attrition for day (e.g., sick leave)

    • Not following scheduled breaks

    • Unauthorized breaks

    • Extended breaks or lunch periods

    • Unanticipated workload

  5. The SA must make daily real-time adjustments to the schedules based on the actual demand and actual staffing.

  6. Use the available resources to assist you in scheduling to meet peak staffing requirements.

  7. Use available data to assist in monitoring and analyzing efficiency. This includes

    • Idle and Sign on Times

    • Average Handle Time (AHT)

    • Average Wrap Time

Average Handle Time
  1. Average Handle Time (AHT) impacts scheduling assumptions. Unnecessary talk time compromises program goals and increases the number of abandoned calls. Needing additional training in conversation control could be an indicator.

  2. Identify Assistors who may be using excessively long or short times in handling calls. Monitor a few of their calls to identify problems such as:

    • Training deficiency

    • Failing to keep call brief while maintaining standards of courtesy and full service

    • Placing a call on hold during the research process when it is inappropriate, instead of arranging for a call back

    • Answering a large volume of unusually complex questions

    • Failing to provide a complete or accurate response

Average Wrap Time
  1. After releasing the customer, use wrap to complete a call Only use wrap to complete actions related to the previous call. As most systems update while on-line or on hold with the caller, use of wrap time will be minimal except in rare instances.

  2. Use wrap time or use reported wrap time to gauge if your staff is coping effectively in a telephone environment. This will assist you in determining the amount of time your staff is unavailable for calls.

  3. Possible reasons for high percentages of wrap time are:

    1. Level of training

    2. Extensive research on callbacks

    3. Excessive requirements in reporting callbacks

    4. Minor illness (e.g., headache) which caused the assistor to take short rest periods between calls

    5. Excessive conversation among assistors

    6. Excessive research

Idle Reason Codes
  1. "Idle" is a Finesse / CTIOS / IPBlue Desktop application status that assistors must use when not in "Available" or "Wrap-Up" status.

  2. When assistors are not available for incoming calls (e.g., meetings, breaks, read time, lunch, part-day training), they will go into idle to indicate their status using the appropriate reason code in IRM 3.42.7.14.1.1, Reason Codes for Idle.

  3. To ensure adherence, monitor employee statuses using the appropriate system.

  4. If an employee fails to properly use the idle reason codes, counsel them according to the guidelines in IRM 1.4.18.9.3.1, Adherence. Use reason codes solely for real time management of call volume. Do not use them for evaluating individual performance (e.g., to prepare a formal appraisal, performance indicator, or as an evaluative recordation, nor to make any comparisons, cross-references, or reconciliation with SETR entries).

Scheduling Employees on the Telephones
  1. Consider the following when you schedule telephone assignments:

    • Break/lunch schedules

    • Leave schedules

    • Training schedules

    • Team meeting schedules

    • Level of Service

  2. Attempt to assign an equal amount of telephone duty to each assistor.

  3. The Systems Analyst provides a schedule, but you can adjust the schedules during the day, if needed. TSA will notify you if you need to increase or reduce staffing based on call volume, unanticipated emergencies at another site, or other issues that may arise affecting the enterprise’s ability to adequately staff the telephones.

  4. Notify the EPSS telephone site analyst when making scheduling changes (i.e., meetings, training). Arrange meetings and training courses in advance. Evaluate unanticipated needs to determine if moving or adjusting adherence.

End of Day Procedures
  1. Assistors must sign onto Finesse / CTIOS / IPBlue Desktop application at the beginning of their TOD and remain signed on until their TOD ends. While signed onto Finesse / CTIOS / IPBlue Desktop application, assistors will use the Idle Reason Codes found in IRM 3.42.7.14.1.1, Reason Codes for Idle. Exceptions to the requirement to sign into Finesse / CTIOS / IPBlue Desktop application are as follows:

    1. Assistors in all day training sessions will not sign into Finess / CTIOS / IPBlue Desktop at all.

    2. Assistors who attend training, meetings, or other situations, which will result in an absence from their workstation at the beginning of their TOD will not sign into Finess / CTIOS / IPBlue Desktop until they are at their workstations.

    3. Assistors who report to their workstation at the beginning of their TOD, but thereafter attend training, meetings or other situations resulting in an absence from their workstations until the end of their TOD, will sign off when they leave their workstation.

  2. Managers will allow assistors to sign off Finesse / CTIOS / IPBlue Desktop application up to 12 minutes prior to the end of their shift to conduct end-of-the-day activities including completion of SETR input, etc. Managers may approve more time on an as needed basis.

  3. On rare occasions, a call may go past an assistors TOD. If this happens, the assistor will notify their manager or lead immediately. The manager or lead will determine how best to handle the call and can offer Credit, Compensatory, or Overtime (if available) to the assistor as a resolution.

Aceyus Reports
  1. Aceyus is a software program used to view reports from a server collecting call and non-call activity. Reports may show real-time or historical system data. Aceyus also supports the creation or modification of personal reports based on existing templates. You can work with Intelligent Contact Management (ICM) software reports directly from the browser on your PC.

  2. Aceyus stores multiple fields of information about every call transaction in its database. Aceyus also stores information about non-call events, such as agents remaining in the Idle state and logon times. Reports can include historical or real-time data. Historical data tells you about calls during a specific period. Real-time data will tell you what agents are doing now; in other words, it is a snapshot of the current activity. Updated real-time data is about every 15 seconds.

  3. Reports may include printed tables and charts of call activity information on specific areas of the Call Distribution System. Use reports to monitor the telephone system, agent skill group performance, and agent performance data.

  4. In Aceyus, the IRS.STND folder stores templates for filtered, edited, and grouped reports to present data for your customized personal reports. Apply views to your reports to present data with commonly used fields. Save reports in your personal folders. Only you can view the reports in your Personal folder.

  5. Each Business Operating Division (BOD) has designated report writers who can develop new Aceyus Reports and schedule reports to run upon the request of the site Telephone System Analyst (TSA).

    • Refer to the JOC Aceyus Web page CUIC Reporting for instructions concerning Aceyus Reports, training materials, and Cisco Unified Intelligence Center (CUIC) to Aceyus crosswalk with a list of available report options.

Reports

  1. Management in EPSS and product owners use reports to track and address issues. Run reports on a daily or weekly basis. There are also adhoc reports run when a customer wants specific information not provided by the regular reports.

  2. There are two types of reports used in e-help:

    1. EHSS reports give a manager case statistics on either an assistor or a product. Provide EHSS reports to managers on a weekly basis. Access them from the EPSS web site at EPSS website.

    2. Finesse / CTIOS / IPBlue Desktop application reports give managers call activity statistics on an individual assistor or workgroup.

  3. Creating the Business Object Reports (BOE) through ESAM to collect e-file application data and assist with workload management.

  4. Reports are indicators of an individual's performance but not used alone for evaluative purposes. Use reports to determine the need for further monitoring and assistance.

EHSS Reports

  1. The following reports are available in EHSS:

    Report Definition
    Closed Interactions with Additional E-mail Response Report Shows the e-mail responses previously closed however, the customer is responding to the closed e-mail.
    Open Aged Incident by Provider Group Report (Telephone) Shows the number of Incidents over seven days old assigned to a provider group.
    Open Aged Incident Report Same as open aged Interactions, only will show open Incident.
    Open Aged Interaction Report Shows all open Interactions and how long they have been open by an assistor or provider group.
    Open/Closed Incident Report (Telephone Report) Same as open and closed Interaction report only will show the open/closed Incident.
    Open/Closed Interaction Report Shows all open and closed Interactions by Site and Assistor. Open cases still assigned to the assistor will also show in the Open Age Interaction Report. The closed cases are those opened and closed within the week.
    Product/Problem Type (Telephone Report) Shows the number of Interactions opened under each Product broken down by Problem Type.
  2. EHSS also provides a list of Dashboard Reports providing a real time look at the system. It allows the user to see an overview and the functionality to drill down to a particular Interaction or Incident. Below is a list of reports:

    Dashboard Report Definition
    EPSS Open Inventory Report (Paper) Is for each site and TSO. It shows all open paper cases. You can export this report to Excel.
    Inventory by OFP and Problem Type Report (Paper) Shows the weekly inventory counts for each OFP (Product) and its related sub program (Problem Type). It will show the Receipts, Closures, Ending Inventory, Aged Incidents, Rolling Inventory, and the Average Days to Close.
    Inventory by OFP Report (Paper) Shows the weekly inventory counts for each OFP (Product). It will show the Receipts, Closures, Ending Inventory, Aged Incidents, Rolling Inventory, and the Average Days to Close. It’s used to report volumes to Batch/Block Tracking System (BBTS).
    Open E-mail Interactions Report by Provider Group Chart Shows the open e-mail Interactions by provider group. The user can link into any provider group by clicking within the chart/graph to see the details of the case.
    Product Report - Weekly/Cumulative Chart This chart/graph shows the Interactions open for the week (last seven days) and year to date. The user can link it to any section of the chart for more details. Hover over a section of the chart to see the volume.
    Provider Group Aged Incidents Report (Telephone) This chart/graph shows the aged Incidents by provider group. The user can link it to any section of the chart for more details. Hover over a section of the chart to see the volume.
    Resolved on First Contact Report Shows a resolved Interaction on first contact. It allows the user to link to the Interaction and can exported to Excel.
    Weekly Aged Interaction Report by Provider Groups Chart Shows the number of aged Interactions by person and provider group. It allows the user to link into the aged Interaction case or export to Excel.
    Year to Date (YTD) Source Report Shows the source used to open all Interactions. It shows the Business Unit, Provider Group, Product, Problem Type, date opened and date closed. It can export to Excel.
  3. Managers will review each report to determine organization and team goals met. Determine reason aged cases are open for more than seven days. If there is no valid reason for the open case, managers will discuss it with the assistor. Instruct employees not to use any products marked "Inactive" on the product report.

Infrastructure Update Project (Finesse / CTIOS / IPBlue Desktop Application) Reports

  1. Team managers use Finesse / CTIOS / IPBlue Desktop application activity reports to determine the status of telephone activity. There is an employee snapshot report weekly.

  2. The EPSS telephone systems analysts (SA) runs these reports and automatically schedules them for delivery via e-mail or server. The analyst has the capability of running adhoc reports for various timelines or for a specific type of data. If you need an additional report, contact the analyst to have the data pulled from the Finesse / CTIOS / IPBlue Desktop application system.

  3. Reports are a tool managers can use to identify areas where the team members excel (e.g., adherence, efficient talk time, and minimal use of wrap time) and areas needing improvement (e.g., adherence and improper use of idle reason codes, etc.). Use these reports as a diagnostic tool to support your personal observations.

    • Managers cannot share the Finesse / CTIOS / IPBlue Desktop application report information with employees because the report may suggest a production quota or goal on employees.

    • Managers can use the Finesse / CTIOS / IPBlue Desktop application reports as an indicator to locate areas needing additional monitoring. In conjunction with your observation use the reports as an indicator of time (e.g., I have not seen you since... I noticed you were away from your desk while in wrap).

  4. All sites have standardized reports. The employee snapshot report includes the following reports.

    1. Agent Performance Summary by Team Report – Shows general call activity for all agents signed on to the system during a specified period.

    2. Agent Events Detail Report – Shows events statistics based on Extension groupings.

    3. Agent Performance Detail by Agent Group New Work Time - 707 Report – Shows performance statistics based on Agent Group 707 groupings.

    4. Excessive Reason Code Report – Shows agents in idle codes for an excessive amount of time. It uses the Agent Idle view and is available by daily intervals.

    5. CE10 Outbound Agent Detail by Team Report – Shows all outbound calls dialed, grouped by Team.

    6. Messages Detail by Team Report – Shows message statistics based on Team groupings.

    7. Sign-On Idle Profile by Team Report – Shows sign on/off and idle statistics based on Team groupings.

EHSS Business Continuance and Disaster Recovery

  1. In the event of a disaster or other event interrupting the service of the e-help Desk or TSO, use the following strategy to ensure the business continues.

  2. Scheduled Interruption of Service:

    1. The site manager will notify the Operations Support senior manager, e-help Desk or TSO senior manager, and telephone analyst by e-mail at least 48 hours before the interruption begins. List the reason for the request, the desired start time, and the duration of the interruption.

    2. The e-help Desk or TSO senior manager will notify all site managers.

    3. The telephone analyst will contact JOC if there is a routing change needed.

    4. The receiving site manager will reallocate resources in anticipation of the increased call volume(s), if applicable.

  3. Unscheduled Interruption of Service (Site Recognized):

    1. The site manager or a selected person will notify the Operations Support senior manager, e-help Desk or TSO senior manager, and telephone analyst by telephone. Provide as much information as possible about the disruption.

    2. The e-help Desk or TSO senior manager will notify their site managers.

    3. The telephone analyst will contact the JOC if there a routing change needed..

    4. The receiving site manager will reallocate resources in anticipation of the increased call volume(s), if applicable.

  4. Unscheduled Interruption of Service (JOC Recognized):

    1. The JOC will enable the current e-help disaster closure matrix.

    2. The receiving site manager will reallocate resources in anticipation of the increased call volume(s).

  5. Distribute among at least two sites, all e-help applications and TSO (Applications 806, 811, 812, 813, 814, 815, 816 and 819). There is no specified back-up site. If the Andover site becomes compromised, operations will fail over to the Austin site for suitability.(Currently TSO does not have an alternate or fail-over site.)

  6. When EHSS, e-services, FIRE or one of the other systems used by the e-help Desk and TSO are experiencing a problem or outage the manager/lead will report the problem by submitting an e-mail to the appropriate personnel. Refer to the Reporting System Issues Job Aid for the required actions. The job aid is located on the EPSS SERP Research Portal Resources - EPSS Research Portal. Assistors will manually record all data during the outage. See IRM 3.42.7.17.2.1, System Downtime Procedures

Miscellaneous Procedures

  1. Included in this section are various miscellaneous managerial functional responsibilities.

Organization, Function, and Program (OFP) Codes

  1. Employees record Organization, Function, and Program (OFP) codes in SETR to identify work IRS employees perform daily.

    1. Organization Code – A five-digit code used to describe where (e.g., Document Perfection or Input Correction) the performed work is. In EPSS, the first and second digits identify the operation, the third digit identifies the department, and the fourth and fifth digits identify the team.

    2. Function Code – A three-digit code used to describe what the e-help assistor does.

    3. Program – A five-digit code used to describe the program (e.g., Form 8453, EFTPS) worked.

  2. OFP codes have various uses including the preparation of work plans and work schedules. For this reason, it is important that reported information is consistent and accurate. Managers can verify correct reporting by accessing SETR reports. Find a complete list of all OFP codes at OFP Codes, "Organization Function Program (OFP) Code" .

  3. Managers must ensure employees use the correct code when working telephones, e-mail, paper, and call backs. These codes can be found in the TSO OFP Code Desk Guide, located on the EPSS SERP Research Portal, IRM 3.42.7-1, Organization, Function, and Program (OFP) Codes (Phones and e-mail), and IRM 3.42.7-2, e-help Organization, Function, and Program (OFP) Codes (Paper), and provide a breakdown of each codes' function, program, and title.

  4. It is critical to communicate the importance of tracking and reporting time accurately. When making assignments, limit frequent program switching, whenever possible, to help employees record time accurately.

Subscribing to QuickAlerts

  1. QuickAlerts is a free, online service disseminating mass "e-file" messages, within seconds, to all "subscribed" individual and business e-file software developers, transmitters, and authorized e-file providers.

  2. Quick Alerts also provide e-file information to assist employees in their job performance and enhance the filing season.

  3. There are four categories the assistor should subscribe to:

    • Alerts – Processing delays, programming issues, changes to any filing season procedure.

    • General Notifications – Seminars, Conferences, e-file publication changes.

    • General IRS e-file Service Center Messages – IRS e-file program updates, general information, service center maintenance schedules, IRS e-file help Desk phone numbers and more.

    • Technical - Updates on Schema Information and Software (ATS) testing.

  4. As a manager you will ensure all new employees subscribe to QuickAlerts and verify all returning seasonal employees still have a subscription.

EPSS Communications

  1. EPSS Communications are to keep EPSS employees informed of the many policies and procedural changes impacting IRS electronic products such as:

    • IRM updates

    • New procedures or information impacting the e-help Desk and or TSO

    • Solutions

    • Site Closures

    • Programming changes

    • System/application changes

  2. To request an EPSS Communication, we send pertinent information to the designated EPSS Operations Support analyst with a courtesy copy to the back-up analyst. For example, send communication related to software testing to the program analyst assigned to that program.

  3. To maintain quality and readability of communications, all originators, reviewers, and approvers of EPSS communications must follow the guidance in the "EPSS Communication Job Aid" located on the EPSS SERP Research Portal Resources - EPSS Research Portal.

  4. Designated personnel (as outlined in the EPSS Communication Request Job Aid) will issue the communication from the *EPSS mailbox.

  5. EPSS Communications distributed to EPSS employees only. A courtesy copy sent to Centralized Quality Review System (CQRS) for review purposes, and SERP for posting to the EPSS SERP Research Portal.

  6. As a manager you will ensure to add all new employees to the appropriate EPSS email distribution list and remove employees leaving EPSS. E-mail requests to add or delete employees to the EPSS Operations Support management and program assistant.

Personally Identifiable Information (PII)

  1. You must protect Personally Identifiable Information (PII), as defined in IRM 10.5.1.2.3, Personally Identifiable Information (PII), and sensitive but unclassified (SBU) data, as defined in IRM 10.5.1.2.2, Sensitive But Unclassified (SBU) Data. This includes personal and tax information. See Personally Identifiable Information for a more detailed definition.

  2. The protection of information is of vital concern to the IRS; make every effort to protect it. Ensure you and your employees review your electronic files and paper holdings for this type of information. Verify you have only PII in your possession you have a "need to know" .

  3. You and your employees must follow proper procedures for safeguarding PII you have in your immediate possession. You must encrypt SBU data, including PII and tax information, whether in email or on computer hard drives or transferred to CD-ROMs, jump drives, or other portable media. The IT4U Icon on every IRS computer has step-by-step guidance on methods of Encryption. See IT4U.

  4. Report lost or stolen laptop or other electronic devices within one hour to:

    • Your manager

    • Office of Privacy, Governmental Liaison and Disclosure (PGLD) Incident Management (IM) Office

    • The Computer Security Incident Response Center (CSIRC) at 240-613-3606

    • Treasury Inspector General for Tax Administration (TIGTA) at 800-366-4484

    The timely reporting of all information losses or thefts to CSIRC and TIGTA is critical to ensure any investigation needed and recovery initiated quickly. This can decrease the possibility of compromised information used to perpetrate identity theft or other forms of fraud.
  5. Managers are responsible for following and ensuring employees adhere to the Clean Desk Policy, as outlined in IRM 10.5.1.5.1., Clean Desk Policy. Managers must be continually alert and proactive in protecting Sensitive But Unclassified data (including PII and tax information). Managers must secure and lock all sensitive employee personnel taxpayer data in cabinets or drawers.

  6. Find additional information on how to protect PII on the Disclosure and Privacy Knowledge Base Site Disclosure and Privacy Knowledge Base.

Customer Engagement

  1. While EPSS supports external customers, its relationships with internal customers are also critical. Customer Engagement relates to how EPSS conducts business with these customers. Policy owners (i.e., organizations within the IRS and other government agencies) contact EPSS to support their products or programs. Use Form 13764, EPSS Customer Engagement Request Form, to initiate this process. This document serves as the basis for an initial meeting with EPSS to discuss the project and tailor support to meet the needs of the business organization.

Business Requirements
  1. The success of the support provided by EPSS is largely dependent upon the commitment of the policy owner to provide quality service and customer satisfaction. The business must provide the following:

    • Completed Form 13764, EPSS Customer Engagement Request Form.

    • Approved Memorandum of Understanding (MOU) outlining business, funding, and training agreements.

    • Completed solution documents (also known as Knowledge Management (KM) articles) in electronic format within 60 days of EPSS support start date. Solutions must provide instructions on how to resolve customer issues. Policy Owners must approve all new solutions and participate in the continuous solutions update process.

    • Staff (a primary and secondary contact) to work on all Level 3 Incidents assigned to their respective business provider group. Assign all business analysts to a Provider Group. Assign to this group, Incidents requiring a business response. Analysts must log in to EHSS daily to work on any cases assigned. If the Incident remains open, EHSS will automatically send an e-mail to the analyst’s manager every two hours until the case is assigned.

    • EPSS clearance on all Unified Work Requests (UWR) related to products supported by the e-help Desk and TSO. Program Management (PM) must review all UWRs and field changes for FIRE, Automated Magnetic Media Processing System (AMMPS), Information Return Project (IRP) Homepage, etc., prior to submission. You must include the PM Analyst in pre-coordination meetings.

  2. EPSS support includes the following:

    • Business requirements consultation

    • Professionally trained staff committed to timely resolution of customer issues

    • Toll-free technical support number (e-help Desk 866-255-0654, Affordable Care Act (ACA) and Information Returns Intake System (IRIS) product line 866-937-4130, or TSO 866-455-7438)

    • Technical support number for international callers (e-help Desk 512-416-7750 or TSO 304–263–8700)

    • E-mail support, if appropriate

    • EHSS training for policy owners (IRM 1.4.18.5.4.9, Training)

    • Weekly call volume and Interaction/Incident reporting (IRM 1.4.18.11, EHSS Business Continuance and Disaster Recovery)

    • Annual Filing Season Readiness Workshop

  3. Policy owners will contact EPSS headquarters analysts with all issues regarding product support. They should not go directly to the EPSS sites to initiate or change support. Find information under the EPSS Customer Engagement Request Form on the EPSS web site at EPSS website.

Training Requirements
  1. A highly trained workforce is an EPSS priority. As such, products need appropriate supporting training material. The training will cover system functionality, and a review of the solutions added to the EHSS database for Interaction/Incident research and documentation. The Policy Owner (business) must provide:

    • Formal training material during the project planning phase. Obtain guidance for the development of training material from Learning and Education or the EPSS Workforce Planning, Training, and Quality Section.

    • Just-in-time classroom training for EPSS employees prior to product deployment. Provide logins and passwords as needed.

    • On-site expert(s) for two to four weeks after the product "go-live" date.

    • Annual filing season’s readiness updates and training material will be due at a timeframe agreed upon by WPTQ and Operations. The Workforce Planning, Training, and Quality Section or the Technology Design and Support center will send requests for updates for course development.

Funding Requirements
  1. Policy Owners must provide funding reimbursement to EPSS for new products or services, increasing e-help Desk/TSO support. Reimbursement amounts calculated by the FTE expended to provide direct support, overhead, and training hours. Special reporting and programming may require additional funding.

The Process
  1. The average lead time for EPSS is six months for the following tasks (these tasks may be handled concurrently):

    • Telephone Scripting

    • Solutions Development

    • Technical Support Staffing Analysis

    • Training Development and Delivery

  2. To begin this process, take the following steps:

    1. The Policy Owner will complete Form 13764, EPSS Customer Engagement Request Form, and send it to the designated EPSS staff members.

    2. EPSS will review the request and contact the business for a project planning meeting, usually within 10 business days. The meeting will serve as a forum to discuss help desk services, product details, resources, and expected delivery dates.

    3. EPSS will develop a project plan detailing completed tasks prior to the support start date.

    4. A MOU will be prepared which outlines the business, training, and funding agreements between EPSS and the Policy Owner. You must approve the MOU before the EPSS support start date.

  3. IRM 3.42.7, EPSS Help Desk Support, provides instructions for assistors at e-help Desk sites. Business analysts responsible for the product will also use this IRM for procedures.

Discovered Remittance

  1. Immediately take remittances found in the work area to the unit manager. The Manager/Coordinator will immediately record the remittance daily on Form 4287, Record of Discovered Remittances log.

  2. See IRM 3.8.46, Discovered Remittance, for more information on handling Discovered Remittances.

Guidance for Creation and Maintenance of Job Aids/Desk Guides

  1. A Job Aid/Desk Guide is a technical support tool designed to support a business need such as:

    • Documenting an internal procedure for processing paper and electronic inventories.

    • Improving quality results.

    • Improving program efficiency.

  2. The originator of the job aid/desk guide must work with the analyst and program owner and complete the following actions:

    • Review accuracy of procedures. Ensure there is no contradiction of existing procedures, processes, or laws.

    • Receive approval from the responsible IRM author and Operation Chief.

    • Update simultaneously with the submission of an IRM Procedural Update (IPU).

    • Revise timely with technical updates for training and peak season.

    • Post to a central location. Examples include EPSS SERP Research Portal or Shared Drive.

  3. Learning and Education (L&E) will incorporate approved job aids/desk guides into existing and new training material.

eGain Live Chat System Guidelines

  1. EPSS uses the eGain Application, which provides monitoring capabilities, database records, and management information.

  2. The eGain Supervisor Console allows managers to:

    • Monitor the workload and service level adherence of various agent groups and assistors

    • Determine the availability of agents

    • Track assistor performance, including viewing active and complete chat sessions

    • Provide guidance and assistance by joining active chat sessions

  3. The eGain Reports Console provides analysts and supervisors with access, creating reports to view information about agent and service level performance. Users have access to the following data:

    • Agent Performance Reports

    • Knowledge Base Performance Reports

    • Service Level Performance Reports

    • Workforce Scheduling Reports

  4. To obtain access to the eGain Supervisor Console and the eGain Reports Console, submit a BEARS request for PROD USER EPSS SUPERVISOR (EGAIN SOLVE). Requests should include name, position, and SEID.

  5. System Administrators (SAs) use eGain Admin Console to:

    • Add/delete/modify agent groups, knowledge articles, and users

    • Re-skill assistors to agent groups

    • Configure organizational settings

    • Manage eGain user profiles and permissions

  6. Secure access to the eGain Admin Console application by submitting a BEARS request for PROD ADMIN EGAIN DEPT (EGAIN SOLVE). Requests should include business unit, name, and SEID.

  7. SAs also manage the content in the EPSS Chatbot. They have access to the eGain Knowledge Base Console to manage knowledge articles, quick responses and links, and communication templates.

  8. Secure access to the eGain Knowledge Base Console by submitting a BEARS request for PROD USER EPSS AUTHOR (EGAIN SOLVE). Requests should include name, position, and SEID.