Ok this is amazing. Feedback on intros is so important, and I really need something like this for my professional workflow. Wondering on the experience from the receiving end and how receptive they are? I've used some email-based scheduling assistants and they are chaotic with communications.
scheduling bots got their bad reputation from a few concrete failure modes Loop was actually designed around. it sends an email from a clearly-labeled automated address, it's not pretending to be a person. It asks one simple, one-tap question, not an open-ended thread. It also never chases you with another email. The only people who ever hear from it twice are ones who explicitly tapped "still in motion, check back with me," and even then it's capped to 2x.
Reputation was the number one thing in mind so that Loop adds to your credibility as a connector and not the other way around.
One thing I will mention here is that when I make an intro, I always add one line - "Adding loop to see if this intro was helpful down the road, feel free to BCC us from here". This makes the process more intentional. Either way, recipient responses have been positive.
+1 for trying to stay as minimal as possible. Great principles.
How did you manage to do the answer tapping mechanism in the thread? Is it a similar interface to Google Scheduler?
My job is measured based on quality of intros. I definitely resonate with the need for this solution. Does log the data in a dashboard or provide any central data? Is there an mcp?
Thanks, that's exactly the use case I built it for.
Yes to the dashboard. It's completely optional so you can theoretically never open an account but if you do, you'll find all the intros in one space (sent and received). It offers more visibility on when loop emerges, allows for manual edits and more control over outcome notifications. There's also statistics like what types of people you get introduced to (investors, founders etc) your heatmap, loop rate (how many intros resolved with a real outcome) for quality measurement and more.
No MCP yet. You're right that data shouldn't stay trapped behind a dashboard/inbox. I'm genuinely curious what shape would be useful to you specifically. Something like "which of my intros are stalled," a reciprocity view ("who's a good connector for me"), or more of a raw export?
Ok this is amazing. Feedback on intros is so important, and I really need something like this for my professional workflow. Wondering on the experience from the receiving end and how receptive they are? I've used some email-based scheduling assistants and they are chaotic with communications.
Thanks for the kind words!
scheduling bots got their bad reputation from a few concrete failure modes Loop was actually designed around. it sends an email from a clearly-labeled automated address, it's not pretending to be a person. It asks one simple, one-tap question, not an open-ended thread. It also never chases you with another email. The only people who ever hear from it twice are ones who explicitly tapped "still in motion, check back with me," and even then it's capped to 2x.
Reputation was the number one thing in mind so that Loop adds to your credibility as a connector and not the other way around.
One thing I will mention here is that when I make an intro, I always add one line - "Adding loop to see if this intro was helpful down the road, feel free to BCC us from here". This makes the process more intentional. Either way, recipient responses have been positive.
+1 for trying to stay as minimal as possible. Great principles. How did you manage to do the answer tapping mechanism in the thread? Is it a similar interface to Google Scheduler?
Replies are managed through a magic link (one-tap answers). You can also just reply in-thread in natural language and loop will pick it up.
My job is measured based on quality of intros. I definitely resonate with the need for this solution. Does log the data in a dashboard or provide any central data? Is there an mcp?
Thanks, that's exactly the use case I built it for.
Yes to the dashboard. It's completely optional so you can theoretically never open an account but if you do, you'll find all the intros in one space (sent and received). It offers more visibility on when loop emerges, allows for manual edits and more control over outcome notifications. There's also statistics like what types of people you get introduced to (investors, founders etc) your heatmap, loop rate (how many intros resolved with a real outcome) for quality measurement and more.
No MCP yet. You're right that data shouldn't stay trapped behind a dashboard/inbox. I'm genuinely curious what shape would be useful to you specifically. Something like "which of my intros are stalled," a reciprocity view ("who's a good connector for me"), or more of a raw export?