Skip to content
klercDocs
Get started

Try “workflows”, “templates”, “SOQL” or “create a record”.

klercDocs
GuidesAPI reference
Sign inBack to klerc.co

Chatbots

Build conversations on a canvas, publish them as a web widget, and see where people drop off.

A klerc chatbot answers routine questions and collects details in a structured way, then hands the conversation to a person or an AI agent when it should. Bot conversations land in the inbox like any other channel.

The canvas#

Open Chatbot → New Chatbot and design the conversation as a graph of nodes:

NodeWhat it does
StartWhere every conversation begins
SaysSends text or media
AsksAsks a typed question and stores the answer in a variable, such as {{policy_number}}
BranchesChooses a path based on an answer
Hand offPasses the conversation to a person or an AI agent

Ask-nodes validate what people type, so a phone number has to look like a phone number before the bot moves on.

Example: claim status#

The demo brokerage's Claim status bot does this:

  1. Welcome the visitor to the claims desk and ask for their policy number.
  2. Ask for the claim or intimation number.
  3. Send the claim's status.
  4. Ask for a rating. If it's two or lower, hand off to a claims executive.

A second bot, Get a quote, collects name, mobile, email and the product someone is interested in, then creates a lead.

Publishing#

Publish a bot as a web widget. Each bot gets a shareable link, and the widget can be embedded on your site behind origin allow-lists. The overview shows Live once it's running and Ready to run when every step is filled in. Unpublish takes it down.

Analytics#

Each bot's overview shows, for the period you choose:

  • Chats, and the share that finished the flow;
  • how many were handed to a person and how many left early;
  • the typical length of a conversation;
  • How far people get — chats reaching each step in order, so a big fall shows you where people leave;
  • What people answer — a breakdown of choices, such as Travel 50%, Motor 38%, Health 13%.

Typed answers are counted rather than listed, so personal details stay out of the dashboard. The full answers are on each chat.

Through the API#

Chatbots live under /docs/api/chatbots:

  • list, read, create, update and delete bots;
  • POST /chatbots/{id}/publish and POST /chatbots/{id}/unpublish;
  • GET /chatbots/{id}/sessions, paged with limit and cursor.

Reading needs chatbot:view; changes need chatbot:manage.