How to set up the Action Bar and lead forms
Turn the widget footer into a focused conversion path without overloading visitors.
The Action Bar places up to five actions at the bottom of the floating widget and replaces prompt buttons in that location. Use it for destinations or transactions that should remain permanently available.
Custom form submissions become leads, with email and phone recognized automatically and extra fields stored in lead details.
What you will have at the end
- A focused link-and-form Action Bar
- A callback form with required validation
- A real stored lead with mapped contact fields
Before you start
- Standard plan or trial
- Approved destination URLs and phone numbers
- A defined lead owner and privacy text
Persistent actions, measurable outcomes
Link, WhatsApp, Form and Calendly items use different visitor flows but share one compact row. A form submission is stored in Leads and can trigger notifications.
More actions do not necessarily convert better. Prioritize one main action and keep forms short.
01–07
Set it up step by step
Enable the Action Bar
Start with the complete empty configuration in view.
Open Widget Integration → Action Bar and enable it. The bar can hold up to five Link, WhatsApp, Form or Calendly items and replaces prompt buttons at the bottom of the floating widget. Decide on one primary conversion goal before adding anything.
Build the callback form and field validation
Collect only the data needed for the promised follow-up.
Create “Request a callback” under Forms. In the verified example, Full name and Work email are required, Phone is optional, the submit button says “Send request” and the success message promises contact within one business day.
Choose semantic field types: email and phone types add format-aware validation, while labels control how the submission maps into the lead record. Use an Info field for privacy context if the surrounding page does not already explain processing.
Connect a documentation link and the form
Keep the primary action visible and every destination explicit.
Add a Link item named “Documentation” and a Form item named “Request a callback”, then select the callback form. Link targets must use HTTPS; WhatsApp numbers should use international format; Calendly URLs should point directly to the intended event type.
Save the widget settings only after every item shows the correct icon, label and destination. Icon-only mode is suitable only when the icon remains unambiguous without surrounding text.
Verify both actions in the live widget
Confirm the saved bar, not merely the dashboard editor.
Open the real light-mode visitor preview. Confirm that Documentation and Request a callback are both visible, keyboard reachable and do not overlap the message input. Open the link in a safe test context and then select the form action.
Complete the form as a visitor
Use recognizable, non-production test data.
Enter Alex Example, alex@example.com and +49 30 123456. Verify that required fields block an incomplete submission and that the email and phone inputs accept the correctly formatted values before selecting Send request.
Confirm the visitor success state
The exact promised follow-up now appears in the widget.
Wait for the success state before closing the widget. The verified result displays “Thanks! Our team will contact you within one business day.” This proves that client validation and the form-submit API completed successfully.
Verify the stored lead in the dashboard
Close the loop from visitor action to team workflow.
Open Dashboard → Leads and locate the new row. Verify chatbot, name, email, phone, interest, status and timestamp. Open details when you use extra fields, then assign an owner or update status according to your lead process.
The test account showed exactly one new lead for Alex Example with the submitted email and phone. This is the required end-to-end proof; a form preview alone does not confirm storage.
Example & result
See the practical test and its result
Every tutorial includes a fixed input, the expected outcome and a transparent record of what was actually verified locally.
Practical example: How to set up the Action Bar and lead forms
This exact scenario was completed with the temporary tutorial account.
Exact test input
Open “Request a callback” and submit Alex Example, alex@example.com and +49 30 123456.
Expected result
The form validates, displays the one-business-day success message and stores one mapped lead.
What was actually verified
The real visitor form submitted successfully and Dashboard → Leads showed exactly one new Alex Example row with the submitted email and phone.
Tips & tricks
Make the setup reliable
Test with realistic examples, record your baseline and change one setting at a time. That makes real improvements visible.
One primary action wins
Place the highest-value action first and remove options that duplicate the same outcome.
Ask later for optional details
A short initial form improves completion; sales can collect secondary details during follow-up.
Enable and monitor the Leads tool
The Action Bar form stores the record; the Leads tool and notification recipients make sure someone actually handles it. Test both storage and ownership.
When something does not work
Troubleshooting
Check status, permissions and test data systematically before changing the model or prompt.
The expected option is missing
Confirm the account plan, feature permissions and selected chatbot. Paid or beta features can be hidden when prerequisites are not met.
The test result is inconsistent
Reset the test conversation, keep the input identical and change one setting at a time so the cause remains measurable.
Ready for a production-style test
Compare item clicks and completed leads, then shorten or reorder the bar based on outcomes rather than aesthetic preference.