Pre-chat form· Conversation design
Pre-Chat Form — The Questions Before the Chat
Quick answer: A pre-chat form sits between "I want to ask something" and the first message. It can collect an email for follow-up, a department for routing and the question itself, so the agent starts with context. The cost is friction: every required field is a reason for some visitors to close the widget instead. Vendors also call it a pre-chat survey.
What a pre-chat form usually contains
| Field | Why teams add it | What vendors document |
|---|---|---|
| Name | Personal greeting, record keeping | Zendesk and LiveChat offer it as a standard field |
| Follow-up if the visitor leaves; matching to a contact | Zendesk notes that without name and email collection you cannot follow up after the session | |
| Phone | Call-back | Zendesk: optional by default, can be made required |
| Department or group | Routing to the right team | Zendesk shows it automatically when departments exist; LiveChat's group selection routes the chat |
| The question | Agent sees the topic before answering | Zendesk adds a message field; its label cannot be changed |
| Choice or dropdown questions | Qualification, topic picking | LiveChat lists choice list, dropdown and multiple choice fields |
| Consent checkbox | Privacy notice, AI disclosure | LiveChat gives sample consent clauses; HubSpot has a separate consent setting |
LiveChat's page says that "three-liners" (name, email and a short description) work in most cases. That is a vendor suggestion, not a measured rule.
The trade-off: context versus conversations
The form exists because an anonymous chat is hard to route and impossible to follow up once the visitor leaves. It costs conversations because some people will not type an email to ask a quick question.
Intercom is the one vendor read here that puts a number on it. Its article on requiring an email before a conversation estimates that requiring it only outside office hours reduces conversation volume by about 5% on average, and requiring it always by about 30%. It recommends the office-hours option. Those are Intercom's own estimates without a published method, so treat them as a direction, not a forecast for your site. LiveChat's page makes the same point without a number: more required fields make people less likely to chat.
Pre-chat form versus asking inside the chat
| Pre-chat form | Asking in the conversation | |
|---|---|---|
| When details are collected | Before the first message | After the visitor has asked |
| Effect on starting a chat | Adds a step up front | No extra step to start |
| Routing | Can route from the first second | Routes after the answer |
| Risk | Visitors leave before asking | Visitors leave before giving details |
| Typical tool | Live chat widget settings | A chatbot flow; see slot filling |
Many teams combine them: an optional form, or no form, and a chatbot that asks for an email only when the conversation needs a follow-up. Collecting a little at a time across visits is progressive profiling.
When the form does not appear
- Proactive chats. Zendesk's proactive chat article says chats started by a proactive trigger skip the pre-chat form, so routing and contact details can be missing. See proactive chat.
- Manual invitations. LiveChat's page says the form is not shown when agents invite a visitor to chat manually.
- After campaigns. LiveChat lets admins choose whether the form shows after a campaign message; its page says Starter plan users always see it.
- Known visitors. Intercom does not ask leads who already gave an email again. LiveChat lets you pre-fill the form for logged-in customers through its API.
What the vendor pages do and do not say
- Zendesk documents five elements for the Classic web widget (greeting, identity, phone, department, message) and how to make phone, department and message required. It does not say whether name and email are required by default.
- LiveChat lists eight field types and a required checkbox per field. It gives no conversion data and no recommended maximum number of fields beyond the three-liner suggestion.
- Intercom offers "Always" or "Only outside of office hours" for requiring an email from leads and logged-out users.
- HubSpot sets when visitors are asked for their email in an email capture section, creates a contact if the address is new, and has separate consent options, including explicit "I agree" consent before sending a message. It does not say whether known contacts are skipped.
- Zoho SalesIQ lets you add fields and mark them mandatory; its page does not list field types or describe skipping the form for returning visitors.
None of these pages reports a measured completion rate for the form itself.
Privacy
A pre-chat form collects personal data before the visitor has said a word, so it is a natural place for a short privacy notice and, where your rules require it, consent. Ask only for what the chat needs, and decide how long you keep it; see data retention policy and the GDPR chatbot compliance guide. This is not legal advice.
FAQ
What is a pre-chat form? A short form shown before a chat starts, asking for details such as name, email, topic or department, so the chat can be routed and followed up.
Is a pre-chat form the same as a pre-chat survey? Yes. LiveChat, for example, uses "pre-chat survey" and "pre-chat form" for the same feature.
Do pre-chat forms reduce the number of chats? They can. Intercom estimates about a 30% drop when an email is always required and about 5% when it is required only outside office hours. These are vendor estimates; test on your own site.
What fields should a pre-chat form have? As few as the chat needs. Email and the question are the most common; department only if you route by it. LiveChat suggests name, email and a short description for most cases.
Should I use a pre-chat form or let a chatbot ask? A form gives context from the first message; asking inside the chat lets the visitor start immediately. Many teams use no form, or an optional one, during working hours and ask for an email when a follow-up is needed.
Do proactive chats show the pre-chat form? Not always. Zendesk says proactive chats skip it, and LiveChat says manual invitations skip it. Check your platform.
Related terms
- Live chat — the channel the form usually sits in front of.
- Proactive chat — chats you start, which may bypass the form.
- Conversational form — asking one question at a time instead.
- Progressive profiling — collecting details over several visits.
- Lead generation chatbot — a common reason to collect contact details.
- Human handoff — where routing data from the form is used.
- Chat routing — how the topic or department from the form picks a team and an agent.
- Chatbot abandonment rate — a metric a form can shift.
Sources
- Zendesk, How do I customize the pre-chat form? — support.zendesk.com/hc/en-us/articles/4408825438746-How-do-I-customize-the-pre-chat-form, read 10 November 2026. Source of the five elements, the required options and the follow-up note. Applies to the Classic web widget; silent on default required fields and plans.
- Zendesk, Using proactive chat to target key visitors — support.zendesk.com/hc/en-us/articles/4408883473178-Using-proactive-chat-to-target-key-visitors, read 9 November 2026. Source of the note that proactive chats skip the pre-chat form.
- LiveChat, Chat surveys — livechat.com/help/chat-surveys/, read 10 November 2026. Source of the eight field types, required fields, group routing, the three-liner suggestion, manual-invitation and campaign behavior, API pre-fill and sample consent clauses. No conversion data.
- Intercom, Require leads to give their email to start a conversation — intercom.com/help/en/articles/2301967-require-leads-to-give-their-email-to-start-a-conversation, read 10 November 2026. Source of the "Always" and office-hours modes and the 30% and 5% volume estimates. No method published.
- HubSpot, Create a live chat — knowledge.hubspot.com/chatflows/create-a-live-chat, read 10 November 2026. Source of the email capture and consent settings.
- Zoho SalesIQ, Pre-chat window fields — zoho.com/salesiq/help/configuration-fields-pre-chat.html, read 10 November 2026. Source of adding and requiring fields; silent on field types and returning visitors.
- Chatbotscape evaluation methodology. /methodology (continuously updated).