Aller au contenu

Peak Helpdesk / For coaching

The session went well.The follow-up question got lost.

In coaching, questions come between sessions: reschedule, access to materials, an invoice. In Peak Helpdesk each one becomes a ticket. The client is the same person record as in Peak Booking, so you see appointments and requests together.

Put the goal into words. Add perspectives and timing right below.

Local draft · no product activation
See the coaching example

Try it on a local sample question.

The question between two sessions.

Appointment / access / invoice

01Intake02Context03Close
Working example / client question

What happens between sessions.

Intake
E-mail, website chat or a noted call.
Context
Appointments and tickets on the same person record.
Close
Solved, satisfaction 1–5 recorded by the team.
Editorial structure sketch · sample data · not the product interface

Your client question in three answers

What does the client need?

Fill in the example with a made-up question. You see what a ticket should capture. Nothing is saved or sent.

Local working example · nothing is saved or sent. Please don't enter personal data.

Peak Helpdesk / Start noteLOCAL DRAFT
01 / Your thoughts
02 / Your start noteLocal preview

Three questions. One clear reply.

Draft · not yet put together

The question
Still open
The owner
Still open
The next step
Still open
Your input appears here right away. With “View the start note” you check the three details locally.

From follow-up question to reply

One question. No digging through the inbox.

The order makes sure no client question sits unanswered between two sessions.

  1. 01Capture

    Capture the question.

    Intake

    E-mail, website chat or a noted call.

    Forwarded e-mails and the Live Chat become tickets. A question on the phone you capture yourself in a few fields.

    Message → ticket
  2. 02Understand

    See the context.

    Context

    Appointments and tickets on the same person record.

    Earlier tickets sit on the person record. The history shows every change to the ticket.

    Ticket → history
  3. 03Reply

    From your own mailbox.

    Close

    Solved, satisfaction 1–5 recorded by the team.

    The reply goes out with your signature through the account connected in Peak Chat. A new appointment is made in Peak Booking.

    Sample artifact → reply note

The next proof is the product

Forward your coaching address.

In Peak Helpdesk follow-up questions land as tickets with a response target. “Needs reply” shows you each morning what comes first.

Start with Peak Helpdesk

Peak Helpdesk / Your next step

The session counts. So does the follow-up.

Try the example with the question that's been waiting for a reply since the last session.

See the coaching example
Local working example

More time for the session.

Solved, satisfaction 1–5 recorded by the team.

Frequently asked questions

Is it worth it if I work alone?

Yes, when requests come through several channels. The Reply due view shows who needs an answer first.

Can clients move sessions themselves?

That runs through Peak Booking. In the helpdesk you answer the request about it and close the ticket.

Which address do replies come from?

From the Gmail or Outlook account connected in Peak Chat. If nothing could be sent, the ticket says so.