Signals Notebook: How to report a Signals Notebook issue

To reduce the number of interactions between support and administrators and users, we have created this article to inform them of the necessary information to provide.

However, admins/users should have gone through some steps before reporting an issue to support, which can be found in the KB article 'Troubleshooting Steps before support contact'.

• Subject: The issue description should be related to the ´problem reported.
• Steps to reproduce: The steps to reproduce an issue are very important since the support engineer might not be knowledgeable of what you are trying to accomplish, and they should always include the expected result and the observed result. 
• Tenant URL and Order number: The URL will give the support engineer information regarding your Signals notebook tenant, like the system's primary contact, users, and creation/expiration date. Also, the Order number is a factor in most of the issue reports.
• Organization: The name of your organization or the organization that owns the tenant is important in order to find details that will expedite case resolution.
• Images, Screenshots, and videos: Images, screenshots, and videos will give the support engineer a view of what and where, which is very important for issue comprehension.
• Logs: when reporting an issue related to a particular workflow that is now working as expected, that may or may not pop up a visible error, login delivers an incite into behind the scenes and are valuable when the issue needs to be escalated to a development team. If you do not have a reference on how to gather logs from your browser, please use the KB regarding How to obtain the network log in different browsers

Meeting availability: On some occasions, the support person will need to meet with you to help you resolve your issue or to gather more details. Teams is a tool that is used by our support team to set these meetings and assist our customers daily.