SocketLabs Onboarding Experience
Overview
As a UX/Product Designer, I led onboarding design for email senders at SocketLabs, collaborating closely with a developer-heavy team.
Problem
Analytics revealed that users would sign up to land on an empty dashboard and then abandon the platform altogether.
Role:
UX/Product designer
Product Discovery, Strategy, Research, Visual Design, wireframing, documentation handoff, QA collaboration, and clarity.
Collaboration
Marketing to bring more light to the new code libraries SocketLabs offered
Development to implement the design
QA testing
Approach:
Baseline User research was done as part of the discovery
Agile, Daily Stand up, 3 sprints, UX stays ahead of each sprint and follows up with QA Testing
I conducted interviews with several developers and system administrators to walk through the SocketLabs platform. These sessions revealed valuable details about the language users naturally use and the types of information they expect to see surfaced during onboarding.
“User Journey”
A key finding was that much of the friction occurred around sign-up and locating the API credentials needed for integration. Users wanted reassurance that SocketLabs provided the necessary tools and infrastructure before committing to long-term use. This insight informed design decisions around making credentials more transparent, accessible, and easy to verify early in the onboarding journey.
“Customers wanted reassurance that SocketLabs provided the necessary tools and infrastructure before committing to long-term use. “
To ground the design in real-world needs, I created personas based on interviews with developers across different experience levels. These personas highlighted variations in technical skill sets, preferred tools, and common pain points during the onboarding process.
By understanding how junior developers, senior engineers, and system administrators approach email integration, I was able to design an onboarding tool that feels more “turnkey” — reducing technical barriers, surfacing the right guidance at the right time, and ensuring a smoother path to successful setup for all user types.
Key User Objectives!
Defining the overall flow and User Objectives
When exploring SocketLabs’ onboarding, I identified three major steps in the user journey:
Sign Up & Provisioning – New users are onboarded with safeguards in place to prevent abuse from bad actors while still ensuring a smooth registration process.
2 Integration via API or SMTP – Developers need quick access to clear setup instructions. This step is often the biggest friction point, so I designed an integration screen with language-specific code snippets (PHP, C#, Python, Go, Java) to accelerate implementation.
3 Test & Authenticate – Users can send a test email immediately after setup, then are guided to configure SPF, DKIM, and DMARC records to fully authenticate their domain and improve deliverability.
“Each objective has smaller steps, such as adding a Sending Domain or multiple Domains. How many should we allow for the first sprint?” Users only need to or 3 to run a test.
Product Positioning
“What unique value can we offer that competitors do not?”
“We are the developer friendly service, and provide email expertise”
How does SocketLabs compare?
Comp Analysis
Across competitors, the biggest friction clustered around signup, provisioning, integration, and authentication. Some products reduced the barrier by delaying email verification, allowing limited/test sending before full approval, simplifying account creation, or breaking DNS configuration into smaller steps.
Others leaned on documentation, setup guides, or third-party integrations, but often pushed users out of the product to finish the job.
The Ultimate Opportunity
Make SocketLabs the fastest path from “I want to send email” to “my first authenticated email was delivered.”
I created a story map to identify the major steps in the SocketLabs experience and highlight where new features could provide the most value. Each stage of the journey included opportunities to reduce friction and increase confidence for developers
“Each objective has smaller steps, such as adding a Sending Domain or multiple Domains. How many should we allow for the first sprint?” Users only need to or 3 to run a test.
Expand and expose new code libraries for developers who want to integrate with SocketLabs
FIrst Round Rapid prototype
Get the Customer’s domain
Choose how to send email
API offers code libraries in a varity of languages; get a quick snippet of code and see how it works its like a quick sample.
First round Rapid Prototype for code integration
Give users a quick sample
Provide pathways for all email-sending audiences
Designing the Integration Experience
After mapping the overall flow and identifying the required pages, I quickly built a prototype to help developers get started with bulk email integration faster. To reduce friction, I placed the key integration components in two places:
Onboarding wizard – where users immediately receive their SMTP credentials and API code snippets as part of the setup process.
Dedicated integration pages – where the same resources are always accessible in context, so developers don’t need to dig through documentation or switch tools.
This approach ensured that critical setup information was surfaced at the right time and place, helping users move from sign-up to successful integration with minimal effort.
“We want the design to speak to the developers who integrate with our platform.”
Choose your language and start sending
In 3 Steps you users can see how our system works:
Users now have the tools and steps to start sending
Integration and test complete
IMPACT
Developer-Centric Bulk Email
To support developers integrating with SocketLabs’ email delivery API, The screen helps technical users quickly copy, customize, and test bulk email requests without digging through documentation. By presenting language options in a clear, tabbed layout with syntax-highlighted examples,].
Challenge:
After completing integration, many users were uncertain whether the system was correctly configured. This hesitation often delayed their first email send, which is a critical milestone for building trust in the platform.
Solution:
I designed custom iconography that clearly signals when SocketLabs is ready and awaiting the first email. This moment reassures users by validating that the server is functioning correctly while also creating an engaging prompt that encourages them to take the next step and begin using the platform.
Now users can send, but
Authentication
is what really improves deliverability
“Education, Help Documents for domain authentication instructions”
“To further reduce friction, I created step-by-step instructions and expandable troubleshooting drawers”
Domain Authentication Education
Challenge:
Authenticating a sending domain (via SPF, DKIM, and DMARC) is often treated as an afterthought by users, even though it’s a critical factor in email deliverability.
Solution:
I applied my infographic design skills to create concise, visually engaging explanations to illustrate the role of authentication in preventing deliverability issues. By surfacing this information at the right moment in the journey,
Integration & Authentication Support
Challenge:
Getting users to fully authenticate and integrate with SocketLabs is complex because many of the tasks (such as configuring DNS records) happen outside the platform’s direct control.
Solution:
To further reduce friction, I created step-by-step instructions and expandable troubleshooting drawers, giving users contextual guidance without overwhelming them.
users need a way to track Engagement…. Opens …. Clicks
Rapid Prototype on Engagement Tracking Setup
Driving First-Email Engagement
Challenge:
During onboarding testing , some users were dropping out of the wizard before completing integration or sending their first email. This created risk of churn, as they never experienced the value of the platform.
Solution:
I introduced a setup status module on the dashboard to clearly show users what steps were remaining. I also added placeholder charts for email reporting, paired with a strong CTA — “Send your first email to see your reports.” This created a visual incentive and guided users toward completing their first send, turning onboarding into a momentum-building experience.
Onboarding can be lengthy and confusing. Here is a way to keep track of the steps:
Onboarding and Authentication Status bar
