Using the Khoros Community Case Portal
This article refers to Khoros’s own implementation of the Case Portal within the Khoros Atlas Community. To access the Atlas Case Portal Register for Khoros Atlas using the email address you log into the Khoros Platform with, and follow the email verification steps. Once registered and verified, email support@khoros.com and provide the following information: Full Name Email Address Khoros Atlas community username Whether or not you will need access to all of your organization’s cases. What environment/Khoros product you will need access for You will receive a confirmation email once the team has granted you with access, at which point you will be able to access the Case Portal. Creating a New Case Click Create Case. 2. Fill out the form, including as much detail as possible, attach screenshots where relevant, and save your Case. Looking for an existing case Go to the main Case Portal page to view all open/resolved cases that you personally created. From here you can both search for your case by Case # or subject, and review the status and last response for each Case. If you requested access to the organization's cases, you can view them by clicking on 'Account Cases' Managing Existing Cases Click on the title of an existing case. 2. To Reply to the Case, scroll past the Case Details sections to the thread of comments beneath. Add a new Comment to reply and update the Case. 2. ToClose a Case, click Close Case at the top right corner of the page. Additional Information Guide to reporting issues Troubleshooting the Atlas Case Portal If you experience any issues while navigating the Case Portal, please submit a new Case and the team will investigate. If you are unable to submit a new case, please contact support@khoros.com with details of the issue you are experiencing.Escalating Support Cases
Considerations before escalating In Khoros’ support case portal, you can set or change the "Customer Priority" field between low, medium, and high. When issues are urgent, changing the priority to "high" will push them up the list of issues based on your support level. One practice to avoid is creating a support case and escalating it the same day. Same-day escalations are generally pushed back to allow the team to go through the standard support triage process and gather all necessary information before bringing in other experts or teams. Shortcutting tends to be disruptive to that process and introduces further delays. While it is essential to stay in close contact with your account team, we strongly recommend bypassing them for escalations and instead escalating directly via Khoros’ support chatbot, Maia. Ad-hoc escalations create back channels and can duplicate efforts, resulting in delays or confusion. Customer success managers are also automatically informed about escalations, so they will be aware. When should I escalate? You should escalate a support case when there is urgency involved. 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 a severity 1 issue SLA missed for first response Unresponsive or lack of updates in a case Although Khoros endeavors to keep it to a minimum, there may be times when escalated issues are not accepted as valid escalations. Decisions about 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 that qualifies as outage severity should continue to go through the standard outage process of emailing outage@khoros.com or setting the case severity to "1." When can I escalate? All severity 1 cases (outages) are automatically escalated to our Mission Critical Support team and thus do not require further escalation. Cases submitted through email or the case portal with a lower severity rating can be escalated. We recommend allowing the support team 24 hours to review the case before escalating. Can I escalate outages? All severity 1 issues are considered outage level, and it's unnecessary to escalate since an on-call team is available 24/7/365 for issues that qualify. Severity 1 cases are already at the highest and most visible level possible. How do I escalate a support case? You can escalate a case by opening Maia (in-app chat or via Atlas) and typing ‘escalate a case.’ Maia will ask a few questions: Enter your case number Reason for escalation (select one): time constraints, lack of updates, defect resolution time, missed SLA, security concern Number of users impacted: (select one) single user, less than 50% of users, more than 50% of users Explain how this issue impacts your business operations Would you prefer a live call to share the latest update on this escalation? (select one) Yes, No All escalation requests will go to an active queue, which our shift supervisors and managers will acknowledge and review to determine the next steps. All further updates will be provided directly in the case.How do I close a support case that's been resolved?
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.Guide to reporting issues
So you've launched a subscription with one of our products and ran into an issue or have a question that you couldn't find the answer for on this community. Don't fret - we've got you covered! It's our mission to ensure your support experience is seamless and effortless. If you have access to the Case Portal, you might have noticed a lot of fields on the new case submission page. Why is all of this information necessary / required? We understand that noteverything you submit to us will merit this information. For example, if you have a simple request or a question, providing steps to replicate or describing the expected and actual behavior may not be relevant. However, the more information you can provide from the start, the faster your experience will be. For all service requests, whether to report a defect or simply a question, there are some fields that will help us solve for your query more effectively. Subject - Just a brief summary, a tweet if you will, about the request Description - Here's where your novel goes, with the entirety of the request Customer Priority- By default, this is "normal" but sometimes there's a High or Low priority request. These should be compared to your others, meaning 90% of your request would typically be "Normal" in priority. Severity- These are contractual levels, but take a look at our Support Page for some definitions. This is a field you can't change once submitted, but our support team can if appropriate. When reporting a defect or issue to Khoros Support, please provide the following information: URL of Khoros Product and/or URL(s) of where the problem occurs Steps to Reproduce Expected Behavior Actual Behavior Browser and OS Username, Roles, or Ranks When asking a question or making a request to Khoros Support, please provide the following information: Subject Description / Request / Question URL of Khoros Product Providing the above will eliminate the chance for any confusion or unnecessary back-and-forth that may lengthen the time your case stays open. On a final note, a picture is worth a thousand words - if you're able to attach screenshots to your case submission, it will be extremely helpful to the team in getting your case moved along even faster. And if a picture is worth a thousand words... a video is worth a million! If the issue you're experiencing is intermittent or rather involved, capture it on a quick video. There are several applications out there that offer video capturing of your screen - Jing is a great free tool to try and works on both PC and Mac.How many users are we entitled to get access to the Case Portal?
Question How many users are we entitled to get access to the Cases area? Answer Standardcustomers are allotted 5 case portal seats. Premiumsupport customers are allotted 10 case portal seats. If you need to add/remove any users (the latter to make way for new additions), please follow the process outlined in our case portal activation guide. Note: If you have more than one community, you can spread the "users" as desired. For example if you had two Premium Support communities, you could potentially have 8 users for Community A and 2 users for Community B.Cases Activation and Deactivation
Question How can I activate/deactivate users to view and submit cases through the case portal? Answer To activate a case portal user, please create a case by emailing support@khoros.com and mention that you want to ACTIVATE this user: Full Name Title Email Address Phone Number 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 support@khoros.com and mention that you want to DEACTIVATE this user: Full Name Email Address Khoros Community Username (link to profile is preferred) Community and/or AccountAbout the Aurora Case Portal
After you set up the Salesforceintegration with your community, you can activate the Case Portal within the community. The Case Portal enables members to: Create Support Cases directly from the community. Correspond with Support agents on cases via case comments in the community. Cases can be discussed in public and private areas of the community. Access their open and resolved cases from a private community page regardless of where that case originated. For example, you might have created several support cases via different channels (phone, email, Facebook, Twitter, and/or the community). The Case Portal enables you to access and respond to all of your cases regardless of how they were originally opened. In the Case Portal, all the interactions between the Support agent and the user are captured in threaded conversations. To enable Case Portal for your instance, open a Support ticket. After the Case Portal is enabled in your community, you can set it up by performing these tasks: Enable and configure the Case Portal in Community Admin Set up Case Portal permissionsAurora: Enable and configure Case Portal
Prerequisite Case Portal must be enabled for your Community to complete this procedure. If you need Case Portal enabled for your instance,open a Support ticket. To enable and configure the Case Portal: Sign in to the community as an Admin. Open the Account menu and click Settings. Go to Features > Salesforce. Go to Case Portal Integration and configure the following: Case Portal: Turn on this option to enable Case Portal in the community. You must have a valid integration with Salesforce CRM to use this feature. Case creation: Turn on this option to enable members to create support cases from the Case Portal. Case update: Turn on this option to enable members to update a case. API error messages: Turn on this option to allow users to see the actual error messages generated by the CRM instead of generic error messages. Case portal field customization options: CRM Fields to include as filters in the Case Portal: Specify the names of the CRM fields that you want to configure as filterable columns in the Case Portal page. Modifiable fields when editing cases: Specify the names of the CRM fields that you want to configure as fields that can be modified in the Case details page. Note: You must turn on the Case Update option to modify the configured fields in the case details page. Custom fields in case creation form: Specify the CRM fields that you want to configure as a fields in the Create Case page Custom fields in case view:Specify the CRM fields that you want to configure as a fields in the Case details view page. Case list custom columns:Specify the CRM fields that you want to configure as a fields as a column in Case Portal page. Close case settings: Close Case form status field: Enter a comma-separated list of statuses to be displayed in the Close As status field. These entries must match entries in your CRM. Close Case form comment field: Enter a comma-separated list of values to be displayed in the Comments field. These values can be anything you want to reflect close reasons. For example, “Found my answer” or “Agent fixed my issue.” Query parameters override: Account cases: Enter a SOQL custom query WHERE clause to override the default query or comma-separated parameters to append to the existing query to display specific cases to Supervisors in the Case Portal. If left blank, the Case Portal shows the default Supervisor cases. My cases: Enter a SOQL custom query WHERE clause to override the default search query or comma-separated parameters to append to the existing query to display only specific cases in the Case Portal. If left blank, the Case Portal shows the default list of cases. 4. Click Save.Aurora: Create a support case in the community
From time to time, members may encounter issues or have queries related to your product or service and need assistance in resolving them. If you community uses a Case Portal, members with the Create new support case permission can create a new support case to address any issues, queries, or requests related to the product or service. The Support team reviews the submitted cases and assists in resolving them. Note: The Create Case option must be enabled in the Salesforce settings to view this option in the Case Portal. To create a support case: Sign in to the community as a member withCreate new support case permission. Open the Account menu and click My Support Cases. Note that you must have the Read and reply to own support cases permission to view this option. The Case Portal page opens. Click Create Case. The editor window opens. Enter the Title of the case and Describe the issue. (Optional) In the Attachments, click Add an Attachment to attach a file. Click Submit. Update support case You can update an existing case to provide additional information, track progress, or address ongoing issues. Note that the Case update option must be enabled in the Salesforce settings to view this option in the Case details page. To update a support case: From the Case Portal, go to the case you want to update. From the case details page, click Settings > Update Case. The Update Case window opens. Update the required fields and click Save.Aurora: View support cases in the community
In the community, the Case Portal lists all the cases that are created by members via different channels (phone, email, Facebook, Twitter, and/or the community). The Case Portal option must be enabled in the Salesforce settings to view the support cases. Members with the Read and reply to own support cases permission can access the Case Portal to view their own support cases: The page lists: Case No.: The unique identification numbers for each case. Title: The titles for each case. Status: The current status of each case. Origin: The source through which the cases were created. Created On: The date on which each case was created. Last Update: The date on which each case was last updated. You can sort the cases based on Last Update. You can further filter cases based on View,Keyword, Status, and Origin: To view support cases in the Case Portal: Open the Account menu and click My Support Cases. Note that you must have the Read and reply to own support cases permission to view this option. The Case Portal page opens. To view the details of a case, click the Title of the case. The case details page opens. From the case details page, you can update or close your case. You can also reply to your own cases: Related topics: Create a support case in the Community Update or close support cases from the Community Set case portal permissions
