Bluebirds prospecting in Sales Cloud and Agentforce

A sales manager opens a board pack and finds a blank cell labelled conversion lift. Someone asks what figure to type, because the brief mentioned Bluebirds. There is no figure on this page. A rate from another company's pipeline is not yours. Their mix of sources, their sellers, and their willingness to disqualify are not your operating system. Bluebirds is AI prospecting. Salesforce planned to bring it into Sales Cloud and Agentforce. The work you can price is who may become a Lead, from which sources, under which rule. The cell stays blank until your own pipeline has a before and an after you measured.

The line you can date is this one. "Salesforce completed its acquisition of Bluebirds on August 13, 2025." Planned, in the announcement's shape, is not the same as a screen this page has seen. Scope from Sales Cloud objects you already know: Lead, Account, Contact, and the person who owns them. Do not scope from a button nobody in the room can open.

#A prospect is a write

Prospecting adds people and accounts to a pipeline. That is a create, or a match to a record you already have. Both are dangerous in different ways. A create that skips dedupe fills the org with twins. A match that is too eager attaches a new conversation to the wrong Account, and a seller calls a stranger by a customer's name. The quote starts with the rule, not with the model.

Write the sources you allow. A provider you already pay. A list your counsel has cleared. A signal your team can explain in one sentence, such as a job change you are permitted to use. Sources you do not allow belong on the same page. Bought lists you have not reviewed. Anything scraped against a terms page you have not read. Personal data your region does not let you use for this purpose. The deny list is the scope. A partner who says the tool will find the right people, without asking what you forbid, is not ready to connect it.

Write the minimum fields before a Lead exists. Name, a way to contact them that you are allowed to use, the source, the reason the source was relevant, and the owner. If a field is missing, the item stays in a review queue. It does not become a Lead so the dashboard moves. A review queue with a named owner is a design. An automatic create that backfills blanks with guesses is how bad data becomes everyone's problem.

Dedupe is a rule you can show on an example. Same email. Same company domain plus same person name, if that is your standard. A fuzzy match needs a threshold you set and a person who reviews the maybes. This page will not give you the threshold. Your data tells you how many maybes you can staff. If you cannot staff them, choose a stricter match and accept that some new people will wait.

#Agentforce may suggest. Creating is a separate permission

The announcement placed the capability with Sales Cloud and with Agentforce. A suggestion and a write are different acts. An agent may draft a reason and show it to a seller. A seller, or a rule you have already signed, decides the create. If the agent creates Leads on its own, that permission should be explicit, narrow, and logged. "Help the seller prospect" is not that permission. It is how you discover on Monday that the weekend produced records nobody recognises.

Territory and ownership come before volume. Who receives the Lead. What happens when two territories match. What happens when none do. A round robin that ignores territory will be priced as simple and resented as unfair. Write the rule you already use for inbound leads, and say whether this source follows it. A new rule needs a sales manager's name on it, not a default from the partner.

Opt-out and do-not-contact sit in the path, not in a follow-up phase. If your org already stores those flags, the create must read them. A prospect who has opted out is not a Lead with a careful sentence. They are a skip. Test that skip with a record you know should be skipped. If the pilot cannot show the skip, it is not ready for a seller.

Cadences and sequences you already pay for are a neighbour. This quote does not replace them by accident. If a new prospect should enter a cadence, name the cadence and the person who owns its words. If it should not, say that the Lead waits for a seller. Automatic email from a new source is a brand decision. Put it in the brief or keep it out.

#What cost means before anyone prices it

Cost is the source list, the deny list, the dedupe rule, the create permission, the territory rule, the opt-out check, the licences you already hold, and the hours sellers and operations spend on a sample. This page has no prices and no conversion rate. A proposal that leads with either is guessing in a unit buyers remember. Take the number off before you compare the rest.

Partner time connects the sources you allowed, implements the match, builds the review queue, and proves the skip. Internal time is the sales manager who signs the create-rule, the operations person who judges duplicates, counsel if a source is new, and the sellers who look at a sample and say whether they would call. If sellers will not look, you do not have a pilot. You have a feed.

Out of scope: a forecast of pipeline value, a target for meetings booked, a rebuild of Sales Cloud, a new data vendor chosen by the partner, a claim about win rate. Those phrases sell. They are not acceptances you can mark. The acceptance is a sample. Fifty Leads, or whatever count your team can actually read. For each, the source, the match, and a seller's yes, no, or duplicate. You choose the count. This page will not choose it for you, and it will not turn the result into a rate you should publish.

The before column, if you want one later, is your current inbound for the same segment, counted your way, for a period you already report. Until that exists, call the pilot a pilot. A pilot can be worth running. It is not a lift.

#Migration services, which usually means the old list

Some teams have a prospecting tool they want to leave. Migration then means the sources, the suppression list, and the open items a seller still means to call. It does not mean every historical contact the old tool stored. Old contacts are a privacy and a quality decision. Bring across the suppression list first. Bring across open items second, through the same dedupe rule as new ones. Leave the rest unless you have a reason and a retention basis.

Map fields in the open. The reason for outreach does not belong in a free-text note that overwrites a seller's comment. Put it in a field you add on purpose, or keep it off the Lead. Overwritten notes are the quiet failure of prospecting projects. The seller loses the sentence they wrote last quarter. Specify the field. Test one record that already has a note.

Duplicates found during the move go to the review queue. They do not auto-merge because a score was high. A bad merge is harder to undo than a delayed create. Say that in the statement of work so nobody is rewarded for clearing the queue by merging.

#The hiring test

People search for the best bluebirds Salesforce integration agency. Give the partner two examples: a person you already have as a Contact, and a person you have never stored. Give them one suppression record. Ask what each becomes. Ask who may press create. Ask which sources they will refuse. Ask them to leave any conversion figure out of the proposal. Ask which Sales Cloud features you already own that they need to see.

A pass writes a create-rule and a skip. The existing Contact matches. The new person waits or is created under the rule. The suppression record never becomes a Lead. The partner asks about territory. The partner refuses a percentage. The partner does not describe a button they have not opened.

A fail types a lift into the blank cell. It connects a source you did not allow. It lets the agent create all weekend. It merges on a fuzzy score with no reviewer. It calls itself the best agency. The examples are enough to end the pricing conversation.

Second test: a Lead that matches two Accounts. The partner should stop for a person, or apply a rule you already use. Inventing a tie-break in the workshop, and writing it straight to production, is how the wrong seller inherits the relationship.

#The sample week

Turn the feed on for one segment, into the review queue, not into every seller's list. Read the sample. Count duplicates, suppressed records that leaked, and Leads a seller would not call. Those three counts are operational. They are not a conversion rate, and they should not be slid into one. Fix the rule that failed. Then, and only then, decide whether creates may skip the queue for the sources that stayed clean.

Keep a person on the queue after that. Sources drift. A provider changes a field. The skip breaks quietly. The hours for that person were part of the cost. If the quote assumed the feed would be unattended, add the hours before you sign.

A later question is whether any of this is worth the hours. That is a method, with a baseline, and it is not a figure to borrow. Spindle AI and the forecast method is the neighbouring page. Read it when someone wants a return in the same pack. Keep the percentage out of both documents until you have measured.

Send the two examples and the suppression record. Ask for the three outcomes in writing before a fee. A partner who can show the skip, and who leaves the blank cell blank, is fit to price a segment. A partner who fills the cell has told you they will fill other blanks the same way.

#The other searches

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