ข้ามไปยังเนื้อหา
Peak Atlas

Peak Chat · Automations (planned)

The conversation ends. The follow-up starts.
Nothing gets left behind.

Peak Chat is planned to suggest follow-up steps after a conversation: a task, a note to your team, an updated person record. Anything with an outside effect should only run after your approval. Today you can turn a message into a Peak task by hand.

Planned feature · fixed examples · nothing is executed

CONTEXT BEFORE ACTION

Your request.
A proposal you can check.

01 / Your request

93/600 · fixed examples, no model call

Peak Chat / Your flowSIMULATION
02 / The visible proposal3 example steps

Callback as a task

Why: A task is internal and reversible. It can be created by your rule without further approval.

  1. 01Trigger: client asks for a callback in the conversation
  2. 02Suggestion: task “Callback” linked to the conversation
  3. 03Execution: task in Peak Task, the person in charge sees it
Check all steps & reasons

02 / How it should work

Detect. Suggest. Let it run.

Automations should take over routine, never a decision.

01 / The starting point

Detect the event

When a client asks for a callback in the chat, a task should appear for the person in charge.
Your sentenceCallback as a task

For example: a conversation is closed, or a client asks to be called back.

02 / Visible proposal

Suggest a follow-up

Your request / Proposed flowSIMULATION
  1. 01
    Example step

    Trigger: client asks for a callback in the conversation

  2. 02
    Example step

    Suggestion: task “Callback” linked to the conversation

  3. 03
    Example step

    Execution: task in Peak Task, the person in charge sees it

03 / Your decision

Run by rule

Internal steps by your rule, anything outside only after approval. Run through Peak Automations.

Local review

Your review is still open.

These marks send nothing.

Proposal and execution stay separate

What holds today.

01 / Here in the browser

Today: by hand

In the inbox you can turn a message into a Peak task. Automatic follow-ups from the chat are planned.

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

No silent messages

Later, too, Peak Chat should never write to anyone on its own. Outgoing messages need approval.

Execution
Only with your approval
Rights
Roles in the workspace
03 / The limit

Fixed examples here

This page executes nothing and calls no model.

ProposalExecution

The next step

The conversation ends. The work does not.

Try the example flows above and check what would be triggered.

View the example flow
Peak Chat · Automations (planned)What happened?

Planned feature · fixed examples · nothing is executed

Frequently asked questions

What works today?

In the inbox you can turn a message into a task in Peak Task by hand.

Does Peak Chat message clients automatically?

No. Planned automations, too, should only have an outside effect with approval.

What should run the automations?

The plan is to run them through Peak Automations, not separate chat logic.