Case study

Parley's IT team cuts busywork by rebuilding workflows on Halyard

Highlights

  • 18 workflows folded into a single Halyard story
  • Build time down from seven weeks to ninety minutes
  • In daily use by IT infrastructure, support, cloud security, and solutions teams
PARLEY

“However many tools you swap out, Halyard stays exactly where it is.”

About Parley

Parley is a customer conversation platform built for support teams. More than 21,400 organizations use Parley to send over 430 million messages to their customers each month.

Executive summary

In 2021, Parley was looking for new ways to let employees automate their own processes. Their IT team landed on Loopwise and started building workflows with its recipes. A year in, they found that the pricing structure capped the team's ability to build, and that the platform's thin change-control story was becoming a real concern.

Enter Halyard, and the chance to fix the problem while trimming and consolidating their workflows at the same time.

The challenge

Marisol Ferreira, Parley's Director of IT, started her search with a long wish list in hand. Her team needed to automate workflows freely and safely. She also needed a pricing model that would encourage automation across Parley's teams rather than ration it.

And there was another hurdle. Parley had dozens of high-value workflows waiting to be migrated to whatever platform came next. They covered business processes like managing forwarding rules in Sundial Mail, syncing people from Tandem into Keyward, and automating hardware issue reporting and response. The migration had to be uneventful.

Halyard was able to cover every item on Parley's wish list, which included:

  • Role-based access control via Keyward SSO
  • A custom editor role without the ability to create or change credentials
  • Governance through mandatory change control on every story
  • All Loopwise recipes migrated to the new platform
  • An interface that IT infrastructure, cloud security, IT support, and solutions teams can all use
Why Halyard?

Marisol first came across Halyard in 2018 and, although she was impressed by the platform's potential, it couldn't meet her criteria at the time. But she kept a close eye on it and checked in regularly to watch it evolve. In 2022, she was glad to discover that Halyard appeared to offer the functionality she needed. Now it was time to put it to the test.

During the trial, Marisol and her team worked with Halyard engineers to convert a complex user-lifecycle management workflow — around 18 recipes — into a single Halyard story. It was a good example of the kind of consolidation they were after.

18 workflowsfolded into a single Halyard story
Full existing librarymigrated to Halyard
23 workflowsbuilt in five months
90 minutesto build workflows that previously took seven weeks
The impact

Parley's onboarding with Halyard went unusually smoothly, Devon Achebe, Staff Engineer, Information Systems, tells us. “We worked with Halyard engineer Priya to migrate all of our Loopwise recipes across. That process was genuinely easy. We were able to move things over and make a lot of the existing automations simpler along the way.”

“It's remarkable to be able to say, 'Halyard just does this for me.' I don't have to think about it. For me, that's the biggest benefit — it just makes my week lighter.”

Marisol was particularly struck by the speed of onboarding, the flexibility of the platform, and the hours it gave her team back.

In Loopwise, one story took seven weeks to build. In Halyard, it takes about ninety minutes. Marisol Ferreira, Director of IT

Parley is growing a culture of secure automation, using Halyard to remove barriers to entry.

Freedom to build

The previous platform's pricing structure didn't only limit Parley's ability to build — it created extra work for the IT team.

“For a long time we've had this goal of letting other people in the company automate their own processes, without waiting on engineers to have bandwidth,” Devon says.

“With Loopwise, every time anybody had an idea to automate something, it turned into a question for IT: is that automation worth another few hundred dollars a month? And I don't necessarily have the context for how important it is, or what it would do for the business. With Halyard, that isn't a conversation we have.”

The Halyard pricing model lets Marisol and Devon actively encourage teams to build efficiencies into their own workflows. “It reduces friction,” Devon adds, “and it lowers the barrier to picking the platform up in the first place.”

Tenant-wide change control

One potential downside of a wider team embracing automation is added security risk. “At Parley we're very security-minded, and we have a strong change-control mindset,” Devon says. “So we wanted to put in place the thing I've been calling no code as code. We deploy all of the infrastructure we manage, as an IT team, as code. We use a change-control pipeline through Rivet and Stonework to deploy anything we can as infrastructure as code.”

Historically, when they looked at automating processes, most tools didn't offer a high level of governance or change control.

“One of our requests for Halyard was the ability to enforce change control tenant-wide as a policy, which didn't exist before,” Devon explains. “We also asked for per-team event execution limits, as well as a separate limit for the test versus live environments. Halyard shipped a batch of those capabilities very quickly for us.”

Shifting from chatbots to Halyard pages

For Devon, migrating existing recipes to Halyard stories was a chance to rethink his team's workflows. “We drastically simplified a handful of our automations while we migrated them. Loopwise leans very heavily on chat-app integrations. In my opinion it's harder to design a bot flow than it is to design a Halyard page, by several orders of magnitude. And it was a little annoying, because they charge per bot. Whereas with Halyard you can have as many pages as you want.”

That overreliance on bots was increasing the team's alert fatigue, not reducing it. Devon adds that there were several examples of it in their recipes. “Managing forwarding rules in Sundial Mail on behalf of our users — that's another one that used to be a bot in Loopwise. Now it's just a simple, legible Halyard page.”

Top workflows

Let's look at a few of the critical and complex processes Halyard has helped Parley tighten up.

Employee lifecycle automation

Devon's favourite workflow is one that Halyard engineer Priya built during the trial: a user-lifecycle workflow he had previously built in Loopwise.

“This is an entire re-architecting of that workflow,” Devon explains. “And Priya just built it for us in a week. It ingests a JSON report from Tandem covering all of our workers, then uses the warehouse API to make SQL queries against HR data coming out of Tandem, and runs all sorts of complicated lifecycle automations in Keyward.”

Hardware issue reporting

Another workflow automates responses to on-site hardware issues. Say an employee wants to report a broken webcam in a meeting room: a QR code brings them to a Halyard page where they can file the issue.

“Then it opens a Parley conversation on behalf of the user, because our IT support team uses Parley for support. We're planning to integrate this with the calendar too, so it can move every event scheduled in that meeting room to another room, and stop the room being booked until IT resolves the hardware issue.”

Handle malware alerts with Sentrix, Assetly, Rivet, and Alertside

Receive Sentrix events by webhook, alert the security channel, look up endpoint metadata in Assetly and Sentrix, open Rivet issues for tracking, and escalate to Alertside to page on-call responders when the alert warrants it.

Tools

Sentrix, Rivet, Alertside, Hubbub

Community author

Devon Achebe at Parley

Import story
Look up endpoint metadata in Assetly & Sentrix, then match it to the employee who owns the device.
Open a Rivet issue as a durable record, post it to the security channel, and page on-call if unacknowledged.
Webhook
New Sentrix detection
Event transform
Set environment vars
HTTP request
Get endpoint in Sentrix
HTTP request
Get asset in Assetly
HTTP request
Create issue in Rivet
HTTP request
Post to #it-general

Security alert notifications

Devon also built a Halyard story that connects Sentrix, Assetly, Hubbub, and Alertside to automate security alert notifications. It receives webhooks from Sentrix, works out the severity of the issue, traces the relevant employee through Assetly, and requests more information from that person over chat. Depending on what they say, it can also page the security practitioner on call.

“This one, again, was migrated from a giant folder of stories in Loopwise into a single story in Halyard,” Devon explains. “It's a good way to reduce noise and add context to security issues that land on our endpoints.”

Embed Parley's story in your tenant with a single click.

Access request management

Before Halyard, Parley's access request management workflow ran through a chatbot, which Devon says only created unnecessary noise.

The Loopwise recipe required the IT team to supply information through that bot. “Whenever we wanted to add a user to the allow list for an app integration, we would have to message the bot and follow the steps there. That created friction and slowed our ability to do the task. We got rid of the bot altogether. It's simply a story in Halyard with no need for human interaction — we don't even need to use a Halyard page.”

Devon adds that the support from the Halyard team has been invaluable in getting these workflows up and running. “We get very, very responsive feedback and action from the team at Halyard,” he says, “so we're excited and happy to see that.”

What's next?

Teams at Parley hope to repeat recent successes by extending the use of Halyard across the organization. The IT team plans to migrate their Keyward workflows over in 2023, and there are projects in the pipeline for sales engineering and solution architecture teams, too.

With an interface that teams in IT infrastructure, cloud security, IT support, and solutions can easily use, Halyard is helping Parley build that culture of secure automation faster.

More case studies

nodeone
We used the tools we'd already bought, from Sentrix to Rangefind, far more effectively because we…
CytoLab
38 min saved per onboarding request
Cedar Ridge Labs
We'd been trying to build an automated report for three years, and now because of…
See all case studies

Built by you, powered by Halyard

Talk to one of our engineers about the ways your team can put Halyard to work this quarter.