Designing inquiry forms for humans and AI agents
A useful inquiry form collects enough information for the business to respond. Its questions should make sense to a person filling them out and to an agent gathering answers in a conversation.
Begin with the first reply your team usually sends. Which missing details force another round of questions? Which information can wait until a real conversation begins?
Give the form one clear purpose
Name the action the customer is taking: request an estimate, ask about a service, or arrange an introductory call. Explain what the business will do with the request.
A form serving several purposes can use a service or topic choice. If the required information differs substantially, separate forms may make the experience clearer.
Ask for observations the customer can provide
Use familiar labels and short help text. Someone reporting a problem may know what they observed without knowing the technical diagnosis. Include an appropriate “not sure” option when uncertainty is normal.
Required fields should be information the team needs to begin. Additional details can be optional. The agent should be able to distinguish both groups without guessing from visual styling alone.
Example: a repair inquiry
| Question | Why it helps |
|---|---|
| What type of appliance needs service? | Identifies the service category. |
| What is the brand? | Helps the business check whether it handles the equipment. |
| What is the model, if you know it? | Adds useful detail without requiring knowledge the customer may lack. |
| What have you noticed? | Collects the customer’s own description. |
| Where is the appliance located? | Establishes the service area. |
| How should we contact you? | Gives the team a route for follow-up. |
Example: an introductory bookkeeping call
| Question | Why it helps |
|---|---|
| What does your business do? | Supplies context for the work. |
| Which accounting software do you use? | Identifies the existing system. |
| What would you like help with? | Separates ongoing work, cleanup, and other requests. |
| Approximately how much activity do you handle? | Gives an initial sense of scope; ranges can be sufficient. |
| When would you like to begin? | Adds timing context. |
| What email or phone number should we use? | Enables the reply. |
Adapt these questions to the actual business. They are examples of an initial inquiry, not a requirement to gather a complete customer file in one form.
Describe the action for an agent
Give the tool a clear purpose and explicit input definitions. Use stable field identifiers and describe the expected values. The agent should know when it has enough information to submit and whether the customer wants the request sent.
Use the same validation rules for human and agent submissions. Errors should identify the problem and make correction possible. A tool should return a useful result after acceptance.
Write an honest confirmation
Tell the sender that the inquiry was received and what happens next. If your team must confirm timing, scope, or price, explain that next step. Avoid wording that turns a request into a commitment the business has not made.
Test delivery as well as submission
Submit a labeled test inquiry, inspect the saved entry, and check the destination your team uses. A successful form response and a delivered CRM notification are separate events.
Review the questions after real use. Remove fields that provide little value and improve the wording where customers repeatedly misunderstand it.