> ## Documentation Index > Fetch the complete documentation index at: https://docs.asapp.com/llms.txt > Use this file to discover all available pages before exploring further. # Dynamic Forms > Collect customer information in Apple Messages for Business using multi-page forms that route to the next question based on each answer. Dynamic Forms are multi-page forms in Apple Messages for Business (AMB) that decide the next question based on the answer a customer just gave. Each page presents one question, and the response determines which page the customer sees next. Use Dynamic Forms when the information you need depends on earlier answers, such as an intake questionnaire where a claim type changes the remaining questions. For fixed sets of fields that every customer answers, standard AMB Form Messages remain the simpler choice. Dynamic Forms require configuration by your ASAPP account team. Contact your account team to enable the feature for your company. ## How it works A Dynamic Form is a set of sequential pages joined by transition rules. When a customer submits a page, ASAPP evaluates the rules for that page and serves the next page in real time. * **Question-to-question transitions:** each page declares which page follows it. A page can route to different destinations depending on the response. * **Conditional logic:** transition rules use if/then conditions evaluated against the answer on the current page and answers collected earlier in the form. * **Real-time progression:** the path through the form is resolved as the customer answers, so no page is sent until its condition is met. * **Default paths:** each branching page needs a fallback destination so that any response that matches no condition still advances the form. Because pages are served one at a time, a customer never sees questions that their earlier answers made irrelevant. ## Question types available on a page Each page holds a single question or a small set of related inputs. Configure the input type per question: * **Date & time** : Allows customers to select both a date and a time. * **Numeric** : A numeric input field that accepts only numbers. Can be used for phone numbers, zip codes, or any other numeric input. * **Selector** : A question that allows the customer to choose from a predefined set of options. * **Text** : A free text input field that accepts any characters. Can be used for names, addresses, or any other textual input. * **Paragraph** : A multi-line text input field that allows customers to provide longer responses. Selector questions are the most reliable basis for conditional logic, because the set of possible answers is known when you write the rule. Free text and numeric answers can also drive conditions, using comparisons rather than exact option matching. ## Build a form in AI Console The Form Builder in AI Console handles form creation, question configuration, and the logic that connects pages.

To create a secure form, follow these steps:

  1. Navigate to the ASAPP Messaging section in the AI Console.
  2. Navigate to the Library section and click Forms tab.
  3. Click Add Form to create a new form.
  4. Fill in the required details for the form, such as the Display Name, Description, Unique Id. For the Form Type, select Universal View.
  5. Click Create View to create the form view.

Optionally, you can enable if you want to display a title and summary for the form.

To enable the title, toggle the Title switch on and enter a title in the text box. Similarly, to enable the summary, toggle the Show Summary switch.

The splash text is the introductory text that appears at the beginning of the form. It provides context and instructions to the customer before they start filling out the form.

To define the splash text, enter the Header, Splash Text, Button Title, and Image Identifier in the respective fields.

Add one page per question. To add a new page:

  1. Click Add under Item.
  2. Select a [question type](#question-types-available-on-a-page) from the available options.
  3. Configure the question text, labels, ID, and any additional settings for the question.
  4. Repeat the above steps for each question/page you want to add to the form.

Keep question text short, because AMB renders each page in the Messages interface.

 For each page, define the conditions that determine the next page. The builder displays these transitions visually, so you can trace every path a customer can take through the form.

To define transition rules, select the page you want to configure, navigate to the Routing tab, and select a destination page under Route to or Route from for each possible answer.

A branching page with no default destination can leave a customer with no next page. Confirm that every page has a reachable destination for all possible responses.

After configuring all pages, questions, and transition rules, click the Save button on the top right to save the form.

For any changes made to the form, you can choose to save the changes as a part of the same version or a new version.

 ## Add a form to a virtual agent flow Dynamic Forms are embedded in [flows](/agent-desk/virtual-agent/flows "Flows") rather than triggered on their own. Add the form at the point in the conversation where you need the information, and the virtual agent sends it to the customer and waits for submission before continuing. Answers collected by the form are available to later nodes in the flow, so you can use them for branching, API calls, or agent context on handoff. ## Manage draft and live versions Forms have two states, which lets you edit a form without changing what customers currently receive: | State | Behavior | | ----- | --------------------------------------------------------------------------------------- | | Draft | Editable. Not served to customers. Multiple rounds of edits and validation happen here. | | Live | Served to customers by any flow that references the form. Read-only. | To change a live form, edit its draft, validate, then promote the draft. Promotion replaces the live version for every flow that references the form, so review which flows use a form before promoting. ## Channel and adapter support Dynamic Forms are delivered in Apple Messages for Business and are compatible with custom chat adapters, so the same form can be reached through a brand's own chat integration. Support constraints follow existing AMB Form Messages behavior, including the operating system versions that render form messages natively and the field configurations that cause a form to fall back to a web form. Confirm the current constraints with your ASAPP account team before designing a long or complex form. For channel setup, see the [Apple Messages for Business](/agent-desk/integrations/apple-messages-for-business "Apple Messages for Business") integration guide. ## Next steps Learn how to integrate Apple Messages for Business with your virtual agent to enable dynamic forms. Learn how to add a form to a virtual agent flow, so the agent can collect information from customers during the conversation.