Team & Spotlight

Use Inbox for internal requests

Find member requests and understand the difference between an internal request and a delivered chat message.

4 min read For All membersReviewed 2026-10-30

Before you start#

Step 1: Open Inbox#
Choose Inbox in the workspace. It is the private area for requests directed to you, including relevant Connect or Rescue flows.
An empty inbox can simply mean no requests have been received. It is not the same data as visitor submissions in Pipeline.
Step 2: Read the request before responding#
Review the sender information, message, and any optional social profiles or reply details supplied. A supplied profile or name is context, not an independently verified identity claim.
Do not assume a sender has access to your private contact details just because they can send an internal request.
Step 3: Choose the appropriate next action#
Use only the reply or contact options actually available in the request. If an option opens an external app, review the destination and complete the action there yourself.
Connect and Rescue Nudge are request forms rather than live chat. Do not expect a continuous chat thread or a confirmed delivery receipt unless the interface specifically provides one.
Step 4: Keep private information private#
Avoid forwarding screenshots that show other people's request text or contact details. If you need help with an error, redact private information and record the page and action that failed.
Review requests at a pace that works for you; there is no need to treat every activity prompt as an urgent obligation.

I cannot find a visitor's name here.: Check Pipeline for visitor submissions. Inbox is for internal requests, not a duplicate lead list.
I expected a chat conversation.: The current Connect and Rescue flows are private request forms. Use the available next action rather than expecting live chat.