Qualifying Prospects: "Not a Prospect" button

Need to remove a prospect from the ToDo list? Need to mark a prospect as Spam? This article will explain how to mark a prospect as "Not a prospect."

Anyone who calls one of your Knock tracking numbers will create a guest card in Knock. Most of the time this is an actual prospect, so this behavior is expected/desired. However, we have found there are always the following people who are not prospects:


  1. Vendor

  2. Existing Resident (calling from an office line or number we don't have on file)

  3. Not a prospective renter (but has questions about the property)

  4. Other

  5. Spam 

  6. Duplicate/Error


Now in Knock, there is an easy way to flag these Guestcards, so that they are not counted in your To-do list/engagement score, but still show up in the Call Report or other reports where desired.

Here's how to mark a guest card as "Not prospect":

Step 1:

At the top of the Guest card, click the icon to the left of the status for Mark as 'Not a prospect':

Step 2:

A list of possible reasons will populate. Select the most applicable reason (in the below example I selected "Vendor") and then click Save:

That's it! Now you can see at the top of the guest card to the left of the status that the "Not a prospect" icon is red, meaning this guest card will not be counted against your engagement score.

Note: The icon will not turn red if you select "Duplicate / error", because duplicates are categorized differently on the backend.

This will accomplish the following:

  1. Non-prospects will be removed from your To-Do List, and not count against engagement scores

  2. Conversion rates in analytics will exclude Non-prospects, rather than treating them as "Lost" prospects.

Pro tip: If this phone number calls in the future (or if the email is on file for their emails), that message will still show up in Knock under the same guest card. The difference is it will not show up on your to-do list as someone you need to follow up with.

Was this article helpful?
0 out of 0 found this helpful



Article is closed for comments.

Articles in this section

See more