ShapedSI Journal · Applied AI
CRM and enquiry handoffs: make the next action visible
A form or CRM connection is useful when the next person knows what to do. Begin with the customer’s request, the information the team needs and the point where somebody takes responsibility. The integration should preserve that context and make unfinished work visible, without collecting details that do not help the reply.
In this guide
01
Define a useful enquiry
Write down the minimum information needed to begin a response. That often includes a reply method, the requested service and a short description of the situation. Explain why an unusual field is needed, and let a person describe an exception in their own words. Avoid turning the first enquiry into an unnecessarily long application.
Check what the visitor sees after submission. The message should accurately explain whether the request was received and what the next step is. If the form cannot complete, give the visitor useful feedback and an appropriate alternative contact route. A reassuring message should reflect an actual completed step.
02
Choose a record and an owner
Decide where the request belongs and which information should travel with it. Keep the source page or enquiry context where it is useful to the authorised team. Use the existing customer record where appropriate, and define how a duplicate is recognised. A new record for every retry can make the queue harder to understand.
Assign an owner or a clear routing rule. The team should be able to see which requests are unassigned, waiting for information or ready for a reply. Decide what happens if the intended person is away. A shared inbox without responsibility is not the same as a managed handoff.
03
Use states that describe the work
Choose a small set of statuses with an agreed meaning. Received, under review, waiting for information and completed may be enough for a first workflow. Explain what event moves the record and who may make that change. Do not mark a request completed merely because an automatic acknowledgement was sent.
If AI proposes a category or summary, keep it separate from the customer’s original message and allow the reviewer to correct it. A suggestion can help with preparation while the record’s owner remains responsible for the next action. Avoid hiding important uncertainty inside a confidently worded summary.
04
Test delivery and recovery
Test the form, record creation, notification and follow-up as a complete path. Include a missing field, a duplicate request and an unavailable integration. Decide whether a failed step retries or enters a queue, and give that queue a reviewer. A visible exception is easier to resolve than a request that silently disappears.
Review a small set of enquiries after launch. Ask whether the team can respond with the information provided and whether statuses reflect the actual work. Update the fields and routing when services or responsibilities change. Keep the process simple enough that staff can explain where a request is and who will handle it.
Bring this to the conversation
A working brief.
- Necessary fields with clear labels
- Accurate submission feedback
- A destination record and duplicate rule
- An owner and understandable states
- A monitored exception path
A few useful questions.
Should the form automatically create a sales opportunity?
That depends on your process. An enquiry may need review before it is appropriate to treat it as a qualified opportunity.
Where does AI help in this workflow?
It can propose a summary or category, provided the original request remains available and a person can review the suggestion.
Original sources
Sources and further reading.
HubSpot documents lifecycle stages as a way to understand where contacts are in a process and support handoffs. W3C’s forms guidance covers labels and feedback that help people submit a request.
Shape the next step