FAQs: Blueprint

1. What does the error message "Unable to process your request" mean when I try to modify my Blueprint?

This error can happen if there are tickets currently associated with the transition or state you're trying to delete or modify within the Blueprint. Zoho Desk restricts modifications in such cases to avoid disrupting active ticket workflows.

Verify if any tickets are still within the state you want to delete. If there are, revoke the tickets. Ensure you revoke your tickets from "All Tickets" in the ticket module.

2. How do I manually associate a ticket with a Blueprint?

No, you cannot associate a Blueprint manually with a ticket. However, there is a workaround to ensure that all tickets go through the Blueprint.

Setting the Blueprint criteria to All records ensures all tickets created within the specified department trigger the Blueprint automatically and are subject to its control.

If a ticket was added without meeting the Blueprint’s criteria, you can still modify or add new criteria to apply the Blueprint to that ticket.

Steps to modify Blueprint criteria and apply it to a ticket:

1. Go to Set up > Automation > Blueprint.

2. Select the Blueprint you want the ticket to be associated with.

3. Click Blueprint Info in the right panel.

4. Select the Edit icon next to the entry criteria.

5. Under Specific Records, click the + symbol to add a new criterion that matches your ticket.

6. Define a simple criterion that aligns with the ticket's details, such as "Team + is + Development."

Important: Click the AND button to switch it to OR, which allows the blueprint to trigger based on one criterion rather than requiring multiple conditions.

7. Click Done and then Save & Complete Blueprint to confirm the updates.

8. All the tickets created by this team will be associated with this specific Blueprint.

After these steps, the Blueprint will apply to the manually added ticket and incorporate it into the specified workflow.

3. How can I rename a status in a Blueprint?

To rename a ticket status in Zoho Desk:

Navigate to Setup → Customization → Layouts and Fields → Ticket Status.
Hover over the status you want to rename.
Click on the options menu (three dots) that appears.
Select Rename.
Enter the new name in the Enter the new name field.
Click Save.

Once renamed, the updated status will automatically reflect in all associated Blueprints.

4. How many Blueprints can I create per department in Zoho Desk?

The number of Blueprints you can create depends on your subscription plan:

Standard plan: No Blueprints.
Professional plan: Allows 1 Blueprint per department.
Enterprise plan: Supports up to 20 Blueprints per department.

5. Can I notify my customer about the ticket closure within a Blueprint?

Yes, you can notify your customer of the ticket closure within the Blueprint as a transition. You can send a ticket closure notification to your customer with many actions.

Enable Closing a Ticket under Contact Notification option in Set up → Customization → Notification

.

But, if you want to set up customer notifications for the closure of specific Blueprint-associated tickets only, You can follow the steps below.

1. Create a custom check box field (Send notification) with the option disabled by default in the ticket layout.

Go to Set up → Automation → Workflows → New Rule
To trigger this workflow rule set the Execute on to Field update → Status

Also, set Criteria → Status is "Closed" AND Check box is true.

In All actions, go to Set alerts and select the email template Notify contact on ticket closure and check Notify Contact.
Save the rule.
As a final step, go to your Blueprint and select the transition that closes the ticket.
Add the Send notification field operation to the During tab of the Closed transition and make it mandatory.

6. How do I disable the Revoke Blueprint option?

You cannot remove the Revoke Blueprint button itself because it’s essential for revoking tickets that are stuck or looped in the Blueprint process.

However, you can restrict access to this option by adjusting permissions:

1. Go to Setup > Users Management > Profiles.

2. Select the Agent profiles and any other roles you wish to restrict.

3. Under Ticket Permissions, disable the "Revoke Blueprint" option to prevent those profiles from accessing this feature.

7. How do I count ticket transitions through each stage in Blueprint?

Blueprints do not track the number of times a ticket has entered a particular status. While you can configure various stages and transitions, the tracking of status history isn’t directly available within Blueprints.

An alternative solution is to use the Ticket Stages Report, which provides insights into the time a ticket has spent in each stage. You can use it to observe how often tickets pass through particular stages by manually reviewing the history, although it won’t provide exact counts without additional filtering.

To track your ticket stage report:

1. Go to the Analytics Module

2. Open the Reports Tab in the left panel → Ticket Stages

3. The report will display tickets along with the stages they've passed through and the duration spent in each stage.

4. To find how often a ticket has entered a particular status, examine the stage history for each ticket.

8. Is it possible to add a validation rule to a Blueprint transition?

Yes, you can add a validation rule to your During Transition. For example, if a specific field should not be empty during a transition, you can set up validation to ensure it’s filled out before the transition completes.

To Apply a Validation Rule in Blueprint:

1. Go to Set up → Automation → Blueprint.

2. Find the Blueprint associated with your workflow, or create a new one.

3. In the transition settings, scroll down to the During Transition section.

4. Add a field operation and click on the Validation option next to the field.

5. Click Update and then Save to update the Blueprint.

9. Is it possible to reopen my ticket automatically?

Fall back to default is when the customer replies to the ticket, the status will change back to the default, which is "Open", but as an alternative solution you can set up a workflow triggered by customer response to change the status from "On Hold" or "Closed" to "Open."

To create a workflow rule:

1. Navigate to Setup → Automation → Workflows.

2. Click Create Rule.

3. Choose the Tickets module.

4. Give a name for the rule, e.g., "Reopen Ticket on Customer Reply".

5. Check the rule trigger as Customer Reply.

6. Set the Criteria as

Status is On Hold (or)
Status is Closed

7. Under Actions, add Field Update as Status -> Open.

Optionally, add notifications or alerts to inform agents about the status change.

8. Click Save

10. Can I assign a transition owner from different departments?

Yes, you can assign transitions across multiple departments and agents with no restrictions on roles using Blueprints.

1. What is a Blueprint?

A Blueprint is a structured, visual framework that defines the exact sequence of stages and transitions a ticket must follow from creation to resolution within a department. It enforces a standardized process by clearly defining transitions, mandating fields, approvals, and assigning responsibilities at each stage. This eliminates ad-hoc handling, reduces manual errors, and ensures every ticket is resolved in a compliant, traceable manner.

For example, in a software support team, a blueprint could define the following flow: Open → Analyze → Reach Out to Customer → Provide Resolution → Close. Every agent handling a ticket in that department must follow these stages in order — they cannot skip directly from "Open" to "Close" without passing through the intermediate transitions.

2. How is a Blueprint different from a Workflow Rule?

A Workflow Rule triggers automated actions (like sending an email or updating a field) when specific conditions are met, but it does not enforce a sequential process. A Blueprint, on the other hand, dictates the path a ticket must take — agents can only move a ticket forward (or backward) through predefined transitions, and each transition can mandate specific fields, approvals, and owners. In short, workflow rules automate actions; blueprints enforce process compliance.

3. Who can create and manage blueprints?

Only users with the Support Administrator permission can create, edit, deactivate, and delete blueprints. Standard agents without this permission profile cannot access the Blueprint configuration page, though they can still perform transitions on tickets if they are designated as transition owners.

4. Can agents view blueprints on mobile devices?

Yes. In the Zoho Desk mobile app (iOS), agents can view blueprint information and perform transitions. However, blueprints can only be created and configured through the web application — the mobile app is strictly for viewing and executing transitions. Agents can also revoke a blueprint from a ticket via the mobile app by tapping the More icon and selecting Revoke Blueprint.

5. What are the step-by-step instructions to create a blueprint?

Navigate to Setup > Automation > Blueprint > Create Blueprint.
On the Create Blueprint page, enter the blueprint Name and Description.
Select a layout that is created in the respective department. The status field auto-populates based on the selected layout.
Select the record type:

Specific records — Apply the blueprint only to tickets matching specified field criteria.
All records — Apply the blueprint to all tickets in the department.

Select any advanced configuration options (Strict Mode, Dynamic Transition Owner Assignment, or Continuous Blueprint) based on your requirements.
Click Next.
On the blueprint canvas, drag and drop the required states.
In the transition tab, enter the transition name and description.
Select the conditions to be performed before, during, and after the transition.
Click Save & Complete Blueprint.

6. What is a "state" in a blueprint?

A state represents a stage in the ticket lifecycle — such as "Open," "On Hold," or "Closed." States are the nodes in the blueprint flow, and transitions are the connections between them. A ticket must be in one state at any given time, and it can only move to another state by performing the transition that connects the two.

7. What is a "transition" in a blueprint?

A transition is the action that moves a ticket from one state to another. Each transition can include:

Before conditions: Criteria or actions that must be satisfied before the transition can be performed (e.g., a mandatory field must be filled).
During conditions: Actions executed while the transition is being performed (e.g., sending a notification).
After conditions: Actions executed after the transition is completed (e.g., updating a field or triggering an approval).

For example, a transition named "Escalate" might move a ticket from "Open" to "Escalated," require the agent to fill in a "Reason for Escalation" field (before), send an email to the manager (during), and update the ticket priority to "High" (after).

8. What happens when I select "Specific records" vs "All records"?

Specific records: The blueprint applies only to tickets that match the field criteria you specify. For instance, you could apply a blueprint only to tickets where the Category is "Hardware Issue" and the Priority is "High." This is useful when different ticket types require different processes.
All records: The blueprint applies to every ticket in the department, regardless of field values. This is suitable when all tickets in a department should follow the same standardized process.

9. What is Strict Mode and when should I enable it?

Strict Mode prevents agents from performing actions outside of a transition — including editing fields, sending replies, adding comments or resolutions, and uploading attachments. When enabled, agents can only interact with the ticket through the blueprint's defined transitions.

Administrators can apply Strict Mode to:

All agents
Specified agents only
All except specified agents

This is particularly valuable in regulated environments (e.g., healthcare or finance) where every action must be logged and auditable. For instance, if an agent must fill in a "Resolution Summary" field as part of the "Resolve" transition, Strict Mode ensures they cannot close the ticket without going through that step.

10. What is Dynamic Transition Owner Assignment?

Dynamic Transition Owner Assignment allows administrators to assign transition owners within a record at runtime, rather than fixing them at the blueprint configuration level. Owners can be assigned from:

The current department — The agent or team responsible for the transition is from the same department as the ticket.
Other departments — The record is automatically shared with the assigned agent's department, enabling cross-departmental collaboration.

For example, a ticket starts in the "Support" department, but the "Approve Refund" transition is dynamically assigned to an agent in the "Finance" department. The ticket record is automatically shared with Finance so their agent can complete the transition.

11. What is a Continuous Blueprint?

When enabled, a Continuous Blueprint automatically triggers the next transition in the sequence as soon as the current transition is completed — without requiring manual agent intervention. This is useful for processes where transitions are purely systemic and don't require human decision-making.

For example, after an agent performs the "Submit for Approval" transition, the "Approve" transition could automatically fire if an auto-approval rule is met, followed by the "Notify Customer" transition — all without the agent needing to manually click through each step.

12. Can transition owners be from a different department?

Yes. Administrators can select agents from other departments as transition owners. When this happens, the ticket record is automatically shared with the assigned agent's department, ensuring the agent has the necessary access to perform the transition. This is tightly integrated with the Dynamic Transition Owner Assignment feature.

13. What happens if an agent is not assigned as a transition owner?

Only designated transition owners can perform a specific transition on a ticket. Agents who are not assigned as owners cannot perform the transition — the transition will not be visible or actionable to them. This enforces accountability and ensures the right person handles each step.

14. Can a blueprint edited after it has been created?

Yes. A blueprint can be edited at any time. Navigate to Setup > Automation > Blueprint, select the required blueprint, make the necessary changes, and click Save Blueprint. Changes take effect immediately for new tickets entering the blueprint. Tickets already in progress will continue following the blueprint based on the updated configuration.

15. What happens when a blueprint is deactivated?

Deactivating a blueprint means no further tickets will follow that blueprint process. Existing tickets already in the blueprint will continue through their current transitions, but new tickets will not be routed into it. The blueprint can be reactivated later if needed. To deactivate, navigate to Setup > Automation > Blueprint, toggle off the active option, and click Deactivate to confirm.

16. Can a blueprint be deleted?

Yes, but with an important restriction: if there are any active tickets currently in progress within the blueprint, it cannot be deleted. You must first ensure all tickets have completed or exited the blueprint process. To delete, navigate to Setup > Automation > Blueprint, click the More icon next to the blueprint, and select Delete. Confirm on the dialog screen. Deletion is permanent and cannot be undone.

17. Is there a Blueprint Dashboard and what metrics are available on the Blueprint Dashboard?

Yes, Zoho Desk provide a Blueprint Dashboard which is a department-specific monitoring tool that allows managers to track the effectiveness and adherence of blueprint processes. It provides insights into active tickets, SLA violations, transition performance, and agent-level metrics.

The dashboard provides the following high-level metrics:

Active blueprint tickets: The number of tickets currently progressing through blueprints.
SLA violated tickets: The number of tickets that violated the overall SLA defined in the blueprint.
All transitions: The number of tickets that went through all transitions as defined in the blueprint.

18. What Blueprint Dashboard components provide deeper insights?

Component	Description
Active and completed records	Shows tickets currently in the blueprint (active) vs. tickets that have completed or exited the process.
SLA violated states	Displays how long tickets stay in each state (Open, On Hold, Closed) and whether they violate the SLA defined for that state. Helps identify unrealistic SLA targets.
SLA violated vs. adherence records	Compares the percentage and count of tickets that violated SLA targets vs. those that met them, showing team consistency.
Average time per blueprint	Shows the average time taken per transition across each blueprint. Useful for comparing different blueprint types (e.g., bug fix vs. feature request).
Average time per state	Shows the average time a ticket spends in each state from Open to Closed, helping identify bottlenecks.
Transition occurrence	Displays how many times a particular transition is performed. High occurrence of a specific transition (e.g., "Escalated") may indicate a process gap.

19. How to filter the Blueprint Dashboard?

By default, the dashboard displays data from the last 24 hours. You can filter by:

Blueprint name: All blueprints created in the department are listed for selection.
Duration: Last 24 Hours, Today, Yesterday, Last 7 days, Last 30 days, Current week, Last week, Current month, Last month, or a Custom range.
Agent: The "All agents" dropdown in the top-right corner allows filtering transition occurrence data by individual agent.

20. How can the Blueprint Dashboard help identify process gaps?

The Transition Occurrence chart is particularly useful for this. If a specific transition — such as "Escalated" — is performed repeatedly on the same tickets, it signals that tickets are cycling back to a state multiple times, indicating a bottleneck or a process deficiency. For example, if the average response time for a ticket is 4 hours but responses are being sent at 10 hours, the "Escalated" transition would fire repeatedly, and the dashboard would surface this pattern for managerial investigation.

Similarly, the SLA Violated States component helps identify whether SLA targets are realistic. If the SLA for an "On Hold" state is set to 7 days but tickets routinely stay there for over a month, the data suggests the SLA should be adjusted to reflect actual operational timelines.

21. What happens if a ticket matches the criteria of a deactivated blueprint?

A deactivated blueprint will not be applied to any tickets, even if they match its record criteria. The ticket will simply bypass that blueprint and may be evaluated against the next active blueprint in the execution order (if one exists). If no active blueprint matches, the ticket will follow the standard department workflow without blueprint enforcement.

22. Can an agent bypass a mandatory field defined in a transition?

No, If a field is marked as mandatory within a transition's "before" conditions, the agent cannot complete the transition without filling in that field. This is one of the core enforcement mechanisms of blueprints — it ensures data completeness at each stage. However, if Strict Mode is not enabled, agents may still be able to edit other fields on the ticket outside of the transition.

23. What happens to in-progress tickets when a blueprint is edited?

When you edit and save a blueprint, the changes take effect immediately. Tickets already in progress will follow the updated configuration for any transitions they have not yet performed. If you remove a state or transition that a ticket is currently in, the ticket may become stuck — in such cases, you may need to revoke the blueprint from that ticket or manually adjust its status.

24. Can a blueprint be revoked from a specific ticket?

Yes. On both the web application and the iOS mobile app, you can revoke a blueprint from an individual ticket. On the mobile app, open the ticket, tap the More icon, and select Revoke Blueprint. This removes the ticket from the blueprint process, allowing it to be handled freely without transition enforcement.

25. Does the blueprint override manual status changes?

Yes. When a blueprint is active on a ticket, the agent can only change the ticket's status by performing a defined transition. Manual status changes outside of the blueprint's transitions are blocked. This ensures the ticket follows the exact path defined by the blueprint, preventing agents from skipping steps or moving tickets to unauthorized states.

26. What is the maximum number of transition connections per state?

A single state can have up to 16 transition connections (combined input and output points). This means you can design complex branching and merging patterns — for example, a single "Triage" state could have outgoing transitions to "Assign to L1," "Assign to L2," "Escalate to Manager," and "Close as Duplicate," while also receiving incoming transitions from "New Ticket" and "Reopened."

FAQ: Blueprint | Zoho Desk

FAQs: Blueprint