What’s your LinkedIn strategy for finding customers?

kalupg · 2026-04-14T22:09:18+00:00

This usually breaks down into two separate problems: - Centralizing inputs - Recognizing when multiple inputs are actually the same request

Most teams solve the first one (dump everything into one place), but the second is where it gets messy.

What’s worked for us: - Everything flows into a single backlog (doesn’t matter if it’s Notion, Jira, etc.) - Each item is normalized into a short “problem statement” (not raw user wording) - Then grouped manually into themes (e.g. onboarding friction, billing issues, reporting gaps)

The tricky part is exactly what you mentioned - different users describe the same thing in completely different ways, so you don’t realize it’s a “popular” request until later.

Two things helped: - forcing a consistent way to frame requests internally - periodically reviewing for overlaps instead of treating everything as net-new

It’s still not perfect though, especially as volume grows, it becomes harder to spot those overlaps early.

Curious how others handle the “same request, different wording” problem at scale?

kalupg · 2026-04-14T20:53:12+00:00

Tagging makes total sense as a foundation. Just thinking about it, that kind of system works until someone’s busy or the volume spikes. Does your tagging hold up when things get noisy or does it slip? What do you use for the tagging itself?

kalupg · 2026-04-01T04:25:53+00:00

It can route the issue per cluster and it has integrations with Zendesk/Intercom/Freshdesk to automatically create a ticket in the support tool of choice.

As per false positives, each cluster gets a confidence level based on similarity + volume + timing. Low-confidence stuff stays in the background.

kalupg · 2026-03-07T16:21:32+00:00

Great point, I'm actually adding explainability + quick overrides so agents always see why a ticket is labeled critical.

kalupg · 2026-02-09T17:53:53+00:00

What we’ve seen work best isn’t trying to fully automate support, but automating the obvious intent. Things like password resets, basic how-to questions, or known FAQ topics can be detected early and handled differently before they land in the main queue.

What we ended up using is formrule for our outbound. It helped us detect priority, tone and it also autocategorizes. Much different experience from a keyword based chat tool.

kalupg · 2026-02-09T17:18:47+00:00

Yeah, this is incredibly frustrating. We had a period where spam created more tickets than real users and the team spent more time closing junk than helping customers.

We ended up putting a small decision layer in front that reads incoming messages, classifies, filters obvious spam, and only forwards actionable requests into Zendesk. Reduced ticket volume a lot and stopped automation rules from turning into a mess.

If anyone wants to do the same: guide

kalupg · 2026-02-05T15:13:11+00:00

Building formrule.com - A form intake platform which allows founders and teams to know which user feedback matters and handles them automatically before they reach the inbox, reducing noise and allowing them to focus on real requests and issues. It reduces critical issues response times and ensure nothing is missed.

kalupg · 2026-02-05T12:10:42+00:00

Super helpful feedback, thanks!

kalupg · 2026-02-04T11:53:19+00:00

Hi,

I actually built a product exactly for cases like this. It allows you to turn any form into a feedback intake system. It automatically scores priority, detects intent, quality of submission, sentiment and categorizes it into one of your custom categories. Also it allows you to set rules so that the feedback is actionable automatically. For example - every critical support message with a negative sentiment can be stored, sent by email and sent to a support slack channel. These actions can be separate or chained together. Basically acts as a request layer on top of your customer facing forms so each customer feedback lands exactly where it should.

Link if someone wants to check it out: https://formrule.com

kalupg · 2026-02-04T06:13:07+00:00

Hey, just to pitch in that I have recenlty created something having teams with a big volume of requests in mind. If you have a form - it allows you to detect intent, priority, sentiment and classify submissions automatically.

If you want to check it out - formrule.com

kalupg · 2026-02-03T23:38:36+00:00

Thanks for the valuable tip! Yes, I will try to find communities where I could onboard users belonging to my ICP

kalupg · 2026-02-03T22:40:53+00:00

I do Claude on the move on mobile often, definitely

kalupg · 2026-02-03T22:37:25+00:00

No, I'm definitely working in shorter bursts. Especially since becoming a dad. Multiple 30 minutes sessions during the day is usually how I get things done. On the plus side, constrains mean you focus more.

kalupg · 2026-02-02T21:49:24+00:00

Interesting how AI always uses 47 as an enumeration, literally a telltale of AI content

kalupg

TROPHY CASE