Draft response | Business Helper AI

Inputs and purpose

Use this workflow to prepare: Response draft and internal follow-up notes.

Start with: Customer message and verified product/policy/context facts.

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

Identify the customer's request, emotional context and the action the business can actually take under the supplied policy.
Resolve facts needed for the response from the provided record; mark uncertain order or account information rather than guessing.
Draft a clear acknowledgement, relevant explanation and next step. Match the level of commitment to the responder's stated authority.
Return customer-facing text separately from internal notes. Check promises, amounts, dates and policy references before release.

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: draft-response
description: "Prepare response draft and internal follow-up notes. Use for this workflow with supplied business information."
---

# Draft response

## Inputs and purpose

Use this workflow to prepare: Response draft and internal follow-up notes.

Start with: Customer message and verified product/policy/context facts.

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. Identify the customer's request, emotional context and the action the business can actually take under the supplied policy.

2. Resolve facts needed for the response from the provided record; mark uncertain order or account information rather than guessing.

3. Draft a clear acknowledgement, relevant explanation and next step. Match the level of commitment to the responder's stated authority.

4. Return customer-facing text separately from internal notes. Check promises, amounts, dates and policy references before release.

## 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).