> ## Documentation Index
> Fetch the complete documentation index at: https://support.parker.work/llms.txt
> Use this file to discover all available pages before exploring further.

# Contact support

> Who to ask when something isn't working: your Parker admin, your Salesforce admin, or Parker support, and what to include so the first reply fixes it.

Email Parker support at [support@fieldko.com](mailto:support@fieldko.com). Before you do, check whether the problem is one your own admin can fix in a minute.

## Who to ask

| Ask | When |
| - | - |
| **Your Parker admin** | You need an account, a role change, or a feature turned on for your workspace. Something is admin-only in **Settings**. You want to know whether the Parker app, voice notes, or another channel is set up for your team. |
| **Your Salesforce admin** | Parker can't see a record or field you think you should see, or Salesforce refused a save because of a validation rule, required field, or permission. Parker works under your own Salesforce access, so the fix is in Salesforce. See [When Salesforce says no](https://support.parker.work/mobile/when-salesforce-says-no.md). |
| **Your IT team** | You can't sign in to the Parker web app with your work login, you can't install the Parker app on a work phone, or your mail provider blocks Parker from connecting. |
| **Parker support** | A message or feature isn't working the way this guide says, a linked channel has stopped replying for everyone, your admin needs a new workspace member added, or you've found an answer that looks wrong and can't explain it. |

If you aren't sure, start with your Parker admin. They can see settings and recent activity for the whole workspace, and they know whether support is already looking at it.

## What to include

Copy this into your email and fill in what you know. The more of it you include, the more likely the first reply solves it.

```text Support request theme={"system"}
Workspace name:
Channel (web app, Parker app, Teams, Messages, email, automation):
What I did:
What I expected:
What happened instead (exact message, if any):
When (date, time, and time zone):
What I've already tried:
Salesforce record (name or number), or the Parker chat or run, if relevant:
Screenshot attached (with other people's details covered): yes / no
```

> [!WARNING]
>
> Never send a password, a sign-in or linking code, an access token, or more of a Salesforce record than the problem needs. Support doesn't need any of them to help you, and a code is a secret: treat it like a password.

## Feedback is different from a problem

If Parker worked but the answer could have been better, tell Parker rather than support. In the Parker app, press and hold the answer and select **Helpful** or **Not helpful**. In the web app, select **Good response** or **Bad response** under the answer. Admins see this feedback, and it's the quickest way to shape how Parker answers your team.

Save support for something that's broken, missing, or wrong in a way you can't explain.

## When it's urgent

Nothing you do in chat reaches Salesforce or a customer without a person confirming it, and automations and routines only do what your admin's settings allow, so a stuck chat or a late update is an inconvenience, not an incident. If a message you confirmed saved the wrong thing, fix the record in Salesforce as you normally would, then tell support what Parker showed you before you confirmed. See [Confirm, edit, and correct](https://support.parker.work/mobile/confirm-and-correct.md).

## Related

> [card] [Troubleshooting](https://support.parker.work/reference/troubleshooting.md)
>
> Fixes for the messages Parker shows.

> [card] [FAQ](https://support.parker.work/reference/faq.md)
>
> Short answers to common questions.

> [card] [Permissions](https://support.parker.work/reference/permissions.md)
>
> What admins, members, and Parker support can each change.

> [card] [Supported features and availability](https://support.parker.work/reference/availability.md)
>
> What works on each channel, and what needs setup.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.