skills.rest
tenexity
tenexityOFFICIAL
Explore all skills by this author →
WebsiteGitHub

account-drift-detector

Detect drifting customer accounts from captain's log entries and customer lists.

Updated Apr 25, 2026
Search Tags:#customer retention#sales prioritization#account health#captain's log#account drift#hvac distribution
One-click install
npx skills add https://github.com/tenexity/cowork-distributor-plugins --skill account-drift-detector
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: account-drift-detector
Source: https://github.com/tenexity/cowork-distributor-plugins/tree/main/plugins/tenexity-setup-team-hvac-plumbing/skills/account-drift-detector
Command: npx skills add https://github.com/tenexity/cowork-distributor-plugins --skill account-drift-detector

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill identifies customer accounts that have gone quiet so distributors can catch relationship drift before it turns into lost business.

Core Features & Use Cases

  • Drift detection: Reviews captain's log entries and recent tasks to find accounts that have not been mentioned for 30 or more days.
  • Source cross-checking: Compares the log against the customer list and top-25 tracker when available so the strongest accounts are prioritized first.
  • Distributor-aware timing: Adjusts the urgency of silence based on account type, treating will-call and service-heavy customers more tightly and project or MRO accounts more leniently.
  • Practical output: Produces a ranked report with recent context, last-mention timing, and specific next actions for follow-up.

Quick Start

Ask the skill to review the last 60 days of captain's log entries against your customer tracker and surface any quiet, drifting, or at-risk accounts.

Frequently Asked Questions about account-drift-detector

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I detect customer account drift before revenue loss in wholesale distribution?▼

Customer account drift is detected by parsing captain's log entries and cross-checking them against customer lists and top-25 trackers to flag accounts that have gone quiet for 30 or more days.

What is the best way to spot quiet or at-risk accounts using a captain's log?▼

Spotting quiet accounts requires parsing recent captain's log entries, applying alias matching, and bucketing accounts by inactivity thresholds to generate a ranked report of at-risk customers.

Does account drift detection work for HVAC and plumbing wholesale distributors?▼

Yes, account drift detection is designed for HVAC and plumbing wholesale distributors, adjusting urgency based on account type to treat will-call customers more tightly and project accounts more leniently.

How do I prioritize sales follow-ups for drifting accounts?▼

Prioritize sales follow-ups by comparing the log against the customer list and top-25 tracker, ensuring the strongest accounts are bucketed and surfaced first in the generated ranked report.

What timing thresholds should I use to flag drifting customer accounts?▼

Drifting customer accounts are typically flagged after 30 to 60 days of silence, with distributor-aware timing that applies tighter thresholds for service-heavy customers and lenient ones for MRO accounts.

Related Skills

Explore More Marketing & Sales Skills→
tenexitytenexity

vendor-pulse

Summarize weekly vendor activity from captain's log entries.

Official
Advanced
miriamdongmiriamdong
2

pipeline-gap-check

Cross-reference HubSpot CRM, Gmail, and Google Calendar to identify deals missing next steps.

Community
Advanced
keboolakeboola

cs

Automate customer success workflows in the Keboola CRM platform.

Official
Advanced
GoldenZeroGoldenZero
1

churn-risk-detection

Analyze customer behavioral signals to score churn risk and prescribe retention interventions.

Community
Advanced