Help and Resources

Help and resources helps you choose the right page before opening a help request. Use this page when you are stuck, when search did not find the answer, or when you need to report a problem with useful context.

Good help requests start with context: the item name, the page, the visible status, and the last action you tried.

Start Here If

Use this page when:

• you know something is wrong but not which page owns it;
• search did not give a confident answer;
• you need a product help link for a visible state;
• you are preparing a help request and need the right context.

At a Glance

What you know	First route
Only the symptom	Decision Tree
Issue type is known	Common Issues
Product state needs a docs target	Product Help Links
You need to report it	Collect the help request packet on this page.

How Can We Help?

Something looks wrong Start with the visible symptom and choose the first page to check.

A button is locked Check plan limits, upgrade required messages, and current usage.

I cannot connect Check the client, hub choice, connection file, and live state.

Access is denied Review linked clients, allowed actions, and blocked actions.

Something is not showing Check stale, missing, warning, filters, and refresh state.

Security blocked me Review two-step sign-in, recovery codes, active browsers, and connection file access.

Start with the symptom, open the owner page, and collect a small help packet if the issue remains.

Fast Help Routes

I only know the symptom Use the decision tree to choose the first page to check.

I know the issue type Use common issues for client, permissions, billing, runtime, and Live Map checks.

I need the owner page Use the glossary owner map to find the page that explains a term.

I need a product help link Use stable targets for locked actions, warnings, empty states, and support handoffs.

Start with the Owning Surface

Hubs

Start here for hub visibility, address, health, or public listing questions.

Skills

Start here for skill install, update, or settings questions.

Runtime

Start here for language, location, speech, blocked skills, or live skill status questions.

Clients

Start here for client connection files, live status, pause, or restore questions.

Permissions

Start here for allowed actions, blocked actions, and linked client questions.

Live Map

Start here for live connection, stale clients, and missing client questions.

Billing

Start here for limits, hub addresses, help options, and paid skill questions.

Profile

Start here for two-step sign-in, recovery codes, active browsers, and avatar questions.

Account and Plan Context

1. Use Profile for personal security and active browsers.
2. Use Billing for plan limits, private skill setups, hub addresses, paid skills, and help options.
3. Use Help and resources when you are not sure which page owns the question.

Common Issue Routing

If something looks wrong but you do not know whether it is setup, permissions, plan, or live status, start with Troubleshooting Decision Tree. It walks from symptom to the right page.

Open decision tree Open common issues

Tip

When reporting an issue, include the item name, the page where you saw the issue, the visible status label, and the time you last refreshed the page.

Before Asking for Help

Check these first:

• Dashboard for the workspace summary;
• the page that owns the item, such as Hubs, Clients, Permissions, Skills, Runtime, Billing, or Profile;
• Live Map when the issue is connection state;
• Common Issues when you are not sure where the symptom belongs.

Help Request Packet

If the issue still needs help, collect:

1. Page: the page where you saw the issue.
2. Item name: the hub, client, permission set, skill set, or plan item involved.
3. Visible status: the exact status, warning, locked button, or message.
4. Last check: the last action you tried and when you refreshed.
5. Expected result: what you thought should happen.

Copy help packet

Page:
Item name:
Visible status:
Last check:
Expected result:
What changed recently:

This packet keeps support focused on the next check instead of re-discovering basic context.