With Dex open in a browser tab, Strawberry can help you work through people, interactions, reminders, and the context around a relationship. It can prepare follow-up ideas from the history you have recorded, identify contacts who have gone quiet, research a new detail from the tabs you choose, and leave the final message in your hands.
01
Remember the relationship, not just the reminder.
A “follow up” task without context is easy to ignore.
Strawberry can read the Dex history you open, pull out the last meaningful interaction, and prepare a reconnection idea that has a reason behind it. The aim is not to manufacture networking activity; it is to avoid forgetting people who matter.
02
Prepare messages that start from what actually happened.
A personal CRM becomes impersonal when every outreach note starts with a template.
Strawberry can use the visible Dex notes, meeting history, and context you provide to draft a message that refers to a real shared thread. You can make it your own before it leaves the browser.
03
Keep contact details current without playing detective.
People change roles, companies, and priorities.
Strawberry can use the pages you already have open to prepare a factual update for a Dex contact, show the source for each proposed change, and leave you to decide whether it belongs in the relationship record.
04
Make relationship maintenance fit the week you actually have.
A recurring relationship review should distinguish a thoughtful reach-out from a task generated because a date elapsed. Save a good review as a skill and run it as a routine to prepare a small Friday list with reasons, not a bulk outreach quota.
It can use the contacts, notes, reminders, and interaction history visible in the Dex tab you open.
It can prepare a message from the relationship context. Review and approve anything before it is sent.
It can prepare a sourced change proposal from the browser context you provide. Confirm each update before changing the Dex record.
Yes. Save a review that reflects your own standards as a skill, then use a routine to prepare it at a sustainable cadence.
Keep the scope narrow, verify any drafted message against the original context, and never use private relationship history as a reason to automate outreach blindly.
Dex Strawberry