> ## Documentation Index > Fetch the complete documentation index at: https://docs.boothrev.com/llms.txt > Use this file to discover all available pages before exploring further. # Connecting claude # Connecting Claude to BoothRev BoothRev can connect to Claude, Claude Code, and other MCP-compatible AI tools, so you can ask questions about your leads and events in plain language and get help planning what to do next — without leaving your chat. **Requires a paid plan (Monthly or Annual).** Connecting Claude — both the Connect flow and personal access tokens — isn't available on the Pilot. Every call is checked live, so a downgrade takes effect immediately and an upgrade unlocks it on your very next request; nothing to reconnect. Pilot accounts still get full CSV export and the same in-app capture, qualification, and reporting as any paid plan. See [Billing and plans](/for-admins/billing-and-plans). *** ## What this is for This is a **post-event** tool. During a live event, the BoothRev app itself — mobile for reps, web for everyone else — is still where you capture leads and manage the floor. Once the event's context is captured in BoothRev, connecting Claude lets you work with that context conversationally: reviewing leads, finding who hasn't been followed up with, and preparing next steps to carry into your CRM, calendar, or sequencing tool. BoothRev stays the system of record. Claude doesn't write directly into your CRM, calendar, or email tool — it reads your BoothRev context and prepares clean, structured next steps for you to act on in those other tools. *** ## What you can ask it to do * Find leads: "show me my hottest leads from the SaaStock event," "who hasn't been followed up with yet" * Get the full picture on one person: notes, transcripts, priority, ICP fit, and what's been done so far * Find follow-up gaps: leads that are qualified but nobody's followed up with, or leads past the SLA window * Prepare a CRM update, a meeting-setting brief, or a sequencing brief from a lead's context * Add a quick note to a lead, update its follow-up status, or ask Rev to draft (or redraft) a follow-up * Log or check a meeting agreed, or see what's on the calendar this week * Compare how your events are performing against each other, or see which qualification criteria you're weakest on * Check what's waiting on a merge decision in your Duplicates queue * Walk through creating a new event conversationally, start to finish, or update an existing event's goals Every read or write goes through the same role-based access BoothRev already enforces — Claude only sees and can act on what you'd see and do if you were signed in yourself. As a rough guide: Reps get their own leads plus a few personal updates; Event Owners get everything for the events they own; Field Marketing Managers and Admins get everything across the whole account, plus event creation. *** ## Available actions Everything below is something Claude can actually call in BoothRev — grouped by the kind of question it answers. You don't need to know the tool names; ask in plain language and Claude picks the right one. The names are here so you know what's possible and can be specific if you want to be. ### Find and review leads | Action | What it does | | --------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Search leads | Finds leads by name, company, or email, with filters for event, state, priority, owner, tag, replied/not, or meeting booked. Can sort by recency or by score to surface who's most likely to convert. | | List recent leads | The newest leads you have access to, across one event or all of them. | | List hot leads for an event | High-priority or strong-ICP-fit leads for one event, in one call. | | Get a lead's full brief | Everything on one person: identity, qualification signals, scorecard, activity history, pain points, rapport notes, and follow-up state. | | Look up a target account | Finds a curated target account by email domain and the leads captured against it. | | Review pending duplicates | Leads flagged as possible duplicates of each other, grouped and waiting on a merge decision — the same list as the Duplicates queue. Read-only: it shows you what needs a decision, it doesn't merge anything itself. *(Event Owner and above)* | Sample prompts: * "Show me my top 10 leads from Web Summit by score" * "Which leads at the SaaStock booth haven't replied yet?" * "Pull up everything we have on Priya Nair from Acme" * "Did anyone from acme.com stop by our booth this quarter?" * "What duplicate leads are waiting on a merge decision at this event?" ### Follow-up planning | Action | What it does | | ---------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Get a follow-up brief | What happened with a lead and what should happen next — qualification summary, recommended next step, follow-up/meeting state. | | Find follow-up gaps | Leads with no follow-up sent, leads past their event's SLA, and leads with no assigned owner — scoped to one event, one rep, or your whole account. | | Get follow-up coverage | The follow-up funnel for one event or your whole account — how many leads got no follow-up, a draft, or a sent follow-up, plus your SLA compliance rate. Leave the event out and it breaks the numbers down per event, so you can see which one needs attention. | | List booked meetings | Every meeting agreed to, across one event or all of them, soonest first — what's on the calendar this week. | Sample prompts: * "What's the recommended next step for this lead?" * "Who's overdue on follow-up from last week's event, grouped by rep?" * "Show me qualified leads at DevConf with nobody assigned to them" * "What's our follow-up coverage across all my events right now?" * "What meetings do we have booked this week?" ### Prepare next steps for your other tools BoothRev doesn't write into your CRM, calendar, or sequencing tool directly — these actions package up a clean, ready-to-use brief that you (or your connected automation) take there. | Action | What it does | | --------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Get a CRM action brief | A CRM-ready record for one lead — in a generic shape, or remapped to Salesforce, HubSpot, or SAP field names (the same mapping BoothRev's CSV export uses). | | Get a meeting-setting brief | Who to meet, why, relevant context, urgency, and suggested framing. Doesn't book the meeting. | | Get a sequence-enrollment brief | Talking points and segment for enrolling a lead in an outbound sequence. | | Export a whole event for your CRM | Every lead in an event, CRM-ready, in one go — the same field mapping as the single-lead brief above, just for the whole list at once. An alternative to a CSV export when you're already working from a connected CRM tool in the same chat. *(Event Owner and above)* | Sample prompts: * "Give me a Salesforce-ready update for this lead" * "Draft the case for why we should get 15 minutes with this person, and what to open with" * "What sequence segment does this lead fit, and what should the first touch say?" * "Give me every lead from this event in Salesforce format" ### Import attendees from another tool If you also have a registration platform — like Luma — connected as its own MCP server in the same chat, Claude can read your attendee list straight from there and bulk-create pre-registered leads in BoothRev, without a CSV export/import round trip in between. BoothRev doesn't connect to these platforms directly; it's the chat session holding both connections and doing the read-then-push itself. Re-running it is safe — attendees already imported are skipped, not duplicated. Sample prompt: "Pull the attendee list from Luma for this event and import it into BoothRev as pre-registered leads" *(Event Owner and above)* ### Event and programme performance | Action | What it does | | ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | List events | Finds the event(s) you mean by name, date, status, territory, or line of business — the starting point for everything else below. | | Get an event summary | Lead counts by state and follow-up status, qualified/hot/decision-maker counts, meetings booked, SLA stats, pipeline/ROI/cost projections, and progress against the event's goals. | | Get target account coverage | For one event: which curated target accounts were engaged, which weren't (the ABM "who did we meet, who did we miss" view), and any pre-registered attendee domains that aren't on the target list at all. | | Get rep performance | Per-rep rollup: leads captured (with a channel breakdown), qualified count, meetings booked, SLA compliance, and coaching signals like missed next steps. | | Compare lead cohorts | Compares two filtered groups of leads (by event, tag, capture channel, or date range) on SLA compliance, follow-up rate, and qualified/meeting rate. | | Get conversation themes | Top pain points and topics across a filtered set of leads — useful for messaging or product-marketing input. | | Get scorecard results for an event | How leads stack up against your qualification framework (BANT, MEDDIC, or your own custom scorecard), attribute by attribute — where you're strong and where you're consistently missing evidence to judge someone. | | Compare your events | Spend, projected ROI, cost per qualified lead, and pipeline-to-spend across every event you can see, side by side — which one actually earned its budget. *(Event Owner and above)* | Sample prompts: * "How did last week's event do against its pipeline goal?" * "Which of our EMEA target accounts did we miss at this event?" * "How's the team doing on follow-up SLA this quarter, by rep?" * "Compare leads tagged 'enterprise' against everyone else at this event" * "What are prospects at fintech events telling us their biggest pain point is?" * "Where are we weakest on BANT at this event?" * "Which of my events had the best ROI this quarter?" ### Make updates | Action | What it does | | ------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Add a note to a lead | Appends a note to a lead's activity timeline, attributed to you. | | Draft a follow-up | Queues Rev to write (or rewrite) a follow-up draft for a confirmed lead — same as "Generate Draft" in the app. Takes Rev a few seconds to finish; ask again shortly to read it. | | Update follow-up status | Marks a confirmed lead's follow-up as sent, or reverts it — mirrors the "Mark as sent" action in the Leads inbox. | | Set or update a meeting agreed | Records a meeting for a lead, the same as tapping "Meeting Agreed" in the app. If someone else already booked one for this lead, you're told who and when before it's replaced — not silently overwritten. | | Update an event's goals | Updates an event's meeting/SQL/pipeline goals, follow-up SLA window, spend and budget figures, expected deal size, or ICP definition — the numbers on the Event Success tab. Only the fields you mention change; everything else is left alone. *(Event Owner and above)* | Sample prompts: * "Add a note that this lead wants a follow-up call in September" * "Draft a follow-up for this lead" * "Mark this lead's follow-up as sent" * "Log a meeting with this lead for next Tuesday at 2pm" * "Bump this event's meeting goal to 25 and set the follow-up SLA to 12 hours" ### Create an event, conversationally Event creation walks through a **draft → validate → create** sequence rather than one big form-fill, so Claude can check your inputs and let you fix anything before it's actually created. 1. You describe the event in plain language — name, dates, location, goals, whatever you know. 2. Claude drafts it and shows you the normalized fields. 3. Claude validates the draft against BoothRev's real rules (required dates, pilot-plan caps, owner eligibility) and flags anything that needs fixing. 4. Once it's clean, Claude creates the event for real. Sample prompt: "Set up an event called DevConf Berlin, Sept 14–16, goal of 40 meetings and \$200K pipeline, I'll own it." *** ## Setting it up There are two ways to connect, depending on what you're using. ### Claude.ai or Claude Desktop: Connect 1. In Claude, add BoothRev as a connector and click **Connect**. 2. You're sent to BoothRev to sign in (if you aren't already), then land on a consent screen showing what's being requested in plain language — for example, "See your leads, events, and follow-up activity" or "Add notes, update follow-up status, and create events on your behalf." 3. Click **Allow**. Claude can now read and act on your BoothRev context, scoped to your role. ### Claude Code or another MCP client: Personal access token 1. Go to your account menu (click your name in the sidebar) and open **Personal access tokens**. 2. Click **Generate token** and give it a name that reminds you where it's used (e.g. "Claude Code"). 3. Copy the token immediately — BoothRev shows it to you exactly once and can't display it again. If you lose it, revoke it and generate a new one. 4. Add BoothRev as an MCP server in your client, using that token as the connection's bearer token. Both methods are tied to you personally, not to your role. If your role changes later, your access updates automatically on your next request — no need to reconnect or regenerate anything. *** ## Managing your connections and tokens Go to **Account → Connected apps** to see every app you've approved through Connect and revoke one you no longer need. Go to **Account → Personal access tokens** to see every token you've created, when it was last used, and to revoke one you no longer need. Either way, revoking is immediate — the connected client stops working right away. Create a separate token per client (one for Claude Code, another for a script, for example) so you can revoke access to one without disrupting the others. *** ## What it won't do * It won't act during a live event in place of the mobile or web app — it's built for the higher-context work that happens after or between events. * It won't write directly into your CRM, calendar, or email tool. It prepares the update; you (or your connected automation) executes it there. * It can't see or do anything your BoothRev role couldn't already see or do. *** ## Related * [Roles and access](/getting-started/roles-and-access) * [Exporting leads to your CRM](/for-event-owners/exporting-leads) * [Connecting your CRM or enrichment tools (for admins)](/for-admins/connecting-crm-and-enrichment-tools)