Disclaimer: This works only if the technology and its users can operate flawlessly! (Just kidding)
Until then when the day comes when, at some point or another, you’ll most likely require reporting to the SharePoint Admin or Technical Team. Despite the team you use, the users need the same kind of information available to every user to troubleshoot the problem. The more specific you can depict the issue, the snappier your users can respond and less you need to pay for the fixes.
Here’s some of the areas that you should consider including when you showcase your issue to the support team:
Office 365, SharePoint Server 2016, SharePoint Server 2013, and SharePoint Server 2010 all have diverse features, functionality and design structure. Ensure that the developer working on your support ticket will instantly know which server they're working on.
Give URLs to all sites, libraries, lists or webpages that might be pertinent.
If the issue does not show up immediately at the URL, describe the steps that requires to be followed to uncover the issue.
If there's a layout or design issue, knowing the client's program specs can be useful.
What you see isn’t really what other users will see. It is recommended to provide screenshots of the layout of alert messages.
This is a common issue faced in SharePoint. If only few of your users are facing such issues, find out their department and permission levels so that you can compare with other account properties to identify the root cause of the issue.
If the issue has occurred due to server updates/system changes, make sure to record the time of when the update was done.
If you're working on projects and meeting an important due date, inform the support team. If there are times where the intranet should not be reset, you must intimate them as well.
For emergency situations that could go outside of the normal working hours, inform the support team on how and when they'll need to be informed of the outcome.