Yasa Help brings practical product guides and common questions together across the Yasa Ecosystem. Browse by service or search for the task you want to complete, then open the guide that matches your situation. The documentation is public, so you can read the relevant instructions before entering a private application.
A useful help journey starts with a specific question: how to find a message, review an order or understand a sign-in prompt. You can follow the relevant steps, check the expected result and provide clear context if something still needs attention. That makes support easier to begin and everyday work easier to continue.
Where Yasa Help fits in the ecosystem
Open the public Help home from the ecosystem menu or the normal Help address. Its product sections lead to current guides, while Common questions offers direct routes into frequently relevant workflows. The navigation guide explains how the shared menu and service-specific navigation work together.
Our Yasa Ecosystem overview explains the wider platform and the roles of its applications. Yasa Help focuses on the practical task inside that context. Use an introduction to understand the service, then use its current product instructions for the operation you actually need.
Choose a product in Yasa Help
Start with the service that owns the work. Account covers shared personal settings and sign-in, Hercules covers projects and tasks, and Midas covers billing records. Nexus concerns assigned hosting resources, while Webmail concerns the messages inside an existing hosted mailbox. Those distinctions help you choose a guide with the right prerequisites.
The service chooser guide also covers SkillJobber opportunities, PC Shop purchases, PC Builder hardware records and supported Pay flows. A product section narrows the questions to that application. Check its label before applying a familiar instruction to a different service with a similar-looking control.
For example, mailbox access and hosting administration involve different responsibilities. Our Nexus hosting guide explains assigned resources and invitation-based administration. A person reading email can need the mailbox’s own credentials without needing access to the infrastructure panel that manages it.
Search Yasa Help using the task’s own words
Enter a short, concrete term in Search help, then choose Search. Use the name of the thing you need to manage, such as mailbox, invoice or build. Read the product label, question and short explanation in each result before opening the most relevant guide.
The search results provide Explore by product to narrow the same question to a particular service. A search for mailbox can return both hosted-mail administration and everyday Webmail topics. Choose Webmail and search again to narrow the result list to the mailbox client’s guides.
That example shows why the product filter matters. Creating a hosted mailbox and finding an email already inside it share vocabulary, but they require different access and actions. If the results do not match your task, simplify the term, review the selected product and try the relevant product section directly.
Read the guide as a complete workflow
A typical guide sets out Before you start, What to do, What happens next and If something goes wrong. Read the prerequisites first so you know which identity, existing record or permission is needed. Then follow the part of the procedure that applies to your actual situation.
Use What happens next to decide what to inspect after the action. A saved setting should show its accepted value; an order or request has its own reference and state. Check the result in the service before repeating a submission that appeared slow or uncertain. The next visible screen matters more than simply having pressed a button.
The problem-solving section can help distinguish a missing prerequisite from a failed operation. A hidden folder, selected workspace or pending review can require a different next step from an incorrect password. Follow the displayed guidance and collect the relevant error instead of changing unrelated settings to see what happens.
Match an access question to the right account or resource
Public documentation can explain a workflow while the destination application still requires its normal access. Shared identity, an application’s connected session and permission for a workspace are separate parts of that journey. Our Account profile and security guide explains those roles.
If a service appears empty, check the intended identity, workspace and filters after loading finishes. If it asks for an invitation or verification, read that service’s current requirements. A Help page makes instructions available; it does not create a missing mailbox, company membership or infrastructure assignment.
The older account links guide is useful when a retired website page points toward a current service. Retain an existing project, order or invoice reference and follow the appropriate route. An old link changing is a reason to identify the right destination, rather than create another identity or repeat a payment.
A practical search example: finding a missing message
Imagine someone who can open a hosted mailbox but cannot see an expected email. They open Yasa Help, search mailbox and choose Webmail. Next, they read the guide about finding and organising messages, checking the active mailbox, folder and search scope before deciding the message was deleted.
Our Webmail workflow guide provides the wider context for those mailbox tasks. If the expected message remains missing, the person can follow the relevant troubleshooting guidance and provide the approximate time and non-sensitive error details through the approved support route.
This is an illustrative support journey. It does not require changing a hosting account or sending the same confidential message repeatedly. The useful outcome is a clearer description of the affected stage: entering the mailbox, finding an existing message, submitting a send or investigating recipient delivery.
Prepare a support request that explains the problem
Start with the service name and affected page address. Explain what you expected, what happened and approximately when. Add the relevant non-sensitive record reference and the steps you already tried. The contact guide explains the context that helps identify the right next step.
A concise description is easier to investigate than a general statement that everything is broken. For example, say which page opens, which action shows an error and whether an existing record still appears. Include only the screenshot or error details needed to understand that behaviour, removing unrelated personal or customer information.
Keep passwords, verification codes, private sign-in links and card information out of the message. If access is needed later, arrange it through the appropriate private process. Before submitting a second request, inspect the form result or existing conversation so one issue does not become several disconnected copies.
Use Yasa Help to find the appropriate support route
An application may provide an order conversation, billing route or another product-specific process. Use that route when the question concerns its existing record. For a website or service enquiry outside an app, the Yasa contact page provides a starting point, with the business context and intended outcome in the initial description.
For a new website or store, our website planning and launch guide explains how to shape a useful brief. The service request guide covers the information to prepare and the responsibilities, scope and cost that need to be agreed for the work.
For an urgent website problem, use the current urgent help instructions and identify the affected site, symptoms, start time and recent changes. Review the actual reply and proposed availability. Sending an enquiry gives context for assessment; it does not establish that a repair has started or a response time has been promised.
Keep documentation, agreements and confirmations in their roles
A guide explains how to use a service, while the actual order, membership or project agreement records its particular terms. Read the relevant service information before making a commitment. The privacy and terms guide explains where to find those documents in the footer and service flow.
For a change, cancellation or delivery concern, identify the existing record and the outcome you want reviewed. The service changes guide explains how to raise that request. Keep the actual confirmation available, because submitting a question and an accepted change have different recorded outcomes.
Keep useful guides within reach
Bookmark the actual product guide you use regularly, and return to its current page when a workflow or requirement is unclear. Check the application’s displayed controls alongside the instructions. If they differ materially, describe the page and step to support rather than assuming a familiar action still has the same effect.
Articles & guides provides broader reading and its own search and topic filters. Help has a separate search for product questions. The articles and feeds guide explains those routes and the public RSS feed. Choose the source that fits whether you need background knowledge, current instructions or help with your own record.
Start with one clear question
Use Yasa Help to identify the right service, find the relevant task and understand what to check afterward. If the instructions leave an unresolved question, keep the context specific and use the appropriate support route. This turns a general problem into a practical next step while preserving the information needed to investigate it.
Open the public help centre for current guides and common questions. If you still need assistance, contact Yasa with the service, page, expected result and observed problem. Keep private credentials and unrelated records out of the enquiry.
