Cubu Docs
User Guide
User Guide
  • 👋Welcome to Cubu!
  • Getting Started
  • Understanding the Basics
    • Organizations
    • Process Management
      • 📚Introduction to Cases
      • 📚Service Models and Flow
      • 📚Storing Data with Fields
      • 📚Categorizing Cases with Tags
      • 📚Service Categories and Types
      • 📚Inboxes
      • 📚Routes
      • 📚Working Hours
      • 📚Walk-in Services
      • 📚Appointment-based Services
      • 📚Data Tables
      • 📚The Customers Data Table
      • 📚Automation
        • 📄Automation Triggers
        • 📄Automation Conditions
        • 📄Automation Actions
    • Agent Status Tracking
    • Portals
      • 📚Portal Flow I: Single Unit
      • 📚Portal Flow II: Cross Unit Search
      • 📚Prerequisites & Data Collection
    • Kiosks
      • 📚Kiosk Flow
      • 📚Kiosk Accessibility
    • Virtual Tickets
    • Service Level Alerts
    • Security and Permissions
      • Access Control
        • 📚Unit Access Permissions
        • 📚Inbox Access Permissions
        • 📚Service & Calendar Access Permissions
        • 📚Fields Access Permissions
        • 📚Data Table Access Permissions
      • 📚Built-in Roles
    • Subscriptions & Licensing
    • Chats Overview
  • User Tools
    • About Agents and Managers
    • Agent Console
      • ⚒️Agent Console Basics
      • ⚒️Processing Cases
      • ⚒️The Inbox Tab
      • ⚒️The Case Tab
      • ⚒️Workspace Settings Tab
    • Calendar
      • ⚒️Selecting Calendars
      • ⚒️Booking, Checking-in & Canceling Appointments
    • Appointment Booking
    • Data Manager
      • ⚒️Searching for Records
      • ⚒️Managing Data Records
    • Case Browser
    • General Tasks
      • ⚒️Updating your Profile
      • ⚒️Selecting Your Current Unit
      • ⚒️Change Language
      • ⚒️Switch Organization
    • Report Center
    • Real-time Monitor
      • Widgets Reference
      • Metrics Reference
  • Connected Apps
  • Admin Tools
    • About Administrators
    • Organization Tree
      • ⚒️Managing the Organization Tree
      • ⚒️Configuring Unit Access
      • ⚒️Configuring Time Zones
      • ⚒️Managing Inboxes
      • ⚒️Managing Routes
      • ⚒️Managing Workstations
      • ⚒️Managing Portals
      • ⚒️Managing Kiosks
        • ⚒️Printed Tickets Templates
    • Service & Process Configuration
      • ⚒️Global Service Settings
      • ⚒️Managing Service Categories
      • ⚒️Managing Service Types
      • ⚒️Managing Fields
      • ⚒️Managing Tags
      • ⚒️Managing Working Hours
      • ⚒️Managing Automations
      • ⚒️Managing Data Tables
      • ⚒️Managing Back-office Tasks
      • ⚒️Managing Alert Rules
    • Service Management
      • ⚒️Walk-in Services Settings
      • ⚒️Appointment-based Services Settings
      • ⚒️Managing Service Availability
      • ⚒️Manage Service Daily Plans
      • ⚒️Manage and Scedule Daily Plan Templates
    • Security and Permissions
      • ⚒️Managing Users & Invitations
      • ⚒️Managing Groups
    • Customer Engagement
      • ⚒️SMS Templates
      • ⚒️Email Templates
      • ⚒️ICS Templates
      • ⚒️Managing Themes
      • ⚒️Managing Fonts
      • ⚒️Media Library
      • 🗒️Dynamic Text Parameters (Messaging)
    • Localization and Translation
      • ⚒️Translating Resource Names
      • ⚒️Translating Kiosks, Portals, Tickets, and Chats
      • 📄Dynamic Text Parameters (Public Apps)
    • Organization Settings
      • ⚒️Organization General Settings
      • ⚒️Public Text Languages
      • ⚒️File Storage
      • ⚒️SSO
      • ⚒️BI and Reports
      • ⚒️Certificates
      • ⚒️Webhooks
      • ⚒️Integrations
      • ⚒️Groups
      • ⚒️Registered Applications
    • Chats Admin
      • ⚒️Chat Settings
      • ⚒️Chatbots Configuration
    • Billing
      • ⚒️Subscription Management
      • ⚒️Payments
    • Logs
      • ⚒️Event Log
      • ⚒️SMS Log
      • ⚒️Change Log
  • Digital Signage
    • 📚Digital Signage
    • 📚Digital Sign Appearance
    • ⚒️Managing Digital Signs
    • ⚒️Managing Screen and Frame Layouts
    • ⚒️Managing Playlists
    • ⚒️Managing Public Announcements
  • How To Guides
    • Agent Tasks
      • 🧐How to unlock a case processed by another user
    • Admin Tasks
      • 🧐How To: Compensate For No-shows
      • 🧐How To: Reference Data Records from Cases
      • 🧐How To: Configure a Phone Call Meeting
      • 🧐How To: Set Up a Kiosk Ticket Printer
      • 🧐How To: Configure SendGrid as an Email Provider
      • 🧐How To: Configure Mandrill as an Email Provider
      • 🧐How To: Use Google Fonts in Themes
    • Automations
      • 🧐How To: Use Automation to Send SMS
      • 🧐How To: Use Automation to Move a Case to Another Inbox
    • In-Branch Operations
      • 🧐How To: Use the Kiosk Client App
      • 🧐How To: Connect a Digital Sign
    • Kiosks
      • 🧐How To: Configure Accessible Kiosk with IVR
Powered by GitBook
On this page
  • Case States and Lifecycle
  • Case Data
  1. Understanding the Basics
  2. Process Management

Introduction to Cases

Understanding Cubu cases.

PreviousProcess ManagementNextService Models and Flow

Last updated 8 months ago

A "case" is a record that encapsulates a customer's issue, storing key details like a unique identifier, customer information, issue description, status, and priority.

It also includes timestamps, communication logs, and resolution details.

Cases streamline customer support processes, ensuring efficient issue resolution and maintaining a comprehensive history of interactions for effective relationship management.

Important facts about cases:

  • A case is opened by an agent (using the Agent Console), by a customer (using the Portal or Kiosk), or by another program (using the S2S API).

  • To initiate the case lifecycle, you must use a service that provides all the necessary information to create a new case.

  • A case is closed after an agent resolves it, and no further work is required.

  • A case always belongs to an inbox, determined by the Service. However, it may move between inboxes during its lifetime.

  • A case belongs to a , which is determined by the Service and Service Type selected when the case is created. The service category and service type cannot change during the case's lifecycle.

Case States and Lifecycle

A case can be in one of the following states:

Icon
Status
Description

Planned

When booking an appointment, a case is created to represent the appointment. The case status is Planned until the customer checks in.

Waiting

Indicates the case is waiting in queue and is ready to be served by an agent.

Pending

The case is waiting for something before it can be called. It keeps its place in the queue but may be skipped if agents move on to the next case without the required action.

Active

An agent is serving the case. While active, the agent can update the case fields, add tags, link a customer, etc.

Resolved

This status indicates that a customer service representative has handled the case. You can use this status to implement custom business logic through Automations. You can decide whether to close the case or move it to another inbox for further processing. If there are no automations set up, the case's status will be automatically changed to Closed.

Closed

The status of this case is that no more work is required. This is a terminal status, which means the case has been completed and no further action is necessary.

Cancelled

The case has been cancelled. This is a terminal status.

During its lifetime, the case status can change multiple times until it is closed or canceled.

Case Data

To capture and organize information in a case, such as issue details and resolution type, enhance the case record by incorporating relevant fields. This involves creating case records with specific fields added to the corresponding Service Category. When initiating a new case through a service, the fields associated with the service category are automatically included.

Cubu offers diverse field types to accommodate various data formats (e.g., text, number, email). Additionally, you can specify a contact phone number and email address, facilitating SMS and email communication with the customer related to the case.

For users leveraging the Customers Table feature in Cubu, it's possible to establish a link between a customer record and the corresponding case. Furthermore, cases can be categorized or labeled through tagging.

📚
Service Category
📚Storing Data with Fields