Support Knowledge Loop Bridge Planner

The Prompt

You are a support operations architect. Build a safe, multilingual support bridge that ties customer-facing intake, knowledge capture, and escalation systems through governed toolchain actions.

PREFERRED LLM / FAMILY:
{{preferred_llm}}

SUPPORT CONTEXT:
{{support_context}}

TICKET INPUTS:
{{ticket_inputs}}

LANGUAGE MATRIX:
{{language_matrix}}

HANDOFF RULES:
{{handoff_rules}}

QUALITY CRITERIA:
{{quality_criteria}}

APPROVAL REQUIREMENTS:
{{approval_requirements}}

Return exactly these sections:

1) Intake and Translation Architecture
- Language detection and routing design.
- Evidence capture rules and metadata standards.

2) Knowledge Loop Design
- FAQ, context, and closure templates.
- How to keep multilingual evidence synchronized.

3) Escalation and Owner Routing
- Low/medium/high severity routes.
- Human handoff points and confirmation requirements.

4) Safe Draft Action Matrix
- Suggested updates for support knowledge pages and status artifacts.
- Which actions require draft review.

5) Connector Implementation Plan
- Read-first integration order.
- Write-capable integration and guardrail profile.
- Observability and drift checks.

6) Quality and Governance
- SLA and quality targets.
- Audit logging and policy checks.
- Rollback conditions for incorrect or stale suggestions.

Rules:
- No direct external customer writes without explicit approval.
- Mark every proposed write as draft unless approval is already granted.
- Keep translation quality and legal constraints explicit.

When to Use

Use this when support and documentation systems are multilingual, distributed, and repeatedly recreate manual routing logic that should be standardized into a controlled AI-assisted process.

Variables

Variable	Description	Example
`preferred_llm`	LLM family for planning and drafting	`claude-opus`, `gpt`
`support_context`	Support environment scope	”Tech support + onboarding support, EMEA + APAC.”
`ticket_inputs`	Main sources and channels	”Zendesk exports, Slack support threads, Notion article repository.”
`language_matrix`	Priority languages and quality requirements	”English, French, German; legal-safe tone checks.”
`handoff_rules`	Escalation and ownership rules	”Escalate P1 to operations lead within 10 minutes.”
`quality_criteria`	Accuracy and response standards	”90% factual accuracy threshold, unresolved rate < 3%.”
`approval_requirements`	What needs human signoff	”Draft article updates need content owner approval.”

Tips & Variations

Add region-aware routing if support SLAs differ by geography.
Ask for a “contradiction resolver” rule when KB versions diverge by locale.
Include sentiment and urgency heuristics for routing policy tuning.
Request a periodic stale-content cleanup cadence.

Example Output

Routing plan separates translation, triage, and draft-update tracks with clear ownership.
Knowledge loop output includes source-of-truth synchronization rules between ticketing and KB.
Governance section lists where approvals pause automation.

The Prompt

When to Use

Variables

Tips & Variations

Example Output

Related site references