The agent holds your mailbox.
So the first thing to say is what it may touch, what it may never do, and how you stop it.
One gate, before every send and every booking
Nothing goes out and no meeting is booked until one gate has run and written down what it allowed or refused and which rule decided. That record sits in your workspace and you can read it. A seat's first week runs at the lowest autonomy, so a person presses for every letter.
One press stops everything
There is a stop button and it is the whole workspace's. It reaches letters and bookings now. It does not yet reach the paired browser lanes, and the button says so on itself rather than implying otherwise. We would rather write that sentence than let you discover it.
Your workspace is separated at the database
Every row belongs to a workspace and no route reads across workspaces. Suggestions that help your team invite each other store counts, never the content of a message. Anything learnt across workspaces stays switched off until a published floor is met, is anonymous and aggregate when it is on, and is visible to the workspaces that contribute to it.
What the agent reads, and what it writes
The agent reads the mailbox and calendar you connected, and writes from the seat whose name is on the letter. When you bring an old CRM, the grant reads and writes nothing back, not even a field definition. You approve the field map before anything is imported, so the boards that must never enter your workspace are unticked by a person rather than discovered afterwards.
Your rules per market, shown with their reasons
We do not tell you what is legal in your market and we never claim to. Each market carries its own card: the language, the legal tier, whether named contacts are on or off by default and why, the number of touches, the send window and the footer. The default is shown with its reason, you decide, and every override is written down with who, when and why.
Your data, on the way out as well as in
Every export carries the source and the as-of date of every enriched value, and every count carries the denominator behind it. What your team accumulates in Belda leaves with your team.
Where the data sits
The application and its database run in Frankfurt, inside the European Union.
Ask us the hard question.
Belda
The AI-native CRM that does the work and asks before it sends.
Belda, Copenhagen. The legal entity line is the Approver's own words and is not generated.