When you create an incident in SAM.gov, a ticket is created at the Federal Service Desk (FSD). The purpose of the FSD ticket is to allow communication between agents and you as they review your documentation.  Although the incident is managed through FSD.gov, ticket specialists from our entity validation service (EVS) team will review and process your incident. The EVS team will contact you through your ticket only.  

If you created an incident in SAM.gov while getting your entity information validated, here’s how you can check the status: 

• • Check your email.  An email with your FSD incident number was sent to your inbox when you created your incident. Keep this email to reference your incident, and respond promptly to any requests from the entity validation team handling your incident.
  • Look at My Incidents at FSD.gov. You can sign in to the Federal Service Desk (FSD) at FSD.gov using your SAM.gov username and password to view the incident and its status. Select My Incidents from the page menu. Select the incident number and description assigned to your ticket to see its status. The link to My Incidents will show a bubble with the number of incidents created.

• • Do not call or chat. Customer service agents do not have access to validation documents. If you need to contact a customer service agent about your issue, respond in the FSD ticket at FSD.gov. The best way to communicate with the agent handling your ticket is to open the entity validation incident as described above and add a message (KB0061458). You can only add a message to open incidents. If the state of the incident shows as Resolved, Canceled, or Closed, please contact the Federal Service Desk. 
  • Look at your Entities Workspace in SAM.gov. You can attach any further required documentation in your Workspace or view your original request. Read more about adding documentation to your entity validation incident (KB0057690).
  • Do not open another ticket for the same entity and validation information issue. This does not escalate your issue. It delays both the original ticket and the new duplicate ticket(s).