Some tips before escalating
In the case portal, you have the ability to set/change the "Customer Priority" field between low, normal and high. When issues are urgent but not necessarily world ending, changing the priority to "high" will push it up the list of issues based on your support level, which is a good way to get support's attention to an issue.
One thing to avoid if possible is creating a case and escalating it that same day without a strong reason. Same day escalations are generally pushed back on to allow them to go through the standard support triage process and gather all necessary information before bringing in other experts or teams, but short-cutting tends to be disruptive to that process and introduces further delays.
While it is important to stay in close contact with your CSM or account rep, we strongly recommend bypassing them for escalations and instead escalating directly via the case portal. Ad-hoc escalations create back channels and can duplicate efforts, which has resulted in delays or confusion around escalations. CSM's are also informed around escalations automatically, so they will be aware.
When should I escalate?
You should escalate when there is urgency involved in a support ticket. This would include issues such as, but not limited to:
Time constraints (SSL cert expiring, deadlines, events, etc.)
A major impaired function that does not qualify as an severity 1 issue
SLA missed for first response
Unresponsive or lack of updates in a case
While we'll do our best to keep it to a minimum, there will be times when escalated issues will not be accepted as an escalation. If/when that happens, an automated reply will be sent to inform the user who originally escalated the case. Decisions around escalations are entirely at the discretion of the team responsible for escalations.
Additionally, the escalation feature is not designed to replace the outage alias. Any issue which qualifies as being of outage severity should continue to go through the standard outage process of emailing email@example.com or setting the case severity to "1".
When can I escalate?
The option to escalate a case is available to all customers. However, there are restrictions in place to reduce the number of same-day escalations, and give front line support time for due diligence. Please note that these times are subject to change, but currently leverage support tier.
Can I escalate outages?
All severity 1 issues are considered outage level and it's not necessary to escalate since an on-call team is available 24/7/365 for issues that qualify. S1 cases are already at the highest and most visible level possible.
How do I escalate a support case?
After a case has been created, the option to escalate it will be available. Simply open the desired support ticket within the Case Portal and click Escalate Case located under the case details near the bottom left-hand corner.
A new form displays along with some details and instructions. On that form, provide a summary of why the case needs to be escalated to an Escalation Manager for review within 4 business hours.
After you've filled out the escalation summary and submitted the request, an alert is sent to an Escalation Manager for review. An Escalation Manager will review the request and reply directly in the case you escalated with a decision or plan of action.
What if I'm not satisfied with the current escalation decision or progress?
Should you be unsatisfied with the results of your case escalation, you have the option to go up a higher level by clicking the "Escalate Case" button again. When the "Escalate Case" button is used again, you'll be presented with a different form acknowledging the next-level escalation and again requesting you provide an explanation around the reason for escalating again / higher. Once submitted, an Escalation Manager will review the request and respond directly within the escalated case.
You can perform this process multiple times. The higher the escalation, the more members of Leadership or Management will be involved. Here's a breakdown of the various levels and what occurs:
Level 1: The case is escalated to our support leads and front line managers.
Level 2: All of the previous team is alerted, but the escalation is extended to the head of global technical support for the relative product and your account's Customer Success Manager (CSM).
Level 3: All of the previous manager groups from Level 2 are alerted, but in addition, the Senior Director of Global Technical Support will be included. A full root cause analysis will be completed to understand why this case needed an escalation to this level.
Level 4: All of the managers from Level 3 are alerted, but VP of Support is also alerted and will take personal responsibility to drive through to completion.
Khoros is committed to providing ongoing coverage regardless of natural disaster or crisis (regional or global). Our customers need to be able to work with our team regardless of the situation or region. Therefore, our support organization is prepared and built with redundancy to absorb any short term impact from unpredictable causes.
In the event that any individual Khoros office is impacted by a threat that results in the actual or effective shutdown of said office--for example, from potential Coronavirus impacts--we have the following contingencies in place for all products and levels of support, including Technical Account Management, Severity 1 Outage, and standard support:
Support is located in a number of locations including Austin, Bangalore, London and Portland. Any location may be called up to work 24/7/365 to cover for an office that is impacted.
In addition to our office locations, we have remote staff members that can be deployed to work 24/7/365 to augment existing offices.
Work From Home
All locations are empowered to immediately enact a temporary work from home policy, allowing our entire support staff to continue to work with limited impact.
We will continue to evaluate the need for any additional contingencies based on business or customer requirements.
Hours of Operation
On Severity 1 Service Incidents, Khoros hours of operation are 24/7/365. For all others, standard hours of operation for Khoros Support are as follows:
6 AM – 6 PM PST
6 AM – 6 PM PST
7 AM – 6 PM GMT
11 PM - 10 AM PST
7 AM – 4 PM IST
5:30 PM – 2:30 AM PST
Additional hours of operation are available with additional support levels or on some grandfathered agreements. Coverage for major holidays, as defined by Khoros regional support, is limited to Severity 1 issues only.
Observed Holidays for 2020
New Year’s Day
Martin Luther King Jr. Day
Day after Thanksgiving
Christmas Eve (observed)
New Year's Eve
New Year’s Day
Easter Monday Bank Holiday
Early May Bank Holiday
Spring Bank Holiday
Summer Bank Holiday
New Year’s Day
Mahatma Gandhi Jayanti
Take special note to the holidays based on your location, as they may differ from public holidays in your specific country.
Example: If your organization falls within the EMEA region (including, but not limited to UK, France, Germany, Switzerland), all days listed under EMEA are holidays Khoros Support will be observing during 2018.
Standard support coverage will resume on the next business day.
Note: We're prepared to support any severity level 1 issue all year round, 24x7x365. Should the need for this arise, be sure to include the nature of the service outage or security risk, a link to the impacted environment, and your contact information. To receive severity 1 support at any time, email firstname.lastname@example.org.
We know that there are events that specific communities consider "major" for their business -- whether this is the Superbowl , Black Friday/Cyber Monday, a live event, a new product launch, a relaunch of your design, a demo for executives, or any one of a dozen other scenarios, it is our goal to work with you to ensure that events are as seamless as possible.
Khoros is committed to ensuring that you are supported 24/7/365 on any outages. We have a comprehensive guide to outages and information about our general status page available for you to take a look at, but the summary of this is that if you or your customer's are down or unable to work, let us know and we'll quickly take a look to see what's going on! You can always keep up to date on our status page where we do our best to provide insight to outages impacting multiple customers.
Assuming you know ahead of time that you have a major event coming up, please let us know as early as possible - at least a week - if not more - is ideal! Although we have monitoring in place to help mitigate issues as best as possible, the best situation is where we can proactively review allocated resources, your server side setup, and make sure that there simply aren't any issues!
If you have a Technical Account Manager via Premium Support or CSM, please make sure that they and Support are aware of your impending event so that they can pay attention to it. If you don't, don't despair! Open a support case letting our team know that you have an event coming, what the date and time of it is and that you'd like us to take a look to see if there's anything that needs to be done to help prevent an impact on you or your customers. If you can add Proactive to the case subject, it'll help us organize the solution as well. Depending on need and contracted level of support, this may require some additional conversations to figure out what is necessary to help you be successful.
The above applies to whether you're a Care, Communities, Marketing, or JX customer!
We've updated the status page to provide more specific and targeted information regarding the topics that you care about. This allows us to also be more proactive in order to provide the necessary details to you, our customers, about what is occurring on our servers, APIs, or functionality within the product lines. It is our goal to continue to improve this communication and we are happy to continue to receive feedback.
What's the URL?
What does this provide?
You'll receive an email or SMS about new investigations, monitoring, or resolutions as they occur based on your preferences and selections. It is the best way to be proactively notified about any problems across the Khoros product lines.
Who should sign up?
Anyone that's interested in keeping up to date about our infrastructure should be signed up. This includes administrators, community moderators, Care supervisors, or even agents who are expected to respond to customers! It is always great to know what is going on with the tools being used and this is the place to get that information.
Won't I get spammed?
We update this page only for relevant information and you can select the subcategories to be notified about. By default, everything is checked but there may not be any need for you to be notified on Communities API if you're only using Care in your business (even if we think you should use both!).
How can I activate/deactivate users to view and submit cases through the case portal?
Note: Customers under the Silver support tier will not have access to any case portal users. For a breakdown of each tier, refer to our support data sheet.
To activate a case portal user, please create a case by emailing email@example.com and mention that you want to ACTIVATE this user:
Khoros Community Username (the user must be registered on this community first)
Community and/or Account
To deactivate a case portal user, please create a case by emailing firstname.lastname@example.org and mention that you want to DEACTIVATE this user:
Khoros Community Username (link to profile is preferred)
Community and/or Account
When you have an open support case, you will be able to see a new button on the case details page with the option to Close case.
Once you are happy that your support case has been resolved you can click on the button, which will trigger a popup box confirming that you would like to close out your case with the support team.
Once you have closed your support case you will be able to find it in the Resolved tab in the Case Portal.
Note: If you wish to let us know why you are closing your case, please feel free to leave a comment on the case before closing. You may also receive a survey after the case is closed.
What information should I provide to Support if I am having performance issues?
When diagnosing performance issues, it is extremely helpful to have the following information:
Product. Which product(s) are you having issues with?
Define slow. What do you mean by 'slow'? e.g. How many seconds/minutes did it take to load a page?
Narrow the scope. Is the slowness specific to any set of browsers/users? Is it everyone at a particular location? Everyone at the company?
Any particular URLs loading slow?
What region do you live in?