01
Take a request by topic
The client picks a topic first, then writes what happened.
- Payment and access do not sit in one pile
- An empty “it does not work” reaches you less often
SUPPORT
The client describes the problem, you see the request
Topic, details, and a contact in one form. The request arrives as a submission, instead of getting lost among emails.
Try it free
no developer needed
The problem
The request drowns in the inbox
Everything lands in one inbox
Payment, access, and an order question arrive as one pile of emails.
The client does not write what broke
An email that says “it does not work” has no topic, order, or the step where they stopped.
A follow-up is not tied to the first email
The person writes again. The earlier request has to be found in email.
In the form
What the support form collects
Request topic
The client picks a topic before the text: payment, access, or an order.
Fields of their own by topic
Payment asks for the invoice number. Access asks for the login. Extra fields stay hidden.
A contact for the reply
Email or phone sit on the same request as the description.
The request in the submissions list
Topic, text, and contact stay as a request. A shared inbox is not needed for this.
The work
What FormDesigner handles
The topic, the description, and the request in one list.
02
Narrow the problem with a branch
The topic opens its own fields. The client does not fill in someone else’s questions.
- An invoice number is asked only about payment
- A short path for a simple question
03
Keep support requests apart from site leads
The help form collects a problem. The form on a landing page collects a lead.
- Support has its own list of requests
- The contact for a reply sits on the request
How it works
How to open requests
-
Set the topics
Payment, access, order. The client picks one before writing the text.
-
Add the topic fields
An invoice number is asked only of those who picked payment.
-
Put the form on the site
The link or the code goes on the help page. The request lands in submissions.
CLEAR ANSWERS
FAQ
How is this different from a request on the site?
A site request takes a lead. Here the client describes a problem and picks a topic.
Can different topics have different fields?
Yes. They pick payment and see the invoice number. They pick access and see the login.
Where does the request arrive?
Into the form requests and to email. Topic and text sit on one request.
Is a separate helpdesk needed?
No. A form and the requests list are enough to take support requests.
Can the client attach a file?
Yes. A screenshot or a document is added with a file field in the same form.
Can you reply to the client from the form?
The contact for a reply is on the request. The email to the client is set up in the modules.
SUPPORT
Take requests without a shared inbox
The client picks a topic and writes what happened. The request lands in the submission list.
Sign up and create a form in the builder, without installing software.
Zero credit card required
Instant AI form generation
Production-ready webhooks