Skip to content
Chatbotscape
Zendesk's pre-chat form article, LiveChat's chat surveys page, Intercom's article on requiring an email, HubSpot's live chat setup article and Zoho SalesIQ's pre-chat fields page were read on 10 November 2026. Settings, plans and menu names change, so check each vendor's current documentation.
Pre-chat form· Conversation design
A pre-chat form is a short set of fields, such as name, email, topic or department, that a chat widget shows before the conversation starts, so the team or chatbot knows who is writing and where to send the chat.
By Chatbotscape Editorial· Methodology· Published 11 November 2026· Updated 11 November 2026

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

FieldWhy teams add itWhat vendors document
NamePersonal greeting, record keepingZendesk and LiveChat offer it as a standard field
EmailFollow-up if the visitor leaves; matching to a contactZendesk notes that without name and email collection you cannot follow up after the session
PhoneCall-backZendesk: optional by default, can be made required
Department or groupRouting to the right teamZendesk shows it automatically when departments exist; LiveChat's group selection routes the chat
The questionAgent sees the topic before answeringZendesk adds a message field; its label cannot be changed
Choice or dropdown questionsQualification, topic pickingLiveChat lists choice list, dropdown and multiple choice fields
Consent checkboxPrivacy notice, AI disclosureLiveChat 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 formAsking in the conversation
When details are collectedBefore the first messageAfter the visitor has asked
Effect on starting a chatAdds a step up frontNo extra step to start
RoutingCan route from the first secondRoutes after the answer
RiskVisitors leave before askingVisitors leave before giving details
Typical toolLive chat widget settingsA 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.

Sources