Blueprint in Zoho Desk serves as a structured framework that guides the agents on the stages that are included in the ticketing process, from creation to resolution.
By standardizing the process and creating a blueprint, organizations ensure that every ticket in the department follows a predefined structure. With blueprint, organizations can clearly define transitions, mandate fields, approvals, and responsibilities at each stage. This avoids confusion, reduces manual errors, and ensures that service requests are handled in a systematic and compliant manner. They also provide visibility into the progress of tickets, enabling better monitoring, accountability, and performance tracking.
Users with Support administrator permission in their profile can access this feature.
On enabling this, admins can control whether agents can perform actions and update fields only through blueprint transitions or outside them. The restriction can be applied to all actions, only selected actions, or all actions except the selected ones.
ii) Dynamic Transition Owner Assignment
On enabling this, the support administrator can assign transition owners within the same within a record. They can assign transition owners from the current department or share the record with other departments for their agents to complete the transition.
iii) Is this a continuous Blueprint?
On enabling this, the next transition in a blueprint is automatically triggered as soon as the current transition is performed.
For example, an order processing workflow where a ticket moves through three stages: Order Verification, Payment Approval, and Order Confirmation. The admin assigns the Sales team as the transition owner for Order Verification. Once the Sales agent completes the verification, the next transition, Payment Approval, is automatically triggered.
The admin assigns a Finance agent from a different department as the transition owner for Payment Approval. The ticket is automatically shared with the Finance department. After the Finance agent approves the payment, the workflow proceeds to Order Confirmation.
Not enabling "Is this a continuous Blueprint" requires agents to manually move the record through each stage.
With these three advanced configurations, admins can control who exactly has access to what.
Creating a blueprint
Blueprints are department-specific. Select the department, and proceed to create a blueprint, which will apply only to the tickets of the appropriate department