Proactive Messages

Our customers wanted the ability to send personalized and targeted messages that anticipated their customers’ needs well before they had to ask for help. We built an experience that allowed them to do just that.

Our customers wanted the ability to send personalized and targeted messages that anticipated their customers’ needs well before they had to ask for help. We built an experience that allowed them to do just that.

Our customers wanted the ability to send personalized and targeted messages that anticipated their customers’ needs well before they had to ask for help. We built an experience that allowed them to do just that.

Role

Lead Product Designer

Team

Product Designer Product Manager Engineering Coach Frontend Engineers x 2 Backend Engineers x 2 QA Engineer

Skills

Product Design, UI + UX User Research QA + Testing Full Feature Delivery

Duration

Jan 2021 - Oct 2021

Help Scout's Messages feature was originally designed as part of Beacon, our self-service widget, making Messages limited in its scalability and flexibility. Our research also showed that key aspects of the user experience that were not meeting our customers' expectations, and therefore affecting their willingness to pay for Messages as an add-on. To address the technical limitations, we moved Messages out of Beacon and into its own application, allowing the feature to scale more effectively. This also allowed us to make vast improvements to the overall experience. We simplified the entire setup flow while still delivering powerful features, like targeting and scheduling—making it easier and more enjoyable for our customers to create, send, and manage effective messages.

Managing Messages

With the growth of the feature and the introduction of usage-based pricing, we needed to provide customers with a better way to track the usage and performance of their Messages. I designed the new dashboard to clearly show top-level performance metrics for all Messages within a billing period, as well as increased visibility into individual Message performance. The new dashboard now shows Message statuses, which we also established during this project. Customers are now able to take various actions right from the dashboard, such as pause, resume, copy, and delete. We also provided a Message preview, so they could quickly reference a Message before diving in to edit or view reporting. The ability to filter, search, and sort was de-scoped. This work was planned as a fast-follow, but ultimately has not been implemented due to changes in priority. I also would have liked to build the ability to archive Messages that were no longer being run.

Building a Message

A Message may look simple on the outside, but they're designed within a builder tool with powerful features. The existing builder had a great foundation but was still missing support for scheduling, renaming, drafting, or a clear way to pause and resume the Message. Because we also had to move the builder from another part of the app, I redesigned the information architecture to better stand on its own and support the introduction of those needed features. The navigation bar was a newer, more conceptual component which earned a spot in our design system, supporting the editing experience for our Docs product. We removed the "forced" step-through to allow our customers to work on drafts. Instead, we moved the summary to a side panel that included a clear checklist, eliminating any anxiety our customers had previously felt when launching a Message. Our most requested feature was Message scheduling. I kept an easy option to quickly start running a Message alongside opt-in complexity of setting more defined time and date parameters.

I led all design on the Messages team and conducted user research alongside our PM. I contributed to the overall strategy, scoping, and timeline for the project. It was my responsibility to bring designs back to the product design team and synthesize feedback across all key stakeholders. We worked cross-functionally with the Growth team to ensure our work was in sync, as Messages was changing to usage-based pricing. This required significant in-product design collaboration to ensure customers knew what they'd be billed for. I collaborated closely with our engineers for the entirety of the project, keeping a "Work-In-Progress" document updated and recording Looms to make sure everyone stayed on the same page. We all worked in sync to deliver the new experience, delivering value to customers and launching successfully.