AGXLENS
MODULE 01 · SUPPORT
Technical Support
Home · Capture · Signal · Map · Vault — bug intake, release help, and local-data questions in one ticket flow.
WHAT WE COVER
Capture defects
Item list · logging · scales
Signal / Map issues
Grids · lag · association views
Vault & export
Backup · import · glossary
HOW TO LOG
Standard flow
Submit a ticket
Module · steps · iOS/app version
Triage P1–P4
Assign eng / QA
Fix & verify
Mitigate · patch · regress
Close & learn
Root cause · knowledge base
REALITY CHECK
Response targets
| LEVEL | SITUATION | FIRST RESPONSE |
|---|---|---|
| P1 | Production outage / data loss risk | 15 minutes |
| P2 | Critical module broken | 30 minutes |
| P3 | General defect | 4 hours |
| P4 | Technical question | 1 business day |
Excludes new feature builds and cross-system rewrites. 24/7 coverage requires a separate plan.
NOTES AND DISPLAY
FAQ
Is my Capture data uploaded?
Default design keeps items and snapshots on-device. No account and no cloud sync are required.
What if Vault export fails?
Note iOS/app version, file type, and whether storage permission was granted. Attach screenshots if possible.
Signal grids look empty
Log a few Capture snapshots first — association views need enough local samples.
Out of scope requests?
New modules and large refactors are estimated and scheduled separately.
INITIALIZE