Rippling needs to improve their support stream.
Wanted to share some feedback in case it's useful, and in case others have run into the same thing.
We have a business-critical integration (Time API) that's central to how our company operates. When we hit an issue, we opened a ticket and that ticket ended up spawning a second one to isolate part of the problem. That's reasonable in principle, but nobody told us it happened, so for a while we were responding on one case that had actually been handled under a separate case we didn't know existed. It created a lot of avoidable confusion.
The bigger pattern is ticket continuity. Over the course of this one issue, we've worked with four different support people. Each time a new person picks it up, a new thread gets created, they reply only to me (despite my team needing to be looped into this issue to solve it), and the prior context doesn't carry over. So I've ended up manually copy-pasting the full history each time just so my engineers have something to work from. When an issue is time-sensitive and business-critical, that overhead adds up fast.
I understand support is a hard thing to run, and it's likely that no single person owns a ticket end-to-end, but that seems to be the root of it. Without clear ownership, each handoff starts over from zero and the critical people get dropped. Especially when Rippling uses Salesforce to manage this, it just screams of a bad implementation and management.
The product itself is great when it's working. My ask is simple: better thread continuity and clearer ownership when a ticket changes hands, so customers aren't the ones holding the context together.
Has anyone else run into the thread-continuity issue? Curious whether this is common or specific to our setup.