Tell whether a customer is reporting a fault or asking for a new feature

A draft behaviour classification note with fault and enhancement tracks.

Choose one of three approaches. The steps for that option appear below.

Choose an option above. On a phone, swipe the tabs left or right to see all options →

Claude: proposes the worksheet and note, you check

Claude proposes the behaviour worksheet, then the fault and enhancement note from your corrected rows. You check both.

  1. You

    Have ready

  2. Claude

    Propose worksheet

  3. You

    Correct the rows

  4. Claude

    Draft the note

  5. You

    Check and label

  1. Have ready: the ticket, documents and approved rules

    Use: You

    Collect the ticket, the versioned behaviour documentation and the approved rules, scope and as-of dates. Keep the originals locally.

    Check

    Upload only after the case owner clears the sharing scope. Never paste credentials, passwords, authentication codes, session tokens or full payment details.

  2. Propose the behaviour worksheet

    Use: Claude

    Ask Claude for a worksheet separating observed, expected and documented behaviour by version, with quoted evidence.

    Details

    What to paste into the tool

    Task: Proposed behaviour worksheet with quoted evidence and version references; Redacted case bundle with source IDs and approved dated rules. Use only this case bundle; give each row a stable ID, original value or contiguous quote, source ID, version, approved rule, applicability date and confirmed-versus-reported status; retain contradictions and not-stated markers; return the case bundle alongside the proposed worksheet

  3. Correct the worksheet against the originals

    Use: You

    Check each row against the originals for this case: Customer expects an unsupported export layout.

    Check

    Compare every worksheet row with the supplied originals. Do not resolve missing or contradictory facts by inference. List each correction.

  4. Draft the fault and enhancement note

    Use: Claude

    Ask Claude in the same chat to apply your corrections and draft separate fault and enhancement tracks with open questions.

    Details

    What to paste into the tool

    Task: Proposed fault and enhancement note; Open case questions and next human decision proposal. First apply my listed corrections to the worksheet rows; where I marked a row wrong, fix or drop it. Then compare each expectation with the documented version boundary and approved rules; cite worksheet row IDs; distinguish supported fault evidence from requested enhancements; mark gaps not stated; include unresolved questions and a proposed human decision without any external action, remedy or deadline. My corrections: [paste checked corrections or none]. Worksheet and rules: [paste the worksheet and the redacted rules].

  5. Check the note and label gaps

    Use: You

    Return a clearly labelled incomplete draft if required source material or a qualified reviewer is missing; a human separately approves any downstream action.

    Check

    Preparation only: do not send, publish, change records or accounts, assign work or commit a remedy or deadline.

Before you paste into any AI tool, remove any confidential information. Put it back at the end.

Tools in this workflow

Deciding between ChatGPT and Claude for this? See the comparison.

Final check

Never paste credentials or full payment details.

Use only the supplied case evidence and approved rules; preserve source references, applicability dates and unresolved facts.

Cut down customer information in drafts and handoffs; never request or reproduce passwords, authentication codes, session tokens or payment credentials.

If required source material or a qualified reviewer is missing, return a clearly labelled incomplete draft rather than inventing a result.

Each expectation is compared with documented behaviour or marked not stated. Support triage lead confirms the evidence and draft; completion is preparation, not downstream execution.

Suggestions and preparation only. Do not send, publish, change records or accounts, assign work, execute code, initiate a purchase, or commit a remedy or deadline. A human separately approves any downstream action.

Check the result against your original inputs. Approve it before sharing or acting.

What still needs checking
  • Exact case extraction, version-boundary classification and draft audit behaviour remain unchecked for these proposed requests

Share this page