Define what matters
State the purpose, tone and approved facts. A date, price or promise should come from a source you have checked.
AI, with a clear place in the process
A first draft.
You have the final word.
An assistant to find a phrase, prepare an email and refine a document. Your facts, choices and approval remain part of the process.
Explore this guidePrivate project · public opening in preparation
THE MAILIE APPROACH
A proposal is not permission
01
A brief and a specific document
02
Changes you can still edit
03
A separate human approval
Useful messages. Clear choices.
Information updated on 14 October 2026. These guides describe product choices and private integration work. They are not a certification, reviewed legal terms or a qualification of live providers.
TRY THE REVIEW PROCESS
A proposal you can change.
Local illustration with prewritten fictional content. No AI call, save or send takes place.
01
Choose a brief
Invite registered participants to a workshop. Use a simple tone. Practical details will be checked before sending.
02
Make it your own
Choose a brief, then open its proposal. You can edit the subject and text here.
FROM IDEA TO DRAFT
Create, review, refine.
In the private foundation being integrated, the assistant proposes changes to an editable document. The Studio then lets you work on its blocks and check the rendered email. A brief never grants sending permission.
Keep control of the content
Review the proposal, edit the wording and check the links. Changes after preparing a send require another review.
Approve sending separately
The sender, eligible recipients, content and sending conditions undergo separate checks. A sentence addressed to the AI cannot replace them.
FOCUSED CONTEXT
Information useful for writing.
The intended API context is limited to the brief, the relevant document and excerpts from approved knowledge. The contact database, recipient addresses and access keys do not belong in the model’s context.
A brief or document may itself contain personal information that you enter. Use fictional examples and remove information that is unnecessary for writing.
The OpenAI choice is implemented in the code under development. Processing and retention terms, and permitted data, must be specified before external calls are activated. We do not promise zero provider retention.
EXPLICIT CHOICES
Your key or a Mailie allowance.
Two modes are planned: an organisation’s OpenAI API key, kept on the server, or Mailie AI units tied to a reviewed plan contract. Their usage remains separate.
A budget is reserved before a call. Known provider usage allows actual consumption to be settled; an unknown outcome needs reconciliation. An unusable result does not establish that the call had no cost.
Your organisation’s key
You retain your billing relationship with the provider. Mailie limits still apply to protect the workflow.
Mailie units
The contract must state the limits and terms. This page approves neither a commercial allowance nor a paid model.
Manual editing remains an essential path. Current testing does not qualify live OpenAI calls.
FOR AUTHORISED PRIVATE ACCOUNTS