Integrating Momentum with Salesforce

A seller opens an opportunity on Monday and finds a note they did not write. The note describes a call. The call happened. It happened with a different account. The words were faithful to that other conversation, and they are now sitting on the wrong record, where a forecast conversation will treat them as fact. Nobody can say which field was supposed to receive the note, because the project never named a field. The write used whatever text area was easiest to fill.

That is the integration. Not the close. The close does not know your opportunities. The integration is the system that heard the conversation, the note as an object with a real field name, and the failure when the note lands on the wrong opportunity. Until those three are written down, a connector is a way to misfile calls at speed.

This page holds the three labels. How you scope consent, retention, and a partner is Momentum, call insight, and what the acquisition does not prove. What the close itself published, and what it did not, is What happened to Momentum. Go to those when the room is arguing about the deal or the build. Stay here until you can point at the opportunity and say why the note belongs there.

#What the cited page says

The sentence this page quotes is the completion record: "Salesforce completed its acquisition of Momentum on March 2, 2026." Outside the quotation, the day is 2 March 2026. Completed means the deal is done. It is not a statement that your org gained a new write into opportunities that morning.

The sentence does not name a field. It does not name an object. It does not give you a win rate. A business case that needs a percentage will not find one here, and this page will not invent one. A before-and-after on your pipeline is a study you have not run. A round number in a footnote is not that study. Take it off the slide. The integration does not get easier because a slide is more persuasive.

There is also no screen, no daily cap, no price, and no connector name in the sentence. Do not draw them. If a proposal includes a connector with a product name this source does not use, ask where the name is published. If the answer is the proposal itself, the name comes off.

What you may say, from the work in front of you, is narrower. People have conversations. A note might be written back to Salesforce. That note is only an integration when it has a field that already exists, on a record you can identify, under a rule a person can apply. Everything else is a wish.

#The system

The system is the path from a conversation to a Salesforce record. Name both ends. The conversation has a source you can point at: a call, a video, a room where people spoke. Salesforce, for this page, is the opportunity the note might land on. If you cannot name the source of the words, you cannot defend the note. If you cannot name the opportunity, you must not write.

Do not start by connecting every seller's calendar because the deal closed. A calendar is easy. The opportunity match is the work. "The latest open opportunity on the account" is a rule you may choose, and it is a dangerous default, because accounts have more than one open opportunity. Write the rule in a sentence. Include what happens when two opportunities match, and what happens when none do. The safe result when none match is no write. A new opportunity created so the note has a home is a second decision, with its own owner. Do not hide it inside the note.

The person who accepts the write is part of the system. A note that appears with no one accountable will be treated as the system of record by the next reader. Field history should show a person when a value changes. Confidence in a summary is not a person. If the seller owns the relationship, the seller accepts the note, or the note stays in a place the seller can reject. An automatic write that skips the seller will produce the Monday failure faster than a careful one.

There is no win-rate system hiding behind this. Do not add a score, a percentage, or a forecast stage because a summary sounded sure. Stage and amount already have owners in most orgs. This page will not tell you to overwrite them. It will not give you a substitute field either. Your org has field names. Use one that already exists, chosen by the people who own the opportunity, or do not write.

#The object

The object is the note. A note written back needs a field name. This page will not invent the field. Inventing a field is how a diagram grows an API name that no admin can find on Monday. If the team cannot point at a field that already exists, the integration is not ready. The missing name is the status. It is not a gap for a consultant to fill with a plausible word.

Say what the note is allowed to contain, in plain language, without pretending you have named the field for them. A short account of what was said. A next step the seller can accept or reject. Not a guess about whether the deal will close. Not a personality judgement. Not a number the customer read aloud that you are not prepared to store. The refusal list sits beside the field, once the field has a real name. Until the name exists, the refusal list has nowhere to attach, and that is a reason to wait.

The note is not the recording. The recording, if you keep one, is a different object with its own retention and its own audience. Collapsing them means a CRM field becomes a place to hide a transcript, and a transcript becomes something the whole account team can read. Split them. This page's object is the note that lands on the opportunity. Who may hear the original conversation is a decision on the implementation page. Do not skip it by only talking about the note.

A note without a target record is not yet the object. It is a draft in the system that heard the call. Leaving it there is allowed. Forcing it onto an opportunity so the integration "does something" is how the wrong record gets the words.

#The failure

The failure is a note on the wrong opportunity. The words can be a fair account of a real conversation. The record is still wrong. A colleague who was not on the call will trust the note, because it sits where truth usually sits. The seller who was on the call may not see it for a week. By then the forecast has moved, or a renewal has been briefed from the wrong history.

Wrong can mean several concrete mismatches. The right account and the wrong opportunity. The right seller and an opportunity they no longer own. A conversation about a different product, filed on the only open deal someone could find. A note copied to every open opportunity on the account so none would be missed. That last one feels thorough. It is the failure, repeated.

Test it with a fixture you control. Two opportunities on one account. One conversation that is clearly about only one of them. Run the write. The pass is a note on the matching opportunity and silence on the other. If both receive the note, stop. If neither rule can explain the match, stop. Do not tune the rule by reading a success on a single-opportunity account. Most damaged notes happen where the account is busy.

When the match is uncertain, write nothing to the opportunity. Surface the draft to a person. A person can file it. A guess cannot unfile it cleanly, because people will have read it. Uncertainty is a normal state, not an error to paper over.

Keep a log of which conversation, which rule, which opportunity, and which field. If a seller disputes a note, you will need that line. A design that cannot say why a note chose a record has already failed, even if this week's sample looked fine.

#The diagram

A diagram that does not name the system, the object, and the failure is a poster. A box called Momentum, an arrow, and a box called Salesforce will be built as "write the summary somewhere". Somewhere is how the wrong opportunity gets the note.

If the object cell says "TBD" or a field name nobody can find in the org, the diagram is not finished. Do not connect the write while the cell is a guess. If the failure cell is missing, people will test for spelling and call it quality. Spelling is not the failure this page is about.

Leave win rate off the picture. A percentage in the corner turns the diagram into a business case. This source will not support it. Also leave off any connector name, any screen, and any price. You were not given them.

#What you write before a note is allowed to land

One page, from the people who own opportunities, not from a template.

The match rule. How a conversation chooses an opportunity. What happens when two match. What happens when none match. The none-match result is no write, unless a separate decision creates a record, with an owner.

The field name. Copied from the org, spelled as the org spells it. The person who confirmed it. If you cannot produce the name, you stop. You do not coin one.

The acceptance. Who must accept before the field changes. What the seller sees when they reject the note. Where the rejected text goes, and how long it stays.

The refusal list. What must never be written, even on the right opportunity. A payment number. A health aside. A guess at close. Test the list on a real conversation, not on a polished example.

The log. Conversation, rule, opportunity, field, accepter. Who can read it when a note is disputed.

Out of scope. Any win-rate claim. Any new field invented for the diagram. Any write to amount or stage unless the owners of those fields have agreed, in writing, on this page. This guide does not make that agreement for them.

A quote for the work prices this list. It does not price a lift in win rate. If the quote cannot name the field, it is early. Send it back for the name.

#How the other two pages fit

This page is the diagram and the rule that a note must be able to name its field and its opportunity. It is not the whole programme.

What happened to Momentum is the close. The day, the owner, and the absences, including a price and a shutdown story the record does not tell. Use it when someone treats a headline as a scope. Do not let the headline choose a field.

Momentum, call insight, and what the acquisition does not prove is the build around the conversation itself. Consent, retention, who may hear a recording, and how to test a partner who arrives with a percentage. Use it once this diagram is accepted. A partner who starts by writing notes to every open opportunity has skipped both pages.

#A first note you can reverse

Pick one team and one kind of conversation. Pick an account with two open opportunities, so the match has a chance to be wrong. Agree the field name with the admin who can show it to you in the org. Run one conversation you are allowed to use. Look at both opportunities.

If the note is on the right one, in the named field, and the other opportunity is untouched, keep the sample. If the note is on the wrong one, turn the write off and fix the rule before a second conversation. Do not average the two outcomes into a soft pass. One wrong record is the failure.

At the end of the exercise you should be able to read the diagram without inventing a cell. System, object, failure. The object cell has a field name you did not coin. If the name is still a blank, the integration has not started, however complete the acquisition may be.