Confirm a capital call is ready before the notices go out.

What it does

The agent always runs against one specific capital call — the one you are about to send notices for. Its checklist is fixed: every step runs in the same order, and there is nothing to configure or skip. It is the capital-call counterpart to the Distribution Readiness Agent, which applies the same kind of gate to a distribution before payments are released.

Each step gates the next.

1. Gets started. Sets up trackers to collect findings on KYC, documents and notifications.
2. Checks investor KYC. For every investor on the call, confirms their KYC record exists and has been verified. If any investor is missing KYC or is not verified yet, the checklist stops here — none of the later checks run.
3. Checks that call documents have been generated. First confirms the fund has at least one Call Notice template uploaded; if not, the checklist stops immediately with a fund-level blocker. Otherwise, for each investor — except those whose commitment is explicitly set to skip document generation — it confirms the call notice documents have actually been generated. Missing documents stop the checklist here.
4. Checks that call documents have been approved. For each investor still in scope, confirms all of their generated call notice documents have been approved. Unapproved documents stop the checklist here.
5. Checks notification setup. Confirms an active email notification is configured for this capital call. A missing or disabled notification stops the checklist here.
6. Confirms ready to send. A final confirmation step that only runs if every prior check passed. It changes no data — it confirms the call has cleared every gate.
7. Saves the report. Records whether the call passed every check or was stopped partway through.

No AI or LLM calls. Every check here is a straightforward yes/no comparison against your existing records.

What it needs

Configuration fields

None. This agent has no settings form at all — there is nothing to toggle, reorder or adjust, and the checklist above is fixed for every entity. Setting the agent up simply makes it available; it does not add any configurable options.

What feeds the run

• A single capital call, specified each time you trigger a check.
• The investors on the call, pulled along with their KYC status and documents as each step needs them.
• Templates. The fund needs at least one Call Notice template document uploaded for the documents-generated check to pass.
• Notification setup. An active, enabled email notification configured on the capital call.
• No AI provider key is required.

Setup warnings

Although the checklist itself has no settings, the agent still depends on fund-level setup. The agent's General tab, under AI → Support Agents, shows a yellow warning banner listing every fund that has no Call Notice template uploaded; upload one under Fund → Documents before preparing a call for that fund. This matters most for batch or scheduled runs, which do not walk through the step-by-step checks the way a run from the capital call's own page does, so a missing template would otherwise only surface at the moment you try to send.

Turning it on

• Where it is switched on. A Company Admin ticks the “Call Notice” box under Admin → Edit Entity → Support Agents, and saves.
• AI key needed? No.
• Who can manage it. Only Company Admin users can set up or run support agents. The readiness panel itself is visible to anyone with access to the capital call's page.

If the agent is not enabled for your entity, the checklist is simply not available. Check with your administrator if the panel does not appear or “Run Now” stays disabled.

Running it

Unlike the E-Sign Monitor or Data Quality agents, this one has no entity-wide “Run Now” button on its own page. It is tied to a specific capital call and runs as part of preparing that call to be sent.

1. Open the capital call record you intend to send.
2. The capital call's details page shows the readiness panel at the top, displaying the most recent check for that call, if one has been run.
3. Trigger a fresh check from that panel. It starts a new readiness check and shows live progress as each step completes.
4. The panel shows six step indicators — KYC, Docs Generated, Docs Approved, Notification, Ready to Send, Save Report — updating in real time, along with a progress bar.

This agent only ever checks one capital call at a time. There is no way to run it against every call in a fund at once.

Where the output goes

• The capital call details page — the readiness panel itself, showing the latest check inline.
• The agent's General tab — a “View Report” link under AI → Support Agents → Call Notice, showing whichever capital call was checked most recently across the whole entity.
• The Execution History tab — every past check across every capital call, with status and duration.

There is no email for this agent. It is purely a readiness gate shown in the app, and it sends nothing to investors or to your team on its own.

Reading the result

Each failed check records the specific investors or records affected, with a plain-language reason for each one. The details are organised by category — KYC issues, document issues or notification issues — so you can see exactly what needs fixing.

• Ready — every check passed; the capital call is cleared to send notices.
• Blocked — at least one check failed. The report notes exactly which step the checklist stopped at, so you can go straight to the blocker without reading the whole panel.

Where it can fail

• An investor has no KYC record at all. The KYC check fails with “No KYC record linked to this commitment” and the checklist stops there; document and notification checks never run, even if they would have passed. Create or link the missing KYC record from Investor KYCs, filtered by fund, then re-run.
• The KYC exists but is not verified. The check fails naming the investor and noting “KYC not verified”, with the same stop-here behaviour. Mark the KYC as verified from the Investor KYCs screen, then re-run.
• The fund has no Call Notice template uploaded. The documents-generated check fails immediately at fund level: “No call templates found for Fund”, directing you to Fund → Documents to upload a Call Template. This blocks every capital call in that fund, not only the one you are checking — and uploading one template unblocks the step for all of them.
• A commitment is set to skip document generation. That investor is quietly left out of both the documents-generated and documents-approved checks. They neither pass nor fail; they are simply not evaluated. If an investor you expected to see flagged is missing from the failed list, check whether that flag is turned on for their commitment.
• Call notice documents have not been generated yet. The check fails, listing each affected investor with “No call notice documents generated” and pointing you at “Generate Docs” on the capital call page. The checklist stops there, so approvals and notification checks never run.
• Documents are generated but not approved. The documents-approved check fails, listing each affected investor with a count of pending documents. The checklist stops there and the notification check never runs.
• No notification template is configured. The notification check fails: “No email notification template configured.” Go to the Notification tab on the capital call and create or enable the notification used for sending call remittance notices.
• A capital call with no investors linked yet. The KYC, documents-generated and documents-approved checks all pass automatically, because there is nothing to evaluate; only the notification check can still block.
• Re-running after fixing one blocker. Each re-run reuses and overwrites the same report rather than keeping every historical attempt, though Execution History still logs each run. The panel will progress further and may reveal a brand-new blocker you could not have seen before, so read the whole panel each time.
• A mid-check error — for example a missing or broken link between the call and its fund — is not handled as a normal checklist failure. It can appear as “Failed” rather than “Blocked” in Execution History, which signals a data integrity problem worth investigating directly rather than an unmet checklist item.

Questions we get asked