Send Survey Leads to Your CRM With Claude and MCP, No Code

Ask for the leads instead of exporting them

The earlier parts of this series covered capturing leads with a QR code survey, which qualification questions to ask, turning webinar polls into follow-ups and importing the CSV into your CRM. That last step works, but the cleaning and mapping by hand is the slow part.

If you already use Claude at work, there is a shorter route. With the rifts.to MCP connector, part of Pro, you can build the lead survey, check on it during the event and close it afterward by asking in plain language. Hand Claude the export, and it can turn the answers into a call list and, if your CRM is connected to Claude too, add the leads there. None of it needs code.

What MCP is

MCP (Model Context Protocol) is a standard way for an AI assistant to use another service's tools on your behalf. Once rifts.to is connected, Claude can create a survey, read its answers and close it when you ask, using your account.

Connect rifts.to to Claude

The connector needs a current Pro subscription, and it checks that on every request. Setup takes a couple of minutes:

1. On claude.ai or in Claude Desktop, open Settings, then Connectors, then Add custom connector, and enter https://mcp.rifts.to/mcp.
2. In Claude Code, run one command:

claude mcp add --transport http rifts https://mcp.rifts.to/mcp

The first time you connect, rifts.to opens in your browser and shows a consent screen. Approving it gives Claude its own access to your account. It does not hand over your password or your surveys' admin links, and you can revoke it at any time under Connected applications on your account page. The MCP connector page lists every tool it offers, and using the API explains how it relates to access tokens.

Build the lead survey by describing it

Tell Claude what the survey is for and what you need out of it. For a booth at a trade show, something like this:

Create a rifts.to survey called "Visit our booth at Midwest Ops Summit".
Questions:
1. Which best describes you? Multiple choice: evaluating tools for my team,
   already using something similar, just browsing.
2. When are you looking to make a change? Multiple choice: this quarter,
   this year, no plans yet.
3. What should we do next? Multiple choice: email me the one-pager,
   call me, nothing for now.
4. Email address. Required if they picked "email me the one-pager" or "call me".
5. Phone number. Required only if they picked "call me".
6. Best time to call. Multiple choice: morning, afternoon, either.
   Required only if they picked "call me".
Label the contact questions so people know when to answer them,
for example "Phone number (only if you asked for a call)".

Claude replies with two links: the public link for attendees and the admin link for you. The "required only if" part uses answer rules, which are part of Pro. Every question is still shown to everyone, since the rules only decide which ones must be answered, so the labels matter.

Open the public link on your phone and answer it once before you print the QR code. Once people have answered, questions can be added but not removed or reworded, so fix wording now.

During the event: check how it is going

You can ask from your phone between conversations:

How many responses does the Midwest Ops Summit survey have so far, and how many picked "call me"?

What are people saying about their timeline?

The connector reports each question on its own: counts for multiple choice questions, an average for ratings, and every free-text answer in a list. It does not line up one person's answers across questions, so it can tell you that nine people asked for a call, but not which phone number belongs to which timeline. For that, open the results in your dashboard, or use the export in the next step.

After the event: turn the export into a call list

A call list needs each person's answers kept together, and that is what the CSV export does: one row per response, one column per question. Download it from the survey's dashboard (export is part of Pro), attach the file to your conversation with Claude, and ask for the list in the shape your sales team works from:

From this file, list everyone who picked "call me". For each, give the phone number, email, best time to call and their answer to "When are you looking to make a change?". Sort by timeline, "this quarter" first. Flag any entry that does not look like a real phone number or email address instead of fixing it.

Check the list against the file before anyone starts dialing. A free-text answer is exactly what the person typed, so a phone number may have no country code, and a joke entry will come back as written. The export also puts an apostrophe in front of any answer that starts with a + sign, so a spreadsheet does not read it as a formula; ask Claude to remove it.

Hand the leads to your CRM

If your CRM is also connected to Claude, you can finish the handoff in the same conversation:

Add each person on that list to our CRM as a lead. Set the lead source to "Midwest Ops Summit 2026", put their timeline and best time to call in a note, and tell me which ones you skipped and why.

Review what Claude adds before you rely on it. Open a few of the new records, confirm the phone numbers landed in the phone field, and check that nobody who only asked for the one-pager was added as a sales lead. Start with a short list the first time.

If your CRM is not connected to Claude, ask Claude for a cleaned CSV with the columns your CRM expects instead, and import that as described in part 4.

Draft the follow-up emails

Claude can write a first draft for each group, using what people told you:

Draft two short follow-up emails: one for people who asked for a call and said "this quarter", one for people who asked for the one-pager. Mention the Midwest Ops Summit, keep each under 120 words, and leave a placeholder for my name.

Read and edit them, then send them yourself from your usual email tool. The "email me the one-pager" group gets the one-pager and one follow-up at most.

Close the survey when the event ends

Close the Midwest Ops Summit survey.

Closing stops new answers, and the results stay readable. Claude can reopen it if someone missed the deadline.

What the connector does not do

• It does not line up one person's answers across questions. For a per-person list, give Claude the CSV export.
• CSV export, collaborators and insight summaries stay in the browser dashboard.
• It sees only surveys on your account. Build the survey through Claude, or while signed in, so it is there to find.
• It does not send anything to your leads. Emails, texts and calls are yours to send.

Privacy and your company's AI policy

A rifts.to response carries no name, email or account. The only identifying details in it are the ones people typed, like the email and phone number you asked for. See what anonymity actually means. When Claude reads those answers, through the connector or from the export you attach, the contact details pass through an AI service, so check your company's AI and data policy first.

Say in the survey what you will do with people's details, and do not add the one-pager group to a marketing list. Rules on marketing email, sales calls and texts differ by country (the EU's GDPR and US rules on calls and texts are two examples), so check with whoever owns compliance.

Common questions

Do attendees need Claude or an account?

No. They scan the QR code and answer in their phone browser. Claude is only on your side.

Can I do this on the free plan?

The survey itself is free to run and answer. The MCP connector, answer rules and CSV export are part of Pro.

Can Claude read my other surveys?

It can read any survey on your account when you ask it to, and nothing outside your account. You can revoke its access from your account page.

Getting people to answer in the first place

Claude can only hand over the leads people actually give you.

• Ask out loud. "Scan this for the one-pager, and pick 'call me' if you want to talk" works better than a sign alone.
• Give a reason in one line on the sign or slide, so the code does not look like homework.
• Put the code where people stop: the booth table at eye level, the last slide of your talk during questions, and the post-event email. Print the link under the code for anyone whose camera will not focus. See sharing a survey.
• Send it again the next morning to everyone who attended. Anyone who missed it on the day can still ask for a call.