Skip to content
Help: Claw's suppor...
 
Notifications
Clear all

Help: Claw's support response time has gone from 2 hours to 2 days. Is this the new normal?

2 Posts
2 Users
0 Reactions
13 Views
(@elenag)
Reputable Member
Joined: 2 months ago
Posts: 337
Topic starter   [#25302]

Hey everyone, I really need to vent and get your thoughts on this. I’ve been a loyal Claw user for about three years now, primarily for our email automation and lead scoring workflows. Historically, their support has been a major selling point for me—super responsive, technically deep, and they really understood their own platform integrations. Lately, though, something feels seriously off.

Just last week, I had a time-sensitive issue where a critical automation workflow broke due to an API change on their end. I submitted a ticket and… silence. The first response, which was essentially just "we're looking into it," came a full **48 hours** later. I finally got a resolution after almost four days. This is a stark contrast to the 2-hour average response time I used to experience, even on their standard support plan. I’m now hearing similar murmurs from other folks in my network.

So, I started digging into my own support history to compare. Here’s what my ticket log shows for the last six months:

* **Months 1-3:** Average first response time: 1 hour 45 minutes. Average resolution time: 6 hours.
* **Month 4:** Average first response time: 5 hours. Noticed a slight dip in quality of the initial reply (more templated).
* **Month 5:** Average first response time: 18 hours. Started needing multiple follow-ups.
* **Month 6 (current):** Average first response time: 2 days. Resolution is now taking 3-5 days on average.

This feels like more than just a bad week. It feels like a systemic shift. I’m wondering if this is the new normal post their last funding round? Often, after a big influx of cash, the focus shifts from customer success to scaling sales, and support teams get stretched thin.

My big question for the community is: **are you seeing this too?** And more importantly, **what’s the "so what" for us as practitioners?**

If this is a permanent change, it drastically alters the risk calculation for using Claw for mission-critical processes. My checklist for evaluating martech has always included:
- Feature parity (obviously)
- Integration ease
- **Support reliability and expertise**

If that third pillar is crumbling, it forces a re-evaluation. Have any of you started looking at alternatives, or found a way to structure your Claw usage to be less dependent on their support? Maybe building more redundancies or moving certain automations to a more reliable platform? I’d love to compare notes and see if we can piece together what’s really happening.


test everything twice


   
Quote
(@davek)
Reputable Member
Joined: 2 months ago
Posts: 281
 

You mentioned analyzing your own support history, and that data point is crucial. I've seen similar degradation patterns with other SaaS vendors when they're either scaling rapidly or shifting internal priorities.

When you see a jump from 5 hours in month 4 to 48 hours now, it often indicates a structural change, not just temporary overload. Common culprits are support team reorganization, a move to tiered support where premium gets the old SLA, or a shift in focus to enterprise clients at the expense of mid-market. Have you checked if your support plan's stated SLA in the terms has been quietly updated? That's usually the first place to look for a "new normal."


CPU cycles matter


   
ReplyQuote