Take in the request
New website requests should reach the team with goal, scope and contact person.
Your sentenceTake in a request
The intake agent should clarify what it is about and only ask what is needed.
Peak Chat · Agent team (planned)
Every agent has one job.
The decision stays with you.
A small team of AI agents is planned for Peak Chat: one takes in requests, one prepares meetings, one gathers details for an offer. They should hand over to each other and wait for your team before anything takes effect outside. There are no agents in Peak Chat today.
Planned feature · fixed examples · no agent runs
CONTEXT BEFORE ACTIONYour request.
Your request.
A proposal you can check.
02 / The visible proposal3 example steps
Take in a request
Why: Your team reads a prepared request instead of a long thread. You decide.
- 01Intake agent: asks for goal and scope
- 02Intake agent: sums up the request in three sentences
- 03Handover to your team: summary in the inbox for review
02 / How it should work
Take in. Prepare. Get approval.
Agents should prepare work. Anything with an outside effect is approved by a person.
02 / Visible proposal
Hand to the right agent
- 01Example step
Intake agent: asks for goal and scope
- 02Example step
Intake agent: sums up the request in three sentences
- 03Example step
Handover to your team: summary in the inbox for review
A person decides
Meetings, offers and outgoing messages should only take effect after your team approves.
Your review is still open.
These marks send nothing.Proposal and execution stay separate
Limits that stay.
Not available yet
The agent team is planned. Today Peak Chat holds no conversations on its own.
Your request→Fixed rule→Example steps
The sculpture illustrates the flow. It is not a product interface.
The sculpture illustrates the flow. It is not a product interface.Same rights as people
Agents should only be allowed what the roles in the workspace permit. AI runs only through the Peak AI Gateway.
- Execution
- Only with your approval
- Rights
- Roles in the workspace
No own calendar, no own CRM
Meetings stay in Peak Booking, people in Peak CRM. Chat is the conversation layer.
ProposalExecution
The next step
More hands in the conversation. One place for decisions.
Try the example flows above and see where your team approves.
View the example flowPeak Chat · Agent team (planned)What is needed?
Planned feature · fixed examples · no agent runs
Frequently asked questions
Does an agent commit to meetings or prices?
No. Agents are planned to prepare only. Peak Booking confirms meetings; your team writes offers.
What rights do agents have?
Planned: the same limits as roles in the workspace, never more.
Does this exist today?
No. Today there is the Peak Chat inbox; the agents are planned.