How I would run the public queue across seven Payward handles in English and 简体中文, and a working desk that checks every post against Kraken's live status.
Seven brands with different support paths: exchange, Pro, Krak card, xStocks, Breakout prop, NinjaTrader futures, Payward. The queue mixes funding delays, account locks, scams and brand questions.
The Chinese channels launched in February 2026 and route support to the English desk. Binance, OKX and Bitget run Chinese accounts 8 to 50 times larger.
A bilingual triage desk: intent, priority and SLA; impostor and PII detection; live checks against status.kraken.com and the public REST API; EN and 中文 macros linted against safety rules.
Payward bought or launched most of these in the last 18 months. Each brings its own users, its own failure modes and its own support path.
| Brand | Handle | What it is | What social will hear |
|---|---|---|---|
| Kraken / Kraken Pro | @krakenfx, @krakenpro, @krakensupport | Spot, margin, futures, staking. 6.6M funded accounts (Q2 2026). | Funding delays on specific networks, verification and restrictions, 2FA recovery, delistings. |
| Krak | @krak, @kraksupport | P2P money app with Kraktags and a card (launched June 2025). | Card declines, transfers between users, PIN and OTP safety. |
| xStocks | @xStocksFi | Tokenized equities, via the Backed acquisition (Dec 2025). | Region eligibility ("not available in your region"), corporate actions, onchain transfers. |
| Breakout | @BreakoutProp | Crypto prop trading, funded accounts up to $200K (Sept 2025). | Evaluation rules, payout timing, "is this a scam" posts after a slow payout. |
| NinjaTrader | @NinjaTrader | US futures platform, $1.5B acquisition (May 2025). | Desktop platform bugs, data feeds, account funding. A different user base from crypto. |
| Payward | @Payward | Parent brand; Payward Services B2B infra (Mar 2026); Reap in Hong Kong (Jul 2026). | Corporate and IPO questions (now Q2 2027 at earliest). Route to Comms. |
Sources: payward.com; Kraken social directory (support.kraken.com, updated 2026-09-01); CoinDesk 2026-09-02.
Where a reply can be needed, with audience size on 24 September 2026.
| Channel | Size | Note |
|---|---|---|
| X @krakenfx | 1.75M | Main brand account. Complaints arrive as replies to marketing posts. |
| X @krakensupport | 36.2K | Support since 2014. Also the route for Chinese questions today. |
| X @KrakenFX_ZH | 13.7K | Chinese account since Feb 2026. Bio sends support to @krakensupport. |
| Telegram | 8,669 / 964 | @kraken_exchange_official and @kraken_chinese groups, plus @krakensupport and the Chinese support bot @krakensupportZH_bot. |
| Reddit, Discord | n/a | r/kraken, r/krakensupport; Kraken Exchange Discord. |
| Trustpilot | 3.2 / 5, 8,922 reviews | 50% one-star. Kraken replies to all negative reviews, usually within 24 hours. Top complaint: the AI chatbot and reaching a human. |
| App stores | 4.3 to 4.74 | iOS Kraken 4.74 (35K ratings), Google Play Kraken 4.3 (54.9K reviews), Krak 4.64 to 4.7. |
Recent public events that shape the posts this desk answers.
| Event | What happened | Social consequence |
|---|---|---|
| Network funding halts (ongoing) | On 24 Sept, 10 of 740 funding gateways were degraded (Cosmos, Neutron, MultiversX, Vanar, WMTX and others); EGLD and WMTX pairs in cancel-only. | "My withdrawal is pending" posts. The answer is on the status page; the reply should link it and promise nothing. |
| HTX-linked dust (Aug 2026) | About 12,000 dust deposits from a wallet tied to sanctioned HTX; screening temporarily locked accounts. | Confused, angry posts, many from former Huobi users writing in Chinese. Replies stay generic and route to Compliance. |
| Support-data extortion (Apr 2026) | Insiders viewed support data for about 2,000 accounts. No systems breach; Kraken refused to pay. | Targeted impersonation that quotes real ticket details. The desk has to spot fakes fast. |
| 21 delistings (Sept 2026) | Tokens delisted on 11 Sept; region-specific delistings scheduled (UAE, 25 Sept). | "Why can't I buy" and "is X being delisted" in both languages. |
| IPO delay (Sept 2026) | Target moved to Q2 2027 at earliest. | Solvency rumours from large accounts. One factual reply pointing to Proof of Reserves, then no argument. |
Sources: status.kraken.com; Bloomberg 2026-08-25; CoinDesk 2026-04-13; CoinDesk 2026-09-02.
How the large exchanges split brand, support and Chinese-language accounts on X (followers, 24 Sept 2026).
| Exchange | Main | Support handle | Chinese handle | Gap vs Kraken |
|---|---|---|---|---|
| Binance | 16.1M | @BinanceHelpDesk 219K | @binancezh 463K | Scale. Binance says it gives no support on Telegram, which narrows its impostor surface. |
| OKX | 5.6M | @OKXHelpDesk 27.9K | @OKXChinese 707K | Chinese account larger than its main support account. The Chinese audience is the core. |
| Bitget | 4.3M | @BitgetSupport 21.6K | @Bitget_zh 110K | Mature Chinese presence with a dedicated handle. |
| Bybit | 4.9M | @BybitHelpdesk | @Bybit_ZH 57.6K | Closest in Chinese size; still 4 times Kraken. |
| Coinbase | 7.2M | @CoinbaseSupport 359K | none | No Chinese account. Kraken is ahead here. |
| Kraken | 1.75M | @krakensupport 36.2K | @KrakenFX_ZH 13.7K | Trust record, Proof of Reserves and official Telegram support with a Chinese bot. Chinese reach is the gap. |
Takeaway: Kraken's reputation for care is the asset. A native Chinese voice that answers fast and safely is the cheapest way to turn it into reach.
Chinese crypto users get their news on X and gather on Telegram; WeChat and Weibo censor crypto. The media and on-chain analysts they read set the tone of every incident.
Media on X: Wu Blockchain (558K), TechFlow 深潮, PANews, BlockBeats, Odaily, ChainCatcher. On-chain analysts 余烬 @EmberCN and Ai 姨 @ai_9684xtpa, whose wallet-flow posts often name exchanges.
Eligibility and KYC, withdrawal networks and fees, listings (上币), account restrictions, and after August, the HTX dust locks. Tone is direct; slow or templated replies get screenshotted.
Mainland China bans crypto trading. Replies never solicit mainland users or discuss workarounds. Eligibility questions get the official list on support.kraken.com/cn.
| Move | How |
|---|---|
| Answer in Chinese on @KrakenFX_ZH | Reply publicly in Simplified Chinese, then move to @krakensupportZH_bot or DM. Today the bio sends Chinese users to the English desk. |
| Chinese incident posts | When a network halts, post the status link in Chinese within the hour on X and in @kraken_chinese, with the same wording as the English update. |
| Impostor sweep | Daily search for Chinese-named fake support accounts and 假冒客服 reports; report and pin the official-accounts list in the Telegram group. |
| Monitor the analysts | Watch the on-chain analysts and news accounts for Kraken wallet mentions; reply with facts when a post misreads a flow. |
| Listing and feedback tally | Log Chinese listing requests and product feedback by asset and theme, and report them monthly to Listings and Product. |
| JD duty | How I would do it | Detailed in |
|---|---|---|
| Monitor social channels and respond promptly | Work the queue by priority and SLA age. Check the status page before replying to any funding post. | §06 |
| Work across platforms, prioritising by urgency and volume | One priority model for every channel: safety first (scams, exposed data), then funds and access, then questions, then praise. | §06 |
| Moderate communities and enforce guidelines | Remove impostors and referral spam, pin the official-accounts list, warn under threads where a fake link appears. | §08 |
| Proactively engage to grow Kraken's voice | Thank advocates, join relevant threads with facts, publish Chinese incident updates. | ★ |
| Partner with internal teams on complex cases | A Zendesk note for every case moved off social: post, findings, reply sent, next owner. A Jira signal when similar posts cluster without a live incident. | §08 |
| Stay current on crypto and Kraken products | Daily read of the status page, listings and Chinese crypto media; keep the macro library current with each launch and delisting. | §09 |
The model the demo runs. Targets are first public response; they are my proposal, to be replaced by the team's own.
| Level | Target | Triggers | First move |
|---|---|---|---|
| P1 | 15 min | Scam or impersonation, impostor reply in the thread, personal data posted publicly, solvency rumour from a large account. | Warn, report, ask for deletion; tag Comms for rumours. |
| P2 | 30 min | Funds or access: withdrawals, deposits, locks, 2FA, card declines, prop payouts, wrong balances. | Check live status, reply, move to DM or ticket. |
| P3 | 60 min | Product and eligibility questions, bugs, support-experience complaints, trading status. | Answer with the fact and the link. |
| P4 | 4 h | Praise, listing requests, general chat. | Thank, log, answer. |
Reach escalates priority: a post from a 50K-follower account moves up a level. Chinese posts are answered in Chinese, with an English gist in the ticket.
Every reply is public and screenshot-able. The demo lints each draft against these before it can be copied.
| Rule | Level | Why |
|---|---|---|
| Never request secrets | fail | Passwords, 2FA codes, seed phrases, remote-desktop access. Mentioning them is fine only as "we never ask". |
| No personal data in public | fail | Account detail moves to DM, @krakensupportZH_bot or a ticket. |
| Official domains only | fail | Impostors reply with "restore" links. The desk links kraken.com, krak.app, ninjatrader.com and payward.com domains only. |
| Channel length | fail | X counts each Chinese character as 2, so a Chinese reply has 140 characters. |
| No timeline promises | warn | A network halt can outlast any estimate. Link the status page instead. |
| Link the live incident | warn | If a status incident matches the post, the reply points to status.kraken.com. |
| Reply in the post's language | warn | An English answer to a Chinese post reads as a brush-off. |
Pull the ticker, check its gateway and pairs on the status page and REST API. Incident open: name it, link it, promise no time. No incident: ask for a DM; three similar posts in 30 minutes raise a signal to on-call.
Reply under the user so the warning sits above the fake link, report the account, log the handle. We never DM first.
Ask the user to delete the post, move to DM, note the exposure in the ticket. Never repeat the data.
No public detail on screening. Acknowledge, move to DM with the ticket number, route to Compliance. Applies to the HTX dust cases.
Tag Comms first. One factual reply linking Proof of Reserves and status, then no back-and-forth. Watch quote-posts for two hours.
Check if the asset already trades (often it does). If not: no comment on future listings, point to @krakenlistings, log the demand.
Breakout payouts, NinjaTrader platform bugs and Krak card issues go to each brand's own support path, from that brand's handle.
Trustpilot and app-store replies: acknowledge, one concrete next step, ticket reference. Reply to every negative review within a day.
| Window | Do | Output |
|---|---|---|
| Days 1 to 30 | Learn Sprinklr, Zendesk and the macro library; shadow shifts; answer English and Chinese queues under review. | Solo shifts at the team's response targets; a list of macros missing a Chinese version. |
| Days 31 to 60 | Fill the Chinese macro gaps; start the daily impostor sweep; publish Chinese incident updates. | Chinese macro parity; a weekly impostor log. |
| Days 61 to 90 | Monthly report on themes, listing demand and sentiment from Chinese channels; propose one process fix from the data. | First monthly CX report; one shipped fix. |
Public data read on 24 September 2026. Follower counts read the same day. The demo's queue posts are fictional; its status and asset data are live.
Demo: kraken-social.leverlabs.workers.dev. Built by me for this application; it is not Kraken software.
Independent CE social homework for the Kraken Client Engagement Social Specialist role · 2026 · edwardtay.com