5.0 Process and Procedures Flashcards
5.1.1 Define procedure
A procedure is documented set of steps required to produce a desired result.
5.2.1 Define quality assurance (QA)
Quality assurance (QA) is a systematic way of ensuring that all the activities necessary to design, develop, and implement services that satisfy the requirements of the organization and of customers take place as planned.
5.2.2 What are the types of quality assurance practices in a support center?
> Service Quality
> Customer Satisfaction
> Employee Satisfaction
> Monitoring
> Call
- Incident/ Request (ticket/case) monitoring
- Knowledge monitoring
- Email/Chat monitoring
> Maturity Assessments
Service Improvement Plans (SIP)
5.2.3 What are the mechanisms for call monitoring?
Live service observations, in which a reviewer sits with the representative and listens in on the call
Remote service observations, in which a
reviewer listens to calls live (the representative is not aware that the call is being evaluated)
-Call recording and evaluation used for
training, providing the representative with
an opportunity to hear how they sound on the telephone and where they can improve
5.3.1 Explain the importance of customer satisfaction surveys.
Customer satisfaction surveys allow the support center to:
- Understand the customer’s perception of the products, services, support, and the quality received
- Identify whether customer expectations are being met
- Identify what the customer feels is important
- Define and assist with the development of new products, services, and support offerings based on customers needs
- Identify opportunities to improve support processes, tools, training, and documentation
5.3.2 Describe the three most common types of surveys and the importance of each.
- Ongoing incident surveys:
Completed as soon as possible after a call is closed.
-Typically short (e.g., 5-6 questions) and can be completed quickly
- Used to measure the quality of a specific incident resolution
- Used to monitor customer satisfaction between annual surveys and measure the impact of changes to processes, products, or services
2. Annual or periodic - Planned and scheduled on a periodic basis (e.g., annually)
- Used to evaluate overall satisfaction levels with the support center’s products, service offerings, and staff
- Used to identify changes to products, services, and processes that customers feel would improve their relationship with the support center and better meet their needs
- Based on the customer’s perception of the company over the last year or period
- Typically skewed to emphasize recent experiences
3. One-Time Surveys - Not completed at regularly scheduled intervals
- Conducted for a specific purpose
- Appropriate for evaluating satisfaction levels with current products and service offerings or for identifying changes that customers feel are important
5.3.3 What are the methods for distributing and completing satisfaction surveys?
- Phone interviews
- Internet, Web-based surveys
- in person interviews
- regular mail
- satisfaction follow-up cards left by a service tech
- CTI and ACD systems
5.4.1 What is the purpose of the Security Management process?
- Protect information assets against threats
- Assess and mitigate security risks
- Ensure confidentiality, integrity, and availability of the information assets
5.4.2 What the the types of security policies
- Unique login name and password parameters
- Password reset requirements
- Reducing the visibility of credit card information
- Blocking access to personal information
- Identification badge requirements
5.4.3 What are the types of data that should be protected
- Customer names and IDs
- National ID numbers
- Individual or corporate financial information
- Personal information
- Credit card numbers
5.4.4 Explain the importance of reporting security compromises
- Protects the company and the customer
- Identifies the offender and prevents the security breach from occurring again
- Limits the damage that is caused
- Alerts customers to possible security threats
- Helps in the resolution of security incidents
- Enables effective security policies and procedures
5.5.1 Explain the purpose of Incident management process
The primary purpose of the Incident Management process is to restore normal service operation as quickly as possible and thus minimize the impact on business operations, thus ensuring that the best possible levels of service quality and availability are maintained. ‘Normal service operation’ is defined as service operation within service level agreement (SLA) limits.
5.5.2 Define Incident
An unplanned interruption to the standard operation of a service, or a reduction in the quality of that service. An Incident can also be the failure of an IT component that has not yet impacted a service - something is broken or not working as expected.
5.5.3 List and explain the activities of the Incident Management Process
Incident Identification - incident is reported
Incident Logging — incident is logged and time/date stamped
-Incident Categorization —
incident is classified by type
- Incident Prioritization -priority is assigned based on impact and urgency
- Initial Diagnosis - search for match or Workaround to attempt quick resolution and service restoration
Escalation — a transfer and/or notification to
another team, individual, or management
Investigation and Diagnosis- activities undertaken identify a solution and/or workaround
- Resolution and Recovery- solution is applied and service is restored
- Closing - support center verifies with the user that the incident is resolved and the incident is documented correctly
5.5.4 List the value of the incident management process
Incident Management provides value by:
- Minimizing impact to the business for any failures of the infrastructure
- Minimizing downtime for users
- Identifying training requirements for Support Center staff and users
5.5.5 Describe the responsibilities of the customer service rep in the Incident Management process
- Perform the process as defined (for their role)
and at the agreed time frames (service level)
-Serve as a liaison with other groups as necessary
to coordinate the resolution of incidents
5.5.6 Explain the purpose of the request fulfillment process
The Request Fulfillment process is designed to deal with service requests (e.g., standard changes from users, Installations, Moves, Adds, Changes (IMAC), How to Questions that are handled by the support center).
5.5.7 Define Service Request
request from a user for information, advice, a standard change or access to an IT Service
5.5.8 List and explain the activities of the Request Fulfillment process
Request Fulfillment is very similar to the Incident Management process, though Requests are conceptually planned/scheduled, Whereas incidents are typically unplanned.
The activities of Request Fulfillment are:
- Logging requests
- Determining if any other approvals are necessary, if so, forward for approval
- Following appropriate procedures for request (assumes each type of request is defined)
5.5.9 List the value of the request fulfillment process
Request Fulfillment provides value by:
-Reducing downtime and cost for users via effective
and efficient fulfillment of service requests
-Prioritizing requests based on business goals/alignment
5.5.10 Describe the responsibilities of the customer service rep in the request fulfillment process
Perform all activities within the process as documented
Serve as a liaison with other groups as necessary to coordinate the fulfillment of requests
5.6.1 List the best practices for customer management during the incident management process
> Prepare for the call
-Take a deep breath
- Stop working on other tasks and focus
- Get ready to take notes
- Prepare your tone of voice
> Greet the customer
- Provide a salutation
- Identify your support center
- Identify yourself
- Verify the customer’s name and entitlement by asking a closed-ended question
- Ask an open-ended question to begin the problem-solving process
> Resolve the incident
- Assist the customer by resolving the incident, redirecting the call, or escalating
- Close the call
> Summarize the call
- Ask the customer if there is anything else you can do
- Thank the customer
- Allow the customer to hang up first
- Provide documentation to the customer and ensure the information in the service management system is correct
5.6.2 Explain the benefits of using the customer’s name during the call
> Sets the tone for the call
> Builds rapport between the representative and the customer
> Contributes to a positive first impression of the rep and the support center
> Serves as a subtle reminder to the caller that you know who he/she is and enables him or her to focus in emotional situations
5.6.3 Identify when to use the customer’s formal or informal name
> During formal communication:
- Use the customer’s title and family name
- Use business-oriented terminology and language
- There is little or no social discussion
> During informal communication:
- Do not use titles
- Use the customer’s first name
- Social discussion occurs
5.6.4 Identify techniques to keep the customer focused on the resolution
> Use empathetic statements to acknowledge emotion and convey understanding
> Use the customer’s name to gain attention
> Request that the customer complete the steps with you
> Asking closed ended questions to direct the conversation
> Paraphrasing to ensure understanding
5.6.5 Identify habits or situations to avoid when interacting with customer
> Asking the customer to repeat information that has already been documented
> Continuing a separate conversation while answering a call
> Expressing negative opinions about other people, teams, or departments
> Background noise
> Eating food or chewing gum
> Extended hold times
> Multiple transfers
> Using acronyms, slang, regional expressions, and terms of endearment (e.g., “honey,” “mate,” and “dear”)
> Being drawn into an argument with a frustrated customer
5.6.6 Explain how to use silent time effectively
> Complete your current incident including documentation, investigation, and follow-up
> Build rapport by engaging in informal communication
> Train the customer in order to raise their level of competency
> Review the incident’s history
> Communicate with the customer regarding new releases or new service offerings
5.6.7 Describe ways to handle and redirect issues related to non-supported items
> Maintain a positive service attitude
> Explain what services are offered and/or supported
> Provide alternatives to handle non-supported issues
5.6.9 List the steps for transferring a call
- Let the customer know the reason for the transfer and get the customer’s agreement.
- Ensure that the customer has your name and number in the event the call does not transfer successfully.
- Place the customer on hold while calling the receiving party.
- Explain the circumstances of the call and transfer all relevant information so that the customer will not have to repeat him/herself.
- Verify that the receiving party is able to assist.
- Connect the customer to the receiving party in a three-way call and introduce the customer.
5.6.10 List the steps to closing a call
- Summarize—use the customer’s name and summarize the incident or service requests resolution. Confirm that the incident/service request has been resolved to the customers satisfaction.
- Ask if the customer has any other questions
- Thank the customer—use a standard closing and thank the customer for contacting the support center.
- Allow the customer to hang up first.
- Document—provide written confirmation to the customer and update the incident or service request documentation with the appropriate information.
5.6.11 List the benefits of customer management
- Optimized talk time
- Faster incident resolution times
- Improved support center productivity
- Establishing credibility for the support center
- Increased confidence of the representative
- Enhanced image of the support center in the mind of the customer
- Increased level of customer satisfaction