Contact Status Playbook: Turning Discovered Teammates Into Invited Users

Discovery without a status workflow just becomes a longer list

Teammate discovery answers a narrow question: who else at this company is worth knowing about. It does not answer what to do with that person once you know about them. Without a status workflow, discovered contacts pile up in a spreadsheet or a dashboard tab that nobody revisits, and the account expansion the discovery was supposed to unlock never happens.

Groful tracks every discovered teammate against four statuses: PENDING, INVITED, JOINED, and IGNORED. That sounds simple, almost too simple to write a post about. In practice, most PLG teams either skip the workflow entirely or treat all four statuses as equally important, which buries the handful of contacts that actually matter under hundreds that don't.

This post covers how to run the status workflow so discovery turns into invitations, invitations turn into signups, and the contacts that were never going to convert stop cluttering the queue.

What each status actually means

PENDING: discovered, not yet acted on

A contact lands here the moment Groful's teammate discovery surfaces them from a user's company. PENDING is a queue, not a resting state. A contact that has been PENDING for three weeks is not "in progress," it's forgotten. Treat a growing PENDING count as a backlog metric, the same way you'd treat an unanswered support queue.

INVITED: someone took action

Moving a contact to INVITED should correspond to a real action: an email sent, an in-app invite triggered, a personal outreach message logged. It should not be a status you set because a contact looks promising. If INVITED doesn't map to an actual touch, you lose the ability to measure invite-to-join conversion later, and the whole point of tracking status disappears.

JOINED: the expansion actually happened

JOINED means the teammate signed up and became their own EndUser record, not just that they clicked a link. This is the status that should feed your expansion pipeline and your win-rate math. A high JOINED rate from a specific discovery source (LinkedIn search, email pattern match, company directory) tells you that source is worth prioritizing; a low rate tells you to check whether the contacts it surfaces are actually the right people.

IGNORED: a decision, not a default

IGNORED is for contacts you've deliberately decided not to pursue: wrong seniority, wrong department, already a customer under a different account, duplicate person matched twice. The mistake teams make is leaving irrelevant contacts as PENDING indefinitely instead of marking them IGNORED. That inflates the backlog and makes it harder to see which PENDING contacts genuinely deserve attention.

Why teams let the queue rot

A few patterns show up repeatedly in PLG teams that never get value out of teammate discovery:

• No owner. Discovery is automatic, but invitations are not. If nobody is responsible for working the PENDING queue, it grows until it's ignored on principle.
• No triage rule. Every discovered contact gets treated the same, so a VP of Engineering and a contractor who logged in once sit in the same queue with the same priority.
• No feedback loop. Nobody checks which discovery sources produce contacts that actually reach JOINED, so the team keeps paying attention to sources that mostly produce noise.
• Invitations sent without context. A generic "your colleague is using our product" email to a stranger converts poorly. The invite needs to reference something specific: the tool, the workflow, the teammate who's already using it.

None of these are enrichment problems. They're operating problems. Better data does not fix a queue nobody works.

A status workflow that holds up

Step 1: Triage PENDING contacts by ICP fit and seniority

Not every discovered teammate deserves an invite. Run new PENDING contacts through the same ICP scoring you apply to primary users. A contact who scores as a strong ICP fit and holds a decision-making title should move toward an invite within days. A contact with weak fit or an unrelated role can sit lower in the queue or move straight to IGNORED if the mismatch is clear.

Step 2: Decide who sends the invite and how

Three common paths, in order of typical conversion:

1. Peer-to-peer, where the existing user forwards an invite or CC's a teammate directly. Highest conversion, lowest volume, because it depends on the existing user taking action.
2. In-app nudge, where the existing user is prompted to invite a specific teammate Groful identified. Medium conversion, scalable, and it keeps the ask inside a product moment instead of a cold email.
3. Direct outbound, where growth or sales emails the discovered contact without going through the existing user first. Lowest conversion per contact, but useful at volume for high-fit accounts where peer invites stall.

Match the path to the contact's ICP score and the account's stage. High-fit contacts at active accounts justify the peer-to-peer ask. Lower-fit contacts across a large account are better handled with a lighter in-app nudge or batched outbound.

Step 3: Move to INVITED the moment the action happens

Update status at the point of send, not before. If you're triggering invites through the dashboard, the bulkUpdateContactStatus action handles multiple contacts at once so a growth manager can invite an entire discovered team from one account in a single pass instead of clicking through each contact individually.

Step 4: Track INVITED to JOINED conversion by source and message

Once a contact reaches JOINED, look backward: which discovery source found them, which invite path was used, how long the INVITED-to-JOINED gap ran. A 40% conversion rate from peer-to-peer invites and a 4% rate from cold outbound is a real signal about where to spend time, not a coincidence to shrug off.

Step 5: Clear IGNORED contacts out of active review

IGNORED contacts should not resurface in the same queue as PENDING ones. Export or archive them periodically so the working queue only shows contacts still worth a decision. Groful's contact export supports PDF and XLSX output, which is useful for handing a filtered, ignored, or invited list to a rep or a CSM without giving them dashboard access.

A weekly checklist for the contact queue

• Review the PENDING count. If it's growing faster than it's being worked, either add triage capacity or tighten the discovery filters feeding it.
• Confirm every INVITED contact corresponds to a real, timestamped action.
• Pull the INVITED-to-JOINED conversion rate for the past 30 days, broken out by discovery source.
• Spot-check five IGNORED contacts to confirm the reason still holds. Companies restructure, and someone marked irrelevant six months ago might be relevant now.
• Flag any account where a high-ICP contact has sat PENDING for more than two weeks and route it to whoever owns outbound for that segment.

Where this fits with the rest of your enrichment stack

Contact status is the execution layer sitting on top of discovery and scoring. Teammate discovery finds the people, ICP scoring tells you who's worth pursuing, and the status workflow is what actually moves someone from a name in a list to an active user or a qualified opportunity. Skip any one of the three and the other two lose most of their value. Discovery without scoring wastes outreach on the wrong people, and scoring without a status workflow just produces a prioritized list that nobody works.

If you're building this out for the first time, start narrow: pick one account segment, run the full PENDING → INVITED → JOINED cycle on it for two weeks, and measure the conversion before rolling the workflow out everywhere. A working process on ten accounts beats an unworked queue across a thousand.

Put teammate discovery to work

Groful discovers teammates automatically as part of enrichment, scores them against your ICP, and gives growth teams a status workflow to manage the invite-to-join process without building custom tooling. See how it fits your growth manager workflow, check pricing, or read more on PLG signup enrichment and teammate discovery and expansion signals. Questions about your account structure or invite volume? Get in touch.