Emmanuel Alabi

When I joined Bitlink Exchange as Customer Service Team Lead, the support function existed in name only. Agents were handling tickets across the African crypto market with no ticketing system, no documented processes, no performance metrics, and no training programme. Every agent was running their own version of support. Leadership had no visibility into what was happening.

My job was to build it properly. All from scratch.

• Zendesk Implementation: Ticket routing rules, automation workflows, SLA configurations, and reporting dashboards built end-to-end. The team went from email chaos to a structured queue in two weeks.
• 14 SOPs: Covered every support workflow such as account issues, transaction disputes, KYC escalations, withdrawal delays, platform errors, and escalation paths. New hires had a process to follow on day one.
• KPI Framework: Introducing first-contact resolution rate, average response time, resolution rate, and CSAT. Before this, leadership had no consistent data. After, performance reviews ran on actual numbers.
• Training Programme: Built from scratch — Zendesk workflows, CS standards, escalation procedures, product knowledge. Every agent hired during my tenure went through it personally.

Karate Combat is a live combat sports platform with a blockchain-based gaming layer built on Hedera. Users vote on fight outcomes using $KARATE tokens and interact across a 20,000+ member community on Discord, Telegram, and the KC mobile app simultaneously.

Support during fight nights is different from standard support. Response windows compress. Volume spikes without warning. The same technical issue can affect hundreds of users at once. Slow response shows, publicly, in real time.

• Live Event Triage System: Voting errors and wallet issues first, app feedback and general questions last. The right problems got resolved while the event was still live.
• Security Infrastructure: Scam detection, bot raid blocks, and phishing filters deployed from scratch. Community incident rate dropped within 30 days. Detection ran automatically so it didn't eat into support bandwidth during peak hours.
• Pattern Documentation: Recurring complaint categories tracked across shifts and turned into structured feedback reports for the product team. Several fed directly into platform updates including changes to voting confirmation display.
• Structured Escalation: Technical issues went to engineering with device type, OS, wallet type, exact error message, timestamp, account ID. Not vague descriptions.

A Bitlink user can't complete a withdrawal. It's been two hours. The app shows 'pending' with no further information. Same problem, same resolution path, but handled differently across four channels.

Tone, format, and message length shift per channel. Discord and live chat are faster and more direct, Telegram sits in the middle, email is the only context where a formal opening, full paragraphs, and a sign-off belong. Live chat works better in short bursts than one long message.

What stays the same: reassurance comes first, the information request is always specific, and the response time commitment is always stated.

Three recurring complaint patterns were generating the bulk of support volume in Q3 2024. Each represented a fixable problem that nobody had formally documented. This report covers the themes, root causes, and recommendations submitted to the product team.

Users initiated $KARATE withdrawals from centralized exchanges close to the 48-hour snapshot deadline. CEX withdrawal delays meant tokens arrived after the snapshot even when initiated before it. Users had no way of knowing this was possible.

Recommendation: In-app snapshot reminder at 72hr and 24hr before cutoff with a clear explanation of CEX withdrawal times. Pin a snapshot FAQ in Discord and Telegram before each event.

Outcome: Snapshot reminder added before KC49. Ticket volume on this theme dropped ~40% in Q4.

Post-vote UI didn't show a clear success state. Users voted, saw a brief UI change, and weren't confident the action registered, especially on slower connections. Several users tried to vote multiple times.

Recommendation: Explicit 'Vote Confirmed' screen with corresponding graphics.

Outcome: Updated confirmation screen shipped in KC48.

Reward distribution is processed on-chain after each event and can take 30 minutes to several hours. No in-app communication existed to tell users this was normal.

Recommendation: Post-event message explaining the reward distribution timeline — 'Rewards are being distributed. This typically takes 1-4 hours.'

Outcome: Reward status messaging appeared in the app by KC47.

Karate Combat's voting system requires $KARATE tokens to be in a user's wallet 48 hours before each event. The snapshot is hardcoded in a smart contract, no manual override exists. During KC55, a user withdrew from a CEX 20 minutes before the deadline. The transaction was confirmed 11 minutes late due to network congestion. They couldn't vote, came into general chat in front of a live audience, and threatened to post publicly.

Moved the conversation to a private ticket within 90 seconds to remove the audience. Asked for the wallet address and transaction hash before saying anything else. Pulled the on-chain record, confirmed the user initiated before the deadline, but the CEX delay was the problem. Explained the smart contract constraint directly without softening it. Offered to flag the case as product feedback.