Formulários que coletam respostas, contatos e pagamentos.

Forms that collect answers, leads and money.

• Build the form for the thing you actually need.
• A contact form.
• A lead form.
• An application.
• A booking.
• A survey.
• An order.
• A payment.
• Start with one of 50 templates.
• Choose the fields.
• Publish it.
• Then send every submission where it needs to go.
• Create your account
• See the templates

The problem

Most forms are built for the person making them.

• They open a blank form builder.
• Add a name field.
• Add an email field.
• Add a phone number.
• Add another question.
• Then another.
• Then another.
• Eventually, the form asks eleven questions when it only needed four.
• People stop filling it.
• Or the wrong information comes in.
• Or someone has to manually move every submission into another tool.
• Or the form collects an order but sends the customer somewhere else to pay.
• The form was built.
• But the workflow around it was not.
• Klairova Forms starts with a different question:
• What are you trying to get from the person filling this in?

50 templates

You do not need to invent the form every time.

Klairova Forms has 50 templates across the things people actually use forms for.

Contact

For people trying to reach you.

Lead generation

For turning interest into a contact.

Registration and signup

For getting people registered.

Survey and feedback

For finding out what people think.

Application

For collecting the information needed to decide.

Order and payment

For taking an order and the money for it.

Booking and RSVP

For registrations, appointments and events.

Quiz

For testing knowledge or collecting structured answers.

Support

For getting a problem to the right place.

Hr and operations

For internal processes.

Real estate

For property enquiries and related workflows.

Healthcare and education

• For forms built around those specific needs.
• Each template already has a starting structure.
• You change what you need.
• Then publish it.

23 field types

The field matters.

A form asking for an email address should have an email field. A form asking for a date should have a date field. A form asking someone to rate something should not make them type a number into a text box.

Klairova Forms gives you 23 field types.

Payment

Take payment directly through the form.

Rating

Collect structured ratings instead of free text.

Range

Let people select a value within a defined range.

Nps

Measure Net Promoter Score properly.

File upload

Collect documents, images, portfolios and other files.

Consent

Ask for permission with a separate, unticked consent field.

Date

Collect a date.

Time

Collect a time.

Datetime

Collect both.

Address

Collect an address.

Phone

Collect and validate a phone number.

Company

Collect company information.

Email

Collect and validate an email address.

Name

Collect a person's name.

URL

Collect a website or other URL.

Heading

Break a longer form into meaningful sections.

Paragraph

Add explanation where the person filling out the form needs it.

Select

Let someone choose from a list.

Radio

Choose one option.

Checkbox

Choose one or more options.

Number

Collect a number.

Text

Collect a short written answer.

Textarea

Collect a longer written response.

Payment built into the form

Sometimes the form is not just collecting information.

• It is the checkout.
• An order form.
• A paid application.
• A deposit.
• A registration.

A service request that needs payment. With a payment field, the person can submit their information and pay through the same form.

• No:
• "Fill this out."
• "Now click this other link."
• "Now pay over there."
• One form.
• One submission.
• One payment.
• ASK LESS. GET BETTER ANSWERS.

A form that asks eleven questions usually gets fewer submissions than one that asks four. That is why the templates are not just visual starting points. They are starting points for the questions themselves. A quote request can ask for a budget band. A demo request can ask for company size. A lead magnet can ask for an email and consent.

An application can ask for the information you actually need to make a decision. Start with the form that already understands the job. Then remove anything you don't need.

Qualify before the conversation

Sometimes the form should do some of the filtering for you.

• A quote request can ask:
• What service do you need?
• What is your budget?
• When do you need it?

• Now the person who reaches your inbox has already given you useful context.
• You are not starting the conversation with:
• "So, what exactly are you looking for?"
• The form has already asked.

See what the form is doing

A submission count alone doesn't tell you much.

• You also need to know how many people saw the form.
• Klairova Forms tracks:
• Views.
• Submissions.
• Completion rate.
• That difference matters.

A form with 1,840 views and 212 submissions tells you something very different from a form with 1,840 views and 40 submissions. The problem may not be your traffic. It may be your form.

Where submissions go

The form is only useful if the answers reach the people or systems that need them.

Every submission is stored against the form. From there, it can move into Klairova or into tools you already use.

Into Outpost

Contacts collected through a form can flow into Outpost.

• They can also be tagged when they submit.
• A lead magnet can therefore do this:
• Collect the email.
• Capture consent.
• Create the contact.
• Apply the tag.
• Build the segmented list.
• Without somebody moving the data manually afterwards.

Into your existing tools

You can also connect forms to tools you already use.

• Mailchimp.
• ConvertKit.
• MailerLite.
• Brevo.
• ActiveCampaign.
• HubSpot.
• Google Sheets.
• Discord.
• Telegram.

A submission can land in a spreadsheet and notify a team channel at the same time.

Publish it where people already are

Your form can have its own address.

• Or it can live inside something else.
• Put it on a landing page.
• Embed it on your website.
• Send the direct form link.
• The form does not need to dictate where the conversation starts.

Who it is for

Brands

• Capture leads.
• Request quotes.
• Book demos.
• Collect applications.
• Take support requests.
• Run internal operations.

Creators

• Collect enquiries.
• Receive brand collaboration requests.
• Run audience surveys.
• Build waitlists.
• Take paid orders.

Publishers

• Collect advertiser enquiries.
• Run reader surveys.
• Receive submissions.
• Register people for events.

Anyone who needs an answer from somebody else can use a form.

How it works

From template to published form

Pick the template

• Start with the form closest to what you are trying to find out.
• 50 templates.
• Multiple use cases.
• One starting point.

Edit the fields

• Add what you need.
• Remove what you don't.
• Reorder the questions.

Do not ask for information you will never use.

Choose the right field types

• Email for email.
• Phone for phone.
• Date for date.
• Rating for rating.
• Payment for payment.

Use the field that matches the answer you need.

Connect the submissions

Send them into Outpost or connect the form to the tools your team already uses.

Add payment if needed

If the form needs to collect money, add the payment field.

Publish it

Give the form its own address or put it inside your landing page or website.

Watch the numbers

Compare views with submissions. The gap tells you whether people are actually completing the form.

Three ways it gets used

Qualifying enquiries before they reach you

• A service business wants people to request a quote.
• Instead of asking:
• "Tell us what you need."
• They create a form that asks:
• What service do you need?
• What is your budget?
• When do you need it?
• What is the project?

Now the team receives enquiries with enough information to decide what happens next. The form does some of the qualification before the conversation starts.

A form that takes the money

• A creator is selling a paid product.
• Previously:
• Someone fills an enquiry form.
• The creator responds.
• An invoice gets sent.
• The customer asks how to pay.
• The payment is made.
• The order is confirmed.

With a payment field, the form can collect the order information and payment in the same flow.

• One submission.
• One payment.
• Less chasing.

Asking an audience properly

• A creator wants to know what their audience thinks about a new product idea.
• They could ask:
• "What do you think?"
• And receive hundreds of paragraphs.
• Instead, they use the appropriate field types.
• Rating.
• NPS.
• Select.
• Checkbox.
• A few targeted questions.

Now the answers can be compared instead of becoming a pile of free text nobody reads twice.

Forms + Outpost

A form collects the answer.

• Outpost gives that answer somewhere to go.
• When a contact submits a form, they can flow into Outpost and receive a tag.
• So the form does not just collect information.
• It can start the contact workflow.
• [Explore Outpost]

Forms + Landing Pages

Sometimes the form is enough.

• Sometimes someone needs to understand the offer before they fill it in.
• Put the form inside a Landing Page.
• Explain the offer.
• Build the case.
• Then ask for the response.
• [Explore Landing Pages]

Forms + Website

If your website already gets the traffic, put the form there.

• Embed the form where the action should happen.
• The website explains.
• The form collects.
• [Explore Website]

Forms + Wallet

When a form needs to take payment, the payment field lets the transaction happen inside the form. The money flows into your Klairova Wallet. The form collects the information. The Wallet holds the money. [Explore Wallet]

Forms + Circuit

Some submissions should not end up in an inbox.

• They should trigger work.
• An internal request.
• An operational process.
• A workflow.

Circuit can turn the information collected through a form into something your team can act on.

[Explore Circuit]

Klairova Forms vs a blank form builder

Klairova Forms vs using a separate form + checkout

Things to know

EVERY FIELD COSTS YOU SUBMISSIONS.

• Ask for the minimum information you need to act.
• You can always ask for more later.
• WATCH COMPLETION RATE.
• A form seen 2,000 times and completed 40 times has a problem.
• Views alone don't tell you that.
• CONSENT SHOULD BE ITS OWN FIELD.
• Do not hide consent inside the submit button.
• Use a separate, unticked consent field.
• USE THE RIGHT FIELD.
• An email field validates an email.
• A text box labelled "Email" does not.
• A rating field gives you structured ratings.
• A text box asking someone to rate you does not.
• A form is easier to complete when every question behaves the way people expect.
• A FORM IS NOT A LANDING PAGE.

If someone needs convincing before they fill out the form, give them the explanation first. Put the form inside a landing page. THE PAYMENT FIELD CHANGES THE JOB. Once a form can take payment, it is no longer just collecting information. It can become the order. THE FORM SHOULD SERVE THE WORKFLOW. Do not build a form because forms are easy to build.

Build it because you know what should happen after someone submits it.

FAQ

What is Klairova Forms?

Klairova Forms is a form builder for collecting information, leads, applications, bookings, survey responses, orders and payments.

How many templates are available?

There are 50 templates across different form use cases.

What types of forms can I create?

Contact forms, lead generation forms, registration and signup forms, surveys, feedback forms, applications, order and payment forms, bookings, RSVPs, quizzes, support forms, HR and operations forms, real estate forms, healthcare and education forms and more.

How many field types are available?

Klairova Forms has 23 field types.

Can a form take payment?

Yes. The payment field lets you collect payment directly through the form.

Where does the money go?

Payment collected through the form flows into your Klairova Wallet.

Can I collect files?

Yes. The file upload field lets people submit documents, images, portfolios and other files.

Can I collect consent?

Yes. There is a dedicated consent field that is separate and unticked by default.

Can I see how many people viewed my form?

Yes. Klairova Forms tracks views and submissions.

Can I see the completion rate?

Yes. Views and submissions allow you to see how the form is performing and where people are dropping off.

Where do form submissions go?

Submissions are stored against the form and can flow into Outpost or connected external tools.

Which external tools can I connect?

Supported connections include Mailchimp, ConvertKit, MailerLite, Brevo, ActiveCampaign, HubSpot, Google Sheets, Discord and Telegram.

Can a submission create a contact?

Yes. Contacts collected through forms can flow into Outpost.

Can I tag contacts when they submit a form?

Yes. A form can apply a tag when someone submits it.

Can I embed a form on my Website?

Yes. You can publish a form on its own address or embed it inside a landing page or website.

Do I have to use a template?

No. The templates are starting points. You can customise the form to your needs.

Why use a template?

• Because the templates are already structured around a particular job.
• A quote request already knows it needs information such as a budget.
• A demo request can ask for company size.
• A lead magnet can handle the email and consent.

You start with a form that has already been thought through rather than an empty builder.

Can I add and remove fields?

Yes. You can add, remove and reorder fields.

Can I use different field types?

Yes. Use the field type appropriate to the information you are collecting.

Can I create a survey?

Yes. There are survey and feedback templates, along with rating, range, NPS and other field types.

Can I create an order form?

Yes. Use an order and payment template and add the payment field.

Can I create a booking form?

Yes. There are booking and RSVP templates, along with date, time and datetime fields.

Can I create an application form?

Yes. There are application templates and fields such as file upload, consent and structured information fields.

Can I use Klairova Forms for lead generation?

Yes. There are dedicated lead-generation templates, and submissions can flow into Outpost.

Can I use a form with a landing page?

Yes. A form can be embedded inside a landing page when the offer needs explanation before someone submits.

Can I use a form on my Website?

Yes. You can embed it on your website.

Can a form send submissions to multiple places?

Yes. A submission can be connected to Klairova and external tools, depending on the connections configured for the form.

Can I use forms for internal operations?

Yes. There are HR and operations templates, and forms can also feed operational workflows through connected Klairova features.

What is the difference between a form and a landing page?

A form collects information or payment. A landing page explains an offer and can contain a form.

Can I use forms without using Outpost?

Yes. Outpost is where contacts collected through forms can be managed, but forms can also connect to other supported tools.

Does Klairova Forms replace my existing form builder?

It can, particularly if you need forms alongside the rest of your Klairova workflow. It combines templates, field types, payments, contact capture, integrations and publishing in one place.