Sending event emails from your own domain has been possible for a long time. Getting there hasn't. It meant a request to Support, a round trip with our Customer team, and zero visibility on whether your DNS records had actually landed. The Email Domain Manager moves that entire process into Studio: you add the domain, publish the records, watch each one turn verified, and hand the sender addresses to the right events. Yourself.

How it works

1. Add your domain. In Organization Settings, open the Email Domain section and enter your domain. Studio generates the DNS records your provider needs to publish.
2. Publish and track. Each record is checked independently and carries its own status — under verification, verified, or invalid — so you can watch propagation happen instead of guessing.
3. Create your sender addresses. Once the domain is verified, build the addresses you'll actually send from (hello@, registration@, support@) on top of it.
4. Scope them to your events. Decide which events and communities can use each address. Event and Community Managers then pick it from the dropdown in their own settings (Emails > Sender address).

Deliverability, in plain sight

The manager doesn't only confirm the domain is yours. It shows you what stands between your emails and the inbox.

• Record-level diagnostics. Authentication, DMARC policy, and MX records are each checked and flagged on their own, so you fix the one that's broken instead of restarting the whole setup.
• A clear invalid state. A record that fails validation says so, in the same screen where you'd correct it. No support thread to find out why a magic link never arrived.
• Status in real time. Your IT contact publishes a record, your event manager refreshes, and the status moves. Nobody has to read DNS values back to anyone over email.

Assign once, cover the whole series

• Community-level in one action. Enable a sender address for a community and every event inside it can use it.
• Future events inherit it. Create a new event in that community later and the address is already attached, so nothing quietly reverts to noreply@swapcard.com on send day.
• Or stay granular. Scope an address to specific events only when a client, sponsor, or sub-brand needs its own sender.
• Verified once, shared across the group. Enterprises running several organizations under one umbrella don't re-verify the same domain for each one.
• Deletion is safe. Remove a sender address and every event using it falls back to the default Swapcard address. Communications never break mid-campaign.

Why organizers will love it

Email deliverability is invisible until it isn't: a magic link that never arrives, a registration confirmation sitting in spam, an open rate that craters because attendees don't recognize the sender. Every one of those used to start as a ticket and end with someone on our side interpreting DNS records for you — slow for you, and slower still when the fix was a single wrong character in a record.

Now the loop closes where the knowledge lives. The team that owns the domain manages the domain, sees the health of every record, and assigns senders across a whole community before the first campaign goes out. Faster setup, fewer tickets, and registration and marketing emails that land in the inbox your attendees are actually watching.

💡 Pro tip: Get your DNS contact in the room for the ten minutes it takes to publish the records. Verification is the only step that depends on someone outside the platform — everything after it is yours.

💡 Pro tip: For a recurring series, assign the sender address at community level rather than per event. Every future edition picks it up automatically, which kills the most common cause of an event going out from the default address.

A company wants 25 passes for its team. The catch: the team isn't finalized, and forcing them to name 25 people at checkout is the fastest way to stall the sale. Anonymous Group Registration removes that blocker. Buyers reserve and pay for a whole block of registrations in a single transaction, then hand out the seats on their own schedule, so the sale closes now and the roster catches up later.

How It Works

1. Turn it on. In Registration Settings, enable Anonymous Group Registration and pick what buyers can bulk-buy: tickets only or packages only (one type per event, matched to your package and classification setup).
2. Build the purchase flow. A dedicated page builder gives you a fixed five-page flow — Landing, Purchaser & Financial Contact, Review, Payment, Completion — with the same elements, theming, conditions, and languages you already use everywhere else.
3. Buyers purchase in bulk. The new Bulk Quantity Selector lets a purchaser choose how many of each item they want, watch the order total recalculate live, and pay once, with no per-attendee fields anywhere before payment.
4. Slots are created, unassigned. Every pass bought becomes a slot with a status of Unassigned, linked to its item and the group order. The buyer lands on a Pass Assignments dashboard, also linked in their confirmation email.
5. Seats get filled, two ways. From that dashboard, the group contact can assign a pass directly (enter someone's email and name) or invite by email (send a tokenized link and let the person complete their own registration).
6. Badges unlock on assignment. A slot only earns a badge and check-in once it's tied to a real, completed registration. No name, no badge.

Key Behaviors

• One payment, zero names. The whole block is a single transaction and a single group order; attendee details are collected later, never at checkout.
• Tickets or packages, not both. Each event runs one bulk type, and a cart can't mix a package with a ticket.
• A clear slot lifecycle. Every pass moves through Unassigned → Pending → Assigned, with Canceled for anything pulled back, so you always know what's still open.
• Revoke and reassign. Pull back an invitation that was never completed and the slot frees right up for the next person.
• Tiered quantity discounts. Set promo codes that unlock at a quantity threshold, and buyers get a nudge as they approach it ("you're 1 registration away from your discount") to push the cart higher.
• Cancel and refund from Admin. Recover unused inventory and process refunds against the original group payment, straight from the group's Financial tab.
• Reporting and reminders, built in. Track fulfillment with Unassigned / Pending / Assigned counts on the Group Registrations report, filter searches and advanced reports by Assigned status, and fire off Unassigned Slots and Incomplete Invitation reminder emails to chase the stragglers.

Why Organizers Will Love It

Group and corporate sales are where a lot of registration revenue lives, and they're exactly the deals that stall when you demand a full roster upfront. This flips the order: buyers commit budget and lock in passes the moment they're ready to buy, and the names arrive on their timeline instead of yours. You get cash and committed capacity earlier in the cycle; your buyers get a checkout that doesn't punish them for planning ahead. And because assignment, badge gating, reporting, and reminders are all part of the same flow, an unnamed pass never quietly becomes an unusable badge on-site.

💡 Pro tip: Decide tickets-only vs packages-only before you open sales. It's tied to your event's package and classification setup and it shapes the entire bulk-buy flow.

💡 Pro tip: Set your tiered discount thresholds where they'll actually bump buyers into the next bracket. The "you're X away" nudge does the upselling for you, but only when the next tier is within reach.

The biggest bottleneck to Sherlock adoption was never the AI, it was the blank box. Attendees and exhibitors open the chat, don't know what to ask, and give up before they even start. Smart Predefined Questions closes that gap: the moment someone opens Sherlock, three suggested questions are already waiting, tailored to that exact person and event.

How it works

1. Sherlock's recommender engine pulls from five signals: the user's profile data, their past Sherlock interactions, the event's trend questions, the event timeline, and a set of hard-coded questions.
2. It ranks and narrows those down to the three most relevant questions for that specific attendee or exhibitor, and surfaces them the moment they open Sherlock.
3. Tap a suggestion, and it's sent straight to Sherlock as a message, kicking off a normal Sherlock reply, plan mode included, when the question calls for it.

Key behaviors

• Personalized when there's data: Returning users get questions ranked against their profile, their Sherlock history, trend questions, and the event timeline.
• Cold start, covered: New users with no profile data or interaction history still get three relevant questions, pulled from trend questions and a hard-coded set.
• No awkward gaps: Fewer than three good candidates? Sherlock shows whatever's available, no empty placeholders, no error states.
• Fallback built in: If the recommender comes up empty, or has an off moment, the hard-coded questions step in by default.
• No repeats: Once a question's been suggested and answered, or it's one Sherlock can't answer, it drops from that person's pool for the rest of the event.
• Always current: Close and reopen Sherlock, and the three questions recompute against the latest data available.

Why organizers will love it

Adoption for an AI agent lives or dies on that first message. Smart Predefined Questions turns Sherlock from "type something and hope" into a guided nudge, personalized per attendee, per exhibitor, per moment in the event. More people start a conversation, more of those conversations are relevant from message one, and matchmaking, session discovery, and exhibitor Q&A all get a running start instead of a cold open.

Sherlock has always been able to answer on the fly. But "find our best leads and send them meeting requests" isn't a one-shot question, it's a project. Sending Sherlock off to handle multi-step or ambiguous requests without a check-in point meant crossing your fingers and hoping the AI understood the assignment. Not anymore.

Two updates land together to fix that: Plan mode, so you see Sherlock's approach before it moves, and multiple-choice questions, so Sherlock can ask for missing context instead of assuming it.

Plan Mode: See the Steps Before Sherlock Takes Them

When an organizer asks Sherlock something that needs deeper reasoning, or that involves Sherlock actually doing something on your behalf, Sherlock now stops to lay out its plan first.

How it works

1. You ask Sherlock a complex request (multi-step, action-oriented, or open to interpretation).
2. Sherlock detects it needs a plan and replies with a numbered breakdown of what it intends to do, formatted as a normal chat message.
3. You react to the plan:
   • Agree, and Sherlock proceeds to execute it.
   • Discuss changes, and Sherlock updates the plan and re-displays it for your confirmation.
   • Disagree, and Sherlock stands down. No action taken.

Key behaviors

• Nothing happens without your sign-off. Sherlock only starts executing after explicit agreement, no silent actions on your event.
• Plans are editable, not just approve/reject. Talk to Sherlock like you would a teammate: tell it what to change and it revises the plan in place.
• Same message format you already know. Plans show up as a regular Sherlock message in the thread, no new UI to learn.

Multiple-Choice Questions: Answer in a Tap, Not a Paragraph

The second piece: when Sherlock doesn't have enough context to give a solid answer, it now asks, with suggested answers you tap instead of typing out.

Key behaviors

• Single-select moves fast. Tap one answer and the flow jumps straight to the next question, or submits everything back to Sherlock if it's the last one.
• Multi-select waits for you. Tap as many answers as apply, then hit Submit to advance. The button stays disabled until at least one is selected.
• "Something else" always has a place. Every question includes a free-text fallback for the answer that isn't on the list.
• Ignore it and Sherlock adapts. Send a new message instead of answering, and Sherlock drops the question flow and answers your original request as-is, no dead-end conversations.
• Works everywhere Sherlock does. Same experience on the event mobile app and the web app.

Once every question is answered, Sherlock goes back into thinking mode and returns one refined answer that accounts for every response, instead of a generic best guess.

Built to Work Together

Plan mode and multiple-choice questions are designed to pair up. Ask Sherlock to identify and reach out to your best leads, and it might propose a plan (review the list, draft messages, send requests) and then tap you for the missing piece, like which seniority levels to prioritize, before it drafts a single message.

Why Organizers Will Love It

Exhibitor ROI and lead retrieval workflows live and die on trust: if you can't see what an AI agent is about to do, you don't hand it real work. Plan mode turns Sherlock from a black box into a collaborator you can steer mid-task. And multiple-choice questions mean neither your organizers nor your attendees have to write an essay just to get matchmaking, session, or networking recommendations that actually fit.

💡 Pro tip: Use plan mode for anything Sherlock will act on (sending messages, updating records), and let the clarifying questions do the work on anything ambiguous. Together they cut down on the "that's not what I meant" follow-up messages.

Chasing down who was meeting whom used to mean cross-referencing two tabs and matching internal IDs by hand. Not anymore. The Meetings tab of your meeting export now packs everything onto a single row per meeting, participant details included, so you can follow up onsite without the spreadsheet gymnastics.

What's new

The Meetings tab (Studio > Meeting export > Meetings) is reorganized so every meeting is fully readable in one row:

1. Core meeting info comes first: status, dates, location, source, in a fixed column order.
2. A new Meeting Description column, so you can read the meeting subject without opening the Studio.
3. Two full participant blocks, Participant 1 and Participant 2, each with 13 fields: contact info, status, feedback, groups, job title, company, and exhibitor details.
4. An Additional participants column for group meetings, bundling every participant from the third onward into one cell.

Key behaviors & options

• Participant 1 is always the requester (or the earliest-added participant, if no one's flagged as requester), so you always know who started the conversation. 
• Participant 2 is the next person added, built for reading 1:1 meetings, which make up 95% of meetings on Swapcard, at a glance.
• Full contact + context per participant: email, name, status, feedback, job title, company, exhibitor name and booth, plus internal/external IDs, no more jumping to the Participants tab.
• Group meetings still fit on one row: from the 3rd participant onward, details land in a single "Additional participants" cell, separated by semicolons.
• The Meetings Participants tab is untouched: same columns, same data, if your workflows already rely on it.

Why organizers will love it

No more manual matching between tabs. Whether you're chasing exhibitor ROI, prepping onsite follow-ups, or auditing who met whom, it's all on one line: sortable, filterable, ready to drop straight into your CRM or follow-up sequence.

💡 Pro tip: Filter by Participant 1 - Requester to instantly surface who initiated each meeting, handy for prioritizing your onsite follow-up list.

Your event home page is prime real estate for brand expression. Until now, when you uploaded a custom image for a homepage button, the platform enforced a label overlay — limiting how much visual control you had. With image-only homepage buttons, that constraint disappears.

Now organizers can display buttons as pure background images: no label, no overlay, just the branded visual your event deserves.

What's New

The Homepage Builder's Buttons block now offers a third Display Mode option:

• Background image with Label — Your original choice; displays the image plus a button label
• Icon with Label — Icon-driven navigation with accompanying text
• Background image only — NEW; displays only the destination page's background image

When you select Background image only, each button shows exclusively the background image you've configured for its destination page — giving you total control over typography, spacing, and branding.

Why Organizers Will Love This

Homepage buttons are often the first interactive element attendees see. When they're constrained by mandatory labels, your design suffers. Image-only buttons unlock creative freedom — perfect for events where your visual identity matters as much as the navigation itself. Build a home page that's unmistakably yours.

💡 Pro tip: Use high-contrast, professionally designed images for your button destinations. Image-only buttons shine when the visuals do the talking — so invest in the photography or graphics upfront.

An exhibitor just bought a premium booth upgrade, a lead-capture license — that's the ideal moment to talk to them. Until now, there was no way to trigger a tailored email off a Marketplace purchase, let alone build one without leaving the extra's settings. That changes today: create a pre-filled Email Manager campaign in one click, and it sends automatically to every exhibitor who purchases the extra.

How it works

Spin up a campaign without ever opening a blank canvas:

1. Open the settings of any Exhibitor Marketplace extra.
2. Find the new section, "After purchase email Campaign"
3. Click Create campaign.
4. Swapcard generates a campaign named "Campaign for Marketplace - {Extra Name}", targeted at that extra, and drops you straight into its email settings.
5. Edit the pre-built blocks
6. Flip the status to Enabled when you're happy, and you're live.

Prefer to build from scratch?

There's a new "Extra Purchase" target in the Email Manager too. Pick it, choose one or more extras from the multi-select list, and your audience is set — combine it with the email content and timing of your choice.

Key behaviors & options

• Pre-filled, not pre-sent — every campaign is created Disabled by default, so nothing goes out until you've reviewed the copy and switched it on.
• Reaches the whole booth team — when an exhibitor purchases the extra, the email is sent to every exhibitor member attached to that company.
• "All-of" logic on multiple extras — select two or more extras and only exhibitors who bought all of them are targeted — perfect for bundle and upsell follow-ups.
• Stackable targeting — layer the Extra Purchase target on top of your existing targeting rules in the same campaign.
• Continuous or one-time — choose whether the email fires on every qualifying purchase or as a single send.
• No duplicate hunting — open an extra that already has campaigns and you'll see links to each one.
• Independent sends — several enabled campaigns can target the same extra, and each sends its own email.

Why organizers will love it

Marketplace extras are a core driver of exhibitor ROI — but the relationship shouldn't go quiet the second the payment clears. This feature turns every purchase into a moment of communication: onboard exhibitors into what they just bought, point them to the right resources in the Exhibitor Center, and upsell the next add-on, all on autopilot. You build it once from the extra itself, customize it like any other marketing email, and let Swapcard handle the timing — so exhibitors feel looked after and your team saves the manual campaign setup for everything else on event week.

For associations and membership-driven events, registration has always carried a manual tax: check whether someone's a current member, apply the right price, and hope the record you pulled was accurate. This integration removes that step entirely. Connect your membership data through Salesforce Flows, map the fields once, and registration validates members, applies the correct pricing, and keeps Salesforce in sync on its own.

Set It Up Once, Right in Your Salesforce Integration

Configuration is self-serve and Flow-driven — no custom dev per event.

1. Add your credentials. Enter your Organization Domain, Consumer Key, and Consumer Secret. All three are required — Save stays disabled until they're filled, and invalid credentials throw an inline error before you can go further.
2. Pick the processes to run. The integration now shows a list of available processes, each with a Type, Description, and Enable/Disable + Edit actions.
3. Map your Flows. For each membership process, select the Salesforce Flow you want to use, and Swapcard loads its inputs and outputs for you to map.

The process list covers three options:

• Registration (existing) — now toggled on or off directly from this list, with Edit routing to your familiar Salesforce Registration Settings.
• Membership Lookup (new) — validate membership status at registration.
• Membership Purchase (new) — connect the Flow that handles membership transactions.

Field Mapping That Speaks Both Languages

Selecting a Flow opens a clean, two-way mapping page so Salesforce and Launchpad stay perfectly aligned:

• Send Data — the fields Salesforce expects, shown read-only, each with a dropdown to pick the Launchpad field that feeds it.
• Return Data — the fields Salesforce sends back, each mapped to the Launchpad field that receives the value.
• No Flows available? You get a clear "There are no available Flows to be configured" message instead of an empty screen — and the data sections stay hidden until there's something to map.
• Nothing lost on the way out. Disabling a process keeps its saved configuration, reopening a configured process pre-fills every selection, and a failed save surfaces an error without wiping your mappings.

Real-Time Validation at Registration

The moment a registrant enters the flow, Swapcard queries Salesforce using your configured lookup identifier and pulls their membership type, status, and expiration date — no promo codes to chase, no spreadsheet to cross-check.

• Match found: their membership data and status are retrieved and ready to drive pricing.
• No match: the registrant is simply treated as a non-member and continues without friction.

Purchases and Renewals Flow Back to Salesforce

When a membership transaction is processed through registration, the details write back automatically — so your source of truth stays current without anyone re-keying data.

• The right data, only the right data. The payload carries registrant profile and membership product details — never financial information.
• A paper trail you can trust. The returned Salesforce Sales Order ID is stored against the registration.
• Failure never blocks a registration. If a write-back fails, it's logged and flagged for follow-up, and the attendee still completes registration uninterrupted.

One Report for Every Membership Transaction

A dedicated Launchpad report captures every membership transaction processed through the event — New Membership, Renewal, and Early Renewal — in one place.

• Everything in one row: registrant and contact details, Fonteva Contact/Member ID, membership type, transaction type, chapter, purchase amount, date, event, and Sales Order ID.
• Built for reconciliation: filter by transaction type, date range, or membership type; export to CSV or Excel; scoped to the current event by default.
• Nothing slips through: transactions where write-back failed show a blank/flagged Sales Order ID, so manual follow-ups are easy to spot.

Why Organizers Will Love It

Member pricing is where association registration gets messy — manual verification, mismatched records, and reconciliation headaches after the fact. This integration turns all of it into configuration you set once. Members get the right price automatically, your team stops fielding "am I a member?" tickets, and Salesforce stays the single source of truth without anyone copying data between systems. For membership-driven events, that's faster registration, cleaner revenue tracking, and member records that keep themselves honest.

💡 Pro tip: Have your Salesforce Consumer Key and Secret ready before you start — credentials are validated on entry, so setup is smoothest with your Salesforce connected-app details in hand.

💡 Pro tip: Map your Membership Lookup Flow first and run a test registration before opening the doors. Confirming that member pricing applies end-to-end takes minutes now and saves a scramble on launch day.