Session Objective

Assess why the SAIL Command Center is still not functional enough to drive daily operations, using live evidence from the command-center app, Notion Knowledge Base, Outlook/Gmail, Litify/Salesforce, Attorney Hubs, intake data, and the Marketing Center.

Work Completed

• Ran the local command center in auto-live mode and verified /api/health plus /api/dashboard-data?mode=auto.
• Queried live Salesforce through LITIFY_ORG for current-month Intake, Matter, CallRail, Attorney Hub classes, reports, and dashboards.
• Sampled Outlook for current-day CallRail, Intaker, Alert Communications, call-analysis, and website-intake messages.
• Sampled Gmail and found it is mostly SEO/vendor/personal noise for this use case, while Outlook is the primary intake ops lane.
• Searched and fetched relevant SAIL KB records, including the June 4 Today Attention panel and June 1 Marketing Center wiring handoff.
• Probed the live Marketing API and Litify marketing payload.
• Staged a docs-only assessment at Repos/sail-command-center/docs/command-center-daily-ops-gap-assessment-2026-06-14.md.

Key Findings

• Health score: 43 / 100. The system is live enough to prove the idea, but not daily-driver ready.
• The problem is not lack of data. It is fragmented data contracts and weak decision packaging.
• The command center currently shows live Litify aggregates, but Outlook, project memory, SEO, and several report lanes are stale or pending.
• Outlook had current-day intake and call evidence from CallRail, Intaker, Alert, call analysis, and website intake. The app still uses mock Outlook examples.
• Current-month Intake showed 274 all intakes, 104 MVA intakes, 26 all-intake records missing Source, 0 Exact Source populated, 21 GCLID, 30 UTM Source, and 159 call-center call IDs.
• CallRail object showed 752 calls MTD, 351 linked to Intake, 36 with GCLID, and 693 with UTM Source.
• Attorney Hub controllers and dashboards are active and current, but the command center attorney-team table still only shows open case counts and leaves fees, outcomes, dropped/referred, and desk-time pending.
• The case-manager exception layer is valuable but too buried. It should become ranked exception cards.
• Marketing Center data is live and rich, but command center is not consuming the Marketing Center semantic layer. The Marketing API also exposes conflicting KPI layers that need source-priority rules before promotion.