You can use them as reference examples: to see what is possible before you build, to adapt a configuration to your own process, or to find a starting point close to your industry.
Each session post has a comments section. You can ask questions about a configuration there, or share a kiosk you have built. Some may be featured in later sessions.
If you run into an error or need help with your own kiosk, submit a ticket and our support team will assist you.
If you are new to Kiosk Studio, Sessions #1 and #8 are the smallest builds and can be implemented quickly. Sessions #6 and #7 cover longer, multi-step processes. Sessions #9 and #10 involve Zia agents and assume you are already comfortable building kiosks.
|
Session #
|
Link |
Description
|
|
1
|
A kiosk on the deal record that retrieves existing customers in the same industry as the prospect, so a sales rep can answer the question without leaving the record.
|
|
|
2
|
A kiosk that combines the call script, the CRM data a rep needs during the call, and the follow-up actions that come after it. |
|
|
3
|
A kiosk placed in the CRM portal so that customers — in this example, patients booking a hospital appointment — can complete a process themselves.
|
|
|
4
|
A cross-selling kiosk that presents the script and customer data together, filters eligible products automatically, and creates the application record.
|
|
|
5
|
A kiosk on the home page that lists applications awaiting review, consolidates the details needed to assess each one, and records the decision.
|
|
|
6
|
A longer service-request flow: selecting a dealer and a piece of equipment, checking warranty status through an external system, branching on the result, and creating the resulting records.
|
|
|
7
|
A kiosk that converts records from a custom module into other entities, with its own approval step, field mapping, and notifications. |
|
|
8
|
A kiosk launched from a button in the list view that displays a record's subform entries — such as invoiced items — and allows entries to be added or removed without opening the record.
|
|
|
9
|
A kiosk launched from a Blueprint transition, where a Zia agent reads an unstructured email, verifies the claim through external systems, and the kiosk decides which screens the user sees based on the result.
|
|
|
10
|
A kiosk on the account record that uses one agent to assess renewal risk from existing CRM data and a second to log the reviewer's final decision.
|