Create you Service Request via:
OR
The Escalation Process – Explained
The service request escalation process must be done by telephone! Also, until you’ve spoken to a manager from oracle support, an escalation has not occurred.
Severity increases are different from Escalation request!! Know this!!
3 (I need help) 2 (Help this is causing bigger issues) and 1 (parts of production or all of production isn’t working)
Escalations Manager (usually a shift manager and sometimes an analyst)
Sr. Manager Level Escalation
Director Level Escalation
VP level Escalation
Here’s how it works;
Step 1 – Call Support 1800 223 1711.
You can choose #1 for Existing SR or #2 for New SR.
If you choose #1, you will be presented with the option to either Escalate or speak to an engineer. If you choose to speak to the engineer, most often you’ll get voicemail. Don’t leave a voicemail if you desire escalation – You need to speak with a HUB analyst – or person that takes notes. Remember HUB folks are there trying to help you — also most of the time they are not technical but have an idea of how to be helpful. Let them be helpful. They are like the receptionist at the front office building… Remember you can win more favors with Sugar than you can with spice. Provide all the details they ask for. Talk to them, not at them!
Get your pen handy!
Step 2 – Initiate Escalation: SAY – I would like to speak with and receive a callback from the Escalation Manager. Heads Up – It’s not called the Duty Manager anymore (Escalation Manager). Then provide the explanation as to why your doing what your doing. Write answer to the next stuff down –
- ask who or what is the name of the analyst assigned to your SR
- What group they work in
- What country and time zone do they work in
- What are their working hours and if or when they become on duty. (Its Global Support anymore)
- How many SR’s are they currently working and confirm yours in the highest priority.
- If you don’t like the answers provided and haven’t gotten a call back since you opened the SR… let Oracle know. REMEMBER – This is the ESCALATION PROCESS – The first Phone call of many to come!
- Ask the HUB analyst to ping or sametime the analyst assigned to your SR and get answers for the questions above.
- If they aren’t online – this tells you something (you might be waiting for awhile). Ask the HUB person to find out when to expect your call back.
TIP #1 - I usually follow up my Severity 1 Service request with an immediate call for an escalation manager!
Anyway – your goal is to get someone to call you back – Hopefully an analyst calls you before the Escalation Manager calls you.
Be watching the Service Request at the my oracle support website. — Often times you may not get a phone call or any e-mail from support – or even a call back for that matter. Somebody just put an update into the Service Request asking for a piece of information, and has the service request status of waiting on you.
Even if you speak with an analyst – double check the Service Request online. Analyst will often say they need time to research your questions… I try not to let them off of the phone.
TIP #2 — Ask for an Oracle Web Conference (OWC) – this allows oracle to see what you see. A picture is often worth a thousand words. If you end up having a bug and development needs to see your screen – oracle can screen scrape or record what you have going on.
TIP #3 You must have a game plan in place for how the Service Request is going to be worked.
Nothing bites worse than waiting for hours just to have an analyst ask for a piece of info that takes two minutes to gather.
TIP #4 Ultimately Oracle will ask you for an RDA ouput. I believe this is Remote Diagnostic assistant script output. Provide it via the upload button. Then put a separate entry in the SR asking for what additional information they require – and urge for a phone call back. Follow up with a phone call and let Oracle know you need assistance immediately.
TIP #5 If you have called in more than two times on an SR – and have updated the SR via the web – and you have clearly put the onus of responsibility in Oracle’s court. You’ll get your call back.
Oracle’s internal system does keep track of Service Requests that are unattended. If you called twice and updated twice – something is triggerd internally –letting the Analyst or the analsyst responsible manager know they have Service Requests waiting. If you don’t have a plan of action at the call back —- Its time for the next level of escalation.
Call 1800 223 1711 and let them know you need to speak to a person… Now you escalate the SR beyond the escalation manager. Ask to speak to a senior level escalation manager.
You should get a call back within one hour. However, if your SR isn’t in the correct group at oracle — and you don’t want your Service Request transferred around for hours on end. After that hang up and escalate to the next level. Ask to have the service request escalated to the Vice President level.
- Step 4 – Update the SR – to say you called and ask for an escalation – document in the Service Request that you haven’t been called in X minutes and that your not sure what is going on – or where the hang up is.
Here’s how it plays out:
- A manager will call you back to discuss the technical details and review the Service Request with you. Typically, the first level escalation managers make excuses for your engineers and try to get you to someone else. – Your supposed to give that manager an opportunity to make thing correct. However, typically the don’t have access to the resources to fix your issue. Next tell the manager you want this issue brought to attention of the director. You must say “I am requesting a director level escalation of my Service request”. Chances are this manager doesn’t have the resources you need under his/her control. Let the next level manager do this.
- At this time, discuss any concerns you have. (time to respond, time to resolve, technical direction, key milestones at risk, etc.) Work up an agreed upon action plan and ask for the name of the director that’s call you back – find out when they work and where and when the call back is coming.
- As a customer, document the action plan in the Service Request. Write, “I just spoke to so-n-so and we agreed to the following” The manager should be doing the same.
- Know when the next follow-up will be. Is a follow up phone call necessary? Discuss it.
Managers have control of the resources and time of the support engineers. They may reassign it to someone else on the team. They may free up the time of the current engineer to devote more time to your problem. They will review what can and can’t be accommodated.
DON’T HANG UP with any manager until you know these 3 things:
1-The Manager’s name
2-A piece of contact information from that manager (office phone, cell phone, or email address) Go direct to the source for updates
What if the Service Request has a Bug Associated with it?
Still use the Escalation Manager(s) to get in touch with Development Management.
TIP #6 Ask that only one analyst put entries into the Service Request. Make sure Oracle development knows how this bug is affecting your business.
What if I’ve done what you’ve prescribed and it didn’t work?
Simply call the 800# again, state either the escalation manager you’ve spoken too isn’t able to help you, or the escalation call wasn’t returned, then request to RE-escalate the issue to the next level of management. Go to the top until you get things your way! However, be sure you escalate in the order defined – Oracle won’t allow you to skip an escalation manager.
- Sr. Manager Level Escalation
- Director Level Escalation
VP level Escalation TIP #1 - I usually follow up my Severity 1 Service request with an immediate call for an escalation manager!
Each one of these escalation requires a separate phone call to oracle and a bit of time is wasted between each call. You’ll be working with one analyst – and all they are going to do is — collect information.
TIP #7 – You can have another teammate call in on the Service Request on your behalf and ask to have it escalated. While you are working with lower level analysts.
Say simply – there is no game plan yet and all we are doing is collecting information. We need someone on the phone on a Oracle Web Conference that is capable of collecting data – analyzing data and providing a feasable a solution. The person we are working with is not it. We don’t need to be waiting on three separate people. Senior level escalation managers at oracle can get these “go to people” on the phone for you rather quickly. Just be sure to ask for each of the escalation in the SR at different intervals of time – in-between the support notes and updates.
TIME IS MONEY WITH A DOWN PRODUCTION SYSTEM – YOU ARE PAYING FOR SUPPORT SO GET THE MOST OUT OF IT.