- 1.4.18.8 Operational Review Overview
- 1.4.18.9 e-help Support System (EHSS) Guidelines
- 1.4.18.10 Aspect Telephone System Guidelines
- 1.4.18.11 Reports
- 1.4.18.12 EHSS Business Continuance and Disaster Recovery
- 1.4.18.13 Miscellaneous Procedures
- Exhibit 1.4.18-1 e-help Site Hours Requirement Forecast
-
The Operational Review should cover the following:
-
Personnel management practices
-
Workload management practices Administrative, security, safety practices
-
Manager's organization
-
-
Review personnel management practices of maintaining Employee Personnel Files (EPF), Drop files and Personal/Training files for the following:
-
Critical Job Elements (CJEs) and Performance Plan Receipt (Form 6774)
-
Seasonal agreements (if applicable)
-
Training and OJT documentation
-
Evaluative reviews, including content, scope and amounts (Front line manager)
-
Mid-year progress reviews (Front line manager)
-
Performance reviews (Department manager)
-
Operation reviews (Department and Operations manager)
-
Evaluations
-
Poor performance handling
-
Awards
-
Non-evaluative reviews and coaching
-
Position management
-
Leave administration
-
Employee development
-
Communication including team meetings
-
Employee satisfaction
-
-
Review Workload Management Practices for the following:
Note:
All reviews must be documented in writing.
-
Quality of work performed in function (phones and paper). For example, acknowledgement and follow-up of Form 3210.
-
Timeliness of work performed in function (paper)
-
Expectations for phone functions
-
Utilization of lead employee
-
-
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
-
-
Review Manager's organization effectiveness:
-
Timeliness of controlled responses
-
Effectiveness of method for managing tasks or assignments
-
Completeness, thoroughness, timeliness of reviews, projects, etc.
-
-
EHSS utilizes the PeopleSoft Customer Relations Management (CRM) Support Application Version 8.8. It is utilized by e-help Desk locations, e-help Level 2, EMS Level 2, IRB, various internal policy owners, and other support personnel. The system contains:
-
Downloaded select customer data from TPDS
-
All electronic products supported by the e-help Desk and Information Returns Branch
-
Problem types associated with each electronic product
-
A knowledge database which guides an assistor through issue identification and resolution
-
Formal tracking and reporting of issues (which includes information about the customer, problem, and resolutions (both successful and unsuccessful attempts)
-
Downloaded select customer data from Transmitter Control Database (TCB) (Forms 1099 data) and Special Projects database (Forms 8027 and Forms 1042-S)
-
-
EHSS allows for:
-
Committed timely completion of issues
-
Analysis of documented issue type in order to improve offerings and service
-
Alternative communication methods (i.e., e-mail through ERMS for external customers)
-
-
There are four physical servers in the production environment:
-
Two physical servers each have a logical web server and an application server.
-
One physical server has a logical application server.
-
One physical server has a logical database server.
-
-
The embedded BEA Tuxedo Server Software load balances the work among the three logical application servers. Automatic load balancing between the web portals is employed through the use of F5 load balancer located in Martinsburg.
-
There are two physical servers in the development and test environment. One contains the logical web servers and application servers, and the other is a database server.
-
Contingency plans have been created for disaster recovery and fail over.
-
The system is configured with multiple web and application servers. If an application or web server fails, the system will continue to operate without interruption.
-
Online 5081 is an automated way to request access to Information Technology (IT) systems and applications. It gives faster access and automates the process of annual re-certification. To use Online 5081, click on the OL5081 link: https://ol5081.enterprise.irs.gov. View the Online 5081 Quick Reference Guides, Tutorials, User Guides and Re-certification Reference. If you have questions, try the Online 5081 FAQs or call the Help Desk at 1-866-743-5748.
-
To log into EHSS, an Online 5081 must be completed to get a user ID and password. Ensure your employees have taken the necessary actions. You must approve the employee(s) 5081. Refer to the Online 5081 Manager User Guide on the Online 5081 web site for detailed steps.
-
Refer to IRM 3.42.7.5, Introduction to e-help Support, for detailed instructions for navigating in EHSS.
-
To provide support to electronic product users, the assistors use the following systems:
-
e-help Support System (EHSS) – EHSS uses the PeopleSoft Customer Relationship Management (CRM) Support Version 8.8 Application as the tool for customer interaction and ticketing.
-
Aspect Telephone System – The delivery of calls to the e-help Desk is done using the Aspect Telephone System.
-
Control-D/WebAccess Server - This system accesses reports via the Internet. It uses your Web browser to view reports using viewers, filters, and indexing capabilities.
-
Electronic Management System (EMS) – EMS provides protocol translation, telecommunication structure, security, and data management support for electronic commerce, including e-filing of tax returns.
-
ELF 15 Automated Reporting System (EARS) – EARS is a report repository used by e-help Desk managers. EARS receives and stores data FTP'd from ELF15, PAT15, ETD68 and PAT 68 Unisys runs (electronic filing) and displays data in a report format to a user's workstation (IMF only).
-
Filing Information Returns Electronically (FIRE) - The FIRE system is the means by which transmitters can send information returns electronically to the IRS. It is an internet based system.
-
Integrated Data Retrieval System (IDRS) – IDRS is Real Time processing that uses various Command Codes, and daily, weekly, and periodic support processing for various systems (e.g., Centralized Authorization File (CAF), Fact of Filing (FOF)).
-
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 and are accessed through EUP.
-
Third Party Data Store (TPDS) – TPDS is used 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.
-
Employee User Portal (EUP) – The EUP supports an Intranet portal that allows IRS employees to access business applications and data (e.g., Integrated Financial Services (IFS), e-services, MeF, and Customer Account Data Engine - Individual (CADE-I) in the future). Employees registration and authentication is required, which is supported by Enterprise Directory and Authentication Service (EDAS). The EUP consists of Web and Web Application Server platforms and Firewall/Load Balancer equipment. The EUP communicates with back-end Application systems (modernization and legacy) via Application Message and Data Access Service (AMDAS). The EUP infrastructure is located at MCC.
-
Transmitter Control Database (TCB)– The TCB contains data for transmitters/payers of information returns filed magnetically or electronically.
-
-
Managers must ensure that employees have the appropriate EUP roles needed to perform the work on the e-help Desk:
Figure 1.4.18-2
Roles System Comments AASU ESRV Approve Suitability Note:
Only for Assistors trained on suitability
AERA ESRV Enter and Revise e-file Application AESD ESRV Enter Suitability Status and supporting documentation Note:
Only for Assistors trained on suitability
AUSD ESRV Update Suitability Status and supporting documentation Note:
Only for Assistors trained on suitability
AVEA ESRV View e-file Application DEIS ESRV Enter and revise existing Disclosure Authorizations DRIS ESRV Generate DA Reports EVRP ESRV View EAR reports for tracking purposes ICMCU ESRV Update and maintain customer, contacts and addresses within PeopleSoft MADM ESRV View and revise a TIN-Matching Application PUPA ESRV Update PTIN Application PVPA ESRV View PTIN Application RURD ESRV Update registered user records TDAU ESRV Assist IVES Customers with their application links Note:
In OL 5081 Special Instructions notate: "e-help Desk Assistor and needs this role to support the IVES project."
TDUS ESRV Enter and revise transcript requests. Also view transaction history. MEF BOE BUSINESS OBJECTS USER GROUP PROD (BUSINESS OBJECTS ENTERPRISE (BOE) SERVER FARM) Business Objects Enterprise (BOE) Allows user to pull report from the MeF riled returns. Needed to resolve From 8453 Binary Attachments. MEFHLP MEF Needed for testing returns. MEFHLP_PR MEF Needed for live returns. A2A MEF Automated System Enrollment (A2A System Enrollment) -
In addition to the above EUP roles, managers must ensure employees have these appropriate roles as well:
Figure 1.4.18-3
Roles System Comments (Site) Control– D Web CTDWA Control D Web Access Note:
In 5081 Special Instructions notate the specific ORG Code and RACF Security Group for site.
OIRSC Control–D Web CTDWA Needed for Assistors working Form 1041 e-filed returns. Note:
In 5081 Special Instructions Notate: ORG Code: 36000–OG; RACF Security Group: B9INCOR
ANSC-ELF USERS EARS 1544 Database (ANSC and KSCS) EARS-AUIRSC EARS 1544 Database (PSC and AUS) EARS-TCC EARS 1544 Database (FSC) E-HELP DESK Version 8.8 EHSS e-help Support System Note:
In 5081 Special Instructions notate which team employee needs to be added.
Example:
Add to Austin Assistors 2
EMS HELP DESK EMS Electronic Management System IDRS–(SITE) IDRS Integrated Data Retrieval System Note:
In 5081 Special Instruction notate the IDRS team number. If employee already has an active IDRS access then the security representative for the team can make the change on IDRS.
-
EPSS assistors use EHSS as a tool for customer interaction and ticketing. EHSS allows e-help, and IRB to develop a complete view of a customer’s contact history with the Desk. e-help Desk policy requires that each contact with the customer be captured in a new or existing e-case. IRB assistors are not required to create e-cases for tax law inquiries. See IRM 21.3.11.7.1, Escalation Path for Assistance . This policy is necessary for the following reasons:
-
Efficient customer service can be provided.
-
The number of electronic products continues to grow.
-
Documented history for e-services must be established.
-
-
Efficient customer service: e-cases 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. Attention must be given to the way we handle each contact (i.e., opening and documenting the e-case with the caller on the line versus entering the data after the caller has hung up). We must work toward increased efficiency.
-
Growth of electronic products: The implementation of e-services was a 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. Because of the many products that are now available, duplicate issues/contacts can be made to the e-help Desk that, if tracked, can be resolved simultaneously. For example: One customer can make separate contacts to resolve both an e-file issue and an e-services issue. If follow-up with the customer is required, both issues can be resolved with the same contact.
-
Documented History for e-services and other new products: New products, specifically e-services, depend solely on information created from e-cases. Documented history for e-services does not exist as it does for e-file. As customers call in with problems, the issues are captured in e-cases. The documented resolutions for the e-cases are captured in the Solutions database.
-
e-cases are an integral part of the EPSS. Prior to the implementation of EHSS, there was no systemic way to record, track, and identify problems and trends for both e-file and e-services. We must continue to strive to adhere to the policy of capturing each contact with the customer in a new or existing e-case.
-
Review your own worklist at least once an hour. If there is an e-case on your worklist, either work it or transfer it to a lead or an assistor.
-
Follow-up to ensure that the e-case has been worked. This can be done by leaving the e-case on your worklist when it is reassigned so that you can monitor it. Another option is to make yourself an Interested Party so that you will know when action is taken on the case.
-
Once a week, you will receive the Weekly Aged e-case Report. This will allow you to ensure open cases are being worked. In addition, this will help you identify employees needing assistance with their assigned e-cases. See IRM 3.42.7.5.5, Reviewing the Worklist, for assistor instructions.
-
ERMS is an additional channel for communicating with the e-help Desk and IRB. A mailbox has been created on EHSS and the e-mail address given to the following external customers, among others:
-
States
-
Software Developers
-
Gold Card Service members
-
Small Tax Exempt Organizations (990N e-Postcard e-mails)
Note:
See
IRM 3.42.7.8.1,After Hours Support for Gold Card Service Customers
-
-
Employees in Stakeholder Partnerships, Education and Communication (SPEC) are internal users. They send e-mail inquiries on behalf of external customers. The e-help Level 2 assistors also use ERMS.
-
IRB assistors utilize ERMS system to resolve tax law or electronic filing questions and problems.
-
When the customer sends an e-mail, confirmation is sent advising them that their e-mail has been received by the e-help Desk. They are advised to look for an acknowledgement e-mail containing an e-case number in their Secure Object Repository (SOR) within 30 minutes. The customer is advised that they will be contacted within 48 hours regarding their issue or question.
Reminder:
The e-help Desk has an internal goal of responding to the customers' e-mail within 2 hours of receipt.
-
Appoint members of the workgroup to be responsible for reviewing the worklist and working ERMS e-cases. Review the ERMS worklist at least every hour to ensure that e-cases are being worked in a timely manner. e-cases that result from ERMS should be worked within two (2) hours of receipt.
-
See IRM 3.42.7.5.6, e-mail Response Management System (ERMS), for assistor instructions.
-
EPSS is responsible for managing the content of the solutions database. Each product that the e-help Desk and IRB supports has several associated solutions. Before solutions can be added to the database, they must be approved by their Policy Owner.
-
To maintain the solution database, EPSS has established an EHSS Solutions Board. Board members are selected from the Andover, Atlanta, Austin, Cincinnati, Martinsburg and Ogden sites by the Solution Board lead. The EPSS Policy, Training, and Quality staff will issue an annual solicitation for Solution Board members. Interested assistors and Level 2 employees must submit a complete and properly signed Statement of Interest (SOI) form by the designated due date to be considered for a board position. Although there is no term limit, existing Solution Board members must reapply each year. Solution Board members serve on the board as a collateral duty and remain in their current position and grade.
-
The Board lead is an analyst from the EPSS Policy, Training, and Quality staff. The Board lead coordinates with Policy Owners to ensure products supported by EPSS have accurate and valid solutions in EHSS.
-
The responsibilities of the Board members include:
-
Attending bi-weekly conference calls.
-
Working as a team member and independently.
-
Reviewing assigned e-cases and providing recommendations.
-
Creating new solutions and revising existing solutions.
-
Approving new and revised solutions.
-
Entering changes in the EHSS production database.
-
-
The responsibilities of the Board lead include:
-
Selecting Solution Board members.
-
Leading bi-weekly conference calls and working with Board members during the solutions creation and revision process.
-
Working with Policy Owners to obtain final approval of new solutions.
-
Working with Policy Owners and Board members to provide annual certification of solutions.
-
Monitoring the status of all solutions being developed and revised.
-
Maintaining all solution templates and approval records.
-
Providing quality control to ensure solutions have been input and updated correctly.
-
-
New or revised solutions are necessary for various reasons:
-
A user determines that EHSS does not contain an appropriate solution or an existing one needs to be revised.
-
A Policy Owner makes program changes during the year.
-
A new product is added to those supported by the e-help Desk.
-
An internal procedural change is made.
-
-
The Policy Owner is responsible for writing the e-help Communication when a solution changes requires immediate notice to the assistors.
-
When changes are made to an existing product, the Policy Owner must notify the Solutions Board lead. If a substantial number of changes are made a new e-help Solution Template may be required. The template and instructions are located on the EPSS web site at http://win.web.irs.gov/epss/espss_docs/EPSS_Engagement/Solutions_Template_Instructions.xls .
-
After the solutions are worked by the Board members, the Board lead will submit the solution template, to the Policy Owner for final review and approval. When approved, a Board member will place the solution into production on the EHSS solution database.
-
When a new product is added to EPSS, the Policy Owner will follow the procedures in the Customer Engagement Document and submit the solutions on the e-help Solution Template. IRM 1.4.18.1.4, Customer Engagement for more information.
-
After new solutions are created, reviewed and approved, the Policy Owner submit to the Board lead.
-
It is difficult to determine what types of calls will be received for new products; therefore, new solutions will be created as needed by following the procedures in IRM 3.42.7.5.3.4, Requesting New Solutions or Updates to Solutions.
-
The e-help Desk uses the Aspect 7.2 application and software which provides monitoring capabilities, data base records, and management information. The Aspect TeleSet Supervisor key gives managers access to expanded features such as:
-
Leaving messages for employees (each site should have its own policies based on voice port availability)
-
Monitoring agents (listening in on calls in progress)
-
Notifying agents (notifying an agent whom you are monitoring to call you)
-
Monitoring trunks (monitoring conversations on specific trunks)
-
Monitoring specific Aspect application groupings
-
Determining the availability of agents
-
-
The manager and the lead should be given permissions on Aspect to access abilities using the Supervisor button. Using the Supervisor button allows you to monitor telephone calls and trunk lines.
-
Sign on under your Administrative extension to allow assistors to transfer calls to you when necessary.
-
The Exam Managers Resource Guide has a complete description of Aspect Telephone System features in Section 3, Systems Used in Exam. You can access the Resource Guide on the W&I Compliance Examination Discretionary Programs web site at http://win.web.irs.gov/compliance/compliance_exam.htm . You may wish to print and keep this reference handy.
-
The System Administrator/Telephone Analyst (SA/TA) is a valuable resource person regarding the features of the ASPECT system.
-
Managers must coordinate with their SA/TA on any activity limiting the site's ability to deliver its commitment for scheduled ACD time.
-
The SA/TA provides assistance on the following:
-
Information about system operations and call routing
-
Explanation of various ASPECT reports
-
Identification of data availability and creating reports
-
Assessment of current call site performance
-
Networking information
-
Monitoring procedures
-
Assistance with ETD
-
ASPECT equipment repair
-
Database changes
-
-
Supervisors use the Aspect TeleSet to perform the following tasks:
-
Monitoring – Monitor a live conversation for review purposes.
-
Notifying – Alert an employee to a problem during a live conversation.
-
Making an agent available – Force a user into the AVAILABLE state.
-
Performing Side-by side-monitoring– Utilize a second telephone jack on the employee's TeleSet.
-
-
To monitor a call through Aspect, sign on to your TeleSet and perform the following steps:
-
Press "SUPERVISOR" key.
-
Enter the extension of the assistor to be monitored.
-
Press "ENTER." The display on TeleSet LCD will show: "Monitoring Extension 5555 NOTIFY."
-
Press the "RELEASE" key to end the monitoring session.
Reminder:
Contact Recording is the preferred method of telephone monitoring. Conduct this type of monitoring only when Contact Recording is unavailable.
-
-
To notify an employee during a live review, press the "NOTIFY" soft key. This sends a message to the user's TeleSet display instructing them to call you and provides your extension. Do not interrupt a call unless the employee is:
-
Advising the taxpayer/caller incorrectly
-
Providing discourteous service
-
Unable to answer the question
-
Threatened by a caller
-
-
To make an agent available, the agent must be in IDLE state, or in WRAP-UP after pressing the DONE soft key. To make the agent AVAILABLE, press SUPERVISOR, enter 0 and the user's extension, then press ENTER.
Caution:
Be sure the agent is present and at their desk before forcing them into AVAILABLE.
-
Side-by-side monitoring, also known as "double jacking," is used to review telephone calls for training purposes. It can be 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.
Note:
Side-by-side monitoring is non–evaluative and not formally documented. It may be delegated to leads or experienced Assistors.
-
The manager provides a key role in maintaining the accuracy of the Aspect database. Managers should remain in contact with their respective EPSS Telephone Systems Analyst (SA) for any changes needed. Changes include but are not limited to:
-
Adding new extensions for new employees
-
Adding new extensions for current employees (adding agent groups)
-
Changing Team Numbers
-
Deleting obsolete extensions
-
Resetting passwords
Note:
The telephone SA will not always be local to the site, in some instances the SA will be remote.
-
-
Managers should be communicate changes to the SA immediately. Changes should be submitted to the SA by using the "EPSS Aspect Change Form" . Indicate "A" to add a new extension, "M" to modify an existing extension, or "D" to delete an existing extension, and "T" for team changes. Changes should also be submitted monthly for update/review of the Aspect database. If you do not have any changes indicate "No Changes" on the form. EPSS Aspect Change Form.
-
.The site SA communicates the changes to JOC thru the Program Management (PM) analyst. Be sure to allow enough time for the SA to communicate this information to the JOC. The JOC time-lines are as follows:
-
1 - 5 Changes – Request completed within 1 business day
-
5 - 25 Changes – Request completed within 5 business days
-
25 - 100 Changes – Request completed within 10 business days
Note:
Any expedite requests must be notated on the change form with an explanation so the SA can coordinate the request with the PM analyst.
-
-
Forecasting and staffing requirements are developed by Program Management (PM) staff analysts for the e-help Desk and IRB. Required staffing for each site is determined by taking into consideration such factors as:
-
Historical call volumes and handle times (year over year)
-
Abandon rate (15%)
-
Slippage assumptions (5%)
Note:
Adjustments can be made to these factors to allow for seasonal changes as well as holidays and other factors that affect the forecast.
-
-
In generating staffing requirements for EPSS, the PM Analyst considers the requirements from an enterprise perspective. Scheduling is done by application (product) based on forecasts for the enterprise. The adherence of each individual site to the schedule is important and impacts the performance of the e-help Desk Operation and IRB.
-
Site receives a half hourly tool, a Microsoft Excel spreadsheets providing staffing requirements.
-
The columns represent each half-hourly period for each site. The column for each weekday represents the number of assistors needed to meet the inbound contact demand expected for each scheduled half-hour. To schedule your site according to the requirements shown in the spreadsheet, take the following steps:
-
Review the tabs at the bottom of the spreadsheet that shows the applicable Agent Group for each site. This shows the number of assistors required for the applicable scheduling period.
-
Assign this number of assistors to the telephones.
Note:
Requirements for each half-hour do not take into account scheduled off-phone activity (i.e., breaks, lunch, etc.).
-
-
Agent Groups are the skilled groups of assistors that provide service to the customer. Applications are the services that 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.
Note:
Agent Groups should not be confused with Applications. Also, Application numbers and Agent Group numbers and descriptions do not correspond one-for-one.
-
The e-help Desk should always keep AG 709, EH – Lead/Manager, staffed. If a customer requests to elevate an issue, someone should be available in this Agent Group to address the customer's concern.
-
Adherence is used to identify whether the number of agents required by the e-help operation and IRB operation are available for the time periods specified in the schedule. It is also used to identify whether the call site meets the overall telephone schedule provided to them. Adherence is measured by the number of ready assistors signed on to the Aspect system, either taking a call or involved in the completion of a call. Assistors in IDLE status are not included when adherence is determined.
-
Managers are responsible for ensuring the required number of assistors are signed on the telephones to meet adherence.
-
Assistors should sign on when their tour of duty (TOD) begins and remain signed on until their TOD ends.
-
Assistors that must be temporarily away from their work areas are required to use the correct idle reason code.
Exception:
If ... Then ... An employee is in an all-day training session They will not sign on at all. An employee is assigned to non-phone duty at their workstations They will sign on using their administrative extension and log into Agent Group 707 (Extension Routing/Inventory). An employee is 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.
-
-
The telephone schedule allows the team manager to monitor and maintain team adherence. An individual schedule should be given to all assistors so that they know when they are required to be on the telephones.
-
Individual adherence impacts the entire enterprise adherence. Recognize employees with good adherence. Promptly address employees with adherence problems.
-
When an employee is not meeting their assigned telephone schedule, take the following steps:
-
Remember to look at each situation individually.
-
Address the problem directly with the employee.
-
Use results of your personal observations to validate your assessment.
-
Offer guidance as to how to correct the problem.
-
-
If the problem continues, take these steps:
-
Prepare a written assessment of the problem.
-
Describe exactly how the employee is failing to meet a specific Critical Job Element (CJE) or conduct expectation.
-
Refer to prior verbal discussions in the documentation.
-
Offer guidance as to how to correct the problem.
-
-
A determination to counsel verbally or with documentation should be made on a case-by-case basis. Factors to consider include whether or not the employee has displayed the behavior before and whether or not you observed the behavior. Failure to adhere to the schedule may be either a performance problem or a conduct problem. Contact your department manager or Labor Relations specialist for guidance.
-
Regardless of the type of equipment in your area , there is data to assist you in evaluating the service being given to customers and to determine the availability and efficiency of the telephone staff.
-
Managers and Systems Analysts (SA) must determine if the staff is available as scheduled.
-
Managers must ensure their employees are signed on to the telephone system and taking calls when scheduled. This reduces shrinkage.
-
Shrinkage is a combination of one or more issues, such as:
-
Extended read and meet times
-
Tardiness
-
Leaving early
-
Higher than expected attrition for day (e.g., sick leave)
-
Scheduled breaks not being followed
-
Unauthorized breaks
-
Extended breaks or lunch periods
-
Unanticipated workload
-
-
The sites must make daily real-time adjustments to the schedules based on the actual demand and actual staffing.
-
Use the available resources to assist you in scheduling to meet peak staffing requirements.
-
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 (AHT) is based on scheduling assumptions. Unreasonable talk time compromises program goals and increases the amount of abandoned calls. It could be an indicator that additional training in conversation control is needed.
-
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
-
-
Wrap is a TeleSet mode that is used to complete a call after the customer has been released. Wrap should only be used to complete actions related to the previous call. As most systems are updated while on-line or on hold with the caller, use of wrap time should be minimal except in rare instances.
-
Use wrap time or use reported wrap time to gauge if your staff is coping effectively in a telephone environment, and assists you in determining the amount of time your staff is unavailable for calls.
-
Possible reasons for high percentages of wrap time are:
-
Level of training
-
Extensive research for call backs
-
Excessive requirements in reporting call backs
-
Minor illness (e.g., headache) which caused the Assistor to take short rest periods between calls
-
Excessive conversation among Assistors
-
Excessive research
-
-
"Idle" is an Aspect status that assistors must use when not in "Available" or "Wrap-Up."
-
When assistors are not available for incoming calls (e.g., meetings ,read time, lunch, working paper, part-day training), they should go into idle and indicate their status by using one of the reason codes below.
Figure 1.4.18-4
Reason Code Status Explanation 1 Temporarily Off the Phone This code indicates that the employee will be unavailable for telephone work for a period of time not specified by other reason codes. Examples are lunch, meetings, counselling meetings, NTEU official duties, Form 3081 preparation, and rest room breaks. 2 Reserved and will not be used at the present time. 3 Reserved and will not be used at the present time. 4 Training, Partly Available This code indicates the employee will be unavailable for telephone work during a specified portion of the tour of duty (TOD) because of training-related activities. Examples include partial-day off-site, on the job training (OJT), or instructor preparation. Note:
Employee should not sign on if they will be in training their entire TOD.
5 You will not be available for telephone work during a specified portion of the TOD because of read time. 6 Reserved and will not be used at the present tme. 7 Break Time This code indicates that employee will be unavailable for telephone work during a specified portion of their TOD because of a scheduled rest break (other than lunch) or unavailable in order to relieve a stressful situation. -
To ensure adherence, monitor employee statuses using Webview.
-
If an employee fails to properly use the idle reason codes, counsel them according to the guidelines in IRM 1.4.18.10.3.1, Adherence.
Caution:
Reason codes are to be used 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 Form 3081).
-
Consider the following when you schedule telephone assignments:
-
Break/lunch schedules
-
Leave schedules
-
Training schedules
-
Team meeting schedules
-
-
Attempt to assign an equal amount of telephone duty to each assistor.
-
Remember that although a schedule has been provided by the PM staff analyst and the site SA creates the schedules,, adjustments may need to be made during the day. To determine when adjustments should be made, use Webview.
Note:
The EPSS telephone site analyst should be notified when scheduling changes are made (i.e., meetings, training).
-
Assistors are required to sign on to Aspect at the beginning of their tour of duty (TOD) and remain signed on until their TOD ends. While signed on to Aspect, assistors will use the Idle Reason Codes found in IRM 3.42.7.7.1.1 Reason Codes for Idle. Exceptions to the requirement to sign into Aspect are as follows:
-
Assistors in all day training sessions will not sign on at all.
-
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 on until they are at their workstations.
-
Assistors who report to their workstation at the beginning of their TOD, but thereafter attend training, meetings or other situations that result in an absence from their workstations until the end of their TOD, will sign off when they leave their workstation.
-
-
Managers will allow assistors to sign off Aspect up to 12 minutes (0.2 hours) before the actual end of their shift. This time is to conduct end-of-the-day activities (Form 3081 preparation, complete reports, etc). Managers may approve more time on an as needed basis.
-
On rare occasions, an assistor may not able to complete their call before the end of their TOD. If this happens, the assistor should notify their manager or lead immediately. The manager or lead will determine how best to handled the call and can offer Credit, Comp, or Overtime (if available) to the assistor as a resolution.
-
WebView is a web interface to the ICM enterprise reporting. With WebView, you can work directly with ICM reports and scripts from the browser on your computer. Managers can use WebView to view reports (real-time and historical), create new reports (based on WebView's report templates), and modify reports.
-
Depending on the report you choose, WebView shows the user the current state of the enterprise, a site, and/or individual employees. To access WebView follow these steps:
-
Type http://joc.enterprise.irs.gov in your browser
-
Select 'OPS'
-
Select WebView Reporting 7.0
-
Select one of the following options:
-
WebView Reporting 7.0 Log In (to log into WebView)
-
JOC WebView Account Management (to reset/change your password)
-
-
Select Real Time or Historical
-
Click on Submit
-
-
At a minimum, managers should use the following Real-Time reports:
-
Real Time Call Type Report – shows the overview of the enterprise call queue. Monitor this report to identify long queue times, high volumes of calls in queues and high abandon rates.
Figure 1.4.18-5
To access this report on WebView, go to: Call Type Saved Reports Select one of the following: -
E_Help call type_
-
IRB Call Stats w_Lvl_2
Hit "Run" at the bottom right-hand side of the page -
-
Agent Skill Group Real Time Report (e-help Agents_ALL_TJ) shows each site's breakdown of agents logged in and the number of calls in the enterprise queues for the applicable agent groups. It also shows the current status of assistors (i.e., Ready, Talking, Idle, Wrap Up).
Figure 1.4.18-6
To access this report on WebView, go to: Agent By Skill Group Saved Reports Select from the following -
e-help Agents_ALL_TJ
Hit "Run" at the bottom right-hand side of the page -
-
Real-Time reports are updated in intervals of 15, 20, 30, or 60 seconds. The system default is set at 20 seconds. To change this, click on "Refresh" in the menu option and select the time interval preferred.
-
Threshold values can also be set to alert the user when certain values exceed or do not meet expected levels by assigning a color to the display. This is done by clicking on "Threshold" in the menu option of any report.
-
Reports are used by management in EPSS and by product owners to track and address issues. Some reports are run on a daily basis; others are run on a weekly basis. There are also ad hoc reports that are run when a customer wants specific information that is not provided by the regular reports.
-
There are two types of reports used in e-help:
-
EHSS reports give a manager e-case statistics on either an assistor or a product. EHSS reports are provided to managers on a weekly basis. They can also be accessed from the EPSS web site at http://win.web.irs.gov/epss/epss_home.html.
-
Aspect Crystal reports give a manager call activity statistics on a individual assistor or workgroup.
-
-
Reports are indicators of an individuals performance but may not be used alone for evaluative purposes. Use reports to determine the need for further monitoring and/or assistance.
-
EHSS reports are created using MS Query Analyzer and formatted using Crystal Reports. They are saved as Adobe.pdf and distributed to managers and internal customers.
-
Weekly e-case Counts: This report has 2 sections. The cover sheet shows a summary of how many e-cases were opened and closed during the week by site. The pages that follow show site-by-site statistics of opened and closed e-cases.
-
Weekly Product Report: This report is a weekly roll-up report by product. The cover sheet details the number of e-cases opened during the week with an enterprise total provided. The pages that follow are by product and show the top problem types (Issue Reported) and the numbers of each problem.
-
Weekly Total e-case Count by Person: This report shows the total number of e-cases opened and closed by individual assistor by site for the week.
-
Weekly Aged e-case Report: This report shows the number of aged e-cases opened for more than 7 days by individual assistor.
-
Provider Group Aged e-cases: This report shows e-cases open for more than 7 days assigned to a provider group (not an individual).
-
Calls Handled vs. e-cases created: This report shows the number of calls handled compared to the number of e-cases created for the enterprise along with graphs.
-
Weekly Site Contact Report: This report shows the number of calls handled compared to the number of e-cases created for a particular group.
-
Product Report: This report shows products, issues reported and e-cases opened for each product. This report is posted to the EPSS web site.
-
-
Managers should review each report to determine if organizational and/or team goals were met. Determine reason for aged e-cases being open for more than 7 days. If there is no valid reason for the open e-case, managers should discuss it with the assistor. Instruct employees not to use any products that are prefaced by the word "Inactive" on the product report.
-
Aspect Crystal Reports are used by team managers to determine the status of telephone activity. Some reports are received daily and others weekly.
-
The EPSS Aspect Telephone System Analyst (SA) runs these reports and automatically schedules them for delivery via e-mail or server. They have the capability of running ad-hoc reports for various time-frames or for a specific type of data. If you need an additional report contact them to have the data pulled from the Aspect system.
-
Reports are a tool that managers can use to identify areas where the team members excel (adherence, good talk time, and minimal use of wrap time) and areas that need improvement (adherence and improper use of idle reason codes). Reports can be used as a diagnostic tool. They can be used to support your personal observations.
-
Managers cannot share the Aspect report information with employees because the report may suggest a production quota or goal on employees.
-
Managers can use the Aspect reports as an indicator to locate areas that need additional monitoring.
Note:
In conjunction with your observation the reports can be used as an indicator of time. e.g. I have not seen you since... I noticed you were away from your desk while in wrap.
-
-
The reports received vary by site. However, at a minimum, each manager should receive the following reports:
-
Agent Performance Summary by Team – This report shows general call activity for all agents signed on to the system during a specified period.
-
Application Management Summary – This report displays the call statistics based on the different Application groupings.
-
Abandoned Calls Profile – This report shows the number of incoming calls abandoned during each half hour segment of the day. It uses the Application Detail view and sorts by half hour.
-
Excessive Reason Code Report – This report shows agents in idle codes for an excessive amount of time. It uses the Agent Idle view and is available by daily intervals.
-
-
This report shows general call activity for all agents signed onto the system during a specified period. See the figure below for a description of each section of the report.
Figure 1.4.18-7
Section Description Agent Lists each employee within the team and their Aspect number. Duration The amount of time during the period that the agent was signed on the system. Incoming -
Shows the number of incoming calls the agent received during the period.
-
Shows the average length of those calls.
-
Shows the percentage for this overall period the agent spent on incoming calls.
Outgoing -
Shows the number of outgoing calls the agent made during the time period.
-
Shows the average length of those calls.
-
Shows the percentage for this overall period the agent spent on outgoing calls.
Inside -
Shows the number of inside calls the agent made during the period.
-
Shows the average length of those calls.
-
Shows the percentage for this overall period the agent spent on outgoing calls.
Customer Messaging -
Indicates the time spent on reviewing messages.
-
Shows percentage of time spent for the period.
Voice Messaging -
Indicates the time spent reviewing messages.
-
Shows percentage of time spent for the period.
Percent Spent In This column breaks down the amount of time spent in Available, Idle, and Wrap Up. Work Time This column captures the entire time for the period spent on the Aspect system and the percentage. Group Totals This section is across the bottom of the report and provides totals of the entire group in each of the above sections. -
-
This report is useful in evaluating individual agent productivity. Ways to use this report:
-
Compare talk times for all agents on the team. Do you have 1 or 2 with considerably higher talk times? You may need to ascertain why.
-
Does an employee have a higher number of inside calls? The employee may be relying too heavily on the lead for assistance and is not performing required research. This may be an indication that additional training is needed.
-
-
The Application Management Summary report summarizes call activity for applications. The chart format shows handled calls versus abandoned calls for each application. Also shown are:
-
The total number of offered and outgoing calls made by each application.
-
Percentage of calls abandoned.
-
Service level percentage.
-
Average call time for incoming and outgoing calls.
-
Speed of answer for incoming calls.
-
The number of calls handled by the primary agent group, the number that went to another agent group, the number handled by voice messaging, and the number handled by another resource, such as an auxiliary device.
-
-
The Abandoned Calls Profile report charts incoming calls abandoned by the application during each half-hour segment of a day. With this report, you can see:
-
The number of received calls that were abandoned.
-
The half-hour segment in which the call abandoned.
-
The average time callers waited before hanging up.
-
The longest wait before a call was abandoned.
-
-
Calls queue at the ISN/CVP level, so this report only shows calls that abandon after being routed to a local queue. This can happen when a call is in flight from the ISN/CVP to an assistor and the assistor goes from an available status into a non-available status (Idle, Wrap, or Log off) or the caller hangs up while the call is in flight.
Note:
If you see a high number of calls abandoning at particular times of the day, it may indicate a problem with staffing. Check to see if you have assistors moving from an available status to a non-available status for lunch and breaks.
-
This report shows the team, individual agents, time entered into an idle code, the idle reason code used, and the duration of time spent in idle. The data is sorted by team and agent.
-
Use the Excessive Reason Code Duration report, along with WebView, to determine if employees are properly identifying their change of work status, via their Aspect telephone, and using the correct idle reason codes. IRM 1.4.18.10.3.5, Idle Reason Codes.
-
Organization, Function, and Program (OFP) codes are recorded by employees on Form 3081, Employee Time Report, to identify work that IRS employees perform daily.
-
Organization Code – A five digit code used to describe where (e.g., Document Perfection or Input Correction) the work is being performed. 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.
-
Function Code – A three digit code that is used to describe what (e.g., e-help assistor) is being done.
-
Program – A five digit code that is used to describe the program (e.g., Form 8453, EFTPS) being worked.
-
-
OFP codes have various uses including the preparation of work plans and work schedules. For this reason, it is important that this information is reported consistently and accurately. A complete list of all OFP codes can be found at http://ofp.web.irs.gov/index.asp, Organization Function Program (OFP) Code web site.
-
Managers must ensure that employees use the correct codes when working telephones, e-mail, and paper. These codes can be found in IRM 3.42.7.3.5, Exhibits 3.42.7-1 and 3.42.7-2 provide a breakdown of each codes' function, program, and title.
-
Employees should be instructed to make every effort to track and report the time spent on programs accurately. When making assignments, limit frequent program switching, whenever possible, to help employees record time accurately.
-
In the event of a disaster or other event that interrupts the service of the e-help Desk, the following strategy should be used to ensure that the business continues.
-
Scheduled Interruption of Service:
-
The site manager will notify the Operations Support senior manager, e-help Desk or IRB 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.
-
The e-help Desk or IRB senior manager will notify all e-help Desk site managers.
-
The JOC will be contacted by the telephone analyst if a routing change needs to be performed.
-
The receiving site manager will reallocate resources in anticipation of the increased call volume(s), if applicable.
-
-
Unscheduled Interruption of Service (Site Recognized):
-
The site manager or a designee will notify the Operations Support senior manager, e-help Desk senior manager, and telephone analyst by telephone. Provide as much information as possible about the disruption and the anticipated recovery time.
-
The e-help Desk senior manager will notify all e-help Desk site managers.
-
The JOC will be contacted by the telephone analyst if a routing change needs to be performed.
-
The receiving site manager will reallocate resources in anticipation of the increased call volume(s), if applicable.
-
-
Unscheduled Interruption of Service (JOC Recognized):
-
The JOC will enable the current e-help disaster closure matrix.
-
The receiving site manager will reallocate resources in anticipation of the increased call volume(s).
-
-
All applications, except Suitability and IRB (Application 721, 811, 812, 813, 814, 815 and 816) are distributed among at least two sites so a back-up site has not been specified. The following chart shows the alternate or fail-over site for suitability if the primary site is compromised:
Compromised Site Failover Site Andover Austin Note:
At this time IRB does not have an alternate or fail-over site.
-
EHSS Outage or Slow Processing:
-
Open a ticket using the OS Get Services at http://getitservices.web.irs.gov for Priority 3, 4 or 5 tickets or by calling 1-866-7HELP4U for Priority 1 and 2 tickets.
Reminder:
Assistors should manually record all data during the outage. See IRM 3.42.7.8.6, Reporting EHSS Problems
-
-
Various miscellaneous managerial functional responsibilities are included in this section.
-
QuickAlerts is a free, online service that disseminates mass e-file messages, within seconds, to all "subscribed" individual and business e-file software developers, transmitters, and authorized e-file providers.
-
Quick Alerts also provide e-file information to assist employees in their job performance and enhance the filing season. :
-
) There are three categories that the assistor should subscribe to:
-
Alerts – Processing delays, programming issues, changes to any filing season procedure, PATS testing changes.
-
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.
-
-
As a manager you should, ensure all new employees subscribe to QuickAlerts and verify all returning seasonal still have a subscription to QuickAlerts.
-
EPSS maintains an all employee Outlook distribution list to send business unit wide communications commonly referred to as e-help Communications. The e-help mailbox has been established to control and maintain a record of e-help Communications. The primary function of e-help Communications is to provide procedural and systemic updates to e-help Desk assistors in a timely and consistent manner. Additional uses of e-help Communications include but are not limited to:
-
Distribution of the quality news and bulletins.
-
Solicitation for subject matter experts (SMEs) for course development.
-
Notification of changes in agency or governmental procedures during exception periods such as building closures or budgetary constraints.).
-
-
You must contact the Program Management analyst assigned to e-help Communications and request read permissions to the e-help mailbox Inbox and Communications folder. The analyst’s name is in the bottom margin of all e-help Communications.
-
Managers must confirm that employees receive e-help Communications; this should be done verbally. All e-help Communications are sent to and received by the e-help mailbox with the distribution list in the blind copy line. Provide distribution list updates to the Program Management analyst by e-mail request. Employees to include in the request include new hire and return-to-duty e-help Desk assistors. Updates should also be made when e-help Desk assistors leave the business unit.
-
PII is taxpayer information or any combination of information that can be used to uniquely identify, contact, or locate a person that could subsequently be used for identity theft. Some examples of PII include, but are not limited to:
-
Names
-
Home or e-mail addresses
-
Telephone numbers
-
Social Security Numbers
-
Date and place of birth
-
Family information such as a mother's maiden name
-
Tax return or salary information
-
Credit card or bank account information
-
Biometric data (height, weight, eye color, fingerprints, etc.)
-
Other numbers or information that alone or in combination with other data can identify an individual
-
-
The protection of this information is of vital concern to the Service; every effort must be made to protect it. Ensure that you and your employees review your electronic files and paper holdings for this type of information. Verify that you have only PII in your possession that you have a "need to know" .
-
You and your employees must follow proper procedures for safeguarding PII information that you have in your immediate possession. PII stored on computer hard drives or transferred to CD-ROMs, jump drives, or other portable media must be encrypted. The FIND-IT Icon on every IRS computer has step-by-step guidance on methods of Encryption.
-
If a laptop or other electronic device is lost or stolen, it must be reported within one hour to:
-
Your manager
-
The Computer Security Incident Response Center (CSIRC) at 866-216-4809
-
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 that any needed investigation and recovery can be initiated quickly. This can decrease the possibility that the information will be compromised and used to perpetrate identity theft or other forms of fraud.
-
-
Additional information on how to protect PII can be found on the Office of Privacy, Information Protection & Data Security web site, http://irweb.irs.gov/AboutIRS/bu/pipds/default.aspx.
| e-help Site Hours Requirement Forecast | ||||||
|---|---|---|---|---|---|---|
| Site | Agent Group | Apps All | Week ending | |||
| Forecast Requirements | ||||||
| Time | Monday | Tuesday | Wednesday | Thursday | Friday | Saturday |
| 6:30:00 | 28 | 27 | 27 | 27 | 27 | - |
| 7:00:00 | 31 | 30 | 31 | 31 | 30 | - |
| 7:30:00 | 34 | 30 | 33 | 31 | 30 | - |
| 8:00:00 | 36 | 33 | 35 | 35 | 34 | - |
| 8:30:00 | 39 | 37 | 38 | 35 | 37 | - |
| 9:00:00 | 41 | 39 | 39 | 40 | 39 | - |
| 9:30:00 | 44 | 42 | 41 | 41 | 40 | - |
| 10:00:00 | 44 | 43 | 44 | 42 | 42 | - |
| 10:30:00 | 45 | 43 | 45 | 42 | 44 | - |
| 11:00:00 | 46 | 46 | 46 | 44 | 44 | - |
| 11:30:00 | 47 | 46 | 45 | 45 | 43 | - |
| 12:00:00 | 47 | 46 | 45 | 46 | 42 | - |
| 12:30:00 | 48 | 47 | 46 | 46 | 44 | - |
| 13:00:00 | 48 | 46 | 45 | 46 | 43 | - |
| 13:30:00 | 47 | 46 | 47 | 44 | 43 | - |
| 14:00:00 | 47 | 45 | 45 | 44 | 41 | - |
| 14:30:00 | 45 | 43 | 43 | 43 | 40 | - |
| 15:00:00 | 42 | 42 | 41 | 41 | 40 | - |
| 15:30:00 | 39 | 38 | 38 | 38 | 37 | - |
| 16:00:00 | 24 | 23 | 24 | 23 | 23 | - |
| 16:30:00 | 22 | 20 | 21 | 22 | 20 | - |
| 17:00:00 | 18 | 19 | 18 | 19 | 17 | - |
| 17:30:00 | 18 | 18 | 18 | 18 | 17 | - |
| 18:00:00 | - | - | - | - | - | - |
| 18:30:00 | - | - | - | - | - | - |
| 19:00:00 | - | - | - | - | - | - |
| 19:30:00 | - | - | - | - | - | - |
| 20:00:00 | - | - | - | - | - | - |
| 20:30:00 | - | - | - | - | - | - |
| 21:00:00 | - | - | - | - | - | - |
| 21:30:00 | - | - | - | - | - | - |
| 22:00:00 | - | - | - | - | - | - |
| 22:30:00 | - | - | - | - | - | - |







