Skip to content
ChatFrom
Sign inStart free →
Start free →

Crisp

Updated

Your chatbot answering in the Crisp chatbox your website already has, with the same knowledge, tools and workflows, and stepping aside for your team.

Before you start, build your chatbot and make it Live under Deploy: it answers only while it is Live. What works in every app, such as signed-in users and what your users can send, is on the Channels page.

If your website already uses Crisp's chatbox, your chatbot can answer in it. Visitors keep the chatbox they know, and your team keeps working in Crisp's inbox. The chatbot steps aside for people: once someone on your team writes in a conversation, or the chatbot hands it off, it stays quiet in that conversation for a day.

In Crisp, then in ChatFrom

  1. In Crisp, open Settings, Workspace Settings, Advanced configuration, and press Generate Token under API Token. Crisp shows the API identifier and the API key once. Only the workspace owner can do this.
  2. In ChatFrom, under Channels, paste both with your Website ID, which Crisp shows under Settings, Workspace Settings, Setup & Integrations, and press Connect Crisp.
  3. ChatFrom shows a web hook address. Back in Crisp, under Settings, Website Settings, Advanced Configuration, Web Hooks, add it with the events message:send, message:received and message:updated. The last is how Crisp reports a choice in one of the chatbot's questions.
  4. Write in your chatbox to try it.

Keep the web hook address to yourself: it carries the secret that shows an event came from your Crisp. For signed-in users there is no link page to build. Your site hands the chatbox the same token it gives the widget, and the chatbot passes it to your tool servers:

On your site, once the user is signed inJavaScript
$crisp.push(["set", "session:data", [[["chatfrom_user_token", "<your token for this user>"]]]]);

The token is your site's own, as with the widget: your tool server checks it, and ChatFrom only carries it. Crisp keeps it with the conversation, where your team can see it in the inbox, so give the chatbox a token that expires the way you would want a signed-in session to.

What it leaves alone

The chatbot answers what visitors type in the chatbox, and picks they make on its own questions. With Visitors can attach files on under Deploy, it also reads a file or a photo sent in the chatbox; with it off, files are left to your team. Replies that come in by email, other apps' pickers and every conversation your team has written in are left to your team too. While your chatbot is a draft, or has used its monthly allowance, it says nothing in the chatbox rather than explaining itself to your customers. A Crisp API token allows 10,000 requests a day, and an answer takes about four, so a very busy chatbox can reach that ceiling; Crisp then refuses until the next day and the team answers as usual.

To stop, press Disconnect in ChatFrom and remove the web hook in Crisp.