Managing Support Portal Cases

Case Management Process

The Campus Support process begins when the Authorized Contact presents a problem or request that they were unable to address using the self-service options available on Campus Community (24/7 online portal). Campus Support utilizes an online case portal and phone support to assist Authorized Contacts.

1. Submit a Case

Authorized Contacts initiate support by submitting a case via the Support Case Portal.

  • Select the correct case type and indicate the module—this helps route your case to the appropriate team.
  • Provide a detailed description of the issue - “A problem well stated is a problem half solved” 
  • Include replication steps
  • Indicate urgency, impact, and due dates for time-sensitive issues.

Note: For critical issues, the Authorized Contact should follow up with a phone call after submitting the case.

2. Case Review & Troubleshooting

Campus Support reviews the case, investigates the issue, and works to identify the root cause through replication and analysis.

3. Resolution & Pending Status

Once a solution is provided:

  • A written resolution is posted in the case.
  • The case is placed in pending status for customer verification.
  • To ensure resolution, a 3x10 process is followed:
    • Support will follow up up to three times within ten business days.
    • If no response is received by the tenth day, the case will be closed.

4. Case Closure

  • If the issue is resolved, the Authorized Contact should close the case.
  • If no response is received within 10 business days, Support will close the case.
  • Cases can be reopened within 60 days if additional help is needed.

5. Ongoing Communication

All case activity is documented in the Case Portal. Authorized Contacts can:

  • Communicate directly with the assigned advisor
  • Add comments or attachments at any time

6. Case Visibility

All Authorized Contacts within a district can:

  • View all open and closed cases
  • Comment on any case submitted by their district

7. Incident Notifications

If a broader issue is impacting your district:

  • A status banner will appear in the Support Case Portal with updates and instructions.

Incident Reporting and Issue Qualification

At Infinite Campus, we are committed to delivering products that meet the evolving needs of our customers. When issues are reported, our Campus Support team conducts thorough testing and replication to determine whether the issue is isolated or indicative of a broader product defect.

If an issue is qualified as a product defect, it is promptly escalated for triage and resolution in accordance with our established Service Level Agreement (SLA) timelines.

  • Critical defects are addressed quickly through fixes delivered in Rx packs.
  • Minor defects are resolved and included in upcoming product updates.

To ensure transparency and effective communication, each confirmed defect is linked to a unique Product Development issue number and updated within our case management system to reflect its assignment to the Development team.

Once a defect is resolved, Authorized Contacts are notified via a case note and a status change indicating availability in the next release. These corrections are also documented in our Release Notes and published on Campus Community for each release, ensuring clear and consistent communication.

Triage and Maintenance 

An initial review of each issue is done to determine the potential for immediate and future customer impact. An impact assessment can include, but is not limited to, consideration of the following:

  • Level of disruption to customer workflow
  • Inability to perform daily functions
  • Existence of a viable workaround
  • Multiple schools/districts are affected by the issue
  • Multiple users are directly impacted

During the impact assessment review, each issue is thoroughly verified to determine its potential impact. Issues classified as critical, high-priority, or serious regressions in functionality are assigned the highest priority, with resolution efforts initiated immediately to ensure a swift response.

Escalation Guidelines

Our escalation process is designed to be transparent and customer-focused, ensuring that clients are kept informed throughout the resolution journey. While our goal is to resolve cases without escalation, approximately 70% of cases are successfully handled at the initial support level.

If escalation becomes necessary, we follow a clearly defined path to ensure timely and effective resolution. Authorized Contacts are notified of the escalation via a note added to the case.

To resolve escalated issues, Campus Support works collaboratively with teams across Managed Services, Training, Process Consulting, and Development. This cross-functional approach ensures that escalations are addressed accurately and efficiently.

For issues related to product defects, we follow a structured process of replication and testing across multiple environments to validate the defect. Once confirmed, the case is linked to a development issue for ongoing tracking and resolution.

When a product defect is resolved, Authorized Contacts are notified through a case note and a status update to "Available in Release." An email notification is also sent to ensure clear and timely communication.

Case Search

The Support Portal provides Authorized Contacts access to view and post comments on all cases for their district. A list of all cases is presented by default when selecting Cases > View Cases from the dropdown list. Cases are sorted by last modified date and columns can be toggled to quickly sort by status, modified date, module, etc.


Displayed cases may be refined by clicking on the funnel icon to display filters. Using multiple filters will narrow the results, only returning entries that meet the requirements of each entered field. For example, searching for "Grade Book issues" (Subject) created by a selected contact will only return cases matching both of those instances, while only entering "Grade Book issues" in the Subject field will return issues entered by all users.

When available, use the dropdowns to further refine your search. For example, Subject may be filtered using Equals, Not equals, Starts with, Ends with, Contains, and Does not contain. 

Screenshot of the View Cases tool with a callout around the Funnel icon in the top right.

The following fields are available.

OptionDescription
Case Number
Standard
Enter the number assigned to the case when it was created.
Subject
Standard
Enter the title of the case or a keyword that can be used to locate the case. Entering a phrase like "grade book issues" might not return results, but "grade book" will. 
Status
Standard
Indicates the status assigned to the case. Also see the Case Status Workflow.
Options are: 
  • New - case has been created but not yet assigned to a Campus support resource. 
  • Assigned - case has been created and assigned to a Campus support resource. 
  • Assist Request - case is pending the input of an internal Campus resource. 
  • Pending Customer Input - case requires additional information from an Authorized Support Contact in order to seek resolution. 
  • Pending Customer Verification - case resolution is awaiting final confirmation from the Authorized Support Contact.
  • Scheduled - action required to meet request has been scheduled to take place on a future date, such as a planned training. 
  • Assigned to Development - case has been escalated for Campus Development to modify functionality in the product. 
  • Closed - case has been resolved, meeting the needs of the user and marked as complete by your Campus support resource. 
  • Available in Release - issue reported in the case has been developed and is available in a Campus Release Pack. 
  • Re-Opened - previously closed case has been re-opened by the customer and is awaiting further assistance from a Campus support resource.
PriorityIndicates the level of urgency associated with the case. Options are: 
  • Critical - Campus is not operational
  • High - Inability to perform a time-sensitive task
  • Medium - Usable, but functionality is affected
  • Low - Questions, advice and training-related issues
ModuleSelected option relates to the area of Campus where the issue is occurring. 
Case TypeSelected option indicates the type of case that was entered. Options are:

  • Ask a Question
  • Application Issue
  • Data Restore
  • Modify Support Contacts
  • Report an Outage
  • Server/Hardware
  • Server Access
  • Request Training
  • Request Consulting
  • Request Technical Services

The category on a case is automatically populated based on the screen the case is completed.

ContactThe Authorized Support or Technical Contact assigned to the case.
Last Modified Date that the case was last updated or last communicated on.
AccountName of the district that submitted the case.

Search Results

The number of Results returned is displayed at the top of the Cases window. The number of cases returned per page is automatically set to 20. This number can be changed by updating the Page Size value that displays at the bottom of the cases list. When this value is changed, the number of pages also changes. Advance to a new page in the search results by choosing a new page number under the Page dropdown.

Screenshot of the Page and Page Size options at the bottom of the View Cases screen.

Viewing and Communicating on Cases

Clicking on a Case Number will open it to view, add attachments, communicate with Support, or close.

Screenshot of the View Cases tool with a callout around Case Number 1227944 in the far-left column.


Screenshot of the Case screen that opens when a case number is selected from the View Cases list.

The top panel of a case displays important information including its Case Number, Priority, Status in its life cycle, who in Support the case is assigned to, and its last modified date. Cases may be closed (or re-opened) using the button at the top.

 Screenshot of the top panel of the Case screen.


Case Details on the right side of the screen includes the information provided by the contact at the time of case creation, and/or case qualification information added by Support. 

All attachments (added by the district or Campus) display in the Attachments area for easy access.  Click on the text Attachments to expand the box and view additional details.

Screenshot of the Case Details section, located on the right-hand side of the Case screen.

Written case communications between Authorized Support Contacts and Campus are called Posts.  Posts display in the case's Feed with the most recent at the top.  Posts may be searched using the "Search this feed" box.

Screenshot of the Post section with a highlight around the Search field.

To add a Post to a case, click into the Post box that says "Share an update". An editor box will appear. Type your message into the editor and hit Share to submit. Note that you may format your text, add bullets or numbers to your steps, or add saved images directly into your Post. The paperclip icon may also be used to attach files to your post. Up to 10 attachments can be added at the same time. Max file size is 15MB.

Screenshot of the Post editor that displays when you click the Share an update field.

Manage Notification Recipients

The Manage Notification Recipients tool allows districts to manage who receives notifications on a case. All Authorized contacts (Support, Technical, and Implementation) who have access to modify cases can see this tool and be added or removed as a recipient. Read-Only contacts can also see this tool, but they can only add or remove themselves as a recipient.

The Manage Notification Recipients tool for Support Contacts:

Screenshot of the Manage Notification Recipients tool for Support Contacts..The Manage Notification Recipients tool for Support Contacts

To add a Contact as a notification recipient: 

  1. Click Add
  2. From the contacts list, select which contact(s) to add and click Next. Non-contacts and Read-Only contacts are not listed. If the district would like to create a new contact, select the Modify Support Contacts link to submit a case.
  3. Confirm the contact(s) to add and click Next.
  4. Once the contacts have been added successfully, click Finish.

To remove a Contact as a notification recipient: 

  1. Click Remove.
  2. From the contacts list, select which contact(s) to remove and click Next. The case owner cannot be removed as a notification recipient and will not be listed as an option.
  3. Confirm the contact(s) to remove and click Next.
  4. Once the contacts have been successfully removed, click Finish.

The Manage Notification Recipients tool for Read-Only Contacts:Screenshot of the Notification Recipients tool for Read-Only contacts.The Manage Notification Recipients tool for Read-Only Contacts.

To add or remove a Read-Only Contact as a notification recipient, click Add me to notifications on this case or Remove me from notifications on this case.

Case Status Workflow

The following workflow demonstrates how a case moves through our system.