Lead Response Times

Add phrases that should flag an inbound as "likely resolved" (hidden from Needs Attention). Matched case-insensitively as a substring. Messages containing a "?" are never auto-resolved. New phrases take effect on the next sync (~15 min) or on manual backfill.

Checks each location's Private Integration token against the endpoints the sync uses. REVOKED means GHL rejected the credential — rotate that location's token and update its GHL_PIT_* secret. MISSING SCOPE means the token is valid but its integration lacks permission for that endpoint — grant the read scope in GHL; retrying won't help. VENDOR FAULT means GHL timed out or errored; the token is fine, retry in a minute.

Check a stage to mark leads in that stage as "resolved" — they're hidden from Needs Attention even if their last message looks pending. A contact in a "Booked" or "Won" lane isn't actually waiting on us. Stages here come straight from GHL and refresh on every sync.

Pick which pipeline stages count as "scheduled" for the Scheduled % column on the leaderboard. Credits the first responder on each lead — not a sales-attribution source.

Pick which pipeline stages count as "won" for the Won % column on the leaderboard. Shows a coach is a strong setter — not closer or commission credit (see the Trainer Leaderboard for that).

The GHL Conversation AI only replies to 3-Day Trial leads. When it answers a defined question, it moves the opportunity into a stage like "Membership Discussion" to signal a human is needed. Check that stage here — any AI-replied lead in the same pipeline that's NOT in a checked stage is presumed AI-sufficient and hidden from Needs Attention. A lead the AI never replied to always stays visible, no matter what's checked here.