Once the Eternal Pro MCP Connector is set up, you configure Eternal Pro by describing what you want. This article lists everything Claude can do and gives you wording that works. You do not need to memorise operation names, plain English is enough. But knowing the boundaries saves you asking for things that are deliberately out of reach.
Start every session here: "Give me an overview of my intake." Claude will summarise every questionnaire you have, how many questions each holds, the estimated time to complete, and the section structure. It is the fastest way to get oriented, and it gives Claude the context it needs for everything that follows.
Finding out what is there
- Summarise every questionnaire at once, with counts, estimated time and section structure
- List your questionnaires
- List the questions in one questionnaire, in display order
- Show the full detail of a single question, including its choices
- Run a health check on a questionnaire
The health check is worth running before you launch anything. It looks for the problems that actually break a questionnaire in front of a client: dead-end navigation, orphaned or self-referencing parent sections, blank questions, colliding choice ids, removed structural pages and orphaned overrides. It is strictly read-only.
Try: "Diagnose my Standard Intake questionnaire and tell me what's wrong with it."
Editing questions
- Reword a question, its description, help text, slug, link or estimated minutes
- Change a question's setting flags — required, heading, export behaviour, spouse column
- Replace the choice list on a question you authored, preserving answers already given
- Add a new question
- Duplicate a question you added, placing the copy right after the original
- Hide a question (reversible) or restore one you hid
- Permanently purge a question you authored and its overrides (not reversible)
- Reorder every question in a questionnaire at once
- Move one question before or after another, leaving everything else in place
- Promote a nested heading back to the top level
Try: "Add a required question after the digital assets section asking whether the client holds cryptocurrency, with Yes / No / Not sure as the choices."
Conditional questions
Setting flags are how you show a question only to the right clients — only clients with children, only clients with a current spouse or partner, only clients who are single, divorced, separated, widowed, or other. Say it in plain terms and Claude will set the right flag: "Only show this question to clients who have children."
One thing to know: marital status is answered by a single built-in question, and every marital gate reads that one answer. If you add your own separate "are you married?" question, none of the gates will fire and the questions behind them will never appear. Claude knows this and will steer you toward extending the built-in question instead. Let it.
The same applies to people generally. Spouses, children and advisors entered through the built-in people questions are reused across the whole intake, drive the conditional logic, and flow into your exports and the emergency card. A hand-built table of children is dead text by comparison, and the client ends up typing the same person in twice.
Rewriting choices without losing answers
When Claude replaces a choice list, it reads the existing list first and passes the original choice ids back. Answers clients have already given against those choices stay attached. This is why "reword the third option" is safe, and why it is worth letting Claude look before it writes rather than dictating a fresh list from scratch.
Managing questionnaires
- Create a new questionnaire by duplicating an existing one
- Rename one
- Reset one to its baseline, keeping the questions you added yourself
- Delete one and all of its overrides (not reversible)
- Set which questionnaire new clients receive by default
- Export a questionnaire as a portable definition, and import one to create a new questionnaire
Try: "Duplicate my Standard Intake, call it Trust Intake, then remove the sections that only apply to simple wills."
Export/import is the clean way to move a questionnaire between environments, or to keep a copy before a big reorganisation. Importing over a questionnaire that already exists replaces it entirely, so Claude will spell out what that costs before it does anything.
Clients and matters
- Create a new client
- Look up one client by exact email address or site id, and list their matters
- Change which questionnaire a client's matter uses
- List the staff a client can be assigned to
- Assign a client to a member of staff
- Restrict a client site so only Firm Administrators can reach it, or lift that restriction
Creating a client emails them their sign-in details immediately. There is no draft state. Claude will read the name and address back to you before it does anything, so check the spelling of the email address at that point — not afterwards. Client creation is rate limited per firm.
Client lookup needs an exact email address; it is not a search, and it cannot be used to find out which addresses exist at your firm, because an unknown address and an address with no client site give the same answer. What comes back is the site id, the matters on it, who the client is assigned to and whether the site is restricted. Never the client's name, and never the answers inside the matter.
Changing the questionnaire on a matter changes what that client sees, including part way through if they have already started. Answers given against the old questions stay where they are rather than moving across, so Claude will say so and wait for you to confirm.
Firm settings
- List the firm-level settings you are allowed to read or change
- Read or change one setting
- Read or change the intake progress bar colours and height
- Clear the cached question set so the next page load refetches it
The settings you reach cover firm contact details shown on the intake, the notification address, the default questionnaire, welcome messages, the default interface mode, vault directory names, and the client feature toggles — reminders, emergency cards, memorial, Legacy Manager, password manager, vault access, asset managers, disposition choices, AI summaries and bank connections.
Two warnings. Most of those toggles are phrased as disable switches, so setting one to on turns the feature off for clients. Ask Claude to read the setting back to you in plain terms after changing it. And credentials of every kind are excluded entirely — Claude cannot read or rewrite your Anthropic key or any integration token.
The progress bar is the one setting here that is account-wide rather than per questionnaire, so a colour change reaches every client you have.
Try: "List my firm settings and tell me which client features are currently turned off."
Email and message templates
- List every template with its current subject and body
- Change the subject or body of one template
- Find and replace a phrase across every template at once
The bulk replace reports exactly what it would change and waits for your confirmation before writing. Read that preview properly — it is the whole point of the step, and undoing a confirmed bulk replace means running a second replace in the other direction, then fixing by hand anything the reverse pass caught that should have been left alone.
You can narrow a bulk replace to named templates rather than running it across all of them. Worth doing when the phrase appears somewhere it should legitimately stay.
Try: "Replace 'Digital Executor' with 'Legacy Manager' across all my templates — show me what would change first."
Document exports
- Report how each export type is currently styled
- Set fonts, sizes, colours and boldness for headings and paragraphs
- Upload a Word document to use as the styling reference, or remove it
- Put a logo in the header or footer, or remove it
- Add a fixed .docx or .pdf that goes into every packet of one export type
- Remove an attachment, or change where attachments sit in the packet and in what order
- Copy the questionnaire design onto another export type
There are three export types — the questionnaire, the inventory, and generated documents — and each carries its own design, its own attachments and its own header and footer images. Copying the questionnaire design across is the quick way to make all three match.
A few things worth knowing before you start. Attachments keep the design they arrived with; your styling is not applied to them, which is what makes them right for standard terms or an engagement letter. A Word reference document contributes its styling only, never its words — so never upload one that contains real client information, because the file is stored and reused for every export of that type. Files sent this way are size-capped; anything larger goes through the Designer page, which has no such limit. And because every change here reaches every client's next export, Claude will describe the effect and wait for you to confirm.
Try: "Put our logo in the header of the questionnaire export and match the heading font to our letterhead."
Languages
- List the interface strings for one of your languages, with the shipped translation and any override you have made
- Override the shipped translation of one string
- Clear an override and go back to the shipped wording
These only work if your account has more than one language enabled. Use them for firm-specific terminology, not for wholesale retranslation — the shipped translations are already professionally done.
Product feedback
- List the Eternal Pro roadmap requests your firm can see
- Post a suggestion to the roadmap on your firm's behalf
- Open a support ticket when something is wrong or unclear
Before a suggestion is filed, Claude checks the roadmap for requests that look like yours and reads them back to you. If one of them is already what you were going to ask for, vote on that instead — a second copy of an existing request helps nobody.
Voting stays in the Roadmap widget in your dashboard — that is deliberately your own action, not something Claude does for you. Support tickets are rate limited, and Claude will ask you to check the message carries no client names or details before it sends: support does not need them and must not receive them.
Try: "Check the roadmap for anything about bulk client import, and if there's nothing, suggest it."
Which account you are connected from
If you hold the firm's own Firm Administrator account — normally the principal — everything in this article is yours to run.
If your firm has set up additional administrator accounts for staff, those accounts can do most of it: questions, questionnaires, templates, firm settings, client creation and lookup, and changing a matter's questionnaire. A handful of things stay with the Firm Administrator account — document exports, translations, the staff roster and client assignment, restricting a client site, the progress bar, clearing the cached question set, and the roadmap. Asking from one of those accounts gets you a clear refusal saying so, not a silent failure.
When Claude asks you to confirm
Anything consequential is refused the first time by design. Claude comes back with a plain statement of what will happen — who gets emailed, what cannot be undone, how many clients it reaches — and only writes on a second, explicitly confirmed request. That covers purging a question, deleting or resetting a questionnaire, importing over an existing one, creating a client, changing a matter's questionnaire, restricting a client site, every document export change, roadmap suggestions and support tickets.
This is not Claude being cautious. The refusal comes from Eternal Pro, so it happens whatever you have asked for and however you have asked for it. Read what it says before you answer.
What Claude will never do here
- Show you a client's answers, contacts, assets, documents, passwords, emergency card or vault. No operation returns them. Claude cannot access them.
- Tell you a client's name, even when you have looked that client up.
- Read or write any API key, token or stored credential.
- Delete or reposition the structural questions the intake logic depends on.
- Vote on a roadmap item on your behalf.
- Create clients or send support emails faster than the rate limits allow.
Getting better results
- Name the questionnaire. Most firms have several. "In my Trust Intake" removes the guesswork.
- Ask for a plan before a batch. "Show me what you'd change, then wait" is a good habit for anything touching more than two or three questions.
- Diagnose after a big reorganisation. One sentence, catches the breakages that only show up in front of a client.
- Export before anything drastic. "Export this questionnaire first" gives you a rollback point.
- Describe outcomes, not operations. "Clients keep skipping the digital assets section — what would you change?" gets better results than naming a tool.
- Say why. Claude knows how the intake logic hangs together, and will often tell you a better way to reach the same outcome.
- Start a fresh chat for a new piece of work. A long session can leave Claude working from a stale view of what it can do. If it claims something is unavailable that you know exists, a new conversation usually fixes it.
Every request you make this way is recorded in your Audit Trail — reads and refusals as well as changes — so you can always review what happened and under whose account.
Previous article in this series: Part 2 of 3 - Connecting Claude to Eternal Pro with the MCP Connector
How to import clients from MyCase using a webhook ?
How to enable automatic sync to Lawmatics?
How to sync client intake data to Lawcus?
united states
