How to contact support and find the reply

Sign in, open Support and choose Contact support. You can also open a new request directly.

Cannot sign in? Try the sign-in guide. If it does not help, email [email protected], preferably from your account’s email address. Name the site and explain what prevents you from signing in. The on-site form requires sign-in.

This illustrates the form and statuses. Fields depend on the category; picture uploads may not be available on your site.

For a complaint or appeal, choose what it concerns: a vacancy, event, article, company or profile. The form requires this choice. These categories also have an optional Page link field: paste the full address starting with https://. For other categories, include the link in your message.

For rejected content, start from the rejection screen. Choose Ask a person to look or Write to us about it to link the content automatically. See What to do after a rejection.

The initial Message needs 3–255 characters. Explain what you did, what happened instead, and what help you need.

When I save the company description, I get “Network error”. My connection works and I tried twice. Please help me save the changes.

Need more space? Submit the short description, then add details in the conversation. Each follow-up message can contain up to 2,000 characters.

If Choose a picture is available, attach a screenshot of the error. Use JPG, PNG, WebP or GIF up to 4 MB. If there is no upload button, describe the error in text. Hide other people’s details, full card numbers and unrelated personal information first.

Choose Send. The confirmation page means your request was created. If you attached a picture, check that it appears in the conversation; attach it again there if needed.

All requests are in Support. Those answered by the team come first, followed by requests waiting for the team, then closed ones. Use search or the status filter to find a request.

Answered does not necessarily mean unread: it identifies who wrote last.

New replies appear automatically while the conversation is open and connected. If an update is missing, check your connection and reopen the page. Type in the field at the bottom and choose Send. Keep follow-up questions in the same request.

If a team reply remains unread for about 15 minutes, the site sends a notification. This is not a promise to answer within 15 minutes: the clock starts after the team replies. Support notices are service notifications and bypass ordinary notification switches; external delivery depends on available channels. Always look for the answer in the conversation. See Notifications.

After the team replies, the site waits for your message. After roughly 24 hours without one, it asks whether you have more questions. After another 24 hours without new messages, the request closes automatically.

This timer does not close a request still waiting for the team’s first reply. Reading an answer alone does not continue the conversation: send a message if you need more help.

If everything is resolved, you can leave it. If a closed request still needs attention, create a new one and include the previous request’s number or link.

• Check the message length and hints beside the fields.
• Choose a page type for a complaint or appeal.
• If a picture will not upload, check its type and size or send text without it.
• After a connection error, keep a copy of your text and check the request list before submitting again to avoid duplicates.

Read about the site’s rules and documents in plain language.