Detect the event
When a client asks for a callback in the chat, a task should appear for the person in charge.
For example: a conversation is closed, or a client asks to be called back.
Peak Chat · Automations (planned)
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
Why: A task is internal and reversible. It can be created by your rule without further approval.
02 / How it should work
Automations should take over routine, never a decision.
When a client asks for a callback in the chat, a task should appear for the person in charge.
For example: a conversation is closed, or a client asks to be called back.
Trigger: client asks for a callback in the conversation
Suggestion: task “Callback” linked to the conversation
Execution: task in Peak Task, the person in charge sees it
Internal steps by your rule, anything outside only after approval. Run through Peak Automations.
Your review is still open.
These marks send nothing.Proposal and execution stay separate
In the inbox you can turn a message into a Peak task. Automatic follow-ups from the chat are planned.
Later, too, Peak Chat should never write to anyone on its own. Outgoing messages need approval.
This page executes nothing and calls no model.
The next step
Try the example flows above and check what would be triggered.
View the example flowPlanned feature · fixed examples · nothing is executed
In the inbox you can turn a message into a task in Peak Task by hand.
No. Planned automations, too, should only have an outside effect with approval.
The plan is to run them through Peak Automations, not separate chat logic.