Give every sensitive request a trusted route back.
Build trusted links between colleagues first, then extend them to the suppliers and clients you work with. When an unusual instruction arrives, check the exact request outside the call, email, message, or video meeting that carried it.
CodeWords strengthens an existing approval process. It does not replace dual control, payment limits, call-backs, or formal identity checks.
New CodeWords challenge
From a trusted connection
Payment approval
Approve £18,400 to new supplier details?
Biometric approval required
Start internally. Extend trust deliberately.
Create a known route back to the people whose requests can move money, expose data, grant access, or change a plan.
Inside your organisation
Connect colleagues, leaders, finance, IT, and operations before an urgent instruction arrives. Give each person a separate way to check the exact request.
With suppliers
Create trusted links with regular supplier contacts, then challenge bank-detail changes, unusual invoices, urgent orders, and account requests outside email.
With clients
Give named client contacts a trusted route for checking instructions, file requests, approvals, and last-minute changes before either side acts.
Across access, money, and data
Use the same checking habit before changing account access, releasing a payment, sharing a sensitive file, or accepting new contact details.
Meet once. Check from anywhere.
Build the trusted links first
Start with the people inside your organisation, then add named supplier and client contacts. Direct setup binds each relationship to the phones used when they meet.
Challenge the exact action
When a sensitive instruction arrives, record what is being requested, including the amount, recipient, account, file, or access change.
Wait for the separate answer
The trusted phone shows the action and requires protected approval. Your team sees an approved, denied, pressured, expired, or revoked result before acting.
The technology only works when checking is normal.
CodeWords adds a layer of trust, not an invisible shield. Your organisation still needs a clear rule: when a request is urgent, unusual, or sensitive, stop the original conversation and challenge the action. Leaders must make that behaviour expected, especially when a request appears to come from them.
Pause the original call, message, or meeting.
Open CodeWords independently, never from a supplied link.
Challenge the exact action, not just the person’s name.
Keep your existing approvals, call-backs, and account controls.
Familiar faces are no longer enough.
A convincing video meeting can show familiar colleagues and still be an impersonation. CodeWords does not analyse the face, voice, or email. It sends the exact action to a phone connected through direct setup, so the answer returns through a separate signed path.
Read the security modelTrusted phones are added while both people are together
Changing signed QR frames and a fresh signed Bluetooth challenge
Each approval is signed by a key held on the enrolled phone
Biometrics protect sensitive approvals on supported devices
Challenges name the exact request and expire after a short time
Device recovery revokes the old phone and trusted connections
What an approval means
CodeWords confirms that the enrolled phone approved the exact request shown in the app.
It does not prove that a voice, message, video image, or legal identity is genuine. A person may be under pressure, an unlocked phone may be compromised, or the wrong person may have been trusted at the first meeting. Stop if anything still feels wrong.
What people ask before they start
No. CodeWords adds a trusted device challenge to your existing controls. Keep dual approvals, independent call-backs, payment limits, bank controls, and access policies in place.
Yes. The request can arrive through any medium because the challenge and response happen through the separate CodeWords app.
It proves that the enrolled phone signed approval for the exact request shown in CodeWords. It does not prove that the original voice, email, or video was genuine, or that the phone holder was free from pressure.
Start inside your organisation with one narrow workflow, such as bank-detail changes or urgent executive requests. Give the team a clear rule for when to stop and check. Add selected suppliers or clients only after that habit works internally.
Add a trusted check before the next sensitive request.
Book a short call to choose the first high-risk workflow for your CodeWords rollout.