Integrating Enlyft with Slack and Teams
Overview
About the Company and Project
Enlyft helps businesses discover new customers by providing access to data on millions of companies and their employees.
One of its key value drivers is surfacing key buying signals such as visitor tracking, intent, and general news related to companies like Hiring activity, announcements etc.
However, users were only receiving these insights via email, which often got buried or delayed.
This case study explains how we brought those signals into tools our users already live in: Slack and Microsoft Teams.
My Role
As the sole UX Designer, I owned the project end-to-end, collaborating with the Lead PM and engineers. My responsibilities included research, ideation, prototyping, and delivering the final UI.
Problem
Enlyft surfaces rich information like Visitor Tracking, Buying Signals and Buyer Intent — but there was a gap in how these insights reached users.
Users had to:
Check email notifications.
Monitor the Enlyft app for updates.
Manually stay on top of active accounts.
This fragmented flow reduced the timeliness and impact of our most valuable insights.
Why Slack and Teams?
Most of Enlyft's customers already use Slack or Microsoft Teams as part of their daily workflow — often receiving updates from CRMs like Salesforce & Dynamics directly within those platforms.
Integrating Enlyft notifications into Slack and Teams made the most sense because it:
Fits seamlessly into users’ existing communication tools
Increases visibility of key signals
Requires no learning curve or context switching
Project Scope and Constraints
Integration flows for Slack & Microsoft Teams
Notification messages using Slack Block Kit and MS Adaptive Cards
Notification preferences UI in Enlyft
Marketplace content and help articles.
Constraint: Authentication flows and Message design had to follow native component guidelines of Slack and Teams.
Design Process
Step 1 - Understanding Platform Constraints
Researched how Slack and Microsoft Teams handle third-party app integrations and authentication flows.
Studied Slack Block Kit Builder and Microsoft Adaptive Cards to understand visual and interaction limitations.
Step 3 - Defining User Flow & Preferences
Mapped out a seamless flow for users to connect their Slack/Teams accounts within Enlyft.
Designed a new Notification Preferences section in the Enlyft profile page to give users control over which alerts they receive and where.
Step 4 - Creating Supporting Assets
Welcome message post app install
Marketplace content (App description, visuals, metadata)
Help center articles for setup and troubleshooting
Step 5 - Handoff, Testing & Publishing
Collaborated with engineering to ensure accurate implementation across platforms.
Submitted the Slack and Teams apps for approval and prepared documentation for internal QA.
Currently being tested internally and awaiting approval.
Success Metrics
Connection Rate: % of users connecting Slack or Teams
Engagement Rate: Avg. CTR on Slack/Teams messages
Response Time: Time between receiving notification and user action
Churn/Drop-off: % of users disabling notifications
Key Learnings
While this project didn't involve redesigning a product from scratch, it taught me the importance of:
Designing within technical constraints (especially third-party platforms)
Thinking beyond UI — success required clear documentation, content, and communication design
Minimizing friction for users — just making something available where they already work can unlock major adoption gains
As this rolls out, we expect higher engagement with key Enlyft signals — especially from teams who rely on Slack and Teams as their daily workspace.