TemplatesGet a demo →Book a meeting

Plan rules answered in plain words, with the section quoted

Anyone on staff can ask how the plan treats part-time service or early retirement and get an answer quoted from the governing section. Where two documents disagree, it names the more recent and quotes both instead of choosing between them.

Support · Pensions & retirement · Someone asks · 4 steps · Reads your documents

AI Factory · Plan document assistant · run 1221a real run on synthetic data · recorded Sep 11, 2026
QuestionQuestion1 ms
RetrieveRetrieve561 ms3 passages
AnswerAnswer1.2 s
Answer shownAnswer shown1 ms
4 of 4 steps ran1.8 s end to end<$0.001 model costDrag the canvas, or any step, to move it around.
Asked: “What is the normal retirement age under the plan?”

The normal retirement age under the plan is 65. This is stated in the passage: "Normal retirement age is 65" (source [1], page not specified).

Why teams run it

Plan documents, amendments, policies and FAQs accumulate over decades, and the person who knows which clause governs is usually the most senior administrator on the team. Everyone else waits for that person, or answers from an out-of-date copy.

How it is governed

  • Retrieval respects each source’s own permissions for the person asking.
  • Every claim in the answer must carry a citation to a document.
  • It is instructed never to state an amount or entitlement the sources lack.
  • Every question and answer is kept in the run history.
Who runs it
Pension administrators; Member services staff; Benefits and compliance officers.
What you supply
Your plan documents, policies and FAQs as knowledge sources.

It ships with test questions

  • What is the normal retirement age under the plan?
  • How is service counted for someone who works part-time?
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
Add amendments and board resolutions as knowledge sources alongside the plan; Retrieve more passages when the plan is spread across many documents; Attach a skill carrying your house terms for each benefit type.
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

How does it handle documents that contradict each other?
It names the more recent document and quotes both, leaving the ruling to your staff. That keeps a superseded clause from being presented as current without anyone noticing.
Can members use it directly?
It is written for staff. For replies a member will read, the Member service copilot template is the better starting point, because it drafts for your team and escalates to a person.
What does it need before it’s useful?
Your plan documents, policies and FAQs loaded as knowledge sources. Once they are in, you can test it in the builder with the questions that ship with the template, such as the normal retirement age, before anyone else uses it.

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.