A form that accepts a message is not the same as a form that starts a conversation. The second one has an owner, a destination and a sentence that tells the visitor what will happen.

The Cold Banana team together

One form for one job.

A general contact form, a careers form and a product enquiry are different jobs. They can share a pattern. They should not share a single inbox if three teams are then forwarding mail to each other.

Ask, for each form, who must see it and how quickly. Write that name down. A shared mailbox is fine when a named group watches it. It is not fine when everyone assumes someone else will reply.

Ask only for what the reply needs.

Name, a way to reply, and enough detail to route the message. Extra fields feel thorough and reduce the number of people who finish. If marketing needs more, collect it after the conversation has started.

Labels should be clear in every language on the site. A required field that is obvious in English and ambiguous in Arabic will be skipped, or filled with something you cannot use.

Tell the visitor, then tell your team.

The thank-you message should say what happens next and roughly when. The email to your team should say which page the person was on, and it should be sent to the address you agreed, not to a developer who left the project.

Decide what the site does when the message cannot be sent. The visitor should not see a success message for an enquiry that never left the form. Someone inside the organisation should be able to tell that it failed.

Test it the way a customer will.

Submit the form on a phone, in each language, and wait for the email. Reply to it. Check that the reply goes to the visitor and not into a void.

Cold Banana wires enquiry forms into the way your teams already work. The measure is simple: a real message, from the live site, in the right inbox, with a person ready to answer.