App Copy Audit — Feb 2026

Fido · GH, UG, ZM · 22 proposed changes

4
Critical
7
Important
6
Cosmetic
1
Decision

About this audit

What was audited
  • ~157 screens across 5 flows
  • Ghana, Uganda, Zambia variants
  • Error states, CTAs, permission screens, onboarding, credit, repayment
Data sources
  • Figma file PfVoDny9zc7tcCgtS1NDWW
  • Tone of Voice Handbook
  • Customer Support KB
Audit dimensions
  • Error actionability
  • Terminology consistency
  • CTA clarity
  • Tone of Voice compliance
  • Country coverage parity
  • Trust signal consistency
What this report is
  • 22 specific copy changes, each with current text and proposed replacement
  • Node IDs included for direct Figma reference
  • Not a redesign — copy changes only
Ready to implement
Once the team agrees on changes, I can implement them directly in Figma Figma — I have write access and know the node IDs for every screen in this report. No designer handoff needed for copy-only changes.

For changes that also touch code (e.g. C2 contextual error variants), Rachel can implement from a spec. Add comments or flag disagreements in the sheet, then give the go-ahead.
↗ Comment sheet — Current · Proposed · Comments
Critical
C1 Grammar error on settlement screen
Current
"Stay qualify for credit offers"
Proposed
"Stay qualified for credit offers"
74049:34754 Settlement bottom sheet · visible to overdue borrowers 5 min
C2 Generic error popup — replace with contextual variants
Current (all unhandled errors)
"It seems like we've encountered an error. Please try again later or contact our support team for further assistance."
Proposed (4 contextual variants)
MoMo: "Your payment didn't go through. Check your MoMo balance and try again." · Upload: "That file couldn't be uploaded. Check your connection." · KYC: "We couldn't save your details. Try again or reach out." · Generic: "Something didn't work. Try again, or reach out if it keeps happening."
25564:17850 Catch-all error popup — used across every flow 2–3 days (design + dev)
C3 Remove "you must" from permission denied screen
Current
"To continue, you must allow Fido to access your {permission}."
Proposed
"To continue, please allow Fido to access your {permission}. You can do this in Settings > Apps > Fido."
Permission denied screen · Survey flow 1.1 ToV violation + adds actionable path to Settings 30 min
C4 Credit errors must acknowledge money movement
Current (credit draw / repayment errors)
"Something went wrong"
Proposed
"Your payment is being processed. Check your MoMo balance — if funds were deducted but not reflected in Fido, contact us immediately."
Credit flow 3.38 · draw + repayment error states Generic error when money is moving creates anxiety and support calls 1–2 days
Important
I1 Resolve "Credit" vs "Loan" terminology conflict
Product + Brand need to align: keep "Credit" (current nav direction) or revert to "Loan" (ToV standard). CX agents currently receive conflicting guidance. Once decided, ~40 screens need updating.
~40 screens across all flows Decision (1 meeting) + audit pass (1 day)
I2 Standardize repayment CTA to "Pay back"
Current (3 variants in use)
"Pay back" · "Repay" · "Pay now"
Proposed
"Pay back" everywhere — most user-tested, appears on primary loan cards
~10 screens Design audit + 10 screen updates
I3 Replace "bill prompt" with plain language
Current
"bill prompt"
Proposed
"Check your phone for a payment request from [Provider]"
Payment screens · 3–4 instances Telco jargon users don't recognise 30 min
I4 Soften score calculation wait screen
Current
"Please do not leave this screen."
Proposed
"Hang tight! This will only take a moment."
Score calculation screen 1.1 Sounds restrictive at a high-anticipation moment 5 min
I5 Add KYC processing time estimate for Zambia
Zambia — Current
(no estimate shown)
Proposed
"Your ID is being verified. This usually takes 2 business days."
KYC pending screen · ZM only GH and UG both show "2 business days" — ZM leaves users with no expectation 1 screen + confirm ZM SLA
I6 Tell users why ID scan failed
Current
"Failed to identify your ID. Please try again."
Proposed
"We couldn't read your ID. Make sure it's a Ghana Card, well-lit, and all 4 corners are visible."
ID scan failure screen · KYC flow 3.7 Top KYC drop-off point — retry fails for the same reason without guidance 1 screen
I7 Document Zambia repayment channels in-app
ZM — Current
(no offline repayment channels listed)
Proposed
Add ZM repayment channels equivalent to GH (App, USSD, mobile money). Requires confirming ZM-specific channels + USSD shortcode.
Repayment help screen · ZM only CX agents can't assist ZM users with offline repayment Content research + 1 screen
Cosmetic
N1 "More details" → "View loan details"
Active loan card component · high-frequency 1 component
N2 Differentiate "Learn more" CTAs by context
Current (used 6+ times)
"Learn more"
Proposed (per context)
"See savings benefits" · "How KYC works" · "Scan tips" · "About Fido Score"
6 screens 6 screen updates
N3 Standardize privacy phrasing across permission screens
Current (3 variants)
"third parties" · "3rd party" · "any third party"
Proposed
"third parties" — one standard
4–5 permission screens 30 min
N4 Add local flavor to error recovery copy
Current
Generic global English on all error/retry screens
Proposed · GH only
"No wahala, let's try again" · "E go be fine" — on retry CTAs where tone fits
5–10 error / retry screens Creative + implementation
N5 Standardize due date format
Current (2 variants)
"Payment due [date]" · "Due by [date]"
Proposed
"Due by [date]" everywhere
Legacy screen cleanup Audit + updates
N6 Soften credit declined message
Current
"Sorry, credit is declined"
Proposed
"We weren't able to approve your application this time."
Credit declined screen 3.12 1 screen