2026.01: AI assistance

Unless mentioned otherwise, the below updates will be available starting January 13, 2026.

Onomi 360

AI assistance (v1.0)

AI assistance in Onomi 360 takes repetitive work off the people who request, approve, and run events. Every feature in this release follows the same rule. Each AI output is presented for review, applied only on a human's confirmation, and logged. You can trace what was suggested, where, and what the human decision was. AI-powered field mapping for optical badge scanning and AI-generated closed captions with live audio translation are already available in the platform today. See Save time capturing leads onsite with automatic AI-powered field mapping for optical (OCR) scanning and Live session closed captions and simultaneous translation capabilities.

New

AI-assisted request intake. Requesters describe the event they need in plain language. The AI fills the request form from that description, and suggests dates with explained trade-offs. Those trade-offs are conflicts with other planned events on your organization's portfolio calendar, public holidays for the meeting country, and attendance baselines from comparable events. Where a speaker program is involved, the engagement counts the request form's faculty step holds for each speaker are a further input (Available March 3, 2026). The requester reviews the prefilled form, adjusts anything, and submits. Nothing is sent on their behalf.
Approver summaries and risk flags. Approvers see each incoming request with a generated summary and risk flags. A pending queue is read from the summaries rather than from each full record. The decision stays with the approver. The AI never approves, declines, or advances a request.
Natural-language questions over portfolio data. You can ask natural-language questions over your event and portfolio data, and get answers on demand. Understanding your program no longer waits on a report build.
Writing assistance. Drafts event communications, such as invitations and reminders, in your tone of voice, ready for your review before anything is sent (Available February 3, 2026).
Attendance forecasting. See attendance forecasts built from historical baselines for comparable events (Available February 3, 2026). Forecasts are shown with the baseline they draw on, so you can judge them against your own knowledge of the program. Both the baseline and the forecast rest on the registration journey. A meeting run as record-only takes no registrations, is no comparable for another event, and gets no forecast at all. Its panel says so in a message of its own, distinct from the not-enough-history state a meeting backed by a workspace sees when fewer than three comparable events are available.
Translation drafting for a new portal language. Your administrators add a language in Onomi 360 under Policies > Languages. It arrives as a complete draft of both key sets, rather than as an empty column (Available February 3, 2026). Those key sets are the meeting request portal strings and the lifecycle notification templates. None of the draft is live. A string reaches a requester only when a reviewer accepts or edits it. Until then it falls back to your organization's default language, so a machine translation never reaches a requester unreviewed. Coverage counts reviewed strings rather than drafted ones. Every acceptance and edit is recorded with the reviewer and the date, so you can show who approved the wording a market sees.
Your models, your governance. AI features in Onomi run on enterprise model infrastructure: Claude models and OpenAI models available through AWS Bedrock. The provider and models your organization runs on are agreed with your SpotMe team, and are visible to your administrators in Onomi 360 under Policies.

Important: AI features are optional. The Onomi 360 assistance features are enabled at the organization level. The capture features in the event workspace keep their own enablement: badge-scan field mapping per workspace, captions per session. AI never acts without a human decision where HCP data or compliance outcomes are involved. To enable AI assistance, please contact your SpotMe Account Manager.

For the reporting views these questions draw on, see How to use Onomi 360: the portfolio calendar, engagement view, and reports. For an overview and step-by-step setup, see How to use AI assistance in Onomi 360.

Onomi 360 (v1.2)

This release delivers the event, registration, attendance, and engagement data your event workspaces hold into the data platforms your analytics team works in. It runs on the Analytics API, with no manual export step in between. The strategic meetings management records are not carried on that API. Each is read in Onomi 360, on the program-layer report, Event requests, or the event record module that holds it. See How to use Onomi 360: the portfolio calendar, engagement view, and reports and Integration patterns: connecting Onomi to your enterprise systems.

New

Live feeds to your data platforms. Scheduled structured exports deliver recurring extracts without an engineer in the loop. Live feeds add incremental delivery into your data platforms, including Snowflake, as the data changes. Operational dashboards run on current data instead of on the last export. Both work against a documented schema, so your BI team models event and engagement data next to the CRM and omnichannel data already in your warehouse. What happens after delivery, which models get built and which joins are made, stays with your team.

Note: Live feeds run on the Analytics API, which is enabled per organization. Please contact your SpotMe Account Manager. For the data model, the access scopes, and how a BI tool connects, see the Analytics API and Integration patterns: connecting Onomi to your enterprise systems.

Modules

Universal lead capture

Fixes

Automatic field mapping for optical scanning: a badge printing the institution across two lines put its second line in the company field.
Automatic field mapping for optical scanning: a representative's manual correction was overwritten when the same badge was scanned again in the same capture session.

Live sessions