Product Usage Report

Turn a customer's raw product analytics into a usage report worth sharing. Joy reads their activity data and lays out which modules they lean on, how many seats are live, and where the growth opportunity sits.

Pour Customer Success Managers Account Managers CS Operations CS Leaders
Exemple de prompt pour l'assistant Joy

Build a usage report for [account] I can share with them. Show how their team used the product over [the last month], which modules get the most activity, and where adoption is lagging.

À quoi cela peut ressembler

Un exemple illustratif. Votre résultat dépendra de vos sources, de vos données et de vos demandes.

Build a usage report for Meridian Retail I can share with them. Show how their team used the product over the last month, which modules get the most activity, and where adoption is lagging.

I read Meridian Retail's product activity for the last month: 12,400 sessions across their four licensed modules. Here's the breakdown, the seat trend, and the one opening worth raising on your next call.

Here's how Meridian Retail's team used the product last month: 12,400 sessions across the four modules they're licensed for. Analytics is doing the heavy lifting; Integrations is barely touched, which is the clearest opening for a conversation.

12,400Monthly sessions
Analytics5,580
Workflows3,472
Reporting2,108
Integrations1,240

Adoption is healthy but uneven. Analytics drew 5,580 sessions (45% of all activity) and Workflows another 3,472 (28%), so more than seven in ten sessions run through those two modules.

  • Seat activity. 84 of the 120 licensed seats were active last month (70%), up from 61% the month before, so the base is still growing.
  • Under-used modules. Reporting saw 2,108 sessions (17%) and Integrations just 1,240 (10%). For a retail team, leaving Integrations idle usually means data is still moving by hand.

When you share this with them, the story is momentum plus one clear next step: seat adoption climbed from 61% to 70% and Analytics is fully embedded, so the highest-value move is a short working session on Integrations to connect their POS data. That's where the remaining 30% of unused seats are most likely to activate. Copy the summary into your QBR deck or the account email and the numbers carry the point.

Want me to tighten this into a one-slide summary for your QBR, or add last quarter so they can see the trend?

From event logs to a customer-ready summary

Product Usage Report asks Joy to read a single account's product activity and turn it into a clear, shareable summary: which modules see the most use, how many licensed seats are active, and where adoption is lagging. You get the numbers and the story in one written analysis you can take straight into a customer conversation.

  1. Connect the analytics

    Make sure your product usage data is connected to the workspace, or that the account's activity export lives in the Knowledge Center. Joy reads it when you ask.

  2. Name the account and window

    Tell Joy which customer to report on and the period to cover, plus anything specific you want highlighted: seats, a particular module, or adoption trend.

  3. Review the report

    Joy breaks activity down by module, shows seat adoption and its trend, and calls out where usage is lagging and where the opportunity sits.

  4. Share it where you work

    Ask for a tightened summary, then copy it into your QBR deck or the account email. Refine with follow-ups like “add last quarter for comparison.”

  5. Make it one click for your team

    Save this ask as a custom command on the assistant your team already uses, so anyone can run it in one step.

Faites-en la vôtre

Module Breakdown

See exactly which parts of the product the account leans on, as a share of all activity.

Seat Adoption

How many licensed seats are actually active, and whether that number is climbing.

Growth Openings

Joy flags the under-used modules where expansion or deeper adoption is most likely.

Ready to Share

A clean written summary you can paste into a QBR deck or a customer email.

Quarter in Review

Cover a full quarter and compare it against the previous one to show the trend.

Adoption Risk First

Lead with the modules and seats going unused to frame a re-engagement plan.

Portfolio Roll-Up

Summarize usage across all your accounts to spot who's thriving and who's slipping.

Feature Launch Check

Focus on adoption of a newly released feature across the account's team.

Frequently Asked Questions

How do I create a product usage report for a customer?

Name the account and the period, and Joy reads that customer's product analytics to build a shareable summary: module activity, seat adoption, and where usage is lagging. You review it and copy it into your QBR deck or an account email.

What goes into the usage report?

A breakdown of activity by module, how many licensed seats are active and whether that's trending up, and the under-used areas where there's room to grow. Joy also calls out the single clearest next step to raise with the customer.

Is the report live or a snapshot?

It's a written snapshot built from the account's data at the moment you ask. It doesn't auto-refresh or update itself. When you want a current read, you ask again and Joy rebuilds it from the latest data.

Can I compare periods or accounts?

Yes. Ask Joy to add the previous quarter for a trend, or to roll usage up across your whole book of business to see which accounts are thriving and which are slipping.

Does Joy send the report to the customer?

No. Joy drafts the report and a tightened summary in chat; you copy it into your deck or email and send it yourself. Joy doesn't message customers on your behalf.

Ready to turn usage data into a better customer conversation?

Rejoignez la liste d'attente et soyez parmi les premiers à essayer ce workflow lors du lancement de JoySuite.