FXpress · AI Co-Pilot for Cross-Border Remittance · Design Iterations
| Property | Value |
|---|---|
| 🏷️ Status | Complete |
| 🔬 Source | Usability Debrief · 6 post-test decisions |
| 👥 Participants | Janice · Jerry · Gabriela · Jin · Ollie |
| 🔖 Format | Before → After · participant attribution · implementation status |
Issue: "Use This Trigger" as a CTA label was ambiguous — it referred to a trigger the user hadn't created yet, so "this trigger" had no antecedent. Jin, the most FX-literate participant, completed the task but flagged the label as vague, which suggested it would be worse for less confident users.
Before: "Use This Trigger"
After: Renamed "Set Trigger for Best Rate" — makes the outcome explicit. The label now answers "what will happen if I tap this?" without requiring the user to read the Fexi recommendation first.
Attribution: Jin (flagged the label as vague during trigger setup)
Implementation: ✅ Committed · live in the widget
Issue: The trigger CTA and "Send Now" had equal visual weight as buttons. Users hesitated between them — not because the wrong one was primary, but because nothing signaled which was which. Two of five tapped Send Now, backtracked, then chose the trigger.
Before: Both options as filled blue buttons — same size, same weight, no visual distinction
After: Distinct visual treatments — Send Now as the filled primary button (it is the most common action a remittance user takes), Set Trigger for Best Rate as the outline secondary button. The two are now immediately distinguishable, which removes the hesitation; Send Now remains primary because sending is the core job, and the testing showed it is what users reach for first.
Attribution: Jerry (misclicked Send Now during the trigger task, backtracked)
Implementation: ✅ Committed · live in the widget
Issue: "Threshold Amount" with a numeric input (e.g. 1,380) gave no indication of which currency the threshold referred to. Across corridors this was genuinely ambiguous — 1,380 could plausibly be USD, KRW, or KES.