Who to hire for Radian6 on Salesforce

Radian6 earned its reputation by letting a small social team watch a very large amount of public conversation and act on the parts that mattered. That reputation is exactly why the hiring question is awkward now. A buyer who remembers the product fondly may assume that a Salesforce partner can reinstate it, and a less careful firm may let them keep believing it. They cannot. The useful question is what a partner can do for a team that used to listen through Radian6 and now has to do it somewhere else.

#Where the product stands

Salesforce's help site is blunt: "Salesforce retired the following Marketing Cloud Social Studio subscriptions (“Marketing Cloud Social Studio Products”) on November 18, 2024." Radian6, the listening engine that sat at the heart of that suite, went with it. A practitioner summary of the retirement notice, at Tectonic, records the consequence that matters most to anyone holding history: "all associated customer data will be deleted once your contract ends" That sentence is about data, and it frames the first piece of hiring advice. Before you meet any partner, find out what you actually have: exported mention archives, saved query definitions, report snapshots, or nothing at all.

The honest position for a hiring manager is that Radian6 is a requirements document now. Its queries and rules describe what your organisation wanted to know. The tool that answers those questions will be different, and the work is translation.

#Who is asking, and what they need

The sensible hire depends on which kind of team you are.

The brand team that watched sentiment and share of voice. They need the query logic rebuilt in a new listening tool and a decision about which metrics they will still trust. The useful partner is a listening analyst with a data background, not a Salesforce developer.

The service team that used social posts as cases. They need replies and complaints to arrive in Service Cloud with a link to the original post, an owner and a service level. The partner here is a Salesforce developer who has built case creation from external sources, plus someone who understands social customer care.

The reputation and risk team. They watched for crises, regulatory mentions or executive names. They need alerts that fire quickly and a record of what was seen and when. The partner needs to understand escalation and evidence, and the archive matters more than the dashboard.

Naming the team you are before you write the brief changes the shortlist. A firm that proposes the same solution to all three has not listened.

#What the work looks like in practice

Listening work sounds glamorous and is mostly editing. A query for a brand called Orbit, or Apple, or Virgin, will return an ocean of irrelevant mentions until someone adds exclusions, language filters, author rules and proximity operators. That tuning is knowledge, and it lives in the saved queries and in the heads of the people who wrote them. The partner's first job is to extract it. Their second is to rebuild it in a tool with different syntax and different source coverage, accepting that the counts will not match and agreeing in advance how to explain the break in the trend line.

Source coverage deserves its own conversation. Every listening tool sees a different slice of the public web and of the platforms that allow access, and platform rules about what can be collected change. A partner should be able to tell you which sources matter for your market and which will always be blind spots. If the answer is "everything", they are selling.

#What to ask for in a first engagement

A good first engagement is a written translation of your listening, with a small proof in the new tool. Ask for four things.

First, an inventory of your old queries, with each Boolean expression recorded and the reason it existed. Teams often discover that several of their queries were created for a campaign that ended years ago.

Second, a noise review. Listening tools return false matches for brand names that are also ordinary words, and the tuning that kept Radian6 useful was knowledge held in a person's head. Capture it.

Third, a decision on which alerts need a person within minutes, and who that person is at night and on weekends.

Fourth, a small proof: take five of your most important queries, run them in the candidate tool for a fortnight, and compare what comes back with what your people expect. The proof is cheap, and it ends arguments before a contract is signed.

#Connecting listening to service

If cases matter to you, spend real time on this part, because it is the Salesforce-specific core of the hire. Turning a public post into a case sounds simple, and several design choices decide whether it works. Which posts qualify: every mention, or only those that match a complaint pattern or come from an account above a certain reach? Who is the contact: an existing customer matched by handle, a new person record, or nobody? Where does the conversation happen: do agents reply from a social tool and log the reply on the case, or do they reply through a channel integration? What happens when a post receives a dozen replies, or is edited, or disappears?

A partner with service experience will also raise volume and cost. A busy brand can generate far more mentions than any team can answer, and creating a case for each one buries agents. The skill is in filtering at the source, setting thresholds, and routing the rest to a report rather than a queue. Ask for an example of a rule that cut the volume of cases without losing the important ones, and ask how it was checked. They should also be able to say how a case gets closed and who confirms the customer saw the reply.

Finally, ask about the people side. Social customer care has its own tone of voice, response expectations and escalation habits. An agent who handles email well will not necessarily handle a public complaint well. A partner who proposes the build and says nothing about coaching or style guidance has treated the project as plumbing.

#Keeping evidence when you have to

Some organisations need to prove what was seen and when. Financial services firms, utilities and public bodies may be asked about a social complaint years later. If that is you, add a records requirement to the brief: what is retained, for how long, who can read it, and how it is deleted when the retention period ends. The data kept from Radian6 may form part of that record, and the retirement notice's warning about deletion is a reminder that vendors do not keep your history for you. A partner should discuss storage location, access controls and the terms of the platforms the posts came from, and should be willing to involve your legal team early.

#Comparing the roles

The table shows why one firm rarely covers everything. If a single partner claims all four, ask which of them they have personally done.

#Ten questions for a listening partner

1. Show me a query you wrote for a brand name that is also a common word, and how you reduced the noise.
2. How do you test a query before it goes live?
3. What would you do with a Radian6 export that lacks language or location fields?
4. Which of my old queries would you retire, and what evidence would persuade you?
5. How do you decide the threshold for an alert that wakes someone up?
6. How would a social post become a Service Cloud case, and where would you store the post link?
7. What happens to a case when the original post is deleted by its author?
8. Which platform terms limit what we can store about people who posted?
9. How do you report listening results to a board without implying certainty the data lacks?
10. What will my team be able to do alone when you leave?

Question 8 deserves attention. Social platforms and privacy laws limit how long posts and personal details may be kept, and a partner who has not thought about this will hand you a risk. Questions 1 and 5 are the experience tests. A person who has tuned a real query talks about specific false matches.

#Reporting without false precision

Boards and executives like a single sentiment number, and listening tools will happily supply one. A good partner will explain how that number is produced, how often automated sentiment is wrong for sarcasm, slang and industry jargon, and how a sample of human-checked posts can calibrate it. Ask for an example of a report they wrote where the headline figure came with an honest caveat. If the previous reports you received from Radian6 were treated as fact, expect some friction when the new tool shows a different picture, and plan the communication before launch.

#Red flags

Any proposal that offers to "restore Radian6" or "implement Radian6" should end the conversation, because the product is retired. Be wary of a firm that sells a single replacement tool as the only answer before understanding your queries. Be wary of fixed-price proposals that do not mention noise tuning, since that is where listening projects overrun. And be wary of a team with no one who has ever worked in a social or service operation. Dashboards are easy to demonstrate, and the hard part is deciding what a human should do when a number moves.

#Checking references

Ask for a reference who moved from one listening tool to another, and ask what changed in their numbers. A good partner will say the new tool counted differently and will show how they explained the break in the trend line. Ask for a sanitised query inventory or alert runbook. Ask whether the consultant who wrote it is the one who will work for you. Verify any Salesforce certification the firm advertises on Salesforce's credential site, but remember that no certification covers social listening skill.

#Commercial models and the statement of work

Query translation and the proof suit a fixed fee. Case-creation work in Service Cloud suits a fixed fee per flow with acceptance tests. Data archive work is better capped and time-based. In the statement of work, list the query inventory format, the proof duration and pass criteria, the alerting runbook, data retention rules agreed with your privacy officer, any referral fees from tool vendors, the Service Cloud objects touched, and the handover documentation. For the money behind the retired product, see Radian6 implementation cost and the Radian6 licence page.

#When you do not need a partner

If you listened on a dozen keywords, the results went to a shared inbox and nobody created cases, then a social manager can rebuild everything in a replacement tool within days. A partner earns their fee when the queries are numerous and subtle, when listening drives service workflows, or when evidence has to be retained. Related reading includes what happened to Radian6, should I migrate from Radian6 and integrating Radian6 with Salesforce. This page ranks no agency and names no tool as the winner.