Everything you need to run a great event.

EventisLive is a platform for running events of any size, anywhere in the world. As an organizer, you create an event from your dashboard, get a public landing page at eventislive.com/e/your-slug, and manage everything — schedule, speakers, tickets, sponsors, the live audience experience — from one place. Attendees find your event through its public page, join the live experience, and (where enabled) buy tickets or merchandise. Admins you add to an event share management access, and vendors can list in the marketplace and capture leads at events that turn that on.

Everything runs in the browser from your dashboard. Your event page is live the moment you create it and the audience experience (messages, Q&A, polls, the participants wall) updates in real time. You don't need to install anything to organize.

• A public event page — your hero, description, schedule, speakers, and any features you enable, shareable by link.
• A live audience experience — a real-time space attendees open during the event for messages, Q&A, polls, and more.
• A six-character event code — a stable identifier auto-generated for every event, used by the companion apps to join.
• À-la-carte features — ticketing, certificates, a call for papers, sponsor lead capture, and more, switched on per event.

From your dashboard, start a new event at /dashboard/events/new. The wizard is two short steps — Essentials then Details — and the heading says it plainly: *you can change everything later.* Your progress is saved in the browser as you go, so a refresh won't lose your work.

1. 1

   Fill in the essentials

   Step 1 collects the Event name (required), the Event URL slug (required — auto-filled from the name as you type), an optional Short description (up to 200 characters, used in listings and previews), a Category (required), the Start and End date/time (required; end must be after start), and a Timezone (defaults to yours — attendees see event times in this zone).

2. 2

   Add the details

   Step 2 is optional polish: a wide Cover image (upload up to 10MB, or paste a URL; ~1920x900 works well), Location and Country, an Event hashtag for sharing, and an About section with a rich-text editor for the full pitch — agenda, speakers, what to expect.

3. 3

   Set visibility and publish

   Choose Public or Private, then choose Publish immediately or Save as draft. If you belong to an organization that can host events, a Create under picker lets you attach the event to that org (or keep it personal — you can move it later).

4. 4

   Create the event

   Click Create event (or Save draft). Your event is created with a public page and event code, and you'll be taken into the event dashboard to keep building.

Visibility controls who can discover your event. A Public event is listed in the EventisLive events directory for anyone to find and join. A Private event is link-only — it never appears in the directory, and only people you send the link to can reach its page. Pick whichever fits in the wizard's Visibility step; you can flip it anytime from the event dashboard.

Separate from visibility is the publish status. A draft event's public page is hidden from everyone except you and your event admins, so you can stage a private rehearsal of the real page before launch. Publishing makes the page reachable (subject to the visibility setting above).

Every event also gets a unique event code — a six-character code like K7M9PQ, generated automatically at creation. It deliberately leaves out look-alike characters (no I, O, 0, or 1) so it's easy to read aloud and type. On the web, attendees reach your event by its link or the directory; the event code is the stable identifier the companion apps use to look an event up and join it directly.

Your event lives at eventislive.com/e/<slug>. The slug is generated from your event name as you type — lowercased, with spaces and punctuation collapsed into single hyphens — but you can edit it to whatever you want. For example, Barcamp Kumasi 2026 becomes barcamp-kumasi-2026.

• Allowed characters: lowercase letters, numbers, and single hyphens between words (the rule is ^[a-z0-9]+(?:-[a-z0-9]+)*$).
• No leading, trailing, or doubled hyphens, and no spaces, capitals, or symbols — these are stripped or rejected as you type.
• Globally unique: the wizard checks availability live as you type and shows a green check when the slug is free, or flags it if it's already taken.

Creating an event is free — the wizard's summary shows the cost to create as Free, and that includes the live audience experience, your public page, the schedule, speakers, the participants wall, Q&A, and a free capacity baseline of 100 attendees per event. You only pay when you outgrow the baseline or want a premium add-on.

Premium features unlock à la carte from inside the event dashboard once the event exists. Each is a one-time unlock priced per event, in your local currency (the catalog is denominated across USD, GHS, NGN, EUR, and GBP):

• Higher capacity — raise the attendee cap beyond 100 in tiers up to Unlimited.
• Call for papers (CFP) — collect, review, and vote on speaker submissions.
• Sponsor lead capture — let sponsors and exhibitors scan attendee badges to capture leads.
• Apple Wallet passes, broadcast emails, custom branding, the flyer generator, and an analytics dashboard — each unlocked per event as you need it.

Here's the fastest path from a blank dashboard to a shareable, live event page.

1. 1

   Sign in and start a new event

   Open the dashboard and click into Create event.

2. 2

   Enter the essentials

   Name your event, accept or tweak the auto-generated slug (wait for the green check), pick a category, and set start/end times. That's everything Step 1 requires.

3. 3

   Publish

   Skip or fill in Step 2's details, choose Public or Private, leave it on Publish immediately, and click Create event.

4. 4

   Share the link

   Your page is live at eventislive.com/e/your-slug. Send the link, or — for a public event — let people find it in the directory. Attendees open the page and join the live experience.

5. 5

   Layer on what you need

   Back in the event dashboard, add a schedule and speakers, turn on ticketing or a CFP, and unlock any premium features when the moment calls for it.

Open your event in the dashboard and go to Landing page (Content → Landing page). This is where you control the public page at /e/{slug}: the hero cover image, basic info (title, short description, About, location, dates), contact and social links, and — most importantly — which sections appear and in what order. Use Preview page (top right) at any time to open the live page in a new tab.

The Page sections card lists every section of your page. Each row has a visibility toggle (Visible / Hidden), up/down arrows to reorder, and an optional Custom title field that overrides the default heading. The built-in sections are: About, Tickets, Schedule, Speakers & Mentors, Team Members, Sponsors, Frequently Asked Questions, and Custom Content Blocks.

1. 1

   Reorder a section

   Use the up/down chevrons on the left of each row. The number badge (01, 02, …) updates to reflect the new order top-to-bottom.

2. 2

   Show or hide a section

   Flip the toggle on the right. Hidden sections are dimmed and won't render on the public page. FAQ and Custom Content start hidden by default — turn them on once you've added content.

3. 3

   Rename a section

   Type into Custom title (optional). Leave it blank to keep the default label, e.g. "Sponsors".

4. 4

   Pick a layout where offered

   Sponsors and Speakers expose a Display style picker (see the Sponsors/Mentors subsection). Sections without a layout choice simply hide the picker.

5. 5

   Save

   Click Save changes in the sticky bar at the bottom. Your public page updates immediately.

Your page's color scheme lives under Settings → Theme. A theme is four values: a Primary color, a Secondary color, a Background (the page backdrop), and a Text color. New events start on the Midnight preset (indigo on a deep navy background).

The fastest way to a polished look is the Presets row. Click any swatch to apply its full palette in one go. Eight curated presets ship today: Midnight, Aurora, Sunset, Royal, Ember, Mint, Slate, and Paper (a light theme). Picking a preset sets the background type back to a solid/gradient color and fills in all four values; you can then fine-tune any of them by hand.

• Primary / Secondary / Text color — set each with the color picker or by typing a hex value like #6366F1.
• Background type — switch between Color and Image. Color mode supports both Solid and Gradient.
• Gradient — toggle Gradient to pick a start and end color; the page renders a 135° linear gradient between them with a live preview bar.
• Image background — choose Image to pick a background photo from your image gallery instead of a color.

The cover image is the background of your landing page hero. Set it under Landing page → Hero → Cover image. Click Select cover image to open your event's image gallery, where you can browse existing uploads or add new ones. The recommended size is 1920×1080 (16:9). Selecting an image saves it immediately — you don't have to wait for the main Save button.

To keep hero text legible over a busy photo, add an overlay. Once a cover image is set, two controls appear: an Overlay color (color picker or hex) and an Overlay opacity slider from 0% (transparent) to 100% (solid). The default is black at 10%. The hero preview updates live as you adjust them.

These three fields live under Settings → Details. They shape how your event is displayed, discovered, and shared.

• Timezone — pick from a grouped list organized by region. Attendees see your event and schedule times labeled with this timezone, so set it to where the event actually takes place. Choosing a timezone here also sets the schedule display timezone.
• Event Category — an optional single choice from a fixed list (Music, Nightlife, Performing & Visual Arts, Health, Business, Food & Drink, Sports & Fitness, Science & Tech, Networking & Conferences, and more). It helps attendees find events of interest.
• Event Hashtags — optional, for social sharing. Type words separated by spaces; you don't need to type the # (it's stripped automatically). For example, TechConf2024 Innovation AI.

Two content sections on the Landing page editor let you add free-form material beyond the structured records: Frequently asked questions and Custom content blocks. Both start hidden — add your content first, then flip the matching section to Visible in the Page sections card.

• FAQ — click Add FAQ to create a Question + Answer pair. Answers are plain text with line breaks preserved, rendered as expandable items on the page. Reorder with the up/down arrows; remove with the trash icon. Empty entries (blank question or answer) are dropped on save.
• Custom content blocks — click Add block for a free-form rich-text section with an optional heading and a formatted body (links, lists, emphasis). Good for travel info, a code of conduct, accommodation details, or a sponsor pitch. Blocks with an empty body are dropped on save.

Sponsors, Speakers & Mentors, and Team Members each have a dedicated management page (reachable from Manage content on the Landing page editor). You add and edit the actual people/logos there; the Landing page editor only controls whether each section shows, its order, and its title.

• Sponsors — add each sponsor with a name, logo, and a Sponsorship Tier: Platinum, Gold, Silver, Bronze, or Other. On the public page you can choose a Display style for the section: Identical grid (all logos equal size) or Tier-grouped (larger logos for higher tiers).
• Speakers & Mentors — managed from the Mentors page. The section offers two display styles: Show all (grid) or Slideshow (carousel) — an auto-advancing horizontal scroller.
• Team Members — managed from the Team page and rendered as a straightforward section; reorder and rename it like any other.

After your event ends, you can publish a public recap hub at /e/{slug}/recap. It collects your thank-you note, the event recording, and the community photo gallery in one shareable page. Configure it under Landing page → Post-event recap.

• Enable recap — the toggle in the section header. The page only goes live once the event has ended *and* the toggle is on (drafts never expose a recap).
• Recording URL — a YouTube or Vimeo link only. It's embedded with a privacy-enhanced player (youtube-nocookie / player.vimeo.com); other hosts are rejected.
• Thank-you message — up to 500 characters. It appears at the top of the recap page and is reused as the intro of the recap email.
• Photo gallery — the recap automatically pulls in approved photos from your event gallery; you don't attach them here.

You can set all of this up before the event ends — the page simply stays hidden until your end time passes. While it's hidden you'll see an amber notice with the go-live time; once it's live you'll see a green confirmation with a View recap page link.

When the recap is live, use Send recap email to email every ticketed attendee a link to the page. Unsubscribed and bounced addresses are skipped automatically, and the email uses your last *saved* recap settings — so save before sending. If you've already sent it, the button becomes Send again and asks you to confirm before re-sending to all attendees.

Every ticket has one of three types, chosen when you create it under Tickets → New ticket. The type determines what fields you fill in and how money (if any) moves.

• Free — no charge. Attendees register with name, email, and optional phone, and get a confirmation with a QR code. You still set a quantity and per-user limits.
• Paid — you set a Price in your event currency. A platform fee applies (typically 5%) — depending on your event's fee mode it's either added on top at checkout (you keep 100% of your price) or deducted from your payout.
• Donation — you set a Minimum donation and the buyer chooses any amount at or above it. Donations have no quantity cap (inventory is unlimited) and no per-user/per-email limits, and the platform fee never applies to them.

Silent is not a separate type — it's a toggle (Silent ticket) you can switch on for any ticket. A silent ticket is hidden from the public tickets page and is only reachable through its direct link, which you copy from the ticket card (Copy link). Use it for VIP comps, press, or pre-sale access you don't want listed publicly.

Rather than a fixed tier ladder, you model pricing tiers as separate tickets — e.g. an "Early Bird" ticket and a "General Admission" ticket, each with its own price, quantity, and silent flag. This gives you full control over how each tier looks and sells.

Individual tickets also support built-in early-bird pricing: a ticket can carry an earlyBirdPrice and an earlyBirdEndDate. While the current time is before that date, the checkout shows the early-bird price (with the regular price struck through) and an Early bird badge; after it passes, the price automatically reverts to the standard price. No manual switch-over is needed.

Each ticket can also define a sales window with salesStartDate and salesEndDate. Outside that window the ticket isn't on sale — this is how you schedule a tier to open or close at a specific time. The USSD flow honors these windows too, so a ticket that hasn't opened or has already closed won't appear on feature phones either.

Each non-donation ticket has a Quantity available. As tickets sell, the ticket card shows Sold / Left with a progress bar; the Tickets overview rolls these up into total capacity and a sell-through percentage. When remaining inventory drops to roughly the last 10%, the card flags a low-stock "N left" badge, and the public page shows a "Few left" chip once 10 or fewer remain. A quantity of -1 means unlimited.

When two buyers reach for the last seat at the same instant, the system handles the race fairly — only one succeeds and gets the ticket. When stock hits zero the ticket reads Sold out and the buy control is replaced by a waitlist option.

• Max per user (maxPerUser) — caps how many of this ticket a single logged-in user can buy. -1 is unlimited.
• Max per email (maxPerEmail) — caps purchases tied to one email address, which also limits anonymous/guest buyers. -1 is unlimited.
• Max per order (maxPerOrder) — the per-checkout ceiling for a ticket, defaulting to 10. The quantity stepper on the public page won't let a buyer exceed it (or the remaining stock, whichever is lower).

Coupons live under Tickets → Coupons. Each coupon has a code (uppercase letters and numbers — you can auto-Generate one), a name, and a discount that's either a percentage (0–100) or a fixed amount in your currency. Buyers enter the code in the Promo code box at checkout; a valid code shows the savings and applies it to the order total.

• Max total uses — an overall redemption cap across all buyers. Leave blank for unlimited.
• Start / end date — the validity window. The end date defaults to your event's end date. Codes outside their window show as Scheduled or Expired.
• Active toggle — flip a code off without deleting it; you can also Deactivate from the list. Exhausted, expired, scheduled, and inactive states are color-coded in the list.

Coupons can also be auto-applied via referral links: if a referral carries a linked coupon code, the checkout pre-fills and validates it for the buyer automatically, while still letting them swap it out.

When a buyer adds more than one of the same (non-donation) ticket, the checkout reveals a Group tickets panel with an "Assign tickets to attendees" section. There they can name each seat — one row per ticket — with a name and email, or click "Same as buyer" to keep a seat for themselves. Assignment is entirely optional; any seat left blank simply falls back to the buyer.

If at least one seat is assigned to someone other than the buyer, EventisLive creates one ticket per seat — each with its own QR code — instead of a single multi-quantity ticket. The order totals (and platform-fee share) are split evenly across the seats so each ticket carries an accurate price.

Delivery follows the assignments: the buyer gets the full order confirmation, and each distinct non-buyer email receives its own email containing only their ticket(s) and QR. The confirmation page also lists the per-seat assignments (with attendee emails masked) so the buyer can confirm everyone was covered.

When a ticket sells out, its buy button on the public page is replaced by a Join Waitlist action (showing how many people are already waiting). Attendees submit name, email, and optional phone to join; each entry records a queue position and a status of waiting.

Manage the queue under Tickets → Waitlist, which streams entries in real time. You can filter by status (Waiting / Notified / All) and by ticket, search by name or email, select individuals or the whole filtered list, and Export CSV. Stats at the top show how many are waiting, how many you've notified, and how many tickets have active waitlists.

1. 1

   Free up inventory

   Increase the ticket's quantity, or let a cancellation/refund return stock to the pool.

2. 2

   Notify the queue

   Click Notify on a single entry, or select people and Notify selected / Notify all to email a batch that tickets are available.

3. 3

   Buyers convert

   Notified attendees get an email with a direct purchase link; their status moves to Notified, then Purchased once they buy.

After checkout, the buyer lands on a confirmation page and receives an order confirmation email (sent via Resend). Both surface the order summary, any coupon savings, and a QR code that covers every ticket in the order — present it once at the door to check the whole order in. Donation-only orders get a tailored "thank you" email with no QR or ticket details.

• QR code — the confirmation page shows the QR code plus the order ID.
• Apple Wallet — an Add to Apple Wallet button on the confirmation page (and a wallet link in the email) downloads a signed .pkpass for the ticket. Wallet passes are a gated paid feature; without the right configuration the pass request will not be available.
• Add to Calendar — an .ics file is attached to non-donation confirmation emails for one-tap saving, and the page offers an Add to Calendar button.
• Resend — if the email doesn't arrive, the buyer can click "Resend it" on the confirmation page; resends are rate-limited to prevent abuse.

Transfers are organizer-initiated from Tickets → Attendees: open a ticket's Transfer dialog, enter the new attendee's name, email, and optional notes, and the old and new owners are both notified. A ticket records that it's been transferred and can only be transferred once — a second attempt is rejected with an explicit message. Transferred tickets are badged in the attendee list.

Cancellation requests are attendee-initiated. From their confirmation page, an attendee can click "Request a cancellation" and give a reason. This does not cancel the ticket or trigger an automatic refund — the tickets stay valid, and the request appears in your refunds queue for review.

Refunds are managed under Tickets → Refunds, which streams completed purchases, existing refund records, and pending cancellation requests. You search by order number, order ID, or email, then issue a full or partial refund with a reason code (requested by buyer, duplicate, event cancelled, fraudulent, or other). The page tracks how much of each purchase has already been refunded so you can't over-refund a single order.

Sell from your own website with the Embed ticket widget, generated at the bottom of the Tickets page. Pick a light or dark theme and an accent color (it defaults to your event's brand color), preview it live, and copy the snippet. The widget renders an iframe pointing at /widget/[eventSlug]; buyers open your full checkout in a new tab.

<iframe src="https://YOUR_DOMAIN/widget/your-event-slug?accent=6366f1" title="Your Event — tickets" width="100%" height="480" style="max-width: 480px; border: 0; border-radius: 16px;" loading="lazy"></iframe>
<noscript><a href="https://YOUR_DOMAIN/e/your-event-slug/tickets" target="_blank" rel="noopener noreferrer">Get tickets — Your Event</a></noscript>

• The widget adapts to container widths between roughly 300 and 500px.
• Outbound ticket links carry utm_source=widget and ref=widget, so widget-driven sales show up in your existing analytics and referral attribution with no extra setup.
• A <noscript> fallback link is included so the widget still works for visitors without JavaScript.

EventisLive can sell tickets over USSD — the menu-driven flow you reach by dialing a short code on any phone, no internet or app required. It's built for markets like Ghana where mobile money and feature phones are common. The caller picks an event, picks a ticket, chooses a quantity (1–5), and confirms — all in a session-based menu.

Welcome to EventisLive tickets
1. Tech Summit Accra
2. Highlife Night
  > pick event, then:
1. General Admission - Free
2. VIP - GHS 150.00
  > pick ticket, then:
How many tickets? (1-5)
  > enter quantity, then:
2 x VIP = GHS 300.00
1. Confirm
2. Cancel

• Free tickets are issued immediately and the reference is delivered by SMS.
• Paid tickets trigger a mobile-money charge to the caller's number; once they approve the prompt on their phone, the ticket is confirmed and the reference arrives by SMS.
• Only tickets that are active, on-sale, in their sales window, and not silent appear in the menu, and the event must be published.
• Sessions expire after 10 minutes, menus show up to 5 events/tickets, and the per-order quantity is capped at 5 (or the ticket's maxPerOrder / remaining stock, whichever is lowest).

EventisLive supports three major payment providers, each accepting different currencies and payment methods. When you collect a payment, EventisLive automatically selects the provider that works best for the currency and region:

• Paystack — handles GHS (Ghana cedi). It's the primary choice for cedi payments.
• Flutterwave — the pan-African and international provider. Supports NGN, USD, EUR, GBP, ZAR, GHS, KES, TZS, UGX, RWF, XAF, XOF, and more, plus card, bank transfer, USSD, M-Pesa, and Ghana mobile money.
• Stripe — covers USD, EUR, GBP, NGN, CAD, and AUD. It's available as a fallback for currencies the other providers don't support.

Mobile money works on both sides of the platform: attendees can pay with it at checkout, and you can request payouts to it. On the checkout side, mobile money options include payment from Ghana, Kenya, and other mobile money networks, so buyers can pay from their wallet instead of a card.

For payouts, EventisLive supports instant Ghana mobile money transfers to three networks: MTN, Telecel (formerly Vodafone Cash), and AirtelTigo. When you request a withdrawal to a mobile money wallet, enter your phone number in any format — the platform accepts 024 123 4567, 0241234567, +233241234567, and 233241234567. The platform normalizes it to local format before processing.

Each event sells in a single currency of your choosing, which is set on the event and applied to every ticket and purchase. The platform supports USD, GHS, NGN, EUR, and GBP. Currencies are rendered with their correct symbols — GH₵ for GHS, ₦ for NGN, $ for USD, and so on.

All money in the system is stored in minor units — pesewas for GHS, kobo for NGN, cents for USD. A GH₵100.00 ticket is stored as 10000 internally, so prices always remain precise integers.

EventisLive charges a 5% platform fee on paid ticket sales as its primary revenue. This is the only fee taken on ticketing — there is no separate withdrawal fee. The fee is calculated on the ticket price at the time of sale and cannot change retroactively for past orders.

There are two fee modes, and you can set which one applies to your event:

• Pass to buyer (the default) — the buyer is charged ticket price + 5% fee, and you receive the full ticket price. On a GH₵100.00 ticket, the buyer pays GH₵105.00 and you keep GH₵100.00.
• Absorb — the buyer pays exactly the ticket price and the 5% fee is deducted from what you receive. On that same ticket, the buyer pays GH₵100.00 and you keep GH₵95.00.
• Donations always absorb — donors are never charged more than the amount they choose to give, regardless of your event's fee mode.

Your available balance is the total ticket revenue from your event minus any already-paid withdrawals and any refunds you've issued. You can withdraw this balance at any time.

1. 1

   Request a withdrawal

   Pick the event, an amount, and a destination — bank transfer, mobile money, PayPal, or other. The minimum is the equivalent of $10, and the amount can't exceed your available balance.

2. 2

   Your request is reviewed and approved

   Depending on the payment method and amount, your request may be approved automatically or reviewed by our team. Instant mobile money transfers in GHS process immediately; other methods may take time. Either way, you'll be emailed when your payout is complete.

3. 3

   You're paid out

   Once approved, the payment is transferred to the account or wallet you specified.

• pending — created, awaiting processing. You can cancel it yourself only while it's still pending.
• approved — cleared for payout. No longer cancellable by you.
• completed — paid out and final.
• transfer_failed — the payout didn't land. Contact support for help.
• cancelled — closed without payout; the amount is released back to your available balance.

EventisLive turns ticket sales into a fast door experience: scan attendees in (online or fully offline), register walk-ins on the spot, and design, print, and hand out attendee badges. This section covers everything from the registration desk to self-service badge downloads.

Open Check-in from the Tickets area of an event (/dashboard/events/{eventId}/tickets/check-in). The page has two input modes — a live QR scanner that uses the device camera, and an Email or phone lookup for attendees who can't produce their code. Switch between them with the button on the check-in card. Four stat cards across the top track Total tickets, Checked in, Pending, and your live check-in rate.

• Scan — point the camera at the ticket QR. EventisLive finds every ticket sharing that code and checks the attendee in.
• Email or phone lookup — type an attendee's email or phone number. Phone matching compares the last 9 digits, so local (024…) and international (+233 24…) formats both resolve to the same ticket — useful for USSD buyers who have no email on file.
• Multi-ticket orders — if one QR or email covers several ticket types, an Order check-in dialog lists each type so you can admit them individually.
• Group tickets — when a single ticket holds multiple admissions, a Bulk check-in dialog lets you choose how many people are entering now (it defaults to all remaining) and shows how many will be left.

The right-hand Checked-in attendees panel updates in real time as scans land, newest first, with a search box to find a specific name. Each row shows the ticket type, an n of m in counter for group tickets, and the check-in time.

The check-in page is built to keep working when the venue WiFi isn't. A connectivity pill shows Online or Offline — scans saved on this device, and the page validates scans against a locally-stored guest list so the door never stops moving during a dead zone.

1. 1

   Download the guest list while online

   Press Refresh guest list to pull a snapshot of every valid ticket for the event. The snapshot is cached on the device for offline use.

2. 2

   Label the device

   Set a short device label (e.g. "Gate A") so synced check-ins and any conflicts are attributed to the right station.

3. 3

   Scan offline

   When you go offline, scans are validated against the cached snapshot and queued in an on-device outbox. Each accepted scan optimistically marks the ticket checked-in locally so your counts stay accurate.

4. 4

   Reconnect and sync

   EventisLive auto-syncs the outbox and refreshes the snapshot the moment connectivity returns. You can also press Sync now at any time.

Real events get people who arrive without a ticket. From the Attendee Badges page (/dashboard/events/{eventId}/badges), click Walk-ins to mint badges for them on the spot. Unlike generated badges, walk-ins don't need a pre-existing ticket record — EventisLive creates a synthetic attendee and a ready-to-print badge in one step.

Paste a CSV or drop a .csv file — one row per attendee. The expected columns, in order, are name, email, company, title, ticketName, template. Only name is required; a header row is optional. The modal previews parsed rows and flags any it skipped (for example, a row with a missing name) before you commit.

Jane Doe, jane@example.com, Acme Corp, CEO, VIP, vip
John Smith, john@example.com

Open the Settings tab on the Attendee Badges page to design your badge. A sticky Live preview on the right updates as you change anything, so you always see the printed result. Click Save settings to apply.

• Format — choose Landscape (85.6 × 54 mm, credit-card size) or Portrait (3.75 × 5.5 in). The dimensions are set automatically per orientation.
• Template — start from one of six palettes: Standard, VIP, Speaker, Sponsor, Staff, or Custom. Picking one seeds the colors below.
• Colours — fine-tune the header (primary), footer (secondary), and card background independently with a picker or hex value.
• Background image — upload artwork (PNG/JPG up to 5 MB) or pick from your event gallery, with an opacity slider from 10–100%.
• Badge content — toggle what appears: event name, event logo, attendee name, company, job title, ticket type, QR code, and photo.
• Ticket type → template — map each ticket type to its own template (e.g. send VIP tickets to the VIP design), overriding the default per attendee.

Badges are rendered at 300 DPI for crisp print output, so results are consistent regardless of browser. Generate badges first with the Generate badges button (it creates one for every attendee who doesn't have one yet), then print individually or in bulk.

• Single badge — open a badge's preview (the eye icon) and click Print badge for a one-off, or download the high-resolution PNG.
• Bulk PDF — use Download PDF in the toolbar. Choose a layout: 8-up sheet (landscape), 10-up sheet (portrait), or 1 badge per page. EventisLive auto-picks the grid that matches your badge orientation and adds crop marks at each badge corner for clean cutting.
• Avery-style sheets — the multi-up grids (2×4 landscape, 2×5 portrait) lay out on A4 or Letter stock for standard label/badge sheets.
• Print what's selected — the export honors your current status filter, or pass a specific selection. For example, filter to Generated and export only those.

Badges move through four statuses — Pending → Generated → Printed → Collected — shown on the stat cards and as colored chips. Select badges and use Mark printed or Mark collected to keep the funnel accurate, which also feeds the kiosk's duplicate detection.

Kiosk mode (/dashboard/events/{eventId}/badges/kiosk) is a full-screen station built for a tablet next to a printer at the registration desk. Staff scan an arriving attendee's badge QR; the kiosk looks it up, prints the badge, and marks the attendee collected — all in one round-trip, no name typing required.

• Hardware scanner — the input stays focused, so a USB/Bluetooth scanner that types-and-presses-Enter just works.
• Camera scanning — click Scan with camera to use the device camera (works cross-browser, including iPad Safari). Continuous scanning ignores the same code held in frame for a few seconds.
• Paste — paste a badge code or URL; the kiosk extracts the identifier from either.
• Auto-print on scan — toggle on to print automatically the moment a badge is found and collected.

Cut the registration queue by getting badges into attendees' hands before they arrive. From the badges toolbar, Email badges sends each attendee a private link to a self-service page where they can preview and save their badge as a PNG (or screenshot it). The email leads with a "show this at registration" message and works for the current filter or an explicit selection.

Each link is personal to that attendee and badge, so attendees can't see other people's badges by guessing IDs. The same credential powers the QR code printed on the badge, so scanning it at the desk resolves directly to the right person. The self-service page lives at /e/{eventSlug}/badge?t={token}.

Center Stage is the projector or screen at your event — the public display rendered at /e/{eventSlug}/display. What it shows is driven by a single mode that you switch from the dashboard. Open the Center stage control modal (the Monitor button on the event dashboard, or the floating bubble on any event sub-page) to pick what runs. There are 14 modes: Live Messages, Participants Wall, Mentors Showcase, Sponsors Highlight, Q&A Session, Team Showcase, Winner Announcement, Photo Gallery, Event Schedule, eBanner Display, Live Polls, Image Spotlight, Contestant Voting, and Intermission (the branded standby screen).

Switching a mode uses a stage-then-go-live flow so you never flip the screen by accident. Tapping a mode tile *stages* it (queued, screen unchanged); hitting Go live promotes the staged mode to the projector. The modal embeds a live iframe preview of the actual display so you can confirm what's on the screen without leaving the dashboard. Keyboard shortcuts: ⌘K toggles the modal, 1–9 switch directly to an enabled mode by position, and Esc closes.

1. 1

   Manual mode

   Pick one mode and push it live yourself. The default — full control, you decide every transition.

2. 2

   Playlist

   Select at least two modes and an interval (5–600 seconds). The display auto-rotates through them. The current slide is computed from the playlist's start time, not a per-device timer, so every screen and channel stays perfectly in sync.

3. 3

   Schedule

   The display follows your event schedule: any session with a displayMode set takes over the projector automatically while it's running. Sessions without a mode fall back to your manual mode. Set the mode per-session in the schedule editor.

Polls let the room vote on a question in real time, with results animating on Center Stage and (optionally) on attendees' phones. Manage them at Dashboard → Events → {event} → Polls. Each poll has a question and 2 or more options; click Add option for more. Polls requires the Polls feature enabled in Settings — otherwise the page shows a "Polls feature disabled" notice.

Every poll card has three independent toggles that control its live behaviour:

• Show on Stage — activates the poll on Center Stage. Only one poll can be active at a time; turning this on automatically deactivates any other live poll. The card shows a pulsing green Live badge.
• Accepting Votes — opens or closes voting. Closing freezes the tally without removing the poll from the screen (shows a Closed badge).
• Show Results — reveals the vote bars and percentages to attendees in the experience hub. When off, attendees vote blind and only you see the running totals.

Attendees submit questions from the experience hub; nothing reaches the screen until you approve it. Moderate at Dashboard → Events → {event} → Q&A. Every question moves through three states, shown by the stat cards and filter chips at the top: Pending (amber, awaiting approval), Approved (blue, cleared for display but not yet addressed), and Answered (emerald). Filter by All / Pending / Approved / Answered to focus your queue.

1. 1

   Approve or reject

   On a pending question, hit Approve to clear it for the display, or the X to delete it (with a confirmation). Only approved, unanswered questions appear on the Q&A display mode.

2. 2

   Pin the one you're taking

   On an approved question, click Pin to push it to the top of the display. Pinning is exclusive — pinning one question automatically unpins any other, so the screen always highlights the single question being discussed.

3. 3

   Mark answered

   Once you've addressed it, hit Mark Answered. It drops off the live display and moves to the Answered tab. You can toggle it back to Unanswered if you reopen the topic.

When the Reactions feature is enabled, attendees get a floating reaction button in the experience hub, and the emoji they tap float up over whatever is currently on Center Stage. It's the lightweight, always-on way for a big room to show energy without typing anything. The eight available emoji are fixed:

🔥  ❤️  👏  🎉  😂  👀  💯  🙌

• Tapping the button opens a picker of all eight emoji; double-tapping sends 🔥 instantly as a quick reaction.
• Reactions are throttled client-side (a brief cooldown between sends) so one person can't spam the screen.
• On the display, reactions animate as a floating overlay on top of the active mode and clear themselves automatically — they layer over polls, Q&A, voting, or any other mode without interrupting it.

Contestant voting runs a structured race — pageant, talent show, awards — with a live leaderboard. Manage it at Dashboard → Events → {event} → Voting. You can run multiple campaigns per event, each its own standalone race with its own contestants, results, and (if paid) its own revenue stream. Create a campaign with a title, optional description, and a mode that you choose at creation and *cannot change later*:

• Free — each voter gets a fixed number of votes total (you set Votes per user, default 1). The cap is enforced per voter (by user ID when logged in, or an anonymous session key otherwise).
• Paid — voters pay a price per vote that you set in your event's currency. Revenue lands in your event's available balance and pays out through the standard withdrawal flow (the usual withdrawal fee applies). Optionally allow buying multiple votes in a single transaction.

1. 1

   Add contestants

   Open the campaign and add each contestant with a name, optional bio, and optional photo (upload one or pick from the event image gallery). Square photos work best.

2. 2

   Set the status

   Each campaign is Draft → Active → Closed. Voting is only accepted while the campaign is Active; the server rejects votes on draft or closed campaigns.

3. 3

   Put it on the screen

   Toggle Show on Center Stage to push the live leaderboard to the display, and Show results publicly to reveal vote counts to voters. Share the public vote page with Copy vote link — it points to /e/{eventSlug}/vote/{campaignId}.

Broadcasts are push announcements that land as notifications on people's devices — "Doors open in 10 min", "Coffee break in main hall". Compose them at Dashboard → Events → {event} → Broadcasts. Pick your audience, write a short title and message, and the composer shows a live notification preview of exactly how it'll land on a phone before you send.

• Audience — Team only (operators running the event in the studio app), Attendees (people who joined in the participant app), or Everyone.
• Limits — title up to 80 characters, message up to 500. The counters turn red if you go over.
• Cooldown — a 30-second rate limit per event between sends. The button shows a live countdown; the server also enforces it and returns a 429 if bypassed.

The Recent panel shows your last 50 broadcasts with a delivery indicator on each: Delivered (push succeeded), Failed (with the error on hover), or Unknown (older rows or ones that couldn't confirm delivery).

The Live Messages board (the messages Center Stage mode) is your channel for posting cards to the big screen — text shout-outs, an image, or a QR code. Manage it at Dashboard → Events → {event} → Messages. Text messages take a colour (preset swatches or a custom hex); QR messages can encode a URL, plain text, Wi-Fi credentials, or a link to one of your own event pages (experience hub, display, mentors, gallery, schedule, and more). Images are capped at 10MB.

Image Spotlight (the spotlight mode) is a separate, controlled image rotation — manage it at Dashboard → Events → {event} → Image Spotlight. Upload images one at a time or in bulk (max 10MB each; JPG, PNG, GIF, WebP), drag to reorder, and add captions. Each image has an Active/Hidden toggle, and you can pin a single image as "Showing now" to hold the screen on it. The display settings rail controls the rotation: transition effect (fade / slide / zoom), per-image display duration (1–60s), transition duration (0.5–5s), caption position (top / bottom / overlay), image scaling (contain / cover / fill), plus toggles for captions, auto-advance, and background blur. A live preview cycles your images so you can dial it in before going live.

Everything attendees do during the event happens in one place: the experience hub at /e/{eventSlug}/experience. It's a phone-first page they reach by scanning the QR code you show on the display (set the display's QR overlay to the experience type so it deep-links straight here). The hub renders a tab bar that adapts to which features you've enabled — attendees only see what's switched on.

• Share — post a message or learning to the participants wall.
• Ask Q&A — submit a question (enters your moderation queue as Pending).
• Gallery — upload a photo to the event gallery (max 5MB).
• Schedule — browse the agenda.
• Polls — vote on the active poll and, if you've enabled Show Results, watch the live tally.
• Networking — the attendee networking tab (only when networkingEnabled is on).

The public display lives at /e/{eventSlug}/display. Open that URL on whatever drives your screen — a laptop plugged into the projector, a smart TV browser, or a dedicated display PC. It's a public page (no login), it listens to Firebase in real time, and it reflects your Center Stage mode, theme background, logo, and QR overlay automatically. There's a fullscreen button in the top-right corner; use it once the screen is positioned.

1. 1

   Open the right URL

   For your main screen, use the plain /e/{eventSlug}/display. For a secondary screen, add its channel: /e/{eventSlug}/display?channel={channelId}. The Center Stage control modal has copy and open-in-new-tab buttons for each channel's exact link.

2. 2

   Go fullscreen

   Click the fullscreen toggle (top-right) so the browser chrome disappears. The display fills the screen and stays put — you drive everything from the dashboard on your own device.

3. 3

   Control from anywhere

   Switch modes, start a playlist, or stage the next slide from the dashboard or the floating Center Stage bubble. Because the display is a live listener, changes appear on the screen within a second — no refresh needed.

The schedule is your event's timeline of sessions. Open it from Program → Schedule in the event dashboard. Sessions are grouped automatically into day tabs (e.g. *Mon, Jun 28*), each showing a count of how many sessions fall on that day, and rendered as a time-railed list with start time, end time, and computed duration. Editing requires the schedule edit permission, so coordinators and editors can manage it without full admin access.

1. 1

   Add a session

   Click Add session and fill in the required fields — title, start date/time, and end date/time. The end must be after the start, or the form rejects it.

2. 2

   Set the type and location

   Pick a Session type (General Session, Keynote, Workshop, Panel Discussion, Break, or Networking) — each gets its own color tint on the public schedule. Add an optional Location like "Main Hall" or "Virtual".

3. 3

   Group parallel tracks

   Use the optional Track field to run parallel rooms. Reuse the exact same track name across sessions and attendees can filter the public schedule by it.

4. 4

   Attach speakers and tags

   Type a speaker name to add it; the field autocompletes against your active mentors. Add tags the same way. Optionally set a Maximum attendees cap.

5. 5

   Save

   Click Create session. The new session appears under the correct day tab immediately. Use the row hover actions to edit, duplicate, or delete any session later.

Call for Papers (CFP) collects and reviews speaker proposals. Enable it in your event settings, then manage it under Engagement → Call for Papers, which has four tabs: Overview, Submissions, Reviewers, and Settings. The Overview shows live stats (total submissions, pending review, accepted, reviewer count), a timeline status pill — *Scheduled*, *Open*, *Closed*, or *Disabled* — and a Copy Link / View Public Page button for your public submission portal at /e/[eventSlug]/cfp.

• Portal & timeline — Turn on Enable Call for Papers, give it a title and description, and set the *Submissions Open*, *Submissions Close*, and *Results Announced* dates. The portal opens and closes automatically against these.
• Tracks & formats — Define the Tracks (e.g. Frontend, AI) and Session Formats (e.g. *Talk (30 min)*, *Workshop (60 min)*) authors choose from. Formats containing "keynote", "workshop", or "panel" map to the matching schedule session type when you import accepted talks.
• Form fields — Toggle visibility and required state for built-in fields (Track, Format, Experience Level, Notes, Speaker Bio, Company, Social Links), and add Custom Questions of any type (short/long text, email, phone, URL, number, date, dropdown, radio, checkboxes).
• Review process — Enable Double-Blind Review to hide author names, photos, and social links from reviewers so proposals are judged on content alone.
• Scoring rubric — Define weighted criteria (each with a name, optional guidance, max score, and weight). With a rubric set, reviewers score each criterion and the overall is a weighted average; with no rubric, reviewers use a single 1–10 score.

Submissions lists every proposal with search and filters by status, track, and format. Each submission moves through statuses — *Submitted → Under review → Accepted / Waitlisted / Rejected / Withdrawn*. Select multiple rows to bulk-change status, and open the Export menu for CSVs of submissions, reviews, or public votes. On a submission's detail page you can change status, read the abstract and custom answers, see all reviews (with average score and private organizer-only notes), assign reviewers, hold an internal discussion, and send the author a status email. Accepting a submission and emailing the author issues a speaker-confirmation request automatically (see Speaker portal).

Reviewers is where you build your review team. Click Invite reviewer, enter a name and email, and they receive an email invitation with access to the review dashboard. Invited reviewers can be re-sent the invite; active reviewers can be deactivated or removed. On any submission you can assign specific reviewers, and a reviewer who flags a conflict of interest on a proposal is surfaced so you don't assign them to it.

Speakers manage their own proposals through a self-service portal at /cfp/my-submissions — no account or password required. They enter their email, receive a 6-digit one-time code, verify it, and land on a dashboard of every proposal tied to that email, across all your events. The session lasts 7 days, so they can come back without re-verifying.

• Edit a proposal while the CFP is still open.
• Withdraw a proposal they no longer want considered.
• Confirm or decline their spot once a proposal is accepted.

When you accept a submission and send the acceptance email, EventisLive generates a unique, expiring confirmation link for that speaker (with an optional deadline). The link opens a confirmation page showing the event details and their accepted session, a live countdown to the deadline, and three choices: Yes, I'll Be There, Release my spot (a soft decline that signals you can offer the slot to a waitlisted speaker), or Just decline. Their response flows straight back to the submission's *Speaker Confirmation* card in your dashboard, including any reason or note they leave.

Mentors (also used for speakers and featured experts) are managed under People → Mentors. They appear on your public mentors page and on the center stage when *mentors showcase* mode is active. The list shows totals for all, active, and pinned mentors, and editing requires the speakers edit permission.

• Add a mentor with a required photo (uploaded or chosen from your image gallery, with a built-in crop tool), name, email, title/position, and bio (max 500 characters). Email is required because it's used for broadcasts.
• Optional details — contact phone, an expertise topic, and social usernames for Twitter, LinkedIn, and GitHub (usernames only, not full URLs).
• Pin one mentor to feature them first on the display — pinning a new mentor automatically unpins the previous one. Hide a mentor with the eye toggle to keep them in your list but off the public display.
• Email all sends a broadcast to every active mentor who has an email on file, using your saved *Broadcast* mentor template.

Grants let attendees apply for financial support — travel, registration, full sponsorship, or a custom amount. Manage everything under Engagement → Grants. Because grants touch money, the area requires finance-level (sales) access. Toggle Accepting Applications on to publish the public form at /e/[eventSlug]/grants/apply, with a one-click Copy link.

• Budget tracking — Set a total budget and currency (USD, EUR, GBP, NGN, GHS, KES, ZAR). The Budget Overview shows allocated, disbursed, and remaining amounts with a progress bar; approving an application allocates its amount against the budget.
• Timeline & review — Set application open/close and review windows, plus an optional results-announcement date (before which applicants only see "Under Review"). Optionally require multiple reviewers (2–5) before a decision, allow reviewer self-assignment, and let reviewers see each other's reviews.
• Application form — Choose which grant types are offered, what documents applicants must upload, and add Custom Questions (short/long text, dropdown, multiple choice, checkbox).
• Pre-disbursement documents — Require approved applicants to upload proof (flight/hotel bookings or receipts, registration receipts, etc.) before payment, with a deadline of 7–60 days after approval. Applications missing required docs are flagged Docs Pending.
• Notifications — Add email addresses to be notified whenever a new application arrives.

Applications stream in live with search (name, email, organization) and filters by status and type. Each moves through *Pending → Under Review → Approved / Rejected / Waitlisted → Disbursed*. Approving prompts you for an approved amount (which may differ from the requested amount) and an optional note to the applicant; rejecting lets you record a reason. Use Export CSV to pull the full applicant list with amounts and answers.

Custom forms collect anything the built-in tools don't — volunteer sign-ups, vendor interest, session feedback, lead capture, and more. Build them under Registration → Custom Forms (requires the settings edit permission). Each form has a name, an auto-generated URL slug, an optional description, and your fields. Field types are text, email, phone, long text, date, dropdown, radio, checkbox, and file upload.

• Field options — Dropdown, radio, and checkbox fields take a custom option list. File-upload fields let you set a max size (1–50 MB, default 5) and accepted types (images, PDF, both, or all).
• Form settings — Toggle Accept responses, require approval before submissions count, and set a custom success message shown after submit.
• Layout & theme — Choose Single Column, Two Columns, or Split (cover + form), and a theme: Minimal, Light, Dark, Aurora, or Brand (which uses your event's color and cover image).
• Open/close window — Optionally set submission start and end date/times; outside that window the public form shows a clear "not yet open" or "closed" message.

Publish by sharing the link, the Embed code, or the QR code — all available from the form's row. The public form lives at /f/[eventSlug]/[formSlug], validates required fields, uploads files, and is protected by reCAPTCHA. Review responses under each form's Submissions page: search and filter by *All / Pending / Approved / Rejected*, open any submission for full detail (images and files render inline), step through with prev/next, approve or reject (in bulk if you like, with an optional rejection reason saved for your team), and Export CSV.

<iframe src="https://your-domain/f/your-event/volunteer-registration" width="100%" height="800" frameborder="0" style="border: 1px solid #ccc; border-radius: 4px;"></iframe>

EventisLive sends program emails in two ways: automated templates that fire on a trigger, and reusable templates you pull into a broadcast. Both are configured per event so the wording always matches your voice.

• Mentor email templates (*Communications → Email Templates*) — Five automated emails sent at each stage of the mentor application lifecycle: Submission (auto-sent on apply), Shortlisted, Approval, Rejection, and Broadcast (sent to all approved mentors from the Mentors page). Edit the subject and body of each, toggle any of them on/off, and use variables like {{name}}, {{email}}, {{eventName}}, {{topic}}, and {{title}} — they're replaced with real values at send time.
• Communication templates (*Communications → Templates*) — Reusable, designed templates scoped to an audience: Attendees, Speakers, Mentors, Everyone (event-wide), or a specific Form. You create and edit these once, then reuse them across broadcasts.
• CFP status notifications — From a submission you can send an *Under Review*, *Acceptance*, *Waitlist*, or *Rejection* email to all of its authors. Acceptance also wires up the speaker's confirmation link automatically.
• Bulk speaker email (*Email Speakers* under CFP) — Compose a message or pick a saved template, filter recipients by submission status and track, preview the exact recipient list, and send to every unique speaker that matches.

Open the Configure button on the Certificates page to design your template. Edits are reflected in a live PDF preview on the right of the dialog — the preview is the real renderer, so what you see is exactly what attendees receive. Settings are organized into four tabs: Content, Branding, Style, and Settings.

• Content — the Certificate title (e.g. Certificate of Attendance), an optional Subtitle (e.g. This is to certify that), the Body text, and a Footer text line. Body text supports the placeholders {{name}}, {{event}}, and {{date}}, which are substituted per recipient at generation time. The default body is {{name}} has successfully attended {{event}} on {{date}}.
• Branding — upload a Logo and a Signature image (or pick either from your event's image gallery), plus a Signer name and Signer title that print above and below the signature line.
• Style — choose one of four templates (Modern, Classic, Elegant, Minimal), an Orientation (Landscape or Portrait), Primary and Secondary colors, and whether to Show border.
• Settings — the Require check-in eligibility toggle (covered below).

The four styles share the same skeleton — logo, title, subtitle, name, body, signature block, footer — but differ in ornamentation: Modern uses an accent strip and bold sans-serif headline, Classic a formal double border with a serif title, Elegant italic body text with corner ornaments, and Minimal is pure typography with no decoration. Pages render at A4 (landscape 841.89 × 595.28 pt, or portrait flipped).

By default, certificates are gated on check-in: only attendees who were actually checked in at your event can receive one. This is controlled by the Require check-in toggle on the Settings tab of the template. Turn it off if you want every valid ticket holder to be eligible regardless of attendance.

The attendee list on the Certificates page only ever shows tickets in the valid or used state. When check-in is required, attendees who haven't checked in are dimmed and can't be selected, previewed, or generated for. A banner at the top of the page reminds you of the rule and shows how many of your attendees have checked in (for example, "42 of 80 attendees have checked in"). Use the Checked in / Not checked in filter chips and the search box to narrow the list.

Each eligible attendee row has a preview (eye) and a download action. Previewing opens the real PDF for that attendee in a modal so you can sanity-check the output before issuing. Downloading generates the certificate, streams the PDF straight to your browser as certificate-Attendee-Name.pdf, and records the certificate as issued.

1. 1

   Select recipients

   Tick attendees individually, or use Select all eligible (N) to grab everyone who qualifies. A selection toolbar appears showing the count.

2. 2

   Download as a ZIP

   Click Download ZIP. EventisLive renders every selected certificate and streams back a single certificates-Event-Name.zip containing one PDF per attendee, each named after the recipient.

3. 3

   Confirm issuance

   Once a certificate is generated — single or bulk — that attendee gets an Issued pill in the list, and the Certificates issued stat at the top of the page increments.

Every certificate gets a unique certificate number in the form CERT-YYYY-XXXXXX (e.g. CERT-2026-A1B2C3) and a separate 8-character verification code. Both print on the certificate footer, and the issued record snapshots the attendee's name and email so it stays accurate even if their ticket changes later.

Instead of downloading and forwarding files yourself, you can email certificates directly to attendees. Use Email all (N) in the page header to send to every eligible attendee, or select a subset and choose Email selected. Either opens a dialog where you can set an optional custom subject and message before sending; leave them blank to use the default subject Your Certificate of Attendance - {Event}.

Each recipient gets the certificate as a PDF attachment (certificate-{number}.pdf) plus the certificate number and verification code in the email body. When your event has a public slug, the email also includes a View & download anytime button — a personal link unique to that attendee, so they can re-open or re-download their certificate later even if they lose the attachment. After sending, the dashboard confirms how many went out and marks each attendee as Issued.

That self-service link points at /e/{eventSlug}/certificate. The page renders the attendee's certificate on demand and offers a Download PDF button. The same link is encoded into the QR code printed on the certificate, so a printed copy can be re-fetched by scanning it.

Every certificate is independently verifiable. Anyone — an employer, a registrar, or the attendee themselves — can confirm a certificate is genuine at the public verification page /certificate/verify, no account needed. The verification code is printed at the bottom of the certificate (and included in the certificate email). From your dashboard, the Verification page button in the header opens it in a new tab.

1. 1

   Enter the code

   On /certificate/verify, type the 8-character verification code (e.g. ABCD1234). The field upper-cases input automatically, and you can pass it directly via the ?code= query parameter to pre-fill it.

2. 2

   Get the result

   If the code matches an issued certificate, the page shows a green Certificate Verified panel with the attendee's name, the event name, the certificate number, and the date issued.

3. 3

   Handle failures

   If no certificate matches, you'll see a red Verification Failed message. Codes are looked up across all events, so an attendee never needs to know which event a certificate came from to verify it.

Open your event dashboard and go to Store. From there, click Add product to open the new-product form. Each product has a name, an optional description, a category (Apparel, Accessories, or Other), a price, and one or more images. You can upload an image directly or pick one from your event's image gallery with Browse gallery.

1. 1

   Enter product details

   Fill in the name (required), an optional description, pick a category, and set the price. The currency is shown read-only next to the price.

2. 2

   Add images

   Upload photos or add them from your gallery. The first image is used as the product thumbnail and on the public store card.

3. 3

   Decide on variants

   Leave the Multiple sizes or colors toggle off for a simple single-option product, or turn it on to build size/color variants (covered below).

4. 4

   Set pickup instructions

   Optionally add per-product pickup notes (e.g. "Visit the swag booth near the main entrance and show your order QR code").

5. 5

   Create

   Click Create product. New products are created with status Active and appear in your store list immediately.

When you enable variants, you choose from preset sizes (XS, S, M, L, XL, 2XL, 3XL) and ten common colors. The store generates the full combination set: pick sizes and colors and you get one variant per size×color pair; pick only sizes or only colors and you get a variant per option. A live Variants to be created preview shows exactly what will be generated (e.g. Black / M, Navy / L) before you save.

Inventory is tracked per variant. When creating a product you set a default Inventory per variant — either a fixed quantity or Unlimited. To adjust stock later, open the product from the store list (the pencil/Edit icon) and edit each variant under Variants & Inventory. Each row shows the variant's current Sold count and lets you set its stock to a number or toggle Unlimited.

• Unlimited stock means the variant never goes out of stock.
• A variant is available while stock remains above zero.
• When every variant of a product is exhausted, the product status automatically flips to Sold out and it stops accepting orders.
• The store list shows a per-product Stock summary as sold / total (or an infinity symbol when any variant is unlimited).

Stock is also returned to inventory automatically. If an order is cancelled, refunded, or its online payment fails, the reserved units are restocked. Orders already marked Picked up are never restocked (the physical item has left your hands), which keeps your counts accurate.

On the main Store page, the Payment settings card controls how customers can pay. There are two independent toggles: Online payment (accept Paystack, Stripe, or Flutterwave) and Pay at pickup (collect payment when the order is picked up at the event). Flip the toggles and click Save settings.

• Pay at pickup — the order is placed immediately with payment status *pending*; you collect cash or card at the booth and mark it paid. Good for low-friction, in-person events.
• Online payment — the customer pays during checkout. Which providers appear depends on the order currency: the checkout only offers providers configured for that currency (e.g. Paystack/Flutterwave for GHS and NGN, Stripe for international cards).
• Online payments are verified and the order amount is confirmed correct before it's marked paid — a customer can't underpay their way to a confirmed order.

Attendees reach your store at /e/{eventSlug}/store. They open a product, pick a variant and quantity, and Add to cart. The cart lives in the browser (per-event, in local storage), so it survives a refresh. They can adjust quantities, remove items, and on the checkout page add an optional per-item customization note (e.g. a name to print on a jersey).

1. 1

   Enter details

   On checkout the customer provides full name and email (required) and phone (optional). The confirmation and QR code are emailed to that address.

2. 2

   Choose how to pay

   They pick Pay Online or Pay at Pickup, depending on what you've enabled. For online, they also choose an available provider for the currency.

3. 3

   Place the order

   On submit, the order is created: prices and totals are calculated from your current catalog, stock is reserved, and a unique order number like SWAG-A1B2C3 is assigned.

4. 4

   Pay or confirm

   Online orders open the provider's payment modal/redirect, then confirm on return. Pay-at-pickup orders go straight to confirmation. The cart is cleared on success.

The confirmation page (/e/{eventSlug}/store/order/{orderId}) shows order status, a line-item breakdown, payment status, customer details, and a QR code to present at the swag booth. The customer also receives a confirmation email with the QR; you (the organizer) get a notification email for each new order. If an online payment is cancelled or fails, the order is saved in a *pending* / *failed* state and the page explains what to do next.

Manage everything from Store → Orders (/dashboard/events/{eventId}/store/orders). Each order carries two independent statuses: a pickup status (*Pending → Ready → Picked up*, or *Cancelled*) and a payment status (*Unpaid / Paid / Failed / Refunded / Cancelled*). The list is searchable by order number, customer name, or email, and filterable by pickup status and by payment.

1. 1

   Prepare the order

   When an order's items are bagged and waiting at the booth, click Ready to move it from *Pending* to *Ready for pickup*. The customer's confirmation page updates to "Ready for Pickup."

2. 2

   Hand it over

   When the attendee collects, click Picked up. This records who marked it and when. Picked-up orders are final and won't be restocked.

3. 3

   Collect on-site payment

   For a pay-at-pickup order that's still unpaid, open the order and click Mark as paid once you've taken payment. This sets payment status to *Paid* and stamps the completion time.

Open any order to reveal its actions. Cancel is available for orders that aren't already refunded, cancelled, or picked up — use it when an order won't be fulfilled. Refund appears only for paid orders that haven't been picked up yet. Both actions run through an authenticated organizer endpoint and restock the order's inventory automatically (at most once), so cancelling or refunding frees the stock back up.

Use Export orders (top-right of the Orders page) to download a CSV of whatever is currently filtered/searched — so you can export just unpaid orders, just one product's buyers, etc. The file is one row per line item (customer fields appear on the first row of each order) and is named store-orders-YYYY-MM-DD.csv.

Order Number, Date, Customer Name, Customer Email, Customer Phone,
Product, Variant, Quantity, Customization, Item Price, Order Total,
Currency, Payment Method, Payment Status, Pickup Status

The Store page header shows a Revenue tile alongside Active products, Orders (completed), and Pending pickup. Revenue counts only orders whose payment status is *completed* — pending and failed orders don't inflate your numbers.

The Orders page breaks the money down further with four cards: Total orders, Total revenue (split into online vs on-site), Pending payment (the value of unpaid orders, with a count), and Awaiting pickup. The online/on-site split lets you reconcile what was collected through a provider against what you took in cash at the booth.

Attendees never need to sign in to use networking. Your identity is tied to the device you're using — the same phone or browser keeps the same profile across visits. When an attendee saves a card for the first time, it's created automatically on that device.

Networking is an opt-in feature you control per event. Turn it on under Settings → Features (toggle labeled Networking, "Opt-in attendee directory and connections"). Once enabled, a Networking tab appears on the public event experience page (/e/[eventSlug]/experience) and a Networking card shows on your event dashboard. With the feature off, the tab is hidden and attendees can't create or view networking profiles.

1. 1

   Open the Networking tab

   On the event experience page, tap Networking and see the "Create your networking card" form.

2. 2

   Fill in the card

   Name is required. Role / company, interests, a short "Looking for" line, and a contact email are all optional. A "Show me in the directory" toggle is on by default.

3. 3

   Save

   Tap "Create my card" to save it. Your card is now in the directory (if visible) and you can scan QR codes to connect with others.

Each card carries up to 5 interests. You pick from a curated tag set with one tap, and can also type your own (an "Add your own..." field, capped at 30 characters per tag). Tags are de-duplicated so "Fintech" and "fintech" are treated as the same. The curated list keeps the directory consistent enough that interest-based matching actually works.

• Fintech · AgriTech · Startups · Investing · Software Engineering · AI & Data
• Product & Design · Marketing · Sales & BD · E-commerce · Health · Education
• Media & Content · Music & Arts · Fashion · NGOs & Impact · Logistics · Real Estate
• Tourism & Hospitality · Energy · Policy & Government · Mentorship · Hiring · Job Seeking

The directory powers a "People you should meet" strip at the top of your networking view. Suggestions are based on shared interests: they rank other visible profiles by how many of your interests they also have, drop anyone with zero overlap, and show the top 5. Ties break toward earlier joiners, so first movers surface first. Below the suggestions, you get the full directory with free-text search and one-tap interest filters (the most common tags in the room).

Browsing the directory is anonymous — it never exposes contact details. To actually exchange contacts, two attendees make a connection by scanning a QR code in person. Every card has a personal QR code (displayed under the My card tab). One attendee taps Scan to connect and points their camera at the other's QR; that single scan creates a mutual connection for both people.

1. 1

   Show your QR

   On My card, display your QR code. A note reminds you that sharing it shares your card (and email, if you added one).

2. 2

   The other person scans it

   They tap Scan to connect and point their camera at your QR.

3. 3

   A mutual connection is recorded

   Both attendees now see each other under My connections — including the email, if shared.

Connections are mutual and de-duplicated by design. It doesn't matter who scans whom — scanning the same person again just returns the existing connection ("You're already connected with ...") instead of creating a duplicate. From My connections, an attendee can export their collected contacts to CSV (name, role, interests, looking-for, email).

The privacy model is built around one principle: attendees only ever share what they explicitly chose to. Three controls back this up — directory visibility, contact-email reveal, and self-delete.

• Directory visibility — the "Show me in the directory" toggle. When off, your card is hidden from the public directory and from everyone's match suggestions, but you can still connect by QR.
• Contact email is connection-only — your email is hidden in the directory and matchmaking. It's shown only to people you've actually connected with via QR; sharing your QR is treated as consent to share your card and email with that person.
• Self-delete — from My card, "Delete card" removes your profile from the directory and deletes all of your connections. Former connections will no longer see your details. You can opt in again later from the experience page.

Your view lives at Dashboard → Event → Networking ("Attendee Networking"). It's restricted to the event owner and admins. The page opens with four stat cards — Members (opted-in profiles), Connections (mutual QR scans), In directory (visible vs. hidden split), and Top interest — followed by the full roster: name and email, role/company, interest tags, a Visible/Hidden badge, each member's connection count, and join date. Filter the roster by visibility (All / In directory / Hidden) and search across name, role, interest, or email.

Use Export CSV to download the whole roster — name, role/company, interests, looking-for, contact email, directory visibility, connection count, and join timestamp — for follow-up or for handing leads to sponsors and partners. The export reflects the same data shown on screen, including hidden profiles.

For moderation, hover over a roster row to reveal a remove (trash) action. Removing a profile deletes that attendee's card and every connection that references it. A confirmation dialog tells you exactly how many connections will be cleared. The attendee can opt in again afterward.

Before tickets are live — or for free events — you can collect a soft "I'm interested" signal from your public event page at /e/{slug}. Visitors tap a button, enter an email (and optionally a name), and land on your interest list. The same component also powers the ticket waitlist that appears once an event sells out, so both flows feel identical to attendees and feed the same dashboard.

Re-submitting the same email address will re-confirm rather than create a duplicate. When email is configured, the first signup gets a one-shot "You're on the list" confirmation.

Review everyone who raised their hand under Registration · Audience (/dashboard/events/{eventId}/audience). Two tabs — Interested and Waitlist — show your interested contacts; search by email or name, and use Export CSV to pull a list you can import into an email tool or re-target with a broadcast.

Referral links give each ambassador, partner, or channel a trackable code so you can see who actually sells tickets — not just who shares. Manage them under Growth · Referrals (/dashboard/events/{eventId}/referrals). Every link looks like /e/{slug}?ref=CODE, and every completed order placed after a visit through that link is credited to the code, even when no coupon is used.

1. 1

   Create a link

   Click New referral link, give it a Label (e.g. "Kofi — campus ambassador") — this is shown to buyers as "Referred by …" at checkout.

2. 2

   Set a code

   Type a Code (2–24 chars: letters, numbers, hyphens, underscores; unique per event) or leave it blank and hit Auto to generate one.

3. 3

   Optionally link a coupon

   Pick a coupon under Linked coupon so buyers arriving through the link get the discount applied automatically at checkout. Coupons come from Tickets → Coupons.

4. 4

   Share and watch

   Copy the shareable link and hand it out. The table tracks Clicks, Orders, Tickets, Revenue, and Conv. (orders per click) per code.

Deactivating a link stops it from tracking new clicks and attributing new sales, but existing attributions are kept — so historical numbers stay intact. You can reactivate a link at any time. Revenue figures count only completed purchases attributed to each code.

Send a one-off broadcast to ticket holders from Tickets → Email attendees (/dashboard/events/{eventId}/tickets/email-attendees). Write a subject and message or select a saved template, then narrow the audience by ticket status (All / Valid / Checked-in / Not checked-in / Refunded / Cancelled) and by ticket type. The composer de-duplicates by email and shows a live recipient count before you send.

Every broadcast is logged. Review delivery under Communications · Email history (/dashboard/events/{eventId}/emails, which redirects to …/emails/history). The top cards summarize Total, Sent, Delivered, Bounced / Spam, and Failed to send, and you can filter the list by any of those states. Open any message to see the rendered email, the recipient breakdown, and — for large sends — batch progress.

Each message can show a per-recipient status: Delivered, Opened, Clicked, Bounced, Marked spam, or Delayed. Bounced or complained addresses are added to a suppression list shown on the same page so you stop mailing addresses that hurt your sender reputation.

Reminders are emails scheduled to fire automatically relative to your event date. Manage them under Communications · Reminders (/dashboard/events/{eventId}/reminders). Each reminder fires at a trigger time, targets an audience, and uses either a template or a default layout you can override.

• Timing — pick a preset (7 days before, 24 hours before, 1 hour before, or 24 hours after) or set a custom date/time. Presets anchor to the event's start (or end, for the post-event follow-up), so the page warns you if the event has no start date yet.
• Audience — Attendees (valid ticket holders), Speakers (confirmed only), or Everyone (attendees plus confirmed speakers).
• Content — choose a communication template scoped to the audience, or leave it blank for a generated default reminder and optionally override the subject and body.

Reminders are grouped into Upcoming, Already sent, and Failed or cancelled. You can cancel any upcoming reminder before it fires. Use Apply defaults to bulk-create a sensible starter set in one click — it reports how many were created versus skipped (so it won't duplicate ones you already have).

The Flyer studio (/dashboard/events/{eventId}/flyers) generates promo images in your brand colours, rendered on-demand and updated live as you type. It has two tabs: Event promo for the event itself, and Speaker flyers for individual speakers. Every flyer embeds a tracked ticket QR pointing at your tickets page, with scans and sales attributed to the FLYER referral code.

• Event promo — choose a format (Status 9:16 for WhatsApp/Stories, Square, or Landscape), pick one of four typography-led designs, set an accent colour from your theme swatches, and edit the copy (name, tagline, date, venue, price chip). The price chip pre-fills from your ticket prices.
• Speaker flyers — pick a speaker from your list (or fill in details manually), choose an aspect ratio (Square, Story, Landscape, Twitter) and a template (Classic, Bold, Minimal), and tune colours. Save brand preset stores these so future flyers start on-brand.
• Batch — Generate for all speakers renders one flyer per speaker and downloads them together as a ZIP.

Export with Download flyer (re-rendered at 2x for retina/print), Share (uses the native share sheet with files where supported, otherwise copies the ticket link), or Copy ticket link. The photo design needs a cover image on the event; without one it falls back to an accent gradient. Where configured, Suggest taglines offers AI-written copy options.

Short links turn any long URL into a tidy, trackable /{shortCode} redirect. Create and manage them under Short links (/dashboard/short-urls): provide a destination URL, an optional custom code (otherwise a random 6-character code is generated), and an optional title/description. Each link resolves at /s/{shortCode}.

When someone opens a short link, it records a click and then forwards to the destination. Click tracking is best-effort: if it fails, the visitor is still redirected. Disabled and expired links show a friendly error page and fall back to the homepage after a short countdown.

• Toggle active/disabled to retire a link without deleting it (a disabled link shows the "Link Disabled" page).
• Edit the destination or metadata, or Copy the short URL to share.
• Click counts are shown per link so you can compare channels at a glance.

Featuring is a paid placement that surfaces your event in the Featured row on the public /events directory and sorts it ahead of the regular feed. Your event appears in the featured row (which still respects the visitor's active filters) for the length of your purchase period and is ordered with the soonest-to-expire feature first.

Only the event's owner or an admin can purchase. You choose a tier and pay via Paystack; the placement activates once payment is confirmed. Tiers are length-based and priced per currency, so the same purchase works worldwide (defaulting to GHS):

• 7 days — evt_feat_7
• 14 days — evt_feat_14
• 30 days — evt_feat_30

Open Organizations in your dashboard and click New organization. You only need a name to start — everything else (logo, brand color, public profile) is added later from Settings.

1. 1

   Name it

   Enter the organization name, e.g. "Cradx Events". This is the public-facing display name and can be changed any time.

2. 2

   Pick a URL slug

   A slug is auto-suggested from the name (lowercased, dashes for spaces). It becomes the handle in your public URL: /o/your-slug. You can override it, but it must be unique across the platform.

3. 3

   Create

   Click Create organization. You're taken straight into the new org, where you become its Owner automatically.

Every org has a public landing page at /o/{slug} — a full-bleed branded hero with your logo, name, description, follower and event counts, social links, and a grid of your upcoming and past public events. The soonest upcoming event is spotlighted as Next up. The page is off by default; you publish it from the Settings tab by toggling Public profile page on.

• Logo — upload a square image (PNG/JPG, under 2 MB). It anchors the hero and is used as the social-share preview image.
• Brand color — pick a preset swatch or paste a 6-digit hex (e.g. #6366F1). It drives the hero gradient and accent buttons across the public page. Defaults to indigo if unset.
• Description — a short bio, up to 500 characters.
• Website — a full https:// link, shown as a globe icon in the hero.
• Social handles — X/Twitter, Instagram, LinkedIn, Facebook, and YouTube. Enter just the @handle or username (or paste a full link) — the page builds the correct URL for you.

Orgs have three roles, in increasing order of power. Manage them from the Members tab.

• Owner — full control, including renaming, deletion, and restore. The creator is the Owner; the Owner role can't be changed or removed from the Members list.
• Admin — manages the org and every event under it. Admins can run any event whether or not they created it. They also see organization analytics and audience data.
• Creator — can create new events under the org and manage the ones they personally created, but can't see other people's events or organization analytics.

1. 1

   Invite

   On the Members tab (as Owner or Admin), click Invite, enter an email, and choose Admin or Creator. The invite appears under Pending invites and the person gets an email.

2. 2

   Accept

   The invitee accepts from their in-app invite inbox or the email link. They must be signed in with that exact email address and have a verified email — accepting with a mismatched or unverified email is rejected.

3. 3

   Adjust later

   Use the Admin/Creator toggle on each row to change a role, or the trash icon to remove a member. Revoke a pending invite with the × on its row.

The Events tab is the org's command center: every event attached to the org, filterable by Live, Upcoming, or Past (status is derived from each event's dates). Owners and Admins can open and manage any event; Creators see an Open button only on events they created and a read-only View link on the rest.

• Create under an org — when you create a new event, a Create under picker lets you choose one of your orgs (or keep it personal, "Just me"). Pick an org and the event is attached on creation.
• Attach an existing event — only the event's creator can attach their event to an org, and they must have at least Creator rights there. An event can belong to just one org at a time.
• Trash & restore — Owners and Admins can move an event to Trash from its row. Trashed events are hidden from the public org page but keep their data; restore them any time. Trash is a soft archive, not deletion.

Once your public profile is on, visitors see a Notify me button in the hero. They drop an email and join the org's follower list — no account needed. When you publish a new public event under the org, every follower gets a single announcement email.

• No duplicates — re-submitting the same email won't add you twice; the visitor just sees "You're already on the list."
• One email per event — the announcement fires once per event (guarded so a re-publish won't re-send), so followers aren't spammed.
• Spam-resistant — the form includes anti-spam measures and validates the email, and only works for orgs with a live public page.
• Unsubscribe anytime — every announcement email carries a one-click unsubscribe link, so followers can opt out at any time.

The Insights tab rolls every event in the org into one view. Switch the range between All time, This year, and 90 days — the window filters events by start date.

• Overview KPIs — total events (with live/upcoming/past breakdown), total attendees, check-in rate, revenue (after platform fees), and tickets sold with average fill rate.
• Audience — unique reach across all events, repeat-attendee rate, new people this period, and a cumulative growth chart plus your top attendees.
• Money — revenue, withdrawn, and available balance, drawn from each event's financial status, with a per-event revenue bar chart.
• Events leaderboard — a sortable table ranking each event by attendees, revenue, check-in rate, and engagement (High / Med / Low, scored from messages, questions, and polls).

The Audience tab unifies contacts across every event in the org into one searchable, deduped list — so you can see your whole crowd, not one event at a time. It has two views: Attendees and Subscribers.

• Attendees — everyone who holds a valid or used ticket to any org event, deduplicated by email. Each contact shows how many events they attended, when you first and last saw them, and whether they ever checked in.
• Segments — filter attendees by All, Repeat (≥2 events), Checked in, or New this year. Search by name or email on top of any segment.
• Subscribers — your follower list (the notify-me opt-ins), with each email and its subscribe date.

Both views have an Export CSV button that downloads exactly what's currently filtered. Attendee exports include name, email, events attended, first/last seen, and check-in status; subscriber exports include email and subscribe date.

Only the Owner can delete an org. Deletion isn't instant — it's a scheduled, reversible action with a 30-day grace period. Start it from Settings — Danger zone — Schedule deletion.

1. 1

   Schedule

   Confirm the dialog. A banner shows the date the org will be permanently removed.

2. 2

   Grace period

   For 30 days, the org and its events are archived and read-only. The public page goes dark and the org stops accepting new follows.

3. 3

   Restore (optional)

   Any time before the date, the Owner can click Restore — from the banner or the Settings danger zone — to cancel and reactivate the org.

4. 4

   Permanent removal

   After 30 days, deletion is finalized: events are detached and archived read-only, the slug is released for reuse, and the org is removed.

To list your business, go to Dashboard → Marketplace and fill out the application. It captures two things at once: your business profile (the vendor behind the listing) and your listing (what organizers actually see in the directory). Required fields are business name, category, bio, contact email, base location, and a listing title. Phone, service areas, a logo, a longer description, tags, portfolio images, and packages are all optional and can be added later.

• Category — pick one of 25 categories, from Catering and Photography to Tents & Marquees, Power & Generators, and Ushers. Pick Other if nothing fits.
• Base location — your home city (e.g. Accra). Service areas is a comma-separated list of other cities you cover (e.g. Accra, Kumasi, Takoradi); these feed the city filter organizers use.
• Contact email — where lead notifications are sent. It is shown to organizers who inquire, so use one you monitor.
• Tags — comma-separated keywords (e.g. vegan, outdoor, corporate) that make your listing easier to find in search.

1. 1

   Submit the application

   Complete the two cards — "About your business" and "Your listing" — then click Submit application. Your provider and listing are both created and your application enters the review process.

2. 2

   Wait for review

   Your listing goes into review and shows an "Under review" state. Approvals typically take 1–2 business days. You can't edit while pending — the submitted details are shown read-only.

3. 3

   Get notified

   When your listing is approved, you receive an email ("You're live on the Marketplace") with a link to your public listing. If it isn't approved, you get an "Application update" email with the reason and an Edit & resubmit link.

Once approved, manage everything from the Listing tab in Dashboard → Marketplace. You can edit your title, description, logo, service areas, tags, portfolio images, and packages. Edits save through Save listing and take effect immediately on the public marketplace — there's no re-approval step for content changes.

• Portfolio images — the gallery organizers see on your listing. Upload PNG, JPG, or WebP up to 8 MB each. The Free plan allows up to 8 images; Pro raises the cap to 20.
• Logo — a single image shown on your public profile and as your avatar on directory cards. Same formats and 8 MB limit.
• Packages — optional priced tiers. Each package has a name, a "price from" amount, a currency (defaults to GHS), and a free-text "what's included" line (e.g. "Buffet, 2 mains, up to 100 guests").

When an organizer submits the quote form on your listing, it's saved as a lead (an inquiry) and you're notified instantly. Each lead carries the organizer's name, email, and message, plus optional phone, event date, and budget. View them in the Leads tab; the tab label shows your running lead count.

• Email notification — a "You have a new lead" email lands at your contact email with the organizer's full details inline. Reply directly to the email address shown to start the conversation.
• In-dashboard table — every lead appears in the Leads tab with name, email/phone, event date, budget, message, and received date. Click any row to open the full inquiry. The lead is saved even if the notification email fails to send, so the dashboard is always the source of truth.
• CSV export — click Export CSV to download all leads for the listing (name, email, phone, event date, budget, message, received date). This is available on every plan, including Free.

Verified is a trust badge awarded to vendors who meet quality standards — it's separate from being approved and listed. Approval just means your listing is live; verification is an extra recognition signal that builds trust with organizers.

• On directory cards and your detail page, verified vendors show a green check beside the title; the detail page also adds a "Verified business" chip.
• In your own dashboard, a verified badge appears next to your business name and an overview card flips from "Listed" to "Verified — trust badge active".
• Being verified is independent of your plan and of any Boost — a Free vendor can be verified, and a Pro vendor isn't automatically verified.

There are two paid add-ons for vendors, available once your listing is approved, from Dashboard → Marketplace → Boost. They're independent — you can buy either, both, or neither. Checkout runs through Paystack in a popup; the effect is applied automatically a few seconds after payment, so the page polls until it lands (up to ~30 seconds).

• Boost listing (GHS 440, one-time) — pins your listing to the top of the marketplace for 30 days with a "Top Vendor" badge. After 30 days it simply returns to its normal position; re-boost any time.
• Go Pro (GHS 750, one-time) — unlocks the Pro vendor toolkit: 20 portfolio slots (up from 8), priority placement in directory results, and the lead analytics dashboard.

Placement in the directory is tiered: currently featured listings rank first (ordered by how recently they were boosted), then Pro vendors, then everyone else (each ordered newest-first). So Boost outranks Pro, and Pro outranks a standard Free listing — a Free vendor can still jump to the very top by boosting.

The Analytics tab is a Pro perk. On Free it shows a locked panel with an "Unlock with Pro" link; on Pro it renders a dashboard computed entirely from your real inquiries — no projected or sample numbers.

• Headline stats — total leads, plus a breakdown by status (new / replied / closed).
• 4-week trend — weekly buckets over the trailing four weeks, labelled "3w ago" through "This week". The "last 4 weeks" headline equals the sum of those bars, so the number and the chart always reconcile.
• Every figure is derived from each lead's creation time and status — if you have no leads yet, the analytics simply read zero.

Browse the public directory at /marketplace — no account required. Every vendor shown is an approved listing. Use the search box for free-text matching (across title, business name, tags, and description) and the Filters panel to narrow by category, city, budget tier, and a Top Vendors only toggle. Active filters appear as removable chips with a live vendor count.

1. 1

   Open a listing

   Click a vendor card to see the full listing — gallery, description, packages with starting prices, service areas, tags, and the vendor's bio.

2. 2

   Request a quote

   Use the Get a quote button (a sticky bar on the detail page, or the button on each card). Fill in your name and email (required), your message (required), and optionally phone, event date, and budget.

3. 3

   Send and wait for a reply

   On submit you get a confirmation that your request was sent. The vendor receives your details by email and replies to you directly — the marketplace itself doesn't host the conversation.

Creating an event costs nothing. There is no tier picker and no card required at creation — you fill in two steps and the event is live. A set of features are included for free with every event, regardless of whether you unlock paid add-ons.

• Ticketing — sell paid or free tickets. The platform doesn't charge to unlock ticketing; revenue comes from a per-ticket fee instead.
• Event store — sell merchandise alongside your event.
• Attendance certificates — issue verifiable certificates of attendance.
• Event capacity — every event starts with a free 100-attendee live-audience tier (see Capacity tiers below).

Everything beyond the free baseline is a one-time, per-event purchase — no subscription. You buy it once for a specific event and it's unlocked for that event. You manage all of this from the event's upgrade hub at Dashboard → your event → Upgrade your event, where each add-on shows as Active or Locked with its price and an Unlock button.

• Flyer generator — auto-design speaker and event flyers.
• Apple Wallet passes — issue signed Wallet passes with ticket purchases.
• Call for papers — collect and review speaker submissions.
• Broadcast emails — send bulk announcements to attendees.
• Analytics dashboard — attendee analytics and engagement reporting.
• Custom branding — replace EventisLive branding on public pages.
• Sponsor lead capture — let sponsors and exhibitors scan attendee badges to capture leads.
• Featured event — surface your event in the "Featured this week" row and sort it first in the directory; sold in 7, 14, or 30-day durations.
• Marketplace add-ons for vendors — Featured listing pins a vendor listing to the top with a badge, and Vendor Pro adds portfolio slots, lead analytics, and priority placement.

Capacity governs how many people can actively participate in your live experience — posting to the wall, asking questions, and adding to the gallery. Passive viewers and ticket-holders don't count against it. Every free event starts on the 100-attendee tier for free; you raise the limit with a one-time tier purchase from the Live audience capacity panel on the upgrade page, which shows a live meter of active participants against your current limit.

• 100 attendees — free (the default baseline).
• 500 attendees.
• 2,000 attendees.
• 10,000 attendees.
• Unlimited.

Features are priced across multiple currencies: USD, GHS (Ghana cedi), NGN (Nigerian naira), EUR, and GBP. When you upgrade a feature, the upgrade modal shows prices in your event's default currency and lets you pay through any configured payment provider that supports it.

Coupons can grant features without payment. They come in two types: lifetime grants (permanent access) and time-bound grants (valid for a set number of days). Each coupon has a code, feature(s) it grants, and usage limits.

• Lifetime grant — permanent. When redeemed on an event, it unlocks that feature for that event forever. Some lifetime coupons can be redeemed account-wide so all future events inherit the feature.
• Time-bound grant — valid for a set number of days after redemption. Must be redeemed on a specific event; the access expires after the duration.

1. 1

   Open the unlock modal

   On the upgrade page, click Unlock on any locked feature (or Upgrade on a capacity tier).

2. 2

   Enter the code

   Type your coupon code into the "Have a coupon?" field at the top of the modal and click Redeem.

3. 3

   Access is granted immediately

   Coupon redemption grants the feature right away. The feature flips to Active and you can start using it.

Open any event in your dashboard and go to Analytics (/dashboard/events/[eventId]/analytics). The page aggregates data straight from your event's live records — tickets, check-ins, messages, polls, Q&A, gallery, the swag store, grants, and mentor/speaker applications — so the numbers always reflect the current state, not a nightly snapshot. There's nothing to enable or configure; it populates as soon as your event has activity.

The top of the page is a row of headline KPIs: Participants, Tickets sold, Net revenue, Messages, and Questions. Net revenue is gross (tickets + store) minus the exact platform ticketing fee, and each card carries a sublabel for context — for example tickets sold shows how many have checked in, and net revenue shows the gross and fee it was derived from. Revenue is formatted in the event's own currency (USD, GHS, NGN, EUR, GBP, and so on).

• Conversion funnel — visitors → RSVPs/interested → ticket orders → tickets issued → checked in, with the conversion rate from each stage to the next. Stages only appear when there's data for them.
• Approval & answer rates — participant, question, and gallery approval rates, Q&A answer rate, check-in rate, and poll participation, each as a progress meter.
• Activity throughout the day — an hourly area chart of messages, participants, questions, and poll votes, with the peak hour called out.
• Ticketing & check-ins — sold vs. checked-in by ticket type, check-ins by hour, and a day-by-day check-in timeline.
• Content & commerce — top polls (with winning option), Q&A performance, message-type and gallery-reaction breakdowns, and — when present — swag store, grant, and mentor/speaker sections.

Sections render only when the underlying feature has data, so a simple ticketed meetup shows a lean page while a multi-track conference with a store and grants program shows the full set. Empty events fall back to an "Analytics not available" card rather than rows of zeros.

The dashboard loads a fresh snapshot each time you open it, and shows a Last updated timestamp under the header. For the day of the event, you have two ways to keep it current without reloading the page.

• Refresh — pulls a new snapshot on demand. The icon spins while it's fetching.
• Live refresh — a toggle that silently re-pulls the data every 30 seconds in the background. When it's on, the button turns green with a pulsing "Live" indicator and the timestamp note reads "auto-refreshing every 30s".

Two export controls sit in the dashboard header. CSV opens a menu of focused datasets; PDF generates a polished, full report. Both use the data already loaded on the page, so exports reflect whatever you're currently looking at.

• Summary report — a single CSV with topline metrics, engagement rates, ticket types, the check-in timeline, recent check-ins, and hourly activity. Always available.
• Ticket sales — one row per order: date, order number, ticket type, quantity, gross, fee, net, status, and buyer name/email. Appears when there are ticket purchases.
• Attendees — one row per attendee ticket: name, email, ticket type, quantity, checked-in (yes/no), status, and purchase time. Appears when tickets have been issued.
• RSVPs / interested — the email-capture list for people who registered interest. Appears when you have RSVPs.

CSV files are named like your-event-attendees-2026-06-28.csv and are written with a hardened CSV writer: values are quoted and escaped per RFC 4180, money is rendered in major units (e.g. 120.00, not 12000), and cells that begin with =, +, -, or @ are neutralized to prevent spreadsheet formula injection. They open cleanly in Excel, Google Sheets, or Numbers.

PDF opens a print-ready report page (/dashboard/events/[eventId]/analytics/export) that lays out your overview, engagement metrics, top polls, Q&A, peak activity, ticketing/check-ins, store, and grants on a branded sheet, then downloads it automatically and returns you to the dashboard. It's rendered as an A4 snapshot — great for sharing a recap with sponsors or stakeholders who don't have dashboard access.

If your events belong to an organization, the org page has an Insights tab that rolls every event up into one cross-event view (/dashboard/organizations/[orgId]). Where the per-event dashboard answers "how did this event do?", org insights answer "how is our whole program doing?" — total reach, repeat attendance, revenue across events, and a side-by-side leaderboard.

• Overview — total events (with live / upcoming / past breakdown), total attendees and check-in rate, revenue after platform fees, tickets sold, and average fill rate against capacity.
• Audience — unique reach across all events (de-duplicated by attendee email), repeat-attendee rate, new people this period, a cumulative growth chart, and your top attendees by number of events attended.
• Money — organizer revenue plus a payouts bar splitting withdrawn vs. available balance.
• Events — performance — a sortable leaderboard of every event by attendees, revenue, check-in rate, and an engagement tier (High / Med / Low) derived from message, question, and poll volume.

A range control at the top scopes everything to All time, This year (year-to-date), or the last 90 days. Because attendees are unified by email, someone who came to three of your events counts once toward unique reach and shows up in your repeat-attendee rate — which is the metric that tells you whether you're building a returning community or starting from scratch each time.