The new Exhibitor/Personal Toggle on the mobile Me tab helps your exhibitors seamlessly manage their dual roles as both active booth representatives and event attendees.

Instead of digging through menus to find the Exhibitor Center (EC) while on the move, exhibitors can now toggle instantly between their personal event experience and critical booth management tools directly from the main navigation.

What’s New? 🚀

We’ve redesigned the mobile Me tab specifically for users registered as exhibitors. They now have a clean, intuitive toggle at the top of their screen to swap between two distinct views:

• Exhibitor View (Default): Surfaces direct shortcuts to high-value Exhibitor Center actions like lead retrieval, contact scanning, and booth meetings.
• Personal View: Preserves the classic personal navigation they need as an attendee, including their personal contacts, scheduled sessions, and bookmarked items.

(Note: The toggle is smart. Standard attendees who are not registered as exhibitors will continue to see their regular, uncluttered Personal view without any distracting buttons.)

How It Works & Key Benefits

⚡ Permission-Based Shortcuts

Exhibitors will only see the shortcuts they actually have rights to use. If an exhibitor's plan doesn't include lead retrieval, that shortcut is dynamically hidden rather than greyed out, keeping their mobile workspace clean, focused, and highly relevant.

🛍️ Ubiquitous Marketplace Access

If you have enabled the event marketplace, your exhibitors will be able to access it from both the Exhibitor and Personal tabs. Whether they are shopping for solutions as an attendee or looking for partner tools as an exhibitor, the marketplace is always just one tap away.

🔒 Graceful Access Control

If you ever need to restrict or block an exhibitor's access, the app handles it gracefully:

• The toggle automatically defaults to the Personal tab.
• The Exhibitor tab is visually disabled.
• Tapping the disabled tab triggers a friendly message: "[Exhibitor Center Name] is currently unavailable," ensuring the user is informed without disrupting their personal event experience.

Why This Matters for Organizers

• Boosts Exhibitor ROI: Putting lead retrieval and meeting shortcuts on the most-frequented mobile screen means exhibitors scan more badges, book more meetings, and stay on top of their pipeline.
• Reduces Friction: Dual-role users no longer have to log out or navigate complex menus to switch contexts. They can represent their company and enjoy the event as an attendee simultaneously.
• Fewer Support Tickets: Clear visual states and automatic permission handling mean fewer confused exhibitors asking where their tools went.

Changes to a registration now reach your external tools automatically. When someone registers, cancels, gets approved or is declined, Swapcard sends an update through webhooks and Zapier. Each update also shows whether the registrant has paid or still has a balance due.

What's Changing

Until now, registration changes stayed inside Swapcard. If someone cancelled, your CRM didn't know. And there was no way to see who had actually paid without exporting lists by hand.

Now your connected tools, such as HubSpot, stay up to date on their own.

How It Works

• Automatic updates. Your connected tools are notified whenever a registration is confirmed, pending approval, rejected, cancelled or abandoned.
• Payment visibility. Each update shows whether the registrant has paid in full or still owes a balance.
• Ready in Zapier. Registration and payment status can be used in your Zaps to filter, map and sync them to your CRM.
• No setup changes. This works with your existing webhooks and Zaps. Nothing breaks.

💡 Pro tips

• Add a filter to your Zap, for example only cancellations, so that just the updates you need reach your CRM.
• Use payment status to build follow-up lists of registrants with a balance due.

Until now, the "Add member" button in the Exhibitor Center had one behavior for everyone — and for exhibitors who weren't allowed to add members manually, that meant a button that led nowhere. No path, no link, no explanation. That's fixed. The button now reads each exhibitor's permissions and your event's registration setup, then offers the method that actually applies to them. And organizers get a new exhibitor-specific registration link in Studio to steer people to the right place.

What's new

Two connected changes, one cleaner flow:

• A dedicated exhibitor registration link in Studio. When your event uses External Registration, Registration Settings now shows a new Exhibitor member registration link field — separate from your attendee link.
• A renamed attendee link. The existing attendee registration link is now labeled Visitor Registration link, so the two entry points are impossible to confuse.
• An adaptive "Add member" button. In Exhibitor Center → Team Members, the button now changes its behavior based on the exhibitor's permission and the registration method available to them.

How it works (for organizers)

1. Go to Studio → Registration → Registration Settings.
2. Select External Registration.
3. Fill in the new Exhibitor member registration link — this is the external page exhibitors will send their team to.
4. Note that your attendee link now reads Visitor Registration link.
5. Save. The value applies event-wide (one link per event), and it's kept even if you later switch External Registration off.

Admins, community managers, and event managers can all edit and save the link.

What the button does now (for exhibitors)

The "Add member" button reads the situation and adapts:

• Add from your attendees — if your booth is allowed to add registered members, clicking opens a modal to search the event's attendee list and add someone directly.
• Share your in-app registration link — if the event uses in-app registration and your booth can register members, the modal shows your booth's unique registration link, ready to copy or open in a new tab.
• Share the external link — if the event uses External Registration and an organizer has set the exhibitor link, the modal surfaces that link to copy or open.
• Mix and match — when you can both add attendees and have a link available, the modal does both in one place: search-and-add on top, link to share underneath.

Your event app was never the only place people look for answers: some guests never install it, some just want a quick check before they commit to downloading anything. Until now, Sherlock couldn't follow them there. That gap closes today: enable guest mode, grab an embed snippet from Studio, and Sherlock shows up wherever you already have a website.

What's New

• One toggle, one snippet: turn on Guest mode for Sherlock in Studio and an embed code section appears, giving you a copyable snippet scoped to your event.
• Guest-scoped answers: Sherlock only draws on content you've explicitly marked "available for guests" in Studio. Nothing else leaks through.
• White-label aware: "Powered by Swapcard" shows on standard events and disappears automatically if your event is white-labeled.
• Fresh start, every time: no conversation history carries over between visits, so every session starts clean.

How It Works

1. Open the AI Agent page in Studio with Sherlock enabled.
2. Turn on Guest mode: the embed code section unlocks.
3. Copy the snippet; it's already scoped to your event.
4. Paste it into your website.
5. Mark the content you want Sherlock to use as available for guests in Studio, so it has something to answer with.

Key Behaviors & Options

• Scoped content only: even with the widget live, Sherlock will only ever surface guest-accessible content; anything not marked for guests stays out of the conversation entirely.
• Feedback built in: the same suggestions, app-support answers, chat, and thumbs up / thumbs down controls guests get in the app carry over to the embedded widget.
• No content marked yet? No problem, sort of: the embed still generates and works technically, but Sherlock won't have anything to answer with until you flag content as guest-available.

Why Organizers Will Love It

Your website is real estate you already own and control, and now it can answer attendee questions before they've even considered the app. It's a lower-friction first touchpoint for prospects browsing pre-event, and a safety net for onsite guests who'd rather not install anything. Same AI agent, same guardrails on what it can share, just meeting people where they already are.

💡 Pro tip: Mark your guest-accessible content in Studio before you flip on Guest mode, an embedded Sherlock with nothing to say is a rough first impression.

💡 Pro tip: This is a great addition to a pre-event landing page, let prospects get quick answers about the event without the "download our app first" wall.

We've introduced configurable service fee handling, giving organizers more flexibility in how service fees are applied to ticket purchases.

Organizers can now choose, on a per-ticket basis, whether to:

• Absorb Fee (default): The service fee is included in the ticket price and paid by the organizer.
• Pass on to Registrant: The service fee is added to the ticket price at checkout and paid separately by the registrant.

When the Pass on to Registrant option is selected:

• The checkout order summary displays the ticket price, tax (if applicable), and service fee as separate line items.
• Organizers can choose whether refunds include the service fee or retain it, by processing a full or a partial refund (where the service fee can be calculated and retained).
• Service fee details are reflected throughout Studio, transactions, and invoices for greater transparency.

Note: The default behavior remains unchanged. Existing tickets continue to absorb the service fee unless updated, and any changes apply only to future purchases.

Attendees have always used the News Feed to thank a speaker, call out a great conversation, or tag the people they met at the booth. The problem: the person being talked about had no idea. Their name sat in plain text, buried in the feed, with nothing pointing them to it. Mentions fix that. Type "@", pick the person, publish, and they get a notification that takes them right to the conversation.

How it works

1. Write a post or a comment. On the web event app, open Write a post in the News Feed, or reply to an existing post.
2. Type "@" and start typing a name. A dropdown of matching event participants appears, each with their name and job title, and narrows as you type.
3. Pick the person. Their name drops into your text as a highlighted mention.
4. Publish. The mentioned participant receives a notification in the event app.
5. They open it, and they're there. The notification takes them straight to the post, so they can react, reply, or reach out.

Key behaviors

• People only. Mentions point to event participants: attendees, speakers, exhibitor team members, anyone with a profile in the event.
• Posts and comments. Mention someone when you start a conversation or when you jump into one.
• Mentions are clickable. Anyone reading can click a mention to open that person's profile, a one-click path from "who's that?" to a connection request.
• One post, one notification. Mention the same person three times and they still get exactly one notification. Enthusiasm, not spam.
• No self-pings. Mention yourself and nothing fires.
• No match, no mention. Type "@" followed by text that doesn't match any participant and it simply stays plain text. No broken tags, no errors.
• On by default, nothing to configure. Mentions are live on every event's News Feed. There's no setting to switch on, or off.

Why organizers will love it

A News Feed only feels alive when people talk to each other, not just at the room. Mentions turn one-way posts into conversations with a clear recipient: the speaker actually sees the thank-you, the contact actually sees the follow-up, and the mentioned person has a reason to come back into the feed and reply. That's more audience engagement on the posts you already have, plus a built-in bridge from the feed to profiles, and from profiles to networking.

💡 Pro tip: Get the ball rolling yourself. Publish a welcome post on day one that mentions your keynote speakers or session hosts. Each of them gets notified, most will jump in to reply, and attendees see what a mention looks like before they try their first one.

On web, Sherlock was easy to miss and a little cramped — a small window that either got in the way of the page or hid where no one looked. Now it opens as a proper side panel that sits alongside your content instead of on top of it. Participants get their AI concierge exactly where they expect it, without losing sight of the session, exhibitor, or profile they're browsing.

What's new

Sherlock now lives in a dedicated side panel on the Web Event App and the Exhibitor Center. It's open by default the first time you land, so participants notice it without hunting for a button — and it's resizable, so everyone can set the width that suits their screen and reading habits.

Key behaviors & options

• Open by default — on first load with no saved state, Sherlock is already there, ready to answer. No searching, no tiny launcher to spot.
• Respects your choice — close it manually and it stays closed for the rest of the session, even on reload. Open-by-default only kicks in when there's no state yet.
• Resizable panel — drag to adjust the panel width within a set range, so Sherlock never crowds the content you're actually working with.
• Reading-direction aware — in left-to-right languages the panel sits on the right; in right-to-left languages (like Arabic) it flips to the left, matching the natural layout.
• Persistent across surfaces — move between the Event App and the Exhibitor Center and Sherlock holds its open/closed state and your active conversation, with no reload or flicker. Your context follows you.
• Mobile untouched — the native iOS and Android apps keep their current Sherlock experience; this update is web-only.

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.

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.