
What I value most about Xirsys is that it solves a problem I didn't even know HR operations had until we started running remote onboarding sessions for clients in Alberta and BC.
Our firm handles end-to-end HR outsourcing, and a big chunk of that is conducting remote onboarding and exit interviews for mid-market manufacturing and retail clients scattered across provinces. We kept running into connection failures—candidates on mobile networks, employees behind restrictive corporate firewalls, or people joining from rural areas with spotty internet. The video would freeze, audio would drop, and my team would spend twenty minutes troubleshooting instead of actually talking to the person. That's a terrible first impression for a new hire.
Xirsys provides the underlying STUN/TURN infrastructure that makes those WebRTC connections actually hold up across messy real-world networks . What I appreciate is the API-first approach—my IT partners integrated the credential system into our existing scheduling workflow without ripping out anything. A concrete example: last quarter we ran exit interviews for a manufacturing client in rural Alberta, and several participants were joining from locked-down corporate devices. Before Xirsys, those sessions would have been a coin flip. Instead, the relay fallback kicked in automatically, and we completed every interview without a single dropped call. The audit trail from the channel usage reports also helped when the client's compliance team asked how we protected PIPEDA-sensitive conversation data during transit.
The pricing model makes sense for a 51-200 person firm like ours. Direct peer traffic stays free, and we only pay for bandwidth when the network genuinely forces a relay . That's not a sales pitch—it's just how it's structured, and it means our monthly spend doesn't spiral when a client has a bad network week.
It's not a flashy platform. Nobody outside IT ever notices it's running. But for an HR ops manager who just needs onboarding calls to work the first time, every time, that invisibility is exactly the point. Review collected by and hosted on G2.com.
My biggest gripe with Xirsys comes down to the administrative overhead when managing access across multiple client environments. We run highly segmented onboarding and exit interview workflows for distinct manufacturing and retail partners in Ontario and Alberta. Because our HR coordinators rotate frequently between these accounts, I need to provision and revoke credentials constantly to maintain PIPEDA compliance.
The platform’s dashboard lacks robust native support for bulk identity management. Last month, I had to manually update permissions for fourteen different temporary HR contractors who were transitioning off a specific retail client's project. Instead of a streamlined SCIM integration or a straightforward CSV upload tool, I had to click through each individual profile to adjust their specific channel and region access. It was tedious, error-prone, and frankly, a waste of my team’s time. We eventually had to loop in our internal IT partners just to build a custom script using the management API, which shouldn't be necessary for a routine offboarding task.
Furthermore, the documentation surrounding regional edge node selection feels remarkably sparse. When we were setting up a new remote onboarding pipeline for a client with staff spread between urban Toronto and rural parts of Alberta, I wanted to ensure we were routing traffic through the most optimal data centers to prevent latency. The technical guides gave me a very superficial overview but didn't provide the deep-dive metrics I needed to make an informed architectural choice. I ended up relying on trial and error during live test calls to figure out which regional configurations actually performed best for our specific geography.
Finally, the reporting interface, while functional for basic bandwidth tracking, is incredibly rigid. I often need to extract telemetry data to prove to a client's compliance officer that we maintained secure, localized routing for sensitive HR discussions. The standard export options don't allow for custom date ranges or specific data filtering. I usually have to pull the raw data and spend time reformatting it in Excel before I can even present it.
None of these are dealbreakers—the underlying relay infrastructure is rock solid, which is why we stay. But the administrative friction and shallow technical documentation definitely create unnecessary speed bumps for an HR operations team that just wants to keep things moving. Review collected by and hosted on G2.com.