The first voice AI pilot asks for many HubSpot fields because they might be useful someday. Callers spend longer answering questions, and the office still lacks the one field needed to route the enquiry.
Choose fields from the next business action backward. Collecting more information is not a substitute for deciding how the request will be used.
Begin with one operational outcome
For a fictional service-request pilot, decide which staff member receives the request and what they need to act. A callback number, location, service category, and clear issue description may matter more than a broad lead profile.
Do not treat this list as universal. Each business must approve its own minimum information and handling rules.
| Field purpose | Design question |
|---|---|
| Identity | What evidence is needed for the permitted record relationship? |
| Contact | How can the office perform the agreed follow-up? |
| Routing | Which value sends the request to the right team? |
| Outcome | What verified state should be recorded? |
| Uncertainty | What remains missing or unconfirmed? |
Distinguish required, optional, and inferred values
Required fields should have a clear reason and a useful missing-data path. Optional fields should not prevent a valid core request from being saved.
Keep model-inferred classifications separate from caller-confirmed facts and backend-verified outcomes. A guessed service category may be useful for review, but it should not masquerade as a customer instruction.
HubSpot's developer documentation is the reference for the supported property types and account-specific constraints. Verify the actual configuration before fixing the integration contract.
Define corrections and unknowns explicitly
Decide how an absent value differs from a refusal, an invalid value, and an uncertain transcription. Empty strings should not silently become meaningful business decisions.
For numbers, dates, and addresses, use appropriate validation and caller clarification. Do not generate a plausible placeholder merely because the destination field is mandatory.
The missing-consent guide illustrates why an unknown needs its own handling policy.
Test whether the office can use the saved record
Run fictional calls with a complete request, one missing critical value, a correction, an uncertain classification, and a caller who declines optional questions.
Ask staff to route and follow up using the resulting record alone. If they need to replay the entire conversation for routine intake, revise the field model.
Start narrow. Additional fields can be added when actual review demonstrates their value, with a plan for older records that lack them.
Pilot-field questions
Should every CRM property become a voice question?
No. Select the information required by the agreed workflow.
Can the model fill required gaps with guesses?
No. Preserve missing or uncertain information and apply the fallback.
What should the handover contain?
Document field purpose, type, source, validation, and correction rules in the pilot contract.