Why Salesforce falls behind
Salesforce is only as current as the last time someone typed into it. The conversations that move a deal mostly happen somewhere else, in a LinkedIn thread or a Gmail reply or a call whose notes live in a Google Doc, and logging them is the chore reps push to Friday before Friday gets busy too.
dassi does that logging from wherever the conversation is. It reads the thread or the notes in one tab, opens the right record in another, and prepares the activity, the task and any field changes for you to approve. You don’t need a connected app, an edition with API access, or a ticket to your Salesforce admin, because dassi works through the same Lightning pages you use, signed in as you, which also means it’s held to whatever your profile and permission sets allow.
Example: tidying the pipeline before the forecast call
Teach this one once and schedule it for Friday at 2pm.
- dassi opens your list view of open opportunities closing this quarter.
- For each one it finds the latest Gmail thread with the primary contact, plus any LinkedIn messages you’ve exchanged with them.
- It drafts an updated Next Step, flags close dates that have already passed, and marks opportunities with no activity in three weeks.
- You get one table with the opportunity, the current value, the proposed value, and the email or message that justifies the change. Approve row by row, or approve the lot and strike the two you disagree with.
- It makes the approved edits, logs a completed activity on each record, and lists anything it couldn’t save and why.
We’re a bit obsessive about that report. Orgs with years of custom fields tend to have validation rules nobody remembers writing, and we’d rather tell you about a failed save than let you find it at the forecast call.
What stays with you
Every record change waits for your approval by default: stage, amount, close date, owner, and any field that already has a value in it. Once you trust it, logged calls and notes can be set to save without asking. dassi doesn’t delete or merge records unless you ask for that specific thing. If a validation rule or a required field blocks a save, it stops and shows you the error message rather than inventing a value to get through.
Limits
Salesforce requires multi-factor authentication for direct logins. When a session times out, dassi signs in with whatever Chrome’s password manager autofills and waits for you to approve the MFA prompt. Scheduled runs happen in your own browser, so it has to be open on Friday at 2pm. Working through pages is slower than the API, which means loading 50,000 leads is still a Data Loader job; dassi is for the record-by-record upkeep that nobody gets around to. The records it reads also go to the AI provider you picked (through dassi’s relay on included credits), so think before pointing it at accounts full of sensitive notes.
For the LinkedIn end of this, see the LinkedIn page and LinkedIn message to CRM. Lead list building and candidate sourcing and screening feed new records in, and Gmail inbox triage catches the replies. If your team is on HubSpot, that page covers the same ground with different field names.