Create a Helpdesk and choose its address
Create a new Helpdesk draft with the correct company identity and stable Humind address Follow a safe workflow, verify the customer-facing result, and isolate common problems.
Create a new Helpdesk draft with the correct company identity and stable Humind address This guide keeps the work focused on Helpdesk administration and provides a repeatable path that a new Humind user can follow without changing unrelated configuration.
A Humind Helpdesk is a published projection of eligible public Knowledge. It has its own address, content selection, languages, appearance, navigation, support destination, metadata, and immutable publication versions. Editing the configuration or Knowledge does not change the public site until a new coherent version is published.
Before you begin
Access: Knowledge and company settings write permissions are required for Helpdesk creation.
- Confirm the company and audience for the Helpdesk.
- Choose a recognizable name and stable address slug.
- Publish at least one eligible public Knowledge article before final publication.
Work in the smallest owning area described below and keep the current customer-facing state available while you prepare the change. Before clicking any final action, confirm the active company, Agent, store, language, and market shown in Humind. A missing control can indicate read-only access or a capability that is not configured for this company. In that case, record the intended task and ask an administrator to review the exact permission or dependency. Do not bypass the boundary by sharing an account, copying data into another area, or promising a capability that the workspace does not expose.
Step-by-step workflow
Confirm the scope and current state
Open Helpdesk and review existing centers before creating another one for the same audience.
- Confirm the active company and Agent before editing.
- Record the current state so the result can be compared after the change.
- Stop if the screen or permission does not match the intended task.
Prepare the change
Create the center, enter its customer-facing name and available Humind address, and confirm the generated public address belongs to the correct company.
- Use the smallest change that completes the customer task.
- Keep authoritative information in its owning source.
- Review labels, dates, language, and customer-visible wording before saving.
Save and allow required processing to finish
Review inherited Agent identity, languages, content mode, appearance, navigation, support, and search metadata while the center remains a private draft.
- Wait for the interface to confirm that the change is saved.
- If synchronization, indexing, or publication is required, wait for its final state.
- Reload the area and confirm the saved values persist.
Test the complete customer journey
Open the test area and review the complete candidate, but do not publish until content and customer-facing settings are coherent.
- Use a fresh session and a realistic customer scenario.
- Check desktop and mobile when the result appears on a storefront.
- Capture the exact failing step if the outcome differs from the expectation.
Important limits and operating notes
- A successful save confirms persistence, not every downstream synchronization or public update.
- Workspace permissions can hide an area or allow reading without allowing changes.
- Do not copy volatile catalog, account, or customer facts into narrative content as a workaround.
- Test only supported capabilities that are visible and configured for the current company.
- Keep changes in Helpdesk administration separate from unrelated Agent, Knowledge, catalog, Inbox, or Helpdesk work.
Verify the result
- The new Helpdesk appears only in the intended company.
- Its name and Humind address are correct and stable.
- It remains private until publication.
- The draft can see the intended eligible Knowledge content.
Keep a short record of what you tested, which customer scenario you used, and what changed. This makes later troubleshooting more precise and helps another teammate reproduce the result without relying on memory.
Troubleshooting
The desired address is rejected
Use the address rules shown in the form and choose a unique stable slug. Do not use a custom domain workflow that the interface marks unavailable.
The new center contains unexpected content
Review its all-public versus selected-content mode and Knowledge eligibility before publishing. Creating a Helpdesk does not copy or delete Knowledge.