Skip to main content

Run a report

Running a report answers a specific business question—pipeline velocity, rep call counts, campaign performance—with filters you can save, export, and schedule.

Video

Video coming soon for this topic

Who can do this​

Reporting permission.

Before you begin​

  • Question defined (metric + timeframe + team scope)
  • Spot-check data in CRM for sanity

What you'll accomplish​

  • Report exported or added to Favorites

Step-by-step procedure​

Run flow​

  1. Reports Center → pick category (e.g. Sales /reporting/sales).
  2. Select report tile.
  3. Set date range (preset or custom).
  4. Apply filters: owner, team, source, pipeline, etc. (vary by report).
  5. Select Run / apply filters per UI.
  6. Review table/chart; drill links (e.g. to Call Logs) when available.
  7. Export CSV/PDF if offered.
  8. Add to Favorites for reuse.

Interpret responsibly​

  • Compare periods of equal length.
  • Note attribution settings on call reports (fact vs lead).
  • Cross-check messaging totals with Email Campaigns analytics.

Extended guidance​

Save filter sets mentally as recipes: date range + owner + source. Before board meetings, rerun favorites—do not screenshot stale exports. When sharing CSVs externally, strip personal columns per privacy policy.

Practice scenarios​

Run Lead Sources for last 30 days, export CSV, spot-check top source against CRM contact filters. Schedule the same report weekly and confirm filter chips persist. Drill from a call metric into /reporting/contacts/call-logs and back using the browser back control.

Sandbox validation​

Repeat the procedure in a test workspace or with two internal colleagues before customer-facing launches. Document who approved each step (marketing, legal, ops). Screenshot Verify your work outcomes for audit trails. When something fails, capture the URL, role, timestamp, and exact UI label clicked—Support resolves tickets faster with that context. Re-read See also links after your first successful run; adjacent topics often cover edge cases you have not hit yet.

Team rollout checklist​

Assign a single owner for this workflow per workspace. Schedule a 30-minute handoff training with screen share. Add the See also links to your internal Notion or wiki. Re-verify after each major product release (labels move occasionally). Pair junior staff with a senior reviewer for the first live execution. Log lessons learned in your team retro—especially permission surprises and integration timeouts.

Keep learning​

Bookmark this page and the Product module map. After major releases, re-walk Step-by-step procedure—UI labels move occasionally. Share feedback with your workspace Admin so Help stays aligned with how your team actually works.

Verify your work​

  • Numbers match manual spot checks
  • Export opens in spreadsheet tool
  • Favorite reloads same filters

Tips​

tip

Name personal saves clearly in My Reports so teammates do not confuse them with Shared Reports.

Troubleshooting​

| Zero rows | Filters too narrow; widen dates | | Drill link 403 | Missing permission on underlying module | | Export missing | Report type may be view-only |

See also​