The reference layer that ties the rest of the docs together. Four pages: a symptom-first Common issues index, the Browsers and devices compatibility matrix, cross-cutting FAQ on pricing and migration and data, and Getting help on how to reach us. Feature-specific symptoms — POS register frozen, repair status wrong, an automation didn't fire — live on the troubleshooting section of each feature page; the index here points you to the right one rather than restating it.
A symptom-first index. Group the problem (can't sign in, data not syncing, printing, payment and billing, mobile-specific) and find the matching canonical-page troubleshooting section. The page itself does not restate feature-specific entries — it points you to the right docs page for the symptom you're seeing, plus a small handful of cross-section patterns that don't naturally live on a single feature page.
Which browsers Nexpura is tested on, what works on mobile, and the platform-specific quirks worth knowing — HEIC photo display in Chrome on Windows, Safari-on-iOS quirks where they apply, printer-driver gotchas that span surfaces. Reference content for the question 'will this work on the device my team uses?'
Cross-cutting Q&A only — pricing and plan questions, migration from your existing software, data ownership and export, account and security at the meta level, forward-looking 'is X coming?' questions, and how Nexpura compares to legacy jewellery systems framed honestly. Feature-specific questions live on each feature page's Common Questions section, not here.
How to reach the Nexpura team when the docs don't answer your question — which channel for which kind of issue, what to include in a support email so we can help fastest, and what response timing to expect. State what's verifiable today, no fabricated SLAs.