Connect
Fathom for your calls, Cal.com for your calendar, HubSpot for your pipeline, Brevo to send. Every permission is read only, except the one that sends a message you approved yourself.
calendar readpipeline readpublic APIemail send
They prep, they write, they chase.
You sign.
Five agents read your calls, your calendar, your pipeline and your own playbook. Everything they write lands in one queue. Nothing goes out without you.
Five agents in the catalogue. Not one of them holds the send button. The rule lives in the code, not in a sales promise.
Every agent reads your playbook first: ICP, positioning, call scripts, customer stories. That is why the text sounds like you.
Three moves,
the last one is yours
Three to twenty people. A CRM nobody spent six months configuring. Calls recorded, notes taken, and follow-ups that slip because the week moved on. That gap is where the agents work.
Write
The agent pulls your positioning and your real emails from the context before it writes a line. Post-Call Follow-up runs at noon and 5pm on weekdays, CRM Watchdog at 8:30.
knowledge searchread meetingcreate draft
Sign
The draft arrives with its trace: what was read, which tools answered, what the run cost. You edit, you send, or you bin it.
review queuemanual sending
Watch it
work
One real run, from click to send: the agent runs, the draft waits for you, you edit, you send.
Kalio › AgentsSearch...⌘K?
Agents
Each agent reads your calls and your context, then writes a draft. None of them ever sends anything.
Reads the notes from recent calls and writes the follow-up, in the founder's voice.
Run nowSee the workflow
Marc,
You told me half your follow-ups go out on Friday evening, when nobody reads them any more.
We can move them to Tuesday morning and see what three weeks of that gives.
You told me half your follow-ups go out on Friday evening, when nobody reads them any more.
We can move them to Tuesday morning and see what three weeks of that gives.
1 draft waiting for you.
Post-Call Follow-upCRM WatchdogDiscovery PrepBuying Signal ScraperProposal Follow-up
Every draft comes
with its receipt
You do not have to take our word for it. Open any draft and you get the log of the run that wrote it: which meetings were opened, what was looked up in your context, what came back, and what it cost.
Kalio · AgentPost-Call Follow-up12:00:04 · 1,240 tokens
| Action | What came back |
|---|---|
| Read recent callsFathom | 3 calls, 1 with no follow-up |
| Open the meetingFathom | northbase · 42 min · 6 action items |
| Search your GTM contextNotion | founder voice, Lumen story |
| Write a draftDrafts | 1 draft, waiting for you |
In plain words: the agent read 3 recent calls, found one with no follow-up, checked your voice and your customer stories, wrote one draft, and stopped there.
Example for Kalio: only the steps that use the connectors on this account. Not an exhaustive list of what agents can do.
Five agents,
one rule
One for each moment of the cycle, from the signal you never saw to the deal going quiet. Every one of them writes a draft, and not one holds the send button.
Buying Signal Scraper
Looks for the buying signals of your ICP: a role being hired for, a raise, a change at the top, the trigger event you sell against. Writes up to five briefs: company, signal, angle. Never an email ready to send, because it knows a company, not an address.
- Runs
- Weekdays at 07:00
- Time back
- 2 to 4 hours of prospecting a week
Discovery Prep
Reads the next days of bookings, digs into the company, the persona and the likely pain, then leaves you five questions in the order to ask them.
- Runs
- Weekdays at 08:00
- Time back
- 20 to 30 minutes per call
Post-Call Follow-up
Reads the recap, writes the follow-up in your voice, and picks the customer story that genuinely matches the profile.
- Runs
- Weekdays at 12:00 and 17:00
- Time back
- 30 to 45 minutes per call
Proposal Follow-up and Offer Builder
Takes the recap and your own offer template, drops in the prospect's numbers and the scenario that fits them. Still to be built in the product.
- Runs
- Weekdays at 12:00 and 17:00
- Time back
- around 90 minutes per proposal
CRM Watchdog
Sorts your open deals by days of silence, from the friendly nudge at three days to the walk-away message at twenty-one.
- Runs
- Weekdays at 08:30
- Time back
- 5 to 10 deals a month that used to die of drift
Connected
today
12 tools are live. The rest of the catalogue is planned, and we would rather say so than show you a dead button.
Live, in flow
Gmailsends an approved draft from your own address, and reads threads with your prospects
Brevosends an approved draft, contacts, account
Google Agendaupcoming meetings, their description, times and attendeesPlanned
Triscale GTM AI Agents reads the tools you connect and writes drafts that a human approves. Here is what we ask a Google account for, and why.
What we ask Google for
calendar.events.readonly- Your upcoming events, read only, to prepare the brief. We never create or modify an event.
gmail.send- Sending a message you approved, from your own address, so replies come back to you.
gmail.readonly- Searching threads with a known prospect (an attendee or a deal contact): subject, date, direction and a short excerpt, to ground the draft. We do not list your whole mailbox and we do not copy messages into your GTM context.
drive.readonly- Read only, and only the files in a folder named Triscale or GTM context: we copy that text into your GTM context. We do not list, show or store the rest of your Drive.
openid, email- The address of the authorized account, so we can show it to you before you send.
Data hosted in Paris, never sold, never used to train a model. Privacy policy
What we do not let
the software do
Six limits that live in the code and not in a sales promise. The first one is the reason the other five exist: no agent tool can reach the sending function.
An agent drafts, it never sends
The rule lives in the code, not in a promise: no agent tool can reach the sending function. A human can ask the platform to send a specific draft they just read. An agent cannot.
Minimal scopes
Cal.com is booking read. HubSpot is contacts, companies and deals, read only. Fathom is its single public API scope. Gmail is send plus a search of threads with a known prospect. Brevo's write scope is used to send what you approved.
Encrypted at rest
Connection tokens are encrypted with AES-256-GCM under a key held on the server, never returned to the browser, never written to a log. Passwords are hashed with bcrypt.
One account, one silo
Every database query is scoped to your account. Deleting an account deletes its connections, drafts, runs, notes and context with it.
Auditable runs
Every run keeps its trace: tools called, inputs, outputs, errors, token cost. When a run produces nothing, you can see exactly why.
No resale, no advertising, no training
Your data is not sold, not used for advertising, and not used to train models. We look at your content only when you ask us to look at a problem.