Kiosk Studio新着
Every team has procedures that only work when somebody remembers each step: qualifying a lead, logging a visit, closing a ticket. Kiosk Studio turns that procedure into a guided assistant that appears as a button on the record page, with the label you choose. Whoever clicks it is led through screens that display and collect fields, actions that write values and create tasks, calls, meetings, notes, notifications or tickets, and branches that change the path based on a condition. Everything is built in Settings, Kiosk Studio, with no code, and it only runs when someone presses the button, never in the background. Writes go through the same validations, processes and permissions as a normal edit, so the assistant is not a shortcut around the rules: it is the easiest way to follow them.
- Custom button in the record's action bar, with its own label, for every active assistant of the object
- Three step types: Screen (collects fields), Action (set field, create task, call, meeting, note, notification or ticket) and Branch (condition true or false)
- A branch goes to the next step, ends, or jumps to another step, with targets validated on save
- Fields prefilled with the record's current values and required flags that block moving forward
- Starts inactive; activating shows the button immediately and deactivating hides it immediately
Sellioでは無料。お支払いはインフラ利用分だけ
Kiosk Studio is part of the free SellioCRM: build as many assistants as you need, in as many objects as you like, as long as your account's infrastructure usage always stays under US$ 20 a month.
Procedures that actually get followed
Instead of a document nobody opens, the step by step lives on the record, on the button the person was going to click anyway.
Faster onboarding
Someone who starts today qualifies a lead the same way the veteran does, because the assistant asks exactly what the team decided to ask.
Complete data at the source
Required fields per screen and the object's validations make sure the record leaves the assistant with what the next stage needs.
One action, many effects
One click writes fields, creates the follow-up task, logs the note and alerts the manager, without opening four screens.
No code and no risk
Everything is configuration stored as data, validated on save, executed with the clicking user's permissions and switchable off at once.
Reuses the automation vocabulary: actions and conditions are the same ones flows use, so nobody relearns anything; the difference is that here a person drives and there the system runs on its own
{{field}} placeholders in action texts insert the record's value into the created task, note or notification
Structural validation before saving: unique identifiers, existing jump targets and at least one interactive step, so you never publish an assistant that gets stuck
Respects the object's validations, process (blueprint) and permissions on every screen: an empty required field blocks the next step
Screens that ask for what is missing
A Screen shows up to thirty fields of the object, prefilled with what the record already has, and marks the required ones. Moving forward writes the values to the record under the same rules as a regular form. You can add a guidance message to each screen so the procedure is explained inside the step itself.
Actions that do the real work
An Action step runs a list of up to ten composite actions: set a field, create a task, call, meeting or note, notify someone or open a ticket. Use {{field}} in the text to pull the customer name, amount or date straight from the record. When the assistant ends, the actions are applied and visible on the timeline.
Branches that change the path
A Branch evaluates a field with an operator and a value and decides where to go when the condition is true and when it is false: next step, end, or jump to a specific step. The same button then serves the new customer and the returning one, the simple ticket and the critical one, without two assistants.
Built in minutes, governed by admins
In Settings, Kiosk Studio, you name the assistant, write the button label, pick the object and add steps with the Screen, Action and Branch buttons, ordering them with arrows. Who sees the menu is controlled by the permission matrix (Kiosk resource). Activating and deactivating is immediate, and deleting asks for confirmation.
- 1
Open Settings, Kiosk Studio and click New kiosk.
- 2
Fill in the name, the button label and the object the assistant applies to.
- 3
Add steps with Screen, Action and Branch, choosing fields, actions and conditions; order them with the arrows.
- 4
Save: the system validates identifiers, jump targets and that at least one interactive step exists.
- 5
Click Activate. The button appears in the action bar of that object's records, ready to use.
リードの見極め
A Qualify button: one screen asks for budget, timeline and decision maker; a branch sends leads above the minimum amount to the scheduling screen and the rest to an action that creates the nurturing task.
Sales visit log
A Log visit button: a screen with outcome and next steps, an action that creates the note with {{name}} and the follow-up meeting, and a notification to the manager when the risk field is set.
Ticket closure
A Close button: a screen with root cause and satisfaction, a branch that opens a follow-up ticket when satisfaction is low, and an action that writes the final status.
Pre-sales checklist
A Prepare proposal button: screens in sequence with the fields the proposal requires, and the assistant refuses to move on while any required field is empty.
Does the assistant run on its own in the background?
No. A kiosk is interactive: it only runs when someone clicks the button on the record. For rules that run by themselves, use automations, which share the same vocabulary of actions and conditions.
Can it bypass a validation or permission?
No. Each screen writes under the same rules as a normal edit: the object's validations, process and permissions. An empty required field blocks moving forward.
How many steps and actions fit?
Up to forty steps per assistant, up to thirty fields per screen and up to ten actions per action step.
Who sees the button?
Anyone who opens a record of the chosen object while the kiosk is active. Visibility of the Kiosk Studio menu in Settings is controlled by the permission matrix.
What happens if I deactivate it?
The button disappears from records immediately. The assistant stays saved and comes back when you activate it again.