Skip to main content

Contact Siteligent Support

Learn how to securely give Siteligent Support temporary access to your account for troubleshooting without sharing your passwords.

Written by Surya

When you need help with a website issue, you can contact Siteligent Support directly from your dashboard. Support tickets let you describe the problem, attach useful diagnostics, and keep the conversation available to your team.

Create a Support Ticket

To submit a support request:

  1. Log in to your Siteligent Dashboard.

  2. Open Support from the main navigation.

  3. Select a category for your request, such as Technical, Billing, General, Troubleshooting, or Feature Request.

  4. If the issue is related to a connected website, select the affected site.

  5. Choose a priority: Low, Medium, High, Urgent, Critical

  6. Add a clear subject and describe the issue.

  7. Attach any relevant screenshots, error logs, or other files.

  8. Submit the ticket.

Link the Affected Website

If your issue is related to a specific website, linking that site to the ticket helps the support team understand the environment involved.

Siteligent can associate relevant site information with the request, such as the PHP version, WordPress version, and active plugin count.

This can reduce the need to provide basic system information manually.

Choose the Right Priority

Use the priority level that best represents the impact of the issue.

Critical and Urgent should generally be reserved for situations such as a complete website outage or a serious security emergency.

For issues that do not immediately affect the availability or security of your site, Medium or High is usually more appropriate.

Track and Manage Your Tickets

After submitting a ticket, Siteligent gives it a unique Ticket Number that you can use to identify the request.

View Ticket History
​

Your ticket keeps a chronological record of the conversation and related system events. This gives you a single place to review previous messages and follow the progress of your support request.

Close a Resolved Ticket
​

Once the issue has been resolved, you can mark the ticket as Resolved.

You may also be asked to provide a quick satisfaction rating and optional feedback about your support experience.

Support Access for Troubleshooting

For issues that require deeper investigation, you can temporarily give the Siteligent Support team secure access to your account.

This can help our team investigate and resolve account-level and website-level issues without requiring you to share your Siteligent password or your WordPress site credentials.

Enable Support Access

You can enable Support Access from: Settings → Security → Support Access

Turn on the Enable Support Access toggle to allow the Siteligent Support team to access your account when troubleshooting is required. Support Access remains available for 7 days and automatically expires after that period.

What Support Access Helps With

Support Access allows our team to investigate issues that may not be possible to diagnose through a support ticket alone, including:

  • Account-level configuration issues

  • Siteligent dashboard issues

  • Website management problems

  • Site connection issues

  • Other technical issues that require access to your Siteligent account

This means you don't need to share your account password or website credentials with the support team.

Revoke Support Access

You remain in control of support access at all times.

  • To revoke access before it expires: Settings → Security → Support Access

  • Then disable the Support Access toggle.

Disabling the toggle immediately revokes active support access. Support Access will also automatically expire after the 7-day period.

Security

Support access is temporary and intended only for troubleshooting purposes. Support sessions are logged for security and accountability.

Before You Submit a Ticket

The more specific your support request is, the easier it is for the support team to investigate the issue.

Include:

  • The affected website and URL

  • The exact error message

  • Screenshots when relevant

  • Relevant PHP errors or debug logs

  • Steps to reproduce the problem

  • Recent changes made to the website or server

For example, instead of: "My backup failed." A more useful report would explain which site, when the backup failed, what error appeared, and whether anything was recently changed on the server.

This information can significantly reduce back-and-forth questions and help the support team investigate the issue faster.

Did this answer your question?