Your Website Form Should Do More Than Send an Email.
Someone visits your website.
They fill out a form.
They click Submit.
You get an email.
Technically, everything worked.
But then someone on your end has to open the email, figure out what the person needs, forward it to somebody else, copy part of the information somewhere, send a response and remember what needs to happen next.
The form worked. The process didn’t.
This is one of those small things businesses get used to doing manually because each individual step doesn’t seem like a very big deal.
But if the same thing happens five times a day, 20 times a week or hundreds of times a year, the question changes.
Instead of asking, “How can we handle these emails more efficiently?” it may be worth asking:
Why does this need to become an email in the first place?
Website form automation doesn’t have to mean building a complicated system. Sometimes it simply means using information the customer has already provided to make the next step happen automatically.
A Form Isn’t the Process. It’s Where the Process Starts.
Most conversations about website forms focus on the front end.
What fields should we include?
Should we ask for a phone number?
How long should the form be?
What should the button say?
Those things matter.
But when we’re building forms for a business, there’s another question that can be much more important:
What needs to happen after the customer clicks Submit?
That’s where a basic contact form can become something considerably more useful.
The answer will be different for every business.
An estimate request might need to go to a salesperson.
A maintenance request might need to reach the person responsible for a particular property.
An application might need documents attached to the customer’s record.
A new-client inquiry might need to create a follow-up task.
An appointment request might need to connect with scheduling.
A payment form might need to trigger a receipt and notify accounting.
Once you understand what actually needs to happen, you can start designing the form around the business instead of simply designing a nicer way to send an email.
Start With the Next Step
Here’s a simple exercise.
Pick one form on your website and pretend someone just submitted it.
Now follow the information.
Who receives it?
What does that person do with it?
Does somebody have to decide who should handle it?
Does the information get entered somewhere else?
Does someone send a standard response?
Does a task need to be created?
Does a customer need to provide something else?
Does another employee need to know about it?
What happens if nobody notices the email?
That last question is particularly useful.
Because if the entire process depends on the right person seeing a message in an inbox, the form may only have digitized the first five seconds of the process.
Different Requests Shouldn’t Always Go to the Same Place
One of the simplest improvements is routing.
Imagine a commercial property-service company with a form that asks what kind of request the customer is submitting.
The choices might include:
- Request an estimate
- Report a service issue
- Submit a billing question
- Request additional work
- Upload photos or documents
Those requests don’t necessarily belong with the same person.
Yet a traditional contact form often sends all five to info@company.com and leaves a human being responsible for sorting them.
The website already knows what kind of request was submitted.
Why not use that information?
An estimate can notify sales.
A service issue can go to operations.
A billing question can reach accounting.
A request associated with a particular community, office or property can be routed to the person responsible for that location.
If the customer has already told the website where the request belongs, your staff shouldn’t necessarily have to figure it out again.
The Confirmation Message Is Part of the Process Too
“Thank you. Your message has been sent.”
That’s better than nothing.
But it doesn’t tell the customer very much.
A useful confirmation should answer the questions the person is likely to have next.
Was the request received?
What happens now?
When should they expect a response?
Should they do anything else?
Is there something they should not do, such as submitting the same request again?
The confirmation can also be different depending on what the person submitted.
An estimate request might explain that someone will review the project details before contacting them.
A service request could provide a reference number.
An application could identify missing documents.
An appointment request might send the person directly to scheduling.
This is a small part of the experience, but it’s often the moment when a prospective customer is paying the most attention.
They’ve just raised their hand and asked your business for something.
Don’t leave them wondering whether anything happened.
Ask for What You Need. Not Everything You Might Ever Want.
It’s tempting to use a form as an opportunity to collect as much information as possible.
More information feels useful.
But every additional field creates another decision for the customer and another piece of information your business has to handle.
The Federal Trade Commission’s guidance for businesses handling personal information makes a very practical recommendation: understand what personal information enters your business, where it goes and why you’re keeping it. The FTC also recommends that businesses avoid collecting sensitive information they don’t legitimately need.
That’s good security advice.
It’s also good form design.
If you don’t need someone’s home address to answer an initial question, don’t ask for it just because the form builder has an address field.
If you need a property address to dispatch a service crew, that’s different.
The business requirement should determine the field.
Not the other way around.
A Short Form Isn’t Automatically a Better Form
You’ve probably heard the advice that shorter forms convert better.
Sometimes they do.
But that’s an incomplete way to think about it.
A three-field form that forces your employee to call the customer and ask eight more questions isn’t necessarily more efficient than a seven-field form that gives everyone what they need the first time.
The goal isn’t simply to make the form short.
The goal is to ask for the right amount of information at the right point in the process.
An initial contact form should probably be simple.
A detailed project-estimate form may reasonably need more information.
A service request may need a property, location, priority and photograph.
An application may need several sections and supporting documents.
Context matters.
Forms Should Be Easy to Understand When Something Goes Wrong
We’ve all encountered the form that refuses to submit without making it clear why.
Something turns red.
You scroll up.
You scroll down.
You try again.
Eventually you abandon it.
The W3C Web Accessibility Initiative’s form guidance recommends that errors clearly identify the affected field, explain the problem and tell the user how to correct it.
Required fields should also be clearly identified rather than relying solely on a tiny red asterisk.
These are accessibility considerations, but they’re also common-sense customer-experience considerations.
People shouldn’t need to solve a puzzle to contact your business.
What Can Happen Automatically After a Form Is Submitted?
This is where the possibilities get interesting.
Depending on the business and the tools it already uses, a form submission might:
- Send the request to the appropriate employee or department
- Send a useful confirmation to the customer
- Create or update a customer record
- Add information to a CRM
- Create a task
- Trigger an internal notification
- Send someone to a scheduling page
- Start an estimate or approval process
- Associate uploaded files with the right request
- Notify different people based on location or request type
- Record the submission somewhere other than an email inbox
- Trigger a follow-up if nothing happens within a certain period
Not every business needs all of that.
In fact, most shouldn’t do all of it.
Automation is useful when it removes an unnecessary step.
It’s not useful when it turns a simple process into a complicated collection of software that nobody understands.
That’s why we don’t start with the automation.
We start with what needs to happen.
Don’t Automate a Bad Process
This is important.
If a process doesn’t make sense manually, automating it can simply make the confusion happen faster.
Before connecting a form to five other systems, map out what should happen.
Who actually needs this information?
Which steps are necessary?
Which steps exist only because “that’s how we’ve always done it”?
Where does somebody need to make a judgment?
Where is the same information being entered twice?
Where does the process regularly get stuck?
Those questions often reveal that the best improvement isn’t adding technology.
It’s removing a step.
That’s the same principle we discussed in our article about stopping repetitive manual work with better business systems.
The objective isn’t automation for its own sake.
It’s making the work make more sense.
Some Things Should Still Reach a Person
Not every submission needs an automated journey.
Sometimes the right next step is simply for a salesperson, a property manager or another real person to read what someone wrote and respond thoughtfully.
That’s especially true when the request is unusual, sensitive, complicated or valuable.
Automation shouldn’t remove judgment where judgment matters.
It should remove the unnecessary work around that judgment.
A good system might make sure the request reaches the right person, provide that person with the information they need and acknowledge the customer immediately.
Then the human takes over.
Technology handles the handoff. The person handles the relationship.
What About Sensitive Information?
This deserves more attention than it sometimes gets during website projects.
If your form collects personal, financial, health-related or otherwise sensitive information, don’t casually treat it like an ordinary contact message.
Think about what you’re collecting, why you’re collecting it, where it’s stored, who can access it and how long it needs to exist.
The FTC’s Start with Security guidance specifically advises businesses not to collect personal information they don’t need and to limit how long information is retained when there is no continuing business reason for it.
Different industries may also have specific legal or regulatory requirements.
That’s another reason a form shouldn’t be designed in isolation from the business process behind it.
Your Website Already Knows More Than You May Be Using
Think about what a customer tells your website during a typical request.
Who they are.
What they need.
Where they’re located.
Which service they’re interested in.
Which property they’re contacting you about.
How urgent the request is.
When they’re available.
Maybe even photographs or documents that explain the situation.
Then think about how often somebody inside the business reads that information and manually turns it into the next action.
That’s the opportunity.
Not necessarily to automate everything.
But to ask whether the website can do a little more of the work it has already been given enough information to do.
This Is Especially Useful for Businesses Managing Lots of Requests
In Palm Beach County, we work in a market full of service businesses, professional firms, property-related companies, associations and organizations where customer requests don’t all look the same.
A commercial landscaping company may serve dozens of communities.
A professional office may receive several different kinds of inquiries.
A retreat or event business may need registrations, payments and participant information.
A contractor may need photos before deciding whether a site visit is necessary.
For businesses like these, a website doesn’t have to be just the place where customers learn about the company.
It can become a useful part of how customers interact with it.
So What Should You Look at on Your Own Website?
Start with one form.
Don’t buy anything.
Don’t install anything.
Just submit the form yourself and follow what happens.
Then ask:
- Are we asking for the information we actually need?
- Are we asking for anything we don’t need?
- Does the request reach the right person?
- Does somebody manually forward or re-enter it?
- Does the customer know what happens next?
- Can the customer understand and correct an error?
- Does someone have to perform the same predictable task after every submission?
- Could one of those steps happen automatically?
- Where does human judgment actually add value?
You may discover that the form is perfectly fine.
Or you may discover that a five-minute improvement could remove a task your business has been repeating for years.
A Better Website Doesn’t Always Mean More Pages
When people think about improving a website, they often think about redesigning it, adding pages or changing how it looks.
Sometimes that’s exactly what’s needed.
But sometimes the biggest improvement is invisible to most visitors.
It’s what happens after they click the button.
A request reaches the right person.
A customer immediately knows what happens next.
An employee doesn’t have to copy the same information again.
A document stays connected to the request it belongs to.
A task doesn’t disappear into an inbox.
None of those things makes for a dramatic homepage screenshot.
They simply make the business work better.
That’s what we mean when we say a great website is only the beginning.
If your website is collecting information but your team is still doing a lot of work manually after every submission, we can look at what happens next.
You don’t need to know which plugin, platform or automation you need.
Tell us what you’re trying to accomplish.
We’ll start there.
Schedule a Complimentary Discovery Call →
Built in collaboration with ChatGPT.
