Fictional product demo
A demo assistant grounded in
fictional mail — with visible sources.
The public demo uses deterministic fictional documents to preview amounts, due dates, deadlines, and renewals. It does not analyze production customer mail, and no production AI provider or private-document pipeline is enabled today.
"Your electric bill increased 18% compared with your three-month average."
- Amount due$177.00
- Payment dueJul 28, 2026
- Higher than usual+18% vs avg
Intended production model
Controls required before customer documents are analyzed.
Nothing is read until you ask for a piece to be opened and scanned.
A production scan would need validated, access-controlled storage before any text processing.
Data retention, training use, region, deletion, and authorization terms must be approved before a provider receives content.
Accuracy, confidence behavior, missing data, and failure modes must be measured on an approved test set.
A summary must remain visibly secondary to the original document and link back to its evidence.
Only reviewed capabilities should appear in a customer account, with clear limitations and recovery behavior.
What the demo previews
Details represented in the fictional fixtures.
The demo presents pre-authored sample findings so you can evaluate the interface and source-linking behavior. These are not production model outputs or customer results.
Who sent it and what kind of document it is — a bill, a notice, a statement, a renewal, an offer.
The amount due, the total, and how it compares to what you've paid before.
Payment due dates, response-by dates, and government or court deadlines, added to your deadlines view.
Policy expirations, registration renewals, warranty end dates, and membership renewals.
Reference and account numbers captured for context and shown masked to protect them.
Discounts, promotions, and price changes worth acting on, with their expiration dates.
Fixture examples
Specific, plain-language sample findings.
Every statement below is tied to the fictional Morgan Avery corpus. None is a claim about a real customer, production accuracy, or savings.
Your electric bill increased 18% compared with your three-month average.
Your vehicle-registration renewal is due in 24 days.
This insurance notice requests action before September 14.
You received three tax documents from two senders.
A promotional offer in this envelope expires next Friday.
Your last twelve utility bills totaled $2,184.
This month's recurring bills are $147 higher than last month.
A late fee appears on this statement for the first time.
This warranty expires in 60 days.
You have received four notices concerning the same account.
Ask across your mail
Ask a demo question and inspect its fictional source.
The deterministic demo answers from its locked fictional corpus and links back to the sample source item so you can inspect the interaction design.
"Which bills are due this month?"
A list of detected bills with amounts and due dates, each linking to its statement.
Shows the document"Which bill increased the most?"
The biggest change against your own history, with the numbers it compared.
Shows the document"Do I have any coupons that haven't expired?"
Active offers with their codes and expiration dates, and the mail they came from.
Shows the document"What deadlines are coming in the next 30 days?"
Renewals, response dates, and expirations in order, each tied to a document.
Shows the documentThese behaviors apply to the fixture-grounded demo. Any production system would require private storage, explicit authorization, provider and retention review, evaluation, error handling, and source access before customer use.
Fictional demo concepts
Additional interface ideas you can preview.
Spots when a recurring bill creeps up, so a slow increase doesn't go unnoticed for a year.
Previews upcoming insurance, registration, membership, warranty, license, and subscription dates from invented fixture documents.
Groups all correspondence from the same sender so you can see the whole relationship at once.
Suggests sensible batches — forward the vehicle mail, archive the paid bills, gather this year's tax documents.
A short weekly note of what needs attention, so the small stuff doesn't pile into a crisis.
Connects related mail — a renewal notice to the new policy, a violation to its follow-up.
Where we're honest
What the assistant is — and isn't.
The public experience is a deterministic fictional prototype. A future production feature would have additional limits and privacy requirements.
- No production customer analysis today
The public assistant reads only fictional fixture data. Production analysis remains unavailable until the required controls are implemented and approved.
- It can be wrong
Automated reading makes mistakes. Summaries and extracted details can contain errors, so treat them as a helpful first pass, not the final word.
- The source stays primary
The fictional demo links findings back to its invented source document. Any future production feature must keep the authorized scan available and must not overwrite it with a summary.
- Not professional advice
Summaries are not legal, tax, medical, or financial advice. For decisions that matter, rely on your documents and a qualified professional.
Ask it something in the demo.
Open a fictional traveler's sample mail and test the deterministic prototype. The results are simulated product examples, not customer outcomes.