See which accounts went quiet this week
One weekly digest naming the accounts that have gone quiet, with what each signal was. Built for a customer success manager who finds out about churn after it happens.
PostHog
Freshdesk
HubSpot
Slack
5 steps4 integrationsRuns weekly
Quiet accounts look exactly like healthy ones. What it costs while the work is still done by hand.
- 01Quiet accounts look identical to healthy ones in a list.
- 02Usage data and conversations live in different tools.
- 03The warning signs were there, in three places, unread.
- Pull usage64 accounts · 7d events
- Pull tickets19 open · 5 accounts silent
- Read CRMlast contact · 6 over 30d
- Build digest5 accounts · no recent signal
- Post to Slackpost_message · #success
One workflow, five steps. ModuleX drafts this graph from a single sentence, and every step stays editable.
- 01Pull recent product usage per account.PostHog
- 02Pull recent support activity.Freshdesk
- 03Pull the last contact from the CRM.HubSpot
- 04Assemble a digest highlighting accounts with no recent signal.ModuleX
- 05Post it to the team channel.Slack
The workflow is an editable graph. Reading runs freely; post it to the team channel waits for your opt-in approval until you loosen it. The graph is the receipt.
The quiet accounts, named. Paste this into ModuleX chat, or hit Use this workflow.
see which accounts went quiet this week: pull recent product usage per account; pull recent support activity; pull the last contact from the CRM; assemble a digest highlighting accounts with no recent signal. Ask me before anything is sent or written.
to: composerOr skip the workflow entirely. Ask the assistant in chat and it runs the same job agentically: it picks the right actions, chains them, and reports back. The composer is for when you want it repeatable.
See which accounts went quiet this week. One weekly digest naming the accounts that have gone quiet, with what each signal was.
- posthog · get_insights
- freshdesk · get_ticket
- hubspot · get_company_activity
One weekly digest naming the accounts that have gone quiet, with what each signal was.
Where this fits. The tools it runs on, and the teams that run it.
Keep the momentum. Nearby workflows that reuse the accounts you just connected.
Answer an order question with the order in handA reply that answers with the real order status instead of asking the customer for their order number. Built for an ecommerce team answering the same three questions about where a package is.- Answer support questions using your own documentationA drafted answer grounded in your own material, showing what it drew from, behind an approval step. Built for support teams whose answers already exist, just not where the question arrives.
Turn a customer email into a tracked issueA tracked issue an engineer can pick up without opening the email, and a customer who knows it was logged. Built for support and product teams where bug reports die in an inbox.
About this use case.
No. It reports the signals from your own tools; the judgement stays yours.