Automating initial acknowledgments ensures you meet response SLAs every time while freeing up technicians to focus on actually solving problems instead of crafting replies.
This action is only available as a triggered action in workflows.
Quick start
1
Create triggered workflow
Set the trigger to “New ticket created” for the companies you want to cover.
2
Add Acknowledge Issue action
The action will work with default settings, but you can add custom instructions for your company’s tone and style.
3
Add notification action
Use “Notify Ticket’s Contact” to send the generated acknowledgment message to the customer.
4
Test and refine
Check your Event History to see the generated messages and adjust custom instructions if needed.
How it works
When a new ticket arrives, this action analyzes the ticket content and generates an appropriate acknowledgment message that:- Matches the situation - Acknowledges help requests, confirms actions in progress, or promises follow-up for information requests
- Sounds human - Uses empathetic language like “thank you” instead of robotic “acknowledged” responses
- Personalizes greetings - Includes customer names when available (i.e. “Hi John,”)
- Maintains professionalism - Ends with appropriate closings like “Best Regards”
- Follows your style - Incorporates custom instructions to match your company’s voice and tone
Setup
Ticket to process: The action works with any ticket from your workflow - either new tickets from triggers or tickets found by other actions. Custom instructions (optional): Want to customize how acknowledgments sound? You can add specific guidance like:- “Always mention our 4-hour response commitment”
- “Include a link to our customer portal”
- “Sign off with our team name”
What you get
After running, you’ll have polished acknowledgment messages ready to send to customers. The action also creates internal summaries for your team and logs what happened in your Event History.Common use cases
Automated first response
Automated first response
Set up immediate acknowledgment for every new ticket to meet SLA requirements and keep customers informed.
SLA compliance
SLA compliance
Ensure you never miss response time commitments by automatically acknowledging tickets within minutes of creation, even outside business hours.
Multi-client communication
Multi-client communication
Use company-specific settings to maintain different communication styles for different types of clients or service levels.
Best practices
Start with defaults
Start with defaults
Begin with the default behavior and add custom instructions only after you see how the AI performs. The default acknowledgments are designed to work well for most MSPs.
Customize for your voice
Customize for your voice
Use custom instructions to match your company’s communication style:
Use company-specific settings
Use company-specific settings
For clients with unique communication needs, enable “Add company level custom instructions” in your settings. This lets you maintain different styles for different client types.
Always pair with notifications
Always pair with notifications
Remember that Acknowledge Issue only generates the message content. Always pair it with a notification action to actually send the acknowledgment:
- Use Notify Ticket’s Contact to email customers
- Use Add Ticket Note to log the acknowledgment internally
Monitor and refine
Monitor and refine
Check your Event History regularly to see the actual messages being generated. If acknowledgments aren’t quite right, adjust your custom instructions and test with a few sample tickets.
Example workflows
Basic Auto-Acknowledgment
Basic Auto-Acknowledgment
- Trigger: New ticket created
- Acknowledge Issue - Generate professional acknowledgment message
- Notify Ticket’s Contact - Send message to customer
- Result: Every new ticket gets immediate professional acknowledgment
SLA-Focused Acknowledgment
SLA-Focused Acknowledgment
- Trigger: New ticket created
- Acknowledge Issue - Custom instructions: “Always mention our 4-hour response commitment”
- Notify Ticket’s Contact - Send to customer
- Add Ticket Note - Log acknowledgment internally
- Result: Customers know exactly when to expect response
For Autotask users: If you’re using notification templates that already include customer greetings, the AI will avoid adding duplicate “Hi [Name],” greetings to prevent awkward repetition.