In this session of Implementation Stories, we take you through our hour-long discussion with Jharna Moorpana who handles customer onboarding at WebEngage, a B2C marketing automation solution for enterprises. As someone who started her career as a customer support executive with WebEngage in 2016 and now works as an Onboarding Manager, Jharna has had an inside view of WebEngage’s customer success journey and the huge role that onboarding has to play in it.
She talked us through their onboarding approach while telling us how they handle complex integrations, demanding customers, growing startups, and the works. In this article, we share the key takeaways from her session — with additional inputs from implementation folks at Freshworks, Pando, and InstaSafe.
Let’s dive in.
In the early years, WebEngage started its post-sales journey with two teams: Customer Support and Customer Success. At roughly the one-year mark, two things began to happen:
This impacted their conversions and the adoption of the product. That’s when the team decided to separate the two areas: a dedicated function for onboarding, and another for business growth and strategizing with the accounts. This way, issues could be caught on time and addressed with the attention and detail they needed, so that Customer Success Managers (CSMs) could focus on expansion and growth.
They began with a few small MRR & low touch accounts, but now this approach applies to all their clients — low MRR and enterprise clients.
Speaking about the initial phase of their journey, Jharna shared that their approach was still rather ad-hoc — though there was a rigid first call, there was little personalization and focus on processes. Since then, they have worked to get things streamlined — through defined timelines (4–6 weeks) and processes — including a well-designed first call with a predefined set of questions for every business, project trackers, and templates at each step.
As for KPIs, they stuck to the basics — minimal escalations, onboarding within committed timelines of 4–6 weeks, a high CSAT score, and no re-onboarding.
From her experience and interactions with other implementation professionals, Jharna recommends setting up a dedicated onboarding team for implementations that take over four weeks.
With marketing automation and campaigns, data changes often, and failure to track and feed these correctly was the primary reason for failed campaigns. In such implementations involving data and heavy lifting on the customer side, ensuring the correctness of integration is a huge challenge.
In their early approach, the customer performed the integration end to end, post which the onboarding team would help them test it. This would cause issues and delays, mostly right when it was almost time to go-live.
Since then, they have modified their process — considering their model looks at all interactions as events and ensuring the corresponding user-tracking in the system. This is the five-step model that they follow:
Integrations follow an agile and iterative process with weekly focus areas. For instance, a month is broken into themes for each week. The first call is used to explain the methodology and what will be accomplished each week. For example,
And so on.
This approach is very document-intensive with detailed checklists for the key phases and activities — for both the customer and the onboarding team to verify. Anything repetitive is templatized.
The customer is given specific documents and lists for appropriate teams to check implementation at their end. For example, the implementation checklists can be used by the customers' QA team. On the other hand, WebEngage’s onboarding managers also perform testing at their end to verify the implementation.
Here are what the implementation team roles look like at WebEngage and Freshworks and the ideal candidates for these roles.
They look at roles with the onboarding team as a techno-functional role. So, while they don’t look for people who can code, a manager should understand tech concepts and be able to speak the customers' language, and ensure that customers understand how the product is set up.
The right candidate would be someone with a technical background, client-facing experience, project management experience, and the ability to handle multiple clients, deadlines, and the stress that could come with it all.
The implementation team at Freshworks consists of four defined roles.
The right fit: Someone with strong communication skills, customer-facing experience, project management skills, and a fine balance of. diplomacy and assertiveness.
The right fit: Someone who has a good understanding of APIs, webhooks, and the ability to translate something technical into simple plain. language for customers. Besides the ability to say no.
The right fit: An experienced engineer with a very technical, hands-on background.
The right fit: A senior manager with 10–15 years of tech experience.
WebEngage, FreshWorks, and Pando have a well-defined transition across customer-facing functions — from Sales through Onboarding to Customer Success and Support.
WebEngage follows a format where Onboarding collects information from Sales — about the client, their business, pain points, competitors, previous experiences, use cases sold/pitched, etc. This is followed by a call with Sales to understand the customer sentiment before the kick-off call. The Customer Success Manager is involved from the onboarding phase itself and looped in on all correspondence throughout the onboarding journey even if they don't join every call. Sales also sends out an email to all stakeholders capturing all of the above as a formal account transfer.
At Pando, the sales hand-off to implementation/delivery is automated as much as possible with the key stages as below:
At Freshworks, the Customer Success Manager is introduced right after the deal is closed by Sales and continues to be the lifelong point of contact. The CSM introduces the implementation team but also makes sure to be a part of the onboarding journey.
At WebEngage, onboarding is completed in 4–6 weeks. Onboarding is marked complete after the customer successfully runs at least two campaigns. Through this phase, the CSM is looped in on status updates twice a week.
At FreshWorks, the CSM is copied on all emails, status reports, and is on any key calls with executive stakeholders.
At WebEngage, the onboarding team sets up a sync-up call where the CSM is introduced, and the project is officially transitioned over.
At Freshworks, a post-implementation handoff document is created for Success and Support that captures:
Jharna shares a simple thumb rule for documentation — anything that is repetitive goes into a template document — from processes to emails to reports.
The onus of updating these documents rests with the document owner, and any major changes post-go-live are communicated to the customer as applicable.
At FreshWorks, there are at least 5–6 handoff documents, including a document made by the TAM (Technical Account Manager) from the support team who collates everything into a "360-degree" document that gets attached to the helpdesk/CRM.
The onboarding team gets involved in POCs too where needed. The responsibility of defining the objective for the POC and ensuring that the customer’s tech team helps with getting the right data, etc. rests completely with the customer. Only then does the onboarding team showcase how the campaign can be run or the goal achieved
On the subject of dealing with POC timelines and expectations, here are some approaches:
WebEngage has a dedicated 6-month program for startups with suggestive timelines as below
At Freshworks, the onboarding for startups is carried out at the customer end where Sales helps them set up through product guides, checklists, etc, post which they directly transition to Support — without going through Freshworks Onboarding. Institutional guidance in the form of webinars, the Freshworks academy, and DIY resources have been sufficient to support startups.
Jharna shared that in the case of enterprise customers, there were often multiple stakeholders, different teams, with different dependencies — such as a web team, an app team, an Android team, an iOS team, etc. Not all of them are always on the same page — leading to messy situations with different understandings among their teams.
To solve this, here are three changes that have had the most impact:
1. Adhering to the Scope of Work
2. Creating the same understanding among teams
For example, with multiple teams, the WebEngage onboarding team creates data model documents for each team and has a sheet with the names of the events, where to pass these events, where to call tracking functions, etc to create a shared understanding and where separate teams can add their comments in their designated columns.
3. Conducting daily stand-ups or alternate day sync-up calls
This was to make sure the teams have the same understanding and are doing things the right way. If there are issues and open points, ETA for resolving the open items is mentioned and discussed in the next stand-up meeting.
WebEngage sticks to the basics to define what success looks like for the onboarding team:
At Freshworks, there's also a CSAT survey with 5–6 questions sent out at the end of the onboarding journey.
Companies like Innovacer — where the bulk of integration is carried out by the onboarding team and not the customer — also look at efficiency by assessing the delay and the percentage of rework. The aim is to keep rework and delay under 5%.
Here is a quick summary of the key takeaways from this engaging and insightful session.
We hope the discussion leaves you with some ideas for your onboarding team and journey.
If you’d like to read more implementation stories, you can find them here.
If you’re looking for additional resources to plan an onboarding kickoff meeting, or identifying metrics for your team, or making value realization a part of your onboarding journey, do check out our articles here.
Join our private, invite-only Slack community and attend the next Implementation Stories session. You will also gain access to peers, get to share knowledge on customer onboarding, implementation, and customer success.