---
title: "Agent citations: See the accounts behind every number"
description: "Trace any number in an agent report back to the accounts, filters, and definition behind it. Plus a workflow engine and five new connectors."
canonical: "https://vasco.app/blog/agent-citations"
date: "2026-09-16T00:00:00.000Z"
authors:
  - Guillaume Jacquet
jobTitle: "CEO & co-founder"
readingTimeMinutes: 1
contentType: product-spotlight
intent: foundations
pillar: "RevOps systems & architecture"
audiences:
  - enterprise
---

# Agent citations: See the accounts behind every number

_AI agent reports: Verify every number at its source_

Connecting an AI agent to a CRM is a weekend project now, and getting an answer can take minutes. The problem is checking whether that answer is actually right, which can still take an analyst most of an afternoon.

That’s the gap we focused on this cycle. Citations let you trace any number back to the accounts, filters, and definitions behind it. The workflow engine keeps the underlying pipeline data up to date, while five new connectors bring advertising, product analytics, billing, and Microsoft Teams into the context graph.

[https://youtu.be/AazmiiM8m1Q](https://youtu.be/AazmiiM8m1Q)

### Citations

**What a citation card shows you**

Every metric in a Vasco report carries a citation card. It names the metric and its definition, the timeframe, the filters applied, and the accounts contributing to the total. Hover to preview it, click to pin it.

That last item is usually where the answer is. A CRO looking at a pipeline number that seems too high can see exactly which accounts sit inside it. If something is in there that should not be, it is visible without leaving the report.

From the same card you can open an account inspect panel to look at any single account behind the number, or jump into the context graph with that node already selected.

**Citations on calls and emails**

Text and transcript citations work on claims rather than figures. When a report says something about a deal or an account that came out of a call or an email, the citation surfaces the quoted passage inside its source summary.

A sales leader reading a note about why a deal slipped can read the sentence in the call where it was actually said instead of taking the summary's word for it.

### The workflow engine

An agent reasoning over stale data will give you a confident answer built on last week's pipeline. Keeping that data current is a pipeline problem, and until this cycle Vasco tracked it with a job-status service that could watch a job but could not sequence one, retry a failed step, or tell an agent when something had finished.

**What the engine runs**

A deployed orchestration engine now handles that work across four workflow families: refresh, apply, first sync, and extract insights from activities. Each org gets its own workflow graph with retries and timeouts, so a failed job gets another attempt rather than disappearing into a status page.

Every run is recorded, and the Runs view shows what is executing with drill-in to the graph and live updates as steps complete. If a forecast looks off, an operator can check whether the refresh actually completed before the agent ran.

**What agents can do with it**

Agents reach the same engine through 27 MCP tools. An agent can ask what workflows are available to it, check what is currently running, and launch one, which is what lets an agent kick off a sync and wait for it rather than needing someone to trigger the job by hand.

### Five new connectors

- **Google Ads and Google Analytics.** Paid and site performance data flows into the context graph. A marketing leader can look at campaign performance next to the pipeline it produced rather than evaluating channels in isolation.
- **PostHog.** Product analytics sitting in the graph alongside CRM activity. Useful for a RevOps team working out which accounts are trending toward expansion or churn based on how the product is actually being used.
- **QuickBooks.** Billing data pulled through the API, API-only at this stage. A revenue leader can connect what a customer is actually paying against what the pipeline and activity data say about that account.
- **Microsoft Teams, two-way.** Reports can be delivered to Teams channels, and Teams conversations are ingested as activities, so the discussion around an account becomes part of what an agent reads. Teams joins Slack and email as a delivery destination, which matters for any team whose executives do not open Slack.