The CRM That Fills Itself In

The situation

Years of valuable conversations with schools and educators sat buried in one person's personal email and calendar. Logging them by hand meant wading through internal chatter, newsletters, and random meeting invites just to find the handful of interactions that actually mattered, and it rarely happened consistently.

What we built

An automatic logging system that reads incoming emails and calendar meetings, filters out the noise (internal chatter, spam, bot-generated invites), and only logs the real, meaningful interactions into a shared CRM. Even when a contact isn't already saved in the system, it's smart enough to match them to the right school by looking at their email domain, so nothing gets lost just because someone forgot to add a new contact ahead of time.

How it works

1. 01Every new email and calendar invite gets scanned as it comes in.
2. 02A filter throws out anything that isn't a real, external conversation: internal team chatter, newsletters, automated meeting-bot invites.
3. 03What's left gets matched to the right person. If they're not already saved as a contact, the system checks their email domain against a list of known schools and files it there instead of losing it.
4. 04The matched email or meeting gets logged into the CRM automatically, linked to both the individual and their organization.

The challenges we solved

• Staff regularly forgot to add new contacts to the master list before those people emailed in, so the system needed a second, smarter way to still catch and correctly file those conversations.
• Inboxes and calendars were full of noise (internal chatter, marketing emails, automated meeting bots) that all had to be filtered out before anything reached the CRM.
• Historical syncing needed to run through years of old email and calendar history without creating duplicate entries or slowing to a crawl.

The result

Every meaningful conversation and meeting now logs itself, automatically matched to the right school or educator, even when the contact wasn't in the system ahead of time, turning one person's private inbox into a shared, searchable relationship history for the whole team.