The right details. In the same conversation.

A contact, a quote request or a support case needs more than a chat message. Let visitors fill in a clear form without leaving your website chat, then handle their answers with the conversation in view.

Build and manage forms from Standard. Manual sending uses Take Control, available from Pro and during the trial.

Fine engraved illustration of a paper form, fountain pen and organized conversation cards.

Your fields. Your layout. Your request.

Start with a practical template or a blank canvas. Adapt the form to the information your team actually needs.

  1. Start from a useful template

    Choose contact, quote request, appointment request, support, complaint, callback or feedback. Or build your own form from scratch.

  2. Arrange fields by dragging

    Move fields, pair two side by side, and edit their labels and required status. Check the regular and narrow widget previews before publishing.

  3. Publish when it is ready

    Set the confirmation message and your privacy-information link. While using Take Control in a website conversation, an operator can send the published form from the composer.

Form inside the website chat

Leave the details of your request here and our team will follow up.

Tell us what you need

Name
Alex
Email
alex@example.invalid
Your request
Could you send a quote for a workshop for our team?

Your own privacy-information link appears with the form.

Request submitted
Illustrative form with fictional data. This preview does not collect or send anything.

Responses your team can work through.

Submitted details belong in a clear overview, not scattered messages. Read the answers, open the related conversation and keep track of what has been handled.

SubmittedEmailRequestStatus
Today, 10:24alex@example.invalidWorkshop quotePending
Yesterday, 16:40sam@example.invalidCallback requestProcessed
Illustrative response overview with fictional data.
Keep the conversation close
Open a response from its form card in the conversation, or move from the responses table back to the chat.
Separate pending from processed
Mark responses as processed individually or in bulk. Use the filters to focus on pending work, and return a response to pending when needed.
Keep submitted values out of model context
The assistant receives the form's title and status, not the filled-in values. Authorized team members can read the responses and erase their values when needed.

Before you send your first form

A few useful boundaries for setting up your team's workflow.

How does a form reach the visitor?
Today, an operator sends a published form while holding Take Control of a website conversation. Form management is available from Standard; Take Control requires Pro or higher, or an active trial. Automatic form selection by the AI is not available yet.
Can one form have several languages?
Each form currently has one authoring language, Czech or English. Shared multilingual versions and automatic translations are not available yet.
Does an appointment form make a booking?
No. It collects a preferred date and contact details for your team to review. Submitting a form does not reserve a slot, run a Custom Action or send the answers through a webhook.

Ask for what your team needs.

Prepare a form for one real customer request, check its widget preview and decide how your team will handle the responses.

Compare plans and trial