Include the page you were on, the action you took, and the exact error message if one appeared. That small amount of context is usually the difference between one response and three.
support@operationmos.comCommon questions
Accessibility support
We want Operation MOS to work with keyboard navigation, screen readers, browser zoom, and reduced-motion settings. If a barrier keeps you from using a page or completing a task, tell us what you were trying to do and which browser or assistive technology you were using. Do not send a DD214, SSN, medical record, or other sensitive document with the request.
Request accessibility supportWhat to include
The goal is not to write a polished ticket. The goal is to remove the guesswork so the issue can be recreated and fixed.
The page or workflow you were using.
The action you took immediately before the issue.
The exact error message, if one appeared.
Whether this is blocking access, export, or account changes.
Support lanes
Most requests fall into one of these lanes. If you are blocked, say that clearly up front. It changes the priority immediately.
Account access
Password resets, login failures, verification issues, and access problems for veterans, counselors, or admins.
Résumé workflow
Broken import steps, generation issues, export defects, or builder states that do not save correctly.
Privacy requests
Deletion requests, data questions, consent issues, and support follow-up that requires account review.
Need more product context before writing support? The About page explains what Operation MOS is built to do.