Ticket assistance
When a ticket is created or receives new evidence, n8n coordinates structured extraction, transaction verification, procedure lookup and a customer-facing draft. Support reviews and edits the suggestion before anything is sent.
AI in BranchPilot
BranchPilot uses bounded AI for two jobs: preparing support work and finding answers in approved knowledge. The application owns authorization and business state; AI supplies reviewable evidence and suggestions.
When a ticket is created or receives new evidence, n8n coordinates structured extraction, transaction verification, procedure lookup and a customer-facing draft. Support reviews and edits the suggestion before anything is sent.
Approved documents are parsed, chunked, embedded and versioned asynchronously. Access scope, branch and role metadata stay attached to the knowledge so authorization can be applied before vector ranking.
A live question goes through the BranchPilot API and FastAPI retrieval service. It answers with visible sources when approved knowledge is relevant and abstains when it cannot support an answer.
BranchPilot — Ticket Processing
Coordinates extraction, verification and drafting after durable ticket events. It cannot resolve a ticket, modify membership points or execute refunds.
BranchPilot — Knowledge Ingestion
Coordinates private document ingestion and indexing. Live Knowledge Assistant questions do not pass through n8n; they use the authorized API and retrieval service directly.
Additional developer-configured workflows can be added for a customer's approved operational processes while preserving the same authorization, audit and human-review boundaries.