# Support that helps before something breaks > Support for rollout and daily work: Help Center, AI assistant, tickets, documentation, Downloads, and human channels when a case needs tracking. Source: https://reservation.business/en/platform/support · Language: en Business sits inside daily work, so help should start with a correct setup, clear documentation, fast first guidance, and a tracked path to a person when the case requires it. ## This matters when the team needs an organized launch and a clear path from self-serve help to a tracked case - The Help Center and documentation provide steps for setup, access, daily workflows, and more complex operating situations. - The AI assistant is a useful first step when someone needs orientation around a feature, setting, or workflow. - Tickets and human channels are for specific cases that need status, history, files, and follow-up. ## Good support starts before the first problem When software touches scheduling, front desk work, clients, payments, online booking, and reporting, the team needs to know how to start correctly and where to ask without routing every question through one internal expert. ## Set up the launch first, then use the right help path for each situation The strongest support model does not push every question into one generic conversation. It starts with the right foundation, gives teams self-serve resources, and keeps a clear escalation path when a person needs to follow the case. - At launch, the foundations are organized: roles, access, services, schedule, locations, online booking, payments, and the team's operating rules. - When the question is standard or procedural, the Help Center provides steps, examples, and links to current resources. - When someone is not sure where to start, the AI assistant gives fast first guidance for features, settings, and workflows. - When the issue is a specific problem, account, file, error, or longer case, a ticket keeps the conversation history and status together. - When the device or context requires it, the support area can also show additional resources such as phone, documentation, community channels, Viber, or Downloads. ## Each help channel should have a clear role The goal is not to create more places to ask questions. The goal is for each person to know which path fits the question in front of them. - **Help Center and documentation** — The starting point for instructions, first steps, setup, access, daily workflows, and deeper module guides. - **AI assistant for first guidance** — Useful when someone needs quick orientation around a feature, setting, workflow, or common point of confusion. - **Tickets for tracked cases** — The right path when there is a specific problem, a need for status, attachments, conversation history, or human follow-up. - **Access, Downloads, and human channels** — When the question involves installation, device setup, phone support, or community channels, those resources appear where they are available and relevant. ## A calmer go-live and less confusion when questions appear The team spends less time guessing where to ask. Owners do not become the only internal support layer, and more serious cases do not disappear into chats without history. - **Clearer onboarding for new roles** — Reception, managers, admins, and owners can start from different resources without every question passing through one person. - **Faster first guidance for daily questions** — Documentation and the AI assistant help when the question is about a feature, a setting, or a specific sequence of steps. - **Cleaner escalation to a person** — When the case is specific, a ticket keeps status, history, files, and next steps in one place. - **Less dependence on internal memory** — New people have somewhere to check, and repeated questions do not have to restart from zero. ## Frequently asked questions ### Is support only for technical problems? No. It also covers product orientation, documentation, AI first guidance, tickets for tracked cases, access help, and the available human support channels. ### When should we use the Help Center and when should we open a ticket? Use the Help Center for instructions, first steps, and self-serve checks. Use a ticket when there is a specific case that needs status, files, history, and human follow-up. ### Does the AI assistant replace a support person? No. It is for fast first guidance. When the topic is specific, account-related, or needs tracking, a ticket or another human channel is the better path. ### Can this help when onboarding a new team? Yes. This page is aimed at that exact situation: giving the team a clear starting point, access to documentation, and the right help path after real work begins. ### Are all support channels visible for every user? Not always. Some cards, channels, and download options depend on the device and the specific context. ## Related pages - [Help Center](https://help.reservation.studio/en/business/intro/) - [AI assistant](https://reservation.business/en/platform/ai-assistance) - [Access and apps](https://reservation.business/en/platform/access-apps) - [Data migration](https://reservation.business/en/data-migration) - [Book a demo](https://reservation.business/en/book-demo) ## Next step - [Book a rollout and support demo](https://reservation.business/en/book-demo) - [See the AI assistant](https://reservation.business/en/platform/ai-assistance)