Jump Block
What is a jump block?
The jump block allows you to navigate within the same flow or switch between different flows seamlessly. For example, after a user places an order, you might ask if they want to place another one. If they agree, you can loop back to the order block. If they decide to cancel, the Jump Block can redirect them to a separate flow dedicated to handling cancellations and refunds. This versatility enables the jump block to manage various user interactions efficiently.
This block allows navigation between:
- Different blocks within the same conversation flow.
- Various flows within the same department.
- Flows across different departments.
The jump bock is particularly valuable for conversations that require cross-functional activities. It’s essential to map both input and output variables in the jump block to establish a seamless connection between the flows.
Why use a jump block?
- Seamless navigation: Allows smooth transitions within the same flow or across different flows.
- Dynamic interaction: Adapts the conversation in real-time based on user responses.
- Enhanced user experience: Ensures a seamless and uninterrupted conversation flow.
- Versatile usage: Facilitates the management of various user paths, improving the overall chatbot functionality.
Steps to create a jump block
To add the Jump block to the flow:
1. Click the add block icon (+)
2. Choose Jump under the Action section.
3. Add a unique name for the block in the Block name field. If you input the name of a block that already exists, the following error message will appear.
4. Choose where you want to jump to, either Current flow or Other flow.
- If you choose Current flow, you will next have to choose the block in the current flow that has to be jumped to.
- Jumping within the current flow is possible only at the end of the flow to avoid missing out on the blocks which are under it.
- If you choose Other flow, you will next have to choose the other flow and later the block that has to be jumped to in the chosen flow.
5. Set up the Input variable mapping and Save.
6. Map Output variable mapping and Save.
- This is used when you want to send data collected from your current flow to another flow during jumping.
7. The variables required by the other flow will be listed here. You need to map the variables of the current flow to the new flow.
- If there are no variables to map in the jumped flow, an error message will be displayed.
Jump block validations
Field | Mandatory field | Character limit | Additional details |
Block name | Yes | 100 | <, >, ", ' , are not allowed |
Output variable name | Yes | 250 | Special characters are allowed except for underscore. |
Example:
Imagine you are in a flow called Reception and want to jump to a block named View Rooms in another flow called Room Booking. Before the View Rooms block, the Room Booking flow contains two blocks: Name and Address. These blocks expect certain variables.
When you jump from Reception to Room Booking, you must pass the required variables that Name and Address depend on. Sharing these values between flows is known as Input Variable Mapping.For example, after executing Room Booking flow, GC will return automatically to your parent flow, Reception, to finish the remaining blocks present. You are expecting the flow to bring data like Room details from Room Booking to Reception. To get this variable, you have to set Output Variable Mapping in your 'Jump to View Rooms' block. After completing Input Variable Mapping by following the above-mentioned steps from 1 to 4, enter the following details:
Configure the Jump Block
After adding a Jump Block in the Reception flow, fill in the block panel:
- Block name: Provide a descriptive name. Example: Jump to View Rooms
- Jump-to Flow: Select the flow you want to connect to. Example: Room Booking
- Jump-to Block: Select the specific block within that flow. Example: View Rooms
- Input Variable Mapping: Map the variables from the Reception flow to the variables expected by the Room Booking flow.
Once mapped, the Room Booking flow will receive all the data it needs to continue smoothly.
After the Room Booking flow finishes, GC returns to the parent flow (Reception) to complete the remaining blocks. If you want to bring back data from Room Booking, such as selected room details, you need to configure Output Variable Mapping.
This ensures that any values generated in Room Booking are returned to the Reception flow.
Configure Output Variable Mapping
After completing the input mappings, follow these steps:
- Choose the variable you want to fetch from the Room Booking flow.
- Map it to a variable in the Reception flow where you want to store the returned value.
- Use the Add Mapping option if you need multiple output values.
- Write a suitable message in the Error Message field, or continue with the default text.
- Click Save.
Language compatibility and flow visibility
When configuring a jump to another flow, the list of available flows under Other flow is not determined only by channel and publish status. It also depends on language compatibility and publish state of languages.
The following rules apply:
1. Language compatibility is based on the source flow
- The jump is validated from the flow where the Jump Block is added.
- The target flow must support the required language context of the source flow.
2. Single-language to multi-language flows
- If the source flow has only the default language (for example, English), you can jump to a multi-language flow.
- This works as long as the target flow supports the default language.
3. Multi-language to single-language flows
- If the source flow has multiple languages, you cannot jump to a single-language flow.
- This is because the additional languages in the source flow do not have corresponding mappings in the target flow.
4. Multi-language to multi-language flows
- Both flows must have compatible language configurations.
- All required languages in the target flow must be:
- Enabled
- Fully published
- Not in draft or outdated state
5. Draft or outdated language versions are not supported
- Flows with draft or outdated language versions will not appear under the Other flow selection.
- Even if the flow itself is published, any incomplete language configuration can prevent it from being listed.
6. Why this validation exists
- When a jump happens, the system maintains the user’s language context.
- Every active language in the source flow must have a valid destination in the target flow.
- If this mapping cannot be ensured, the flow is excluded from selection.
Steps to edit an jump block
You can edit an jump block whenever required, even after the flow is published or in the drafts section, by following these steps:
1. Open the flow and click Edit.
2. Click the Jump Block, which you may have named differently.
3. Choose Edit from the displayed options.
4. Make the required changes to the block and click Save.
5. Click Save.
6. Publish the flow.
To be noted while editing an jump block:
- If you edit a block while an end user is engaged in a live session with the bot, the previous version of the flow will be rendered until they restart the conversation.
- After making changes, you will need to publish the flow for those changes to be reflected in an end user's session.
- If a change is made to an input variable, it will be updated automatically across all flows where the variable is used.
Steps to copy the jump block
The copy block option can be used when you need to reuse a block that you previously created; you can copy that block and add it to your flow as it is or edit it according to the requirement.
1. Click the Jump Block you wish to copy.
2. Choose the Copy option. The block will be pasted on the clipboard.
3. When you require to paste that block, click the Add block icon (+). The pasted block would appear on the block listing section and be stated as From Clipboard.
4. Make any required edits, then click Paste.
To be noted while copying an jump block:
- The copied jump block can be pasted multiple times. If you no longer need to paste it, you can clear the clipboard by clicking the close icon corresponding to the clipboard option.
- When copying an existing jump block, all of its content, including any variables, will be copied as is. You can edit it as needed before adding it to the flow. Since the names of each block must be unique, the word '_copy' will be added to the copied blocks automatically; this can be changed if required.
- If you have copied a block and it is in the clipboard, deleting the copied block later will also remove it from the clipboard.
Steps to delete an jump block
1. Open the flow and click Edit.
2. Click the Jump block, which you may have named differently.
3. Select Delete from the displayed options.
4. Click Yes, Delete it to confirm.
You can use the undo option to restore a deleted block as your following action, but not otherwise.
5. Click Save.
6. Publish the flow.
6. Publish the flow.
To be noted while copying an jump block:
- If you delete an jump block while an end user is engaged in a live session with the bot, the previous version of the flow will be rendered until they restart the conversation.
- After making changes, you will need to publish the flow for those changes to be reflected in an end user's session.
- If the deleted block has dependencies, such as those given below, errors will be displayed.
Path below the block:
If the block was used to jump to a different flow:
Use cases
Jumping from one flow to another
A travel agency provides different online bookings for flights, hotels, cabs, and more.
If the agency creates different flows for each type of booking in the respective departments, then the jump blocks can help users navigate between the types of bookings. By mapping the input and output variables, information between the bookings can be easily transferred, preventing the customer from repeating basic details for each booking.
Jumping to another block within the flow
A mobile phone manufacturer allows its customers to submit faulty devices and claim a refund or exchange.
Using the GC flow, the customers can select the device and choose "Faulty Device" from the list of options. Using the jump block, they will be directly navigated to select the type of problem they are facing. In the subsequent steps the customer is asked to enter the IMEI number and the date of purchase from where they will be prompted to choose whether the device should be returned (with amount refunded) or exchanged.
So, instead of showing all the intermediate blocks, based on the customer's input, they can be directly shown the appropriate block.
Supported channels
The jump block is supported in the following channels:
If you exceed the limit of 500 blocks in a flow, you have a couple of options to continue building the flow:
- You can create a new flow and use a jump block to connect both flows.
- You can also remove any unnecessary blocks or paths to free up space within the existing flow.
Access your files securely from anywhere
Zoho CRM Training Programs
Learn how to use the best tools for sales force automation and better customer engagement from Zoho's implementation specialists.
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.
- Zoho Workerly Home
- Forums
- Connect With Us:
- Zoho Recruit Home
- Forums
- Connect With Us:
Centralize Knowledge. Transform Learning.
All-in-one knowledge management and training platform for your employees and customers.
New to Zoho Writer?
Create. Review. Publish.
New to Zoho CRM Plus?
Deliver unforgettable customer experiences
New to Zoho CRM Plus?
Deliver unforgettable customer experiences
New to Zoho Marketing Plus?
Everything you need to run your marketing
New to Zoho Marketing Plus?
Everything you need to run your marketing
You are currently viewing the help pages of Qntrl’s earlier version. Click here to view our latest version—Qntrl 3.0's help articles.
New to Zoho Survey?
Zoho Sheet Resources
Zoho Forms Resources
New to Zoho Sign?
Zoho Sign Resources
Sign, Paperless!
New to Zoho TeamInbox?
Zoho TeamInbox Resources
New to Zoho ZeptoMail?
Design. Discuss. Deliver.
New to Zoho Workerly?
New to Zoho Recruit?
New to Zoho CRM?
New to Zoho Projects?
New to Zoho Sprints?
New to Zoho Assist?
New to Bigin?
Related Articles
Operation Block
What is an operation block? This block allows us to perform arithmetic operations and display the result during the chat session. Operation block can also be used to calculate the values retrieved from the block variable, local variable, and global ...Components of the GC Flow Builder
The GC flow builder comprises three components: Blocks Paths Variables Blocks Blocks are the fundamental units of the flow builder. A text message that you want to display, a set of options that you want the customer to choose, the step where you ...Introduction to Webhook Block in GC
We know it’s frustrating to jump between tools just to get simple tasks done. You might find yourself copying data from one app to another, waiting for updates, or refreshing dashboards manually. It’s not just time-consuming, it’s exhausting. That’s ...Currency Block
What is a Currency Block? The currency block enables interaction where users can input and validate the amounts in specific currency formats. For example, an organization's chatbot can be set up to receive donations from supporters. Users can specify ...Number Block
What is a Number Block? A number block allows you to ask questions and receive answers in the form of numbers. For example, if a customer has questions about their order and needs to provide an order ID, a number block can be incorporated into the ...
New to Zoho LandingPage?
Zoho LandingPage Resources