01 / The existing evidence
No handover today
Peak Chat hands nothing to a client portal today. You use portals directly in their own app.
Mapping
- Mapping
- Example
- Arrival in the workspace
- Not checked
Peak Chat · Chat to client portal (planned)
The conversation becomes a project.
The portal keeps it in order.
Client portals exist in Peak One today as their own app. It is planned that a conversation in Peak Chat moves straight into the client's portal: request, files and next step land there instead of in the chat thread. This handover does not exist today.
Watch the live demoPlanned feature · example mapping · no connection
Peak ChatThe conversationClient portalThe portalClient portal · Example mapping
One mapping in detail
01 / Peak ChatClient
02 / Fictional test valueExample Ltd
03 / Client portal
ClientA readable data path as an example. No transfer.
View all 4 mappings
| Peak Chat | In the portal |
|---|---|
| Client | Client |
| Request | Request |
| Attachment | Files |
| Next step | Status |
Example mapping
No transfer
No transfer
The handover from chat to client portal is not available yet.
One concrete targetClient portalArrival in the workspaceNot checked yet
Understand fields. Keep the source.
Client portalArrival in the workspaceNot checked yetThe mapping shows where the data goes. Only a test in your workspace shows what actually arrives.
02 / How it should work
Clarify. Hand over. Keep working in the portal.
A chat is good for questions. Ongoing work needs a fixed place.
- 01 / Today
Clarify in the chat
The request and next step are clarified in the conversation.
What exists?Inbox in Peak ChatClient portals as their own appNo handover - 02 / Planned
Hand over to the portal
With your approval, request and files should land in the client's portal.
What should come?Handover to the portalFiles carried overLinked conversation - 03 / Limit
Work on there
Client and team see the status in the portal. The conversation stays linked.
Who decides?You approveClient sees only approved itemsNothing automatic
Trust needs clarity
Planned means: not here yet.
Mapping02 / Your check
Only with approval
Later, too, nothing should appear in a client's portal without your confirmation.
- Account
- Not connected here
- Rights
- Roles in the workspace
03 / The clear limit
One object, no copy
Client and request should stay the same objects as in Peak One, not a copy in the chat.
- Inbox
- Client portal
- Approval
- Planned
The next step
Questions in the chat. Work in the portal.
See in the live demo how conversations in Peak Chat are meant to continue.
Watch the live demo→Check in your workspace what actually arrived.
Frequently asked questions
Do client portals exist?
Yes, as their own app in Peak One. The handover from the chat is planned.
Does the client automatically see everything from the chat?
No. The plan is that only what you approve appears.
Is the client created twice?
No. Client and request should stay the same objects as everywhere in Peak One.