A public post can be worth reading without being ready for your CRM. I would keep that distinction clear. Creating a record doesn't make the opportunity more real, and somebody still has to decide what to do with it.
The useful handoff happens when you can explain the person's need, their interest, and why your team should continue. That gives the next person something concrete to work with.
Name what you know at each step
Discovery gives you a post that may fit your customer profile. Review tells you whether the stated problem and requirements match your offer. A reply can provide more information. Confirmed interest tells you the person wants to continue discussing the relevant next step.
Those are different pieces of evidence. I wouldn't collapse them into a single ‘lead’ label and expect the sales team to work out which ones are present.
| Stage | What you can record |
|---|---|
| Discovered | The post and the reason it may fit. |
| Reviewed | Known requirements and remaining uncertainties. |
| Conversation | What the author actually said in response. |
| Qualified | Confirmed interest, fit, and a useful next step. |
Read the response for what it establishes
A polite thank-you doesn't necessarily mean the person wants a demonstration or a sales conversation. Look for the request they make next. They may ask about a feature, discuss a relevant need, or explicitly ask to continue.
Keep their words and your interpretation separate. If interest is unclear, ask a proportionate question instead of assigning a later stage because the thread feels promising. Missing information belongs in the handoff as missing information.
Apply the qualification step in ICPSignal
ICPSignal's default CRM transfer requires a reply, confirmed interest, and qualification by your team. Review whether the offer fits the stated requirements and whether there is a useful reason for another person to take action.
Supported CRM connections and access depend on your plan. Check the actual handoff process with the system you use. ICPSignal can also manage leads internally, so you don't need to connect a CRM just to begin discovery and review.
Send context with the record
Include the original conversation, the problem, confirmed requirements, unanswered questions, and any promise already made. Give the next step a clear owner in your team's process.
For your next batch, review which conversations meet those conditions and which should remain under review. I want a CRM record to help someone continue an informed conversation. If the record can't explain why action is needed, the handoff probably needs more work.