0% found this document useful (0 votes)
18 views3 pages

SAP Support Protocol Guidelines

The support protocol outlines that experts must address customer queries via chat in the Ticketing Tool, rerouting requests for calls or screen sharing to SAP. It specifies Service Level Agreements (SLAs) for response times and actions, as well as penalties for breaches of KPIs. Additionally, it emphasizes the importance of compliance, documentation, and best practices to maintain the integrity of SAP support services.

Uploaded by

Mohit Singh
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
18 views3 pages

SAP Support Protocol Guidelines

The support protocol outlines that experts must address customer queries via chat in the Ticketing Tool, rerouting requests for calls or screen sharing to SAP. It specifies Service Level Agreements (SLAs) for response times and actions, as well as penalties for breaches of KPIs. Additionally, it emphasizes the importance of compliance, documentation, and best practices to maintain the integrity of SAP support services.

Uploaded by

Mohit Singh
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd

Support protocol

Experts (Consultants) will address customer queries strictly via chat communication in the
Ticketing Tool. In cases where a customer specifically requests a call or screen sharing
session, we are required to reroute the ticket back to SAP for further handling, as direct
verbal or screen-sharing interactions are not within our current support scope.
SLA
Stage Trigger Timer Expert Action
IRT Expert clicks “Claim” 2 Respond in chat with a solution or
(Initial Hours probe the customer. Mark
Response “Waiting on Customer”
Time)
ORT Customer replies to 24 Respond within 24 hours with
(Operational reopen the ticket Hours clarification or next steps.
Response
Time)
MPT Ticket reopens again 48 Final resolution attempt within 48
(Max. after ORT Hours hours. Reroute if the issue persists
Processing or is out of scope.
Time)
REROUTE Lack of access, not able Immedi Reroute immediately at any
to solve customer ate point if the issue is beyond your
requests for call, scope or guidelines require it.
Customer wants to
share desktop, may
require action from
another team
Auto-Close No customer reply after 21 Ticket auto-closes. No further
"Waiting on Customer" Days action is needed unless customer
reopens it later.

Penalties: Any breach exceeding 10% across defined KPIs will result in a flat 5% deduction
from the total billed amount.
Security, Access & Ethics
 Experts must maintain the confidentiality and integrity of SAP systems and
processes.
 S-User ID access is provided only after onboarding and is required for SAP_Resolve
experts.
 Any misuse of credentials or account-sharing results in immediate termination from
the program.
Compliance, Documentation & Best Practices
 Provide only SAP-sanctioned documents (KBAs, S-Notes, SAP Help Links) when
suggesting system-impacting actions.
 Never refer to or use third-party file/image sharing sites.
 Avoid excessive troubleshooting or vague responses—if uncertain, reroute instead
of risking incorrect solutions.
Do’s
Best Practice Description
Reroute Immediately When Reroute tickets if you lack access, are stuck, SAP
Needed action is needed, or the customer requests
escalation.
Do Not Hold Tickets If unable to resolve, reroute without delay. Never
skip or hold tickets unnecessarily.
Read the Ticket Carefully Understand the issue thoroughly before
responding to avoid confusion.
Provide Clear, Helpful Responses Always explain your suggestions. Share SAP KBAs
or Notes with context, not just links.
Follow SAP Guidelines Strictly Ensure compliance with SAP’s support protocols
and documentation standards.
Help Maintain Quality Report ticket mishandling or violations through the
appropriate channels.
Reminder: These practices uphold the integrity of SAP support services and ensure timely,
effective resolutions for customers.
Don’ts
The following are common reasons for ticket quality failure and must be strictly avoided:
Violation Type Description
Misunderstanding the ticket Responding without fully grasping the issue.
Incomplete or inaccurate response Providing partial or incorrect solutions.
Failure to reroute when needed Not escalating or rerouting when appropriate.
Mishandling due to negligence Careless actions or missing critical details.
Poor communication or tone Using unclear, unprofessional, or inappropriate
language.
AI-generated content violations Use of unauthorized AI content or tools.
Note: All consultants are accountable for quality, accuracy, and professionalism. Repeated
violations may result in removal from the program.
Consultant Declaration
I, the undersigned, confirm that I have read, understood, and agree to comply with the SAP
OSS Platform Scope of Work, SLA guidelines, protocols, and rules described above. I
understand that failure to adhere to these standards may result in termination from the
engagement.
Consultant Name ___________________________
Module Expertise ___________________________
Date ___________________________
Signature ___________________________

Common questions

Powered by AI

When an expert claims a ticket, they must respond within 2 hours with a solution or further probing under the Initial Response Time (IRT) criterion. If the ticket is reopened by the customer, the expert must reply within 24 hours, providing clarification or the next steps under the Operational Response Time (ORT) criteria. These steps are designed to ensure timely resolution while adhering to service level agreements .

The support protocol defines that if there is no customer reply after an expert has marked a ticket as "Waiting on Customer," the ticket will auto-close after 21 days. This mechanism handles customer engagement lapses by closing the ticket without further action unless the customer reopens it later, thus maintaining workflow efficiency .

To successfully adhere to SAP's support protocols, a consultant must read, understand, and agree to comply with the SAP OSS Platform Scope of Work, SLA guidelines, protocols, and rules. This involves maintaining a commitment to quality, accuracy, and professionalism, being aware that failure to adhere may result in termination. The consultant must also document their module expertise and formally sign the declaration to confirm compliance .

If a ticket involves a customer wanting to share their desktop, the stipulated action is to immediately reroute the ticket as such requests fall outside the current support scope. This aligns with the overall handling guidelines, which prohibit direct verbal or screen-sharing interactions and ensure issues beyond the expert's scope are escalated appropriately, preventing unauthorized interactions and maintaining protocol compliance .

Consultants are encouraged to read the ticket carefully to understand the issue thoroughly before responding. They should provide clear and complete responses, sharing SAP KBAs or Notes with context rather than just links. If the consultant is uncertain about the solution, it is best to reroute the ticket instead of risking incomplete or incorrect solutions, thus avoiding misunderstandings .

Experts are expected to maintain compliance with SAP's support protocols by providing only SAP-sanctioned documents such as KBAs, S-Notes, or SAP Help Links when recommending system-impacting actions. They must not use third-party file/image sharing sites and should avoid excessive troubleshooting. Clear and context-explained responses must accompany suggestions to avoid misunderstanding. Moreover, experts must adhere to rerouting guidelines and report any ticket mishandling through appropriate channels to help maintain quality .

The mishandling of SAP system credentials, such as misuse or account-sharing, carries serious ethical implications including immediate termination from the program. Consultants are required to manage their credentials responsibly, ensuring they do not share their S-User ID or any access information. Proper management upholds the confidentiality and integrity of SAP systems and processes, aligning with stipulated ethical guidelines .

Tickets must be rerouted back to SAP when a customer specifically requests a call or screen sharing session, when the issue is beyond the expert's scope, requires action from another team, or when the expert lacks access or is unable to solve the request. If these rerouting protocols are not followed, consultants risk breaching SLA guidelines, which could lead to penalties such as a deduction from the total billed amount if breaches exceed 10% across defined KPIs. Additionally, failure to comply may result in termination from the program due to quality failures or negligence .

Reporting ticket mishandling or protocol violations is critical as it helps maintain the integrity and quality of SAP support services. It ensures that all interactions uphold strict compliance with guidelines, thereby fostering trust and reliability in the support provided. This contributes to consistent service quality by addressing procedural gaps, preventing recurring errors, and facilitating continuous improvement .

The use of unauthorized AI content or tools in the support process violates compliance standards and can lead to serious consequences such as repeated violations resulting in removal from the program. This underscores the requirement for all consultants to uphold quality, accuracy, and professionalism in their interactions and content generation as per SAP guidelines .

You might also like