Forms
Collect the details. Keep the conversation.
Help customers explain what they need with a short native form. Bird brings the submitted answers into the conversation and your service workflow, ready for the next step.
Explore Apple Messages for BusinessWhat can we help you with?
A few details will help us prepare for your visit.
Where would you like to visit?
From a question to a useful request
Give the specialist a head start.
A customer wants a favorite bag repaired. Before the conversation reaches the repair team, a short native form collects the model, the problem and the preferred studio. The specialist opens a request with enough detail to help, and the customer can stay in Messages.
Use forms for service intake, appointment preferences, product recommendations and requests for a quote. Choose a few relevant fields, group related questions and show a review step so customers can check what they are sending.
Read the forms guideA form that fits the conversation.
Design around the decision the answers will support. Bird connects the native form, submitted response and next service step so your team can use the information immediately.
Start with what you already know
Carry the selected product and authorized customer context into the request. Ask for the missing details, such as the fault or preferred location, and explain any information the customer may need to look up.
Choose the right way to answer
Use choices for a defined set of options, pickers for structured values and text where the customer needs to explain something. Group longer intake into focused pages and make the path understandable before the customer starts.
Review before sending
Let customers check the answers and return to the relevant question. Keep the displayed option and its stable meaning together so a translated label or a later template revision does not change the receiving workflow’s interpretation.
Return to a useful next step
Attach the response to the conversation and request, then route it to the team or connected application. Follow a repair intake with an assessment, a quote request with a review, or a visit preference with available appointments.
Build for the request after submission.
Keep the conversation understandable
Tell the customer whether their request was received, needs review or has been completed. If a required detail is missing, ask for that detail with the original context still attached, rather than starting the intake again.
Give sensitive details a clear purpose
Authenticate the customer before asking for account-specific information. Apply access and retention rules to submitted answers, and keep private responses out of unnecessary summaries. Your team should know which information it needs and why.
Forms questions
Should we put a long application into one form?
Can a form branch based on an answer?
How should we handle sensitive customer details?
Is a completed form a completed business request?
Build the connected journey
Put it into practice.
Continue with the documentation, guides and examples for this topic. Resources are in English.
Ask for what the next step needs.
Map the answers, validation and customer confirmation to a specific service request. Review how the submitted result reaches your application.