Skip to main content

    Filter by idea status

    Filter by product

    186 Ideas

    Kurtis StewartParticipant

    Bulk Room Creation and Editing via CSV Import/Export for Large ConferencesOpen to voting

    The challengeOur organization, the Vancouver Island Economic Alliance (VIEA), has used Slido's Professional one-time license for our annual Economic Summit in 2024, 2025, and 2026.Each year, we manage 20+ conference sessions across multiple rooms, with schedules, room assignments, and session details changing throughout the planning process.Currently, creating and modifying rooms individually is time-consuming, particularly when managing a large conference with concurrent sessions that have adjustments right up until the last minute.Suggested improvementIntroduce bulk room creation and editing functionality, ideally through CSV import/export, allowing organizers to: Create multiple rooms and configure their details in a single upload. Export existing configurations to make changes in a spreadsheet. Reimport updated configurations without manually editing each room. Reuse or adapt configurations from previous events. Why this mattersThis would be particularly valuable for organizations running large annual conferences using one-time Professional licenses.Although we're repeat customers, our event configurations change significantly each year. Unlike organizations running recurring events with consistent setups, we're effectively rebuilding our conference structure annually.Bulk management would reduce administrative overhead, minimize manual entry errors, and make Slido considerably easier to scale for complex, multi-session conferences.The goal: Spend less time configuring Slido and more time delivering a great attendee experience.

    a_userContributor

    Remove the Report Download Restriction for Large Slido EventsOpen to voting

    I’d like to request that Slido remove the restriction that prevents customers from downloading reports directly when an event is considered “large.”For smaller events, we can download our reports ourselves without an issue. However, once an event reaches Slido’s large-event threshold, that self-service capability is no longer available and we have to open a support case to obtain the reports.For a large global organization, large events are not an exception. They are a normal part of how we use Slido.This creates a frustrating situation where the events with the greatest visibility and largest audiences are the ones where we have less access to self-service reporting.It also creates a real business impact. Leadership often wants event analytics shortly after an event concludes. With a smaller event, I can provide those results immediately. With a larger event, I have to explain that I cannot download the reports myself and that we are waiting for Slido Support to retrieve them for us. In our experience, that can mean waiting a day or two.The current experience is essentially:Smaller event → Download reports → DoneLarge event → Cannot download reports → Open support case → Wait → Answer questions back and forth due to confusion from support → Support generates reports → Receive reports → Provide results to leadershipFor enterprise customers running large-scale events regularly, that should not be the workflow.If generating reports for large events requires additional processing, I completely understand that. But that processing should happen within the product, rather than requiring intervention from the support team.For example:Generate Report → Processing → Report Ready → DownloadThis would benefit everyone. Customers would receive their data faster, Slido Support would receive fewer tickets for report retrieval, and enterprise customers would have a consistent reporting experience regardless of event size.Event size should affect how long a report takes to generate, not whether the customer can generate it themselves.Please consider making report generation fully self-service for large events. For enterprise customers, this would be a meaningful improvement to the Slido experience.