tiun.Auth, billing, and payments for AI builders
Promoted
The modern alternative to Zendesk, Freshdesk, Intercom, and Front. Connect your database and Stripe. Our AI support agent resolves tickets across email, forms, and other channels.
Free Options
Launch Team / Built With
Freebuff
Hey Product Hunt!
I'm Dawson, co-founder @ Letterbook.
We grew our last product, Martin, to 100k users. At one point, we'd get 50 support requests every day:
"How do I use this feature?"
"Can I get a refund?"
"I can't log into my account."
I had to hire a virtual assistant in the Philippines to reply to users and solve billing issues.
I had to use Zendesk, which was built 20 years ago and designed for a VP of Support, not a founder.
None of this made sense, so we built our own modern, AI-native support platform. We integrate with your database, knowledge base, and Stripe, and our AI auto-prepares resolutions to every ticket.
We’ve already replaced Intercom, Zendesk, Zohodesk, Helpscout, and Freshdesk for many fast-growing companies in YC.
If you’re building a B2C or self-serve B2B product, give it a try or book a demo at:
https://letterbook.ai
P.S. Unlike Zendesk, which takes days to set up (a friend literally hired a consultant to teach him), Letterbook takes 5 mins. And if you need help, you better believe we have top-notch customer support!
INK'A
@darweenist nice! need this for my app, definitely giving it a try.
Freebuff
@frank_denbow Thanks for the support Frank!
Support tooling for founders is usually an afterthought - either paying for Intercom before you have revenue, or handling everything manually through email threads. The AI angle makes sense here. What does Letterbook do when it doesn't know the answer - does it hand off to you, or does it try to figure it out?
Freebuff
@mykola_kondratiuk Great question! Letterbook actually just prepares resolutions for you to approve right now. For example, you'll see a draft of the email response + a suggested Stripe/Database action that you can approve in 1 click!
That's actually the right call for now - founders need to see what the AI is doing before trusting it to send autonomously. Once you've built that trust layer, adding an 'auto-send' toggle for routine cases would be a natural next step.
Freebuff
@mykola_kondratiuk Yup, exactly! As you scale your support we'll turn on auto-send!
That makes sense - auto-send once you trust the resolutions. Looking forward to that being turned on.
Went through the signup flow. The 15 minutes to first resolved ticket claim on the landing page is the right hook, that's exactly what a founder dealing with support volume wants to hear.
The gap is that Signup asks for the organization name before showing any evidence that the 15 minutes is real. For a founder evaluating whether to commit, that's a small friction at exactly the wrong moment. The stronger move would be showing one resolved ticket in a demo state before asking for anything, let the claim prove itself before the founder has to name their organization. What does drop-off look like between landing page and completed signup?
Freebuff
@arun_tamang Hey Arun thanks for the feedback! We'll definitely improve the flow based on what you mentioned. Were you able to eventually resolve a ticket?
@darweenist Signed up and connected Gmail. After signup you land on an empty inbox with two buttons. Connect Gmail or Set up webhook and no indication of what the 15-minute setup actually looks like from there. After connecting, it switches to importing conversations and extracting knowledge in the background with no signal of how long that takes or what to do in the meantime. The setup runs quietly while you figure out where to go next.
Freebuff
@arun_tamang Hey Arun, we are launching a new onboarding flow directly as a result of your feedback! Thanks so much for the input. Also, apologies for missing this comment last week - I'd love to get you set up with Letterbook manually on a call if you're up for it: https://cal.com/dawson-chen-iuthbm/demo
@darweenist That's a fast turnaround, good to hear the feedback translated into something concrete. Curious what the new flow looks like, specifically how you're handling the empty state after Gmail connects. Happy to take a look at the updated version on a call.
Congrats on the launch! Support is one of those things that sneaks up on you, and can eat away at your hours. Once you connect Stripe, how much customer context does the AI actually pull in when it's drafting a reply?
Freebuff
@simonk123 Good question! The AI has full context of that customer's purchases, invoices, subscriptions - basically anything a human support agent would get from Stripe. If that's not enough information to resolve a ticket, a database integration can often fill in the gaps.
Jupid
The Stripe + database integration is what sells this for me. Running a B2B SaaS with self-serve billing, and 60% of our support tickets are "where's my invoice" or "cancel my subscription" — exactly the kind of thing AI should handle autonomously. How does the AI handle edge cases where it's not confident? Does it escalate to a human automatically or does it attempt a response anyway?
Freebuff
@ilya_lee Hey Ilya good questions! Right now our AI just surfaces the task for you to approve in 1 click. It never executes anything without approval. Def want to graduate to full send soon though, for easier tasks!
Good one @darweenist I want to ask if there is a provision for seamless migration from existing support platforms to Letterbook. This will be a game changer for companies with large user database on their existing platforms instead of starting over. The homepage could also do with some relevant FAQs. Good luck with the launch.
Freebuff
@bhadmus_olaide Thanks so much for the feedback! Right now we the founders just hop in a Slack channel and help you migrate manually. We could definitely make it more seamless, like one click to migrate from Zendesk would be huge.
Tidy
So cool. Is it possible to close the loop from tickets -> code?
Freebuff
@aagam_dalal Right now we just add a Linear ticket, but this is the natural next step!
Tidy
@darweenist linear ticket is perfect; we basically use linear tickets as our task queue for both agents and humans!