Warranty Inquiry

Administrative / non-technical issue: Warranty-date, coverage, support-timeline, expiration, extension-policy, or post-warranty option questions rather than primary hardware/software fault resolution.

Summary

Customers ask Support to verify purchase, quote, warranty-start/end, coverage level, support timeline/EOL, self-install or third-party-component policy, active-warranty RMA eligibility, failure-date reconsideration, credit/coverage boundaries, extension availability, post-warranty support scope, or out-of-warranty next steps. Support resolves these by checking internal records, correcting date math when needed, and routing covered failures to RMA or expired/billable needs to Sales/service paths (#21742, #22403, #42831, #43584, #44256, …and 10 more).

Frequency

• 17 tickets cite warranty inquiry handling: date lookups, coverage-level confirmation, support-timeline/EOL inquiry, self-install guidance, third-party component boundaries, expired replacement guidance, out-of-warranty support/replacement cost guidance, active-warranty triage/RMA, failure-date reconsideration, reseller credit, NAS-drive RMA intake, extension requests, and post-warranty support-scope questions (#21742, #22403, #42831, #43796, #44612, …and 10 more).

Common Causes

1. Missing or unclear purchase/warranty records. Customers may inherit systems, lack quote paperwork, fail to find warranty details online, or need date lookup across multiple GPU-server serials (#36062, #41444, #43525, #43584).
2. Coverage status affects replacement path. Failed parts require coverage checks before Support chooses warranty RMA, advanced replacement, failure-date reconsideration, credit, paid replacement, or billable service guidance (#42831, #42851, #43796, #44256, #44540, #44697).
3. Coverage level, term, or extension needs confirmation. Customers ask whether standard or advanced replacement coverage applies, when coverage ends, whether it can be extended after sale, or what remains when production systems near warranty end (#21742, #42831, #43584, #44612).
4. Policy questions go beyond dates. Customers ask whether self-installed GPUs/NVMe SSDs, institutional OS images, third-party components, or older-system support timelines/EOL affect warranty or support scope (#22403, #25251, #42563, #44071).

Diagnostic Steps

1. Normalize asset identifiers. Confirm system serial, order/quote number, organization, and affected component before answering warranty status (#36062, #41444, #42851, #43584).
2. Check records and date math. Use internal warranty, quote, ship-date, and order history to determine start/end dates, term, and coverage level; verify chronology before replying because an incorrect quote-vs-ship date or start year can create a visible contradiction (#21742, #41444, #43584, #43734).
3. Separate warranty status from replacement advice. If hardware is involved, confirm coverage first, verify when failure began near the boundary, gather fault evidence, then choose RMA intake or paid replacement/service quote guidance (#42851, #43796, #44256, #44540, #44697).
4. Answer policy scope directly. For self-install, customer OS image, third-party components, extensions, post-warranty, or EOL/support-timeline questions, state the boundary instead of treating the inquiry as ordinary break-fix (#22403, #25251, #42563, #44071, #44612).
5. Separate non-extendable warranty from post-warranty options. If extension is unavailable, clarify whether troubleshooting, per-incident support, maintenance advice, paid repair, hardware replacement, spare parts, vendor review, and EOL constraints remain possible (#44612).

Solutions

1. Provide exact dates and coverage level. Clear start/end dates and coverage terms can resolve pure inquiries in one touch or allow hardware triage to continue when a failure is also reported (#21742, #36062, #41444, #43525).
2. Proceed to RMA when coverage and evidence align. Covered NAS/drive failures moved to RMA intake after Support collected device/serial and shipping details or accepted evidence that failure began on the final warranty day (#43796, #44256).
3. Correct record/date mistakes transparently. If a public reply has inconsistent date math, explain the corrected warranty-start date and basis for expiration, including whether the date is based on quote issuance or actual ship date (#43584, #43734).
4. Route expired or billable needs appropriately. Expired failed components or physical service requests should shift to replacement purchase, billable onsite service, or Sales quote guidance (#42851, #44540, #44697).
5. Set extension and post-warranty expectations. Exxact does not provide warranty extensions after sale; post-warranty support may include troubleshooting/per-incident guidance, but repair, replacements, spare parts, timelines, and platform longevity are billable and dependent on vendor/component/EOL availability (#43584, #44612).
6. Clarify self-install and third-party boundaries. Customer-installed GPUs/NVMe SSDs or institutional Ubuntu images do not void hardware warranty by themselves; customer-caused damage, third-party components, and unsupported/uncertified software issues remain outside normal Exxact support scope (#22403, #42563, #44071).
7. State third-party replacement and credit boundaries. An active-warranty storage case remained supported through expiration except for drives bought outside Exxact, and management approved credit for the reseller's replacement-drive cost (#42831).

Edge Cases

• Inherited systems and missing purchase history: New administrators may reasonably question records without original quote/purchase paperwork (#43584).
• Date inconsistency can become the issue: Even correct final warranty status may require clear correction if a prior public reply had contradictory chronology (#43584).
• Pure inquiry may have no product fault: Warranty-date, coverage, self-install, support-timeline, and post-warranty tickets can preserve process knowledge without reusable hardware diagnosis (#21742, #25251, #36062, #41444, #44612).
• Active warranty does not guarantee replacement shipment: Parts shortage can turn in-warranty component failure into credit approval, including dispute over original part value vs current market replacement cost (#42831).
• Warranty-boundary wording matters: If logs show failure began during coverage, acknowledge the timeline and correction before RMA or paid-repair intake; however, an internal customer-side report before expiration may still be treated as out-of-warranty if the Exxact support inquiry was opened after expiration (#44256, #43734).

Related Issues

• RMA Workflow
• Defective Storage Drives
• Sales Quote Follow-up