# Design and handle an Apple Messages form

Create a focused native form, verify its branches and connect submitted answers to the customer’s service request.

## Prerequisites

Prepare a supported test device, the form’s service purpose and a workflow that receives and validates the submitted answers.

## 1. Define the minimum questions

Choose one focused task such as visit preferences or request triage. Use the information already available through authorized context and explain why unfamiliar or sensitive fields are needed.

Ask Apple’s required clarifying yes/no question before collecting personal information needed for the task. Use the appropriate Quick Reply and [policy requirements](https://register.apple.com/resources/messages/messaging-documentation/policies).

## 2. Create the pages and branches

Choose suitable selection, input and date controls. Give page and answer references stable meaning. Route each supported branch to a clear completion and include a summary where it helps the customer review.

## 3. Test the device flow

Follow every meaningful branch on a supported device. Test optional answers, longer text, interruption and re-entry. Keep the form short enough that restarting does not impose unnecessary effort.

## 4. Validate the returned answers

Associate the response with the business, conversation and original request. Keep unanswered fields distinct from an explicit choice. Apply data handling and access rules in the receiving systems.

## 5. Confirm the business result

Submit the validated request to the system that owns the case, booking or other action. Tell the customer whether the request completed, needs another step or requires help.

## Verify a complete intake

Use a repair request as a bounded test. Select the product, describe the problem, choose a location and review the answers before submitting. Confirm that the service team receives the selected values with the original conversation and request. The resulting case should be ready for assessment.

| Test case                                       | Action                                                                      | Expected result                                                                  |
| ----------------------------------------------- | --------------------------------------------------------------------------- | -------------------------------------------------------------------------------- |
| The customer changes an answer during review    | Return to the relevant question and preserve the other answers.             | The submitted response contains the revised choice.                              |
| An optional question is unanswered              | Preserve the distinction between absent information and an explicit answer. | The receiving workflow uses the intended default or requests the missing detail. |
| The receiving service rejects a selected option | Keep the request context and explain which choice must change.              | The customer can supply a valid answer without repeating unrelated questions.    |

## Troubleshooting

If a branch does not finish, inspect page references and completion settings. If an interrupted form loses progress, provide a clear retry or another supported task path. A private-answer marker does not replace storage and access controls.

## Next steps

- [Explore the related Apple Messages capability](/products/apple-messages/forms).
- [Find Apple Messages guides and answers](/products/apple-messages/resources).
- [Prepare your first complete conversation](/products/apple-messages/getting-started).

## Related resources

- [What is Apple Messages for Business?](/explained/apple-messages/what-is-apple-messages-for-business) (answer)
- [Apple Messages for Business](/products/apple-messages) (product)
- [Integrate an Apple Messages customer journey](/docs/guides/apple-messages/api) (docs)

[Get an implementation brief](/learn/workspace?topic=apple-messages)