An enquiry arrives on the website. Who owns the next step?
An email to a shared inbox may be sufficient initially. With more properties, consultants and campaigns, context can disappear or replies can overlap. A CRM integration should make each enquiry traceable and assign clear responsibility, including when the connection fails.
Design the record before connecting systems
Define the fields the team needs: contact details, property reference, message, permitted source information and submission time. Decide whether an enquiry creates a person, an opportunity or both. One person may be interested in several properties; merging every request into one text field can erase that distinction and hinder follow-up.
Agree on routing rules
Assignment may depend on the property, area or a team queue. Define a fallback when the owner is unavailable. Check properties without an assigned consultant and general seller enquiries. People using the process should understand it, including when manual intervention is needed.
- Who receives the enquiry and in which system.
- How an owner is selected.
- How a retry differs from a new interest.
- Who receives integration failure alerts.
- How unanswered enquiries are monitored.
Plan retries and failures
An external service may become unavailable after the form accepts a request. Preserve the enquiry and retry without creating duplicate opportunities. Keep operational references and delivery states. A visitor's success message must not hide a queue stalled for days; someone needs to observe it and reprocess failed work.
Test with the sales team
Use test enquiries for an active property, unavailable property, repeated contact and a request without a reference. Check records, assignment and replies. Include the person who will work in the CRM: a technically populated field may sit on a screen nobody reads. Document the final flow, permissions and ownership of future changes.
Frequently asked questions
Can any CRM accept the form?
That depends on its API, plan, connectors and permissions. Start with the chosen provider's documentation and a limited integration test.
Is forwarding email to the CRM enough?
It may suit a simple flow. Before depending on it, check how it preserves fields, avoids duplicates, assigns ownership and reports failures.
A note from ArqWeb
This guide organises checks and decisions for a common situation. Implementation depends on the website, access and systems involved. We can assess your situation if you need help applying these steps.
Let's look at your situation.
Tell us what you need and what you have already. We will reply with next steps and a proposal suited to the work.
Discuss my requirements