Back to support
Reporting

Setting up owner reports and team alerts

How to make reports actually useful by sending them where people already work.

Why reports fail

Reports usually fail because they exist but nobody sees them at the right time. A weekly digest in the wrong inbox is almost the same as no digest at all.

Customerscor works best when reporting is connected to your real operating rhythm, whether that is owner email, a team Slack channel, or both.

Best setup pattern

Send owner summaries to an email inbox that actually gets checked for business decisions. If you use Slack with a team, send operational alerts to a channel where overdue items and follow-ups can be seen quickly.

Keep the destinations focused. One channel for reporting is usually better than spraying messages across multiple places.

What to watch for

Test the report routes before relying on them for beta users. Make sure the sender, webhook, and workspace filters all point to the right place.

Once reporting is working, use CSV exports when you need deeper auditing or manual sharing outside the app.

Need the next step?

Keep moving through the help center or jump back into the product and apply the workflow directly.

Keep reading

Related support articles

View all guides
Branding

Uploading your business logo for branded emails

Add your company logo once and reuse it across outbound email so receipts, reports, and saved templates feel more polished.

Support

Using the support inbox and owner notifications

Keep workspace support conversations organized while sending owner alerts when a new message or signup needs attention.

Getting started

Standalone workspace quick start

Launch without connected billing. Set your business name, import clients, and start managing follow-ups fast.