April 8, 2026 · Updated September 5, 2026
RPA Studio became Relay because the work mattered more than the automation category. The name reflects a familiar agency pattern: information arrives, someone prepares the next step, and a colleague or client makes a decision.
This is the story of that name change. For current product capabilities and access, use the Relay platform overview.
A name built around the handoff
An insurance workflow rarely ends with one click. A prospect sends dec pages. The team confirms what changed, prepares applications, reviews carrier results, and explains the options. A certificate request or renewal question begins another sequence.
Relay is a name for that movement between people and tasks. The agency stays responsible for the relationship. The product helps prepare work the team can inspect and use.
From an automation label to an agency workspace
RPA described one technical approach. It did not describe everything an agency needed from the product: a useful starting point, visible work, a result worth reviewing, and a clear next action.
The workbench brings that idea to client documents, applications, proposals, certificates, client-file questions, and configured browser workflows. Availability depends on the specific task and connections. The current product pages explain what to bring and what to review.
What the name should stand for
Approachable work does not mean hiding the details. An agency should be able to see where information came from, which answers are missing, and what has been prepared. A familiar document or a visible browser task communicates more than a promise about AI.
That is the standard behind the Relay name: help the team carry the next piece of client work forward.
If you knew us as RPA Studio, start with how Relay works and the current getting-started page. Existing customers should use their agreed access and support arrangements for account-specific questions.