Elements of a kiosk
We've started publishing a series of posts on Kiosk Studio. You can check out the second one (with a step by step demo) here!You can build kiosks to cover multiple use cases, but in the end, they are all made up of a few basic elements that are added, configured, and connected in multiple ways.
These basic elements are:
- Screen
- Decision
- Action
Let's look at them one by one.
Screen
A screen presents the user with display text, fields, data from the CRM, data collected from previous screens, and buttons to pick the next step. Each button represents a branch in the kiosk's flow. The data entered in the fields of a screen and the data pulled in from the CRM will be available for use in subsequent screens. This is how a screen will look to CRM users:
The elements available to build a screen are:
- Display elements
- Text: As the name suggests, this is used to display text to the user. You can use this to instruct the user, warn them, give them feedback, make them aware of the importance of some fields, let them know whom to contact, and so on.
- GetRecords: The GetRecords component lets you pull in a record or multiple records from the CRM and display them to the user. You can pick a parent module, or select a parent record and pick its child module. Then, you can set the criteria for the records to be fetched, decide how these records should be sorted, and so on.You can learn more about GetRecords in the Data in kiosks section of this document.
- Screen Field: The screen field component lets you display data collected in previous screens' fields.
- Zia Insights: The Zia Insights component lets you display insights generated by Zia for a particular record. The following components are supported in Kiosks:
- Fields: These are used to collect different kinds of data from users, or to display previously collected data or data from the CRM. These fields are not CRM fields. This gives you greater flexibility when it comes to collecting and presenting data in the kiosk. The field types and their attributes are shown below:Field typeMerge from moduleMark as mandatoryShow tool tipRead onlyOthersSingle lineYesYesYesIf Merge from module is enabledMulti-lineYesYesYesIf Merge from module is enabledPhoneYesYesYesIf Merge from module is enabledNumberYesYesYesIf Merge from module is enabledMaximum digits allowedCurrencyYesYesYesIf Merge from module is enabledMaximum digits allowed, Number of decimal places, Rounding optionCheckboxYesYesYesYesEnable by DefaultEmailYesYesYesIf Merge from module is enabledDateYesYesYesIf Merge from module is enabledDate/ TimeYesYesYesIf Merge from module is enabledPicklistNoYesYesNoPicklist type (local or Global set)Multi-SelectNoYesYesNoUserNoYesYesNoFile UploadNoNoYesNoUpload multiple files
- Buttons: A screen contains buttons. You can choose the button label and the button style. The buttons will be displayed from right to left on the screen. Each button will create a corresponding branch in a kiosk's flow.
Note
- You can add a maximum of 20 fields in a screen.
- You can add a maximum of four buttons per screen.
- The display elements and fields can be rearranged.
- The buttons can't be rearranged.
Decision
A decision component is used to create branches in the kiosk's flow based on existing CRM data or the data in the previous screen fields. It is a counterpart to the buttons on screens. Both dictate the branch of the flow that is to be executed but decision components do this automatically based on data. A criteria is specified to decide the branch that the flow should take. There will always be a default path in case the criteria for the other paths are not satisfied.
Action
Actions are crucial, as they link the data in the screens with the rest of the CRM. Actions added in a branch of the kiosk will be automatically executed if the user's actions lead down that branch. When you create an action, you can make use of the data gathered in the previous screens. For example, the details entered by the user in previous screens can be used as values for a function's arguments.
The different actions available include field update, assign owner, tagging records, notifications via email, adding activities, creating records, and executing webhooks or functions.
Data in kiosks
While screens can be used to gather data from the user, the power of kiosks comes from the ability to use this data and data from the CRM. You have the following options to pull in data:
Screen field
You can display the data gathered in previous screens using the Screen Field component. This can be used whenever you want to present this data to the user for reference.
Current Record
Kiosks can be accessed from multiple places. Two such places are record-specific:
- The record detail view page and
- The module list view page (for each record).
In these cases, the kiosk can use data from that specific record (called Current record). In case you access a kiosk from outside a record, the current record will be null.
GetRecords
The
GetRecords component is used to fetch one or more records from a CRM
module. It can be created and used
in screens, decisions, and actions. This component has the
following kinds of output:
- Single record output:
A single record will be displayed to the user. Its field values can be
used in subsequent screens, decision criteria, and actions.
- Multi-record output: Multiple records will be fetched based on the criteria you've chosen.
- With single selection:
Though multiple records are fetched, the user will be able to select
only one record. Its fields can be used everywhere that the single
record output's fields are used.
- With multiple selections:
These allow the selection of multiple records. The selected records can
be used in decision criteria or in email notification templates (In the
email template builder, under Table > GetRecords).
Merge fields
A
merge field is a reference to another field. At the time of accessing a kiosk, this will be replaced with the value for that referred field.
In kiosks, a merge field can point to:
In kiosks, a merge field can point to:
- GetRecords' fields (CRM record's fields)
- Previous screen's field
- Current record's fields
- A User module field (for data related to the user who's accessing a kiosk)
- Organization fields
They can be used in the following places:
- Within screens:
Enable Merge from module and press # to pick the field.This allows you
to do things like customize your instructions (within the text display
element on a screen), display CRM field data for reference, and so on.
- Email templates: When you're creating an email template, you can use merge fields to customize your notification.
To learn more about Kiosk Studio, see:
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:
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?
Zoho DataPrep Resources
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
Working with Kiosk Studio
We've started publishing a series of posts on Kiosk Studio. You can check out the second one (with a step by step demo) here! Kiosks are not only convenient for your CRM users, they are also easy to build using the no-code Kiosk Studio in Zoho CRM. ...Kiosk Studio - An overview
[Update | Kiosk Studio Session #2] We've started publishing a series of posts on Kiosk Studio. You can check out the second one (with a step by step demo) here! Kiosk Studio is a no-code customization tool in Zoho CRM. It allows admins to simplify ...FAQs: Kiosk Studio
How is Kiosk Studio different from Blueprint, Wizards, CommandCenter, and Cadences? The fundamental distinction lies in the Kiosk Studio's ability to construct tailored UI screens featuring custom inputs—fields not necessarily confined to your ...Customizing Record Detail Page Using Canvas
The canvas list view provides ways to customize the record display in the module list. You can add record images, use custom buttons to represent fields, use specific font style or size for the field labels, change the alignment of field types and ...Process management solutions working together — A perspective
Overview Process management solutions in Zoho CRM could be broadly categorized under two divisions — Business Process Management and Customer Experience Management. While BPM solves the need for streamlining internal processes, CEM addresses the ...
New to Zoho LandingPage?
Zoho LandingPage Resources