Pre-chat form questions are the handful of fields a visitor fills in after opening the chat window and before sending the first message. The form helps when every field solves a specific problem for your team: it routes the case to the right person, lets you reply after the customer closes the tab or saves the agent an opening question. It hurts when it turns a quick question into a registration process. The customer opened the chat to sort something out now, not to fill in a survey.
This guide works through the decision field by field: what to require, what to keep optional, when to skip the form and how to check what it costs you. We cover field count for a regular website form separately in our guide to contact forms. A pre-chat form follows a similar rule but appears at a different moment: the customer has not asked anything yet and does not know whether anyone will reply.
Pre-chat form questions: every field answers a team question
Before you add a field, write down the operational question it is meant to answer. If nobody on the team acts differently because of the value entered, the field is unnecessary. A name does not route anything, but it makes a natural tone easier. An email address makes sense when you really do reply after the visitor has left. A company name helps in B2B sales, while in an accessories shop it usually just makes the form longer.
Scroll the table sideways to see all columns.
| Field | Operational question | When to require it | When to drop it |
|---|---|---|---|
| Name | How should we address the customer? | Rarely; optional is usually enough | When chats are short and anonymous |
| How do we reply if the customer leaves? | When coverage is patchy and you answer later | When agents reply within a few minutes | |
| Company | Is this a business customer, and who owns the account? | When serving existing B2B customers | In retail and services for private individuals |
| Department choice | Who should reply first? | When departments have different people and hours | When the same team handles every chat |
Keep qualifying questions such as budget or rollout date out of the pre-chat form: they belong in the conversation, and we cover their order in our guide to qualifying leads on your website. The form should start the conversation, not replace it.
Required, optional or hidden
A required field is a condition for starting the chat. So require only what your team genuinely cannot work without, most often a way to follow up when coverage is irregular. An optional field collects data from people willing to share it and does not stop anyone else. A hidden field is an honest decision that the information is not needed right now, even if a dashboard would look fuller with it.
The LiveChat documentation warns that the more fields you require, the less likely people are to chat, and suggests name, email and a short description of the inquiry as a typical set. That is vendor advice, not research for your industry. LiveChat Help Center.
A "Describe your issue" field in the pre-chat form usually duplicates the first message. It is better to leave room for the question in the chat itself and write a good sentence above the form. That sentence should say why you need the data and what happens next. We collect sample opening lines in our guide to chat greetings.
"Leave your email if you'd rather not keep this chat open. If we can't reply right away, we'll send the answer to this address." The sentence explains what the field is for and does not promise a response time your team might miss.
Department choice: a short list customers understand
A department choice in the pre-chat form makes sense when a wrong guess means transferring the chat and explaining the case again. Name the options in the customer's language: "Question before buying", "My order", "Invoices". Three or four options are usually enough. A customer who is unsure what to pick needs a general option that goes to whoever is on duty.
The form alone does not decide who owns the chat within a department or what happens to the unassigned queue. We cover those rules in our guide to assigning customer requests. In the Meetlead widget, customers can only pick departments marked as public. If there are none, the chat still starts, and an outdated choice falls back to the default department or to the unassigned queue.
When to skip the form
The form does not have to appear every time. A customer who shared their details last week should not type them again. A chat that is already under way must not be interrupted by a sudden form. Outside business hours, a pre-chat form in front of a chat nobody will answer only delays the news that an offline message is the better route. We cover that situation in our guide to out-of-hours messages.
- A returning visitor who completed the form does not see it again.
- An ongoing conversation is never interrupted by a request for details.
- Outside business hours, customers reach the offline form instead of an empty chat.
- On pages with quick questions, such as delivery, the fields stay optional.
- A signed-in customer does not have to retype details you already hold.
In Meetlead, the form appears before the first message and never interrupts an existing conversation. A visitor who has completed it will not see it again until you change the field setup or the privacy policy URL. A change to the fields means you are asking for different data.
Data minimization and the privacy confirmation
The rule of one field, one operational question matches the GDPR principle of data minimization. A field without a purpose is also hard to justify legally. If the form includes a privacy policy confirmation, link to the section about chat rather than the top of a long policy page. We cover the wider set of decisions about conversation data in our article on live chat and the GDPR.
Article 5(1)(c) of the GDPR, applicable since 25 May 2018, requires personal data to be adequate, relevant and limited to what is necessary for the purpose. The UK GDPR contains the same principle; elsewhere, check your local rules. The provision does not list specific form fields, and this text is not legal advice. Regulation 2016/679, EUR-Lex.
How to measure drop-off before the first message
The form costs you conversations in one specific place: between opening the window and sending the first message. You can measure that gap without guessing. Compare periods with similar traffic and change one thing at a time, because a new greeting and a new field launched together will not tell you which one worked.
- Record a baseline.Count chat opens and conversations with a first message over the past two weeks with your current fields.
- Change one field.For example, switch email from required to optional and note the publishing date.
- Compare the same period.After a similar stretch, count the same two numbers. Set aside days with campaigns or outages.
- Check the cost to your team.Count chats where the customer left without a way to follow up and the answer never reached them.
The last step stops you from concluding that fewer fields are always better. If dropping the email requirement brings more chats but also more unanswered questions, rethink your coverage or bring the field back. In the Meetlead widget, chat opens and sent messages are recorded in the visit history, and the Widget Studio preview lets you check the form before publishing.
Questions about pre-chat forms
Should email be required? Only if your team actually replies by email to chats abandoned midway. If agents usually respond within a few minutes, a required email will stop some customers for no benefit. Start with an optional field and a clear note, then measure how many chats end without a reply.
Should you ask for a phone number? Only if your team actually calls people back. A number requested at the start of a chat makes visitors wonder why you need it, and it often goes unused. If you do call back, offer a separate callback request where the customer leaves a number when they want a call. In the Meetlead widget, that is the callback option, which works independently of the pre-chat fields.
