Map the enquiry and its owner
Define the source of an enquiry, the information needed in the CRM and who receives the next task. A useful flow keeps relevant context with the customer record. Agree what counts as a new customer, an existing contact and a new request from the same organisation.
Avoid duplicate or conflicting records
Choose stable identifiers and field ownership before creating or changing records. Assess what the named CRM permits, including access limits. Missing details and ambiguous matches need a visible exception path. Integration does not authorise unsolicited outreach or wider use of customer data beyond the agreed purpose.
Bring a real follow-up process
Share the CRM name, source applications, safe example enquiries and the team’s current assignment rules. Include duplicate cases and required permissions. We assess feasibility, map the exchange and verify record creation or updates and failure handling; additional campaigns or sales automation are separately scoped.