Enrich RB2B Visitors

Before you begin

Install Connecting RB2B's Profiles API to Claude first. This skill uses it to pull your identified visitors straight from RB2B, so you don't have to export a CSV each time you run it.

You'll also need a MoltSets account connected to Claude. MoltSets does the enrichment and the people search, and every lookup runs on your own MoltSets tokens. Sign up for a free MoltSets account.

Prefer working from a file? An RB2B CSV export still works. Upload or paste it into the chat and the skill uses it instead of the API — as long as it still has its LinkedIn URL column, which is what every lookup keys off.

What it does

RB2B returns a work email for roughly 40% to 60% of the people it identifies. That leaves a large minority you know visited, know by name, and cannot contact.

This skill takes the visitors RB2B has already identified — pulled straight from the API, or from an export — and works from the LinkedIn URL RB2B captured on each person. For every one of them it looks for a business email, a personal email, and a mobile number, then hands them back alongside whatever RB2B already gave you. Nothing is replaced — the original RB2B email stays in the table so you can compare.

When to use it

This is the right skill when your targeting is already working and the bottleneck is purely reach. The accounts visiting are ones you want, the people are the right seniority, you just don't have a way to contact enough of them.

If the accounts are right but the individuals visiting aren't the buyers, you want Non-ICP to ICP Contacts instead. If your traffic is mostly company-level identifications with no person attached, start with Companies to Contacts.

How it works

1. Claude pulls your visitors from the RB2B API for the date range you choose, or reads a CSV export you upload.
2. People are separated out and their LinkedIn URLs extracted; company-level identifications are skipped automatically rather than wasting lookups.
3. You say which deliverability grades you're willing to keep, before anything runs.
4. Three lookups run against each profile — business email, personal email, and mobile number.
5. Results are graded, filtered to your chosen grades, and assembled into one table.

What you get back

A table with name, company, the RB2B email, the business email and its risk grade, the personal email and its grade, and the mobile number. Underneath it, a summary: how many visitors were processed, how many new contact points were found, and how the risk grades were distributed.

That summary is worth reading before the table. It tells you the actual reachability of your traffic, which is a different and more useful number than the identification rate on your RB2B dashboard.

Keeping the credit cost down

You can ask for email only and skip the mobile lookup entirely, which is usually the right call for a first pass — mobile numbers matter for a small, high-intent slice rather than for everyone who read a blog post.

The same logic applies upstream: the cleaner your RB2B collection rules, the less you spend enriching traffic you'd never contact. Restricting collection by URL and excluding internal domains both pay for themselves here.

Start small

Run it on a narrow slice first: a day or two of visitors from the API, or twenty or thirty rows of an export. That's enough to see the hit rate and the risk grades you're getting for your particular audience, and to decide which grades are worth keeping before you point it at a month of traffic.