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.

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.