Blogs

SLA escalation in a CRM means acting when a record stays unresolved, idle, or otherwise matches configured conditions for too long. This guide covers the documented setup in Urdhva Tech’s SuiteCRM Escalation Management add-on. These steps are add-on configuration, not a claim that SuiteCRM core includes all of this SLA automation on its own.

What Is SLA Escalation in SuiteCRM?

In general CRM terms, SLA escalation means acting when a record has waited too long. Typical actions include reassignment and notifying the people who need to take over.

SuiteCRM case escalation is a common example: a support Case that has not been closed within a configured period should move to a manager, another user, or a group. The same idea can apply to other records, not only Cases.

The Escalation Management add-on monitors record criteria and time-based conditions, then reassigns ownership or runs escalation actions when rules match. It can escalate idle records to managers, teams, or round robin groups based on the rules you define.

Why Use SLA Escalation Rules?

Manual follow-up is easy to miss when queues are busy. Configured SuiteCRM SLA escalation helps teams:

• Keep important issues from remaining unattended
• Enforce time-based escalation policies you have defined
• Make ownership clearer when a record is reassigned
• Automate reassignment instead of relying on ad hoc hand-offs
• Notify relevant users by email when an escalation occurs

Those outcomes depend on how you configure rules, timing, actions, and the scheduler.

How SuiteCRM Escalation Rules Work

A complete SuiteCRM escalation workflow on the current product page is:

1. Define business hours and holidays.
2. Create an escalation rule.
3. Select the target module.
4. Create rule-entry criteria.
5. Define escalation timing.
6. Configure escalation actions.
7. Configure reassignment and notifications.
8. Enable the escalation scheduler.
9. Review escalation logs.

The rest of this article walks through those steps in order.

Step 1: Configure Business Hours and Holidays

Escalation rules can use organization business hours and holiday calendars. Configure them here:

• Admin → Escalation configuration → Organization Business Hours — set working hours
• Admin → Escalation configuration → Holiday Details — set holidays for the year

The product page also states that escalation rules can follow holidays. Extra holiday-timer behaviour beyond that is not assumed here.

Step 2: Create an Escalation Rule

Open the Escalation Rules module, then:

1. Click Create Escalation Rule.
2. Enter the Escalation Rule Name.
3. Select the module the rule should apply to.
4. Select the Active checkbox.
5. Save the record.

The add-on is not limited to Cases. It supports major built-in modules and custom modules.

Step 3: Create Rule Entry Criteria

After the rule is saved, open its detail view and click Create Rule Entry.

Rule-entry criteria define the record field values that trigger an escalation. If the criteria match, the record is escalated. You also set how escalation times are calculated and whether business hours apply.

A module can have multiple rule entries, each with its own criteria and associated escalation actions. Field operators and rule priority are not listed on the product page, so they are not described here.

Step 4: Choose How Escalation Time Is Calculated

Your choice here controls when the period in Time Until Escalation Action starts. That field is set on the Escalation Actions page.

Based on Created Time

The escalation clock starts when the record is created. The record escalates when the configured period expires.

Example from the product documentation: if Until Escalation Action is 5 hours and the record is created at 9 AM on Monday, it would escalate at 2 PM on Monday.

Based on Last Modification Time

The escalation clock starts when the record was last modified.

Example from the product documentation: if the record is created at 9 AM and an agent modifies it at 10 AM, with a 5-hour period, it would escalate at 3 PM—five hours after the 10 AM modification.

Use created time when the SLA is measured from intake. Use last modification time when inactivity after an update should start the clock.

Step 5: Use Business Hours for SLA Escalation

On the rule entry, select the Business Hours checkbox if escalation should follow configured working hours.

If business hours are specified on the escalation rule, escalation actions occur only during those hours. The product uses 9 AM–5 PM only as an illustration: if you defined hours that way, Cases would escalate only during that window. That is not a default Urdhva Tech schedule; you set Organization Business Hours to match your team.

Step 6: Configure the Escalation Action

From the Escalation Rule page, open a rule entry and click New Escalation Action. The action is what runs once timing and criteria are satisfied.

Documented settings include:

• Age of Escalation Actions
• Escalate To (the person the record is escalated to)
• Escalate Template
• Owner for the escalated record
• Email template used to Notify Assignee
• Additional Emails

Time until escalation action escalates the record if the rule has not been satisfied within that period. The documented example is: escalate the Case if it has not been closed within 8 hours.

Step 7: Configure Automatic Reassignment

When a record escalates, Auto-reassign record to can move it to a different user or team. Documented options:

Reports To User

Escalates based on the organization’s Reports To hierarchy—to the person the current user reports to.

Specific User

Select From user and To User to reassign records of one specified user to another specified user.

Round Robin

Reassign using:

• All users
• Users in a role
• Users in a security group

When a record is reassigned, the team or user becomes the new owner. The product notes that companies often reassign to a team rather than one person. Example: if Level 1 support does not resolve a Case within 24 hours, reassign it to the Level 2 support team.

Round Robin here is the documented distribution method, not load balancing or AI routing.

Step 8: Configure Escalation Notifications

Email alerts can be sent as part of the escalation action. Documented options:

• Notification template for the current owner
• Notification template for the assignee
• Additional emails to other recipients

Only email notification is documented. SMS, WhatsApp, Slack, Teams, and push notifications are not described on the product page.

Step 9: Enable the Escalation Scheduler

The scheduler processes the escalation queue. Without it, configured rules will not run as expected.

1. Go to Admin → Schedulers.
2. Create a scheduler and choose Process Escalation Queue.
3. Keep it Active.
4. Set execution time as often as possible.

The product page does not prescribe a specific cron interval beyond “as often as possible.”

Step 10: Review the Escalation Log

The Escalation Log module keeps records of escalated records across different modules. Use it to review activity and see which records were escalated after the scheduler runs. It is documented as an operational log, not a compliance product.

Example: Escalating an Unresolved Case

A support team wants a Case to escalate if it has not been closed within 8 hours. Using only documented capabilities:

1. Configure Organization Business Hours and Holiday Details.
2. Create an Escalation Rule for the Cases module and activate it.
3. Create a rule entry with field criteria that match unresolved Cases.
4. Choose created time or last modification time for the clock.
5. Enable business hours on the rule entry if escalation should wait for working hours.
6. Add an escalation action with Time Until Escalation Action set so the Case escalates if it has not been closed within 8 hours.
7. Reassign using Reports To User, a specific From/To user, or Round Robin (all users, role, or security group).
8. Select email templates for the current owner and assignee, plus additional emails if needed.
9. Enable Process Escalation Queue.
10. Confirm activity in the Escalation Log.

Escalation Rules for Custom SuiteCRM Modules

Escalation Management is not only for Cases. The same rule-based approach can be configured for major built-in modules and custom modules.

Create the rule, select the custom module, then add rule entries and actions as you would for Cases. Undocumented module names are not listed here.

Multiple Escalation Rules and Rule Entries

You can create multiple rule entries for a module, each with separate criteria and escalation actions. That is useful when different record conditions need different timing or reassignment.

Rule precedence is not documented on the current product page. Configure entries so their criteria match distinct situations.

Business Hours and Holidays in SLA Escalation

Organization Business Hours and Holiday Details let escalation follow the working schedule you define. If the business-hours option is selected on the rule, actions occur during those hours.

The FAQ states that escalation rules can follow business hours and holidays. Do not assume extra holiday-timer behaviour beyond what those screens and that statement document.

SuiteCRM Escalation Management Use Cases

These examples stay within documented functionality.

Support Case Escalation

Escalate unresolved Cases after a configured period, such as not closed within 8 hours.

Manager Escalation

Use Reports To User so the record moves up the reporting hierarchy.

Team Reassignment

Use Round Robin across all users, users in a role, or users in a security group—for example Level 1 to Level 2 after a defined period.

Notification-Based Escalation

Email the current owner, the assignee, and additional recipients when the action runs.

Custom Module Escalation

Apply the same rules to supported custom modules, not only Cases.

Common SLA Escalation Configuration Mistakes

These are configuration points to check, not ranked or statistical errors:

• Skipping Organization Business Hours
• Skipping Holiday Details when holidays should apply
• Creating a rule but not creating rule entries
• Not setting Time Until Escalation Action
• Not adding an escalation action
• Leaving Process Escalation Queue inactive
• Not selecting notification templates or additional emails
• Not checking the Escalation Log after go-live

SuiteCRM SLA Escalation Checklist

• Business hours configured
• Holidays configured
• Escalation rule created
• Target module selected
• Rule-entry criteria defined
• Escalation timing defined (created time or last modification)
• Business-hours option reviewed
• Escalation action configured
• Reassignment configured
• Notification templates configured
• Process Escalation Queue enabled
• Escalation log reviewed

Frequently Asked Questions

Using Escalation Management for SuiteCRM SLA Automation

escalation management for SuiteCRM provides the documented pieces needed to configure SLA-based escalation: rule criteria, business hours, holidays, escalation timing, reassignment, email notifications, scheduler processing, escalation logs, and built-in and custom modules. Learn more about SuiteCRM Escalation Management if you need this SuiteCRM SLA automation inside the CRM rather than handling aging records by hand.

Conclusion

The documented setup path is: Define business hours → Create rule → Define criteria → Set escalation timing → Configure action → Reassign/notify → Enable scheduler → Review escalation log.

Used that way, SuiteCRM escalation rules can automate the SLA workflows you have configured.

For product details, see the SuiteCRM escalation add-on.