Lindy on X

The largest group states goodwill without specifics: 20 people call it handy or helpful, say its insights could streamline operations, or recommend it to someone else — replies to other people's threads more than accounts of their own use. Next, 15 credit it with what it surfaces across Slack, email and Drive: a broken promise and an unfinished migration caught before scheduled launch comms went out, sales lagging support, stock and open tickets pulled into one note.

4 describe it doing the day's work — scheduling, product tickets, support triage, PR scores — in one case as another employee in Slack, email and text; that testimonial is the most-travelled post here. 2 are taken with phone calls, including a bot that waits on hold. 2 doubt whether the output is real work: "just busywork?".

One person asked whether Lindy's number is a VoIP phone or an eSIM, then reported that the VoIP one "cannot do shit online for OTP" — it can't take the codes sites text you, which blocks anything that needs one. The other flagged to the founders that the Lindy versus Superhuman comparison page still showed the old $49.99/mo price; that complaint has been quiet since 23 September.

No other fault is filed in this section: nothing on reliability, on what the plans cost, or on runs that failed. The section is the thinnest on the page, and both posts are one person each, so neither is a pattern yet.

Calendly is what the comparison talk is about, and it isn't a switching story: one person said Lindy is "like ActorDo and Calendly! Nice to see you copied them!", the other answered a scheduling post with a curt "calendly who?" Neither describes leaving a tool for Lindy or the reverse.

The rest is thin. One person listed Lindy among the workflow tools they tested that day, alongside Gumloop, without saying which won. Another's note that Lindy's comparison page against Superhuman still showed the old $49.99/mo price was filed here as well as under problems, which makes it the only pricing mention on the page; it has been quiet since 23 September.

The questions are mostly follow-ups to someone else's account of a run: "how'd it perform?", what actionable insights it gave the business, what it pulled for them, and how it handled unstructured data like customer reviews. That is 4 of the 7 people in the section, and answering it is what a reader of those threads would want.

The rest are one person each and split in two directions. Two are about coverage and plumbing: whether Lindy works on platforms other than Slack, and whether the number it gives you is a VoIP phone or an eSIM — the same person who later reported the VoIP number can't take online verification codes. Two are about scope: whether it means you never have to call an airline again, and whether it can book reservations by phone and dial for you.

The asks sit level at one person each, so none can be called the biggest. Two are about what it should do with a phone: schedule and call to book reservations, and, from a CRM angle, a 30-second post-meeting call that captures the next step, owner and date while it's still fresh.

Two are about feeding it more or different material: more data examples, and parsing Slack threads for inventory trends to cut restock delays. One is about ownership — "Now how do we opensource this!" — asking how to open source it rather than only wishing it were. The specifics are concrete: reservations, next steps for the CRM, restock delays.