Case Setup is where you configure how cases are created, routed, managed, and closed. Before employees begin raising cases, use Case Setup to define your HR teams, request categories, service targets, notifications, and lifecycle rules.
Most organizations complete Case Setup once during implementation, then update individual settings as their HR services evolve.
This article provides an overview of the available configuration areas and the recommended order for setting them up.
Where available, select Use recommended defaults to populate a section with suggested values you can customize to meet your organization's requirements.
Before you begin
- Understand HR Case Management
- To configure Case Setup, you must have the Case Administrator role.
- Open Case Setup from your Applaud app.
If one section depends on another, save your changes before moving on. For example, create teams before using them in SLA policies or shared views.
How the settings work together
The settings in Case Setup work together throughout the lifecycle of a case.
- An employee submits a request.
- The AI Assistant (or case creation form) collects the required information.
- Categories, priority, and flags help classify the case.
- The case is routed to the appropriate team or agent.
- SLA policies determine the service targets for the case.
- Notifications keep employees and agents informed as the case progresses.
- Lifecycle settings control when inactive cases are resolved, closed, and finalized.
- After resolution, a close survey can collect employee feedback.
Recommended configuration order
When you configure Case Management for the first time, complete the sections in the following order:
- Teams
- Categories
- Flags
- Priority definitionsΒ
- SLA policies
- Notifications
- Close survey
- Lifecycle
- Allow message undo
- AI-only case creation
- Case numbering
Configure teams
Teams define who owns and works cases. Every case is assigned to a team, and each team contains the case managers and case agents responsible for handling those cases.
Create a team
- Open Case Setup > Teams
- Select Add team.
- Enter a Team name.
- Enter a description in What this team handles.
- Select Add member.
- Add at least one Case manager and one or more Case agents.
- Optionally configure the Max cases limit and Background for each agent.
- Select Save.
Team settings
| Field | Purpose | Example |
| Team name | Defines the team's display name and routing label. | Payroll, Benefits, Employee Relations |
| What this team handles | Describes the types of cases the team manages. This information helps route cases to the appropriate team. | Pay queries, deductions, tax forms, and payroll corrections. |
| Case manager | Oversees team queues and assignments. At least one case manager is required for each team. | Jane Smith (manager) |
| Case agent | Agents who work assigned cases. | Tom Lee, Priya Patel |
| Max cases | Optional limit for the number of open cases assigned to each agent. | 15 β helps balance workload |
| Background | Optional description of an agent's areas of expertise. | US payroll, garnishments, W-2 corrections |
Configure categories
Categories define the types of requests employees can raise. They help organize cases, improve routing, and ensure the AI Assistant collects the right information before creating a case.
Well-designed categories make it easier for employees to describe their issue, help agents find similar cases, and improve reporting across your HR services.
Create a category
To load a starter set, select Categories > Edit > Use recommended defaults, or to create a custom category:
- Open Categories > Edit.
- Select Add category.
- Enter a Name.
- Optionally select an Icon.
- Enter a Description.
- Add an AI intake brief.
- Select Save.
Category settings
| Field | Purpose | Example |
| Name (required) | Display name for the category. | Leave and absence |
| Icon | Helps agents and administrators identify the category at a glance. | mdi-calendar-outline |
| Description | Summary of the types of requests included in the category. | Holiday, sickness, parental, and other leave-related queries. |
| AI intake brief | Defines the information the assistant should collect before creating a case. | Ask which type of leave the employee needs, the relevant dates, and whether they need a balance check or a correction. |
Configure flags
Flags highlight important characteristics of a case that affect how it is handled. Unlike categories, which describe what a case is about, flags identify conditions such as urgency, financial impact, compliance risk, or the need for additional attention.
Create a flag
To load a starter set, select Flags > Edit > Use recommended defaults, or to create a custom flag:
- Open Flags > Edit.
- Select Add flag.
- Enter a Name.
- Optionally select an Icon.
- Enter a Definition that describes when the flag should be applied.
- Select Save.
Flag settings
| Field | Purpose | Example |
| Name | Display name for the flag. | People risk |
| Icon | Helps agents and administrators identify the flag at a glance. | mdi-flag-outline |
| Definition | Describes when the flag should and should not be applied. | See the recommended example below. |
Configure priority definitions
Priority definitions describe what each priority level means in your organization. During case triage, the system uses these definitions to help assign the appropriate priority to each case, and agents can use them as guidance when reviewing or updating cases.
The four priority levels are fixed:
- Critical
- High
- Normal
- Low
You can customize the definition for each priority level, but you can't rename or remove the priority levels.
Edit priority definitions
- Open Priority definitions > Edit.
- Update each definition.
- Optionally select Use recommended defaults.
- Select Save.
Configure SLA policies
SLA policies define the service targets applied to cases. They determine how quickly cases should be acknowledged, updated, and resolved, as well as how the quality of the service experience is measured.
Create an SLA policy
To load a starter set, locate SLA policies and select Use recommended defaults, or to create a custom policy:
- Locate SLA policies and select Add policy.
- Enter a Policy name.
- Optionally enter a Description.
- Define the Conditions.
- Configure the SLA and XLA metrics you want to track.
- Enter target values for each enabled metric.
- Select Save policy.
Policy structure
Each SLA policy includes identifying information and the conditions that determine which cases the policy applies to.
| Field | Purpose | Example |
| Policy name | Display name for the policy. | Critical priority |
| Description | Optional description of the policy. | Fast-track targets for urgent cases |
| Conditions | Defines which cases the policy applies to. | Priority is Critical |
For detailed guidance on SLA and XLA metrics, see Understanding SLA and XLA metrics.
Configure notifications
Notifications keep employees, agents, and managers informed as cases progress.
Some notifications are required for case processing and can't be disabled.
- Locate Notifications and select Edit.
- Review the available notification categories.
- Turn optional notifications on or off.
- Select Save.
Notification categories
Notification categories determine who receives notifications for different case events.
| Category | Audience | Example notifications |
| Employee | Requester, raiser, and CC'd participants | Agent replied, case resolved, waiting on you |
| Agent | Assigned agent | New assignment, employee replied |
| Manager | Team managers | Manual triage required, SLA at risk, daily digest |
| Participation | People whose involvement changed | Added as a CC or collaborator |
Required notifications
The following notifications are required and cannot be disabled because they are necessary for case processing.
| Category | Notification | Why it's required |
| Employee | Reply needed on case β x days remaining | The employee must know that the case requires their input. |
| Employee | Case is waiting on you | The employee must know that the case requires their input. |
Example manager notification
When AI triage cannot confidently assign a case, the Case needs manual triage notification alerts team managers so they can assign the appropriate team, assignee, or categories.
Configure close survey
Close surveys collect employee feedback after a case is resolved. You can configure which questions are asked, the rating scale used, and whether surveys are sent.
- Locate Close survey and select Edit.
- Enable Send survey when cases are resolved.
-
Choose the questions to include.
Note: You must enable at least one survey question. - Select a survey scale.
- Preview the survey.
- Select Save.
Survey settings
Configure the questions employees see and when close surveys are sent.
| Field | Purpose | Example |
| Send survey when cases are resolved | Controls whether a survey is sent after a case is resolved. | Enabled |
| Did this fully address what you needed? | Resolution question. Measures whether the employee's request was addressed. | On |
| Did we understand what you needed? | Understanding question. Measures whether the issue was understood. | On |
| Effort/satisfaction question | Numeric scale question that measures effort or satisfaction. | On |
| Effort scale | Defines the rating scale employees see. | CSAT 1β5 (default) |
Effort scale options
Choose a scale that matches the type of feedback you want to collect.
| Scale | Best for | Example question |
| CSAT (1β5) | Overall satisfaction | "How satisfied were you with how this was handled?" |
| CES (1β5 or 1β7) | Ease of getting help | "How easy was it to get the help you needed?" |
| eNPS (0β10) | Likelihood to recommend HR support | "How likely are you to recommend our HR team?" |
Recommended defaults
The recommended configuration enables all three questions and uses the CSAT 1β5 scale.
Configure lifecycle settings
Lifecycle settings automate how cases progress after work is complete. You can configure when inactive cases are resolved, closed, and finalized.
- Locate Lifecycle and select Edit.
- Configure:
- Auto-resolve cases waiting on the employee
- Lifecycle for resolved and closed cases
- Select Save.
Lifecycle settings
Configure the time-based rules that control how cases move through the later stages of the case lifecycle.
| Setting | Purpose | Recommended default | Example override |
| Auto-resolve waiting cases | Resolves cases that remain in Waiting after the specified number of days without an employee reply. | 7 days (warning sent 2 days before) | 5 days for faster case closure |
| Days before auto-closing a resolved case | Defines the grace period between Resolved and Closed. | 14 days | 3β7 days for a shorter grace period |
| Days until a closed case is finalized | Finalizes the case, prevents reopening, and locks reporting data. | 5 days | 30 days to allow a longer reopening window |
Configure message undo
The message undo delay gives agents a short time to review or cancel a message before it is delivered to the employee.
Configure the undo window
- Locate Allow message undo and select Edit window.
- Configure the Window (seconds).
- Select Save.
How it works
When message undo is on, public agent replies are delayed until the undo window expires or the agent chooses to send the message immediately.
- The agent selects Send update.
- The message appears as pending with Undo and Send now options for 15 seconds.
- After 15 seconds, or when the agent selects Send now, the message is delivered to the employee.
Message undo settings
Configure the delay and the length of the undo window for public agent replies.
| Field | Purpose | Example |
| Enabled | Controls whether public agent replies are delayed before being sent. | On (default) |
| Window (seconds) | Defines how long the undo window remains available before the message is sent automatically. | 15 seconds (range: 5β30) |
Configure AI-only case creation
Choose how employees create new cases: through the AI Assistant or via a case creation form.
Configure case creation
- Locate AI-only case creation.
- Turn on the setting to require employees to use the AI Assistant.
- Turn off the setting to allow employees to create cases using a form.
- Select Save.
AI-only case creation settings
Choose how employees create new cases.
| Option | Employee experience |
| On (default) | Selecting New case opens the AI Assistant. The assistant may answer simple questions without creating a case. If a case is needed, it collects the required information before creating it. |
| Off | Selecting New case opens the case creation form. Requests are submitted directly without AI-assisted intake. |
Configure case numbering
Case numbering defines the format of case IDs used to identify and reference cases. You can configure the case ID prefix and the starting number before cases are created.
Configure case numbering
- Locate Case numbering and select Edit.
- Enter a Prefix.
- Enter the Start number.
- Select Save.
Case numbering settings
Configure the prefix and starting number used when generating case IDs.
| Field | Purpose | Example |
| Prefix | Defines a 1β4 letter prefix added to the beginning of each case ID. | HR, CASE, HRS |
| Starting number | Defines the first number in the case ID sequence. | 1000 β first case is HR0000001000 |
Example case numbers
The following examples show how the prefix and starting number determine the first generated case ID.
| Prefix | Starting number | First case ID |
| CASE | 7100 | CASE0000007100 |
| HR | 1 | HR0000000001 |
| PAY | 50000 | PAY0000050000 |
Validation rules
The following rules apply when configuring case numbering.
| Rule | Detail |
| Prefix format | The prefix must contain 1β4 uppercase letters (AβZ). |
| Prefix reuse | A previously used prefix cannot be reused. |
| Starting number | After cases have been created, the starting number can only be increased. |
| Configure before go-live | Configure the prefix and starting number before creating the first case. |