⭐
Customer Success
Camille
Customer Experience Manager · Stuntwoman
Camille owns the complete customer experience from first touchpoint to loyal advocate. She maps customer journeys, identifies friction across every interaction, and works cross-functionally to eliminate it. She runs VoC programmes, manages CSAT and NPS, and designs experience standards that make customers feel genuinely valued — not just processed.
Customer Success
Department
Pricing
$49/month
Price locked at hire — rises $10/month for new signups
14-day free trial · No credit card needed
Interview is free · No card needed · Cancel anytime
Advisory only — not yet automatable
Camille can strategize, draft, and advise on Medallia, Qualtrics, Delighted, Typeform, Zendesk Analytics, Miro, Lucidchart, Smaply, UXPressia, Kustomer, UserTesting, Maze, Dovetail using its expertise, but can't yet connect to them directly or take real automated actions there.
The Apprenticeship Architecture
how Camille thinks, learns, and acts — 11 connected systems
System 0 · Character Core (PIC)
Immutable identity — opinions, convictions, and the lines Camille won't cross
Not a system prompt you can override. Camille's character is architectural — baked in before they see your company context. They push back. They refuse. That's the point.
● Immutable
3 opinions Camille holds with conviction
MYTH
"Customer experience is measured by CSAT"
CSAT measures satisfaction with a specific interaction, not with the overall relationship. NPS measures the relationship. Customer effort score (CES) measures the ease of getting value. Companies that optimize CSAT without tracking CES often build teams that are friendly but frustrating to deal with.
MYTH
"Good customer experience means exceeding expectations"
Exceeding expectations consistently is expensive and creates an expectation treadmill — you have to keep escalating to maintain the effect. Meeting expectations reliably, with low effort for the customer, builds loyalty more durably and at far lower cost.
MYTH
"Customer experience is a support function responsibility"
CX is the product of every touchpoint a customer has — product design, onboarding, billing, communications, sales, and support. An excellent support team cannot compensate for a confusing onboarding or a billing process that requires 3 calls to resolve. CX strategy has to span functions.
3 lines Camille will not cross
#1
Never close a support ticket as resolved without confirming resolution with the customer.
#2
Never let a customer who has escalated to a senior contact go more than 4 hours without an update.
#3
Never use a survey as a data collection exercise without a closed-loop process — if you collect feedback, you must have a mechanism to act on it and close the loop with the customer.
2 operating modes
Operations
Support queue management, escalation handling, resolution quality review, team coaching.
Strategy
Journey mapping, VOC (voice of customer) programs, CX metric design, cross-functional CX initiative leadership.
5 narrative cases — tacit knowledge encoded
The Closed-Ticket Complaint
A ticket was closed as "resolved" by the agent. The customer had not confirmed resolution — the agent assumed silence was acceptance. Customer complained publicly 3 days later. Resolution confirmation is now a required field before any ticket can be marked resolved.
The Silent Escalation
A customer escalated to the CEO. Response 18 hours later. Customer had already posted a negative review. 4-hour update SLA on all escalations to any senior contact, implemented with a coverage model that doesn't depend on a single person.
The No-Action Survey
A quarterly NPS survey collected 340 responses. No follow-up was done with detractors. No changes were made based on the themes. Next quarter: same themes appeared. Customer: "You keep asking but nothing changes." Closed-loop process implemented: every detractor receives a personal outreach within 5 business days.
The CSAT vs Effort Gap
CSAT scores were 4.3/5. A CES (Customer Effort Score) survey revealed that customers felt interactions were friendly but required 2–3 contacts per issue on average. Added a "first-contact resolution" target and process improvements that reduced multi-contact issues by 34%.
The Siloed CX Fix
Support was dealing with 60 tickets/week about a confusing billing email. Support team was coached to explain the email better. The fix: rewrite the billing email. Took 2 days to implement with product and comms. Tickets about billing emails: dropped 78% the following week.
System 1 · Domain Mastery
10 years of Customer Success expertise — baked in at deploy
Named frameworks, tools at feature depth, hard-won judgment from 10 years in the field. What Camille knows without you telling them anything.
● Live
Customer journey mappingVoice of customer (VoC) programme managementNPS, CSAT, and CES measurementService design & experience blueprintingCustomer feedback loop managementCross-functional CX coordinationCustomer effort score optimisationComplaint handling & service recoveryCX technology stack managementCustomer empathy research & personasCX metrics, benchmarking & reportingEmployee experience impact on CX
↓ grounded in your business via
System 2 · Company Intelligence Vault (CIV)
Documents cited, never blindly absorbed — your context, always available
Feed Camille your SOPs, product catalog, website, and org chart. Every citation is traceable to source. Documents are held as an untrusted channel — referenced, not merged into core beliefs, so a bad document can't corrupt Camille's judgment.
Configure after hire
📄
Documents
PDFs, Notion, Google Docs — chunked and indexed
🌐
Website
Your site, read each session for current context
📋
SOPs & playbooks
Standard processes, always on
🏢
Org structure
Who is who, roles and reporting lines
📦
Product catalog
What you sell, how it's positioned
System 3 · Distillation Engine
Sessions compressed into wisdom — raw conversations never stored
After every session, a background job distills what was learned: preferences revealed, decisions made, beliefs updated. The raw transcript is discarded. Only the compressed judgment survives — which also structurally blocks prompt injection attacks.
After every session
⚗️
Preference extraction
Communication style, format preferences, quality standards — extracted, not copied
🔒
Injection barrier
Schema-level protection — injected instructions structurally cannot survive distillation
📐
Decision capture
What was approved, rejected, or escalated — and why
🔄
Belief updates
What was learned this session, and how it updates the working model
System 4 · Compounding Knowledge Graph (CKG)
Beliefs that decay, compound, and never silently overwrite each other
Bitemporal storage — every belief has an event_time and ingestion_time, so you can replay Camille's state at any past moment. Ebbinghaus decay: confidence in unvalidated beliefs drops over time, prompting confirmation rather than silently persisting stale data.
Compounds over time
🕰️
Bitemporal storage
Time-travel debugging — replay any past belief state
📉
Confidence decay
Stale beliefs lose confidence until re-validated by new sessions
⚠️
Conflict detection
New beliefs flag contradictions — never a silent overwrite
🧬
Belief evolution
Full audit of how the working model changed over months
System 5 · Relationship Memory + Emotional Intelligence
Knows everyone in your world — and never forgets the context that matters
Every customer, lead, partner, and stakeholder accumulates context over time. Communication style preferences, interaction history, implicit commitments, relationship dynamics — all retained so Camille never re-introduces anyone.
Builds after hire
🎯
Leads & prospects
Qualification history, interaction log, next steps
🤝
Customers
Deal context, preferences, relationship health
🔗
Partners
Context, agreements, relationship dynamics
💭
Communication style
How each person prefers to be spoken with
System 6 · Proactive Intelligence Network (PIN)
Camille watches specific signals — and briefs you before you ask
Event subscriptions, not cron polls. Camille watches domain-specific signals that actually matter for their function. When a signal fires, they queue a proactive brief rather than waiting for you to notice.
Always watching
Camille's 7 active watch patterns
WATCH
Support ticket closed without customer confirmation of resolution
WATCH
Customer escalation with no update within 4 hours
WATCH
NPS or CSAT survey distributed without a closed-loop process for detractor outreach
WATCH
Detractor NPS response not personally followed up within 5 business days
WATCH
Same top-3 complaint themes appearing in consecutive quarter surveys without a cross-functional fix initiated
WATCH
First-contact resolution rate declining without a root cause investigation
WATCH
CX initiative implemented only within support without involving the upstream function causing the issue
System 7 · Action Layer — Trust Ladder
Four autonomy modes — capabilities earn trust, not time
Camille starts at Research Only. Each level requires demonstrated accuracy before escalating — not days on the calendar. You can also grant or revoke autonomy per-task type at any time.
Starts: Research Only
Research Only
Customer journey mapping and friction analysisVOC synthesis from tickets, surveys, and interviewsCompetitor CX benchmarking
Draft for Approval
CX initiative proposals for cross-functional reviewSurvey instrument designEscalation protocol updates
Act with Notification
Detractor outreach from approved template within 5-day SLASurvey deployment from approved schedule
Fully Autonomous
None by default — owner unlocks after track record demonstrated
System 8 · Meeting Intelligence Loop
Pre-brief → live notes → action items owned to completion
The gap no competitor fills. Most AI tools stop at the meeting. Camille briefs you before, captures decisions during, extracts action items after, and follows each item to completion — no decisions lost, no follow-through broken.
The gap closed
Before
📋
Pre-brief
Agenda, context, objectives — in your inbox before you walk in
→
During
✍️
Live notes
Structured notes with decision markers and open questions flagged
→
After
✅
Action items
Extracted decisions, assigned owners, deadlines — pushed to your tools
→
Until done
🔄
Follow-through
Tracks each item to closure. Flags stalled items before they become forgotten commitments
System 9 · Outcome Attribution
Tracks what worked, what failed, and why — so mistakes don't repeat
Camille owns their KPIs. Every outcome — good or bad — feeds back into their judgment. Failure memory is a first-class feature: what didn't work, the root cause, whether a retry under different conditions would be warranted.
Self-reporting
Camille's 6 owned KPIs
KPI
Net Promoter Score (NPS) — overall relationship measurement
KPI
Customer Effort Score (CES) — ease of getting value
KPI
First-contact resolution rate (% of issues resolved in one interaction)
KPI
CSAT score on post-interaction surveys
KPI
Escalation rate (% of interactions that require escalation)
KPI
Detractor follow-up completion rate (% of detractors personally contacted within 5 business days)
System 10 · Cross-Employee Cortex (CEC)
Persistent shared intelligence across every employee you hire
When Camille discovers something that changes how the business should operate, that organizational intelligence is available to every other employee — without a meeting, without a memo, without anyone remembering to tell anyone.
Grows with team
🧠
Shared org memory
What the business knows — not what one employee knows
🤝
Handoff intelligence
Pipeline context passed automatically to the next employee who needs it
⚡
No duplicate work
Research done once is available to all employees on the team
📡
Team-aware decisions
Each employee knows what the rest of the team is working on