Components of a Blueprint

In Zoho Desk Blueprints, "stages" represent distinct steps or milestones in a business process, while "transitions" define the movement and conditions required to progress from one stage to another. 

Stages

Stages are the specific checkpoints or states that a support ticket or record passes through in a process, such as "Assigned," "In Progress," "Awaiting Response," or "Closed." Each stage captures the ticket's status at a given point in time and provides visibility into the process's progress.

Transitions 

Transitions are the actions, criteria, and intermediate checkpoints required to move a ticket from one stage to another. A transition can enforce checks, require specific actions, or mandate that fields be completed before advancing to the next stage. Transitions can also be configured to trigger automations, send notifications, or assign ticket owners.

• The criteria for when the transition is allowed
• The actions to perform during the transition (updating fields, completing checklists, sending messages)
• Transition ownership (who can act)
• Automated actions are triggered upon execution

Highlights

Enabling Strict Mode ensures that agents strictly follow ticket processes. When activated, all other actions in the ticket interface are disabled, allowing agents to perform ticket-related actions exclusively through the transition bar.

Admins can now selectively set which actions and fields are required during a transition. The introduction of the Configure Mandatory option enhances this capability to provide greater control and flexibility in customizing Blueprints for various groups of agents and refining specific aspects of the support process.

Admins can now effortlessly prioritize and reorder transitions with a simple drag-and-drop feature. This allows them to easily arrange the sequence of transitions in a Blueprint to determine how they are presented to agents. In the past, this process required agents to delete and re-add transitions in the desired order, which was time-consuming and labor-intensive.

The number of Points and Transitions permitted in a blueprint dictates the complexity of the internal processes you can design for your team. We have increased the number of pointers and transitions to allow you to incorporate greater complexity into your support operations as needed. 

When developing a Blueprint, you may find the need to rename a State or modify its Status Type after it has already been linked to the blueprint. This was not an option previously, but we've now made it possible. You can now change the Status Type and rename states associated with a blueprint.