Who's using this thing. Password required.
"auto-approved" means their email is on the company domain, so they were let in without a request. "Requests" counts every call their browser made to the server, and one visit is worth several, so read it as a rough sense of how heavily someone uses the site, not as a visit count. "PI searches" counts how many times someone hit Search on the door-to-door tool specifically, not every request it makes behind the scenes (a single search also triggers a quick lookup and a couple of silent background refreshes, which would otherwise make a handful of real searches look like dozens). Like Requests, it needs no name-matching since it's keyed by the real sign-in email. Activity is logged against whatever name was typed at the time, so each row totals up every form of that person's name ("Chad", "Chad Steele"), and someone with no name on file is matched on their address instead (kevin.kaifer@ is Kevin Kaifer). A name two people could both answer to is never guessed at: it is noted under the table instead, which is why these columns always add up to what's actually in the database.
| Name | Access | Weekly email | Requests | PI searches | Last seen↓ | Emails | Good fit | Bad fit | Contacted | Replied | Prospect |
|---|
| Name | Email↑ | Access | Requested |
|---|
Nobody. Everyone with access has used it.
Usage by day, straight from the request log.
How far prospects get once someone starts working them.
Every action taken on the site, newest first.
Each line is one thing somebody did: a lead triaged, a result recorded, an email drafted, a PI looked up. Unlike the Users list, which shows where each lead stands now, nothing here is ever overwritten, so a lead that two reps worked in turn keeps both of their lines. Lines marked from records were seeded from what the database already held when this log was added. They are real, but thinner than what gets logged now, in two specific ways: on a lead, only the most recent action survived, because earlier ones had been overwritten before there was anywhere to keep them; and a seeded PI search says who searched and when but not what they searched for, because the search terms were never stored anywhere. Everything logged since is complete.