Branched logic to triage, route, summarize tickets and auto reply using Automation Studio

Solution

The organization adopted Automation Studio to consolidate ticket summarization, customer acknowledgement, and conditional routing into a single automation rule, reducing multiple workflow rules into one. Its easy to maintain and manage change log as requirements evolve.

When a ticket is created, the rule triggers and executes a chained sequence of actions:

Generate Content (Zia): Zia analyzes the ticket's latest thread content, subject, description, status, created time, and product name to generate a concise, customer-friendly summary of the issue. The summary is added as a private comment on the ticket, giving agents an immediate understanding of the context without reading the full thread.

Note:

• Generative AI services and Zia action must be enabled in the Zoho Desk account before configuring the Generate Content action.

• Zia generates the content only in English only.

• The accuracy and usefulness of the Zia-generated summary depends on the quality of the prompt and the context fields selected. Admins should test and refine the prompt before deploying the rule.

Send Email Reply: The output of the Generate Content action, the Zia-generated summary, is passed into the email reply template using the placeholder ${1-ziaGenerateContent.ziaResponse}. This method, known as action chaining, allows the generated summary to be dynamically inserted into the acknowledgement email sent to the customer. The customer receives an immediate, contextual response confirming that their request has been received and summarizing the issue as understood by the system.

Note: The Send Email Reply action depends on the output of the Generate Content action. If Zia fails to generate content (e.g., due to insufficient or unclear ticket content), the placeholder ${1-ziaGenerateContent.ziaResponse} will not be populated, and the email reply may contain a blank summary section.

Fork Block with Conditional Assignment: The rule then splits into multiple paths using a Fork Block. Each path evaluates a condition based on the Product Name field. When the condition is met, the ticket is automatically assigned to the corresponding product support team using the Assign Ticket action. This replaces the need for separate workflow rules per product, consolidating all routing logic within a single rule.

Note: A maximum of five paths can be created in a Fork Block. Organizations with many products may need to evaluate whether all product-to-team mappings fit within a single fork or whether additional rules are required.

All four actions - summarization, email acknowledgement, conditional evaluation, and team assignment executed without manual intervention. Even with high ticket volume, every ticket is triaged, acknowledged, and routed within seconds of creation. Additionally, tickets that have been auto-summarized display the Zia-generated summary as a private comment in the ticket's Conversation View, providing direct visibility into triaging accuracy.

Impact Assessment: Manual Workflows vs. Automation Studio  

Monitoring & Optimization 

Support managers can track the automation's effectiveness through three standard reporting tools in Zoho Desk:

• Agent Performance Report: Tracks per-agent metrics including first response time, number of responses, and resolution time. By comparing these metrics before and after the automation rule was deployed, managers can measure the impact of auto-summarization and auto-routing on agent pickup rates and overall productivity.

• Lifecycle Report (Team Report): Tracks ticket transitions by showing exact timestamps of assignment changes and duration spent at each stage. Managers can use this to verify that tickets are reaching the correct product team immediately after the automation rule executes and identify any delays in the handoff.

Configuration / Steps

1. Navigate to Setup > Automation > Automation Studio.
2. Click Create Rule.
3. On the Rule information page, do the following:
   1. Enter Rule Name: Auto-generate Summary and route tickets.
   2. Enter Description: Automatically generate summary using Zia and assign the tickets based on the product.
   3. Select Tickets module from the drop-down.
4. On the Rule configuration page, click Choose Event and select Ticket Created.
5. Click + and select the Action Block.
6. Click Generate Content under Zia.
7. In the Context field, select Last Thread, Subject, Description, Status, Created Time, and Product Name from the placeholder.  
   On selecting the above mentioned values, the context field will have the following input:
   *Ticket Details* 
   Latest thread: ${tickets.$recentThreadContent}
   Subject: ${tickets.$subject}
   Description: ${tickets.$description}
   Status: ${tickets.$status}
   Created Time: ${tickets.$createdTime}
   Product Name: ${tickets.productId.$productName}
8. In the Prompt field, enter Using the ticket details provided in the context, generate a concise and customer-friendly summary of the issue for use in an acknowledgement email. 

9. Click + and select the Action Block.
10. Select Send Email Reply under Ticket and do the following:
    1. In the Record ID field, select the Ticket Identifier placeholder.
    2. In the From Address field drop-down, select an email address.
    3. In the To Address field, select the Email placeholder.
    4. In the Ticket Reply field, enter the following:
       Hi ${tickets.contactld.$firstName},
       Thank you for contacting our support team. We have received your request and our team is currently reviewing it.
       ${1-ziaGenerateContent.ziaResponse}
       If we need any additional information, we'll reach out to you. Otherwise, we'll keep you updated as we work towards resolving your request.
       Thank you for your patience.
       Regards, 
       Support Team

11. Click + and select the Fork Block.
    1. In Path 1:
       Click + and select the If Block.
       In the Set Criteria pop-up, select Product Name is zPad and click Save.
       Click + and select the Action Block.
       Click Assignticket under Ticket.
       In the Record ID field, select the Ticket Identifier placeholder.
       In the Assignee field drop-down, select Team.
       In the Team Name field drop-down, select zPad Support team.
       Click Save.
    2. In Path 2:
       Click + and select the If Block.
       In the Set Criteria pop-up, select Product Name is zPhone and click Save.
       Click + and select the Action block.
       Click Assign ticket under Ticket.
       In the Record ID field, select the Ticket Identifier placeholder.
       In the Assignee field drop-down, select Team.
       In the Team Name field drop-down, select zPhone Support team.
       Click Save.
12. Click Save & Activate.

To view Agent Performance report

1. Navigate to the Analytics module.
2. Click the Report tab.
3. Under Static Reports, select Agent Performance.
    

To view Lifecycle report

1. Navigate to the Analytics module.

2. Click the Report tab.

3. Under Static Reports, select Lifecycle Report.