[SaltyAstronaut]

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.

[Lindathefounder]

+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?

[SaltyAstronaut]

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.