Engagement Report

Knock's Engagement report is a great way to understand how your leasing teams' are doing at responding to traffic at your properties. Here is a glossary for all the data points in the report. We'll also outline below what all the filters and options will do to the report to make sure everything is crystal clear!





Properties: This is a multi-select for what properties you'd like data for. The default will be set to 'all'.

Date range: This will filter the report by date. The default will be 'seven days'.

Agents: This breaks the engagement score down by agent. This helps diagnose at your property if there are coaching opportunities for agents that may not be following up with their leads as they should be. The default will be set to 'all'.



Property/Agent: The property or agent for which the engagement score is calculated. Agents will show when property dropdown is selected.

Recent Score: The engagement score for the row as calculated recently (live). You can click on this value and it will expand out to engagement scores by time and day for further inspection.

Avg Score: The average engagement score for the row. This is the average based on your office hours set in Admin > Knockbot. 

Green: The number of Active Green Prospects for the row. This is all the prospects that are not Lost, Leased, or Waitlisted but have been followed up with appropriately.

Red: The number of Active Red Prospects for the row. This is all prospects that are not Lost, Leased, or Waitlisted, and therefore need to be followed up with but have not been.

Avg Followup: The average follow-up for the row. This is calculated the same as the Conversions report. Knock counts one follow-up type per day. Meaning if you email a prospect five times in one day that counts as one follow-up. If you email once, call twice that would count as two, as there are two different types of communication being made.

Raw Data: This report includes Daily and Hourly Live Scores set by the Date Range filter.




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



Article is closed for comments.

Articles in this section

See more