Automation & Workflows
Streamline your helpdesk operations with powerful automation rules, workflows, and triggers that reduce manual work and improve response times.
Automation Overview
Discover how automation can transform your helpdesk efficiency and consistency
What is Automation?
Automation in Loopdesk allows you to create rules that automatically perform actions when specific conditions are met. This reduces manual work, ensures consistency, and improves response times.
Faster Response Times
Instant actions when tickets are created
Consistency
Standardized processes across all tickets
Reduced Manual Work
Eliminate repetitive tasks
Improved SLA Compliance
Automatic escalations and reminders
Better Organization
Automatic categorization and assignment
24/7 Operation
Rules work even when agents are offline
Types of Automation
Trigger Rules
Fire when events occur (ticket created, updated, etc.)
Time-Based Rules
Execute after delays or at scheduled times
Conditional Rules
Complex logic with multiple conditions
Escalation Rules
Automatic priority increases and reassignments
Notification Rules
Custom email and SMS alerts
Common Automation Examples
Automatic Ticket Assignment
Subject contains "software"
Priority Escalation
Status equals "Open"
Notify supervisor
Customer Communication
Set automatic closure after 3 days
Pro Tip
Start with simple automation rules and gradually add complexity as your team becomes comfortable with the system.
Creating Automation Rules
Master the rule builder interface and create powerful automation workflows
Rule Builder Interface
Accessing the Rule Builder
Navigate to Admin → Automation → Rules
Click Create New Rule
Choose rule type
Event Trigger
Responds to ticket events
Time Trigger
Runs after delays or on schedule
Manual Trigger
Agents can manually execute
Rule Components
1. Trigger Events
- Ticket Created
- Ticket Updated
- Ticket Resolved
- Ticket Closed
- Customer Reply
- Agent Reply
- Status Change
- Priority Change
- Assignment Change
- Due Date Approaching
2. Conditions (AND/OR Logic)
- Ticket Properties: Status, priority, department, category
- Customer Properties: Organization, user type, custom fields
- Time Conditions: Business hours, days of week, age
- Content Matching: Subject/description keywords
- Assignment Conditions: Assigned agent, department
- Custom Field Values: Any custom field data
3. Actions
- Assignment: Assign to agent, department, or team
- Status/Priority: Change ticket status or priority
- Notifications: Email customers, agents, or external systems
- Fields: Update ticket fields or add tags
- Escalation: Move to higher priority or different team
- Integration: Webhook calls, API requests, third-party systems
Step-by-Step Rule Creation
Learn to build effective automation rules with our comprehensive example
Example: Auto-Assignment Rule
Define the Trigger
- Trigger Event: "Ticket Created"
- Name: "Auto-assign billing tickets"
- Description: "Automatically assign billing-related tickets to billing team"
Set Conditions
Define Actions
Configure Options
- Active: ✓ Enabled
- Run Order: 10 (higher numbers run later)
- Stop Processing: ✗ (allow other rules to run)
- Audit Log: ✓ (track when rule fires)
Testing Rules
Rule Testing Features:
-
Dry RunTest rule logic without making changes
-
Sample DataUse existing tickets to test conditions
-
SimulationPreview what actions would occur
-
Debug ModeDetailed logging of rule execution
-
Roll BackUndo changes if rule behaves unexpectedly
Advanced Rule Features
Complex Conditions
Time-Based Conditions
- Business hours only: Monday-Friday 9 AM - 5 PM
- Exclude holidays and weekends
- Different rules for day/night/weekend
- Timezone-aware conditions
Dynamic Values
- Use ticket fields in actions: "Assigned to {customer.account_manager}"
- Date calculations: "Due date = Created date + 2 business days"
- Counter fields: "Increment custom field 'escalation_count'"
Important
Complex rules with many conditions can slow down ticket processing. Monitor rule performance and optimize as needed.
Time-Based Automation
Configure scheduled rules and business hours for precise timing control
Delay Rules
Execute after a specified time period
Useful for follow-ups and escalations
Recurring Rules
Run on a regular schedule
Useful for maintenance and reporting
Calendar Rules
Execute on specific dates/times
Useful for periodic tasks
Example: Escalation After No Response
Rule Configuration
Conditions & Actions
- • Status equals "Open"
- • Priority equals "High"
- • No agent response exists
- • Business hours only
- • Change priority to "Urgent"
- • Assign to supervisor
- • Send escalation email
- • Add internal note: "Auto-escalated due to no response"
Recurring Task Automation
Daily Tasks
- Close resolved tickets older than 7 days
- Send summary reports to supervisors
- Update dashboard metrics
- Clean up temporary data
Weekly Tasks
- Generate department performance reports
- Update agent availability calendars
- Archive closed tickets older than 30 days
- Send customer satisfaction surveys
Monthly Tasks
- Generate SLA compliance reports
- Update knowledge base analytics
- Clean up inactive user accounts
- Backup automation rule configurations
Business Hours Configuration
Setting Business Hours
- • Days of Operation: Monday through Sunday
- • Daily Hours: Start and end times
- • Timezone: Local business timezone
- • Holidays: Exclude specific dates
Business Hours Impact
- • Response time SLAs only count business hours
- • Resolution time excludes nights/weekends
- • Escalation rules respect business hours
- • Automatic scheduling considers availability
Escalation Rules & Advanced Integration
Ensure critical issues receive proper attention and integrate with external systems
SLA-Based Escalations
Technical Support SLA Example
- • If no response in 1.5 hours: Notify agent supervisor
- • If no response in 2 hours: Escalate to supervisor
- • If not resolved in 6 hours: Change priority to High
- • If not resolved in 8 hours: Escalate to senior agent
- • If not resolved in 12 hours: Notify department manager
- • If not resolved in 24 hours: Escalate to director
Escalation Chain Example
VIP Customer Rules
- • Set priority to "High" automatically
- • Assign to senior agent immediately
- • Notify account manager
- • Reduce SLA timeframes by 50%
- • Add "VIP" tag for easy identification
Enterprise Account Escalations
- Dedicated support team assignment
- Faster response time requirements
- Direct escalation to account management
- Custom SLA agreements
- Priority queue placement
Integration Automation
CRM Integration
- • Create CRM records for new helpdesk customers
- • Update contact information bidirectionally
- • Sync support ticket history to CRM
- • Trigger sales follow-up for resolved issues
- • Update customer status and preferences
AND: Customer type equals "Prospect"
THEN: Create sales opportunity in CRM
Email Marketing
- • Add satisfied customers to newsletter list
- • Remove customers who request no marketing
- • Trigger educational email series for common issues
- • Send product update notifications
- • Customer retention campaigns
IT Monitoring
- • Auto-create tickets from monitoring alerts
- • Update ticket status based on system status
- • Close tickets when issues are automatically resolved
- • Escalate tickets for repeated alerts
- • Integrate performance data into tickets
Critical
Test escalation rules thoroughly to avoid notification spam or missed escalations. Monitor escalation frequency to identify process issues.