Disclosure: I work at Skyfall Labs, an official Zoho Partner, so I have a commercial interest. The facts below are from Zoho's own help pages, linked at the end; advice is labelled as advice. Originally published on skyfallhq.net.
CommandCenter is Zoho's journey tool, and it is easy to over-build with it when a Blueprint or workflow would do. This post sets out what Zoho's help pages say about it.
What CommandCenter is
Zoho describes CommandCenter as a journey management suite in Zoho CRM with three parts: Path Finder, which helps discover the journeys prospects and customers take; Journey Builder, which builds contextual journeys; and Analytics, which exposes the journeys taken in your organization. Access requires the CommandCenter permission under Automation.
Zoho's page lists Professional, Enterprise, Ultimate, CRMPlus, ServicePlus and Zoho One bundles, and points to its release notes for current feature availability and limits. Check feature availability for your edition.
Setting up a journey, per Zoho
- Go to Setup, Experience Center, CommandCenter, Journey Builder, click Create Journey, enter a name and description, and click Proceed.
- The builder starts with a Start stage. Add stages with Create Stage; goals are optional and are set by clicking the Start stage.
- Connect stages with transitions that hold signals: record actions, user actions such as email, call or web form, integration signals from Zoho apps, and custom signals.
- Open a stage's Actions tab and create an action group, which can be instant, scheduled or recurring. Zoho lists action types including field updates, functions, webhooks, tasks and email notifications.
- Zoho says identifiers are mandatory to publish a journey; Manage Identifier sets them for all transitions at once.
Caveats Zoho documents
- Zoho says you cannot uncheck the run-for-specific-records option once selected; to change it, delete the action group and reconfigure.
- Ending a journey at an end stage does not prevent a record entering another journey it qualifies for.
- Zoho's help page gives conflicting figures for identifiers per transition (ten in one note, five in another), so check the live page.
- Zoho's pages reviewed do not state limits on the number of journeys, stages or records, or what editing a published journey does.
- If Journey Builder, workflows and Cadences are configured for the same touchpoint, Zoho warns customers may receive the same email several times.
CommandCenter vs Blueprint, per Zoho
Zoho's comparison page says both are built on a finite state machine with states, transitions and actions. It describes Blueprint as a business process tool to promote compliance, for internal teams, with states from picklist values and transitions that depend on completing required actions. Journey Builder it describes as a tool to optimize the customer journey across touchpoints, for customers, with free-form states and transitions driven by signals or events. Blueprint is built for a single module, while Journey Builder can span modules. For simple email, task and call follow-up, Zoho suggests Cadence Studio, saying Journey Builder can do this but it may be laborious.
Deciding what you need (practical advice)
This section is advice from experience, not vendor documentation.
- If you need to force a team through required steps on a record, start with a Blueprint.
- If you need one condition to trigger one action, a workflow rule is usually enough.
- Consider CommandCenter only when a process has many stages, reacts to events across channels and modules, and you can draw it as a flowchart.
- Draw the journey on paper first and name the signal for every transition.
- Never configure the same action in two automation tools for the same touchpoint.
Top comments (0)