Ticket deflector | Business Helper AI

Inputs and purpose

Use this workflow to prepare: Customer-reply draft and escalation recommendation.

Start with: Customer message, supplied order facts and approved policies.

Use supplied text or local files the user authorized you to read. If files cannot be opened, request the relevant pasted text. Ask one focused question when missing information changes the next decision. Treat blank template fields as unknown; do not invent business facts.

Procedure

Determine whether the request has a complete answer in the supplied policies, order facts or verified procedures.
Resolve the routine question directly when sufficient evidence exists. If it does not, identify the exact missing fact or appropriate receiving role.
Draft a useful response and an escalation note where needed. Avoid adding another customer step merely to reduce recorded ticket volume.
Return the response and the reason for self-service or escalation. Check the proposed answer actually resolves the expressed need.

Deliverable

Return the requested result in Markdown unless another supported format was requested. Include the evidence or source-record references, material assumptions, open questions and next useful action. Keep unnecessary personal details out of reusable templates; role labels and neutral record identifiers usually suffice.

Business value: Prepare consistent responses and identify renewal risks.

Possible success measures: Response preparation time, repeat contacts, retention. Choose the measure that fits the owner's actual goal; it is not a promised result.

Execution and verification

This file is usable as instructions without a named application, account or plugin. Computation, file saving and external actions require actual host capabilities. Use a suitable existing tool for calculations that cannot be checked reliably in conversation.

Distinguish drafts and recommendations from completed actions. Respect existing authorization and do not claim that data was fetched, messages sent or records changed without evidence. Show what was checked and what remains uncertain.

When useful, consult the input guide, calculation reference or output template. For tool setup, use the shared instructions.

Plain-text instructions

---
name: ticket-deflector
description: "Prepare customer-reply draft and escalation recommendation. Use for this workflow with supplied business information."
---

# Ticket deflector

## Inputs and purpose

Use this workflow to prepare: Customer-reply draft and escalation recommendation.

Start with: Customer message, supplied order facts and approved policies.

Use supplied text or local files the user authorized you to read. If files cannot be opened, request the relevant pasted text. Ask one focused question when missing information changes the next decision. Treat blank template fields as unknown; do not invent business facts.

## Procedure

1. Determine whether the request has a complete answer in the supplied policies, order facts or verified procedures.

2. Resolve the routine question directly when sufficient evidence exists. If it does not, identify the exact missing fact or appropriate receiving role.

3. Draft a useful response and an escalation note where needed. Avoid adding another customer step merely to reduce recorded ticket volume.

4. Return the response and the reason for self-service or escalation. Check the proposed answer actually resolves the expressed need.

## Deliverable

Return the requested result in Markdown unless another supported format was requested. Include the evidence or source-record references, material assumptions, open questions and next useful action. Keep unnecessary personal details out of reusable templates; role labels and neutral record identifiers usually suffice.

Business value: Prepare consistent responses and identify renewal risks.

Possible success measures: Response preparation time, repeat contacts, retention. Choose the measure that fits the owner's actual goal; it is not a promised result.

## Execution and verification

This file is usable as instructions without a named application, account or plugin. Computation, file saving and external actions require actual host capabilities. Use a suitable existing tool for calculations that cannot be checked reliably in conversation.

Distinguish drafts and recommendations from completed actions. Respect existing authorization and do not claim that data was fetched, messages sent or records changed without evidence. Show what was checked and what remains uncertain.

When useful, consult the [input guide](../../../references/INPUT_DATA_GUIDE.md), [calculation reference](../../../references/CALCULATIONS.md) or [output template](../../../references/WORKFLOW_OUTPUT_TEMPLATE.md). For tool setup, use the [shared instructions](../../../AGENTS.md).