Add, configure, resize, and remove individual report cards on your TrustPager dashboards — covering all card types, data sources, filters, rolling date windows like {{today-28}}, and visualisation options.
Report cards are the individual panels that make up a dashboard. Each card shows a specific metric — a bar chart of opportunities by lead source, a stat showing total pipeline value, a line chart of activity over time. This article covers how to add, configure, and manage cards. If you need to create a new dashboard first, start at https://app.trustpager.com/operations/reporting.
Open any dashboard at https://app.trustpager.com/operations/reporting and use the Add Card button. Give the card a title, choose a visualisation type, pick your data source, and configure the query. Save to add it to the dashboard.
Each card you add lands at position 0 by default. You can reorder cards by dragging them into place on the dashboard.
Choose the right chart type for what you want to show:
These data sources are available when building cards:
| Source | What you can measure | Requirements |
|---|---|---|
| Opportunities | Revenue, win/loss rates, lead sources, pipeline stages, staff performance | None, available in every workspace |
| Activities | Logged follow-up volume and cadence: calls, emails, meetings, notes, SMS, broken down by team member, contact, or opportunity | None, available in every workspace |
| Tasks | Open vs completed tasks, by assignee, priority, category, due date; overdue tracking | None, available in every workspace |
| Invoices / Receivables | Outstanding balances, aged receivables, amount due/paid, invoice totals by customer or date | Your accounting integration connected at https://app.trustpager.com/auto/integrations plus a one-time receivables sync |
| Work Orders | Dispatched jobs: who each one was assigned to, which subcontractor it went to, its status and scheduled date. Your own work order fields appear as extra columns, and numeric ones can be summed and averaged | None, available in every workspace |
| Referrals | Referrals per partner, what converted, and commission. Payment on the referred job comes through as a payment status, so you can report on referrals that have actually been paid | None, available in every workspace |
| Card Movements | Every time an opportunity moved between stages: out of which stage, into which, on which pipeline, by whom, and when. Covers manual drags on the board, API moves and automation moves alike. Filter Automated Move to false for a people-only view, which is what a per-staff scorecard wants | None, available in every workspace |
| Bookings | Bookings by type, status (confirmed, attended, no show, cancelled, late, waitlist), host, and who booked. Duration is summable, so booked minutes per host is one card. Filter the start date from today onwards for an upcoming-bookings digest | Your role needs permission to view scheduling |
| Emails | Emails the workspace sent and what happened to them. Delivery State buckets the outcome into sent, delivered, opened and failed, and Undelivered is the single flag to filter on for a bounce watch, grouped by recipient | Your role needs permission to view email |
| Voice Agents | One row per voice agent, with how long each has gone without a call. Days Without an Inbound Call counts from the last phone call the agent answered, or from when it was set up if it never has, and Usual Days Between Inbound Calls shows its normal pace over the last 90 days. Also call counts for the last 7, 30 and 90 days, with website calls counted separately. Filter Days Without an Inbound Call at 3 or more and send the dashboard on an Auto Schedule, and you get an email only when a line goes quiet | Your role needs permission to view voice agents |
Within the Opportunities source, available measures include:
Dimensions let you break those measures down by pipeline, stage, assigned team member, lead source, status, won/lost reasons, and more.
Custom fields as dimensions: any custom field you have defined on your opportunities (for example Brand, Equipment Type, or Manufacturer) is automatically available as a dimension. Choose it from the "split by" list to group a chart by that field, for example pipeline value split by Brand. New custom fields appear on their own, with no extra setup.
A table card can either summarise (one row per group, like revenue per team member) or list individual records (one row per opportunity, task, or invoice). For the record list, choose the columns you want and the order they appear in, and the table shows exactly those.
Any custom field works as a table column, so a job list can show your own fields side by side with the standard ones. For example a Job Profitability table might show Opportunity, Stage, Property Address, Quote Amount, Subcontractor Cost, and Profit, where the last four are custom fields on the opportunity. Column headers use your own field labels.
You can also include the opportunity value, invoice amount due, or invoice total as a column, alongside dates, stages, owners, and custom fields.
Emailed digests show up to 8 columns per table, so keep a table you plan to email to the columns that matter most. On the dashboard the table scrolls sideways if it is wider than the card.
You can filter a card's data at the card level — for example, to show only Won opportunities, or only a specific pipeline. Set these in the card's query configuration when adding or editing the card.
The dashboard also has a date range filter in the toolbar that applies across all cards at once. Card-level filters refine within that range.
A card that asks a question about time needs the time to move with the calendar. If you type a date into a filter, the card is right on the day you build it and quietly wrong from then on, and nothing tells you: it keeps rendering a number every week, measuring the wrong thing.
Use a rolling window instead. In a date filter's value, write:
{{today}} — today{{today-28}} — 28 days ago{{today+7}} — a week from today{{today-3mo}} — three months ago{{now-24h}} — 24 hours ago, to the hourLeave the unit off and today counts in days while now counts in hours. Spell it out with any of min, h, d, w, mo, q or y (minutes, hours, days, weeks, months, quarters, years).
Months and quarters use the calendar rather than a fixed number of days, so one month before 31 March is 28 February, not the 90-days-ago answer you would get from counting.
Some examples worth stealing:
{{today-28}} and group by stage. That is "open cards nobody has touched in four weeks, and where they are piling up".{{today-7}}.{{today}} and {{today+30}}.These are what make a card safe to put on a recurring digest. Pair one with an Auto Schedule and the same question gets asked afresh every time it sends.
If you mistype the unit, the card tells you and names the ones it accepts, rather than silently returning nothing.
Cards come in three sizes:
Set the size when adding the card, or update it later via the card's edit menu.
Open the card's context menu on the dashboard and choose Edit. You can update the title, visualisation type, data query, filters, and size. Changes take effect immediately.
Drag cards to rearrange them on the dashboard. The new order saves automatically.
Open the card's context menu and choose Remove. The card is deleted from the dashboard permanently. The underlying data is unaffected — you can always add a new card with the same query.
When creating a new dashboard, you can choose a template (e.g. Sales Overview, Pipeline Health, Lead Sources). Templates pre-populate a set of cards with sensible defaults — you can then edit, remove, or add to them. This is the fastest way to get a useful dashboard without building each card from scratch.
A dashboard is the container — it holds a name, visibility setting, and a collection of cards. Cards are the individual metrics inside it. You manage dashboards at https://app.trustpager.com/operations/reporting; you manage cards from inside a specific dashboard at https://app.trustpager.com/operations/reporting (click in to open it).
If you're building automations or agent workflows, cards can be managed programmatically using the add_report_card, update_report_card, and remove_report_card MCP tools, or directly via the REST API. This is useful for agents that build dashboards on behalf of clients or generate reporting views from pipeline events.
Talk to Evie right now, or book a real human for a deeper walkthrough. Whichever feels right.
Hear her in 10 seconds.

30 minutes with a real human · video call · Free.