These are the most common practical questions about setting up and configuring a Zobot in Zoho SalesIQ.
From Settings, then Bot, then Zobot, give the bot a name, and choose a platform: Codeless Bot Builder, SalesIQ Scripts, Zia Skills, Webhooks, Watson Assistant, or Azure Bot Service. From there, write a description, choose the brand and department the bot should be associated with, decide where it should be active (website, mobile SDK, Facebook Messenger, Instagram, WhatsApp, Telegram, or LINE), and choose the languages it should converse in, from the roughly 30 currently supported.
Yes. You choose which website the bot should be deployed on directly while configuring it, so there's no need to deploy the same bot everywhere.
Yes, only one Zobot can be deployed under the same brand at a time.
Yes, set the Trigger Visitors criteria to activate specifically when a visitor clicks the chat widget, rather than firing automatically on page load or another condition.
Yes, this is configured in the Choose Bot Audience section, letting you set criteria so the bot only engages visitors matching your chosen conditions.
Yes, the Trigger Visitor section includes a "Performs custom action" option, letting the bot trigger a message based on a specific action the visitor takes on your site.
Yes, using input and display cards to collect information from and present content to visitors respectively.
Yes, any number of dates and time slots can be included.
Yes, and these can be provided dynamically using multiple options or options cards, rather than only fixed, pre-written suggestions.
Yes, via Webhooks, which lets an existing, fully built bot engine integrate directly with Zobot rather than needing to be rebuilt inside SalesIQ.
Yes, using Connections, which handle authentication and let your bot securely interact with external services during a conversation.
A Zobot is associated with a department at setup, and all departments belonging to the selected brand are listed for you to choose from. Departments themselves can be Public, visible to visitors, or Private, for internal back-office use, with public-department operators able to transfer chats into private departments when needed.