A contact record can exist in your CRM while nobody is responsible for replying. The form succeeds, the contact appears, and the sales inbox stays quiet because the assignment rule found no eligible owner.
A useful acceptance test follows the enquiry from submission to the person or queue that can act on it. Start with one form and one fallback queue. Agree who monitors that queue and how long an item can wait before it gets escalated.
Give every enquiry a visible outcome
Store a submission ID and keep it separate from the CRM contact ID. Two requests from the same contact can be legitimate enquiries. A retry of the same submission should preserve the original assignment and avoid a second notification.
Record the assigned owner or fallback queue, the routing reason, and the time the enquiry entered that state. Record when a person accepts the enquiry. For a missing match, an inactive owner, or incomplete routing fields, send the enquiry to the monitored queue with the reason visible. If no one accepts it within the agreed window, escalate it once to the duty owner.
Test the cases your inbox can't explain
These are illustrative acceptance tests. Replace the example rules and response window with ones your team actually uses.
| Submit or simulate | Verify |
|---|---|
| A valid enquiry with a matching, active owner | The owner sees the enquiry and can accept it. The CRM shows when it was assigned. |
| An enquiry with no matching owner | The monitored queue receives it with the reason. An unclaimed enquiry triggers one escalation after the agreed window. |
| A repeat delivery of the same submission | The original enquiry and assignment remain. The recipient gets one notification for that assignment. |
| A new submission from an existing contact | The existing contact is reused and the new enquiry is visible as separate work. |
| The CRM write succeeds but the notification fails | The assignment stays visible. Retrying the notification uses the same assignment and doesn't create another enquiry. |
Run these against a test form and CRM workspace before switching on live routing. Ask the person who monitors the fallback queue to run the second case themselves. They should be able to find, accept, and reassign the enquiry using their normal permissions.
If you're scoping this work, bring one recent example of an enquiry that reached the CRM but was slow to reach a person. Trace the submission, assignment and acknowledgement timestamps with the team. That shows which handoff needs attention and gives you a concrete test for the fix.
StackEndBox can help scope that first handoff through its CRM development and workflow integration service.
