Help That Knows the Product

By Junaid Ahmed

---

I clicked my own Help button to test something.

I asked it how to add a guest.

It told me to go to a Contacts section.

There is no Contacts section.

---

The Help Button That Didn't Know Me

PodGlue has had a little Help button in the corner of every screen for a few months now. You click it, a window opens, you ask it something, an AI answers. Friendly. Confident. Often wrong.

I had been telling people this was useful. It was useful the way a confident stranger at a train station is useful. They will absolutely point you somewhere. There is no promise the platform they sent you to exists.

It knew nothing about PodGlue. It knew how to give numbered steps. It did not know what tabs we have, what Auto-Pilot runs, where Neural Sync lives, what the Episode Planner is actually for.

So it guessed.

You can tell when a podcast guest is faking expertise. Eight minutes in, the words still sound right, but nothing is being said. Software does the same thing. And when it does it inside a product somebody is paying for, the cost goes up.

---

The Answer Was on the Shelf

The annoying part is that we already had the answer written down.

Fifteen guides at podglue.com/docs. Quick Start. Episode Management. Guest Management. The Book Builder. Brand Voice. Integrations. Eighteen thousand words. Written by me and the team. With screenshots. Kept up to date.

The Help button could not see them.

It was like running a customer call from memory while the binder of right answers sat on the shelf behind the chair.

---

What I Changed

When you click the Help button now, before anything else happens, it goes and reads our guides.

It looks at the question. It looks at the screen you're on. It picks the two guides most likely to contain the answer. It hands them to the AI with one rule: answer only from these. Cite the guide. If the docs don't cover it, say so and send the person to the docs. Don't invent anything.

That last rule is the one I care about.

The Help button is now allowed to say I don't know. It's required to. When the docs don't cover something, it tells you, and it sends you to where a human actually wrote the answer.

No more Contacts section.

---

What It Feels Like Now

Ask it how to add a guest, and the answer comes from the Guest Management guide with a link straight to that guide.

Ask it about something we haven't documented yet, and it tells you the truth. We haven't documented it yet. Here's the docs page. Here's the feedback button. I'll see it.

Truth instead of theater.

---

Why I Cared

I have notes somewhere with thirty-something home studio backdrop configurations. Not because I'm obsessive, though maybe a little, but because I refuse to waste a podcaster's Saturday with a bad background image.

A Help button that quietly guesses wastes the same Saturday in a different way. You came in to do real work. You hit a wall. You asked for help. The product lied to you confidently. Now you've spent twenty minutes chasing a Contacts section that doesn't exist instead of recording the episode you actually came here to make.

That's not a software bug. That's a respect problem.

---

What I Believe About Help

PodGlue is built around a simple belief: the conversation you have with your guest is worth tending.

The conversation a user is having with the product when they're stuck is part of the same conversation.

A Help button that confidently makes things up is not tending anything. A Help button that knows the product, cites the docs, and admits when it doesn't know, that's a small thing. But small things compound, and most of what makes a product feel trustworthy is the absence of small lies.

I kept waiting for the Help button to start working the way I wanted it to. It didn't.

So I built it.

---

Junaid Ahmed is the host of Hacks and Hobbies and the founder of PodGlue.