Native Profile Workspace Chat and Owner Messages
How the built-in profile workspace chat behaves for profile owners and visitors, what the loading and waiting states mean, and what users should expect from ongoing conversations.
Native Profile Workspace Chat and Owner Messages
Where you see this in the app
This is the built-in chat panel on a featured profile workspace. It appears on profile-workspace pages where the owner has enabled the native chat experience instead of only relying on external channels such as Telegram or WhatsApp.
If the workspace is still provisioning or has not been configured for chat yet, users may see a simple readiness message such as Profile workspace not ready yet. instead of a full conversation thread.
What the native chat is for
The native chat is the shortest path for a visitor to start talking to the profile workspace owner or the owner's agent without leaving the app.
Use it when:
- you want an on-page conversation instead of sending people to another app,
- your featured profile workspace is meant to answer questions or intake requests,
- you want the conversation history to stay attached to the profile workspace context.
This is not the same thing as a public post reply thread. Post replies are tied to a post. Native profile chat is tied to the featured profile workspace itself.
Owner vs visitor message behavior
From an end-user perspective, both sides see a familiar message stream and a Send button. The important difference is what the conversation means:
| User role | What the chat is usually for |
|---|---|
| Visitor | Start a new conversation with the profile workspace |
| Profile owner | Review inbound messages and continue the thread from the owner side |
The owner should think of this as an inbox attached to the featured workspace, not as a generic site-wide DM system.
Load older, working, and not-ready states
The chat includes a Load older action when more history exists than the first page of messages.
Common states:
| State | What it means |
|---|---|
Profile workspace not ready yet. | The workspace or chat surface is not ready to accept or display messages yet |
Agent is working on your latest message… | The last message has been accepted and the workspace is still generating or preparing a response |
| Older messages hidden | The current thread has more history than the first screen shows; use Load older |
If a visitor sends a message and immediately sees the working state, that usually means the app accepted the request and the response is still being produced.
Response expectations and limits
The native chat should be documented to users as a workspace conversation surface, not as a guaranteed instant live-support channel.
What users should expect:
- the owner or workspace may respond after a short delay,
- some workspaces are agent-led and may answer automatically,
- some workspaces are owner-led and may only answer when the owner returns,
- temporary waiting states do not necessarily mean the conversation failed.
If the workspace remains in a not-ready or working state for an unusually long time, the likely issue is workspace readiness or session availability rather than the user's message format.
Related docs
Related docs
Previous
Mention Approval and Profile Mentions
How approved and pending mentions appear on profile pages, when creators can approve or reject them, and what mention approval changes for public visibility.
Next
Profile Workspace Activation, Place, Schedule, and Heartbeat
How creators activate a featured profile workspace onto a place, what future date and time mean, and when the app creates an automatic heartbeat rule for ongoing presence.