As part of the MQL nurture, the following will need to be cloned and created for each project:

1. Request a Callback Form.

2. Landing Page.

3. CTAs & HubDB

4. Email.

5. Workflow.

6. Campaign.

The request a callback form needs to include the following fields as a minimum.

• First Name *
• Phone Number *
• When should we call you? *
• What time of day should we call you? *

Hidden Fields:

• Project Estate ID.
• Sync Lifecycle Stage - MQL.
• GA4 Client ID.

* All fields should be required.

Nice to haves:

We have also introduced standard rich text at the start of the form advising the working times of the sales team. It is at your discretion if you want to use this.

You can use the above information to create your own form, or alternatively, you can clone this form.

Please note: Request a call back information is NOT synced with CRM. 

This means, you will need to include your ESM's sales email with the 'Send Submission Notifications to' property under Options.

The Sales Team will need to be informed as to what this email means.

The landing page created is very simple, with the form at the top and then a small  speal about your sales agent.

It is at the marketer's discretion how they would like this created.

Ideally, these pages should be created in HubSpot. If your project does not have a template for landing pages in HubSpot, then you will have to use Kentico but the design may differ.

Two examples of landing pages below.

• Ariella Private Estate Request a Callback
• Atwater Rockingham Request a Callback

Similar to the lead nurture program, the MQL nurtures require a HubDB and CTA Directory. 

To create a new Directory, first navigate to HubDB and clone the PROJECT_CTA_Directory_MQL Nurtures.

Populate the details accordingly.

CTA Button: 

In order to create a CTA - navigate to Marketing > CTAs.

You have the option to clone one of the existing CTA buttons and change the styling (e.g. colour and font) or create your own from scratch.

If you want to create it from scratch, select the 'Embedded Buton' options.

Navigate between the 'Content' and 'Styles' tab to amend the CTA to your project brand and preferences.

Publish CTA.

CTA Naming Example: ARIE_CTA_Request-A-Callback

Be sure to copy the unique CTA code into the HubDB table once published.

Design Manager - CTA Directory:

The final step before you can start adding these CTAs to email is to clone the Module in the design manager and link it with the HubDB table you just created. 

To do this, navigate to Content > Design Manager and search for the PROJECT_Email cta hubdb directory_MQL Nurture module.

Clone and rename for your project.

Link the existing HubDB to this new module you created. On the RHS navigation bar - under 'Fields' - edit the CTA (HubDB Row)

Under Content Options > HubDB Table, change the linked table to be the new table you just created.

Publish changes in the top RHS.

Create an automated email with your project's branding.

The email design is quite simple. 

Copy one of the below two designs for your projects.

• Ariella Private Estate
• Atwater Rockingham

Clone this workflow for your project and update the deal enrolment triggers - mainly the project estate ID.

Then update the 'Send Email' branch to include the email that you have created.

Finally, update the SMS information to be tailored for your project.

Be sure to update the:

• Sender ID (to be your chosen state).
• Workflow ID.
• Text Message Content.
• Owner.

When turning the workflow on, DO NOT enrol existing enquiries and only enrol contacts who meet the criteria AFTER the workflow is turned on.

If you are concerned about turning the workflow on - please raise a ticket and the MarTech team will organise this for you.

Once the above is complete, you must create a new MQL nurture campaign to have each of these assets.

Instructions for how to create a campaign can be found here.

Naming convention is as follows:

PROJECT CODE_MQL Nurture_MMYY

E.g. ROCK_MQL Nurture_0824