This guide covers the client-facing side of RUSHA: the moments where AI-generated content reaches your client directly, and how to use it to make every report feel like it required real analyst work — because it did.
Where RUSHA Shows Up for Clients
1. Executive Summaries on PDF & Web Reports
When you generate a report, RUSHA can write a concise (under 1,000 characters) executive summary that's aware of the report's exact date range — not a generic template, an actual summary of that period's numbers.
How to use it well:
- Generate the report close to when you're sending it, so the summary reflects the freshest data.
- Read it once before sending — it's verified against the underlying data, but you're still the one putting your agency's name on it.
- If something changed (you fixed a campaign, added a platform), regenerate the summary rather than reusing an old one — it costs another insight credit but keeps the report honest.
2. Approved Insights in the Live "Vault" Display
When a client opens their live, tokenized web report, RUSHA's most recent approved correlation insight is shown at the top as ongoing "proof of value" — a standing reminder that something is actively watching their account, not just producing a monthly number dump.
Two things worth knowing:
- Only approved insights ever reach this display — see RUSHA AI for Internal Audits & Proactive Monitoring for how approval works.
- Reports capture an immutable snapshot at generation time. Approving an insight after a report has already gone out won't retroactively add it — generate a new report to pick up anything newly approved.
3. The Client View of Any Insight
Anywhere a client sees AI output — an approved anomaly, a correlation, an executive summary — it's gone through the dual-voice rewrite: a blunt internal diagnosis is turned into diplomatic, forward-looking language before the client ever sees it, while a programmatic check guarantees every number in the client version matches the internal version exactly. Tone changes; data never does.
Using This to Reduce Churn
The whole point of RUSHA's client-facing surface is proof, delivered automatically, that someone (something) is paying attention between calls:
- A client who sees a correlation insight on their live dashboard between monthly calls is seeing evidence of ongoing analysis, not just a report that arrives once a month.
- An executive summary that correctly references this specific period's numbers reads as bespoke analysis, not a boilerplate paragraph.
- Because every client-facing number is verified against the connected platform data before it's shown, you're never in the position of a client catching a wrong number in a report you sent them.
What This Costs
Each of these draws from the same monthly insight allowance:
- Generating or regenerating an executive summary — 1 insight.
- Approving a draft anomaly or correlation into the Vault display — 1 insight (approving is the only cost; the background scan that found it was free).
See Pricing, Quotas, & Billing for the full quota breakdown, deduction order, and how to buy a top-up if you're close to your limit before renewal.
Related Guides
- RUSHA AI for Client Calls & QBRs — the live, on-demand side of RUSHA.
- RUSHA AI for Internal Audits & Proactive Monitoring — how an insight gets found and approved in the first place.
- Mastering the RUSHA AI Insights Engine — the technical deep dive on the dual-voice system and zero-hallucination guardrails.
