Přejít na obsah
Peak Atlas

Peak Helpdesk / Features

Every request
gets a clear answer.

Peak Helpdesk turns every customer request into a ticket with a number, status, assignee and deadline. Here you see each feature on a sample request and can change the subject right away.

Your first linebecomes visible.Local demo with sample data
See the features

Stays in this browser. No reply is sent, no ticket is created, nothing is saved automatically.

Ticket card · previewPreview reacts instantly
Peak HelpdeskLocal demo with sample data

Example: #1042 Delivery arrived damaged

The sample customer sends a photo of the crushed box. The ticket sits in “Needs reply” because the reply promise runs out soon.

Use sample data only.

Stays in this browser. No reply is sent, no ticket is created, nothing is saved automatically.

01 / The features

What do you need
first?

Filter by intake, handle, measure or on site & phone. Each card shows with a sample request which next step comes out of it.

09Sample requests

9 of 9 sample requests

  • HandleSelected

    One inbox, a clear order

    Needs reply, Mine, Unassigned, Waiting, Solved: exceptions come first.

    Inbox
    Request
    Example: #1042 Delivery arrived damaged
    01Customer name02E-mail03Message04Reply due
    More on this feature
  • IntakeSample draft

    E-mails become tickets

    Forward your support mailbox to your workspace's address.

    E-mail
    Request
    Example: invoice missing in the customer account
    01Customer name02E-mail03Message04Company
    More on this feature
  • IntakeSample draft

    Live Chat on your website

    Embed one script. Visitors need no account.

    Live Chat
    Request
    Example: delivery time question in the chat
    01Customer name02E-mail03Message
    More on this feature
  • MeasureSample draft

    Reply promises with a deadline

    Targets for first reply and resolution in hours. Due and overdue are visible.

    Deadlines
    Request
    Example: first reply within 4 hours
    01Customer name02E-mail03Message04Reply due
    More on this feature
  • HandleSample draft

    Follow-up tasks in Peak Task

    What remains after the reply becomes a task linked to the ticket.

    Tasks
    Request
    Example: order a spare part for #1051
    01Customer name02E-mail03Message04Reply due
    More on this feature
  • MeasureSample draft

    Performance over 7, 30, 90 days

    Median first reply, median resolution, share within promise, satisfaction, reasons.

    Výkon
    Request
    Example: the team's weekly view
    01Customer name02E-mail03Message
    More on this feature
  • On site & phoneSample draft

    Plan on-site visits

    Appointment in the technician's Peak Calendar, report, day route, van stock.

    Visit
    Request
    Example: heating fails, visit tomorrow
    01Customer name02E-mail03Message04Phone05Reply due
    More on this feature
  • On site & phoneSample draft

    Phone through sipgate

    Call from the ticket. A call can be taken over as a phone ticket.

    Phone
    Request
    Example: missed call in the morning
    01Customer name02E-mail03Message04Phone
    More on this feature
  • HandleSample draft

    History of every change

    Who changed status, assignee or priority, and when? Everything can be traced.

    History
    Request
    Example: handover between two shifts
    01Customer name02E-mail03Message
    More on this feature

Nine features that are built today. All requests and names are sample data.

02 / The selection

From intake
to the solved request.

A ticket does not end with a note, but with a reply to the customer or a clear next step in the team.

The library

The request comes
before the reply.

A request. The fitting details. A clear next step.

Currently in your previewInboxExample: #1042 Delivery arrived damaged
01 / Handle

Example: #1042 Delivery arrived damaged

The sample customer sends a photo of the crushed box. The ticket sits in “Needs reply” because the reply promise runs out soon.

Details4Reply due
02 / Intake

Example: invoice missing in the customer account

A forwarded e-mail becomes a ticket. The sender is one person record in Peak One, the same as in Chat and Booking.

Details4Company
03 / Intake

Example: delivery time question in the chat

A visitor asks in the chat when her order will arrive. The conversation lands as a ticket in the same inbox as every e-mail.

Details3Only the basic details
04 / Measure

Example: first reply within 4 hours

The ticket shows how much time is left until the promise. It counts calendar time; business hours are still planned.

Details4Reply due
05 / Handle

Example: order a spare part for #1051

The reply is out, but the spare part is still missing. The task in Peak Task stays linked to the ticket.

Details4Reply due
06 / Measure

Example: the team's weekly view

Which reasons come up most often, through which channel, on which day? All values come from your own tickets.

Details3Only the basic details
07 / On site & phone

Example: heating fails, visit tomorrow

The ticket becomes a visit in the technician's calendar. The route opens Google Maps, the van stock shows what needs refilling.

Details5Phone + Reply due
08 / On site & phone

Example: missed call in the morning

A missed call shows up in the call list. With one click it becomes a phone ticket, so nobody is forgotten.

Details4Phone
09 / Handle

Example: handover between two shifts

The early shift started the ticket, the late shift takes over. Notes and history show what has already happened.

Details3Only the basic details

Frequently asked questions

Through which channels do requests arrive?

By e-mail forwarding to your workspace's address, through your website's Live Chat and as a ticket entered by hand, for example after a call. WhatsApp, Instagram and SMS are planned.

Does Peak Helpdesk answer automatically?

No. Your team writes the replies; they go out through the Gmail or Outlook account connected in Peak Chat. An AI agent is planned and not built.

Can I set reply deadlines?

Yes. You set targets for first reply and resolution in hours. They count calendar time; business hours are planned.

More in Peak Helpdesk