Checkpoint is an important feature that helps you save all user's responses and manage them easily. Checkpoint is suitable for transactional data such as deals, bookings or orders. You can set up more than one Checkpoint in Flow Editor. Read more about Flow Editor.
Note: To enable Checkpoint data, you need to setup at least one Checkpoint in your conversation flow.
Setup a Checkpoint
When creating a chatbot with BotStar, sometimes you'll need to save the information of customers. It can be deals, bookings or orders. We'll use Save to Checkpoint action to save the customers' information in "Checkpoints".
For example: you need to design a chatbot that serves the coffee ordering process. Except blocks introducing the products, your bot also contains blocks that collect information like: name of chosen products, instructions, quantity, name of receiver, their email, phone number and date of delivery. The responses of users for these blocks are captured on a Checkpoint by the Save to Checkpoint action.
Example conversation flow of a bot that collects coffee orders. Except blocks introducing the products, the flow also contains blocks that collect information like: name of chosen products, instructions, quantity, name of the receiver, his/her email, phone number and date of delivery
To design a conversation flow using Checkpoint, let's enable the Save Response To Variable option on the block(s) that receive users' response and set a name for variable. Next, drag and drop Save to Checkpoint action from Library Panel into Flow Editor. Then, customize Save to Checkpoint action and set transaction name.
Drag-and-drop a Regular Block into Flow Editor
Customize "Save to Checkpoint" action
Done! When the conversation between your chatbot and users passes by Save to Checkpoint action, the system will capture all user's responses and save them in Checkpoints.
Review and manage Checkpoints
Checkpoints to open the Checkpoints management page.
Checkpoints Management Page
Click on a specific Checkpoint to view its detail information. As you can see from the above example, a Checkpoint captures all of user's responses about the Coffee Deal, including: name of chosen product, instructions, quantity, name of receiver, their email, phone number, date of delivery. It helps bot operators to check an order or a booking easily and effectively.
Review a Checkpoint
In case you want to delete a Checkpoint from the list of record, click "Trash" button as in the illustration below:
Delete a Checkpoint
Checkpoint can be filtered based on: Checkpoint Name, Customer, Date and Environment. You can choose a single filter condition or combine all of filter conditions.
Filter by name of Checkpoint
Checkpoints can be filtered by name. It's really convenient when there are more than one Checkpoint in bot flow for different deals/orders.
Filter Checkpoint by Checkpoint Name
Filter by name of customers
It's possible to use "CustomerID" or "Name" when searching for checkpoints of a specific user.
Filter Checkpoint by Username or ID
Filter by Date
Checkpoints can be filtered by "Date" with options as in the below illustration:
Filter Checkpoint by date
Filter by Environment
There are two types of "Environment" when filtering Checkpoints:
Test: will show all Checkpoints from your trials in
Live: will show all Checkpoints that you receive from real users who interact with your chatbot via Messenger or Website
Filter Checkpoint by Environment