Walk in with the conversation, not a slide about it.
Klate is where you design what the agent does, so when the steering committee asks what happens on the hard paths, the answer is already on your screen.
Nothing for IT to install.
People at these companies design in Klate
Forty minutes in, the real questions start.
A conversation design is the agent’s behaviour, decided in writing before anyone builds: what it says, what it looks up, where it can go wrong and when it hands the customer to a person. The deck lands well until the sponsor asks what the agent does with an angry customer. The architecture slide has no answer in it, and the room turns to you.
From a vague mandate to an approved design.
- Step 1
Settle the ground rules
One Brief holds what the agent is for, what it never touches, who it talks to and when it escalates. Arguments that would surface in month three get had here, where they cost nothing.
- Step 2
Draft the conversation
Example turns on branching paths. A stakeholder reads what the agent does about a delayed order and finally has something concrete to react to.
- Step 3
Design the days it goes wrong
Fork any turn: the payment fails, the record is missing, the caller wants a person. Handing the customer to a person gets designed like any other ending.
- Step 4
Walk the room through it
Reviewers read and comment without paying for a seat, and every comment sits on the turn it is about.
- Step 5
Get it signed off
Your sponsor approves from a private link, with no account to create. The design locks, and the name, the time and the note stay on the record.
The four kinds of path.
Every path in a design carries one of four types, so you can see which kinds a design is still missing.
Happy
Everything works. The data comes back, the customer gets what they came for.
Edge
Unusual but legitimate. Two bookings under one name, a request in the wrong order, a detail the agent has to ask for twice.
Sad
The systems let you down. The lookup times out, nothing is available, the answer is no.
Adversarial
The customer pushes. A refund the policy rules out, a demand the agent has to refuse and still stay civil.
A per-project grid counts your scenarios against these four types. Each gap is the agenda for your next working session.
Before procurement asks.
You can be three designs deep before anyone raises a purchase order.
Start it yourself
Klate runs in a browser. The sign-up is the whole setup.
Stored in the EU
Designs, account data and uploaded files are all stored in the EU. AI requests go to US model providers; the security page has the rundown.
The bill stays small
When the project is funded, Pro covers one editing seat. Reviewers and approvers stay free.
Asked before the first design.
Do I need to know conversation design to use Klate?
No. The document asks the questions a conversation designer would ask, in the order they need answering: the agent’s goal, then the paths it can take, then the example turns, then the system call behind each answer. The first design Klate writes at sign-up shows you what a complete one looks like, and you edit from there.
Can I try it without going through procurement?
Yes. The Free plan is permanent and holds five designs. A card only comes into it if you move to Pro.
Can our consultants and the build vendor work in it too?
Yes. On paid plans, viewers and reviewers are free up to fifty per workspace, and approvers need no account at all. Editing takes a paid seat.
Isn’t this Figma or Word with extra steps?
Those leave the agent’s behaviour undecided until UAT. Klate holds the conversation, down to the system call behind each answer, with approval and version history built in.
Own the answer before the next review.
Klate opens to everyone soon. Send us a situation your agent should handle, and we will show you how it looks as a Klate design.