TipTap
Customers tip support agents that help them the most
Start new thread
Dan Vuckovic

TipTap - Customers tip support agents that help them the most

by
TipTap
•
TipTap lets customers tip the support agents who helped them - directly, after a great interaction. We plug into any existing helpdesk like Zendesk, Intercom, Freshdesk, etc. and add a tipping flow at the end of resolved tickets. Customers who had a great experience can leave a tip. Agents earn extra income. Companies retain their best people. Zero cost to the company. No restructuring. No salary changes. Just happier agents and better internal metrics.

Add a comment

Replies

Best
Dan Vuckovic
Maker
📌
Hey Product Hunt! 👋 I'm Dan, Co-founder of TipTap. After working as a support agent for 5 years and experiencing how badly customer support agents are treated, I built TipTap. Long hours, low pay, high pressure, and almost zero recognition when they do something great. The result? Brutal turnover. Companies spend thousands replacing agents constantly, and the ones who stay are burned out. TipTap fixes this in the simplest way possible. We let customers tip the agents who helped them, right after a resolved ticket. It plugs into any helpdesk you use like Zendesk, Intercom, or Freshdesk with zero cost to the company and no workflow changes needed. Agents earn real extra income. Companies keep their best people. Customers feel good about rewarding great service. We're live and would love your feedback, especially from anyone running support teams or working in CX. What would make this a no-brainer for your team?
Oliver Hayes

Does adding a tipping step after resolution risk making the support experience feel transactional?

Taimur Haider

@oliver_hayes1 I think this only feels transactional if the tip is positioned as payment.

Djordje Popovic
Maker

@oliver_hayes1 The framing matters more than the mechanic. Tip prompt only appears after the ticket is solved, never during. It's positioned as a thank-you, not a fee. Fully optional, no follow-ups. If we ever saw it shift CSAT down, we'd reconsider. So far it's gone the other way.

Miles Anthony

How do you prevent bias where only certain types of issues or customers lead to higher tips?

Djordje Popovic
Maker

@miles_anthony2 Great question. Variance is real. Some ticket types (refunds, account saves) naturally generate bigger tips than password resets. Some customer segments tip more than others (US > EU, enterprise > SMB). We can't fully eliminate that and we don't pretend to.

What makes it workable in practice is that tips are supplemental, not core comp. Base salary still does the heavy lifting on fairness. We're adding upside, not redistributing the foundation.

Managers see tip distribution per queue and per agent. If certain queues are consistently low-tip, they can rotate assignments or use it as a staffing signal.

And the honest counterfactual: today, agents get zero financial recognition regardless of which queue they're in. Even a low-tip queue is a better earnings situation than the status quo. Variance beats nothing.
Let me know what your thoughts are on this.

Noah Bennett

I can see this working in small teams, but wondering how it scales in large enterprise support orgs.

Djordje Popovic
Maker

@noah_bennett5 The whole point of TipTap is that it auto-scales and stays out of the way. Install once at the org level and it works the same whether you've got 50 agents or 5,000. No per-agent setup, no manual ops burden. Nothing changes in your payroll, HR, or finance systems. Tips flow customer → Stripe → agent directly. The company is never in the money flow.

We're also finalizing SOC2 compliance so we can work with enterprises as well.

If you're at a large CX org and want to take a look, happy to chat.

Naomi Florence

Does this change how agents prioritize tickets if they know some interactions are more "tip likely"?

Djordje Popovic
Maker

@naomi_florence1 This is the right concern to raise. There are two scenarios we considered:

If tickets are auto-assigned: there's no cherry-pick surface. Agents work what the routing rules send them.

If the team uses a looser pull-queue setup: cherry-picking is already a pre-existing problem, with or without tips. Today, agents skim the easy tickets and leave the complex ones, the ones that actually need their best work, to sit in the queue. With TipTap, the incentive flips: the harder, more complex tickets are the ones that drive bigger tips, because that's where customers feel real gratitude. So if cherry-picking happens, it shifts toward the tickets nobody wanted before. That's a net positive.

Either way, it's manager-visible behavior. Queue distribution and SLA metrics surface it in the helpdesk. We don't think tips amplify the issue. Please let me know what you think.

Priya K

it's a great approach on the zero cos' model. i'm curious how you guys handle the payout logistics and tax reporting for the agents so it doesn't create extra work for our hr team. if that's automated, this is a 10/10. congrats.. @dan_tiptap

Dan Vuckovic
Maker

@priya_kushwaha1  Thanks so much Priya, great question! Payouts are fully automated. Agents receive their earnings biweekly, deposited directly into their bank accounts via Stripe. Zero work for your HR team.

On the tax side, Stripe provides all the necessary documentation so agents can handle their own filing seamlessly. And worth noting, in many countries like the US, tips are actually tax-free, which is a nice bonus for agents.