Kepler Features

Your CRM updates itself
from the work you already do.

Every proposal shows its source. Nothing is written behind your back.

Book a free demo See how it works ↓

Mia Tanaka 3 items · 2 sources Reject allAccept all 3

Stage ~~Screening~~→Interviewing Email

Interview confirmed for Thursday 14:00 · Supersedes Submitted (Activity)

Notice period Set notice period→4 weeks Call transcript

New task Send Northwind the updated CV Due 4 Aug 2026

Paul Okafor 1 item · 2 sources Reject all

Current salary Call transcript and Email disagree

~~£72,000~~→£78,0002 sourcesAccept

~~£72,000~~→£76,500Accept

Reject all

Senior Data Engineer — Northwind Capital 1 item · 1 source Reject allAccept all 1

Openings 2→3 Calendar event

Headcount raised on the intake call · Supersedes 2 (Email)

Northwind Capital 1 item · 1 source Reject allAccept all 1

Phone Set phone→+44 20 7946 0812 Email

Inside Kepler

How it works.

The loop

A synced email thread becomes three things: matched to the candidate and job it concerns, read for the facts it contains, and turned into proposals you review. This is the whole loop.

Gmail · synced 1 min ago Re: Next steps — interview week

“Thursday 14:00 works on my side…”

Mia Tanaka Candidate · Northwind Capital auto-linked

Threads land on the right person

Synced Gmail and Outlook mail is matched to the candidate and job it concerns on its own — no filing, no “which thread was that?”.

Notice period Set notice period→4 weeks Call transcript

Stage ~~Screening~~→Interviewing Email

Interview confirmed for Thursday 14:00 · Supersedes Submitted (Activity)

Current salary Call transcript and Email disagree

~~£72,000~~→£78,0002 sourcesAccept

~~£72,000~~→£76,500Accept

Reject all

Fills, overwrites, conflicts

Blank field: filled. Set field: proposed, with the reason attached. Two sources disagreeing: laid out side by side. Three shapes, one inbox.

New task Send Northwind the updated CV Due 4 Aug 2026

Suggested tasks too

“Send Northwind the updated CV” arrives as a task proposal with a due date — accept it onto your list or dismiss it, same click either way.

More than email

Email is where the desk lives, but the facts arrive by phone and calendar too. The same engine reads both, and everything lands on the same record in order — no side channel to check separately.

call · 24 min

Notice period Set notice period→4 weeks Call transcript

Calls become fields

Notice period said once on a screening call becomes a field on the record, sourced to the transcript — not lost in someone’s notebook.

Openings 2→3 Calendar event

Headcount raised on the intake call · Supersedes 2 (Email)

Calendars, watched

Headcount raised on an intake call updates the job’s openings — the calendar event is the source, so you know it isn’t a guess.

Re: Interview logisticsMia · Tue 09:12

Quick call — confirmed ThursdayMia · Thu 10:20

Interview · 31 minRecorded, summarised, on the record

Every channel, one timeline

Emails, logged calls and recorded interviews land on the same record in order — no side channel to check separately.

In control

Review works the way you do — one record at a time or the whole queue at once. And an accept is never the end of the story: every field keeps its history.

Mia Tanaka 3 items · 2 sources Accept all 3

Review by record, or all at once

Proposals are grouped by record with the sources counted. Clear a person in one click, or take the rows one at a time.

Current salaryfield history

12 Jun 2026 £72,000 accepted from email · current

14 Feb 2026 £70,500 accepted from call transcript

2 Nov 2025 £68,000 parsed from CV

History keeps the receipts

Every accepted change is dated and sourced at cell level, and any value can be reverted — with conflict detection if things moved since.

The contract

Nothing lands on its own.
Everything shows its work.

Four rules the update engine cannot break — and one boundary we publish about what it reads.

Proposals only. Kepler writes nothing until you accept it — every change lands attributed to the person who approved it, never to “the system”.
Sources always shown. Each proposal carries the email, transcript or calendar event it came from. No source, no suggestion.
Overwrites must argue. Replacing a value someone set costs a reason line: what changed, where it came from, what it supersedes.
Conflicts never resolve themselves. When two sources disagree, both options stay on the table with their sources — you pick.
The data boundary is published. Auto-updates reads only the channels you connected — email, calendar and recorded calls — and nothing outside your workspace.

Questions,
answered

The questions that decide whether an auto-updating CRM is a relief or a liability.

How does Kepler update records automatically?

It reads the channels you connected — Gmail or Outlook mail, your calendar, and recorded calls — matches each thread or event to the candidate and job it concerns, and turns the facts it finds into proposals on the record.

Will it overwrite something I typed in?

Not on its own. A blank field is filled. A field someone already set is proposed with a reason line saying what changed, where it came from and what it supersedes. When two sources disagree, both options stay on the table with their sources and you pick.

What if I accept a change that turns out to be wrong?

Every accepted change is dated and sourced at cell level, and any value can be reverted — with conflict detection if the record moved on since.

What is Kepler allowed to read?

Only the channels you connected: email, calendar and recorded calls. Nothing outside your workspace, and nothing you could not open yourself.

Explore Kepler