Try Omnifox free 7 days free. No credit card required.
Guides

Pre-Chat Forms: What to Ask Before the Chat Starts (and What Not To)

Every pre-chat field costs conversations. What to ask (name, email or phone), what to leave for later, when to skip the form and how to pair it with teams.

September 08, 2026
Pre-Chat Forms: What to Ask Before the Chat Starts (and What Not To)
In this article

    Pre-chat forms are a business decision disguised as a settings screen. Every required field you add before the conversation starts is a toll booth: some visitors pay it, some turn around. Marketing wants the company name and the budget; support wants the order number; legal wants a consent checkbox; the visitor wanted to ask one question about delivery.

    The rule this post argues for: two or three fields at most, require only what you need to follow up (an email or a phone), and let the agent or the AI ask everything else in the conversation, where it feels like talking rather than filling in a form. Below is the field-by-field breakdown (ask, do not ask, ask later), when to skip the form, when to keep it, and an example of one that works.

    What a required field actually costs

    The website chat widget already has a funnel: loads, opens, conversations started, messages sent. The pre-chat form sits between "opened" and "conversation started"; make it longer or stricter and the gap between those two numbers widens. That gap is your cost, visible in the widget funnel week to week.

    The cost differs by visitor: a shopper with a shipping question has low patience and a required email loses a good share of them; a B2B buyer on a pricing page will type a company name if it gets a faster answer; a logged-in customer with a bug has zero patience for a form asking who they are. That is why the widget lets you show the form optionally, make fields required or optional, and let the visitor skip it.

    The two-or-three field rule

    Start from what you would do if the visitor closed the tab mid-chat. Could you continue? Only with an email or a phone. Everything else is nice to have.

    1. Name. Low friction, changes the tone of the whole conversation. Optional.
    2. Email or phone, one required. This turns a visitor into a contact you can follow up with by email, SMS or WhatsApp from the same record. In the US and UK, email is the safer default; offer phone for people who prefer to text.
    3. One qualifier, only if it routes. "What is this about?" as a department selector decides who answers. "Company size" does not change who answers in the next thirty seconds.

    Anything past three fields must be justified by a specific person who will use it within the same conversation. If nobody can name that person, delete the field.

    Field table: ask, do not ask, ask later

    Field Verdict Why
    First name Ask (optional) Personalizes replies; low friction
    Email Ask (required if no phone) Needed for transcript and follow-up
    Phone Ask (required if no email) Enables SMS / WhatsApp follow-up; some prefer it
    Department / topic Ask when it routes Sends the chat to sales, support or billing directly
    Order number Ask only on support pages Lets the agent start with the answer, not the search
    Company name Ask later The agent can ask once it matters
    Company size / role Ask later Qualification belongs in the conversation, or to the AI
    Budget Do not ask Visitors either leave or lie
    Full address Do not ask Not needed to start; collect at checkout or in the CRM
    Marketing consent checkbox Ask later, separately Consent to chat is not consent to a newsletter
    Free-text "your message" Do not ask The chat is the message box

    The last row surprises people: a "your message" field before the chat turns the widget into a contact form. Let them type in the chat. For everything under "ask later", give the agent a short script ("Before I look into this, which company are you with?") and give the AI agent the same fields as a goal, so the CRM contact ends up complete without a form ever being shown.

    When to skip the form entirely

    The visitor is already identified. If your app calls the widget's identify method with the user's id and a server-side HMAC signature, the contact is matched to your customer record and the form has nothing to add. Showing it anyway tells the customer you did not recognize them.

    The visitor is returning in the same browser. The widget reopens their previous conversation; asking for their email again is friction with no benefit.

    An AI agent handles the first message. With the response strategy "always" or "only the first message", the AI can ask for a name and an email at the moment they are needed ("I can send you the quote — what email should I use?"). Fewer people refuse a question from a conversation partner than a field in a form.

    The page is high-volume and low-stakes. Product, FAQ and shipping-policy pages: let people ask without identifying and capture the contact later if the conversation warrants it, as described in how to capture leads with live chat.

    When to keep it

    Support with an order number. On order-status and returns pages, asking for the order number up front saves a round trip and lets the agent (or the AI, through its order-lookup tool) open with the status. Keep the field optional so a customer without the number handy can still chat.

    B2B qualification with real routing behind it. If the sales team is split by segment and the segment decides who answers, one selector is legitimate: "I'm looking at this for: my own business / an agency / a client".

    After hours. When nobody is online and the AI is off, the after-hours form (name and email) is the only way the lead survives until morning. Omnifox shows a configurable offline message and, if enabled, that form creates the conversation so it lands in the shared inbox.

    Pair it with departments, not instead of them

    The department selector and the pre-chat form solve different problems: the selector decides who answers, the form decides how you follow up. Both can be optional, and the order matters: department first, then only the fields that department needs. Billing may require an email to match the invoice; sales may require nothing.

    Each department has a name, color and icon, and its conversations are distributed by the team's strategy (round robin, least load or first available). A visitor who already chose a department will not see the selector again while that conversation is open, by design. The routing side is in departments in website chat.

    A pre-chat form that works

    The configuration for a UK online furniture retailer: three fields, one required, skip allowed. Returning visitors in the same browser resume their conversation and do not see it again.

    Pre-chat form (channel: Website chat — Store)
    
      Title:      Before we start
      Subtitle:   So we can reply even if you step away.
    
      Field 1:  First name          text      optional
      Field 2:  Email or mobile     text      required   help: "We'll only use this to continue this chat."
      Field 3:  What's this about?  select    optional   options: Delivery · Returns · Product question · Order status
    
      Skip button:      visible ("Just ask")
      After-hours form: name + email, creates the conversation
    

    The visitor sees a title, two boxes, a dropdown and a "Just ask" link. Those who click "Just ask" still get a conversation, and the agent asks for an email only if the answer cannot be finished in the window.

    Frequently asked questions

    How many fields should a pre-chat form have?

    Two or three: a name (optional), an email or phone (one required) and, only if it routes the conversation, a topic or department. Everything else is asked once the chat has started.

    Should email or phone be required?

    One of the two, not both. Email is the safer default for US and UK visitors; phone is worth offering because it enables SMS or WhatsApp follow-up from the same contact record.

    Does the AI agent need the pre-chat form to collect contact details?

    No. The AI can ask for a name and email in conversation and save them to the contact, which is often less intrusive. Keep the after-hours form on for when the AI is off and nobody is online.

    Fewer fields, more conversations

    Open the channel settings for your website chat, count the required fields, and cut anything that is not an email or a phone. Then watch the gap between "opened" and "conversation started" in the widget funnel for two weeks. If you do not have a chat channel yet, the 7-day free trial includes it on every plan, so you can test a three-field form against no form on your own traffic.

    Ready to try it in your business?

    Bring WhatsApp, Instagram, Messenger, email and calls into one inbox, and let AI handle the first reply. Set it up today.

    7 days free. No credit card required.

    Comments (0)

    No comments yet. Be the first to share your thoughts.

    Leave a comment

    Your email is never published. Comments are moderated before appearing.

    Markdown supported. HTML is stripped.

    Read more

    Message us on WhatsApp