How can we help?

During a support investigation, you may discover additional information or receive questions from the Polyosync Support team. Keeping relevant communication associated with the original request helps preserve context and avoid unnecessary duplication. How can I provide an update? 1. Open the relevant support request through the available ticket interface. 2. Review the existing information and any Support responses. 3. Use the available reply or update functionality, where supported. 4. Explain what has changed or what additional information you have discovered. 5. Submit the update. 6. Verify that the information appears in the request if the interface provides a conversation or activity history. What information is useful in a follow-up? Examples include: 1. A newly discovered error message. 2. The exact time of another failed execution. 3. A configuration change made after the original report. 4. A newly identified pattern. 5. Confirmation that the problem affects additional users. 6. The result of a troubleshooting step suggested by Support. 7. Confirmation that the issue is no longer occurring. Should I repeat the entire original report? Usually not. Reference the existing request and focus on the new information. Can I change the issue being investigated? If the new information concerns a completely unrelated problem, creating a separate ticket may be more appropriate. Keeping unrelated incidents separate helps maintain clear investigation records. What if Support requests confidential information? Do not send passwords, API keys, or authentication tokens. Ask for an appropriate secure method if sensitive diagnostic material is genuinely necessary. What if I accidentally submitted incorrect information? Provide a correction through the available communication channel. Clearly identify which previous statement was inaccurate. Can I reply after a ticket has been closed? That depends on the supported ticket lifecycle. If the interface does not permit additional replies, use the available process for reporting a recurring issue. Recommended practice Provide concise, factual updates and keep all relevant communication associated with the original issue whenever possible.