--- title: "How to open a ticket that support solves in the first reply" description: "Which channel to use in each situation, what to include in the ticket and why \"it's not working\" costs hours more than the missing information." url: "https://redhosting.com.br/en/base-de-conhecimento/como-abrir-um-chamado-que-o-suporte-resolve-de-primeira" type: "article" language: "en" category: "Other" published: "2026-09-02" translations: pt-BR: "https://redhosting.com.br/base-de-conhecimento/como-abrir-um-chamado-que-o-suporte-resolve-de-primeira.md" en: "https://redhosting.com.br/en/base-de-conhecimento/como-abrir-um-chamado-que-o-suporte-resolve-de-primeira.md" es: "https://redhosting.com.br/es/base-de-conhecimento/como-abrir-um-chamado-que-o-suporte-resolve-de-primeira.md" de: "https://redhosting.com.br/de/base-de-conhecimento/como-abrir-um-chamado-que-o-suporte-resolve-de-primeira.md" --- # How to open a ticket that support solves in the first reply Which channel to use in each situation, what to include in the ticket and why "it's not working" costs hours more than the missing information. - RedHosting knowledge base guide — category: Other - HTML page: https://redhosting.com.br/en/base-de-conhecimento/como-abrir-um-chamado-que-o-suporte-resolve-de-primeira - Published on: 2026-09-02 · Language: en Every ticket has two parts: finding out what happened and fixing it. The fix is usually quick; what eats time is the back-and-forth until support gathers information you already had in your first message. ## 1. Choosing the channel SituationChannelWhy Service down right nowWhatsApp **+55 11 98833-3902**The fastest, 24/7 Technical problem with a serviceTicket in the client areaIt's linked to the service and its history Invoice, cancellation, upgradeTicket in the client areaRequires account identification Question before buyingWhatsApp or the [contact page](/en/contato)No account needed How-to question, not urgent[Knowledge base](/en/base-de-conhecimento)Usually already answered Before opening any of them, check [redhosting.com.br/status](/status): scheduled maintenance and ongoing incidents appear there, with the team already working. ## 2. What to write Five items. With them, the first reply is usually the solution; without them, the first reply is a question. Every technical ticket ✓**Which service**, identified by IP, domain or name in the panel. An account with several services leaves no room for guessing. ✓**Since when**, with an approximate time. That's what lets us find the event in the log. ✓**The exact error message**, copied and pasted. "I got a connection error" and the actual error text lead to different places. ✓**What you've already tested**, and the result. It avoids repeating what's already been ruled out. ✓**What changed shortly before**: deploy, update, DNS change, new plugin. The cause is almost always here. 💡**Tip**: A screenshot helps, but it doesn't replace the error text: a message in an image can't be searched in the log. Send both when you can. ## 3. The difference in practice This costs a lotThis gets solved first time "My site went down""The site example.com has been returning error 500 since about 2 pm today. I updated a plugin at around 1:50 pm. The exact error is: *[pasted text]*. I've already tested from another network and in a private window." "The VPS won't connect""I can't connect via SSH to VPS 203.0.113.45 since last night. I get `Connection timed out`. Through the panel's VNC console the machine is on and responding. I didn't touch the firewall." "Email doesn't work""The account contact@example.com receives but doesn't send, since this morning. The error on my phone is *[text]*. I'm using port 465 with SSL. Sending works through webmail." Notice the pattern in the right-hand column: **what**, **since when**, **the exact error**, **what's been tested**. It's always the same structure. ## 4. Worth checking before you open one - **Test from another network** — over your phone's mobile data. If it works there, the problem is local. - **Private window**, to rule out cache and browser extensions. - **The panel** — machine status, console tab, disk and memory usage. - **The diagnostic checklist** in [My service is down: how to find the cause](/en/base-de-conhecimento/meu-servico-esta-fora-do-ar-como-descobrir-a-causa), which narrows down which layer is failing. None of this is mandatory — if the service is down and you don't know where to start, open the ticket anyway. These steps only shorten things when you're in a position to do them. ## 5. What support doesn't do for you Saying this up front avoids frustrated expectations in the middle of an emergency: - **Debug your application's code.** The team takes care of infrastructure, network and panels; an error inside your code is yours. - **Administer your VPS.** Root access means the system, firewall and programs are yours. Support helps with the machine, the network and the panel. - **Recover data that never had a copy** beyond the daily automatic backup. The split is explained in [Backups at RedHosting](/en/base-de-conhecimento/backup-o-que-e-automatico-e-o-que-e-responsabilidade-sua). ## Channels Tickets at [financeiro.redhosting.com.br](https://financeiro.redhosting.com.br) · WhatsApp **+55 11 98833-3902** · **suporte@redhosting.com.br** · [Discord](/discord). Support 24 hours a day, in Portuguese, English, Spanish and German. ## Frequently asked questions **Which channel is fastest when the service is down?** WhatsApp +55 11 98833-3902, 24 hours a day. For matters that need to stay linked to the service and its history, a ticket in the client area. **What do I need to include in the ticket?** Which service (IP or domain), since when with an approximate time, the exact error message copied and pasted, what you've already tested and what changed shortly before. **Does support fix errors in my code?** No. The team takes care of infrastructure, network and panels. Errors inside your application, and administering a VPS with root access, belong to whoever runs them. **Can I write the ticket in English?** Yes. Support answers in Portuguese, English, Spanish and German. ## Navigation — Other (article 7 of 9) - Previous article: [Backups at RedHosting: what's automatic and what's your responsibility](https://redhosting.com.br/en/base-de-conhecimento/backup-o-que-e-automatico-e-o-que-e-responsabilidade-sua.md) — https://redhosting.com.br/en/base-de-conhecimento/backup-o-que-e-automatico-e-o-que-e-responsabilidade-sua - Next article: [Welcome to the RedHosting Docs](https://redhosting.com.br/en/base-de-conhecimento/bem-vindo-ao-git-da-redhosting.md) — https://redhosting.com.br/en/base-de-conhecimento/bem-vindo-ao-git-da-redhosting - Back to the knowledge base: https://redhosting.com.br/en/base-de-conhecimento --- Need help with these steps? RedHosting's 24/7 support: suporte@redhosting.com.br · WhatsApp +55 11 98833-3902 · https://redhosting.com.br/discord More guides: https://redhosting.com.br/en/base-de-conhecimento.md