Interview with a Diversity and Inclusion Lead: Post-Acquisition Challenges in Edtech Customer Support

Q1: When an online courses company acquires another, what’s the first diversity and inclusion (D&I) pitfall mid-level customer-support teams should watch out for?

One big early snag is assuming both companies have the same baseline culture and policies. Edtech platforms often differ a lot in how they approach inclusivity—whether that means language accessibility, accommodation policies, or hiring demographics. For example, one company might prioritize multilingual support extensively, while the other barely supports anything beyond English.

Post-acquisition, if you don’t surface these differences quickly, you risk alienating both staff and learners. Imagine a support center that previously handled Spanish and Mandarin fluently suddenly being forced to cut back because the acquiring company hasn’t invested in those languages. That’s a cultural mismatch that can lead to attrition and learner complaints.

Follow-up: So what’s a practical first step for mid-level support managers?

Start with a “culture audit.” Use surveys or interviews, with tools like Zigpoll or CultureAmp, to ask support agents about their experiences around inclusion—what works, what’s missing. Don’t just rely on HR data or high-level reports. These frontline voices reveal specifics about what breaks down in day-to-day interactions with learners from diverse backgrounds. You want to gather raw data early.

One note of caution: quantitative surveys can miss nuance, so pair them with qualitative feedback sessions. Otherwise, you might think you’re doing well because numbers look good, when agents feel unsupported.

Reconciling Different Tech Stacks Without Losing D&I Progress

Q2: Post-merger, tech stack consolidation is a big deal. How can customer support teams protect D&I advances during that process?

Merging CRMs, helpdesk platforms, or knowledge bases often pushes D&I tools to the back burner. Features like auto-translation, accessibility settings, or bias checks in chatbots can be lost if the new system doesn’t support them.

For example, a blended learning company I advised had a legacy LMS with built-in speech recognition tailored for disabled users. After acquisition, the acquiring firm’s simpler ticketing system lacked that feature. Support found themselves manually transcribing or repeating info, slowing down service and frustrating learners who rely on those accommodations.

Here’s the hands-on approach:

• Inventory all accessibility and inclusion-focused features in both tech stacks.
• Rank by impact and feasibility: Which features are “must-haves” for your core learner groups?
• Advocate for maintaining or rebuilding critical capabilities in the chosen unified system.

A caveat: Sometimes tech consolidation timelines are aggressive, and you may not get everything immediately. In that case, create workaround SOPs—like flagging tickets needing extra accommodation—so your team is primed to respond thoughtfully, even if the tech isn’t perfect.

Aligning Support Scripts and Language to Reflect Inclusion

Q3: How do you harmonize communication scripts after a merger, especially to uphold inclusive language?

Scripts often carry unconscious biases or culturally specific norms. Post-acquisition, you can’t just pick one company’s scripts and call it a day. The combined learner base is usually broader and more diverse.

One example: An online platform that expanded from US-focused courses into Latin America found their English-centric canned responses didn’t resonate. Translated literally, some phrasing felt awkward or even off-putting. Support reps noticed more repeat tickets and learner confusion.

Step-by-step fix:

• Gather language samples from both companies.
• Run them through inclusive language checkers or style guides tailored for educational content.
• Test with bilingual support reps and even learners from different regions.
• Update scripts to be clear, neutral, and respectful across cultures.

Watch out: Over-standardizing scripts can backfire. You want flexibility for agents to tailor responses based on context—a rigid script kills empathy. Train your team to understand the why behind inclusive language instead of just mandating phrases.

Building Diverse Hiring Pipelines for Support Post-Acquisition

Q4: What should mid-level support leads know about recruiting diverse talent after an acquisition?

Often, acquisitions trigger hiring freezes or reshuffling, which can stall ongoing diversity efforts. But it’s also an opportunity to reset.

A 2024 Forrester report found that 62% of tech companies post-M&A ignored diversity recruitment for up to six months, leading to a 15% drop in minority representation in support teams.

What to do:

• Partner with HR early to understand hiring plans post-merger.
• Advocate to maintain or increase outreach to diverse candidate pools.
• Use industry-specific channels: forums for educators of color, edtech job boards, or partnerships with organizations like Women Who Code or NAFSA.

Pro tip: Incorporate inclusive interview panels quickly, mixing reps from both legacy companies. This helps reduce bias and signals inclusive values to candidates.

Limitation: If leadership deprioritizes D&I, your influence can be limited. Focus on what you can control—like onboarding processes that welcome diverse hires and reduce microaggressions.

Measuring the Impact of D&I Initiatives with Support Metrics

Q5: How do you track if your diversity and inclusion initiatives in support are actually working, especially after merging teams?

Many teams rely on surface-level metrics—like the percentage of diverse hires or employee satisfaction scores. But support-specific measures are often overlooked.

One online university merged support teams and started tracking learner satisfaction broken down by demographic data. They found that learners from underrepresented groups rated their support experience 10 points lower on CSAT than average, which was masked in the overall scores.

Here’s a practical framework:

• Use feedback tools like Medallia, Qualtrics, or Zigpoll to segment learner feedback by identity groups, geography, or language.
• Monitor support ticket resolution times and escalation rates for different learner cohorts.
• Track agent retention and promotion rates across diverse groups internally.

Heads-up: Privacy regulations may restrict collecting demographic data, especially internationally. Work with legal to anonymize data and get informed consent.

Aligning Post-Acquisition Company Values with Support D&I

Q6: How do you help support teams internalize and reflect new, combined company values related to diversity and inclusion?

After an acquisition, mission statements and values often evolve, sometimes abruptly. Support teams can feel disconnected if changes aren’t communicated well.

One mid-sized MOOC platform merged with a smaller niche provider focusing on accessibility. The new values emphasized “learning for all abilities,” but customer reps rarely heard about it beyond an email memo.

What works better:

• Run interactive workshops or focus groups specifically for support staff to discuss how D&I fits their daily roles.
• Share stories and data showing why these values matter—like how learners with disabilities represented 20% of course sign-ups but had lower satisfaction scores.
• Encourage feedback loops so reps can voice challenges in meeting these values.

Gotcha: Don’t overload teams with vague ideals that feel disconnected from their work. Connect values to tangible behaviors—like using inclusive language or flagging accessibility issues to product teams.

Handling Cultural Differences in International Support Teams

Q7: What are common cultural misunderstandings that arise post-M&A in global edtech support teams, and how can you address them?

Merging support teams from different countries can surface communication challenges. For example, directness may be valued in one culture and seen as rude in another.

One company merged North American and Southeast Asian support teams. They noticed misunderstandings in tone—emails intended to be concise sounded curt to some. This caused friction internally and externally with learners.

Practical strategies:

• Set up regular cross-cultural training focused on communication styles.
• Create a shared glossary of tone and phrasing examples to align expectations.
• Use video calls when possible to pick up non-verbal cues.
• Encourage empathy by sharing personal stories of cultural norms.

Note: Language proficiency varies widely in international teams. Avoid jargon-heavy scripts or idioms that confuse non-native speakers.

Prioritizing Accessibility in Support Channels After Merger

Q8: What accessibility features in support channels often get overlooked during tech stack integration?

Chatbots, live chat, and video support are growing in edtech. But accessibility can slip through the cracks during merges.

For example, an acquiring company’s chatbot didn’t support screen reader compatibility or keyboard navigation. When merged, that meant many learners with disabilities suddenly faced barriers.

Focus areas:

• Audit all new and legacy tools for compliance with WCAG 2.1 AA standards.
• Make sure support content is available in multiple formats: text, audio, video with captions.
• Train agents to recognize and escalate accessibility issues immediately.

Warning: This is a continuous process. A 2023 EdTech Accessibility Survey revealed that only 40% of merged companies conducted post-integration accessibility reviews, risking legal and reputational damage.

Incorporating Learner Feedback into D&I Strategy

Q9: How can mid-level support teams incorporate diverse learner feedback into ongoing D&I initiatives post-acquisition?

Learner feedback is a goldmine but often underutilized. Support teams interact directly with a wide range of learners who can indicate subtle exclusionary patterns.

One online coding bootcamp merged and started monthly “learner inclusion panels” facilitated via surveys on Zigpoll and follow-up virtual focus groups. They uncovered that some learners felt microaggressed by canned responses referencing “typical working hours,” which didn’t reflect global time zones.

How to build this in:

• Use varied tools—surveys, interviews, social listening—to gather broad and deep input.
• Make feedback easy, anonymous, and ongoing.
• Share insights with leadership and product teams so support’s D&I efforts influence platform design.

Limitation: Feedback collection depends on learner willingness and honesty. Incentivize participation carefully to avoid bias.

Supporting Mental Health Diversity in Customer Support Post-Merger

Q10: What role does mental health awareness play in D&I for support teams after acquisitions in edtech?

Mergers often increase stress due to uncertainty and change, disproportionately affecting marginalized groups who may already face discrimination or stigma.

Support agents handling sensitive learner issues—like course stress or accessibility challenges—need mental health resources themselves.

One edtech merger saw a spike in support turnover after acquisition. They introduced peer support networks, confidential counseling, and mental health training focusing on cultural competence. Agent retention improved by 25% within 6 months.

Tips for mid-level leads:

• Champion mental health resources tailored to diverse backgrounds.
• Encourage open conversations about stress and bias.
• Partner with HR to identify and mitigate burnout risks.

Heads-up: Mental health support isn’t one-size-fits-all. Some cultures stigmatize counseling, so offer multiple avenues like online tools, anonymous hotlines, or group sessions.

Summary: Action Steps for Mid-Level Support Leads

• Conduct culture audits early, involving frontline support voices.
• Inventory and protect D&I features during tech consolidation.
• Align communication scripts with inclusive, culturally aware language.
• Stay engaged in recruitment to maintain diverse pipelines.
• Track support-specific D&I metrics, respecting privacy laws.
• Help teams internalize new company values through dialogue.
• Build cross-cultural competencies in international teams.
• Prioritize accessibility across all support channels.
• Integrate diverse learner feedback into ongoing improvements.
• Support mental health with culturally sensitive resources.

Even in the swirl of post-merger transitions, these focused tactics can keep diversity and inclusion not just on the radar but driving better support—and better learning outcomes—for all.