Automation health
16 project files are connected, including cancellation monitoring, vendor watchlists, refunds, Slack webhook intake, admin dashboard, and ticket-checker modules.
WEDNESDAY, 07 OCTOBER 2026 / LOCAL TIME
OVERVIEW
A summary of the recon pings, plus quick links to your automations.
TEAM AREA 01
Pings raised in #tf-recon-discrepancies from 7 Oct onwards, with their threads and where each stands.
The key stays in this browser only. When you sort, ping text (BIDs, SP names, amounts, thread messages) is sent to Google’s Gemini API. Free-tier requests may be used by Google to improve its products.
Starting state comes from Slack: Open = no team reply yet, Pending = replied but not closed, Resolved = ✅ reaction. Changes you make here are saved in this browser.
TEAM AREA 02
The central automation layer for cancellations, refunds, vendors, and alerts.
16 project files are connected, including cancellation monitoring, vendor watchlists, refunds, Slack webhook intake, admin dashboard, and ticket-checker modules.
Slack webhook intake is the handoff point for issues that need the team’s attention. Use the Recon section for the working queue.
TEAM AREA 03
Usage reporting and product-level booking visibility.
Daily usage output available
Rolling usage window
Daily Usage · Top Experiences
TEAM AREA 04
Ticket receipt checks and portal verification follow-ups.
Pings about missing or late tickets, raised from 7 Oct onwards
INTEGRATIONS
Links back to the systems that power this control room.
Recon pings, no-loss/refund mismatches, late-ticket checks, and vendor portal questions.
Open source ↗Cancellation monitor, vendor watchlist, refunds, admin dashboard, ticket checker, and Slack webhook modules.
Open project ↗Daily Usage and Top Experiences outputs for monitoring booking behavior and product activity.
Open project ↗