Sherlock is only as useful as the number of people who know to ask it something. Now the email manager can do that job for you: two ready-made blocks nudge attendees, exhibitors, and speakers straight to Sherlock, on WhatsApp or in the app, with zero copywriting on your end.

What's new

Two pre-built blocks are now available in the email manager:

1. Sherlock on WhatsApp: drops a subject, body, and "Chat with Sherlock" CTA straight into any email.
2. Sherlock in-app: same idea, but the CTA ("Discover Sherlock") opens the event in the app with Sherlock already launched.

Both blocks come fully written. All you add is the link.

How it works

1. Open any email in the email manager and browse the block library.
2. Add either the Sherlock on WhatsApp or Sherlock in-app block (or both).
3. Drop in the required link: your WhatsApp conversation link for the WhatsApp block, or the event deep link for the in-app block.
4. Send. Clicking the CTA takes attendees directly to the WhatsApp chat or into the app with Sherlock open.

💡 Pro tip: Leave the link field empty and Swapcard won't let you save or send, an inline error flags it immediately so a broken CTA never reaches an inbox.

Key behaviors

• Pre-written, pre-translated copy: Subject, body, and CTA are ready to go, no drafting needed.
• One required field per block: Just the WhatsApp link or the deep link, nothing else to configure.
• Validation built in: Missing link = blocked send, with an inline error on the block itself.
• Smart defaults:If Sherlock (or Sherlock on WhatsApp) is enabled for your event, the block is automatically added to key campaigns:
  • "It's almost go-time! Are you ready?" (attendees)
  • "Qualified prospects are waiting to meet you!" (exhibitors)
  • "Want to see who's attending your session?" (speakers)

Why organizers will love it

Awareness is the bottleneck for any AI agent, and now it's solved before you even open the email builder. These blocks turn every campaign into a Sherlock touchpoint automatically, no extra effort, no extra emails to design. More attendees discover Sherlock, more conversations happen, and your AI Agent actually earns its keep.

Attendees live on WhatsApp. Now Sherlock can meet them there, without your organization's name disappearing behind Swapcard's. If you run branded apps, you can request a dedicated WhatsApp number, connect it through Meta, and put Sherlock to work answering attendee questions right where they already are.

How it works

1. Request a number. From WhatsApp sender settings, organization admins submit a request form with the phone number's country and legal entity. Customer Success reviews it and assigns a number once approved.
2. Connect via Meta. Click "Add WhatsApp account," then "Connect with Meta" to launch Meta's embedded signup. Enter your number, grab the verification code Swapcard displays, and drop it into the Meta popup to confirm.
3. Bind it to your app(s). Pick which branded application(s) this WhatsApp account should serve: attendees on that app will see Sherlock respond from your number.
4. Manage it anytime. Every linked application shows its phone number alongside Copy URL, Copy phone number, and Download QR code actions, plus an Edit option to change bindings on the fly.

Key behaviors

• One number, multiple apps: a single WhatsApp account can serve several branded applications at once.
• Built-in guardrails: no branded app yet? The request button greys out with a banner pointing you to create one first. Try to save with zero apps selected, and you'll get a clear validation message instead of a silent fail.
• QR codes on demand: download a ready-to-share QR code for each linked app, perfect for on-site signage or booth collateral.
• Clean teardown: deleting a WhatsApp account removes it and all its app bindings in one confirmed action.

Why organizers will love it

Branding isn't just a logo, it's every touchpoint attendees have with your event, WhatsApp included. This closes the gap between "attendees want to message us where they already are" and "our support has to live inside one app." Now it doesn't.

💡 Pro tip: Have the Meta Business account details and your legal entity info ready before you start the request, it's the single biggest thing that slows approval down.

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.

No more bouncing between the chat and the full-page map. Sherlock now shows exhibitors, sessions, and venue facilities exactly where they are, and gets attendees there, without ever closing the conversation.

What's new

Ask Sherlock for a location, and it answers with an actual map, not just text:

• "Show me the event map" → Sherlock drops an embedded ExpoFP map preview right into the chat, level selector included.
• "Where's the AWS booth?" → the preview opens zoomed in and pinned on that exact spot.
• "Where are the Chinese exhibitors?" or "What's in Hall 5?" → the relevant hall or zone lights up, with the matching exhibitor list alongside it.
• "How do I get from Hall 3 to Hall 4?" → Sherlock asks where you're starting from, then draws the route straight to your destination.

Key behaviors

• Pinch, zoom, pan: the embedded map behaves like the real thing, without hijacking the conversation's scroll.
• Closest match first: ask about several exhibitors or sessions at once, and Sherlock pins the closest one to you first (or the first one found, if it doesn't know where you are).
• No dead ends: if a location or route doesn't exist on the map, Sherlock says so instead of showing a blank or broken screen.
• Smart reuse: once the map has loaded in a session, Sherlock reuses that instance instead of reinitializing it every time.
• Open map button: every map reply comes with a one-tap way out: on web it opens full-page alongside Sherlock; on mobile, Sherlock steps aside and the map goes full screen.

Why organizers will love it

Fewer "where is..." messages bouncing between attendees and your help desk, and a much smoother onsite experience overall. Attendees get answers without breaking their flow, exhibitors get found faster, and your floor plan finally works as hard as your AI assistant does.

💡 Pro tip: This release covers single-destination directions. Multi-stop itineraries (visit A, then B, then C) and full route optimization across a wishlist aren't in scope yet, but the groundwork's there for it.

Plans change on-site all the time: a room gets double-booked, a booth gets reshuffled, someone realizes the meeting really should happen near catering. Until now, fixing that meant canceling the whole meeting and starting over, which reset every participant's RSVP and forced everyone to re-confirm from scratch. Not anymore: organizers and attendees can now edit a meeting's location directly from the Event App, on web and mobile, without touching anyone's status.

How It Works

1. Open the details page of any pending or confirmed meeting.
2. Tap Edit location.
3. Pick a new spot from everything available for that time slot, locations and exhibitor booths included, filtered by your meeting rules and permissions.
4. If you're changing to a new location, you'll land on the description step with the existing text already carried over.
5. Save. The meeting page reloads instantly with the updated location.

Key Behaviors & Options

• Statuses stay untouched: confirmed stays confirmed, pending stays pending. Editing a location no longer resets anyone's acceptance.
• Smart filtering: only locations actually free for that time slot and covered by your active meeting rules show up in the picker: no dead ends, no double-booking someone else's slot.
• Automatic notifications: every participant gets a "meeting updated" alert with the old location struck through and the new one front and center, so nobody shows up in the wrong place.
• Built-in guardrails: Save stays greyed out until you actually pick a different location, and if the meeting gets canceled or slips into the past while the page is open, the Edit location button quietly disappears.

Why Organizers (and Attendees) Will Love It

Canceling and rebooking a meeting over a simple room change used to torch attendance confirmations and generate a steady trickle of "why do I have to accept this again?" tickets. Now a location change is just... a location change. Everyone's calendar reflects reality, nobody loses their RSVP, and support stops fielding tickets that were never really about scheduling in the first place.

💡 Pro tip: Review your meeting rules before the event starts. Locations only appear in the picker when they're covered by an active request rule, so tightening those up front means smoother edits once things get busy on-site.

💡 Pro tip: If a location edit shows an error, it means nothing's available for that time slot under the current rules, try a different slot or loosen the rule's location scope rather than canceling the meeting outright.

Organizers can now customize the confirmation page displayed to attendees after they submit a registration that requires approval.

Previously, attendees who registered for moderated tickets always saw a standard confirmation message while their registration awaited review. With this update, organizers can tailor this experience to provide clear next steps, set expectations, and reinforce event branding.

Using the same editor as the existing Registration Confirmation page, organizers can customize:

• Title
• Description and body text
• Image
• Text formatting and other supported content

This provides a consistent editing experience while allowing you to create a more informative and personalized confirmation page.

An Account Email is a user's identity on your event — the key to their login, their history, their profile. Until now, a single stray cell in a People Excel import could quietly change it. One wrong value, one accidentally cleared field, and an existing attendee's Account Email was overwritten. That door is now closed. The People Excel import rejects any row that would change or clear the Account Email of an existing user, and tells you exactly which rows were blocked and why.

What's new

The People Excel import now validates the Account Email column against your existing users. If a row matches an existing user but carries a different Account Email — or leaves the cell empty — that row is rejected before it can touch the account. Everything else imports as usual.

Key behaviors

• Same email, no problem: rows that match an existing user and keep their current Account Email pass straight through, exactly as before.
• Changed email, rejected: any row attempting to set a different Account Email on an existing user is blocked and counted in the import modal's Errors.
• Empty email, rejected: a blank Account Email cell on an existing user is blocked too — no accidental wipes.
• Nothing else gets touched: when a row is rejected, none of that user's other fields are modified. The whole row is skipped cleanly.
• New users unaffected: rows whose ID doesn't match an existing user flow through normally — onboarding new people works exactly as it always has.
• Mixed files still work: in a file with both valid and invalid rows, only the offending rows are excluded. The rest are processed without interruption.

In your results CSV

Download the results and every blocked row is spelled out for you:

• Each rejected row appears with an ERROR status.
• The error column reads: "You cannot change the Account Email of an existing user."
• The row and id columns pinpoint the exact source row and record, so fixing the file takes seconds.
• Other error types keep their own distinct messages — you can tell issues apart at a glance.

For a long time, the Exhibitor Center and the Web Event App looked and behaved like two different products — different top bars, a stray home icon, and that jarring moment when switching between them launched a brand-new browser tab. Exhibitors noticed. Many didn't even realize the Exhibitor Center existed. We've unified the two into a single, coherent experience: same top bar, same navigation logic, same tab.

What's new

The Exhibitor Center top bar is now built from the exact same components and design as the Web Event App — same height, fonts, colors, and spacing. Stand them side by side and the only difference an exhibitor will spot is that the EC hides the notifications and messages icons.

How it works

The new top bar gives exhibitor members three ways to move around, all without leaving the tab they're in:

• Event / Exhibitor Center toggle — a pill-style switch sits in the center of the bar. One click moves between the live event app and the Exhibitor Center, in the same tab, with the browser back button working exactly as expected. Only exhibitor members with EC access see it — regular attendees never do.
• Event switcher dropdown — clicking the event name opens a dropdown of every event the member has access to, split into Upcoming / Current and Past events, each row showing the event name and date, with a checkmark on the active one. This replaces the old standalone EC event-list page entirely.
• Switch exhibitor — members tied to more than one exhibitor company at the same event get a Switch exhibitor option in the sidebar, complete with company logos, so they can hop between booths without logging out and back in.

Key behaviors

• Unified profile dropdown — the avatar menu in the EC now mirrors the Event App exactly: profile, Edit profile, Settings, Contact Support, Interface language, Resource center, Plan an event, Legal, and Log out. Logging out signs the member out of both surfaces at once.
• No more orphan pages — direct access to the deprecated EC root event list now redirects to the member's most relevant event.

Why organizers will love it

Navigation and UX complexity has consistently ranked as a top exhibitor pain point — "clunky," "over-complicated," "two environments when one would do." Fragmentation between the EC and Event App was the headline complaint. By making the two feel like one application, you remove the friction that kept exhibitors from discovering and using the Exhibitor Center in the first place. The payoff: better exhibitor adoption, fewer "where do I go?" support tickets, and stronger exhibitor satisfaction and ROI — without you touching a single setting.

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.