Skip to main content
Find the message or symptom you see, then follow the fix. Headings use the exact text Parker shows where there is one.

Connections

Microsoft 365 shows “Partly connected”

What you see: In Settings > Connections, the Microsoft 365 row shows Partly connected, and its details say Calendar not connected. Why it happens: Microsoft grants mail and calendar access separately, so Parker asks for each one on its own. You’ve connected one but not the other. Fix: Select the Microsoft 365 row. In the Calendar row, select Connect Calendar, then sign in to Microsoft and approve the request. See Connect your mailbox.

Salesforce

Parker can’t see a record or field

Why it happens: Parker works under your own Salesforce permissions. If your profile, field-level security, or sharing rules hide something from you, Parker can’t see it either. Fix:
  1. Open the record in Salesforce yourself. If you can’t see it there, Parker can’t see it.
  2. Ask your Salesforce admin for access.
  3. Ask Parker again.
Being a Parker admin doesn’t change this. See Permissions.

Parker’s changes aren’t in Salesforce

Why it happens: Your Agent mode is Test, so changes are only simulated. An admin may also have turned on Org-wide test mode. Fix: Go to Settings > Connections and select the Salesforce row. Under How Parker works in Salesforce, check Agent mode. Only Live writes changes to Salesforce. See Connect Salesforce.

A “Stale” note under a reply

What you see: Under Notes on this reply, a Stale note, such as “25 of 25 records past your staleness limit”. Why it happens: The records Parker cited haven’t been edited in Salesforce for longer than your workspace’s threshold. Parker still read them live, but the data may be out of date in Salesforce itself. Fix: Check the records in Salesforce and update them if needed. Admins set the thresholds in Settings > Reply notes. See Oversight.

Email

”Who is this email for?”

What you see: Instead of a draft, a card says Parker couldn’t tell who the email is for, so nothing was drafted. Fix: Add the recipient’s email address, or say which lead the email is for. Then select Draft it, or ask again with the details. See Draft and send email.

”Compliance flagged issues — revise the draft first.”

Why it happens: The draft broke one of your workspace’s rules, so the send buttons are unavailable. Fix: Select the compliance result, such as 5 of 7 passed, to see which rule. Then revise the draft. See Draft and send email.

”Sending from Parker isn’t available for your organization yet.”

What you see: This note on an automation’s draft, in place of a send option. Fix: Select Open in Outlook to send, or send the draft from your Drafts folder as usual. See Review drafts and runs.

”Auto-send is paused”

What you see: In Settings > Agent > Autonomy, the Sender identity group shows Incomplete and Auto-send is paused. Why it happens: Parker needs complete legal sender details before it can send on its own. Until then, it drafts every reply for review. Fix: An admin completes the fields the page lists as missing. See Autonomy.

Routines

”Paused, so it won’t fire on schedule.”

Why it happens: The routine’s Enabled switch is off. Fix: Turn on the Enabled switch on the routine’s page. Or, on the Routines page, select Turn on. To run it once now, select Run now. See Routines.

Chat

”Parker AI can make mistakes. Check responses.”

What you see: This line under every answer. Why it happens: Parker can misread a question, pick the wrong record, or get a figure wrong. Fix: For figures that matter, select Sources in the chat header. Hover over a source marker to see the record, and select Open in Salesforce to check it there. See Chat overview.

Still stuck?

Ask your Parker admin, or see How do I get help? in the FAQ.

Connect your mailbox

Connect Outlook or Gmail.

Connect Salesforce

Your Salesforce login and Agent mode.

Review drafts and runs

See what your automations did.

Permissions

Why Parker can’t see some records.
Last modified on October 12, 2026