Is Your Internet Down? Complete Family Troubleshooting Form

Important Note: This analysis provides strategic insights to help you get the most from your form's submission data for powerful follow-up actions and better outcomes. Please remove this content before publishing the form to the public.

Overall Form Assessment

The \"Internet Outage Troubleshooting Guide & Diagnostic Form\" demonstrates exceptional structural design for its intended purpose of systematic home internet diagnostics. The form excels in its logical progression from basic information gathering through advanced technical diagnostics, creating a comprehensive troubleshooting workflow that mirrors professional IT support protocols. Its greatest strength lies in the conditional follow-up system, which provides dynamic guidance based on user responses, effectively simulating an expert troubleshooting session. However, the form's comprehensive nature, while valuable for thorough diagnostics, presents a potential weakness in user experience—lengthy forms risk abandonment, particularly during stressful internet outage situations. The density of technical terminology, though necessary for accurate diagnostics, may alienate less tech-savvy users who constitute a significant portion of the target audience. Additionally, the lack of a visual progress indicator could leave users uncertain about remaining time commitment, potentially increasing dropout rates before completion.

The form's data collection strategy is robust and purposeful, capturing both quantitative metrics and qualitative observations essential for root cause analysis. The mandatory field selection is well-curated, focusing on critical diagnostic data points while leaving supplementary details optional. This approach balances the need for comprehensive information against user burden. Privacy considerations are appropriately addressed through the collection of only essential personal information, though the form could benefit from an explicit privacy statement given the technical data being collected. The inclusion of visual documentation requests (router light photos, error screenshots) represents an advanced data collection feature that significantly enhances diagnostic capabilities beyond traditional text-only forms.

Question: Your Name

Purpose of the Question: This field establishes accountability and enables personalized follow-up support. In a family troubleshooting context, identifying who is completing the form allows support teams to reference previous interactions and tailor guidance based on technical proficiency. It also creates a point of contact for escalation scenarios and ensures that recommendations can be traced to a responsible party within the household.

Effective Design & Strengths: The single-line text input with placeholder example demonstrates excellent UX microcopy. The placeholder \"e.g., John Smith\" provides clear format guidance without being prescriptive. Positioned early in the form, it leverages the commitment principle—users who provide their name are more likely to complete the subsequent diagnostic steps. The field's simplicity ensures universal comprehension and minimal completion friction.

Data Collection Implications: Collects minimal PII (Personally Identifiable Information) necessary for service delivery. The data quality is typically high as users rarely fake their names in support contexts. From a privacy standpoint, this represents a legitimate interest data collection practice under GDPR principles. The data enables case tracking and personalized communication without exposing sensitive personal information.

User Experience Considerations: Presents virtually zero friction as it's a universally understood field. The mandatory nature is justified and expected for a diagnostic tool. One potential improvement would be adding inline validation to prevent empty spaces or special characters that could corrupt data integrity. The field could also include autocomplete for returning users to expedite completion.

Overall Impact: This foundational field, while simple, is crucial for transforming anonymous data into actionable support cases. Its strategic placement and clean design maximize completion rates while capturing essential contact information.

Question: How many family members or devices are affected by this outage?

Purpose of the Question: This quantitative metric immediately establishes the scope and severity of the outage, distinguishing between isolated device issues and household-wide failures. This data directly influences troubleshooting priority and resource allocation in support scenarios. A higher number suggests router or ISP-level problems, while a single affected device points to localized issues requiring narrow diagnostics.

Effective Design & Strengths: The numeric input field is the optimal choice for precise data collection, preventing ambiguous text responses like \"a few\" or \"everyone.\" The placeholder \"e.g., 4\" provides clear guidance on expected format. The question cleverly combines \"family members or devices,\" acknowledging that in modern households, the number of devices often exceeds the number of people, making the question flexible and inclusive.

Data Collection Implications: Generates high-quality, analyzable data for pattern recognition across multiple support cases. This metric can be correlated with router models, connection types, and geographic areas to identify systemic issues. The data is low-sensitivity and presents minimal privacy concerns while providing significant diagnostic value for trend analysis.

User Experience Considerations: While generally low-friction, the question could create momentary confusion—users might wonder whether to count people or devices or both. Adding a clarifying subtext like \"Count each person plus their devices, or just devices if easier\" would reduce cognitive load. The mandatory nature is appropriate as scope assessment is fundamental to diagnostic logic and triage.

Overall Impact: This numerical anchor provides immediate context that shapes the entire diagnostic approach, making it indispensable for efficient problem resolution and resource allocation.

Question: When did the internet issue first start?

Purpose of the Question: Temporal data is critical for correlating outages with external events such as ISP maintenance windows, firmware updates, weather events, or physical changes to the network environment. This timestamp creates a diagnostic anchor point for timeline-based troubleshooting and helps identify patterns in recurring issues that might otherwise appear random.

Effective Design & Strengths: The datetime picker input ensures standardized, machine-readable data formats, eliminating ambiguity from text descriptions like \"this morning\" or \"around 3.\" Capturing both date and time enables precise correlation with system logs and event histories. The mandatory requirement ensures every diagnostic case has a chronological foundation.

Data Collection Implications: Produces highly valuable temporal data for root cause analysis and trend identification. When aggregated across multiple submissions, this data can reveal ISP-wide outages, firmware update problems, or seasonal connectivity issues. The data is non-sensitive and presents no privacy concerns while enabling sophisticated pattern analysis.

User Experience Considerations: During stressful outage situations, users may struggle to recall exact timestamps. The datetime picker simplifies this but could be enhanced with common shortcut buttons like \"Within last hour,\" \"This morning,\" or \"Yesterday\" to accommodate memory limitations. The mandatory nature is crucial for diagnostic validity, though the form should be lenient with approximate times if exact recall is difficult.

Overall Impact: This timestamp serves as the diagnostic timeline's anchor, enabling correlation with external events and pattern recognition that would be impossible without temporal context.

Question: What type of internet connection do you have?

Purpose of the Question: This categorical data fundamentally shapes the entire diagnostic approach, as each connection type (Fiber, Cable, DSL, Satellite) has unique architectures, typical light patterns, and specific troubleshooting steps. It prevents inappropriate advice—DSL troubleshooting differs significantly from Satellite diagnostics, and using the wrong approach could waste hours or cause configuration damage.

Effective Design & Strengths: The single-choice format with an inclusive \"I'm not sure\" option prevents user abandonment while still collecting useful data. The options are ordered from most common/high-performance (Fiber) to less common (Mobile Hotspot), aiding quick selection. The mandatory status ensures diagnostic relevance from the outset of the troubleshooting process.

Data Collection Implications: Creates a critical segmentation variable for all collected data, enabling ISP-specific and technology-specific troubleshooting pathways. This categorical data is essential for building knowledge bases and identifying technology-specific systemic issues. No privacy concerns exist, and the data is highly reliable for analytics.

User Experience Considerations: The \"I'm not sure\" option is a thoughtful inclusion that prevents guesswork and reduces anxiety. For technical users, the options are clear; for novices, the form could add visual icons or brief descriptions for each type to aid recognition. The mandatory nature is non-negotiable as connection type determines all subsequent diagnostic logic.

Overall Impact: This foundational context prevents misguided troubleshooting and ensures all subsequent questions and recommendations are technically appropriate for the user's specific internet technology.

Question: Is this a recurring issue that has happened before?

Purpose of the Question: This binary question immediately flags chronic problems requiring deeper investigation versus one-time events with simpler solutions. Recurring issues often indicate hardware failures, line degradation, or ISP infrastructure problems rather than temporary glitches. This data point influences escalation decisions and long-term solution strategies.

Effective Design & Strengths: The yes/no format with conditional follow-up for \"yes\" responses creates an efficient branching workflow. Users answering \"no\" proceed quickly, while \"yes\" respondents provide valuable historical context. The follow-up multiline text box encourages detailed narratives about previous occurrences and resolutions, building a rich case history.

Data Collection Implications: This qualitative historical data is invaluable for identifying intermittent issues that don't appear in single-incident diagnostics. When combined with timeline data, it can reveal patterns like \"fails every evening\" or \"happens after rain.\" The data quality depends on user recall but provides context that pure metrics cannot capture.

User Experience Considerations: The binary choice is low-effort, and the conditional follow-up prevents unnecessary typing for one-time issues. The question is positioned early enough to frame subsequent diagnostics but could benefit from emphasizing that \"recurring\" means \"more than once in the last month\" to standardize responses. The mandatory status is essential for severity assessment.

Overall Impact: This pattern identification flag prevents misdiagnosis of chronic problems as isolated incidents, ensuring appropriate long-term solutions rather than temporary fixes.

Question: What is the current power light status on your router?

Purpose of the Question: The power light is the most fundamental hardware status indicator, revealing whether the router is receiving electricity, booting up, or experiencing critical failures. This visual diagnostic is the first step in hardware troubleshooting and determines whether to investigate electrical issues or proceed to network-layer diagnostics.

Effective Design & Strengths: The single-choice options provide descriptive interpretations (\"Solid Red/Amber (Error)\") rather than just colors, guiding non-technical users toward correct assessment. The mandatory requirement ensures this basic hardware check is never skipped, preventing wasted time on complex diagnostics for a simple power issue.

Data Collection Implications: This categorical status data is the foundation of the diagnostic decision tree. When aggregated, it can identify batches of faulty routers or power supply issues. The data is objective and highly reliable since it requires direct observation. No privacy concerns exist, and the data is immediately actionable.

User Experience Considerations: Users must physically locate their router, which may be inconvenient, but the clear option descriptions minimize misinterpretation. Adding a small diagram or link to common router light configurations would enhance usability. The mandatory nature is justified as power status is the gateway to all subsequent diagnostics.

Overall Impact: This fundamental hardware check prevents misdiagnosis of power issues as network problems, saving countless hours of unnecessary troubleshooting.

Question: What is the current internet/WAN light status?

Purpose of the Question: This light directly indicates the router's ability to communicate with the ISP, making it the single most important diagnostic indicator for internet connectivity issues. The status reveals whether the problem exists within the home network (local) or in the ISP's external infrastructure, fundamentally directing the troubleshooting path toward appropriate solutions.

Effective Design & Strengths: The options include both status and interpretation (\"Blinking Amber (Connection Issue)\"), educating users while collecting data. The conditional follow-up text for specific statuses (blinking amber, solid red) provides real-time guidance, making the form feel interactive and intelligent. The mandatory status ensures this crucial data point is always captured.

Data Collection Implications: This is arguably the most valuable single data point in the entire form, directly correlating with outage causes. When combined with ISP data, it can automatically trigger outage notifications or service tickets. The categorical data is objective and essential for any meaningful diagnostic conclusion.

User Experience Considerations: The conditional help text transforms a simple question into a mini-diagnostic tool, reducing user anxiety by explaining what each status means. The question could be enhanced by specifying \"wait 2 minutes after power cycling before checking\" to ensure accurate readings. The mandatory nature is absolutely critical—without this data, the diagnostic framework collapses.

Overall Impact: This single status check provides the diagnostic direction for the entire troubleshooting process, making it indispensable for efficient problem resolution.

Question: Have you power cycled (unplugged and replugged) your router and modem?

Purpose of the Question: Power cycling resolves approximately 80% of home internet issues by clearing cache, renewing IP leases, and resetting hardware states. This question verifies compliance with the most effective first-step solution, preventing unnecessary escalation and ensuring users don't skip this simple fix in favor of more complex diagnostics.

Effective Design & Strengths: The yes/no format with conditional branches is masterfully implemented. \"No\" respondents receive immediate, specific instructions (unplug for 60 seconds, plug modem first, wait 2 minutes), while \"yes\" respondents can provide details about the process. This ensures all users either perform or have performed this critical step correctly.

Data Collection Implications: This boolean data reveals user behavior patterns—how many users attempt basic troubleshooting before seeking help. When combined with outcome data, it can quantify the effectiveness of power cycling for different router models and connection types. The data is simple but powerful for support analytics.

User Experience Considerations: The detailed instructions for \"no\" answers transform the form into an interactive guide rather than just a data collection tool. The 60-second and 2-minute specifications provide precision that increases success rates. The mandatory nature is essential because skipping this step invalidates all subsequent diagnostics.

Overall Impact: This verification step ensures the most effective and simplest solution is attempted first, preventing wasted effort and providing immediate resolution in the majority of cases.

Question: Do you have any devices that are still down after completing the table above?

Purpose of the Question: This question acts as a quality gate for the device-specific troubleshooting table, identifying persistent problems that require escalation beyond basic fixes. It ensures users don't prematurely conclude their troubleshooting is complete when devices remain offline, directing them toward advanced diagnostics or ISP contact.

Effective Design & Strengths: The yes/no format with a conditional follow-up for listing still-down devices creates a clear escalation path. The question references the preceding table, creating a logical workflow that validates the table's completion. The mandatory status ensures users consciously acknowledge the status of all devices.

Data Collection Implications: This boolean flag is critical for triage, separating resolved cases from those needing further intervention. The qualitative follow-up data identifies specific problematic devices that may have unique compatibility issues or hardware failures. This data helps prioritize support resources and identify device-specific patterns.

User Experience Considerations: Users must complete the device table before answering, which could cause frustration if the table is complex. However, this dependency ensures systematic troubleshooting. The question could benefit from being disabled until the table is populated. The mandatory nature is important for ensuring users don't abandon the process with unresolved issues.

Overall Impact: This quality gate prevents false resolution declarations and ensures persistent problems receive appropriate escalation, maintaining the form's effectiveness as a complete diagnostic tool.

Question: Are all cables securely connected to your router, modem, and wall outlets?

Purpose of the Question: Physical connectivity is the foundation of network function, yet loose cables are among the most common causes of internet outages. This question forces systematic inspection of the physical layer before proceeding to more complex software diagnostics, preventing wasted effort on misconfigured settings for hardware connection problems.

Effective Design & Strengths: The yes/no format with conditional guidance for \"no\" answers provides immediate remediation instructions. The broad scope (router, modem, wall outlets) ensures comprehensive inspection. The mandatory status prevents skipping this basic but critical check that resolves many issues instantly.

Data Collection Implications: This boolean data, when correlated with outage resolution, quantifies the prevalence of physical connection issues. It can identify trends related to specific cable types or installation practices. The data is highly reliable and requires no technical expertise to provide.

User Experience Considerations: The physical inspection requirement may be inconvenient but is essential for thorough diagnostics. The conditional guidance for loose cables provides immediate value. The question could be enhanced with a checklist diagram showing common connection points. The mandatory nature is justified as physical layer issues are common and easily fixable.

Overall Impact: This fundamental check prevents misdiagnosis of physical problems as complex network issues, providing quick resolution for one of the most common outage causes.

Question: Which specific cable connections have you inspected?

Purpose of the Question: This granular question ensures users perform a systematic physical inspection rather than a cursory glance, as different cable types have different failure modes and criticality levels. This data identifies which physical components have been validated and which might be overlooked sources of problems.

Effective Design & Strengths: The multiple-choice format allows selection of all applicable connections, providing a comprehensive inspection record. The options cover all common connection types across different internet technologies. The mandatory status ensures thoroughness and creates a verifiable inspection checklist.

Data Collection Implications: This detailed categorical data reveals which physical components are most often overlooked or problematic. When aggregated, it can guide educational content about proper cable maintenance and identify common failure points. The data quality is high as it reflects actual inspection actions.

User Experience Considerations: The comprehensive list may seem overwhelming, but it serves as a helpful reminder of all connection points. Users might appreciate a \"Select All\" option for thorough inspections. The mandatory nature ensures no connection is systematically ignored, which is essential for ruling out physical layer issues.

Overall Impact: This detailed checklist ensures comprehensive physical inspection, preventing overlooked connections from becoming misdiagnosed complex problems.

Question: Can you see your Wi-Fi network name (SSID) in the available networks list on your devices?

Purpose of the Question: This question differentiates between Wi-Fi radio failures and internet connectivity issues. If the SSID is visible, the wireless hardware is broadcasting; if not, the problem is localized to the router's Wi-Fi function. This is a critical diagnostic boundary that determines the entire troubleshooting direction.

Effective Design & Strengths: The yes/no format with conditional follow-up for \"no\" answers guides users toward Wi-Fi-specific diagnostics. The question is phrased in plain language (\"network name\") while including the technical term (\"SSID\") for clarity. The mandatory status ensures this key distinction is made for every case.

Data Collection Implications: This boolean data is essential for triaging Wi-Fi issues versus ISP issues. When combined with device connection data, it can identify router hardware failures or configuration problems. The data is objective and easily verifiable by users of any technical level.

User Experience Considerations: Checking for SSID visibility is a simple device-level action most users can perform. The conditional help text for \"no\" answers provides immediate next steps. The question could specify checking from multiple devices to rule out single-device issues. The mandatory nature is crucial for proper diagnostic pathing.

Overall Impact: This simple visibility check creates a critical diagnostic fork, ensuring troubleshooting focuses on the correct layer (wireless vs. internet) from the start.

Question: Can your devices connect to the Wi-Fi network but show 'No Internet' or 'Connected without internet'?

Purpose of the Question: This question identifies the precise failure point—local network functionality versus internet reachability. This distinction is crucial because it directs troubleshooting toward router-to-modem connections (if local network works) or device-to-router issues (if local network fails), fundamentally shaping the diagnostic approach.

Effective Design & Strengths: The yes/no format with conditional guidance for \"yes\" answers provides immediate diagnostic direction. The question uses the exact error messages users see, reducing interpretation errors. The mandatory status ensures this critical symptom is captured for every submission.

Data Collection Implications: This symptom data is among the most actionable in the entire form, immediately narrowing the problem scope. When correlated with router light status, it can automatically suggest specific fixes. The data is highly reliable as it reflects direct user observation of their device's status.

User Experience Considerations: The question's specificity helps users accurately identify their situation. The conditional guidance provides instant value and next steps. The mandatory nature is essential because this symptom fundamentally determines the troubleshooting approach and prevents misdiagnosis.

Overall Impact: This precise symptom identification ensures troubleshooting efforts target the correct network segment, dramatically improving resolution efficiency.

Question: Please describe all troubleshooting steps you've already attempted, in the order you tried them:

Purpose of the Question: This open-ended field prevents redundant troubleshooting efforts and reveals user behavior patterns. Knowing what has already been attempted (and failed) directs subsequent steps and avoids frustrating users by repeating ineffective actions. It also identifies potentially harmful actions like incorrect settings changes.

Effective Design & Strengths: The multiline text box with a detailed placeholder example (\"e.g., 1. Rebooted router, 2. Checked cables, 3. Contacted ISP...\") provides clear structure guidance. The mandatory status ensures support teams have complete action histories for every case, which is essential for escalation scenarios.

Data Collection Implications: This narrative data, while harder to automate, provides rich context for complex cases. Natural language processing could extract common action sequences and their success rates. The data quality varies by user detail level but is invaluable for escalation cases and building knowledge bases.

User Experience Considerations: Recalling and documenting steps requires significant cognitive effort, especially during stressful outages. The placeholder helps, but the field could be enhanced with a dynamic list builder that prompts for each action. The mandatory nature is justified for preventing redundant support efforts, though it may contribute to form abandonment.

Overall Impact: This historical log ensures efficient support by eliminating guesswork and preventing repetitive troubleshooting, making it essential for effective escalation and resolution.

Important Note: This analysis provides strategic insights to help you get the most from your form's submission data for powerful follow-up actions and better outcomes. Please remove this content before publishing the form to the public.

Mandatory Questions Justification

Your Name: This field is absolutely essential for creating a support case and enabling personalized follow-up communication. Without a contact name, any diagnostic information collected becomes anonymous and untrackable, preventing effective escalation or resolution verification. In a family troubleshooting context, knowing who is completing the form helps assess technical capability and ensures accountability for following through on recommended steps. This minimal personal data collection is justified by the legitimate interest of providing effective technical support.

How many family members or devices are affected by this outage? This quantitative metric is critical for immediate severity assessment and resource prioritization. A single affected device suggests a localized problem requiring narrow troubleshooting, while multiple affected devices indicate router or ISP-level issues needing broader investigation. This data directly influences the diagnostic path and potential escalation urgency, making it non-negotiable for effective triage. Without this scope information, support teams cannot properly prioritize cases or allocate appropriate technical resources.

When did the internet issue first start? Temporal data is fundamental to all diagnostic processes, enabling correlation with external events like ISP maintenance, firmware updates, weather incidents, or physical changes. This timestamp serves as an anchor for timeline-based troubleshooting and pattern recognition in recurring issues. Without knowing when the problem began, it's impossible to identify causal relationships or determine if the issue is chronic versus acute. This data is essential for both immediate diagnostics and long-term trend analysis across support cases.

What type of internet connection do you have? This categorical information fundamentally determines the appropriate diagnostic procedures, as Fiber, Cable, DSL, and Satellite connections have distinct architectures, light patterns, and failure modes. Providing incorrect troubleshooting steps for the wrong connection type could waste time or potentially cause further configuration damage. This context is so foundational that all subsequent diagnostic logic depends on it, making it impossible to provide meaningful support without this information. The mandatory status ensures diagnostic relevance from the outset.

Is this a recurring issue that has happened before? This binary flag immediately distinguishes chronic infrastructure problems from one-time glitches, fundamentally altering the troubleshooting strategy and escalation path. Recurring issues often indicate hardware degradation, line damage, or ISP infrastructure problems requiring long-term solutions rather than quick fixes. Historical context prevents repetitive temporary solutions and justifies more intensive investigation or equipment replacement. Without this pattern information, support teams may apply inappropriate short-term fixes to long-term problems.

What is the current power light status on your router? The power light is the most basic hardware health indicator, revealing whether the router is receiving electricity, successfully booting, or experiencing critical failures. This visual check is the gateway to all subsequent diagnostics—if power is compromised, no network troubleshooting is relevant. Skipping this verification could lead to hours of unnecessary network diagnostics for a simple power supply issue. This fundamental hardware status is so critical that it must be mandatory to ensure diagnostic validity.

What is the current internet/WAN light status? This light directly indicates the router's ability to communicate with the Internet Service Provider, making it the single most important diagnostic indicator for internet connectivity issues. The status immediately determines whether the problem exists within the home network (local) or in the ISP's external infrastructure, directing the entire troubleshooting pathway. Without this crucial data point, support teams cannot differentiate between router configuration issues and ISP service outages, leading to inappropriate recommendations. The mandatory status ensures this critical boundary condition is always assessed.

Have you power cycled (unplugged and replugged) your router and modem? Power cycling resolves the vast majority of home internet issues by clearing caches, renewing IP addresses, and resetting hardware states, making verification of this step essential. This question ensures users don't skip the most effective first-line solution in favor of more complex (and often unnecessary) diagnostics. The conditional guidance provided for \"no\" responses transforms the form into an interactive troubleshooting tool, making this mandatory field a key component of user education. Without confirming this step, all subsequent diagnostics are built on an unstable foundation.

Do you have any devices that are still down after completing the table above? This quality gate ensures users don't prematurely conclude their troubleshooting efforts while devices remain offline, directing them toward advanced diagnostics or ISP escalation. It validates the effectiveness of the device-specific troubleshooting table and identifies persistent problems requiring different approaches. This boolean flag is critical for triage, separating resolved cases from those needing further intervention. Making this optional would allow users to abandon the process with unresolved issues, defeating the form's purpose.

Are all cables securely connected to your router, modem, and wall outlets? Physical connectivity is the foundation of network function, yet loose or disconnected cables are among the most common causes of internet outages. This question forces systematic inspection of the physical layer before proceeding to more complex software diagnostics, preventing wasted effort on misconfigured settings when the issue is simple disconnection. The mandatory status ensures this basic but critical check is never overlooked, as physical issues are often invisible to digital diagnostics.

Which specific cable connections have you inspected? This granular question ensures users perform a systematic physical inspection rather than a superficial check, as different cable types have distinct failure modes and criticality levels. The multiple-choice format creates an inspection checklist that systematically covers all potential physical failure points. Without mandatory verification of specific connections, users might overlook critical cables like the coaxial feed or fiber optic line. This thoroughness is essential for ruling out physical layer issues.

Can you see your Wi-Fi network name (SSID) in the available networks list on your devices? This question creates a critical diagnostic boundary, differentiating between Wi-Fi radio failures and internet connectivity problems. If the SSID is invisible, the issue is localized to the router's Wi-Fi function; if visible, the problem lies elsewhere. This distinction fundamentally determines whether to focus on wireless settings or internet pathway diagnostics. The mandatory status ensures this key symptom is captured, preventing misdiagnosis of Wi-Fi issues as ISP problems.

Can your devices connect to the Wi-Fi network but show 'No Internet' or 'Connected without internet'? This symptom precisely identifies the failure point—local network functionality versus internet reachability—directing troubleshooting toward router-to-modem connections versus device-to-router issues. This distinction is crucial for efficient problem resolution, as each path requires completely different diagnostic steps. Without capturing this specific symptom, support teams cannot effectively narrow the problem scope. The mandatory status ensures this critical diagnostic clue is never missed.

Please describe all troubleshooting steps you've already attempted, in the order you tried them: This narrative history prevents redundant troubleshooting efforts and reveals user behavior patterns that are invaluable for efficient support. Knowing what has already been attempted (and failed) directs subsequent steps and avoids frustrating users by repeating ineffective actions. This chronological log also helps identify potentially harmful actions like incorrect settings changes. The mandatory status ensures support teams have complete context, which is essential for effective escalation and prevents wasting time on already-tried solutions.