Capture enquiries from your website

Give your team a lead to follow up as soon as a website enquiry reaches MyCRM. Connecting your enquiry form can save staff from copying names and contact details between systems, and help keep the enquiry attached to the right adviser.

What this could look like

A prospective client submits your website form. Your integration sends their details to MyCRM and records whether the submission succeeded. The adviser can then pick up the conversation from MyCRM.

This is a useful first integration: one form, one agreed destination and a clear result to check.

Agree how enquiries should be handled

• Choose the adviser. Decide who should receive the enquiries and confirm the adviser details to use.
• Collect enough information to follow up. Include at least a first or last name and either an email address or mobile number.
• Decide who checks failures. If an enquiry cannot be sent, someone needs a way to spot it and arrange follow-up.
• Avoid creating the same lead twice. MyCRM protects against repeated lead submissions using the same email address for the same adviser within 60 seconds. A delayed response does not always mean a submission failed. Your developer should check the outcome before sending it again.

The lead integration creates a contact group, contact and residential deal. You can then track the status of the deal through to completion if you need to.

Getting access

For leads-only access, you may be able to create credentials in MyCRM under Profile Management → API Access Management. If you cannot see that page, ask your head adviser or business owner. For a broader integration, request access through Ask LMG.

Implementation notes for your technical team

You need an application with lead access, OAuth credentials, the API and authentication URLs, and the adviser contact identifier supplied for attribution.

1. Send the website enquiry to your own backend.
2. Obtain or reuse an access token.
3. Create the lead with the assigned adviser in the UserId header.
4. Store the returned identifier and the submission result for reconciliation.

Keep the client secret on your backend. A public form must not call the token endpoint using application credentials.

POST {API_BASE_URL}/jsonapi/leads
Authorization: Bearer {ACCESS_TOKEN}
UserId: {ADVISER_CONTACT_ID}
Accept: application/vnd.api+json
Content-Type: application/vnd.api+json

{
  "data": {
    "type": "leads",
    "attributes": {
      "firstName": "Alex",
      "lastName": "Morgan",
      "email": "alex@example.com",
      "mobile": "+61400000000"
    }
  }
}

The 60-second check applies when an email address is supplied and matches a recently created contact that is still a lead under the same adviser. A rejected repeat returns 400 with the message Email address has recently been assigned to another lead. It is a short-term safeguard, not a general idempotency guarantee: submissions without email, later retries and concurrent requests still need reconciliation. If you enable existing-contact matching, a matching contact and contact group can be reused while a new residential deal is created. Save the returned lead identifier and use the read endpoint to follow its dealStatus and customStatusName.

Names and email have validation and length limits. The mobile field is mobile, not phone. If supplying noteTitle, also supply noteDetails. An externalReference requires externalIntegration; this helps correlate systems but is not an idempotency guarantee. A timeout can occur after creation, so reconcile before repeating a POST. The external-reference walkthrough explains the three integration fields and how to retrieve the resulting deal mapping.

Use Create a lead and Read a lead. To try the requests in Postman, follow the Leads collection setup guide.