One member’s full record, answered from your administration system
Staff enter a member number and the flow queries your administration system, totals the contribution record in code, and writes a plain summary with every figure quoted as computed. Nobody pieces a member together across several screens, and no model does the arithmetic.
Support · Pensions & retirement · Someone asks · 5 steps · Your database
QuestionWhich member?
Query a databaseRead the member record
Work out the numbersSummarise contributions
AnswerDescribe the member
Answer shownThe answer
5 steps in the flowDrag the canvas, or any step, to move it around.
Why teams run it
When a member calls, service staff rebuild the picture by hand: status in one screen, employer in another, and a contribution history that has to be scrolled through and added up. A general-purpose assistant is worse, because it will state a total confidently whether or not it ever read one.
How it is governed
- Queries are read-only: SELECT statements through a connection an administrator sets up.
- The member number is bound as a value, so it can never alter the query.
- The database host must be on your approved list before any connection opens.
- Every run is recorded step by step in the run history.
- Who runs it
- Member services representatives; Pension administrators; Contributions team leads.
- What you supply
- A read-only database connection to your member administration system under Admin → Databases, with the query pointed at your own tables.
It ships with test questions
- 100245
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
- Rewrite the query for your own member and contribution tables; Group contributions by period or plan instead of by employer; Choose a stronger model for the written summary, or a faster one.
Questions buyers ask
- Does the model ever calculate a member’s totals?
- No. The database returns the rows and the table step does the counting and summing in code; the model is instructed to quote those figures exactly and never recalculate or round them. If the query returns nothing, the answer says no member was found with that number.
- Which administration systems can it read?
- It reads any PostgreSQL database your administrators connect as read-only, once the query is rewritten for your tables. Drivers for other database engines are not yet included.
- Who can see member data through this flow?
- Only people you give access to the agent can run it, and the database connection itself is set up by an administrator. Every run, including the number asked about and the answer given, is kept in the run history.
Related templates
All 60 templates- Member service copilotAnswers a member’s question from the plan documents with the section quoted, drafts the reply, and hands anything the documents do not settle to a person.SupportSomeone asks7 stepsa person approvesa recorded run
- Plan document assistantLets staff ask the plan documents, policies and FAQs a question in plain words, and answers with the section it came from.SupportSomeone asks4 stepsa recorded run
- Retirement application reviewReads a retirement application against the plan rules, lists what is missing or inconsistent, and drafts the reply — which a person approves before anything is sent.OperationsA document or recording is attached6 stepsa person approvesa recorded run
- Enrolment completeness checkChecks each new enrolment an employer submits for the details the plan requires, and asks a person to chase the employer for anything missing before the member is set up.OperationsSomething arrives from another system5 stepsa person approvesa recorded run
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.