CRM
Drummer + Salesforce
Every call lands on the right opportunity, with notes, next steps, stage and qualification fields filled in.
Every call fills in Salesforce
The rep talks. Drummer writes what was agreed into the record, with the moment in the call that proves it.
DrummerDiscovery call, 34 min
- 12:41An PeetersAnything above twenty-five thousand comes to my desk.
- 21:05An PeetersThe board decides on the twelfth of November.
- 29:40Jonas MaesI will send pricing for the three showrooms by Friday.
SalesforceDeal
Verbeke Keukens, three showrooms
- Owner
- Jonas Maes
- Amount
- €38,400
- Stage
- Proposal31:08
- Economic buyer
- An Peeters, CFO12:41
- Decision process
- Board sign-off, 12 November21:05
- Next step
- Pricing for three showrooms, Friday29:40
Written by Drummer
Your reps already live in Salesforce. Drummer gives each of them an AI twin that works inside it: after every call the twin writes the notes, sets the next steps, creates the follow-up tasks and moves the stage when the conversation justifies it. The rep approves; Salesforce stays current without anyone typing.
Qualification stops being a guess. Drummer fills MEDDIC, BANT or your own fields from what the customer actually said, and every value links back to the moment in the call that proves it. Forecast reviews start from evidence instead of memory.
There is nothing to migrate and nothing new for reps to learn. An admin connects Drummer once, chooses which fields it may write to, and every change after that is logged with its source.
What moves between Salesforce and Drummer
Drummer reads
- Accounts, contacts and their roles
- Opportunities with stage, amount and close date
- Opportunity owners and their teams
- Your custom fields, MEDDIC and BANT included
Drummer writes back
- Call notes and a summary on the opportunity
- Next steps and follow-up tasks for the owner
- Stage changes the conversation justifies
- Qualification fields, MEDDIC, BANT or your own
- The call, linked to the opportunity and its contacts
Set up once, in minutes
An admin connects it once for the whole company. Reps do nothing.
- 1A Salesforce admin connects Drummer once, with OAuth.
- 2Pick the objects and fields Drummer may write to. Everything else stays read-only.
- 3Map your qualification fields to the scorecard criteria they belong to.
- 4Reps keep working in Salesforce. They change nothing.
Questions about Drummer and Salesforce
Do we have to change our Salesforce setup?
No. Drummer works with the objects, fields and processes you already have. An admin connects it once, picks the fields it may write to and maps your qualification fields. Nothing is migrated, your data model stays as it is, and reps keep working in the Salesforce screens they already know.
Can we see what Drummer changed in Salesforce?
Yes. Every write has an audit trail: the field, the old and the new value, and the moment in the call that justified it, with its timestamp. Reps approve updates in Focus mode before they go out, and you decide which fields Drummer may touch at all.
How does a call end up on the right opportunity?
Drummer matches the attendees of the meeting to contacts in Salesforce, finds their open opportunity and links the call to it on its own. When a contact sits on more than one open opportunity, the rep confirms the right one with a single click in Drummer, and the notes follow.
Teams that connect Salesforce also connect
- Microsoft TeamsTeams sales meetings recorded, transcribed and scored, without a rep pressing record.
- OutlookThe follow-up after every call, written for the rep and sent from their own Outlook.
- GmailFollow-ups drafted in the call's language, sent from the rep's own Gmail after one click.
- SlackLow scores, attention points and comment mentions, posted where your managers already work.
Give every rep a day back, starting next week.
Thirty minutes, on your own calls and your own CRM. No migration, nothing for your reps to learn.