Use a rule when the input is structured and the answer should be predictable. Consider AI only when useful meaning must be extracted from messy language, and keep the output as a reviewable proposal. Many intake workflows need both: deterministic controls around a narrow AI step.
This is a proposed decision method for service businesses, not a vendor recommendation. We did not test a live intake system or customer data for this article. Research and drafting were AI-assisted; see how Inquory uses AI.
Start with the smallest reliable mechanism
A required postal code, service-area lookup, duplicate event check, consent checkbox, and “do not book without approval” control are usually explicit rules. They have defined inputs and outcomes that a person can inspect. A free-text message such as “the upstairs unit is making a grinding sound after yesterday's visit” may benefit from AI-assisted extraction into proposed fields.
Do not ask AI to replace a rule merely because it can produce the same answer in a demo. Ask what happens when the input is missing, contradictory, misspelled, multilingual, or crafted to manipulate the workflow.
| Intake need | Prefer a rule when | Consider AI when |
|---|---|---|
| Required fields | Presence and format are known | A reviewer needs proposed facts extracted from free text |
| Service area | Approved postal codes or zones determine routing | The location is described indirectly and needs clarification |
| Duplicate handling | Stable event IDs and record keys exist | AI should not be the uniqueness control |
| Urgency | An approved phrase or category triggers a fixed queue | Ambiguous language may be flagged for human review, without making the decision |
| Customer reply | A template covers the approved response | A draft may help after staff confirms facts and authority |
Give AI a proposal-shaped job
Define an output schema with allowed values and an “unknown” state. Require a source passage for each extracted fact. Reject invented values. Keep pricing, eligibility, diagnosis, promises, rejection, and appointment changes with approved rules and people unless a separate reviewed process authorizes them.
NIST's Generative AI Profile describes confabulation as confidently presented false or erroneous content and recommends risk management across the AI lifecycle. That supports a simple design choice: treat generated fields as claims to verify, not as facts merely because they are fluent.
The lead qualification guardrails provide a worksheet for separating proposed fields from human decisions. If the proposal later writes to a CRM, run the CRM handoff checklist before enabling real records.
Test the boundary, not only the happy path
Prepare fictional cases with missing details, negation, conflicting statements, repeated events, unsupported requests, and text that tells the system to ignore its instructions. Write the expected rule result, AI proposal, reviewer action, and prohibited action before testing.
Count every attempted case. Track unsupported fields, missed required facts, wrong routing proposals, review time, correction time, and any forbidden action. Compare the combined workflow with a form or staff template. A more elaborate intake path has not earned its place if it creates more review work without a useful improvement.
The Office of the Privacy Commissioner of Canada's generative-AI principles advise using synthetic or de-identified data when personal information is unnecessary and considering whether a more privacy-protective technology can achieve the purpose. Begin with fictional inquiries. Before real messages enter a provider, the business must establish its own authority, purpose, access, retention, and vendor controls.
Use a clear stop rule
Stop if the workflow sends a message, changes a booking, rejects a lead, or writes an unapproved fact outside its boundary. Stop if reviewers cannot trace a proposed field to the inquiry, or if an unknown outcome is retried without checking the destination. Return intake to the manual process while the cause is investigated.
Choose rules for stable decisions, AI for bounded interpretation, and people for accountability. If the simplest reliable workflow is a better form plus a queue, use it.