Microsoft 365
An outbound connector sends customer mail through Frankd. Staff keep using Outlook.
Coming nextRECORDED · STORED IN THE UK
Customer emails you can prove.
What was sent, when, and what happened next. For UK regulated firms.
The problem
A customer says they never received the letter. The ombudsman asks what was sent and when. The mail server has a log line, if anyone kept it, and the sent folder has a copy that anyone could have edited.
Regulated firms are asked to prove their customer communications years later: the FCA's record-keeping rules, the Financial Ombudsman Service, the SRA, a court. A sent folder is not proof.
Frankd records every customer email sent through it the moment it leaves the firm, stores the original in the UK, and gives the firm a record it can hand over.
How it works
Recorded.
Your case system or Microsoft 365 sends customer email through Frankd. The original message is stored unchanged, in the UK, before it goes to the carrier that delivers it.
Chained.
Each message is hashed and linked to the one before it, so a record cannot be altered or removed without the chain showing it.
Sealed.
Every night the day's chain is sealed and timestamped by an independent timestamp authority.
Delivered, and shown.
The carrier's acceptance, the recipient server's reply, bounces and complaints are recorded against the message, with the carrier's own words.
A record
This message was recorded by Frankd on 14 October 2026 at 09:12:03 (London) and has not changed since.
- SHA-256
- 071526a7c04a34f5 c419aaf7e4a8420a 0e6be42019a452f4 f631f5ccc76d995d
- Chain position
- #1,284
- Chain hash
- 145b7600e35fa6e0 c9479c58fd36b35b 12f554f252e61521 b5f7d107f4ca7e20
- Previous hash
- 48728b986e69ed8f 6bcceb7a504bf5e4 d770b18118922ab2 b6862ed42feff798
- Daily seal
- 14 October 2026, Granted
- RFC 3161 timestamp
- Granted, seal written 15 Oct 2026, 01:45:12
- Signer public key
- b+FE3wFT...1Hjj/oA=
Verified 15 Oct 2026, 10:14:27: stored bytes match, chain link holds, seal root, object and signature check
A sample certificate for one message, as a firm's staff see it in Frankd. Every value can be checked independently.
The boundary
Frankd is careful about what it claims. These are the statements the evidence pack makes, word for word.
What it proves
- This message, with these attachments, existed in this form at this time (hash plus timestamp).
- It was handed to the carrier at this time (carrier id).
- The recipient's mail server accepted it at this time with this response, or refused it with this reason (delivery event).
- Nothing in the record has changed since (chain and write-once storage).
What it does not prove
- That a human read it. Open tracking is unreliable (mail clients pre-fetch images) and is arguably inappropriate for regulated correspondence. It can be switched on per firm as a weak signal only.
- That the recipient's server delivered it to the mailbox after accepting it. Acceptance is the strongest evidence available to any sender.
Connecting
Case system
Send through the API, with the case reference on every message.
Available nowReplies
Journaling captures the customer's replies so the record has both sides.
Coming nextWho it is for
Claims management, insurance, consumer credit, solicitors, letting and estate agents, financial advice: any firm that must show what it told a customer. Frankd keeps email originals and seals in London (AWS eu-west-2). Frankd is operated by RAXBI LTD, a UK company.
Originals stored in the UK
Email originals and seals are kept in London, for the retention period the firm sets (seven years by default).
Written once, chained
Each original is written once and hashed into a chain that shows any change.
Independent timestamps
Every day's chain is timestamped by an RFC 3161 authority outside Frankd.
Request access
Tell us who you are and we will arrange a walk-through of a live record. Compliance, operations and IT at a regulated firm are the right people to write.