Engagement tracking
The second reply is where relationships are built or burned
Engagement tracking is keeping a durable record of every person you have interacted with on social, so that follow ups are deliberate and nobody is contacted repeatedly by accident.
Social conversations do not land in a CRM, which is why most teams have no idea who they already replied to. The consequence is not just untidy records. It is the same prospect getting three replies in a week from two different people, which is the fastest way to look automated to exactly the person you were trying to impress.
The failure is duplication, not forgetting
Forgetting to follow up costs you an opportunity, which is bad but invisible. Contacting the same person repeatedly costs you the relationship and does it in public. A ledger of who has been engaged exists mainly to prevent the second failure, and that is the one worth designing around.
A cooldown is a rule, not a preference
Decide the minimum gap before the same person can be contacted again and enforce it somewhere that does not depend on anyone remembering. A number that lives in a policy document and not in the system that sends is a number that gets ignored on a busy day.
Scope it to the organisation, not the person sending
Per user tracking is the mistake that reintroduces the whole problem on a team. The prospect does not experience four reps, they experience one company contacting them four times. The ledger has to be shared across everyone who sends.
Track the response, not just the send
A record of what you sent is an activity log. A record of what came back is data: which openings got replies, which accounts warmed up, which went quiet after the second touch. The second one changes what you do next.
How to do it
Decide what counts as an engagement
A reply certainly. A like probably not. Be explicit, because a definition that includes trivial interactions will make your cooldowns fire when nothing meaningful happened.
Pick a cooldown and write it down
Something in the region of a month between meaningful touches to the same person is a defensible default. Pick a number, then enforce it rather than debating it per case.
Make the ledger shared
One record per person, visible to everyone who sends. If two people can each hold their own list, the duplication problem is unsolved.
Capture outcomes, not only actions
Record whether the person responded, and what happened after. Without it you cannot tell a working opening from a busy one.
Review the quiet ones monthly
People who engaged once and then went silent are the most improvable segment you have, and they are invisible unless somebody deliberately looks.
Common mistakes
- Keeping engagement history per user, so a shared prospect gets contacted by everyone on the team.
- A cooldown that lives in a policy document rather than in the system that actually sends.
- Counting likes as engagement, which triggers cooldowns for interactions nobody noticed.
- Logging sends without outcomes, which produces an activity report and no learning.
How Quillen handles engagement tracking
Quillen keeps an engaged account ledger and enforces a thirty day cooldown on anyone you have already engaged, along with deduplication that hard blocks replying to the same post twice for thirty days and caps the same person at three replies per rolling fourteen days. All of it is scoped to the whole workspace rather than to the individual sending, which is deliberate: two connected accounts in the same organisation will not both reply to the same person. There is an engaged accounts view in the dashboard showing who has been contacted, so the ledger is readable rather than only enforced.
Common questions
- How long should a cooldown be?
- Long enough that a second contact feels like a new conversation rather than a follow up to an unanswered one. A month is a reasonable default on social, and shorter than that starts to read as persistence rather than interest.
- Should engagement history be shared across a team?
- Yes, always. Per user history is the same as no history from the prospect point of view, because they experience one company rather than four individuals.
- Does this belong in my CRM?
- Eventually, but a CRM field is a poor enforcement point because it does not block anything. The cooldown needs to live where the sending happens; the CRM is where the summary goes.