ScalingCustomer Experienceat ether.fi
From Reactive Support to a Trust-Driven DeFi Experience
by Luca Luperto— Operation & Escalation Manager | Binance
Why CX Is Critical Now
CX is not a cost center — it's a revenue function. In DeFi, trust is the product.
Why CX is a Revenue Function
What This Analysis Covers
Key Customer Journeys
Four critical user paths where trust is built — or broken.
Onboarding → Staking
Restaking
Cash Card Usage
Withdrawal / Redemption
User Sentiment & Experience Gaps
Excitement is high, but confidence drops when mechanics and outcomes are not obvious.
Delayed support reduces early user confidence
Users question reward accuracy and transparency
Card value compared unfavorably to competitors
What users value
- Premium card experience and cashback
- Integrated earn + spend ecosystem
- Ability to use crypto productively
Where users struggle most
- Product complexity across vaults, rewards and card flows
- Unclear outcomes in withdrawals and vault performance
- Delays around physical cards
What users don't understand
- How rewards are calculated and distributed
- Borrow vs Direct Pay mechanics
- How to interpret APY and actual returns
Sources: Public community channels (Reddit, Discord), Help Center, product walkthrough
Support Experience: What I Found Firsthand
Live audit on April 2, 2026 — real interaction, real timestamps. Not assumptions.
What Works
What Breaks Trust
A Scalable CX Strategy Built on Trust
Customer experience should reduce uncertainty at every step of the journey.
Clarity
Make the product understandable
- Simplify how rewards, vaults and card flows are explained
- Improve onboarding to guide early decision making
- Reduce reliance on external sources (Reddit, Discord)
Speed
Reduce uncertainty in critical moments
- Align support SLAs with real performance
- Improve first response time and resolution time
- Enable faster self-service through better FAQ & bot flows
Continuity
Create a consistent user journey
- Introduce case ownership and conversation tracking
- Ensure seamless transitions between bot and human support
- Maintain context across interactions
Communicating Withdrawals Across User Tiers
Tiered CX is not luxury — it is retention math.
Self-serve + Help Center + Discord
Before withdrawal: 'Expected: instant / up to 14 days if liquidity is low'
'Why did I receive less than deposited?' — plain language FAQ
Real-time queue position + ETA visible from portfolio page
Automated Discord reply to 'pending withdrawal' keyword with link
Notification when withdrawal completes
Dedicated Telegram/Slack with named CX contact
Outreach if withdrawal takes >4h: 'Your request is in queue, ETA X, here's why'
Vault performance summary in plain language before they ask
First response <5 min, resolution same day
Direct path to Product if technical issue detected
Dedicated account manager, weekly sync call
Liquidity forecast 48h before large redemptions
Performance report: yield, fees, reconciliation
API-based status webhook for treasury management systems
Fast response, direct escalation to Engineering
High-APY Vault Launch — TVL Doubles in 30 Days
CX must be in the room before launch — not called to manage the fallout after.
PREPARE
- Brief with Product: vault mechanics, edge cases, expected APY variance
- Write top 10 FAQ for the vault. Publish day 0 in Help Center
- Pre-build 15 macros for predicted ticket categories
- Identify 2 surge agents (contractors or cross-trained internal)
- Agree escalation SLA with Product + Engineering in writing
MONITOR
- Daily triage: categorize every reward/withdrawal ticket within 2h
- Same issue 5+ times in a day: flag to Product same day as bug or doc gap
- War room: daily 15-min standup CX + Product + Eng, first 2 weeks
- Proactive Discord post if APY deviates >10% from marketed rate
- VIP users: individual outreach if withdrawal takes >24h
ITERATE
- 30-day retro: top ticket categories root cause with Product
- Every repeated ticket category → Help Center article or UI fix
- Target: ticket deflection rate +20% within 60 days post-launch
- Stand down surge agents when FRT returns to <5 min baseline
- Publish findings to founders as 'CX Learnings Report'
How I Would Run CX at ether.fi
CX is a function, not a cost center. It turns user pain into product velocity.
Team Structure
Day 1
Assumption: current team exists, I map and reinforce their strengths first
Cross-Functional Rhythm
Tooling Priorities
The 5 Metrics I Own and Report Weekly
First 30 Days: Prioritized Roadmap
Week 1: understand. Week 2: fix fast. Week 3: protect retention. Week 4: build to scale.
Listen
Every support channel (chat, Discord, tickets)
Last 200 closed tickets, tag by category
Product, Marketing, Engineering and understand roadmap
Tooling, macros, bot flows, current SLAs
Written diagnosis + priority list to founders by Friday
Fix Fast
5 Help Center articles for top pain points
Case ID + ticket ownership system
Top 10 macros — empathic, context-aware, no generic deflection
Bot trigger for 'withdrawal pending' and language detection
Promo UI colors; brief Marketing on trust signal impact
Protect
Top 20 TVL users, set up VIP Telegram channel
Weekly CX report to founders (FRT, CSAT, top tickets)
Internal escalation matrix for complex cases as in Binance
CSAT survey on ticket close + first CSAT baseline
SLA messaging in chat widget to match real performance
Scale
Weekly ticket review framework + agent scoring rubric
'Top 3 CX signals' into Product standup weekly
30-day data to founders + 60-day roadmap
Luca Luperto
Escalation & Operations Specialist
Binance
Product and operations-focused professional with experience driving cross-functional initiatives, escalations and performance metrics in high-volume blockchain environments. Led customer support operations with focus on user protection and process optimization across wallet and DeFi operations.
Work Experience
Escalation & Operations Specialist
Binance
- Handle complex, high-impact escalations beyond standard support flows, involving wallet operations, risk, security and compliance constraints, tracked and documented through Jira and Confluence.
- Lead operational initiatives focused on resolution efficiency, user protection and tooling improvements across crypto products, including wallets and DeFi-related workflows.
Security Operations Taskforce (Trust Wallet)
Binance
- Supported Trust Wallet during a critical security incident, coordinated via Jira and Confluence.
- Involved in wallet security operations, blockchain transaction monitoring and on-chain investigations to trace compromised funds and support user recovery in a non-custodial wallet environment.
Spanish and LATAM Team Lead
Binance
- Managed a team of ~60 agents across multiple regions.
- Owned team performance and KPIs achieving CSAT +4% above 97% target and QA +3% up to 98%.
- Acted as escalation point for complex, high-impact cases requiring decision ownership and risk-aware judgment.
Italian and EU Shift Leader
Binance
- Led a team of ~45 agents supporting Italian and EU customers across crypto products.
- Handled complex user cases escalated beyond frontline support, coordinating resolutions with internal business units.
- Positioned the Italian team among top performers in EU KPIs over a two-year period.
Customer Support Specialist
Binance
- Provided multilingual crypto customer support, handling high daily ticket volumes and consistently meeting CSAT, QA and resolution targets.
Education
Bachelor's in Economics & Management
University of Roma Tor Vergata
2016 – 2020
Thesis on market efficiency and its measurement.
Certifications
- Global Sanctions
- Privacy & Data Protection
- Crypto Market Conduct
- Conflict of Interest & Legal Hold
Contact & Languages
luperto.luca.94@gmail.com
+39 333 8280273
Lecce, Italy
Italian (Native) · English (Fluent)