[Early-access] Introducing Zoho's CommandCenter - Cross-Zoho business process automation

[Early-access] Introducing Zoho's CommandCenter - Cross-Zoho business process automation

 

Resources to help

Webinar recording | Documentation 

Feature Restrictions

Currently available on early-access only for US data center accounts

Features Role

CommandCenter as a Service uses signals across Zoho services to propel the movement of records through different stages of a business process


Note: CommandCenter was introduced as a feature within CRM in 2020. Zoho's CommandCenter is a standalone service that operates across Zoho platforms. 

For the sake of clarity, please note that in this post, we will refer to CommandCenter feature in Zoho CRM as "Zoho CRM's CommandCenter", and "CommandCenter as a Service", as "Zoho's CommandCenter"

CommandCenter is powered by signals. Signals are events performed in various arenas of Zoho applications that can be used to trigger the transition of a record to its next state. 

Signals serve as the backbone of the CommandCenter builder., Let's understand a little more about them. 

When you want to connect various customer touchpoints together, and build your customer journey end-to-end, there are many, touchpoints involved. 

Let's consider a real estate business powered by Zoho One end-to-end. .This company uses the following modules for their operations:
  •  Zoho CRM for client management
  • Zoho Finance for bookkeeping
  • Zoho Desk to provide support to clients
  • Zoho Meeting to setup online sessions with prospective clients 
- In their business process, each customer record moves through different stages in each of these services. For example, a lead moves from a "needs assessment" stage to a "needs assessed". 
- Here, for the record to move, it must transition through a stage of "assessment" where "type and budget" details are captured. This transition is fuelled by certain actions which we will configure. 
- In this example, we will configure the transition based on a trigger that the company brochure is downloaded or that a query is submitted on the website.

Each of the actions of updating these fields serve as a trigger for the movement of one or more record(s). We call these actions, "Signals".  At the backend, Signals route the events to multiple destinations. Signals can be setup for several Zoho services, including Zoho CRM. CommandCenter is setup such that any signal can be captured from other Zoho Apps to trigger the movement of a record to its next state.

Default signals - Default signals available in Zoho CRM, Desk, Survey, and Webinar are supported now. Default signals from other Zoho services, and third-party integrations will be supported down the line. 

Custom signals - API triggers or custom signals allow your system to use ANY event as your trigger, besides the readily available signals. Custom signals broaden CC's capabilities by allowing transition of records based on custom events that are specific to your business, making your mapped customer journey that much more accurate.

CommandCenter as a service ties together every single touchpoint of a record, mapping the whole customer journey with all its bits and pieces in ONE space. . Right from capturing information and creating leads, to the final stage, anything that can be automated is mapped within CC. Many of us are familiar with Zoho CRM's CommandCenter that runs and manage an entire business-process end-to-end. CRM's CommandCenter not only allows you to map your customer journey across multiple modules in a single space, but also guides and automates every action in a single space. Zoho's CommandCenter isn't an alternative to this, but an avenue to use and tie together your business processes, across multiple Zoho services. It uses triggers to execute different actions through different Zoho apps, at different stages (states) of a customer lifecycle. 

The main components of this tool are: 

States - The building blocks of a CC flow. They signify the state/stage a record is stationed at that point of the process. In our real estate example, we have many states. Pre-approval,  Funds processing, Inspection completion, Loan approval, etc

Transitions - The process initiating the movement of a record to its next state. A "Documents verification in progress", between the "Waiting for approval" and "Documents verified" states. 

Triggers - Triggers are our signals that propel the transition of records. Any default or custom signal can be used as a trigger for a transition.

Actions - At every stage, automated actions that are configured such as email alters, field updates, task creation, or any custom action.
Here's a quick overview on how Zoho's CommandCenter adds to the existing automation options. 



Comparison 1 - Workflows 
Comparison 2 - Blueprint
Feature
Help automate any set of actions within a module



Automation rules
Mandates certain actions from the user's end (manual) before a record is transitioned. (includes workflow functionalities in actions)

Internal process application tool
Use-case achievable
During the document verification process, we need to automate the "Document submitted" field in the Contact page, based on a rule that a Webform is filled. 
Business process steps that can be included in Blueprint. 
Collateral Assessment| Documentation Check| Document first release| Legal Verification | Release of loan | Loan closure/rejection (based on approval/denial)

Comparison 3 - Zoho CRM's CommandCenter
Comparison 4 - Zoho's CommandCenter
Feature
Allows the entire business process from your CRM to be created end-to-end, within a single space across modules

Cross-module online journey orchestration tool in Zoho CRM
Builds an online replica of your business process with the various entries of the records and signals across all Zoho services in ONE space
Cross-Zoho online replica of a business process
Use Case achievable
All the steps under Comparison 2. Additionally, we will be able to map the following steps of our business process in CRM. 
Pre-approval | Manual approval | Document verification | Loan rejected | Address verified | Loan rejected (if address proof is not submitted) | Loan approved | Funds processing initiated | Loan sanctioned | Loan closed | Loan settled | Overdue (in case of payment failure) | Overdue proceedings in due | Overdue proceedings settled (After legal proceedings are initiated)
All the steps under Comparison 3. Additionally, it will be able to include the following signals as triggers

- Filling of a customized survey used during home inspection process

- Booking of slots using Zoho Meeting to schedule a call with the realtor to understand requirements

- During the loan process, closing of customers' tickets created on Zoho Desk is used as a trigger to fully end their purchase

What's new with Zoho's CommandCenter 
- Advanced reporting for CommandCenter allows for tracking and measuring customer journeys, noting and rectifying pain points as the journey progresses.The new Pivot Charts in reports is noteworthy. 
- Unifies data across multiple apps, but also for multiple orgs across each application. 
- Custom signals or API triggers to flexibly trigger a transition based on any event from other Zoho services. 

Note - We've enabled CommandCenter early-access   to our EA community. Do try it out, let us know what you think as comments to this post. We request that you post any issues you face, feedback and suggestions for improvements, and what you like about it. Our CommandCenter team is all ears and will love to join in on the discussion. 

Access it at commandcenter.zoho.com

Pricing details - CommandCenter will be included in Zoho One when it is ready for public launch. It will be charged based on a Fair Usage Policy, where the base free limits will vary based on the number of users purchased. Post this, they will be charged for additional usage. We'll let you know the exact limits and pricing details closer to the public launch date

Pricing
Free edition
Enterprise Edition (post free usage)
Transitions
300/day
$0.0002/transition
Actions
250/day
$0.0003/action
Journeys
3
$5/journey/month (bonus of 1 free user)
Users
3
$2/additional user/month