ACTIONS
The ACTIONS section lets you configure automation features for your chatbot. It contains these sub-sections:
Lead Capture — Collect visitor information through a contact form
Human Handover — Transfer conversations to your support team
Email Notifications — Get notified about new leads and conversations
Custom Actions — Let your agent look things up and take action in your other systems
Action Buttons — Show clickable call-to-action buttons in the chat at the right moment
Lead Capture

The Contact Form allows you to collect user information directly through the chatbot, making it ideal for lead generation. You can customize its behavior and appearance as follows:
Display Position: Choose when the form appears:
At Start: The form is shown immediately when the chatbot opens.
After First Response: The form is displayed after the chatbot sends its first message.
At End: The form appears after the conversation ends.
Form Heading: Add a custom heading to guide users, e.g., “We need your details to help you better.”
Form Fields: Select the information you want to collect: Name, Email, and Phone Number.
Success Messages:
With Name: Personalized message that includes the user’s name, e.g., ”Thank you for sharing your details with us. How can we help you, {user_name}?”
Without Name: Message displayed if the user did not provide their name, e.g., ”Thank you for sharing your details with us. How can we help you?”
Consent Message (Optional): Enable a consent message to inform users before they fill out the form.
This feature ensures you can seamlessly collect leads while maintaining a smooth chatbot experience.
The generated leads will be displayed in the Conversations section under the Leads tab.
Human Handover

Human Handover allows your chatbot to seamlessly transfer conversations to your support team when users need human assistance. Instead of leaving users frustrated, your chatbot can offer multiple ways to reach your team -- via Email, WhatsApp, Instagram, Telegram, or Facebook Messenger.
How It Works
When a user requests to speak with a human, or when your chatbot determines it cannot help further, the chatbot will:
Display a friendly transition message explaining that their request is being forwarded
Show channel buttons so the user can choose how to reach your team
For messaging channels (WhatsApp, Telegram, Instagram, Messenger): clicking the button opens the app directly with a conversation summary pre-filled (where supported)
For Email: clicking the button shows the contact form to collect the user's details, then sends an email to your support team
Supported Channels
Opens in-chat contact form, sends email to your team
N/A (form collects details)
Opens wa.me deep link in new tab
Yes -- conversation summary
Telegram
Opens t.me deep link in new tab
Yes -- conversation summary
Opens ig.me/m DM link in new tab
No (platform limitation)
Messenger
Opens m.me link in new tab
No (platform limitation)
Setting Up Human Handover
Navigate to ACTIONS → Human Handover
Toggle Human Support Request ON to reveal the full configuration

Escalation Triggers — when the bot offers a human
When to Handoff: Describe, in plain English, the situations that should trigger handover — keywords or sentiments such as "pricing", "talk to a person", or signs of frustration. Example: "Transfer the conversation to a human if the user expresses frustration, asks for a refund, or explicitly asks to speak with a person."
Automatic Triggers: Tick "Offer handoff to human support after N times of fallback messages" to escalate automatically once the chatbot has been unable to answer that many questions in a row.
Handover Channels — how visitors reach you
Enable the channels you want; each has its own card and required details:
Email — Enter your Support Team Email. Optionally tick "Send confirmation email to user" to send the visitor a receipt. When used, the visitor's details and an AI-generated conversation summary are emailed to your support address. ⚠️ Email handover depends on the Contact Form to collect the visitor's name, email, and phone. Use the "Configure from here" link in the Email card (or go to ACTIONS → Lead Capture) to set it up. If the contact form is not configured, the Email option has nothing to collect and the form will not appear — so always set up Lead Capture before relying on Email handover.
WhatsApp — Phone number in international format (e.g.,
+1234567890). The visitor is redirected to WhatsApp with the conversation summary pre-filled.Instagram — Username (without the
@). Summary pre-fill is not supported by Instagram.Telegram — Username (without the
@). Summary is pre-filled; redirection works only if the visitor has the Telegram app installed.Messenger — Facebook Page ID or username. Summary pre-fill is not supported by Messenger.
At least one channel must be enabled while Human Handover is turned on.
Messages — what visitors see during escalation

Transition Message — Shown verbatim when handover is triggered. A short call-to-action line is added automatically based on the channels you've enabled, so you don't need to mention the channels yourself. Example: "I'll forward your query to our human support team so they can better assist you."
Submitted Confirmation — Shown after the visitor submits the email form (their details have been sent to your team). Example: "Thanks! Our team has received your message and will get back to you shortly."
Redirected Confirmation — Shown after the visitor is redirected to a messaging app (WhatsApp, Telegram, Instagram, Messenger). Use
{channel}to insert the channel name. Example: "Opening {channel} — please continue your conversation there."
What Your Support Team Receives (Email Channel)
When a handover request is submitted via Email, your support team will receive an email containing:
User's name, email, and phone number (if provided)
A summary of the conversation
A direct link to view the full conversation in your dashboard
The session ID for reference
For messaging channels (WhatsApp, Telegram, Instagram, Messenger), the user contacts your team directly through the platform. The conversation summary is pre-filled in the message where supported.
Best Practices
Enable multiple channels to give users flexibility in how they reach you
If you enable the Email channel, configure the Contact Form first (ACTIONS → Lead Capture) — without it the Email option can't collect the visitor's details
Set clear instructions in When to Handoff for when handover should occur
Use friendly, reassuring messages to make users feel heard
Enable automatic handover to catch cases where the chatbot gets stuck
For Email, send confirmation emails to users so they know their request was received
Regularly review handover requests to improve your chatbot's responses
Note — Human Handover is a paid feature (Essential & Business plans) — and it's unlocked free while you're on the Free Full Access trial.
Email Notifications
Lead Form Email Notification

Lead Form Email Notification is a paid feature — and it's unlocked free while you're on the Free Full Access trial (it's also included on all paid plans). This feature sends you an instant email notification whenever a user fills out your chatbot's contact form. You'll immediately know when someone has provided their contact information, allowing you to follow up quickly.
How It Works
A user interacts with your chatbot and fills out the contact form (name, email, phone)
As soon as they submit the form, you receive an email notification
The email includes all the contact details and the conversation history leading up to the form submission
You can click a link in the email to view the full conversation in your dashboard
Setting Up Contact Form Email Notifications
Navigate to ACTIONS → Email Notifications
Toggle the feature ON
Enter the email address where you want to receive notifications
Make sure your contact form is enabled in ACTIONS → Lead Capture
What You'll Receive
Each email notification includes:
Contact Details: Name, email, phone number, and consent status
Conversation History: The complete chat conversation that happened before the form was submitted
Quick Access: Direct links to view the conversation in your dashboard
Benefits
Never miss a lead - get notified instantly
See the full context of how the lead was generated
Respond faster with all information in one place
Track which conversations are converting to leads
Conversation Transcript Emails

This feature automatically sends you email transcripts of completed conversations. Instead of manually checking your dashboard, you'll receive a beautifully formatted email with the entire conversation history.
How It Works
A user has a conversation with your chatbot
After the conversation ends, you automatically receive an email within an hour.
The email contains the complete conversation transcript in an easy-to-read format
Each transcript includes user details, timestamps, and all messages exchanged
Setting Up Conversation Transcript Emails
Navigate to ACTIONS → Email Notifications
Toggle the feature ON
Enter the email address where you want to receive transcripts
Save your settings
You can optionally use the "Skip Transcript" checkbox. By ticking this checkbox, for a given conversation if you have already received a "Lead Form" mail or "Human Handover" mail notification, then the conversation transcript mail will be skipped.
What You'll Receive
Each transcript email includes:
Conversation Summary: User name, date, time, and total number of messages
Complete Chat History: All messages formatted exactly as they appeared in the chat
Timestamps: When each message was sent (in your configured timezone)
Quick Access: A direct link to view the conversation in your dashboard
Benefits
Stay informed about all conversations without logging into your dashboard
Review conversations at your convenience via email
Keep a record of important customer interactions
Share transcripts with your team easily
Note: Conversation Transcript Emails is a paid feature — and it's unlocked free while you're on the Free Full Access trial (it's also included on all paid plans).
Custom Actions

Custom Actions let your agent talk to another system in the middle of a conversation — looking up an order status, booking a meeting, creating a support ticket — and answer from what comes back.
You describe in plain English when the agent should use the action, and the agent decides the rest. It collects whatever it needs from the visitor first.
In short:
Go to Actions → Custom Actions and click Add action
Give it a name and describe when the agent should use it
Paste the web address of the system it should call
List what the agent must collect first, such as an order number
Click Try it out to run it for real, then tick which of the returned fields the agent may read
Add sign-in details under Advanced settings if the other system needs them
Click Save changes in the bar at the top
Note: Custom Actions is a paid feature (Essential & Business plans) — and it's unlocked free while you're on the Free Full Access trial.
Action Buttons
Action Buttons let your chatbot show clickable buttons — like View Pricing, Book a Demo, or Contact Us — right inside the conversation, at exactly the moment they're relevant. Instead of hoping the AI mentions a link in its text, you decide which buttons appear and when. When a visitor clicks a button, the link opens in a new browser tab.

How It Works
You create one or more action groups. Each group is a set of 1–3 buttons plus a plain-English rule that describes when they should appear.
While chatting, the AI watches for that situation. When a visitor's message matches your rule, the chatbot shows that group's buttons under its reply.
The visitor taps a button and your chosen page opens in a new tab.
You can create up to 5 action groups per chatbot.
Setting Up Action Buttons
Navigate to ACTIONS → Action Buttons
Click Add action buttons (top-right)
Fill in the group:
Action name — A short name for the group, e.g. Pricing (for your reference only; visitors don't see it).
Buttons (up to 3) — Click Add button and set, for each:
Button Text — the label visitors see, e.g. View Pricing
Button Link — the web address it opens, e.g.
https://yoursite.com/pricingIcon — buttons start with No icon by default; pick an icon from the searchable list, keep No icon, or upload your own image (SVG, PNG, JPG or WebP, up to 1 MB)
Saved buttons collapse into a tidy card — click the pencil to edit or the trash icon to remove.
When should these buttons appear? — Describe the trigger in plain English, e.g. "When the visitor asks about prices or plans." This field is required.
Click Save. Use the toggle to turn a group on or off without deleting it.
Tips for the trigger condition
Keep it short and specific: "When the visitor asks how to get help" works better than a long paragraph.
Each group is independent — make conditions distinct so the right buttons show at the right time.
If no condition matches a message, no buttons appear (that's expected).
What Your Visitors See
When the condition matches, the chatbot first rounds off its answer with a short, natural lead-in line — for example "You can explore our pricing in more detail here:" — and then shows your buttons directly beneath the reply, each with its label (and icon, if you added one). This keeps the buttons feeling like part of the answer rather than appearing abruptly. Tapping a button opens your link in a new tab so the visitor doesn't lose the chat. Buttons show only the label and icon (no extra "open in new tab" symbol) for a clean look.
Example
Action name: Pricing
Buttons: View Pricing →
https://yoursite.com/pricing, Compare Plans →https://yoursite.com/compareWhen should these buttons appear?: "When the visitor asks about cost, pricing, or plans."
A visitor types "How much is the Pro plan?" → the chatbot answers, adds a lead-in line such as "You can explore the full pricing here:", and shows the View Pricing and Compare Plans buttons.
Note: Action Buttons is a paid feature (Essential & Business plans) — and it's unlocked free while you're on the Free Full Access trial.
Last updated
Was this helpful?