When I started building form pages for Formpit, I copied the thing Formpit already did well: every response lands in an inbox and stays "New" until you reply. Then I looked at what people actually make with forms, and most of them never need a reply. This is the story of that mistake, the simple rule I ended up with, and how it changed the product.

Where the inbox came from

Formpit started as a form backend for contact forms. For a freelancer or a small business, a contact form isn't done when the email arrives. It's done when you've replied. So every submission is marked New, Replied or Closed, you can reply from Formpit itself, and it reminds you about anything that has been waiting for two days.

When I added form pages, forms you build in Formpit and share as a link or a QR code with no website needed, I reused that flow without thinking twice. A response is a message, a message needs an answer. Simple.

Nobody replies to 60 RSVPs

The first starting points I built were RSVP, registration, feedback, order and file upload forms. While testing the RSVP one, I filled it in as a host would, and realised I would never reply to a single guest. I'd want three things: how many people said yes, how many guests they're bringing in total, and whether anyone has dietary needs.

In the inbox flow, those 60 RSVPs would sit there as "New". Reminders would nag about them. The unanswered count would never reach zero. The product would keep telling the host they were behind on work that doesn't exist.

Search data told the same story. When I looked at what people search for in Ahrefs, "rsvp form", "sign up sheet", "survey" and "registration form" came up again and again. Contact forms, the one kind that really needs a reply, were just one entry in a long list.

The rule: is someone waiting on an answer?

I posted about this on X and Threads, and other builders put it better than I had. One said: default RSVPs and surveys to a live count, and only open an inbox when a person is waiting on an answer. Another said a count tells you something happened, and one line of free text tells you why.

That gives one question to ask about any form:

Form Is someone waiting on an answer? What it needs
Contact form Yes An inbox
Quote request Yes An inbox
RSVP No A headcount
Registration or sign-up No A list and a total
Feedback or survey No Averages, plus the comments
File collection No The files, in one place
Order Not usually A table, with a confirmation email

What the two modes do

So every Formpit form now has a mode.

Collect

  • Summary: how many people chose each option, averages and totals for ratings and numbers, and the latest written answers.
  • Table: every response, sortable and filterable, with a CSV download.
  • Email: one for every response, one summary a day, or none.
  • Closing: stop after a number of responses or on a date, with your own message.
  • No guilt: nothing is marked unanswered and nothing sends reminders.

    Conversation

  • Each response lands in an inbox as New, Replied or Closed.

  • You reply from Formpit, and the reply goes to the person's email.

  • Anything waiting two days gets a reminder.
    Both modes use the same builder and give you the same link, QR code and embed code. Only what happens after someone presses Send is different.

Defaults, not a quiz

I didn't want people to learn the word "mode" before making their first form. You start by picking what the form is for, and each starting point comes with the right mode: Contact and Quote request start as conversations, and RSVP, registration, feedback, order and file forms start in Collect.

If the guess is wrong, you switch in the side panel at any time. Switching to Collect moves anything still marked New out of the unanswered count. Switching to Conversation turns on an email for every response, because someone is now waiting on you.

How it works under the hood

The change was smaller than I expected, which usually means the model was right:

  • One column. Each form has a mode of collect or conversation.
  • One status. Responses to a Collect form are saved with the status received instead of new. Unanswered counts and reminders only look at new, so they ignore these without any special cases.
  • One summary function. The summary is worked out from the form's own question types: choices become counts, ratings and numbers become averages and totals, and text questions show the latest answers. The same function writes the daily summary email.
// After the submission is saved if (form.mode === 'collect') { setStatus(submissionId, 'received'); // nothing to answer } 

Because the summary comes from the question types, a new kind of question gets a summary for free, and nobody has to set up a chart.

What I'd tell another builder

  • Use your product as the person on the other end. I only saw the problem when I filled in the form as a host. Reading the code would never have shown it.
  • When two groups need opposite things, choose a default for each. A setting hidden in the options would have left most people with the wrong one.
  • Say the lesson out loud. Posting about it got me clearer explanations than my own, and some of them are now in this article. If you're making an RSVP, a sign-up sheet or a survey, you can try Collect mode yourself at formpit.com/create. Form pages are free up to 500 responses a month, and nobody needs an account to answer.

Which kind of form do you make most often: one you count, or one you reply to?