Hey everyone, I’m relatively new here and to using Kling in our stack. I’ve been really enjoying the platform for the last three months, especially its data modeling features which integrate nicely with our existing SQL workflows. The clarity it brings to some of our complex event tables has been a game-changer.
That said, I’ve hit a bit of a snag recently that’s starting to affect our project timelines, and I’m wondering if others are seeing the same thing. When we first onboarded, the support was incredible—like, almost unnervingly fast. We had a minor issue with a schema sync, filed a ticket, and literally got a helpful, human response in under two hours. It felt like having a dedicated engineer on standby.
Over the past few weeks, however, that response time has... well, ballooned. My last two tickets, one about Python SDK connection pooling and another about a billing discrepancy, both took over two full business days to get a first response. The support itself is still knowledgeable and tries to help, but the delay is painful when you’re blocked on something.
I’m trying to figure out if this is just a temporary growing pain for them, or a new normal. Our team was considering doubling down on Kling for more critical data engineering pipelines, but this shift has made us a bit cautious. Has anyone else experienced this slowdown? For those who’ve been using Kling longer, have you seen support response times fluctuate before, and did they bounce back?
I’m really hoping this is just a phase—the product itself is so solid for open-source-friendly data modeling. But that support latency is tough when you’re in a pinch. Would love to hear the community’s experiences before we make our next commitment.
Yeah, seeing something similar here, actually. Got a quick reply on an onboarding thing back in January, but my last ticket about incremental sync behavior sat for a solid three days. Their docs are good, but when you hit a weird edge case, the wait is tough.
Are you on a paid plan? I'm wondering if they're just swamped with new users and the free tier is getting deprioritized.
Might just be growing pains, but it's definitely making me look at adding more logging/retry logic on our end to be less blocked.
That "unusually fast" support speed you saw at the start? Classic honeymoon period. It's vendor lock-in 101, get you committed with amazing service before the real costs kick in. Once you're integrated and dependent, the leverage shifts.
Two days on a billing discrepancy is particularly telling. That's their money pipeline, and they can't even respond quickly when they've potentially overcharged you. It's not just a scaling issue, it's a prioritization one. They've got your data and your queries, what's your recourse?
Your team considering scaling? Run the numbers on what a 48-hour support delay costs in developer hours blocked versus the platform's billed value. It might not pencil out anymore.
-- cost first
I've been tracking similar degradation across several cloud data platforms this quarter, and your point about the billing discrepancy is particularly acute. When support latency impacts finance or invoicing questions, it's often a leading indicator of internal resource allocation problems, not just overall volume.
You mentioned considering scaling your usage. Before committing, I'd recommend building an explicit cost model that factors in this new support SLA. Assign a realistic hourly rate for your blocked developers and model a few scenarios: what if 20% of your tickets now take 48 hours instead of 2? The platform's value often craters when you add the hidden labor cost of working around their slow responses.
It also raises a contractual question. Does your current service-level agreement specify a target initial response time? If it does and they're consistently missing it, that's a leverage point. If it doesn't, then this might be the new normal you're budgeting for.
Always check the data transfer costs.
That's exactly what caught my attention when we were evaluating them last month. The contrast between the onboarding hype and the actual support reality is a big red flag.
If you don't mind me asking, was the billing ticket resolved correctly once they finally replied? I'm trying to gauge if the quality of the fix is still there, or if that's degraded too.