Managing chat flows was like finding a needle in a haystack.

Tools

Figma, Userbit, Miro, Optimizely, Hotjar

Team & Role

Lead Product Designer working with 1 PM, 1 Tech Lead, 3 FE Devs, 2 BE Devs, 1 UX Director, and 1 Tech Writer.

Timeline

Q1 2021 - Q2 2021

Tools

Figma, Userbit, Miro, Optimizely, Hotjar

Team & Role

Lead Product Designer working with 1 PM, 1 Tech Lead, 3 FE Devs, 2 BE Devs, 1 UX Director, and 1 Tech Writer.

Timeline

Q1 2021 - Q2 2021

Tools

Figma, Userbit, Miro, Optimizely, Hotjar

Team & Role

Lead Product Designer working with 1 PM, 1 Tech Lead, 3 FE Devs, 2 BE Devs, 1 UX Director, and 1 Tech Writer.

Timeline

Q1 2021 - Q2 2021

IMPACT

Empowered users to maintain cleaner workspaces by enabling the deletion of outdated flows, reducing clutter across active user accounts.

SCALE

Enhanced the experience for over 12,000+ active Chat Flow users, improving task completion rates and demonstrating the value of user-centric, scalable solutions.

COLLABORATION

Collaborated with a cross-functional team of 9 members, including designers, developers, and product managers, to deliver the feature within a 4-month timeline.

OUTCOME

Launched the delete feature that received a 90% positive feedback rate in user surveys and improved overall workflow efficiency for teams using the platform.

The Chat Flow project aimed to solve the issue of clutter caused by outdated flows in Clickatell's platform for automated chat experiences. Users struggled with managing clutter due to the inability to delete flows, resorting to workarounds like burying them in folders.

The solution involved creating a secure, simple flow deletion system with features like smart alerts for dependencies, sandbox safety checks, and admin approval to prevent errors.

Running observation test and collecting qualitative data

Wireframing and exploring ideas

Error Modal Prototype

When users try to delete a flow with dependencies, Chat Flow would do a check on potential errors. Users are then presented with a list of dependencies that need to be disconnected in order to delete the flow.

Modal Anatomy

Admin Approval Process Prototype

Once a user initiates a flow deletion, it’s not gone just yet! The request gets escalated to an Admin for a final review. Admins can then approve or decline the deletion, ensuring no critical dependencies are unintentionally removed.

Want to get in touch?

Email me at hello@chelms.ca

Follow me:

Chelms Varthoumlien © 2025

Designed and built using Framer

Want to get in touch?

Email me at hello@chelms.ca

Follow me:

Chelms Varthoumlien © 2025

Designed and built using Framer

Want to get in touch?

Email me at hello@chelms.ca

Follow me:

Chelms Varthoumlien © 2025

Designed and built using Framer