TemplatesGet a demo →Book a meeting

Member letters drafted in plain language, approved before release

Describe what needs saying and to whom, and the flow drafts the communication from your plan documents and house style, leading with any action the reader must take and by when. Nothing is released until your communications team approves it.

Marketing · Pensions & retirement · Someone asks · 6 steps · Reads your documentsA person is asked at “Ask a person”

AI Factory · Member communication drafterthe flow as it opens in the builder
QuestionQuestion
RetrieveRetrieve
AnswerAnswer
Ask a personAsk a person
Answer shownAnswer shown
Answer shownHeld back
6 steps in the flowDrag the canvas, or any step, to move it around.

Why teams run it

Every notice to members or employers has to be accurate to the plan, readable by someone who has never opened it, and consistent with the last thing the fund said. Drafting from scratch pulls in a writer, an administrator and a reviewer for each one, and plain language is usually the first thing lost.

How it is governed

  • No draft is released until the communications team approves it.
  • A rejected draft ends the run and is recorded as not sent.
  • It is instructed never to state an amount or date the plan does not give.
  • The draft, the approver and the decision are kept in the run history.
Who runs it
Member communications managers; Pension administrators; Employer services teams.
What you supply
Your plan documents and house style as knowledge sources.

It ships with test questions

  • Tell members their annual statement is now available online
  • Remind employers when this month’s contributions are due
What “a person approves” looks like in the product: the run stops, the banner says what approving will do, and until someone decides, nothing leaves the system. A demo workspace on synthetic data.

From template to a live agent

The same builder, tests and release review apply to a template as to anything built from scratch.

Open it as a working flow
Every step, source, branch and approval is already in place, and every one of them can be changed before it runs on your data.
Prove it before it ships
An evaluation set can gate the release, so a change that breaks an answer never reaches anyone. A question it cannot answer from the sources leaves the gate unproven, not passed.
Keep a person on the decisions
A run that needs a decision stops and says exactly what approving will do, and who it is waiting for.
Publish where people work
A form, an embedded widget, Microsoft Teams or a scheduled batch — with its own access and limits per deployment.
What teams usually change
Load your house style guide and past notices as knowledge sources; Name who approves: the communications team, compliance, or both in turn; Set reading level and length limits in the drafting instructions.
Step 02, in the product: an evaluation set that gates the release. A question it cannot answer from the sources leaves the gate unproven, not passed. A demo workspace on synthetic data.

Questions buyers ask

Does it send the communication?
No. Approval releases the draft to your team, who send it through your usual email or print process; the template contains no sending step.
How does it keep communications accurate to the plan?
It drafts from the plan documents retrieved for the message and names the section behind every rule it mentions. It is instructed never to state a benefit amount, payment date or entitlement the sources do not give.
Can it write for employers as well as members?
Yes. You say who the communication is for when you start the run, and the same plan sources and approval apply; the template’s test questions include a reminder to employers about contribution deadlines.

See it run on your own data

We open it in the builder, point it at a sample of your documents and systems, and run it with you.