🟩 1. What Is a Blueprint in Zoho Desk?

A Blueprint is a guided, step‑by‑step workflow that ensures agents follow the correct process for every ticket. It defines:

• What steps must be followed

• Who performs each step

• What conditions must be met

• What actions happen automatically

Blueprints ensure zero mistakes, consistent service, and perfect compliance.

🟩 2. Why Use Blueprints?

• Standardize your support process

• Ensure agents follow required steps

• Reduce errors in service, warranty, and billing

• Automate repetitive actions

• Improve customer experience

• Enforce approvals and validations

• Perfect for multi‑step workflows

🟩 3. Where Blueprints Are Useful (Kanchan Electronics Examples)

• Warranty approval workflow

• Service visit workflow

• Replacement approval workflow

• Refund processing workflow

• Installation request workflow

• Escalation handling workflow

🟩 4. Blueprint Structure (Two Main Parts)

1. States

These are the stages of your process. Examples:

• Open

• Under Inspection

• Waiting for Parts

• Approved

• Rejected

• Completed

2. Transitions

These are the actions that move a ticket from one state to another. Examples:

• Start Inspection

• Approve Warranty

• Request Parts

• Complete Service

• Close Ticket

🟩 5. How to Create a Blueprint (Step‑by‑Step)

Step 1: Go to Setup

Click the gear icon in Zoho Desk.

Step 2: Select “Blueprint”

Under Automation.

Step 3: Choose the Module

Select Tickets.

Step 4: Choose the Field to Control

Usually Status.

Step 5: Define States

Add all stages of your workflow.

Step 6: Draw Transitions

Connect states with arrows to define the flow.

Step 7: Configure Each Transition

For every transition, set:

• Before Transition (conditions)

• During Transition (mandatory fields, notes, approvals)

• After Transition (automation actions)

Step 8: Publish Blueprint

Your workflow is now active.

🟩 6. Example Blueprint for Kanchan Electronics

Warranty Claim Workflow

States:

• Open

• Under Inspection

• Warranty Approved

• Replacement Issued

• Closed

Transitions:

• Start Inspection

• Approve Warranty

• Issue Replacement

• Close Ticket

During Transition Requirements:

• Upload product image

• Enter serial number

• Add inspection notes

• Manager approval for replacement

🟩 7. How Agents Use Blueprints

When an agent opens a ticket:

• They see the current state

• They see allowed transitions

• They must complete required fields

• They cannot skip steps

• They follow the workflow until completion

Blueprints guide agents like a checklist.

🟩 8. Best Practices

• Keep workflows simple

• Use mandatory fields wisely

• Add approvals only where needed

• Test blueprint before publishing

• Review workflows every 6 months

• Use automation inside transitions

🟩 FAQs

Q1. Can I edit a Blueprint after publishing? Yes, but changes affect all new transitions.

Q2. Can each department have its own Blueprint? Yes, Blueprints are department‑specific.

Q3. Can Blueprints trigger automation? Yes, transitions can run actions like emails, assignments, and field updates.