Qualified and Marketing Cloud: the site chat is not the journey

A marketing lead turns Marketing Cloud Engagement journeys off on a Friday. The reason on the ticket is that Qualified now does marketing, so the journeys are duplicate. Qualified is a conversation with someone already on the website. The journeys were emails to people who are not on the website at all. On Monday the welcome mail does not send. A trial customer who never chatted to anyone receives nothing. The site chat, meanwhile, answers a visitor and creates three leads from one session because nobody decided what a conversation is worth. Sales calls all three. The visitor is confused. The subscriber is neglected. The acquisition has been used as a reason to switch off a product it does not replace.

Salesforce completed the Qualified acquisition on 1 April 2026. Qualified is agentic marketing for inbound buyers on a website. It is not a replacement for Marketing Cloud Engagement. Agentic, here, means the conversation on the site can take steps. It does not mean every send you already run has moved. Leave the journey on until you have a sentence for what it does, and a different sentence for what the site conversation does. If the sentences match, you have not understood either product.

#A date, and a job on the website

The close is one sentence: "Salesforce completed its acquisition of Qualified on April 1, 2026." Read it as a date. 1 April 2026. The sentence does not list your journeys, your forms, or your sites. It does not say Engagement is retired. It does not say a chat transcript is a campaign. Take the date, then write the job in your own words, narrowly. A person arrives on a page. A conversation can greet them, answer from material you allow, and ask for a next step you have defined. That is inbound. It is not the mail you send on Tuesday to a list.

Inbound buyers are people who came to you. A journey often speaks to people you chose. Both can be legitimate. They fail in different ways. A conversation that invents a price is a different incident from a journey that emails the wrong country. Do not collapse the incidents into one tool because one logo is newer. The newer close does not supervise the older product. Marketing Cloud Engagement keeps its work until you deliberately stop a named journey for a named reason. "Qualified exists" is not that reason.

Write the pages where a conversation is allowed. A pricing page and a documentation page are different rooms. A conversation on the documentation page that starts a sales cadence may be unwelcome. A conversation on the pricing page that cannot say who to talk to is unfinished. List the pages. A quote that says "the website" has not listed them. You will discover the missing page when a visitor is greeted in a place you meant to keep quiet.

The conversation runs as some identity, with some knowledge, and with a stop. If it does not know, it should say so and offer the path you named: a form, a meeting link, or nothing. It should not invent a product fact to be helpful. Helpful invention is how a visitor screenshots a promise you did not make. Put the stop in the design. Test it with a question you have decided must not be answered.

#What not to switch off

Do not switch off Engagement journeys as the first task. List them. For each, who it speaks to, what it sends, and the person who owns it. A journey with no owner is a finding. It might be safe to stop, or it might be the only welcome a customer receives. You cannot tell from the Qualified close. You can tell by reading the journey with the person who still answers the replies. If that person says the mail must continue, it continues. The site conversation does not cover a subscriber who never visits.

Do not treat a transcript as a data migration into campaigns. A transcript is a record of a chat. It can be kept for a period you choose, in a place you choose, with a privacy rule you can explain. Loading every transcript into a campaign member list confuses a visit with a subscription. The visitor did not ask for the newsletter by saying hello. Consent for a conversation on a page is not consent for a journey. Write both consents down. If you cannot, do not connect them.

Do not create a lead on every message. A lead is a person sales has agreed to work. A greeting is not that agreement. Decide the moment: a meeting booked, a form submitted, a question a human must take. Until that moment, the conversation can stay a conversation. Three leads from one session is the Monday failure. The fix is a rule, not a deduplication project after the fact. Deduplication is what you do when the rule was missing. Buy the rule first.

A Slack channel is not this conversation. Internal chat and a public website are different rooms, with different audiences. Do not fold them together because both can be called conversational. The neighbouring page is Slack, which is not your Salesforce org. A site visitor is not a colleague in a channel. The quote should say so.

#What the bill is made of

Implementation cost means the parts of the bill. This page will not invent a price per conversation, a conversion rate, or a traffic figure. Those are measurements you may later take. They are not assumptions to type into a statement of work.

Discovery is the list of sites and pages, the journeys that stay, and the owners of each. If Engagement is not in the programme, say so, and do not let a partner remove it anyway. If it is in the programme, it is a separate line from the site conversation. Two owners. Two tests.

The conversation line names the greeting, the questions it may answer, the questions it must refuse, and the next step it may offer. Knowledge names the pages it may quote from, and the pages it may not. A draft pricing sheet is not knowledge. A published help page might be. The lead line, if any, names the moment a lead is created, the fields it carries, the queue that receives it, and the consent you rely on. A line that says "sync chats to Salesforce" is not yet a decision.

Identity and privacy name what the conversation stores, for how long, and who can read a transcript. A seller who can read every chat on the site can read conversations that never became their lead. Decide whether that is acceptable. Often it is not. Cutover is one page, not the whole domain. Hypercare is the next week of transcripts, read by the owner, including the refusals. Training is the next marketer in the organisation who can change the refusal list without the partner.

#The week the welcome mail stopped

Monday the trial customer does not get the mail. They open a ticket. Tuesday sales complains about duplicate leads from the pricing page. Wednesday someone restarts every journey at once, including two you meant to retire, because the panic has no list. Thursday a transcript shows the conversation invented a discount to keep a visitor talking. The discount is not a plan you offer. Friday you are explaining that a website conversation and a journey are different products, which was true before the project and is true after it.

The prevention is the two sentences, written before anyone files a ticket to switch a product off. A partner who files that ticket as their first deliverable has misunderstood the close. The close added a product. It did not subtract Engagement.

#The test a buyer should use

Searches ask for the best Qualified Salesforce integration agency, for a consultant to hire, and for an implementation partner. Test them on one page and one journey.

Ask which page the conversation may use, and which question it must refuse. Ask which journey stays on, and who owns it. Ask when a lead is created, and ask them to say that a greeting is not that moment. A partner who recommends turning Engagement off because Qualified is agentic has failed. A partner who cannot name a refusal has not designed a conversation. They have designed a risk.

Ask for the consent line in writing. Chat on a page and mail to a subscriber are different. A firm that treats them as one permission will connect the wrong systems. Do not rank agencies, including the firm publishing this page. Compare two firms on the refusal and on the journey they refuse to switch off. If both want to start by disabling Engagement, you are not ready to hire. Finish the list of journeys first.

#What you settle before the conversation goes live

Pick one page. Write five questions it may answer and five it must not. Include a price question if your prices are not public. The refusal should be dull and clear. Point the next step at a form or a person, not at an invented offer. Name the journey that welcomes a new subscriber, and confirm it still runs. Create a lead only from the event you chose, once, and read it as the queue user who will work it.

Then read ten transcripts from the test, or as many as the test produced. Look for a promise you do not make, a second lead, and a visitor who was greeted on a page you meant to leave alone. Fix those before you add a second page. The acquisition on 1 April 2026 gives you a date. The transcripts tell you whether the design holds.

Write down what the conversation stored. The question, the page URL, whether a lead was created, and whether a refusal fired. If you cannot see those four after the test, you cannot explain a screenshot a visitor kept. Logging is part of the first page, not a later phase. A seller who wants every transcript should be told no until their lead is the one the rule created. Curiosity is not a permission. The subscriber who never visited is still the journey owner's problem. Send that owner the name of the journey and ask them to confirm it ran this week. Their yes is the proof you did not switch off the wrong product. Their silence is a reason to wait, not a reason to disable anything else.

The quote is ready when a marketer can see which page may talk, which journey still sends, and which event creates a single lead. If the page says one product replaces the other, send it back. The close on 1 April 2026 added a conversation for people who came to the site. It did not retire the mail you send to people who did not.

#The other searches

The project quote is on qualified implementation cost. That page does not print a figure. Who bought the company is on what happened to qualified. The connector is on integrating qualified with Salesforce. Whether to move is on should I migrate from qualified. The customer fee is on qualified licence cost. Who to hire is on hiring for qualified. This page does not rank an agency.