01 / The existing evidence
A mapping is not proof
The example shows the data path. Nothing was transferred on this page.
Field mapping
- Mapping
- Example
- Arrival in the workspace
- Not checked
Peak Helpdesk · Inside Peak One
One ticket.
Connected to your work.
In Peak One the person behind a request is the same as in Peak Chat or Peak Booking. Follow-ups become Peak Task tasks, visits become Peak Calendar appointments, replies go out through the mailbox connected in Peak Chat. Calls join through sipgate.
Start Peak Helpdesk in Peak OneExample mapping · no connection is made
Peak HelpdeskThe ticketPeak TaskThe taskPeak Task · Example mapping
One mapping in detail
01 / Peak HelpdeskTicket
02 / Fictional test value#123 Call-back about delivery
03 / Peak Task
Task referenceA readable field path as an example. No transfer.
View all 5 mappings
| Peak Helpdesk | Field in Peak Task |
|---|---|
| Ticket | Task reference |
| 사람 | 사람 |
| Assignee | Responsible |
| Promise | Due date |
| Next step | Task |
Example mapping
No transfer
No transfer
Nothing is connected on this page. You see the paths in the product.
One concrete targetPeak TaskArrival in the workspaceNot checked yet
Understand fields. Keep the source.
Peak TaskArrival in the workspaceNot checked yetThe mapping shows where the data goes. Only a test in your workspace shows what actually arrives.
02 / Shared objects
Connected because it is the same.
Inside Peak One the ticket needs no interface. Person, task and appointment are already there.
- 01 / The objects
The same person
Whoever writes is a person record in Peak One, with the customer record other apps know too.
What is shared?사람TaskAppointment - 02 / The channels
Tasks and appointments
Follow-ups in Peak Task and visits in Peak Calendar are linked to the ticket.
Where does it arrive?Email forwardingLive Chatsipgate - 03 / The follow-up
Mailbox and phone
Replies through Gmail or Outlook from Peak Chat, calls through your sipgate account. ⌘K finds every ticket.
What happens next?Peak TaskPeak CalendarPeak One Inbox
Trust needs clarity
What is connected, and what is not.
Field mapping02 / Your check
How emails arrive
Today emails arrive by forwarding to an address of your workspace. Pulling directly from Gmail without forwarding is planned.
- Account
- Not connected here
- Rights
- Roles in the workspace
03 / The clear limit
Planned channels named one by one
WhatsApp, Instagram and SMS in the helpdesk and a sipgate webhook are not available yet.
- Peak app
- Same object
- Forwarding
- Planned
The next step
A helpdesk that fits together with everything else.
Start Peak Helpdesk in Peak One and see how tickets, people, tasks and appointments belong together.
Start Peak Helpdesk in Peak One→Check in your workspace what actually arrived.
Frequently asked questions
Is the customer a separate record in the helpdesk?
No. The person is the same as in the other Peak One apps, not a copy.
Can I connect WhatsApp or SMS?
Not yet. WhatsApp, Instagram and SMS in the helpdesk are planned.
How does telephony work?
With your sipgate account you call from the ticket and take over calls as phone tickets.