cus_pelican_health
$84000 ARR · renews 2026-07-24 · 63d to renewal
| Factor | Weight | Current | Contribution |
|---|---|---|---|
| payment_history | 0.40 | 0.32 | 0.128 |
| usage_trend | 0.30 | 0.48 | 0.144 |
| champion_status | 0.20 | 0.62 | 0.124 |
| support_sentiment | 0.10 | 0.58 | 0.058 |
| TOTAL | 0.454 (MED) |
Account health · daily diary from the merged monitor
Diary starts with the next scan
The account-health watcher writes its first entry at the next 06:00 scan. Entries appear here as they're written — verbatim, never summarized.
Timeline · unified account history
No activity yet. As the daily scan, health checks, save plays and renewals accrue, they merge here into one history — newest first.
Save play · Tier-2/3 supervised retention recommendation
expected lift: mediumA broken integration plus a silent billing contact — two compounding contact gaps. Re-establish a live conversation before the signals stack further.
Anchors · cited evidence source_ids
Evidence · cited signals the worker reasoned over
Evidence from salesforce inbound email stripe-
conversation:email_pelican_2 2026-05-16
Two outreach emails to the billing contact went unanswered over 14 days — no opens on the second.
-
salesforce:sf_pelican_sync 2026-05-18
Salesforce sync has been disconnected since 2026-05-04; no CRM activity has flowed for 18 days.
-
stripe:in_pelicanRENEW 2026-05-14
Upcoming invoice $84,000 due in 63 days; auto-renew on.
Raw payload
{ "amount_usd": 84000 }
Diary · longitudinal account memory
First scan — diary builds one paragraph per daily run starting on the next 06:00 UTC tick. After 6 months you have 180 entries; the moat is real and time-based.
Confidence
Medium-HighAll three sources connected — Stripe billing, Slack channel signals, and HubSpot deal context. The worker's classification cites evidence from each source.
Stripe
connected
Slack
connected
HubSpot
connected
Full audit timeline (0 rows)
No audit rows yet.