Interview with Rachel M., Senior Customer Support Lead in Wellness-Fitness Compliance
Q: Rachel, you’ve worked at three different health-supplements companies focusing on customer support and compliance. How does the Jobs-To-Be-Done (JTBD) framework hold up in this heavily regulated space?
A: JTBD is a powerful lens for understanding customer needs, but in wellness-fitness—especially health supplements—it needs a compliance overlay. Companies often treat JTBD like a customer empathy tool only, but compliance is baked into every job. For example, when customers ask, "Can I take this supplement with my prescription meds?"—that’s a job with legal and audit implications.
I found early on that if you ignore compliance in JTBD mapping, you risk building processes or documentation that can fail under FDA audits or internal quality reviews. It’s not enough to know what customers want; you must also capture the regulatory "jobs" your team needs to do behind the scenes.
Compliance as a Core Job to Be Done in Customer Support
Q: Can you give a practical example of how compliance jobs fit within JTBD at these companies?
A: Sure. One of the most overlooked jobs is “ensuring traceability of customer interactions for audit purposes.” On paper, it sounds mundane—document every conversation. But in practice, not all CRM tools support compliance-grade traceability. At a prior company, our audit logs were patchy. We lost time and credibility because the auditors couldn’t verify whether adverse event reports were properly escalated.
We redefined the support job as:
"Help customers safely while documenting conversations so every regulatory requirement is met."
When you add that regulatory angle, processes change. You start questioning your tech stack, training, and even language used in support scripts to avoid off-label claims.
Why Virtual Reality Collaboration Isn’t Just a Fancy Tool for Support Compliance
Q: Virtual reality (VR) collaboration has become a buzzword. Does it have a real role in compliance for customer support in wellness-fitness?
A: VR is often sold as a novelty, but in compliance-heavy environments, it can be a surprisingly useful collaboration layer. Let me explain the difference.
In three companies, we piloted VR for cross-functional compliance training and real-time case discussions. Why? Because supplement formulations and health claims often involve nuanced interpretation of FDA guidance (21 CFR part 111 for GMPs, for example), and compliance officers, legal, product, and support teams need to sync quickly.
VR created a “shared space” where team members could annotate product labels, review customer feedback, and role-play sensitive customer interactions in compliance-safe environments. This led to faster consensus on how to respond to complex inquiries that risk misbranding or off-label promotion.
That said, VR isn’t a silver bullet. The downside: It requires investments in hardware and training. Plus, not every compliance discussion requires immersive tech—sometimes a quick Slack thread or a Zigpoll survey of support agents is enough.
JTBD Framework with a Regulatory Risk Reduction Lens: What Actually Works
Q: When you integrate risk reduction into JTBD, what’s worked well—and what’s more theory than practice?
A: I’ll be blunt: Simply adding “reduce regulatory risk” to JTBD statements sounds good but often leads to bloated processes. What worked was drilling into specific risk points—for example, tracking adverse event reports (AERs) and supplement ingredient queries.
At one company, we mapped the JTBD like this:
- Job: "Respond to supplement safety concerns quickly and accurately."
- Related job: "Document safety incidents per regulatory timelines."
- Pain point: "Manual report consolidation delays AER submissions by 48 hours."
- Solution: Automate AER flagging within the support ticket system.
The outcome? A 35% drop in late adverse event reports in six months, which meant fewer FDA follow-ups.
The theory-buster: Attempts to “cover all compliance bases” in JTBD mapping slowed down support and led to over-documentation, which frustrated both agents and customers. The sweet spot was focusing on high-risk, high-impact tasks.
How to Balance Customer Experience with Compliance in JTBD
Q: Health supplement customers expect quick answers, but regulatory requirements often slow things down. How does JTBD help balance that?
A: It’s a classic tension. Customers want immediate clarity on ingredients, benefits, interactions. Compliance demands careful, sometimes legalistic, wording and follow-up for potential adverse events.
JTBD can clarify what the “job executor” (the support agent) really needs to deliver:
- The customer’s job: “Understand product safety for their lifestyle.”
- The agent’s job: “Provide clear but compliant information, escalate flagged issues swiftly.”
Understanding these distinct jobs helps design layered scripts and decision trees. For example, a customer might ask if a product is keto-friendly—easy to answer. But when they ask if it treats diabetes, agents must avoid unapproved claims and instead guide to appropriate disclaimers and medical counsel.
One team improved compliance accuracy by 28% after restructuring support workflows aligned with these JTBD distinctions, using tools like Zigpoll to gather agent feedback on where scripts failed compliance tests.
JTBD and Documentation: What Auditors Really Want vs. What Support Thinks
Q: Documentation often gets seen as a checkbox, but how should customer support view it through JTBD?
A: Auditors don’t just want piles of paperwork; they want traceable, accessible, and accurate records that link customer interactions to compliance outcomes. The JTBD here is not just “Document every call” but:
"Ensure documentation supports a clear audit trail of regulatory compliance and risk mitigation actions."
In practice, this means embedding documentation needs into the support workflow. For example, when an agent handles a label query or potential adverse event, the system should prompt mandatory fields and flags for legal review.
A caution: Overzealous documentation demands can backfire. One company I worked with mandated 15+ fields per interaction; agents spent more time documenting than supporting, which led to burnout and increased errors.
Edge Cases: Handling Off-Label Questions and Customer Non-Disclosure
Q: How does JTBD help with tricky compliance edge cases like off-label questions or when customers don’t disclose health conditions?
A: These are the thorny spots. The customer’s job might be “Get help for their health issue,” but the agent’s job is to “Avoid creating off-label claims or misbranding, even if the customer pushes.”
JTBD helps by clarifying jobs for “referral to qualified medical advice” rather than direct answering. Scripts can embed phrases like “We recommend consulting a healthcare provider for your specific condition.” Training that aligns with these jobs reduces compliance risk.
In terms of non-disclosure, JTBD mapping can reveal the “job” of “Identify when a customer’s context might trigger a compliance red flag,” prompting proactive questioning in a non-invasive way.
Actionable Advice for Senior Customer Support Leaders
Q: Before we wrap up, what practical steps would you recommend to senior leaders using JTBD in compliance-focused wellness-fitness support?
A:
- Map compliance jobs separately but in tandem with customer jobs. Don’t dilute compliance with generic customer empathy; give it its own space to drive process design.
- Use technology that supports compliance workflows naturally. If your CRM can’t log adverse event details with audit trails, you’re already behind.
- Pilot VR collaboration for complex training and cross-team syncs. It’s not for every meeting, but for nuanced regulatory education and case reviews, it cuts down miscommunication.
- Prioritize high-impact compliance risks in JTBD, like supplement safety queries and off-label questions. Avoid over-documentation traps.
- Gather agent feedback on compliance scripts and workflows regularly. Zigpoll and similar tools can help identify where agents feel scripts fail or complicate compliance adherence.
- Train agents on how to handle edge cases with clear jobs and handoffs to legal or medical teams. Don’t expect them to be compliance lawyers.
- Ensure documentation processes create clear audit trails without overwhelming front-line teams. Sometimes less is more if focused on regulatory priorities.
A 2024 Forrester report showed that companies integrating compliance considerations into JTBD saw a 20% reduction in regulatory incidents year-over-year. Given how costly FDA warnings or recalls can be—often running into millions—this optimization pays dividends.
If you’re still treating JTBD purely as a customer empathy exercise in the wellness-fitness supplements space, you’re missing the full picture. Compliance isn’t just a background task; it’s a job customers and support teams do together, every day.
