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.

Organizers now have more control and visibility over SwapAccess session scans directly in Studio.

Whether a scan needs to be added after the fact, moved to the correct session, or removed, you can now manage your session scan data directly in Studio.

You can now:

• Move individual or multiple scans between sessions.
• Add scans manually or via CSV import.
• Remove scans directly from Studio.
• View all scans for an attendee, including repeated scans 

These updates provide full visibility and control of SwapAccess session scan data directly in Studio.

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 meeting details page is where a lot happens: requests get accepted, schedules get juggled, teams get assigned, and attendance gets tracked. For a page this central to the networking experience, it was long overdue for a proper rethink.

The revamped meeting details page in the Event App now shows the right actions to the right people at the right time - dynamically adapting based on who you are in the meeting (requester, invitee, team member) and where that meeting is in its lifecycle.

How It Works

The page now has a clear, consistent layout split into two components: the meeting details card (participants, time, location, message) and a contextual options panel that updates based on meeting state. Here's what each role sees:

As an invitee receiving a meeting request:

• Accept or Decline the request
• Reschedule directly from the details page
• Connect Google Calendar to stay in sync

As the requester waiting on a response:

• Reschedule or Cancel the request
• Add participants or video conferencing
• Export to calendar without leaving the page

As a team member handling exhibitor meetings:

• Assign the meeting to a colleague (or reassign it)
• Full action set available for both unassigned and assigned states

Once a meeting is in the past:

• Requesters are prompted to confirm attendance — with three honest options: "I joined, and it was valuable," "I joined, but it wasn't valuable," or "It didn't happen"
• Once confirmed, the feedback is locked in and the page reflects it cleanly

Key Behaviors

• Context-driven actions: The options panel only surfaces actions that are relevant to your role and the current meeting status. No clutter, no confusion.
• Google Calendar sync: Available across virtually every meeting state, so attendees can always connect their calendar regardless of where the meeting stands.
• Canceled, rescheduled, and expired: The page still renders cleanly for these states, offering calendar options without surfacing irrelevant actions.
• Multi-participant meetings: Invitees in group meetings can reschedule, add participants, export to calendar, or decline - and if they've declined, the page reflects that clearly.

Why This Matters

This revamp makes the meeting details page feel intelligent. It reduces friction at every stage of the meeting lifecycle, from the first request to the post-meeting attendance confirmation. For exhibitors managing high volumes of meetings across a team, the clearer assignment flow alone is a meaningful upgrade.

It's also built to scale - the new architecture makes it far easier to extend the page as the meetings feature evolves.

💡 Pro tip: Encourage exhibitors to use the post-meeting attendance confirmation as part of their follow-up workflow. The "valuable / not valuable / didn't happen" signals feed directly into ROI tracking and can help teams refine their meeting strategies across events.

Networking at events lives or dies by how easy it is to make the first move. If requesting a meeting takes too many taps, too much scrolling, or too much guesswork, attendees simply won't bother.

The meeting booking experience on attendee and exhibitor profiles has been fully redesigned. The Meet button is now the primary action on every profile: highlighted, prominent, and impossible to miss, if meetings are set up in the event. Time-slot selection has been moved out of the profile view entirely, keeping the page clean and focused on connection.

What's Changed

On Exhibitor Profiles

The exhibitor details page now leads with a clear action pair: a bold, highlighted Meet button alongside a Bookmark button. Time slots no longer clutter the header: visitors see the exhibitor story first, then take action.

Meet button highlighted: shown prominently when meetings are authorized for that exhibitor

• Bookmark: always available, sits cleanly alongside Meet
• Meet grayed out: when a meeting request has already been sent
• Meet hidden: once the attendee has reached their meeting request limit (5), only Bookmark remains

On Attendee/Person Profiles

The person's details page follows the same logic, with Meet taking priority over Connect.

Meet highlighted, Connect secondary: when meetings are authorized between the two participants

• Meet highlighted only: when already connected with that person
• Meet grayed out: after a meeting request has been sent (up to 5 times)
• Meet hidden: once the 5-request limit is reached
• Pending states: incoming meeting and connection requests surface directly on the profile with inline Accept/Decline buttons, replacing the old invitation and pending indicators

How It Works

1. Open any attendee or exhibitor profile in the event app
2. Tap the Meet button, it launches the meeting booking flow directly
3. Select participants, choose a time slot, and send the request
4. The button state updates automatically to reflect the pending or confirmed status

Why Organizers Will Love It 💚

More visible meeting CTAs mean more meetings booked. It really is that simple. When participants see a clear, highlighted action the moment they land on a profile, they engage, which translates directly into more networking activity, more exhibitor interactions, and stronger event ROI.

Cleaning up the profile view also means attendees spend less time confused and more time connecting. The removal of time slots from the header reduces cognitive load at the exact moment participants are deciding whether to reach out.

💡 Pro tip: This update works alongside your existing meeting authorization settings in Studio. If meetings aren't enabled for a specific group or exhibitor, the Meet button won't appear, so your per-event networking configuration stays fully in control.

💡 Pro tip: The 5-meeting request limit per person is a built-in guardrail that keeps networking quality high. Participants who've maxed out on requests to a specific attendee will see only the Connect option, encouraging them to broaden their networking rather than spam a single contact.