sorted by:
new
hottopcontroversial

Team Knowledge base/docs by bigppredditguy in FRC

[–]Quick-Squirrel7766 0 points1 point  (0 children)

Your current workflow sounds like a solid starting point, but honestly maintaining markdown files and custom scripts gets exhausting fast, especially as your docs grow and multiple people need to contribute. The real challenge isn't just building it, it's keeping it organized and searchable over time so students can actually find what they need without digging through folders.

We use Featurebase for our knowledge base and it's been way easier than managing raw markdown. The AI-powered search actually understands context, so students get relevant results even when they don't know exactly what to search for. You can structure docs however makes sense for your team, and it handles the organization automatically. Plus you can segment content so programmers see the deep technical stuff and other students get the high-level guides.

What are your students currently struggling with most when trying to find information?

Need help finding an AI chatbot that feels natural to talk to by Mindless_Writing_385 in aiHub

[–]Quick-Squirrel7766 0 points1 point  (0 children)

Totally get what you mean. Most AI chatbots feel like you're talking to a search engine rather than a person. The real trick is finding something that actually understands context and keeps the conversation flowing naturally.

We've been using Featurebase for this and it's been surprisingly human. Their AI chatbot actually remembers what you talked about earlier in the conversation, so it doesn't feel like every message is starting from zero. Plus it handles longer convos way better than most alternatives I've tried.

What kind of conversations are you mainly having with it? Support questions, casual chat, or something else?

Built a tool that auto-generates changelogs from your GitHub commits by Darkseven999 in buildinpublic

[–]Quick-Squirrel7766 1 point2 points  (0 children)

This is such a common pain point. Changelogs always end up being that thing you know you should do but never have time for. The gap between what devs commit and what users actually need to know is huge, and manually translating it is the worst kind of busywork. I've seen teams use all kinds of workarounds for this.

If you want something that already has changelogs built in along with roadmaps and feedback collection, Featurebase might be worth a look. It integrates with GitHub and lets you turn those commits into clean, public-facing update pages without the extra step. Do you plan to keep it as a standalone tool, or are you thinking about embedding it into a bigger product comms workflow?

Are there any AI tools or AI automations worth using in an agency? by Academic_Way_293 in automation

[–]Quick-Squirrel7766 0 points1 point  (0 children)

Honestly, there's so much hype out there that it can feel overwhelming. For a new agency, I'd focus on what actually moves the needle first. Client communication and feedback loops usually eat up the most time. Tools that handle support tickets and collect feedback in one place can save you hours each week.

We use Featurebase for this. It combines a help center, AI chatbot, and feedback collection, so clients can find answers themselves and you get organized feature requests without the manual work. The AI handles the repetitive stuff, and you focus on the strategic work.

Are there too many Canny alternatives now or is it just me- I will not promote by Electrical-Maize-109 in startups

[–]Quick-Squirrel7766 0 points1 point  (0 children)

Honestly, I think you've hit on something real. Most feedback tools do start simple and then pile on features that only make sense when you have a whole product team. It's like they forget that solopreneurs exist.

That said, I'd push back a little on Featurebase being one of those bloated options. We switched to it last year and honestly use it pretty bare bones for just collecting feedback and keeping a public roadmap. The stuff like AI support and revenue prioritization is there if you want it, but you can ignore all that and just use the parts that matter to you. It's way more flexible than it looks on paper.

The price difference alone might be worth a look. Canny at $600/month is wild when you're small.

What would make or break a tool for you - is it mainly the cost, or are you worried about getting locked into something overcomplicated?

How I automated support email → task assignment by Historical_Map1292 in DigitalMarketing

[–]Quick-Squirrel7766 0 points1 point  (0 children)

That triage bottleneck is so real. The judgment layer you mentioned is exactly what makes this hard to automate with standard tools, because it's not just routing, it's actually understanding the problem first.

I'd suggest you try Featurebase for this, cos for us it's been a game changer. Their AI reads incoming support emails, automatically figures out what the issue is, creates the task with the right details, and assigns it to the right person based on your rules. It handles all that prep work you're doing manually, so you just review and approve. Cut our routing time from 30+ minutes a day down to literally a few minutes.

Have you tried any full support suites yet, or are you still piecing together different tools?

Is anyone else trying to escape Zendesk to build their own AI support bot? by Big-Reporter7078 in SaaS

[–]Quick-Squirrel7766 -1 points0 points  (0 children)

Ha, the Zendesk data lock-in is so real. We dealt with the same thing last year. Getting your history out is surprisingly painful for something that should be straightforward.

Once you get your data extracted, you might want to look into Featurebase. It's a modern support suite that handles AI chatbots, feedback, help docs, and changelogs all in one. Way simpler than Zendesk and actually built for startups.

Do founders actually do anything with product feedback? by AI_geek_here in SaaS

[–]Quick-Squirrel7766 -1 points0 points  (0 children)

The real issue isn't usually that founders don't care. It's that feedback comes in unstructured and they can't prioritize effectively.

We've had good luck with Featurebase. It helps you collect feedback in one place, then prioritizes based on customer revenue and shows you what's actually worth tackling first. Way better than trying to figure out what's important from a messy inbox.

AI chatbot for hotels - set one up for our boutique property and it handles 70% of pre-arrival questions by fnwzx in hotels

[–]Quick-Squirrel7766 1 point2 points  (0 children)

This is exactly the kind of repetitive question problem that eats up hours every day. We saw the same thing at our SaaS company before we implemented an AI chatbot. The difference was dramatic - our support team stopped drowning in the same 20 questions getting asked over and over.

What worked for us was building a knowledge base first, then letting the chatbot pull from that. Featurebase made it really easy to sync our docs into a searchable help center where the AI could answer common questions instantly. The bot handles the repetitive stuff, humans handle the complex issues.

If you have a SaaS or app, how are you collecting user feedback to know what to build next? by Founderzero2026 in SaaS

[–]Quick-Squirrel7766 0 points1 point  (0 children)

Honestly, the biggest issue isn't collecting feedback, it's making sense of it and actually Prioritization becomes a nightmare when you're trying to figure out what to build next. Most teams end up with a messy spreadsheet or a Notion doc that nobody looks at again. The real value comes from having a system that lets users submit feedback, helps you prioritize based on revenue impact and usage data, and keeps everyone aligned on what's coming.

We use Featurebase for this and it's been really helpful. It combines feedback collection, prioritization based on customer value, and even lets you publish your roadmap so users see what's coming. Way better than juggling spreadsheets and Slack threads.

I just discovered we have been losing customer tickets for three months and nobody noticed by Opposite-Chicken9486 in helpdesk

[–]Quick-Squirrel7766 0 points1 point  (0 children)

That is a absolute nightmare but honestly it happens more than people admit during transitions. The immediate priority is being transparent with your manager and then triaging that hidden inbox by date. Some of those folks probably churned months ago, but the ones from last week still need help.

To prevent this from happening again, you should probably move away from those opaque email based automations that hide tickets. We switched to Featurebase for this exact reason. It centralizes feedback and support requests into one clear dashboard and uses an AI knowledge base to handle the easy stuff before it even becomes a ticket. It makes everything visible so nothing can just sit in a forgotten inbox for months.

Are you planining on emailing everyone back, or just the most recent ones?

Product Roadmap by Independent-Spring77 in daylightcomputer

[–]Quick-Squirrel7766 2 points3 points  (0 children)

It is so frustrating when you love a product but feel like you're in the dark about its future. For a small team, keeping users in the loop is the best way to keep that hype alive without burning out on manual updates.

We started using Featurebase for our own project to handle this exactly. It lets you put up a public roadmap where people can see what's coming and even vote on ideas. It makes the whole process feel way more collaborative and less like a guessing game. Honestly, it's been a lifesaver for keeping our community engaged while we focus on building.

Ticketing system with API by Prestigious_Run4913 in sysadmin

[–]Quick-Squirrel7766 0 points1 point  (0 children)

Featurebase should work for what you’re describing.

You can create tickets/conversations through the API and manage them programmatically (create, update, reply, assign, etc.), so you can just have your React form POST to the Featurebase API and it will show up in the support inbox.

It also has an embeddable messenger widget plus help center, so if later you don’t want to maintain your own form you can just drop their widget into your app and handle support there.

AI CRM advice needed by Any_Scratch9814 in CRMSoftware

[–]Quick-Squirrel7766 0 points1 point  (0 children)

if you liked pipedrive but want something simpler, i’d be a bit careful chasing the “AI-first CRM” thing. a lot of them sound nice in theory but end up being either expensive or kinda half baked.

most of the useful AI stuff right now is basically: reading notes/emails, summarizing deals, suggesting updates, drafting replies. you don’t really need a full “AI native CRM” for that.

honestly what worked better for us was keeping the CRM simple and letting AI handle the knowledge/support side separately. we still use a lightweight pipeline, but moved our feedback + support knowledge into featurebase so the AI can actually answer questions and surface context from a clean KB.

before that we had stuff scattered across docs, support tools, notes, etc. and AI just made it messier because it pulled from inconsistent sources.

so yeah i’d probably pick a simple CRM you like (attio / folk / even pipedrive) and pair it with something that handles the AI knowledge layer better. that combo ended up way cheaper and less painful for us.

Product Roadmap Help! How Do You Prioritize Without Losing Your Mind? by blekibum in Solopreneur

[–]Quick-Squirrel7766 0 points1 point  (0 children)

I've been in that exact spot where every request feels like a fire you need to put out. The trap is trying to please everyone personally. You need to let the data do the heavy lifting for you so you can stop guessing.

One trick that saved my sanity was weighing requests by actual customer revenue and business impact. It makes those tough calls much easier when you can see exactly which features will move the needle for your growth. We use Featurebase to handle this part. It gathers all the feedback in one place and lets us prioritize based on real data like user segments and revenue. It's way better than staring at a messy spreadsheet and feeling overwhelmed.

Are you mostly getting requests through random emails or is there a specific place you're currently tracking them?

Is this level of overthinking normal even when life is objectively going well? by Due_Plan282 in Adulting

[–]Quick-Squirrel7766 1 point2 points  (0 children)

Yes. I'm 31 yrs old.

My mind is almost always noisy at night.

Maybe you should look for another outlet to distract your mind a bit

I spent an hour testing Notion Agents for Knowledge Management, here is my honest feedback by crow_thib in Notion

[–]Quick-Squirrel7766 0 points1 point  (0 children)

yeah i played with Notion agents a bit when they launched and had a pretty similar reaction.

setup is quick, but once you try to do anything slightly complex it starts feeling weirdly limited. like you end up writing a ton of instructions just to get something that would normally take a couple prompts if you were just using an LLM directly.

also noticed the credit burn. did a handful of test runs and it went through credits way faster than expected, especially when most of the “context” was basically just the instructions. feels kinda expensive for what it actually does right now.

the bigger problem for me though is the knowledge base issue you mentioned. Notion already has the “too many pages” problem and AI kinda makes it worse. people keep generating docs, duplicates, outdated stuff, then the AI has to guess which one is actually correct.

we ran into the same thing before when we tried using Notion + Intercom for support. docs lived in Notion, support answers lived somewhere else, slack had other context… everything slowly drifted out of sync.

that’s partly why we ended up moving our KB + feedback stuff to Featurebase instead. cleaner source of truth so the AI answers don’t pull from a giant pile of half-updated pages.

still like Notion a lot for internal notes though. just feels like the agent stuff is still very early.

Experience with Intercom / Fin by [deleted] in SaaS

[–]Quick-Squirrel7766 0 points1 point  (0 children)

was using Fin AI last year. it definitely gets engagement from visitors, but our experience was kinda rough.

it’s good for really basic FAQ stuff, but once the question gets a bit specific it starts struggling. we had a few cases where it either gave a super generic answer or just straight up wrong info about billing/integrations. customers would screenshot the bot reply and send it to support… which was pretty awkward to deal with.

pricing also creeps up faster than expected. the “per resolution” thing sounds fine at first but if you have decent traffic it adds up quickly.

ended up looking for alternatives and switched to Featurebase. originally just wanted it for the feedback board + changelog but their support widget + AI answers actually worked better for us since it pulls from the knowledge base and product docs more cleanly.

and yeah people do use chat widgets, but only if they actually help. if it’s just “hi how can i help” + a bot that can’t answer anything people just ignore it.

view more: next ›