# Blueprint Vs Journey Builder — Similarities and differences

## Blueprint Vs Jouney Builder in Zoho CRM

Blueprint and Journey Builder in CRM may have technical similarities in terms of the components of the builder — such as States, Transitions and automated actions.

However, since they primarily differ in their purpose and objective, there is ideally no room for confusion in what they set out to accomplish.
The confusion, if any, between Blueprint and Journey Builder could arise from the fact that both the solutions have similar building blocks — States, Transitions, and Actions. This is because both the solutions are developed based on the concept of Finite State Machine (FSM).

## Finite State Machine (FSM) — The Model Behind the Process Builders

FSM is a mathematical model that is widely used to devise sequential systems in the fields of software, gaming, AI and more.
"It is an abstract machine that can be in exactly one of a finite number of states at any given time. The FSM can change from one state to another in response to some inputs; the change from one state to another is called a transition. An FSM is defined by a list of its states, its initial state, and the inputs that trigger each transition."

Some real-world examples of FSM include a coin-operated turnstile that is widely seen in Metro railway stations, or elevators, combination locks and vending machines. A turnstile can only be in a locked or unlocked state — so there are two states (finite). In order to move from locked to unlocked, it needs a coin. The coin triggers the transition between State A to State B. While it is unlocked, a coin won't put it back to the lock state— it needs to be turned and clicked back into position. Similarly, without a coin, you cannot open it either. So it is a clear and foolproof system — purchase a coin to unlock your way through the turnstile.

In software, various BPM solutions have been modeled on the Finite State Machine, and therefore are bound to be similar. They are all likely to have states and transitions, as that is what the Finite State Machine method primarily involves.

Therefore, Blueprints and Journey Builder in Zoho CRM, which are both modeled on the Finite State Machine, contain the same building blocks — States, Transitions, and Actions. However, what you do with these components differs in both, because the objectives of both solutions are different. Here are some fundamental factors of differences between the two.

### Primary purpose

Blueprint is a business process management tool to promote compliance, whereas Journey Builder is a tool to optimize the customer journey across business touch points.

### States in a process Vs states in a journey

States in Blueprint are built out of picklist values present in a record's layout. Because it helps manage compliance, Blueprint allows you to consider pick-list values like lead status, deal stage, as stages and helps you govern a record's progression across different stages from the time of its creation.

States in the Journey Builder indicate where in the entire buying journey a customer stands. This state can be associated to a CRM module. For example, when a visitor signs up for your product, they can then be classified as a lead and their webform entry could be indicated in the Journey as a state called Lead Created mapped to the Leads module. As they traverse through the Journey, you need to instruct the CRM which module they need to be mapped to , in order to keep a track. Aside that States in Journey Builder are free-form states, as in, you can create a State of your choice as you build your Journey. They are not specifically from a pick-list field and do not need to be pre-defined unlike in a Blueprint.

### Transition Vs Triggers

Blueprints guide sales teams through a systematic process. As part of the guidance, Blueprint prompts data from teams at each stage, validates data received, and automates routine actions, thus promoting compliance across the board. The successful execution of a mandate, be it entering fields or fetching attachments or crossing out checklists, transitions the record from one state to another.

With Journey Builder, there is no question of "collecting data" or guiding teams, because that is not the objective. The objective is to orchestrate a series of events based on a previous outcome. For example, a website visit should prompt a live chat message for a visitor, and a subsequent chat response should alert an agent as well as send an acknowledgement to the customer's email. This email should subsequently trigger follow-up reminders to the agent to attend to the chat message. In this simple example, you can see how the objective is to automate a series of actions or events to make the customer's experience a pleasant one. This is not just for a single customer, but every customer going through the website and chat widget will receive this experience. Therefore, this is all about streamlining the customer journey across the board.

What moves a customer from one stage in their buying journey to another, is the signals or events received, when trigger or propel them forward in the journey. Based on these triggers, subsequent actions are framed. So the transition block here is not a data mandate but signals or events. Examples: Opening an email, Response to a survey, Filing a Desk ticket and so on.

## FAQs

### Is it accurate to say that, in Zoho CRM, Command Center is a "Blueprint across modules"?

No. It is not accurate to say so, because Blueprint and Command Center (Journey Builder) are essentially different in their objectives. It is true that currently Blueprint is built for a single module and Command Center can be built across modules. But this is a technical piece of difference and just because of this difference, one cannot assume that Journey Builder is a Blueprint across modules, because they are both meant to solve different problems.
1. Blueprint is meant for internal process streamlining and compliance.
Even if Blueprint were to soon be built across modules, it will continue to address compliance, so its workings will be different from that of a Journey Builder.

2. Whereas Journey Builder primarily helps you orchestrate a series of planned engagement actions across business touch points.
Even if it is built for a single module, it will comprise of triggers and engagement actions and not data mandates as in the case of a Blueprint.

### How is Journey Builder different from Cadence Studio?

Cadence Studio and Journey Builder are both Customer Experience Management solutions. They are both meant to streamline a series of engagement actions to help a customer in their buying journey. However, while Journey Builder aims to streamline customer journey across the board from lead creation to customer retention, advocacy and beyond,  Cadence Studio is an out-of-the-box solution for you to streamline just the follow-up series of actions. Depending on your exact need, you can choose the right solution.
1. Cadence Studio can be seen as a subset of the Journey Builder.
2. If your need is ONLY to streamline followup  actions — that is use a combination of Email, Task and Call to follow up with a prospect until a desired response is achieved— then use Cadences Studio.
3. You can achieve the above in Journey Builder as well, however it may be laborious in Journey Builder, now that Cadence Studio will help you achieve follow up orchestration in no time. The association of email, task or call, based on a previous open, click or bounce is more seamless and handled directly in the interface of Cadence Studio, that you don't have to configure these triggers meticulously in Journey Builder.
4. This way you can also offload all the follow-up based engagement orchestration from Journey Builder to Cadence Studio and effectively use Journey Builder to focus more on dedicated engagement actions after a successful follow up.
5. Cadence Studio is effective during lead management until your prospect is engaged. Journey Builder could be more effective to continue engagement after the first successful contact and go on to streamline the journey till purchase, retention, loyalty and advocacy.

### How is Kiosk Studio different from Wizards? Is Kiosk Studio a process management solution?

Kiosk Studio and Wizards are both solutions to customize your Zoho CRM account. Kiosk Studio is essentially a customization solution, which helps customize your UI flows in order to execute ad-hoc processes. It is a no-code platform to create your own widget inside which you can perform customized actions such as data entry, retrieval, automation and so on. Whereas Wizards is a specific customization solution which focuses on data experience.

Wizards currently addresses the creation of a record in a systematic manner by breaking a long, cluttered form into more thoughtful segments or "screens", thereby making data entry a less confusing and even enjoyable experience. You can save a record as a draft, and come back to it when you are armed with more details. For example, you have a lead on the phone, and you are trying to explain your product to them. Some of the lead's fields such as details about their requirements, their company background etc are unclear to you during the call. So you can simply save the record as a draft and come back to it when you have all the details and then publish the record into the system. Therefore, Wizards focuses on achieving this flexibility with data experience in CRM. You can also automate alerts.  Learn more>> Help Document

Whereas Kiosk is not just about data entry or retrieval but also beyond that — it can help with data entry, retrieval, execution of alerts, custom functions and other routine actions. More importantly it can be deployed at a convenient location in your CRM such as the Home tab, List View or Detail view and even the Setup space. You can use it to fetch selected records and update specific information from multiple modules inside a single widget, you can use it as a call script, and pretty much customize it the way you want in your organization.

Here is a simple Kiosk for a company called Zylker Travels. Picture that a travel agent is on a phone call with a customer. The customer wants to quickly reschedule their trip. It may be difficult for the agent to navigate to the right module and update the correct fields. So Zylker has created a Kiosk, without the help of a developer, to create a customized widget and deployed it on the Home page, so that the agent can quickly access it, interact with the widget, update only the relevant fields, and navigate a flexible and super easy UI flow that is specific to their organization.

This is what the configuration of a Kiosk looks like:

### Can a Blueprint, Journey Builder and Cadence flow all run their flows without any problems?

Yes, all the process management and automation solutions including Blueprint, approval process, review process, Journey Builder, Path Finder and Cadence Studio will run without interrupting each other. For example, a record converted via a Journey Builder could enter the Contacts module and start following the Contact Management Blueprint applicable without any interruptions. That is what it is expected to do.

You are only recommended to watch out for duplication of actions in multiple features such as the same email in Journey Builder, Workflows and Cadence Studio for example. If you have multiple configurations in each of these setup, they will all get executed so your customer may end up getting 3 emails in this case. Make sure to not configure the same actions on the same touchpoints across these feature sets and you should be able to get all of these to function seamlessly.

### Zoho CRM Training Programs

Learn how to use the best tools for sales force automation and better customer engagement from Zoho's implementation specialists.

Redefine the way you work
with Zoho Workplace

### 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.

Create, share, and deliver

beautiful slides from anywhere.

Zoho Sign now offers specialized one-on-one training for both administrators and developers.

 Quick Links Workflow Automation Data Collection Web Forms Enterprise Begin Data Collection Interactive Forms Workplace Data Collection App Offline Forms Customer Service Accessible Forms Digital Forms Marketing Forms for Small Business HTML Forms Education Zoho Forms for Enterprise Contact Forms E-commerce Lead Generation Forms Healthcare Wordpress Forms Customer onboarding No Code Forms Construction Free Forms Travel Prefill Forms Non-Profit Intake Forms Legal Form Designer HR Card Forms Assign Forms Translate Forms Electronic Forms Notification Emails for Forms Holiday Forms Form to PDF Drag and Drop form builder

Zoho Pagesense Resources

New to Zoho Survey?

Manage your brands on social media

Zoho Desk Resources

• Desk Community Learning Series

• Digest

• Functions

• Meetups

• Kbase

• Resources

• Glossary

• Desk Marketplace

• MVP Corner

• Word of the Day

# Zoho Sheet Resources

New to Zoho Forms?

# Zoho Forms Resources

communication with Zoho Mail

Mail on the move with
Zoho Mail mobile application

Stay on top of your schedule
at all times

Anytime, anywhere

# Zoho Sign Resources

Sign, Paperless!

Sign and send business documents on the go!

Zoho SalesIQ Resources

# Zoho DataPrep Resources

Zoho DataPrep Demo

Get a personalized demo or POC

Design. Discuss. Deliver.

Create visually engaging stories with Zoho Show.

• # Related Articles

• ## Building Journeys Through Journey Builder

Important note: We recently introduced Path Finder- a journey discovery tool as part of our process management tool kit. So, in order to accommodate journey management activity as a whole, we have named the process management tool kit as ...
• ## FAQs: Blueprint

What is a Blueprint and how it is useful for my business? Blueprint in Zoho CRM is a sophisticated tool designed to digitally replicate and streamline a business's offline processes within the CRM software. It's particularly beneficial for companies ...
• ## Difference between CommandCenter, Blueprint, Orchestly, and Zoho Flow

This document will explain the difference between different Zoho applications that are used to build and manage business processes. Comparison metric CommandCenter Blueprint Orchestly Flow What does it let you do? Build a journey in CRM to get an ...
• ## Create a Continuous Blueprint

Unlike a regular blueprint, which is suitable for an intermittent process, a continuous blueprint allows you to design a process that occurs without any pauses. For example, call scripting. Scenario A sales organization wishes to create a continuous ...
• ## Blueprint - An Overview

Right from the moment you capture a lead in your CRM system up until deal closure and beyond, your organization may have several sales processes in place. For instance, leads generation and follow-up, deals closure and order management. Each of these ...
Wherever you are is as good as

# Resources

### Videos

Watch comprehensive videos on features and other important topics that will help you master Zoho CRM.

### eBooks

Download free eBooks and access a range of topics to get deeper insight on successfully using Zoho CRM.

### Webinars

Sign up for our webinars and learn the Zoho CRM basics, from customization to sales force automation and more.

### CRM Tips

Make the most of Zoho CRM with these useful tips.