Purported

This page describes 'purported' as a concept, which is applicable when it comes to lead data or disputed meeting outcomes, and goes hand in hand with the concepts of 'purported' and 'data decay'.

Definition(s)

• Purported, aka 'Alleged', aka 'Supposedly' refers to something appearing or stated to be true, though not necessarily so. The first 20 seconds of this clip are examples of Purported facts about a person:

Why purported is an important concept

When it comes to Leads data, not all data is perfect or accurate.

• When Leadsare added to Lead Pools via Lead Ingestions, the information you see, like: first name, job title, email, phone number, etc, are all purportedly accurate, but not necessarily verifiably accurate.

How purported and verified work together as concepts

There's a Russian proverb, доверяй, но проверяй which translates to trust, but verify.

Verifiedis another concept that goes hand in hand with the concept of Purported, and typically looks like this:

Example of Purported and Verified Working Together

• You see a phone number associated with a contact in your Lists. This is a Purported phone number, but not yet a Verified phone number (because you haven't called it yet)

• You call the phone number, and you hear a 'this number is not in service' automated response on the other line.

  • By calling the phone number, you have Verified this Purported data, and unfortunately it has been Verified as inaccurate.

  • You disposition the lead's phone number as 'bad data' or something similar, or you disqualify the phone number.

By dispositioning the lead properly, you've helped our system improve the quality of the data.

Example #1 of How Purported but not Verified facts can impact Meeting Outcomes

• You scheduled a meeting

• One of the Qualification Criteria is that the business is doing over $5M in annualized revenue

• You looked at the Purported revenue for the account in the Account Details page, and you see a $5M number

• You didn't necessarily verify the revenue on the call because it would have been awkward

• It didn't occur to you to quickly google search or research the company to see if you can soft verify the revenue

• The meeting outcome comes back as Not Qualified

• The Account Executive provides a recording of the conversation, where they Verified the Purported revenue of the company

By choosing not to verify the purported revenue data, you decrease the likelihood of a Qualified meeting outcome.

But, maybe you would have lost the meeting if you'd been a stickler for verification and lowered the prospect's interest level because you were asking too many questions. There's always a tradeoff.

Good sales reps will know how to ask these types of qualification/verification ways in ways that aren't robotic/come off as natural.

Strategic use of humor, or spreading out the timing of qualification questions organically throughout the conversation, can help you get the best of both worlds.

Example #2 of How Purported but not Verified facts can impact Meeting Outcomes

Purported and Verified applies in contexts besides just lead data accuracy. Here's another example.

• You scheduled a meeting

• The Purported meeting outcome comes back as a No Show without any useful or specific context from the meeting taker

• You decide to verify the No Show by calling the lead and asking how the meeting went. This is generally good practice - good sales reps always follow up and are focused on building relationships. Checking in is a form of relationship building

• The lead says they waited 10 minutes on the call but nobody showed up.

• You submit a meeting dispute and you get your payout.

By choosing to verify the purported no show, you changed a Qualified meeting outcome.