What Fasset customers write in about, what the public help centre says, the order I would work a queue in, and a working case desk that checks AI-drafted replies before they go out.
AI answers the routine questions. The analyst takes the cases where money, cards or access are at stake, and owns each one to the end, across shifts.
Mostly Pakistan, Bangladesh and the Gulf, writing in English as a second language, on a card, a USD account, crypto and tokenized stocks in one app.
A case desk: identity check first, scams at the top of the queue, card declines decoded, withdrawals traced live, AI drafts checked against the help centre.
| Takeaway | Why it matters on the desk |
|---|---|
| Possible loss of funds goes first | Impostors pose as Fasset staff on messaging apps. A customer mid-scam needs one line before anything else: do not send. |
| Most card declines are a card-balance question | The card spends its own USD balance, topped up from USDT. A customer with 1,000 USDT in the wallet can still be declined at a hotel. |
| The 5 October login change will drive tickets | Login is now phone number, OTP and PIN. Customers who used Google sign-in and lost their old SIM need the identity route to change number. |
| AI drafts are fast and confidently wrong | In the demo, every queued draft has a fault a person must catch: an OTP request, a promise, a tip-off, a balance shared before ID&V. |
| Saved replies go stale with the help centre | The desk re-reads the articles its numbers come from. A changed article surfaces before a customer gets an old figure. |
One app for a USD account, a Visa card, crypto, tokenized stocks and gold, and Shariah-screened savings. Each product brings its own partner and its own kind of ticket.
| Product | How it works (help centre) | Tickets it produces |
|---|---|---|
| Fasset Card | Prepaid Visa in USD, funded from USDT. 9.99 USDT to issue, 10,000 USD daily spend, top-ups of 1 to 5,000 USDT. Paying in another currency costs about 2% to 3%. | Declines abroad, holds at hotels, Apple Pay not available, disputes (30 to 60 days), unrecognised payments. |
| Global USD Account | US account details for ACH and an account for SWIFT, through banking partners. SWIFT in takes 1 to 3 business days, up to 5. | Incoming transfer pending or under review, name mismatch, recipient not credited, requests to recall a final transfer. |
| Crypto deposits and withdrawals | USDT and USDC on several networks, plus BTC, ETH, SOL and others. Withdrawals up to USD 20,000 each and 100,000 a day. Large ones may get an extra review. | "Not arrived" (usually confirmed onchain, waiting on the receiver), wrong network, review holds. |
| Trading and Earn | Crypto, tokenized US stocks, ETFs, gold and funds. Savings through a Wakalah structure. Every asset screened for Shariah fit. | Fees and spread questions, order and price questions, Shariah questions that need a precise, plain answer. |
| Login and verification | Phone number, OTP and Login PIN since 5 Oct 2026. Automated ID check with 3 attempts, then manual review in 1 to 2 business days. | OTP not arriving, old number lost, KYC rejected (glare, country of issue vs residence), one ID per account. |
Source: Fasset help centre (fassethelpsupport.zendesk.com), read in full through its public API on 31 Oct 2026. Article links in §09.
Customers compare Fasset with a different app for each thing it does. Support has to answer the comparison in the ticket, so knowing what they came from helps.
| What the customer uses it for | Apps they compare with | What support has to explain about Fasset |
|---|---|---|
| Getting paid in USD as a freelancer | Payoneer, Wise, Grey | Which rail they used (ACH or SWIFT), why a transfer is under review, why the name on the payment must match the profile. |
| A card funded by crypto | RedotPay, exchange-issued cards | The card balance is separate from the wallet; top up first. FX cost and holds at hotels and car hire. |
| Shariah-screened investing | Wahed and other halal investing apps | How screening works, what the Wakalah savings structure is, and staying clear of advice. |
| Buying crypto in the Gulf | Rain, BitOasis, global exchanges | Networks, withdrawal limits and review times, and the local wire options in the UAE and Bahrain. |
| Cashing out to a local bank in Pakistan | Exchange P2P desks | The local payout and P2P routes, their timings, and why a completed local payout cannot be recalled. |
The gap Fasset fills: all of these in one regulated app, with Shariah screening. The support cost of it: one customer can have a card, a USD transfer and a crypto withdrawal problem in the same week, so an analyst needs all five areas above.
Recurring themes in public App Store and Trustpilot reviews, 2025 to Oct 2026, with what I would check first.
| Theme | What customers say | First check on the desk |
|---|---|---|
| Verification stalls | Pending for days, rejected several times, email loops. | Which rejection reason; whether the 3 automated attempts are used and manual review is open; country of issue vs residence. |
| Card problems | Cannot add to Apple Pay, activation, merchant declines, a promo price not applied. | Card status and balance, decline code, the Apple Pay article, the promo terms. |
| Getting money out | Few cash-out routes for their country, holds that feel open-ended. | Which routes their country has; review status; a date for the next update. |
| Locked out | Logged out after a deposit, OTP not arriving. | Login change since 5 Oct; OTP channel and number on file; device history. |
| Slow replies | Email-only support, waiting days on stuck funds. | Own the case, give a time for the next update, and keep it. |
App Store ratings by country (iTunes API, 31 Oct 2026): Pakistan 3.58 from 237, US 3.39 from 61, UAE 4.47 from 36, Malaysia 4.33 from 6. Trustpilot 2.6 from 98 reviews.
The JD asks the analyst to keep help articles and saved replies accurate. I read all 231 public English articles. The help centre is detailed and recently updated (most card and login articles were revised in October). These are the items I would raise first.
| Finding | Detail | Suggested fix |
|---|---|---|
| Contact article will need a rewrite | "How do I contact Fasset?" (updated 23 Oct) gives hours of 01:00 to 17:00 GMT and says there is no inbound phone or live chat. The JD describes calls, chats and round-the-clock cover. | Update hours and channels on the day the new coverage starts, and the saved replies that quote them. |
| Lost phone outside hours | "Lost or stolen device": if the customer is logged out, they email and the account is suspended "as soon as we see your email". | With night cover, state a response time for this email, or add a self-serve emergency lock. |
| No complaints page | No public article mentions complaints, how they are handled or how long a response takes. | A short complaints article per licensed entity: how to raise one, when to expect a reply, where to go next. |
| Links that go nowhere | 24 links across the help centre: 16 to articles that are deleted or agent-only, 5 to retired domains or a search page, 3 placeholder links. | A monthly link check. The demo's Sources tab runs one live. |
| Country lists disagree | A few countries are on the card-issuance list but on the unsupported list for sign-up; the UAE and Bahrain are on neither sign-up list. | One country table, linked from each article. |
| ACH eligibility stated two ways | Three articles say Bangladesh only; one says Pakistan and Bangladesh. | Confirm with the product owner and align all four. |
Read through the public Zendesk Help Center API on 31 Oct 2026. The link audit is live in the demo (Sources tab), so the counts update as articles change.
Each line of the JD, how I would do it, and where the demo shows it.
| JD duty | How I would do it | In the demo |
|---|---|---|
| Calls, chats and emails, first contact resolution | Open with the answer if I have it. For card and withdrawal cases most answers are in the back office and the help centre: the decline code, the card balance, the chain status. | Queue, Card declines, Transfer tracer |
| Own each case to resolution | When it moves to another team, the customer gets a time for the next update and I keep it. Open cases go on the handover with the promise made. | Handover |
| Turn frustrated customers into confident ones | One honest line, then the facts, then what happens next and when. No blame, no jargon. | Reply checks: no-empathy, blame, jargon |
| Cards, deposits, withdrawals, transfers, ID verification | A check order for each: decline code then card balance then holds; chain status then network then receiver; rejection reason then attempts left. | Investigate step per case |
| Work alongside AI tools | Read every AI draft as if a new colleague wrote it. Fix it, and log what it got wrong so the prompt or the article behind it gets fixed. | AI draft, Patterns |
| Follow procedures, escalate with a clear ask | Escalation note: what happened, what I checked, and one specific ask with a time. | Escalation note template |
| Spot patterns behind repeat contacts | Tag every case with a contact driver. Weekly note with counts and one root-cause ask per driver. | Patterns, CSV |
| Keep help articles and saved replies accurate | Every saved reply cites its article. Re-check the cited line when the article changes. | Sources |
| Verify identity first | No account detail until verification passes. Never ask for OTP, PIN, password or card number. Third parties get nothing. | Step 1, FC-1047 |
| Log and categorise every complaint | Treat a complaint as a complaint when the customer expresses dissatisfaction and wants a remedy, even without the word. Log the clock on day one. | Complaint logging |
| Security, scams, loss of funds first | Those cases jump the queue. First line to a customer mid-scam: do not send anything. | Queue order, FC-1041 |
| Fair treatment, extra care for vulnerable customers | Watch for coaching by a third party, life savings, illness, bereavement. Slow down, confirm understanding, check for pressure before money moves. | Care flags |
Order: security, suspected scams and possible loss of funds; then vulnerable customers; then complaints on a clock; then the rest by SLA. Five cases from the demo, built on Fasset's own help-centre rules.
| Case | What I check, in order | What the AI draft got wrong | What I send |
|---|---|---|---|
| Asked to pay a "release fee" to withdraw profits | No trades in the app; no such fee exists; address is external; hold any outbound transfer. | Offered to continue on WhatsApp and promised the funds after the fee. | Do not send anything. The person is not Fasset. Fraud team has it. Next update by a set time. |
| OTP not requested, then logged out | Device and login history, number-change requests, outbound transfers. Suspend if anything is off. | Asked the customer to read out the OTP. | What I have done to protect the account, and when I call back. |
| Card declined at a hotel abroad | Code 51; card balance 182 USD; hold of about 295 USD; USDT is in the wallet. | Said the card is blocked in Japan and promised a refund in 2 hours. | Your card works there. Top up the card from your wallet, then ask the hotel to retry. |
| Withdrawal "not arrived" | Trace the hash: network, status, confirmations, receiving address. | Said it was still processing and would "definitely" arrive in 24 hours. | Confirmed onchain at a given time, with the explorer link for the receiving platform. |
| Large withdrawal in review | Review status; a date from the review team; what the customer may need to send. | Told the customer compliance flagged them for AML. That is tipping-off. | Larger withdrawals can get an extra review; I cannot share details; next update by a set time. |
The checks I run on any draft, from AI or a colleague. The demo runs them as you type and blocks sending on the first five.
| Check | Level | Why |
|---|---|---|
| Asks for a secret | block | Fasset's help centre says it never asks for card number, CVV, PIN, OTP or password. A draft that does teaches customers to trust scammers. |
| Moves the customer off channel | block | Impostors work on messaging apps. Support stays in the ticket, email or an official callback. |
| Links off Fasset's domains | block | Only official links in a reply. |
| Investment advice | block | Explain how a product works and leave the decision to the customer. |
| Tipping-off, or account detail before ID&V | block | Never disclose a review or share account detail before identity is verified. |
| Promises, blame, missing next update | fix | Commit to the next update rather than an outcome the desk does not control. |
| Numbers vs the help centre | fix | Limits, fees and timelines are checked against the article they come from. |
Every issue found in an AI draft is logged with the case and the rule. A weekly count by rule shows which prompt or article needs work.
What I would track on my own cases, alongside the team's targets.
| Metric | Why it matters |
|---|---|
| First-contact resolution | The JD's first duty. Split by driver: card and withdrawal cases should resolve first time far more often than KYC. |
| Next-update promises kept | The measure of owning a case. Every open case has a time; count the ones missed. |
| Reopened within 7 days | A case closed with the wrong answer comes back. |
| AI draft edit rate, by rule | How often a person had to change the draft, and why. Falls as prompts and articles improve. |
| Complaints inside their clock | Every complaint logged on day one, and the breaches reported. |
| Time to first action on scam and takeover cases | Minutes matter here more than CSAT. |
Role: Customer Support Analyst, Fasset, Kuala Lumpur (public job posting, 2026).
Help centre: all 231 public English articles, read through the Zendesk Help Center API on 31 Oct 2026. Card, login and contact articles were current as of October 2026.
Reviews: App Store ratings and recent reviews by country through Apple's public iTunes API; Trustpilot public page. Read 31 Oct 2026.
The demo's cases and customers are synthetic. Transaction hashes in it are real, fetched live from public nodes, and are not Fasset transactions. Complaint clocks in the demo are placeholders, since no public timeline exists.
Demo: fasset-cs.pages.dev · Help centre: How do I contact Fasset? · What changed about logging in · Card payment declined · Virtual card fees and limits · Pending charges and holds · Disputing a card transaction · Crypto withdrawal taking too long · Update your phone number · Lost or stolen device · Protect yourself from trading scams · Why was my ID rejected? · Trustpilot
Independent homework for the Fasset Customer Support Analyst role · 2026 · edwardtay.com