Fundraising status across every open deal.

What it does

Unlike the Deal Management Agent, this one runs against your whole organisation rather than a single deal, and works through these steps:

1. Gets started — loads its settings: who should receive the report, the staleness threshold, an optional list limiting it to specific deals, and five on/off switches controlling which sections appear in the email — greeting, activity updates, tasks due, tasks overdue and stale items, all on by default.
2. Loads the deals — pulls in every open deal for your organisation, narrowed to a specific list of deals if one has been set.
3. Calculates summaries — for each deal it works out target against committed, pending and declined amounts, the fill rate, an overall health classification, how many days since the last investor activity, how investors are distributed across pipeline steps, and the top ten investors by committed amount.
4. Generates reports — saves each deal's summary as a report attached to that deal, and creates an HTML document called "Deal Fundraising Report" in a private Reports folder inside that deal's documents, replacing any earlier version rather than piling up duplicates.
5. Sends the email — one consolidated summary to the configured recipients, if any are set.
6. Wraps up — finalises the run's status.

This agent is not AI-powered. It is number-crunching over your deal, investor and activity data, and no AI provider key is needed for it to work.

What it needs

This agent has no field-by-field settings page of its own. In practice you configure it from a dedicated panel on the deal page — open a deal, then the Agent Settings tab.

Field	Default	What it controls
Email addresses	blank	Who receives the summary email, comma-separated.
No-activity threshold (days)	14 from this panel	How many days without investor activity before a deal is flagged as stale.
Greeting & Fill Rate Summary	on	Includes the greeting and fill-rate paragraph in the email.
Activity Updates	on	Includes the updates-to-existing-items section.
Tasks Due	on	Includes upcoming due-date tasks.
Tasks Overdue	on	Includes overdue tasks.
No-Activity Items	on	Includes the staleness section.
Schedule	weekly, 10:00, UTC, enabled	Frequency, day, time, time zone and enabled state — the agent's recurring schedule is created from this same panel.

The settings stored behind that panel are:

• The deal scope — comma-separated deal identifiers, or blank for all open deals.
• The recipient list — comma-separated email addresses.
• The staleness threshold — a day count, falling back to 30 if it was never set at all.
• The five section toggles, each defaulting to on.

What else it reads

• Each open deal's investors, whether active, pending or declined, and each investor's committed amount.
• The deal's target amount.
• The pipeline template steps, used to build the step distribution.
• The most recent activity update tied to any investor, used to determine staleness.

Setup checklist

The agent's General tab shows a yellow warning banner when setup would silence or distort the report:

• No email recipients configured — the summary email, this agent's main output, will never be sent. The run still completes and looks successful in the history.
• A staleness threshold present but blank — a blank value is treated as zero days, which flags every deal as stale. Enter a day count or remove the value.
• A section toggle stored with an unexpected value — the five section checkboxes are strict about how their state is stored, and one holding anything other than a plain on or off value silently drops that section from the email. This can happen when settings are edited outside the deal-page panel. The banner names the affected section, and re-saving the panel fixes it.

Turning it on

1. An administrator turns on the Deals Report Agent for your organisation, from the Support Agents section of the entity's admin settings.
2. No AI provider key is required — this agent never calls the AI.
3. The deal page's Agent Settings tab is available to any user with permission to edit that deal, and is not gated by the organisation-wide toggle. That toggle still controls whether the agent shows as enabled in the Support Agents list and whether its own Run Now button there is active.

Running it

From the deal page — the supported path today:

1. Open any deal and go to the Agent Settings tab.
2. Set the recipients, the staleness threshold, the content toggles and the schedule.
3. Click Run Now to open the confirmation prompt, or leave the schedule to handle it.

Because the agent always runs at the organisation level and works through deals internally, triggering it from any single deal's page still produces a report covering whichever deals are currently in scope — which may already have been narrowed to one deal the last time someone saved that panel.

From the Support Agents list, open the Deals Report Agent card and click Run Now on the General tab.

The agent always runs in the background without a live, step-by-step progress panel, because it is working through several deals internally rather than one target with visible steps. You see a queued notice rather than a step tracker.

Scheduling

This agent does not come with a pre-built schedule. The only place a schedule is created is the deal page's Agent Settings tab: saving that form is what creates or updates the schedule, defaulting to weekly at 10:00 UTC, and saving the form is also what turns it on. If nobody has ever opened that tab and saved it, the agent has no schedule at all and runs only when someone clicks Run Now.

Where the output goes

• Per-deal report — one report per deal, replaced each run rather than kept as history, so only the latest result per deal is available.
• HTML document — a "Deal Fundraising Report" saved into a private Reports folder under each deal's documents, replacing any earlier copy.
• Deal Reports tab — on the agent's own page. The tab name is shared with the Deal Management Agent's deal-level reports; they are told apart by which agent produced them.
• Email — sent to the configured recipients, if any. The subject line includes "- Action Required" if any deal needs attention. With no recipients configured no email goes out, though the run still completes and the reports still save.

Reading the result

Field	Meaning
Deal status	"Closed"; "Complete" at a fill rate of 100% or above; "On track" at 60% or above; "Needs attention" below 60%.
Target, committed, pending, declined and remaining amounts	Fundraising amounts in dollars.
Fill rate	Committed amount divided by target amount, as a percentage rounded to one decimal place. Shows 0.0% if there is no target set.
Investor counts	Total, active, pending and declined, broken out by status.
Stale, no-activity days, last activity date	Whether the deal has exceeded the no-activity threshold, the actual day count, and the timestamp of the most recent linked activity. The day count is blank if there has never been any activity.
Step distribution	How many investors sit at each pipeline step, in order. Empty if the deal has no pipeline template steps defined.
Top investors	Up to ten active investors sorted by committed amount, each with name, status, tier, amount and current pipeline step.

Where it can fail

• Listed deals that no longer exist or are no longer open are dropped silently. A deal that has been deleted, belongs to a different fund, or is no longer open simply disappears from the results without a warning. If that leaves nothing to report on, the agent records "no open deals found" rather than a failure and the run proceeds — leaving you with zero deal reports and a near-empty email.
• The deal-page panel narrows the report scope to one deal every time it is saved. This is the most likely real-world surprise: someone opens the Agent Settings tab on one deal to tweak the recipient list, saves it, and without realising scopes the whole fund-wide report down to that deal. Anyone relying on all-deals coverage should avoid saving that panel unless they intend to narrow the scope, or have it reset afterwards by an administrator.
• There is no interface for choosing a specific handful of deals. The agent supports a custom multi-deal list, but the only panel that touches the setting is the single-deal Agent Settings tab, which always writes exactly one deal. A genuine custom subset has to be set directly on the underlying record by someone with admin or engineering access.
• No schedule comes pre-built. Do not assume a disabled schedule is waiting to be switched on. Check the deal page's Agent Settings tab — if it has never been saved, there is no schedule at all yet.
• Leaving the recipient list blank silences the email. Reports are still generated and saved per deal, but nobody is notified.
• Document-save failures are handled per deal. If saving the HTML report into a deal's Reports folder errors, it is caught and logged and the run moves on to the next deal. That deal's report still saves even if its HTML document does not.
• Staleness is based purely on activity-step updates — not notes, not document uploads, not other interactions. A deal where documents are actively being uploaded but no activity steps have changed can still be flagged as stale.

Questions we are asked