After a Product Pitch or Research Call, Sages share their level of interest and choose whether to reveal their identity. This gives vendors insight into intent while still protecting buyer privacy.
How Post-Call Decisions Work
Sagetap separates the opt-in decision into two questions:
Interest in the product - “Yes, I’m interested” or “No, I’m not interested.”
Sharing identity - “Yes, share my contact info” or “No, don’t share my contact info.”
This creates four possible post-call states:
Interest | Share Identity | What it means |
Yes | Yes | Buyer is interested and revealed identity. You can follow up directly. |
Yes | No | Buyer is interested but remains anonymous. They can opt in at any time. |
No | Yes | Buyer is not currently interested but has shared their contact info, leaving the door open for future outreach. |
No | No | Buyer is not interested and stays anonymous. No follow-up is possible. |
NOTE : Any session where a Sage indicates interest will appear on your Connections page.
Key Points After a Session
The deal’s status (Interested, POC, Purchased or Passed) is updated by the Sage, and both Sages and vendors can apply filters on the Connections page to only view deals in the various stages.
NOTE : This system captures buyer intent while giving them full control over their privacy.
What Buyers Should Know:
You have control over your privacy and can decide whether to share your identity, ensuring a safe and flexible evaluation process.
After each call, you can use one of four post-call options to clearly indicate your intent and privacy preference.
What Vendors Should Know:
Buyers may express interest in your solutions while remaining anonymous. This allows you to gauge their intent without putting pressure on them to share details too early.
At times, buyers may send mixed signals, some may indicate “No” but still provide their contact information, while others may indicate “Yes” without revealing their identity. Both situations create opportunities for future engagement.
The most actionable leads are buyers who share their identity along with their interest. These represent high-intent opportunities, and you can use filters on the Connections page to prioritize them for direct follow-up.
Note : The platform’s post-call options help both buyers and vendors make the most of each session. Structured decisions provide vendors with clarity on buyer intent, session statuses update in real time for accurate pipelines, and filters allow vendors to focus on the most relevant opportunities. This ensures that signals are clear, actionable, and beneficial for everyone involved.
Understanding Sage Opt-Ins
When a Sage indicates interest and chooses to reveal their identity, they opt in to continue the conversation. Opting in means they share upcoming availability or provide a work email address, signaling genuine interest and enabling follow-up outside Sagetap.
Once the Sage takes this action, you will automatically receive an introduction via email. If they select 'Let's chat via email', we require that they share a deadline for when you can expect to hear back from them. We automatically send reminders to close the loop as that deadline approaches, ensuring this opportunity is top of mind for the Sage.
How Vendors Should Handle Opt-Ins
Respond promptly when a Sage opts in and keep the conversation fresh in their mind.
Review the session feedback before your next meeting to understand their questions and areas of interest.
Respect the timeline the Sage has set for follow-up while staying prepared and proactive in the meantime.
Closing the Loop
Sages receive reminders as deadlines approach to either share their availability, postpone the meeting, or close the opportunity if they are no longer interested.
Vendors are also contacted to confirm follow-ups, which helps us track Sage responsiveness.
Note: This responsiveness is recorded on the Sage’s profile under “Opt-in Responsiveness,” providing vendors with insight into their engagement history.
If you have any questions about your Connections, please contact support@sagetap.io.