Approval Queue
salesforce.account · 001gK000017nFcTQAU
Calendar the exec briefing prep so it doesn't slip. Anchors week 2 of the save plan. High priority because Health_Score__c is Red and the briefing is the inflection point.
Current
(no task)
Proposed task
salesforce.account · 001gK000017nFcTQAU
Structured 60-day save aligned to SOP 2.5a §4 (Account-level intervention). Plan references and depends on the other three approvals bundled for Anchor.
Current
(no save plan yet)
Proposed save plan
salesforce.account · 001gK000017nFcTQAU
Conditional move Red -> Yellow once the save plan is in flight AND the CSM check-in is logged. Per rubric 4.1 §C, sustained Red requires either no plan or no exec contact — both addressed by the bundled approvals on this account.
Current health band
—Composite health score for the account, from 0 to 100, pulled from Salesforce. Green > 70, Yellow 40–70, Red < 40. Treat as stale if it contradicts recent engagement signals.Proposed health band
—Composite health score for the account, from 0 to 100, pulled from Salesforce. Green > 70, Yellow 40–70, Red < 40. Treat as stale if it contradicts recent engagement signals.salesforce.account · 001gK000017nFcTQAU
Per SOP 2.3 §1 — every Red-band account must carry a Primary Contact. Anchor & Reed's primary departed May 14 and was never replaced. Filing a Risk_Flag__c so the AE owns the re-anchor before next QBR.
Current
(no flag yet)
Proposed data-gap flag
(empty)
salesforce.account · 001gK000017nFcTQAU
Outbound CSM check-in to re-establish exec rhythm. Anchor & Reed Holdings has drifted on cadence and Health_Score__c flipped to Red — per SOP 2.3 §3 we open with a low-pressure ask before escalating to a formal save plan.
Current
(no email)
Proposed email
Hi there,
Wanted to reach out — we've noticed some shifts on the Anchor & Reed Holdings side that I'd love to align on. Could we grab 30 minutes next week to walk through your current priorities and how we can best support?
Happy to send a few times that work on my end.
— Robbie