Features
The web messenger and the public page: where the customer talks to the agent
One line of code on your site, or a link for your bio. Same agent, same knowledge, same tone.
The problem
A form that demands a name, an email and a phone number before the first word kills half the questions right there.
- 01
Installed in one line
The messenger snippet before the closing body tag, or the WordPress plugin, or the React, Vue, Nuxt, Laravel, Flutter and React Native packages. A signed-in user is introduced with your server's signature, not a claim.
- 02
Appearance and suggested questions
Colour, picture, button position, greeting, and up to four suggested questions; or leave them empty and the agent shows questions built from its own knowledge. Changes show in the preview as you make them.
Messenger settings with a live preview. - 03
The identity form, when it should
Never, after a few answers, before the first answer, or when the agent needs it. Always a small form inside the conversation, never a sentence. Name, phone and email, your choice.
- 04
Cards instead of text
Product, link, document, image, order, form, and a suggested next question. The agent decides when to send a card. Customers can send files and rate answers, if you turn that on.
- 05
A public page, nothing to install
Every agent has a standalone link anyone can open: for a bio, for a message, for where you have no site. Conversations land in the same inbox.
The public page: the agent's name and role, suggested questions, and the conversation.
Typical chatbot
A contact form with three required fields and "we will get back to you".
goya24
An answer right now, and details only when needed, with a form.
The rest of the product
Your first agent is ten minutes away
Free while you evaluate. Bring your own model keys if you'd rather.