01 / The existing evidence
Today: their own apps
Today you use forms, booking pages and calculators in their own Peak apps, not in the chat.
- Mapping
- Example
- Arrival in the workspace
- Not checked
Peak Chat · Mini-apps (planned)
Small Peak apps are planned to appear right inside the conversation: a calculator, a short form, a time picker. Peak Forms and Peak Booking exist today as their own apps. They are not embedded in the chat yet.
Watch the live demoPlanned feature · example mapping · no connection
Peak ChatThe question
CalculatorThe mini-appTaskA readable data path as an example. No transfer.
| Peak Chat | In the mini-app |
|---|---|
| Vraag | Task |
| Quantity | Input |
| Period | Input |
| Result | Card in the chat |
The mapping shows where the data goes. Only a test in your workspace shows what actually arrives.
02 / How it should work
A mini-app should do exactly one step and then lead back into the conversation.
When someone asks something that can be calculated or chosen, the fitting mini-app should be offered.
The mini-app appears as a card in the message, without leaving the page.
The result stays in the conversation. Only what the owning app confirms counts as booked or sent.
Trust needs clarity
01 / The existing evidence
Today you use forms, booking pages and calculators in their own Peak apps, not in the chat.
02 / Your check
The chat should never confirm a booking or payment itself. The app that owns it does.
03 / The clear limit
The mapping on this page is fictional. Nothing is calculated, sent or saved.
The next step
See in the live demo how conversations in Peak Chat are meant to look.
Watch the live demoCheck in your workspace what actually arrived.
No. Today you use forms in Peak Forms. Embedding them in the chat is planned.
No. A booking only counts once Peak Booking confirms it.
No, they are fictional examples. Nothing is calculated or saved.