Offline ticket file

Support Request

Create a structured JSON help request that can be saved locally and sent to SamhitaOffice support through the organisation’s approved channel.

This form is designed for air-gapped sites. It does not upload data, does not call a server, and does not require an internet connection. The user fills the issue details, generates a JSON file, and sends that file by official mail or approved support process.

Open request formHow it works

How Offline Support Works

Air-gapped offices cannot depend on live chat widgets, cloud forms, browser uploads, online diagnostics, or automatic crash submission. A support request therefore has to be treated like an office record: it must be structured, saved, reviewed, and then sent through an approved channel. This page creates a small JSON help file containing officer details, issue description, affected module, priority, workstation context, and reproduction steps.

Fill the form. Enter officer and office details, choose the affected module, describe the issue, and select priority.
Generate the JSON help file. The file is created locally in the browser session. No data is uploaded from this page.
Save the JSON file. Store it in a local support folder or approved removable media according to department instructions.
Mail or submit the JSON. Attach the generated file to official email or hand it to the authorised IT/support desk for transmission.
Keep a copy. Preserve the ticket file with the user’s support record until the issue is resolved.
Do not include confidential document content unless cleared. Describe symptoms, file type, visible error text, and steps. Do not paste classified, restricted, personal, financial, or sensitive record contents into the form unless the organisation has approved that disclosure.

Priority Guide

Priority should describe operational impact, not frustration level. A clear priority helps support staff triage requests fairly and respond to critical stoppages first.

HighWork is blocked for an office, critical record cannot open/save/export, repeated failure affects time-bound submission, or multiple users face the same stoppage.
MediumA normal workflow is affected but a workaround exists, one module behaves unexpectedly, a template/output needs review, or one user cannot complete a non-critical task.
LowGuidance request, cosmetic issue, training doubt, wording confusion, minor layout question, or improvement suggestion.
PriorityUse whenDo not use when
HighSave/export/open failure blocks official work or deadline-bound submission.The issue is only a design preference or general how-to question.
MediumWork continues with workaround but support review is required.The matter is a site-wide outage or complete application failure.
LowUser needs training guidance, clarification, or minor correction.The matter is preventing urgent file processing.

Offline Help Request Form

Fill all required fields, then generate the JSON help file. The generated file name uses a support ticket number so it can be tracked in email, phone follow-up, or local helpdesk records.

Officer and office details
Issue details
Document and workstation context
The JSON file does not attach documents. Mention only what may be sent separately through approved channels.

Generated ticket preview

The preview below appears after generation. Keep the ticket number visible in your email subject or support diary.

No ticket generated yet.

Mailing instruction

After generating the JSON, attach the saved file to the official support email or submit it through the approved IT/support channel. If the workstation has no mail client, move only the JSON file through approved removable media or local support desk procedure.

Suggested subject: SamhitaOffice Support Ticket - [Ticket ID]

What the JSON Contains

The help request file is designed to be useful without collecting unnecessary document content. It records the ticket number, time, officer contact details, department, affected module, priority, issue category, steps, expected result, actual result, file type, optional local path reference, workstation identifier, and browser user agent. It does not read documents from the computer and it does not attach the affected file.

JSON areaPurpose
Ticket identityCreates a traceable support reference for email subject, phone follow-up, and local support register.
Officer detailsAllows support staff to contact the correct user or office.
Issue detailsExplains the problem in a structured way so support does not have to guess.
Document contextIdentifies file type and safe reference information without uploading confidential files.
Workstation contextHelps technical staff identify site or computer-specific patterns.

Before Sending

  • Check that officer name, designation, department, and contact details are correct.
  • Select the right priority. High priority should be reserved for blocked official work or deadline-bound failure.
  • Describe steps clearly enough that support staff can reproduce the issue.
  • Do not paste confidential document contents into the issue description.
  • Attach the generated JSON file to the support email or submit it through the authorised support channel.
  • Keep a local copy of the generated JSON until the issue is closed.
Good support request habitA precise ticket saves time for the officer and the support team. The best ticket says what was attempted, what happened, what should have happened, whether it happens every time, and why the request has the selected priority.