Customer contact · How-to

How to add a contact form to your product website

A contact form doesn't need ten fields or a separate “support experience.” It needs to be easy to find, easy to send, and checked by a human.

Pick the right spot

If people mostly get stuck while using your app, put Contact in the app menu or help area. If the questions are about pricing, put a link near pricing. A form hidden in the footer may be technically available but practically invisible.

Make the link label direct: “Contact us” or “Ask a question.” “Let's connect” can mean anything.

Ask for less

An email address and a message are usually enough to start. A name can help make the reply more personal, but don't require a phone number if you don't plan to call. If you need a project ID to investigate, consider attaching it automatically in your own app rather than asking the customer to find it.

Test it like a visitor

1. Open the page in a private browser window, not your signed-in workspace.
2. Send a short test message from an address you can check.
3. Confirm that the message arrives in the inbox you actually use.
4. Try an invalid email and an empty message. The error should be clear.
5. Try it on a phone. Can you reach the submit button without fighting the layout?

Decide how you'll respond

Collecting a message is only half the job. Put a short daily check on your calendar or route new messages into a workflow you'll see. If you offer an email reply, test that replies reach the sender. For urgent issues, say where to go; don't imply that a small form is 24/7 live support.

MVPKit lets you embed a contact form on your own site or use your project's public Contact page. Messages go into that project's inbox. You can turn public contact on or off in project settings.