← Back

CliqTrix’20 App Submission

It’s time to submit your app and we have put together a checklist of guidelines for both Cliq App and SalesIQ Zobot!

The submissions will close on September 14, at 12 midnight.

Zobot Publish Checklist

Once you're done building your Zobot, it's time to deploy it on your website. We've put together this checklist of important points that you should keep in mind before publishing your Zobot. You can refer to the help tips added to each point on the checklist.

Zobot Requirements

  • You need to be aware that before you start building your Zobot, you will need a website. You can build one either using Zoho Sites or Weebly.
  • Then you have to embed the Zoho SalesIQ Live chat widget code.
  • Build the Zobot and configure all the handlers.
  • Publish the Zobot on your website.

Flowcharts

Design a flowchart before you start building your Zobot. This will give you a clear picture of what you want to build and for what purpose. The flowchart can help you visualize the functioning of each feature that you have in mind. Here's a sample.


Performance

Ensure that your Zobot is tested for stability and bugs before submission. Run multiple quality checks and ensure that the Zobot functionality is intact, and it behaves the same way as you intend for various user scenarios.

Connections

Make sure you've established connections with all the required services and check if all of your connections are working. To establish a connection,

  • Go to Manage Connections inside the script builder and create a connection.
  • After you do, ensure the status is Connected.

Design and UX

1. User Experience

A primary point you should check off your list, before you deploy your Zobot on the website. You can ensure a quality experience to users by keeping the below suggestions in mind.

Offer relevant suggestions

Response suggestions come in handy when users are struggling to discover what to do on your website. You can create suggestions based on common questions that come from the visitor's side.

For example: A Zobot can have an About the website or Need Help option configured in the message handler. This menu can contain details about each product/service on the website and how to get started using it!

Zobot Configuration

Configure information like the name, description, the website on which you want to deploy your bot, bot working hours, trigger visitor criteria and handoff when you start setting up the Zobot. To handle data storage in external services use Connections.

Populate finer results

Do not overwhelm the visitor with myriad options. Configure your component to pull up finer search results or simply provide an option to narrow down the search results!

For example: if an existing visitor comes back to visit your website and book a service for his/her car, you can display suggestions based on services he/she has availed previously.

Avoid complex visitor input

If your Zobot requires the visitor to manually enter data from their end, handle it by providing response suggestions

For example: In case the visitor wants to buy a car on an automotive website, the Zobot should not ask the user to enter the name of the car that he/she wants to buy. Instead, it can pull out the list of cars that are currently available in the market and show them as suggestions for the user to choose from.

Zobot Cards

Use Zobot input and display cards whenever and wherever necessary to display information aesthetically.

2. Handling Errors

Handle all negative use cases with a relative error response. Predict where errors are likely to occur and provide an error message inside the Failure Handler to handle unpredictable scenarios. Inside the handler, you can configure responses for when your operators are unavailable, chat gets forwarded to a department where operators are busy or when there is an incoming chat outside your standard business hours. For errors on the Dialogflow, Zia skills and Watson platforms, you can configure Action Failure Responses. You can see how to handle common errors in Deluge here.

3. Zobot Content

Content used throughout your Zobot should communicate the value it adds to the end users. Your Zobot scripts will go through a stringent content review process, where we will check for authenticity and writing style.

4. Zobot Name, Description and Logo

The Zobot's name, description and logo should all convey the purpose of it.

Quality Analysis

Check your Zobot's working by deploying it on 2 or 3 websites and try using all the Zobot's functionalities and cards.

Data Privacy

Data Use and Sharing: Your Zobot should not store/log user information without an actual requirement. In cases where you do need a requirement, let the user know in prior on what the requirement is.