> Kepler reads your emails, calls and calendar, links them to the right record, and proposes the field changes — you accept or reject in a click.

_Kepler product feature — CRM That Updates Itself From Email & Calls. Canonical: https://keplercrm.com/features/auto-updates/_

# Your CRM updates itself from the work you already do.

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

## 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.

**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?”.

**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.

**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.

**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.

**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.

**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.

**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.

**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.

## 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

### 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.