Lead Ops Sourcing SLAs

Please refer to this document for standard rules of engagement for MQL sourcing and the assignment of Marketing Originated Opportunities. 

Handling the MQL List View or “The MQL Queue”

What is “The MQL Queue”?

When an individual becomes an MQL, they will appear in the MQL List View. The Lead Operations Team has two MQL list views, one for new name MQLs and one for contact MQLs. Here you will find individuals who have scored-up or requested a demo. We refer to both of these list views as the MQL Queue. Lead Operations creates almost all Stage 0 Marketing Originated Opportunities from the MQL Queue.

New Name MQL List View

Contact MQL List View

How to handle the MQL Queue?

The MQL Queue should be reviewed first thing each workday. MQLs should be prioritized based on their source detail. Follow the source detail prioritization list below for both new name and contact MQLs.

1. Demo Requests: Demo Requests should always be handled and converted to opportunities first.

2. Tradeshow Hot Leads: These are treated as Demo Requests and should be prioritized as such.

3. Tradeshow Score-Ups: Warm tradeshow leads should be prioritized after demo requests.

4. Webinar Live Score-Ups: Webinar Live attendees are to be prioritized next.

5. On-Demand Webinar Score-Ups: Lastly, on-demand webinar attendees will be prioritized.

After following the prioritization list above, address remaining score-ups based on their “MQL Date.” Make sure to work the MQL queue from oldest to most recent MQL date. You can do so by sorting the list view by MQL date in ascending order. Demo requests should be handled from oldest “SFDC Demo Request Date” to most recent, to do so sort the list view by SFDC Demo Request Date in ascending order.

Lifecycle Statuses

Before you begin creating Stage 0 opportunities from the MQL queue, it is helpful to mark appropriate leads with a “recycle” or “refer-to-retail” lifecycle status.

• Use the “recycle” lifecycle status when:

  • A B2C title MQL scores up.

  • A Demo Request comes in with a “Contact Us” message indicating that they are seeking support. (Example: “My team members are having issues logging into Relias.”)

• Use the “refer-to-retail” lifecycle status when:

  • A B2C title MQL requests a demo.

  • A Demo Request comes in with a “Contact Us” message indicating they are going to use Relias for personal learning. (Example: “I need to sign up for continuing education.”)

• ONLY use the “junk” lifecycle status if:

  • You see an MQL that clearly appears to be a bot completing a Demo Request form. (Example: A lead with the name “dfsdsd sdfsddfs” and a “Contact Us” message that reads “xcvbvvvbfgfggf”)

  • REMEMBER: The junk lifecycle status will trap a lead. Once you mark an MQL as junk, it cannot re-MQL and return to the MQL queue.

Please refer to the spreadsheet linked below for guidance on distinguishing between B2B and B2C titles.

Buying Titles Guide

Rules of Engagement for Opportunity Assignment

Opportunities are assigned to Account Executives (AE), Account Managers (AM), or Business Development Representatives (BDR) based on vertical, employee count, state/province, and whether the MQL is a Content Score-Up or a Demo Request.

Opportunity Assignment: Demo Requests v. Content Score-Ups

Demo Requests should be assigned to the appropriate representative based on the following guidelines:

• New Name MQL on New Account: A Demo Request from a new name MQL that does not belong to an existing account will always be assigned to an AE. Use the territory map to determine the appropriate AE based on state/province and vertical.

• New Name MQL on Existing Account (or Customer Account): A Demo Request from a new name MQL that belongs to an existing account should be assigned to the owner of that account. If the account is not a customer, this will likely be an AE. Demo Requests from a new name MQL that belongs to a customer account should be assigned to the owner of the account as well. In this case, the account owner will likely be an AM.

• Existing Contact MQL on Existing Account (or Customer Account): Similar to the previous case, Demo Requests from an existing contact MQL on an existing account should be assigned to the owner of this account. This should also be done for a customer account. Again, in this case, the account owner will likely be an AM.

Content Score-Ups should be assigned to the appropriate representative based on the following guidelines:

• New Name MQL on New or Existing Account (NOT Customer): A Content Score-Up that is a new name MQL and either does or does not belong to an existing account should be assigned to a BDR. Use the territory map to determine the BDR who should own this opportunity based state/province and vertical.

• New Name MQL or Existing Contact MQL on Customer Account: A Content Score-up that is a new name MQL or existing contact MQL on a customer account should be assigned the owner of that account. In this case, this will likely be an AM.

For additional information on the differences between AEs, AMs, and BDRs, please refer to the following document. Sales Roles Guide

Opportunity Assignment: Open Opportunities

When assigning Stage 0 opportunities from MQLs, it is very important to ensure an account does not already have an open Marketing Originated Opportunity. This information can be found in the “Attribution Tracking” section of an opportunity.

In the case that there is an open Marketing Originated Opportunity, you should not create a new opportunity. Instead, add the MQL to the open marketing opportunity either by conversion (New Name MQL) or adding a contact role to the opportunity (Contact MQL). Be sure to assign the MQL to the owner of the open marketing opportunity. Add a message to the “chatter” section of the opportunity and tag the opportunity owner. Use the following message as a template: “@Meaghan Kenney a new MQL has been added to this opportunity.”

If there are any other open opportunities that are NOT Marketing Originated, you should create a new opportunity and assign it accordingly.

Opportunity Assignment: Using the Territory Map

When you have a new name MQL that does not belong to an existing account, you will need to assign the Demo Request or Content-Score Up opportunity based on vertical, company size/employee count, and state/province.

• Company Vertical

  • AE, AM, and BDR territories are separated in part by vertical. Our verticals are Behavior and Community Health (BCH), Acute (ACU), and Post-Acute Care (PAC).

  • Be sure to double check that the vertical that appears on a lead record is correct before conversion. This can be done by looking into company information on ZoomInfo, LinkedIn, and the company website.

  • REL cannot be used as a vertical when converting a lead. This should always be changed to BCH, ACU, or PAC before conversion.

• Company Size/Employee Count

  • Territories are also separated by company size/employee count. For PAC and BCH, company size will be determined by employee count. However, ACU organization size will be determined by bed count.

  • Accounts fall into four categories for size based on employee or bed count: Rest of Market (ROM), Small Business (SMB), Mid-Market (MM), and Enterprise (ENT). The Acute AE’s work a hybrid model, new business representatives cover both SMB and MM with separate reps for only ENT.

  • Employee count is determined first by viewing the company’s LinkedIn page, then the company’s website, or by collecting the information from ZoomInfo. ZoomInfo is typically used as a last resort since it tends to be incorrect.

  • If an employee count cannot be found, it is sent by default to the SMB team.

• Company Size/Employee Count Thresholds by Vertical

• State/Province

  • Lastly, territories are separated by U.S. State or Canadian Province.

  • ALL leads should have a state or province on their profile page before conversion. State/province is incredibly important for opportunity assignment.

Assignment based on all three factors above can be done using the territory map. The territory map is obtained from the Sales Operations Team about once a month. Always ensure you are using the most recent territory map for opportunity assignment.

Matrix for Opportunity Assignment

Here is a quick snapshot of the ROE’s for opportunity assignment. Once you are familiar with the rules for opportunity assignment, this is an easy cheat sheet!

Opportunities Outside of Normal ROE

Wound Care MQLs

Our Wound Care BDR Team will handle all MQLs and opportunities with a last touch attribution of wound care. This includes Demo Requests. Here are some items to remember when handling wound care MQLs:

• Any Demo Request or Content Score-Up with a last touch attribution of “wound care” should be sent to a wound care BDR. Use the WC territory map to determine the appropriate representative.

• Only B2B leads should be sent to the wound care team. Mark B2C wound care leads as “refer-to-retail.”

• Follow standard ROE for Marketing Originated open wound care opportunities.

Nurse.com MQLs

Nurse.com leads will typically come in to the MQL queue as a Demo Request. Similar to wound care leads, these will be sent over to a specific team, which would be digital advertising. All nurse leads will be sent to Conor O’Shea on that team. Here are some guidelines for managing Nurse.com leads:

• Any MQL with last touch attribution of Nurse.com is sent to Conor O’Shea and is distributed to the digital advertising team accordingly.

• Although Lead Operations has access to the territory assignments for digital advertising representatives, nurse leads should still only be sent to Conor unless told otherwise by Sales Operations.

• Follow standard ROE for “recycle” and “refer-to-retail.” B2C titles should be marked as refer-to-retail, and support requests should be recycled.

• Follow standard ROE for Marketing Originated open nurse opportunities.

Support MQLs

At times, the Support Team will receive a call from an individual who is actually a B2B lead looking for a demo or more information about Relias. Support will gather as much information as they can before passing this on to the MQL Queue for further review and assignment. Here are some things to remember when reviewing and assigning these leads:

• Support leads will come in to the MQL Queue with a source detail that beings with “Case.” This can include Case-Academy, Case-Nurse, or Case-Wound Care.

• These leads WILL NOT include any campaign attribution outside of “source” and “source detail.” Do not update the campaign attribution.

• Support leads should be assigned to a BDR according to state/province, vertical, and company size. Use the territory map to determine who would be the appropriate BDR.

• Support leads will likely come in with less information than a standard lead. Try your best to gather the most important information (vertical, phone or email, and company name) before assigning the opportunity.

GRC Content Score-Ups

Any Content Score-Ups that have last-attribution pertaining to compliance (ie. Compliance Management, Managed Services, Policy Pro) will go directly to the GRC BDR. The GRC BDR can be found on the territory map. This ONLY applies to Content Score-Ups, GRC BDRs should not receive demo requests.

Helpful Tidbits to Remember

Last Touch Campaign Attribution Information

Always check that the last touch campaign attribution information has populated on the lead or contact profile prior to conversion. If you do not see last touch attribution on a lead or contact, investigate a bit further to understand why this may have occurred.

• If it is an MQL that scored up through email clicks, attribution may not have been captured. This MQL can be recycled.

• If an MQL has interacted with an asset older than two years, attribution information may not populate. Take a look at the MQL’s campaign history and reach out to Chrissey or the appropriate parties (Customer Marketing, Demand Generation etc.) to figure what the attribution should be.

Attribution information MUST be populated or manually updated before conversion or opportunity creation. The opportunity created will not have any attribution information if it does not exist on the lead.

• Only manually update the last touch attribution if you know for sure what the information should be. If it is indeed a marketing lead, the source in attribution should be Source=Marketing.

• If the attribution information cannot be found or there appears to be a system error that is preventing attribution information from populating, submit an ISR to the RevTech Team.

To better understand campaign attribution and it’s importance, review the following document: https://relias.atlassian.net/wiki/spaces/GM1/pages/3795353605

Duplicate Lead and Contact Records

Handling Duplicate Leads

• When a duplicate lead records comes in to the MQL Queue, you will see a notification at the top of the lead record which notifies the user that a duplicate lead exists. Always view the duplicates.

• Review the duplicates thoroughly to ensure they are truly the same person (ie. similar emails, phone numbers, and company information, not just the same name.)

• Always use the lead record with an MQL lifecycle status and the most recent MQL date as the primary record.

• If there are differing emails or phone numbers, but you are certain the duplicate records are the same individual, be sure to copy down this information as you can only save one email or phone number per record.

• Add the differing information to the lead record’s “Contact Us Message” with the following message: “Lead Source Note: Potential alternate email meaghankenney@gmail.com.”

Handling Duplicate Contacts

• Similar to lead records, contact records will also show a notification of duplicate records existing. Always view the duplicates.

• The same process that is used for duplicate leads, should be used for duplicate contact records.

• When a lead is converted to a contact on an existing account, review the “Related Contacts” section on that account to ensure a duplicate contact was not created. Merge the contacts as needed.

• If there are differing emails or phone numbers, but you are certain the duplicate records are the same individual, be sure to copy down this information as you can only save one email or phone number per record.

• Add the differing information to the lead record’s “Contact Us Message” with the following message: “Lead Source Note: Potential alternate email meaghankenney@gmail.com.”

Duplicate Account Creation

• If a duplicate account is accidentally created upon conversion, a Sales Operations ISR needs to be submitted to request that the accounts be merged.

• Always be sure to check that a company does not currently exist as an account prior to conversion to avoid this issue.