Naar de inhoud springen

Peak Helpdesk · Follow-through · Planned

What you promise
does not get lost.

Planned: Peak Helpdesk recognises promises in your replies, such as a callback on Friday, and keeps track of them as follow-up steps until they are done. Today you create follow-up tasks in Peak Task yourself, linked to the ticket, and the “waiting” queue shows open cases. The demo is a concept with sample data.

Planned feature · concept demo · sample data

CONTEXT BEFORE ACTION

Your request.
A flow you can check.

01 / Your request

70/600 · fixed examples, no model call

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

Callback promised

Why: A callback is a promise with a time. Without a task it depends on one person's memory.

  1. 01Promise: callback on Friday recognised, Friday as a sample date
  2. 02Follow-up: task “call Alex back” in Peak Task, linked to the ticket
  3. 03Reminder: to you on Friday morning, call through sipgate from the ticket
Check all steps & reasons

02 / How follow-through is meant to work

Recognise the promise. Plan. Remind.

Good follow-through reminds your team, not the customer. Outside contact stays your click.

01 / The starting point

Recognise the promise

I promised Alex Example on the phone that I would call back on Friday.
Your sentenceCallback promised

Planned: the date and promise in your reply show up as a proposal, never stored silently.

02 / Visible proposal

Create follow-ups

Your request / Proposed flowCONCEPT · SAMPLE DATA
  1. 01
    Example step

    Promise: callback on Friday recognised, Friday as a sample date

  2. 02
    Example step

    Follow-up: task “call Alex back” in Peak Task, linked to the ticket

  3. 03
    Example step

    Reminder: to you on Friday morning, call through sipgate from the ticket

03 / Your decision

Remind in time

Today: customer replies notify in the Peak One Inbox. Planned: a reminder before the promise is due.

Local review

Your review is still open.

These marks send nothing.

Proposal and execution stay separate

Planned means: not built yet.

01 / Here in the browser

What exists today

Follow-up tasks in Peak Task on the ticket, the “waiting” queue, reply and resolution promises with a due time and notifications in the Peak One Inbox.

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

What is planned

Recognising promises automatically and following through on its own does not exist yet. This page shows a concept.

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

No contact without you

Even as planned, Peak Helpdesk does not write to customers on its own. It reminds your team; a person sends the message.

ProposalExecution

The next step

Your first follow-up task, right on the ticket.

Start Peak Helpdesk and add a follow-up task in Peak Task to your first ticket.

Start Peak Helpdesk for free
Peak Helpdesk · Follow-through · PlannedWhat did you promise?

Planned feature · concept demo · sample data

Frequently asked questions

Does Peak Helpdesk recognise promises itself yet?

No, that is planned. Today you create follow-up tasks in Peak Task yourself, linked to the ticket.

How do I keep track of waiting cases?

Through the “waiting” queue and the due times of reply and resolution promises.

Does Peak Helpdesk send reminders to customers?

No. Peak Helpdesk never writes to customers on its own. It is your team that gets reminded.