Open A Ticket

Last updated: April 24, 2026

Video Tutorial

Open the ticket form
In CONTXT, go to Help → Open Ticket

  1. Enter your Name
    So we know who to contact for clarifications and updates.

  2. Enter your Email
    We’ll send confirmations and follow-ups here.

  3. Set Priority (P1–P4)

  • P1 – Critical: i.e. Major outage or shipment visibility failure.

  • P2 – High: i.e. Blocking time-sensitive work.

  • P3 – Medium: i.e. Workflow affected but there’s a workaround.

  • P4 – Low: i.e. Minor issue, question, or enhancement.
    Pick the level that truly matches impact/urgency so triage is accurate.

  1. Issue Summary (2–3 sentences)
    Describe what is wrong and where it’s happening.
    Example: “Shipment creation page fails to load for Site A when selecting Location X.”

  2. Current State (what you see now)
    Explain exactly what’s happening. Add screenshots/error text/logs if you have them.
    Goal: help us reproduce the problem quickly.

  3. Expected State (what should happen)
    Describe the correct behavior.
    Example: “Shipments should save and appear in the Active list.”

  4. Impact (scope and who’s affected)
    Share how widespread it is: single user, team, specific lane, or multiple shipments. An estimate is fine.

  5. Steps Taken So Far (avoid repeats)
    List the actions you already tried, in order (e.g., logout/login, clear cache, different browser).
    This prevents us from repeating the same basic steps and speeds resolution.

  6. Description (extras + attachments)
    Add any additional context and attach screenshots/files that support the ticket. Visuals often pinpoint the cause fastest.

  7. Submit the ticket
    Click Submit Ticket. You’ll see a confirmation and receive an email with your ticket ID.

  8. After you submit

  • Reply to the ticket email with more details or files—your replies attach to the ticket.

  • If the situation changes (worsens/improves), reply to the thread to note the new impact or priority.

  • Keep subject and ticket ID intact so updates thread correctly.

Pro tip: Clear, specific summaries + screenshots + “what I already tried” = fastest path