FAQs: Workflow Automation with Zia Actions
1. What are Zia Actions in workflows?
Zia Actions are AI-powered automation steps that can be embedded within Zoho Desk workflow rules to perform intelligent operations on tickets — such as extracting data from email content, predicting field values, generating contextual summaries, and sending auto-generated email replies to customers. Unlike standard workflow actions (alerts, tasks, field updates) that follow rigid, rule-based logic, Zia Actions analyze the natural language content of tickets using generative AI and take contextual actions that would otherwise require human reading and interpretation.
For example, when a customer emails: "I bought a phone on Sept 15 using PayPal and the screen is cracked," Zia can extract the purchase date (Sept 15), payment mode (PayPal), and issue type (screen damage), auto-populate those fields on the ticket, predict the severity as "Medium," generate a summary for the agent, and send an auto-reply with a relevant knowledge base article — all within a single workflow execution.
2. What are the four types of Zia Actions available in workflows?
- Field Extraction — Extracts specific data points (email, phone number, order number, purchase date, etc.) from ticket conversations and auto-populates them into the corresponding ticket layout fields.
- Field Prediction — Analyzes ticket content to predict values for picklist and multi-select picklist fields (e.g., severity, product type, issue category) without requiring prior training.
- Generate Content — Creates AI-generated contextual text such as summaries, highlights, or concise explanations based on the ticket conversation, and outputs it as a private comment, public comment, or field update.
- Auto Email Reply — Drafts and sends an AI-generated first response to the customer with relevant knowledge base article links, using Answer Bot's training to compose a suitable reply.
3. What prerequisites must be met before configuring Zia Actions?
- Generative AI must be enabled — Navigate to Setup > Zia > Generative AI and enable the Zia Actions toggle. This is the foundational requirement for all four Zia Actions.
- Answer Bot must be configured and trained (for Auto Email Reply only) — The Answer Bot must be set up in the same department where the workflow is created, and it must be trained with relevant knowledge base articles. Without proper training, Zia cannot generate meaningful auto-replies.
4. What language limitations apply to Zia Actions?
All Zia Actions — Field Extraction, Field Prediction, Generate Content, and Auto Email Reply — are supported only in English. Tickets submitted in other languages will not be processed by Zia Actions.
5. How many Zia Actions can be added to a single workflow rule?
A workflow rule can have a maximum of 1 type of each Zia Action — meaning one rule can include all four Zia Actions (1 Field Extraction + 1 Field Prediction + 1 Generate Content + 1 Auto Email Reply). However, each action type can be used only once per rule.
6. Is there a daily execution limit for Zia Actions?
Yes. A maximum of 1,000 executions per organization per day applies across all Zia Actions combined. This limit is shared — meaning if you have multiple workflow rules with Zia Actions, all executions across all rules count toward this 1,000-execution cap. These limits apply only to Zia automation actions and do not affect Zia native features or AI agents.
7. Which module supports Zia Actions?
Zia Actions can be configured only for the Tickets module. They cannot be used with Contacts, Accounts, Tasks, or any other module.
8. Can Zia Actions be disabled?
Yes. Administrators can disable Zia Actions by navigating to Setup > Zia > Generative AI > Zia Actions and toggling them off. This will prevent all Zia Actions from executing in any workflow rule across the organization.
Field Extraction
9. What does the Field Extraction action do?
Field Extraction analyzes the text content of a ticket (such as the email body, description, or thread replies) and identifies specific data points — like email addresses, phone numbers, dates, currency values, order numbers, and product codes — then auto-populates them into the corresponding fields on the ticket layout. This eliminates manual data entry and reduces the risk of agents missing or mistyping critical information.
For example, in a university setting, a student emails about an issue accessing course materials. Zia identifies fields in the layout (Exam Code, Student ID, Contact Number, Registration Date) and maps them with details mentioned in the email, auto-filling the values without any agent intervention.
10. Which field types are supported by Field Extraction?
Zia can extract and auto-fill values for the following field types only:
- Number
- Decimal
- Percent
- Currency
- Phone
- URL
- Date
- DateTime
Fields of other types (e.g., picklist, single-line text, multiline text) are not supported by Field Extraction.
11. How many fields can Zia extract per workflow rule?
A maximum of 5 field values can be extracted per rule. If you need to extract more than 5 fields, you would need to create additional workflow rules with separate Field Extraction actions.
12. How to configure Field Extraction in a workflow?
- Go to Setup > Automation > Workflows and click Create New Rule.
- Select the Tickets module, enter a Rule Name and Description, and click Next.
- Select when to execute the rule (typically Create for new tickets).
- Add criteria if needed.
- Under Actions, select Field Extraction.
- In the Field Extraction page:
- Text to analyze: Select the fields from the placeholder panel that Zia should analyze (e.g., ticket description, email content).
- Field and sample format: Select the target fields (email, phone number, etc.) from the drop-down and optionally provide a sample format (e.g., mm/dd/yyyy or 123-0000-999).
- Click Save.
13. Is the sample format mandatory when configuring Field Extraction?
No, Providing a sample format is optional. However, it can improve extraction accuracy by giving Zia a pattern to match against. For example, if your order numbers follow a specific format like ORD-2025-XXXX, providing that as a sample format helps Zia identify and extract the correct value.
14. How accurate is Field Extraction?
Zia's extraction is generally reliable for structured data types like emails, phone numbers, and dates. However, it is recommended to verify the extracted values to ensure complete accuracy, especially for fields with ambiguous or non-standard formats. Zia may occasionally misinterpret values if the email content is unclear or uses unconventional formatting.
Field Prediction
15. What does the Field Prediction action do?
Field Prediction analyzes the ticket's content — including the email body, thread replies, subject, description, and other fields available in the layout — to predict values for picklist and multi-select picklist fields. Unlike Zia's native field prediction feature, the workflow-based prediction does not require training. Zia evaluates the content and automatically maps the predicted values to the most relevant field.
For example, Zia can analyze a ticket description and thread replies to predict that a student would opt for admission in the "Autumn 2025 batch" and fill the "Admission on" field accordingly. Similarly, it can predict a VISA status as "Awaited" or "Delayed" based on the context of the conversation.
16. Which field types are supported by Field Prediction?
Zia can predict values for:
- Picklist fields
- Colored picklist fields
- Multi-select picklist fields
Standard text, number, date, and other field types are not supported for prediction.
17. How to configure Field Prediction in a workflow?
- Under Actions in the workflow rule, select Field Prediction.
- In the Field Prediction page:
- Text to analyze: Choose the fields Zia will use to predict values (e.g., description, subject, thread content).
- Field to predict: Select the target picklist or multi-select picklist field.
- Possible values: Choose the values Zia can assign to the field.
- Click Save.
18. Can Field Prediction be used for auto-triage?
Yes. Field Prediction is particularly powerful for auto-triage scenarios. By predicting case severity (Critical, High, Medium) and support level needed (L3, L2), Zia can auto-populate these fields, which can then trigger assignment rules or other workflow rules to route the ticket to the appropriate team or agent — all without human intervention.
For example, if Zia predicts severity as "Critical" and support level as "L3," a subsequent assignment rule can automatically route the ticket to the Tier 3 escalation team.
Generate Content
19. What does the Generate Content action do?
Generate Content creates AI-generated contextual text based on the ticket conversation. It can summarize long email threads, highlight key points, or generate concise explanations that help agents quickly understand the issue without reading through every detail. The generated content can be output as a private comment, public comment, or a field update.
For example, instead of an agent reading a 5-paragraph customer email, the Generate Content action produces: "Customer requesting refund for Order #2345, paid via credit card, product unused. Customer asks about return shipping and refund timeline." This summary is added as a private comment for other stakeholders to reference if they join the resolution at a later stage.
20. How to configure Generate Content in a workflow?
- Under Actions in the workflow rule, select Generate Content.
- In the Generate Content page:
- Text to analyze: Choose the fields Zia will use to generate the summary (e.g., description, thread replies, subject).
- Action to perform: Select Private comment, Public comment, or Field update.
- Prompt: Enter instructions or guidance for Zia to follow while generating the content (e.g., "Summarize the customer's issue and highlight any deadlines mentioned").
- Click Save.
21. What is the purpose of the Prompt field in Generate Content?
The Prompt field allows you to provide specific instructions to Zia about how it should generate the content. This gives you control over the tone, focus, and format of the output. For example:
- "Summarize the key issue and any actions requested by the customer."
- "Highlight any dates, deadlines, or SLA-relevant information mentioned in the thread."
- "Provide a brief overview of the customer's sentiment and urgency level."
The more specific your prompt, the more targeted and useful the generated content will be.
22. Should generated content be added as a private or public comment?
This depends on the use case:
- Private comment (recommended for summaries): Internal-facing, visible only to agents and stakeholders. Ideal for agent briefings, issue summaries, and internal context.
- Public comment: Visible to the customer. Use this only if the generated content is customer-facing, such as a simplified explanation of a technical issue.
- Field update: Useful if you want to store the summary in a custom field for reporting or dashboard purposes.
Auto Email Reply
23. What does the Auto Email Reply action do?
Auto Email Reply analyzes the content of an incoming customer email and, using the Answer Bot's training on your knowledge base, drafts and sends an automatic first response to the customer. The reply may include relevant article links, step-by-step instructions, or troubleshooting guidance to help the customer resolve the issue independently.
For example, if a customer asks, "How do I reset my password?" Zia can instantly reply with a step-by-step guide and a link to the relevant FAQ article — reducing the need for an agent to manually respond to common queries.
24. When does the Auto Email Reply trigger?
Auto Email Reply triggers only once per ticket, for the first response. It fires when:
- A ticket is created via the email channel.
- There is an incoming email thread.
- The email content has sufficient detail for Zia to generate a meaningful response.
- No agent has already sent an outbound reply to the ticket.
25. Under what conditions will Zia NOT generate an auto-reply?
Zia will not send an auto-reply if any of the following conditions are true:
Condition | Reason |
Ticket is not received via the email channel | Auto-reply only works for email-originated tickets |
There is no incoming email thread | Zia needs thread content to analyze and generate a response |
Email content lacks detail or has unclear language | Zia cannot generate a meaningful reply without sufficient context |
An outbound email has already been sent by an agent | Zia only sends the first response; if an agent has already replied, Zia will not override |
Answer Bot is not trained on the relevant topic | Zia cannot generate a reply without KB article references |
Knowledge Base lacks information on the customer's issue | No articles to reference in the auto-reply |
Zia was not continually trained on trending issues | Outdated training leads to inability to recognize new query patterns |
26. How to configure Auto Email Reply in a workflow?
- Go to Setup > Automation > Workflows and click Create New Rule.
- Select the Tickets module, enter a Rule Name and Description, and click Next.
- Set the rule to execute on Ticket Creation.
- Under Actions, select Auto Email Reply.
- Configure the following:
- Ticket ID: Auto-populated, cannot be modified.
- User Reply Address: Select the agent's email address.
- From Address: Select the sending email address.
- To Address: Select the customer's email field (e.g., contact's email) from the placeholder panel.
- Email Reply Template: Review and customize the provided response template if needed.
- After Zia sends a reply: Select a field and its corresponding value to update (e.g., set "Auto response sent" to "Yes").
- If Zia cannot send a reply: Select a fallback field and its corresponding value (e.g., set "Auto response sent" to "Failed").
- Click Save.
27. How to track the success rate of Auto Email Reply?
During configuration, you can set up field updates for both success and failure scenarios:
- On success: Update a custom field (e.g., "Auto response sent") to "Yes" when Zia successfully sends a reply.
- On failure: Update the same field to "Failed" when Zia cannot send a reply.
User can then create a custom view called "AI-based Auto Reply Dashboard" to filter and track tickets where the auto-reply succeeded or failed. This allows support managers to monitor Zia's effectiveness, identify knowledge base gaps, and refine Answer Bot training.
28. Does Auto Email Reply work for non-email channels?
No, Auto Email Reply works only for tickets created via the email channel. Tickets created through web forms, chat, social media, or instant messaging will not trigger the auto-reply action.
Integration and Interaction with Other Features
29. How do Zia Actions interact with other workflow actions in the same rule?
Zia Actions can coexist with standard workflow actions (alerts, tasks, field updates, custom functions, and custom actions) in the same rule. All actions execute when the rule's criteria are met. However, since Zia Actions have a daily execution limit of 1,000 per organization, they may not execute if the limit has been reached — even if the standard actions in the same rule continue to fire.
30. Can Zia Actions trigger other workflow rules?
Indirectly, yes. If a Zia Action (such as Field Extraction or Field Prediction) updates a field on the ticket, and another workflow rule is configured to trigger on field updates with criteria matching the newly populated value, that second rule will fire. This creates a cascading automation effect — for example, Zia predicts severity as "Critical," which triggers a separate workflow rule that escalates the ticket to a manager.
31. Do Zia Actions work with Blueprint?
Zia Actions are associated with workflow rules, not directly with Blueprint transitions. However, since workflow rules execute before blueprints in the automation hierarchy, Zia Actions can modify a ticket (extract fields, predict values, generate summaries) before the blueprint evaluates it. This means the blueprint's transition logic operates on a ticket that has already been enriched with AI-extracted and AI-predicted data.
32. Can Zia Actions be used across multiple departments?
Zia Actions are configured per workflow rule, and workflow rules are department-specific. You can create separate workflow rules with Zia Actions in each department. However, the 1,000-execution daily limit is shared across the entire organization, so high-volume departments may consume the limit faster. For Auto Email Reply specifically, the Answer Bot must be configured and trained in the same department where the workflow is created.
Edge Cases and Troubleshooting
33. What happens if Zia extracts or predicts an incorrect value?
Zia's AI-driven extraction and prediction are not infallible. If an incorrect value is populated:
- Field Extraction: The extracted value will be auto-filled in the ticket field. Agents should verify extracted values, especially for critical fields. Incorrect values can be manually corrected by any agent with edit permissions.
- Field Prediction: The predicted value will be auto-filled in the picklist field. Agents can override the prediction by manually selecting a different value.
There is no automatic rollback mechanism — once Zia populates a field, the value remains until manually changed.
34. What happens if the daily execution limit is reached mid-day?
Once the 1,000-execution limit is reached, all subsequent Zia Actions across all workflow rules will not execute for the remainder of the day. The standard workflow actions (alerts, tasks, field updates) in the same rules will continue to fire normally. The execution counter resets at the start of each day. There is no alert or notification sent to administrators when the limit is reached — you would need to monitor execution volumes proactively.
35. Can the email template used by Auto Email Reply?
Yes. During configuration, the Email Reply Template field allows you to review and modify the provided response template. You can customize the tone, structure, and content of the template. However, the actual AI-generated reply content (the specific answer and article links) is determined by Zia at runtime based on the customer's query and the Answer Bot's training.
36. What happens if a customer replies to a Zia-generated auto-reply?
If a customer replies to the auto-reply, the response is treated as a new incoming thread on the same ticket. Zia's Auto Email Reply will not fire again — it only sends the first response. Subsequent replies will follow standard ticket routing and workflow rules. An agent will need to handle the follow-up manually unless other automation rules are configured.
37. Can Generate Content be used to create customer-facing responses?
Yes, by selecting Public comment as the action to perform. However, exercise caution — AI-generated content may occasionally include inaccuracies or tone inconsistencies. It is recommended to use Generate Content primarily for private comments (internal agent briefings) and reserve customer-facing communication for the Auto Email Reply action, which is specifically designed and trained for customer responses.
38. What happens if Generative AI is disabled after Zia Actions are configured?
If an administrator disables Generative AI (via Setup > Zia > Generative AI > Zia Actions), all Zia Actions across all workflow rules will immediately stop executing. The workflow rules themselves remain active, and any standard actions (alerts, tasks, field updates) will continue to function. The Zia Action configurations are preserved and will resume execution if Generative AI is re-enabled.
39. Can Zia Actions process tickets in languages other than English?
No, All four Zia Actions — Field Extraction, Field Prediction, Generate Content, and Auto Email Reply — are supported only in English. If a ticket is submitted in another language (e.g., Spanish, French, German), Zia will not process it. The workflow rule may still trigger, but the Zia Action within it will not produce any output for non-English content.
Access your files securely from anywhere
Zoho CRM Training Programs
Learn how to use the best tools for sales force automation and better customer engagement from Zoho's implementation specialists.
Zoho DataPrep Personalized Demo
If you'd like a personalized walk-through of our data preparation tool, please request a demo and we'll be happy to show you how to get the best out of Zoho DataPrep.
- Zoho Workerly Home
- Forums
- Connect With Us:
- Zoho Recruit Home
- Forums
- Connect With Us:
Zoho FSM Video Tutorials
Centralize Knowledge. Transform Learning.
All-in-one knowledge management and training platform for your employees and customers.
New to Zoho Writer?
Create. Review. Publish.
New to Zoho CRM Plus?
Deliver unforgettable customer experiences
New to Zoho CRM Plus?
Deliver unforgettable customer experiences
New to Zoho Marketing Plus?
Everything you need to run your marketing
New to Zoho Marketing Plus?
Everything you need to run your marketing
You are currently viewing the help pages of Qntrl’s earlier version. Click here to view our latest version—Qntrl 3.0's help articles.
New to Zoho Survey?
Zoho Sheet Resources
Zoho Forms Resources
New to Zoho Sign?
Zoho Sign Resources
Sign, Paperless!
New to Zoho TeamInbox?
Zoho TeamInbox Resources
New to Zoho CPaaS?
Design. Discuss. Deliver.
New to Zoho Workerly?
New to Zoho Recruit?
New to Zoho CRM?
New to Zoho Projects?
New to Zoho Sprints?
New to Zoho Assist?
New to Bigin?
Related Articles
FAQs: AI-powered Workflow Automation with Zia Actions
What are the key benefits of using Zia Actions in workflows? Faster ticket handling - Automatically extracts details like order number, purchase date, or product type from a customer’s email and fills them into the ticket. For example, if a customer ...Understanding Zia Auto Tags
A tag is a label or identifier that helps to categorize tickets into different groups. They facilitate better ticket management and clearing the triage by allowing the support team to focus on tickets that require immediate attention. For example, ...FAQs: Workflow Rules
1. What is a Workflow Rule? A Workflow Rule is an automation mechanism that executes a predefined set of actions — alerts, tasks, field updates, and custom functions — when specific conditions are met on a record. Instead of requiring agents to ...FAQs: Zia Dashboard
Access and Enablement What is the Zia Dashboard used for? Zia Dashboard provides visual dashboards for analyzing support operations. It is part of a larger system (implied to be a customer support platform) and can help businesses understand and ...Predict Picklist Field Values Using Field Predictions
Better customer service that eventually results in long-term engagement and builds stronger relationships with the customers is an asset that every business wants to invest in. While on the surface, customer support service may seem just about ...
New to Zoho LandingPage?
Zoho LandingPage Resources