Messaging and calendars

Balt works inside Google Agenda.

You change nothing about Google Agenda. Balt connects to it, reads what it needs and hands back finished work.

ConnectionYour existing account, read and write

What you can ask it

What Balt does in Google Agenda

Drafts the replies

Drafts replies and follow-ups in Google Agenda and queues them, ready to clear in one pass.

Files what matters

Pulls what never made it into the ATS out of Google Agenda and writes it there.

Spots the signals

Spots an availability or a next step announced in a thread.

Keeps you in control

Never deletes a message and sends none without your approval.

How it works

Step 1
Connect once
You connect your Google Agenda account once, with the permissions you choose.
Step 2
Write your request
You write your request in Slack or Teams, in plain language, as you would to a colleague.
Step 3
Balt does the work
Balt does the work in Google Agenda and shows you anything outbound before it leaves.

Security and permissions

Balt reaches only what you open to it, and access is withdrawn in one move. None of your data trains a model, ours or a supplier’s. Every action is logged: you can say who did what, when, and on whose request.

Frequently asked questions

Does Balt replace Google Agenda?

No. Balt works inside Google Agenda with your existing account: nothing to migrate, nothing to relearn, and your teams keep using the tool as before.

What permissions does Balt need on Google Agenda?

Only the ones you grant. Read and write are set separately, and an access is withdrawn in one move without going through our support.

Does Balt act on its own in Google Agenda?

It acts alone on what stays internal and reversible. Anything leaving the company is shown to you before it goes, and a decision that closes a door stays human.

Is my Google Agenda data used to train a model?

No, contractually, including at downstream model providers. Your data stays yours and is hosted in the European Union.