Support Ticket Follow-up Patterns

Ticket Reply Draft

A static support ticket reply draft shows SUP-2048, Still seeing the spinner, no attachment, and Draft reply status.

Program

Ticket reply drafts should show the ticket, message, and attachment state before any support reply is sent.

ticket_reply_draft.html
Visuals: captured from real browser rendering
<section class="ticket-reply" aria-labelledby="ticket-reply-title"><h2 id="ticket-reply-title">Ticket reply draft</h2><dl>
  <div><dt>Ticket</dt><dd>SUP-2048</dd></div>
  <div><dt>Message</dt><dd>Still seeing the spinner</dd></div><div><dt>Attachment</dt><dd>None</dd></div>
  <div><dt>Status</dt><dd><span class="badge">Draft reply</span></dd></div></dl>
  <p class="check">Learner check: the reply draft is visible before any support message is sent.</p>
  <p class="note">Static ticket reply draft only; no support API, reply service, attachment upload, file API, storage, route, network, script, event listener, form submit, analytics, timer, or live support service runs.</p></section>
<style>
  .ticket-reply { display: grid; gap: 10px; max-width: 38rem; border: 1px solid #0f766e; padding: 12px; background: #f0fdfa; }
  .ticket-reply dl { display: grid; gap: 8px; margin: 0; }
  .ticket-reply dl div { display: grid; grid-template-columns: 8rem 1fr; gap: 8px; }
  .ticket-reply dt { color: #475569; }
  .ticket-reply dd, .check, .note { margin: 0; }
  .badge { border-radius: 999px; background: #ccfbf1; padding: 2px 8px; }
  .note { color: #475569; }
</style>

  1. Label the reply draft.

    The section is labelled by its visible heading.
    The section is labelled by its visible heading.

  2. Show ticket row.

    The ticket id is exact pinned data.
    The ticket id is exact pinned data.

  3. Show message and attachment rows.

    The message and attachment state are exact pinned data.
    The message and attachment state are exact pinned data.

  4. Render draft reply status.

    The status badge says this is a draft reply.
    The status badge says this is a draft reply.

  5. Check reply readback.

    The check says the reply draft is visible before any support message is sent.
    The check says the reply draft is visible before any support message is sent.

  6. Check reply honesty.

    Ticket, message, attachment, status, and no live reply.
    Ticket, message, attachment, status, and no live reply.
step flow step(1) labels the source, step(2) shows the ticket id, step(3) shows message and attachment rows, step(4) shows draft reply status, step(5) checks the reply readback, and step(6) checks the honesty note.
reply readback The section heading names the ticket reply draft surface.
reply rows Ticket, Message, Attachment, and Status values are exact pinned data.
no live reply The lesson should not imply support APIs, reply services, attachment uploads, file APIs, storage, routes, networks, scripts, event listeners, form submits, analytics, timers, or live support services.