> ## Documentation Index
> Fetch the complete documentation index at: https://learn.biq.li/llms.txt
> Use this file to discover all available pages before exploring further.

# Collect responses with native forms

> Build contact, email signup, SMS signup and custom forms with fields, terms and opt-in controls.

In **Content**, choose **Form**, **Contact form**, **Email signup** or **SMS signup**. These use Biqli's native response storage. [Typeform, Laylo and Community SMS](https://learn.biq.li/help/links/biolinks/external-signups.md) use different external-provider flows.

## Build and publish a form

1. Choose the preset closest to your goal, or start a custom form.
2. Set the form title and open its details.
3. Add the fields you need, label them clearly and mark mandatory fields **Required**.
4. Configure choices for selection fields.
5. Optionally add an intro, an outro and custom terms with a valid terms URL.
6. Enable **Mailing list opt-in** only when you intend to collect subscription choices. Include an email or phone field for that purpose.
7. Choose the display and thumbnail, then publish.
8. Submit a test response from the public page and open **View form responses**.

Success means the visitor receives the configured completion view and you can find the accepted response in [Contacts](https://learn.biq.li/help/links/biolinks/contacts.md). The editor cannot collect real responses from an unpublished draft.

## Field types and limits

You can use name, email, phone number, message, country, date of birth, short answer, long answer, single choice, checkboxes, dropdown and date fields. A form supports up to 30 fields, with up to 20 options for applicable choice fields.

Existing fields cannot change type. If the purpose changes, create a new field and review the old one instead of interpreting previous responses as another type. Submitted responses preserve the field labels and choices relevant to that submission.

## Consent and visitor behavior

A response and mailing-list permission are different things. The subscriber flag is recorded when mailing-list opt-in is enabled and the visitor opts in; a supplied email address alone does not imply subscription consent.

Custom terms and mailing-list opt-in also serve different purposes. Supply your own appropriate privacy and consent information and collect only what you need. A contact form is not a private direct-message conversation.

## Edits and errors

Publish field, intro, outro and visibility changes before expecting visitors to receive them. Required-field or choice errors must be corrected before submission. Temporary connection and rate-limit errors should be retried according to the displayed message.

Do not promise an outbound email/SMS campaign merely because you collect an address or number. These presets collect responses; sending a campaign requires its own service and authorization.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.