Home

Website and CRM integrations: who owns a missing lead?

Draw the boundary between the form, the queue or API and the CRM record. Give each handoff a responsible team and a reference that both sides can locate without sharing personal details.

API receipt

In a test environment, simulate a timeout after the receiver has accepted a request. Send it again with the same reference. One form submission should not become two sales records simply because the sender missed the acknowledgement.

Submission ID → API receipt → CRM record
Submission ID → API receipt → CRM record

Did the CRM create one record or two?

Include a rejected field value in acceptance tests. The owner needs a visible failure queue or report; silently dropping a rejected request leaves sales with no way to recover it.

Illustrative record: Request reference (REQ-42 × 1) / Created CRM records (CRM-18 + CRM-19)
A matching email address is insufficient for reconciliation because the same buyer can submit twice. Use the agreed request identifier to distinguish a retry from a genuinely new enquiry.

Acceptance evidence · Created CRM records

Agree on duplicate handling, retry limits and who reviews unresolved requests. Reconcile labelled tests at both ends after changes to field mappings, credentials or CRM routing.

Trace a synthetic submission from your website to the CRM with DigiWeb

Let’s start with
what you need.

Tell us about your project or the website issue you need to resolve. DigiWeb will work through the next steps with you.

info@digiweb.com.vn0902 604 802Nguyễn Đức Thái · Founder DigiWeb