A useful enquiry workflow connects the first message to a clear next step. Before choosing an AI assistant, CRM connector or custom dashboard, map how an enquiry enters the business and who takes responsibility for it.
This checklist helps you brief a developer for business automation and API integrations. Use it to define a focused first release and the evidence you want to see before accepting the work.
1. Define the enquiry and its destination
List the channels you want to include: a website form, shared inbox, chat or another system. Choose one starting point if each channel has different requirements.
For that channel, write down:
- The fields required to take the next step
- Which system should hold the primary record
- Who should receive a notification
- Who owns follow-up when nobody has responded
- What the visitor should see after submitting
Collect only the information the workflow needs. Keep internal notes separate from customer-facing messages, and define which people can read or change each part of the record.
2. Choose rules-based automation or AI deliberately
A selected service category can map to a named inbox through a fixed rule. Required fields, duplicate detection and follow-up dates can also be handled without a language model.
AI becomes a candidate when the task involves interpreting varied text, such as summarising a long enquiry or suggesting a category from an open-ended description. Treat those suggestions as outputs to test. Include ambiguous messages, incomplete information and examples where the correct response is to ask a person.
If the proposed system can contact customers or change important records, define approval boundaries before building it. OpenAI’s guidance recommends explicit human approval for ambiguous or high-risk agent actions. Read its guardrails and human-review guidance.
A project may combine both approaches. Discuss interpretation-heavy steps through our AI agent and assistant development service, while keeping predictable routing rules explicit.
3. Separate the saved record from the email alert
Ask what happens if a valid enquiry arrives while the email provider is unavailable. A useful design discussion covers when the record is saved, how notification status is recorded and how an operator finds an exception.
Our own website enquiry workflow saves the enquiry before attempting its notification and provides a private management dashboard. That is a concrete implementation example, not evidence of a particular conversion or response-time improvement.
Ask your supplier to demonstrate the difference between “enquiry saved”, “notification accepted” and “message received”. Those states answer different operational questions.
4. Specify duplicates, retries and abuse handling
What happens when a visitor double-clicks, loses connectivity or retries after a timeout? Agree how the system recognises a repeated request and when a genuinely new enquiry should create a new record.
Provider features have boundaries. For example, Resend retains email idempotency keys for 24 hours; that should inform the retry design rather than be treated as indefinite duplicate protection. Read Resend’s idempotency documentation.
For forms using Turnstile, verification must happen on the server. Include expired and reused tokens in the acceptance checks. Read Cloudflare’s server-side validation requirements.
5. Test the whole handoff
Include these scenarios in the project brief:
- A valid submission reaches the intended record and inbox
- Invalid input produces a useful message
- A repeated request behaves as agreed
- Notification failure remains visible to an operator
- An authorised person can search, update and follow up an enquiry
- An unauthorised visitor cannot access private enquiry records
- The form remains usable on a phone
Ask for agreed expected results, test evidence and a clear owner for unresolved issues. Define who maintains integrations when fields, credentials or provider behaviour change.
Bring a workflow, not just a feature list
A strong brief can be short: show the current form, name the connected tools, describe the manual handoffs and identify the exceptions that matter most. Agree ongoing provider costs and maintenance responsibilities alongside the build scope.
Discuss your enquiry automation project with Offchain. We can start from the workflow you have and the next step you want it to support.