The following steps will walk you through how a Method user creates a case. It is also possible for a customer with access to a portal to create their own case, but the workflow is largely the same. 

Note: All field marked with an asterisk (*) are required.

Create a Case from the Cases App

1. On your Method dashboard, click ⊕ New on your Cases App. You can also click ⊕ New Case when viewing the Cases List. 

2. This opens the New Case screen. There are a number of sections here which we will cover.

  • Contact*: The contact who is having or reporting the problem. Once selected, their QuickBooks name, phone, and email will appear for quick reference.
  • Subject*: A unique title to help pinpoint the case within the list of cases. 
  • Origin*: How the contact first contacted you about the case. Choose from Phone, Email, or Web Portal. From the dropdown, you can also create your own custom origins.
  • Priority: The level of severity for this case. Choose from 1 - High, 2 - Medium, or 3 - Low. From the dropdown, you can also create your own custom priorities.
  • Type: What kind of issue is this case meant to address? Choose the default here from Problem, Camplaint, Feature Request, Question, or Billing Inquiry. From the dropdown, you can also create your own custom types.
  • Case Status: How far along the case is. Choose from In Progress, Escalated, On Hold, or Closed. From the dropdown, you can also create your own custom statuses.
  • Tags: Help categorize the case. For more information, see our article on Using Tags.

3. Below that we have a few more fields to assign and describe the case.

  • Assigned To*: The Method user who is assigned to the case will receive notifications when the contact responds to the case via the portal.
  • Notify the "Assigned To" user when saving: When checked, the Method user assigned to the case will get a notification this case was newly created. The email template used can be set in the Cases app Preferences
  • Notify the contact about the case via email & portal: When checked, the contact will get an email they can view their case in their portal. The email template used can be set in the Cases app Preferences.
    Note: Method best practice says you should always notify your customer that their case is being reviewed, which is why this option is checked by default.
  • First contact resolution?: Check if the case was resolved the first time your staff interacted with the contact. 
  • Description*: A description of the case. Note: This field is visible to customers, so make sure your comments are customer-appropriate before saving.
  • Attachments: Attach any number of files to this case.

4. Method automatically creates an activity when a case is created to log the initial interaction. Change the fields for this first activity as appopriate. For more information, please see our article What is an Activity? 

5. Schedule a follow-up - If this is checked, you can create a second activity to remind the assigned Method user to follow-up with the contact. 

Note: Depending on your workflow, you may either assign this activity to yourself (e.g. contact the customer for more information about their problem) or to another Method user (e.g. to a user in the department that usually handles these problems). In this walkthrough, we will assume you are assigning the follow-up to yourself.

6. By default, the case status is in progress but you can change it using this dropdown. When you are done making your changes, click Save & Edit or Save.

Here's what happens when the case is saved:

  • The case is now visible in the active cases view of your Cases List screen.
  • If specified, an email is sent to the assigned Method user.
  • If specified, the contact also receives an email if that option was chosen. They are given access to their customer portal, where they can view and comment on their case (by filling in the Comment field and clicking Comment).
  • The assigned user receives an email whenever the customer comments:
  • Method automatically creates a closed activity to log the first interaction of the case.
  • If specified, a follow-up activity is created and assigned to the Method user.
  • These activities are all tracked in the case screen.

The contact can add comments and close the case from their portal screen. The latter changes the case status to complete and informs the assigned user by email that the customer wants to abandon the case, or is satisfied with the work done so far.

Did this answer your question?