How do I get help?

Write to hello@scout-hq.io. These help articles are also reachable inside the product from Help & docs in your profile menu.

What to include

A good report saves a round trip. Include:

Your workspace name, and the email address you sign in with.
A link to the item, page, or connection you are asking about. Every view in Scout has its own address — copy it from the address bar.
When it happened, with a date and a time, and the time zone you are in. Scout's records are timestamped, and a time turns a search into a lookup.
What you expected and what happened instead, in one or two sentences.
Your browser and version, if the problem is visual or a control did not respond.
If the problem involves a notification or a Slack card, the timestamp and the reason shown in the diagnostics panel under Settings → Workspace → Notifications.

Never send a password, a verification code, an authorization code, or an API key. Nobody at Scout will ask you for one.
Do not paste supplier credentials into an email. Supplier credentials are handled inside Scout on your behalf; see Getting supplier credentials through Scout.
You do not need to forward customer mail to explain a problem. A link to the item and a timestamp is enough, and it keeps your customer's correspondence where it belongs.

A control that is missing is often a control your role does not have. See Roles.
A quiet Inbox or a thin brief usually traces back to a source Scout could not read. See A connection shows Warning or Error.
If you think you have found a security problem, say so in the subject line and describe it without including customer data.
Privacy requests — access, correction, deletion — go to the address named in the Privacy Policy. If you are an employee rather than your workspace's Owner, start with your Owner.
Billing questions come from the Owner of the workspace, since Admins do not see billing.