Pular para o conteúdo
Peak Atlas

Peak Helpdesk · Workflows · Partly available

From the ticket
to the next clear step.

Today a ticket links the steps that follow: assign it, create a follow-up task in Peak Task, plan an on-site visit into the technician's Peak Calendar, set the status. Rules that assign on their own or insert saved replies are planned.

Local example · sample data · nothing is created

CONTEXT BEFORE ACTION

The request.
A flow you can check.

01 / The request

81/600 · fixed examples, no model call

Peak Helpdesk / Your flowEXAMPLE
02 / The visible proposal3 example steps

On-site visit

Why: a visit is a calendar appointment linked to the ticket. Everyone sees when and where it continues.

  1. 01Assignment: a technician takes it, with a message in her Peak One Inbox
  2. 02Visit: an appointment in the technician's Peak Calendar, route with a Google Maps link
  3. 03Afterwards: a visit report on the ticket, used parts taken from van stock
Check all steps & reasons

02 / Three building blocks

Assign. Hand on. Follow up.

A flow is good when everyone knows what to do and the ticket shows how far it is.

01 / The starting point

Assign

The heating in a customer's warehouse has failed; he needs someone on site today.
Your sentenceOn-site visit

One person takes the ticket. They get a message in the Peak One Inbox, and again on every customer reply.

02 / Visible proposal

Hand on

The request / Proposed flowLOCAL EXAMPLE
  1. 01
    Example step

    Assignment: a technician takes it, with a message in her Peak One Inbox

  2. 02
    Example step

    Visit: an appointment in the technician's Peak Calendar, route with a Google Maps link

  3. 03
    Example step

    Afterwards: a visit report on the ticket, used parts taken from van stock

03 / Your decision

Follow up

Status, promise and the history of every change sit in the ticket. Due and overdue promises are marked.

Local review

Your review is still open.

These marks send nothing.

Proposal and execution stay separate

What works today, and what is planned.

01 / Here in the browser

Available today

Assignment with an Inbox message, follow-up tasks in Peak Task, visit planning into Peak Calendar, a day route with a Google Maps link, van stock with a refill list.

The requestFixed ruleExample steps
The sculpture illustrates the flow. It is not a product interface.
02 / In the real product

Planned

Rules that assign tickets on their own, saved replies, merging tickets and approvals for refunds. Today your team does these steps by hand.

Execution
Only by your click
Rights
Roles in the workspace
03 / The limit

Nothing runs on its own

Peak Helpdesk never messages customers on its own and never decides for your team. This page creates nothing.

ProposalExecution

The next step

A ticket that knows the way.

Start Peak Helpdesk, assign your first ticket and create the follow-up right on the ticket.

See workflows in Peak Helpdesk
Peak Helpdesk · Workflows · Partly availableWho looks after it?

Local example · sample data · nothing is created

Frequently asked questions

What works today?

Assignment with an Inbox message, follow-ups in Peak Task, visit planning into the technician's calendar, day route and van stock.

Does Peak Helpdesk assign tickets automatically?

Not yet. Rules for automatic assignment and saved replies are planned. Today your team assigns.

Can a workflow trigger refunds?

No. Peak Helpdesk refunds nothing. Approvals for refunds are planned; the decision stays with your team.

More in Peak Helpdesk