How can we help?

A well-documented support request helps Polyosync Support understand the issue, assess its operational impact, and identify the appropriate investigation steps. You do not need to perform advanced technical troubleshooting to submit a useful report. The most important information is what happened, when it happened, and what result you expected. Recommended information to include 1. A clear issue summary. Describe the problem in one or two sentences. Example: "An automation execution failed while attempting to update a connected CRM record." 2. The affected feature. Identify the relevant AI Employee, automation, workflow, business process, integration, or workspace function. 3. The expected behavior. Explain what the operation should have done. 4. The actual behavior. Describe what occurred instead. 5. The error message. Include the exact visible message or status code when available. 6. The date and time. Provide the approximate timestamp and timezone. 7. Execution references. Include a relevant execution, run, or ticket identifier if one is available. 8. Steps to reproduce. Explain how the issue occurred, provided the steps can be repeated safely. 9. Business impact. Describe whether the problem affects one user, multiple users, customer-facing operations, or business-critical processes. 10. Recent changes. Mention relevant changes to permissions, integrations, workflow configuration, or account settings. Example of a useful report "An autonomous workflow failed during an external CRM update at approximately 14:30 UTC. The workflow was expected to update an existing lead record, but the execution shows an error during the integration step. Other workflows appear unaffected. The affected execution reference is available in the workflow history." What should I never include? Do not include: - Passwords. - API keys. - Access tokens. - Private authentication credentials. - Unnecessary personal information. - Unredacted confidential customer records. - Sensitive business documents unrelated to the issue. Can I attach screenshots? Yes, where the support interface permits attachments. Remove or obscure sensitive information before submitting them. What if I suspect a security incident? Clearly identify the security concern and report it promptly. Do not delay reporting while attempting to gather extensive technical evidence. What happens after submission? The request can be assessed using the information provided, and additional details may be requested if necessary. Response handling and any contractual service commitments depend on the support arrangements applicable to your account. Final recommendation Provide enough information to reproduce or investigate the problem, but share only the minimum sensitive information necessary. Clear diagnostic context is more valuable than a large collection of unrelated screenshots or logs.