BFI — Customer Success Report

1. Security Ticket ↔ Google Chat Sync (BFI)

Description: Bidirectional synchronization between the Zendesk ticketing system and Google Chat for BFI's tech security operations team. New tickets and comment updates flow automatically from Zendesk into a dedicated Google Chat space, and responses from Google Chat are pushed back into Zendesk.

Business problem solved: Security operations teams need to collaborate in real time on incoming tickets without manually switching between Zendesk and their chat workspace. This automation ensures the team is instantly notified of new tickets and can respond directly from Google Chat while keeping the audit trail in Zendesk.

Integrations: Zendesk, Google Chat

2. Security Ticket ↔ Google Chat Sync (Curve)

Description: A parallel implementation of the same bidirectional Zendesk ↔ Google Chat synchronization for the Curve workspace, using a custom Google Chat card format with interactive buttons. New Curve tickets and Zendesk comment updates are routed to a separate Google Chat channel, allowing the Curve team to operate independently.

Business problem solved: The Curve team requires its own ticketing notification channel with enriched, interactive messages (cards with buttons) rather than plain text. This automation provides the same real-time visibility as the BFI channel while giving the Curve team a tailored experience.

Integrations: Zendesk (webhook), Google Chat (HTTP/Cards API), Blink Tables (sync state)

Inactive Playbooks

Strengths

• High-volume, consistent automation: The core Zendesk ↔ Google Chat sync workflows are processing thousands of events per year (2,056 + 2,437 for BFI; 430 + 489 for Curve), indicating reliable, production-grade adoption.
• Multi-team architecture: BFI has correctly separated workflows by business unit (BFI vs. Curve), allowing independent operation and channel hygiene without cross-team noise.
• Bidirectional sync realized: The comment-to-Zendesk flow (Google Chat - New comment - To Zendesk) completes the feedback loop, though its low execution count (2) suggests it may be an early pilot or only used in specific scenarios.
• Blink Tables used for state management: The Curve workflows use Blink's internal table system to track sync state, a sign of mature implementation avoiding duplicate notifications.

Gaps & Expansion Opportunities

• No enrichment layer on incoming tickets: Tickets are forwarded to Google Chat as-is, with no automated enrichment (e.g., ticket priority, requester history, SLA status, or similar open tickets). Adding enrichment would reduce analyst triage time.
• First Response playbook is a stub: The First Response workflow has never run and contains only a placeholder step. There is an opportunity to build out automated first-response SLA tracking, acknowledgment messages, or initial triage logic.
• No closure/resolution loop: There is no automation to notify the Google Chat channel when a ticket is resolved or closed, leaving the team without a clear signal of case completion.
• Google Chat → Zendesk channel is underutilized: Only 2 executions on the reverse flow suggests that analysts are not widely using Google Chat as an input channel back to Zendesk, or the workflow needs broader awareness/rollout.
• Limited use case breadth: All current automation is concentrated in a single use case (ticket notifications). BFI has no coverage in vulnerability management, identity, cloud security, or broader SOC automation — significant whitespace for expansion.

Integration Ecosystem