> ## Documentation Index
> Fetch the complete documentation index at: https://docs.soundchecklive.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Live page FAQ

> Straight answers to the 100 questions planners, bands, DJs, producers and venues ask about a guest-facing event page: publishing, privacy, the live schedule, status updates, song requests, tips, QR codes, venue screens, reliability, data and pricing.

This page answers the questions people ask when they choose a tool for a public or guest event page, whether they call it an event page, a guest page, a viewer link, an attendee app or a wedding website. Each answer starts with **Yes**, **Partly** or **No**, says how, and links the page with the detail.

![Public live page for a gig showing the event code, its status and the latest update](https://mintcdn.com/soundchecklive/YID1u3xi3y5B4ur8/images/gigs/live-page-light.png?fit=max\&auto=format\&n=YID1u3xi3y5B4ur8\&q=85\&s=c62dd4447da86351d640abb502e00d23)

When Soundcheck doesn't do something today, the answer says so and gives the best way to work around it.

> [!NOTE]
>
> **How to read the answers.** **Yes** means Soundcheck does it today. **Partly** means it covers part of the need, and the answer says which part. **No** means it doesn't, and the answer gives the workaround. A few questions ask whether a limit or fee exists; there, **No** means there isn't one. A question marked *Buyers ask this first* is one where the wrong answer usually loses the deal or embarrasses the client in front of guests.

> [!NOTE]
>
> **Early access:** publishing a new live page is rolling out gradually. Contact [info@soundchecklive.io](mailto:info@soundchecklive.io) if you'd like it turned on for your organization. A page you already published stays public, and you can still update it or take it down.

## Questions this page answers

* [Creating and publishing the page](#creating-and-publishing-the-page) (12 questions)
* [Privacy and who can see it](#privacy-and-who-can-see-it) (10 questions)
* [Live schedule](#live-schedule) (11 questions)
* [Status updates and announcements](#status-updates-and-announcements) (9 questions)
* [Song requests](#song-requests) (13 questions)
* [Tips and payments](#tips-and-payments) (6 questions)
* [QR codes and signage](#qr-codes-and-signage) (7 questions)
* [Guest engagement](#guest-engagement) (10 questions)
* [On-screen and venue display](#on-screen-and-venue-display) (5 questions)
* [Reliability and performance](#reliability-and-performance) (6 questions)
* [Data, compliance and pricing](#data-compliance-and-pricing) (11 questions)

## Deal-breakers at a glance

These 14 questions decide most evaluations. Soundcheck meets the need on 8 (including two where the answer is that no limit or fee exists), partly meets it on 3, and doesn't on 3.

| # | Question | Answer | Read more |
| - | - | - | - |
| 1 | A guest page in minutes, from what's already in the gig | Yes | [Publishing and managing](https://docs.soundchecklive.io/features/gigs/live-page/publishing.md) |
| 13 | Password-protect the page | No | [Codes and privacy](https://docs.soundchecklive.io/features/gigs/live-page/codes-and-privacy.md) |
| 16 | Crew times kept off the guest view | Yes | [The schedule on the page](https://docs.soundchecklive.io/features/gigs/live-page/schedule.md) |
| 21 | No account or app for guests | Yes | [What guests see](https://docs.soundchecklive.io/features/gigs/live-page/what-guests-see.md) |
| 23 | One schedule, the run of show, updates the page | Yes | [The schedule on the page](https://docs.soundchecklive.io/features/gigs/live-page/schedule.md) |
| 26 | Times in the venue's time zone | Yes | [What guests see](https://docs.soundchecklive.io/features/gigs/live-page/what-guests-see.md#schedule) |
| 38 | An urgent alert at the top | Partly | [Status updates and running late](https://docs.soundchecklive.io/features/gigs/live-page/status-updates.md) |
| 43 | Guests request songs | No | [Music requests](https://docs.soundchecklive.io/features/gigs/run-of-show/setlists/music-requests.md) |
| 58 | Platform fee on tips | No fee (no tipping) | [Tips and payments](#tips-and-payments) |
| 62 | A QR code for the page | No | [Codes and privacy](https://docs.soundchecklive.io/features/gigs/live-page/codes-and-privacy.md) |
| 82 | A venue screen recovers when Wi-Fi drops | Yes | [What guests see](https://docs.soundchecklive.io/features/gigs/live-page/what-guests-see.md#refreshing) |
| 84 | Holds up when everyone scans at once | Partly | [Codes and privacy](https://docs.soundchecklive.io/features/gigs/live-page/codes-and-privacy.md#wrong-codes) |
| 90 | What guest data is collected, and who owns it | Partly | [Codes and privacy](https://docs.soundchecklive.io/features/gigs/live-page/codes-and-privacy.md) |
| 96 | A cap on viewers | No cap | [Subscription plans](https://docs.soundchecklive.io/settings/billing/plans.md) |

## Worked example: a wedding band on a Saturday night

A wedding band's manager runs a 150-guest reception: ceremony at 4:00 PM, cocktails, dinner, first dance at 7:15 PM and dancing until 11:00 PM. The band loads in at 1:00 PM and soundchecks at 2:30 PM. Here's how the deal-breakers play out.

**1. Publish it from the gig**

The run of show already has every section. On the web, open the gig's **Export** menu and choose **Publish live page** (question 1). Load in and soundcheck are crew steps, so they start hidden from guests (question 16). Choose **Open page** to check the guest view.

**2. Share the code**

Soundcheck doesn't make a QR code (question 62). Choose **Copy link**, paste it into any QR generator, and print it on the table cards. Guests scan it and the page opens in their browser, with no account or app (question 21). Anyone with the code can see the page, so share it the way you'd share the venue address (question 13).

**3. Run late without editing every row**

Dinner runs long. On your phone, open the gig's **Live page** card and tap **15 min late** under **Schedule status**. Every guest's page shows "Running about 15 min behind schedule", and **Up next** shifts to match (question 27). Times stay in the venue's zone (question 26).

**4. Tell the room something**

Post a **Status note**, such as "Shuttles leave from the north entrance at 11:15". It shows in the status card at the top of everyone's page within a minute. Soundcheck doesn't send a push or text (questions 35 and 38).

**5. Handle requests**

Guests can't request songs from the page (question 43). Send the couple the **Music requests** form before the wedding for their must-play and do-not-play lists, and do-not-play matches warn you in the run of show (questions 46 and 50).

## Creating and publishing the page

> [accordion] 1. Can I make a guest-facing page for a gig in a few minutes, from what's already in the gig?
>
> **Yes.** The page reads the gig's run of show and key times, so there's nothing to rebuild. Choose **Publish live page** from the gig's **Export** menu on the web, or from the **Live page** card in the app. See [Publishing and managing](https://docs.soundchecklive.io/features/gigs/live-page/publishing.md).
>
> *Buyers ask this first.*

> [accordion] 2. Can I choose exactly what shows on the page, such as the schedule, the venue map, the dress code and the menu, and hide everything else?
>
> **Partly.** On the **Live page** tab you turn run of show sections on or off under **Run of show on the page**. The page always shows the date, hours and venue, and it has no venue map, dress code or menu blocks. Put a short dress code or parking line in the **Status note**. See [The schedule on the page](https://docs.soundchecklive.io/features/gigs/live-page/schedule.md).

> [accordion] 3. Can I preview the page as a guest sees it before I publish?
>
> **Partly.** There's no preview before publishing. Once it's published, **Open page** on the **Live page** tab shows exactly what guests see, so check it before you share the code. Sample gigs show a read-only sample of the tab. See [Publishing and managing](https://docs.soundchecklive.io/features/gigs/live-page/publishing.md).

> [accordion] 4. Can I publish, unpublish and republish the page whenever I want?
>
> **Yes.** **Take page down** stops the code right away, and publishing again issues a new code. Your section choices come back; the **Schedule status** and **Status note** are cleared. See [Publishing and managing](https://docs.soundchecklive.io/features/gigs/live-page/publishing.md#taking-the-page-down).

> [accordion] 5. Can I set a custom link, such as a short name for the event?
>
> **No.** Every page gets a random 8-character code, such as `HRBR-7Q4K`, and you can't choose it. Codes skip look-alike characters, so they're easy to read out. See [Codes and privacy](https://docs.soundchecklive.io/features/gigs/live-page/codes-and-privacy.md#how-codes-work).

> [accordion] 6. Can I put my company's or the client's logo, colours and cover photo on it?
>
> **Partly.** The page shows your organization's logo, brand name and accent colour from branding settings, and the gig's cover image as its poster. Branding is set once for your organization, so you can't put a different client's logo on each gig's page. See [Branding](https://docs.soundchecklive.io/settings/organization/setup.md#branding-email-and-notifications).

> [accordion] 7. Can I use my own domain?
>
> **No.** The page always opens on Soundcheck's address, at `/live/` followed by the code. Link to it from your own site instead. See [What guests see](https://docs.soundchecklive.io/features/gigs/live-page/what-guests-see.md).

> [accordion] 8. Can I make a page for each day of a multi-day event, or one page for the whole event?
>
> **Partly.** Each gig has one page, and a multi-day gig's schedule is grouped by day on it. For a separate page per day, make each day its own gig. See [Multi-day gigs](https://docs.soundchecklive.io/features/gigs/run-of-show/multi-day.md).

> [accordion] 9. Can I make the page from a template I've saved?
>
> **Partly.** A gig made from a template brings its run of show, and the page follows the run of show. The page itself isn't saved in templates, so you publish it and pick its sections on each gig. See [Templates and duplication](https://docs.soundchecklive.io/features/gigs/templates-and-duplication.md).

> [accordion] 10. Can the client edit their own page, such as a couple editing their wedding page?
>
> **No.** Only gig managers (Owner, Admin and Gig Coordinator) can change the page. The client follows the same schedule and status in the client portal. See [Client portal](https://docs.soundchecklive.io/features/client-portal/overview.md).

> [accordion] 11. Does the page work in other languages?
>
> **No.** The page is in English only today. Write your **Status note** and run of show titles in your guests' language; those show as you typed them. See [What guests see](https://docs.soundchecklive.io/features/gigs/live-page/what-guests-see.md).

> [accordion] 12. Can I add custom sections, such as FAQs, parking, accommodation or a gift registry link?
>
> **No.** The page has fixed blocks: status, your updates, when and where, and the schedule. Use the **Status note** (up to 500 characters) for one key message, such as parking, and keep FAQs and registries on the client's own site. See [Status updates and running late](https://docs.soundchecklive.io/features/gigs/live-page/status-updates.md#status-note).

## Privacy and who can see it

> [accordion] 13. Can I make the page private with a password?
>
> **No.** There's no password; the event code is the key, and anyone with it can see the page. Share the code only with the people who should have it, and choose **New code** if it spreads further. For one private link per party, use [guest pages](https://docs.soundchecklive.io/features/gigs/guests.md#the-guest-page). See [Codes and privacy](https://docs.soundchecklive.io/features/gigs/live-page/codes-and-privacy.md).
>
> *Buyers ask this first.*

> [accordion] 14. Can I keep the page out of Google search results?
>
> **Yes.** The code entry page and every event page tell search engines not to index or follow them. See [Codes and privacy](https://docs.soundchecklive.io/features/gigs/live-page/codes-and-privacy.md).

> [accordion] 15. Can I show different content to different audiences, such as guests, VIPs, vendors and crew?
>
> **Partly.** The live page is the same for everyone with the code. Each guest party can get its own [guest page](https://docs.soundchecklive.io/features/gigs/guests.md#the-guest-page) with their pass and their own items, the client sees the [client portal](https://docs.soundchecklive.io/features/client-portal/overview.md), and crew see the full run of show in Soundcheck. See [Codes and privacy](https://docs.soundchecklive.io/features/gigs/live-page/codes-and-privacy.md#who-can-see-what).

> [accordion] 16. Is there a separate view for crew with internal times that guests never see?
>
> **Yes.** Crew see the full run of show, with notes and cues, in the Soundcheck app and web. The live page shows only titles, times and locations; crew steps such as load in, soundcheck, rehearsal and load out start hidden, and items addressed to crew positions or marked **Surprise** never appear. Check the guest view with **Open page** before you share it. See [The schedule on the page](https://docs.soundchecklive.io/features/gigs/live-page/schedule.md).
>
> *Buyers ask this first.*

> [accordion] 17. Can I expire the link after the event?
>
> **No.** Codes don't expire on their own, and archiving the gig doesn't take the page down. Choose **Take page down** on the **Live page** tab after the event. See [Publishing and managing](https://docs.soundchecklive.io/features/gigs/live-page/publishing.md#taking-the-page-down).

> [accordion] 18. Can I see how many people opened the page?
>
> **No.** Soundcheck doesn't count views or visitors for live pages today. See [Codes and privacy](https://docs.soundchecklive.io/features/gigs/live-page/codes-and-privacy.md).

> [accordion] 19. Can I revoke a link that leaked and issue a new one?
>
> **Yes.** Choose **New code** on the **Live page** tab. The old code and link stop working right away, and everyone needs the new one. See [Publishing and managing](https://docs.soundchecklive.io/features/gigs/live-page/publishing.md#issuing-a-new-code).

> [accordion] 20. Does the page hide private details, such as the client's phone number, the crew list and costs, by default?
>
> **Yes.** Only schedule titles, times and locations, the venue, the date and your updates go out. Contacts, crew, notes, cues and money never appear. See [Codes and privacy](https://docs.soundchecklive.io/features/gigs/live-page/codes-and-privacy.md#who-can-see-what).

> [accordion] 21. Can guests view it without making an account or downloading an app?
>
> **Yes.** The page opens in any phone browser from the link, or at `/live` with the code. Nobody signs in. See [What guests see](https://docs.soundchecklive.io/features/gigs/live-page/what-guests-see.md#opening-the-page).
>
> *Buyers ask this first.*

> [accordion] 22. If the venue address is secret until the day, can I reveal it at a set time?
>
> **No.** The page can't reveal anything on a timer. Publish the page, or share its code, only when you're ready for guests to see the venue. See [Publishing and managing](https://docs.soundchecklive.io/features/gigs/live-page/publishing.md).

## Live schedule

> [accordion] 23. Does the page show the schedule from the run of show and update automatically when I change it?
>
> **Yes.** The page reads the run of show, and guests' pages refresh every minute. If your organization publishes run of show changes, guests see the last published version, the same one crew see. See [The schedule on the page](https://docs.soundchecklive.io/features/gigs/live-page/schedule.md).
>
> *Buyers ask this first.*

> [accordion] 24. Can I choose which run-of-show items appear publicly and rename them for guests?
>
> **Partly.** You turn whole sections on or off, and show or hide a section's crew items. To keep a single item off, address it to crew positions or mark it **Surprise**. Guests see the titles you gave the items; there's no separate guest title. See [The schedule on the page](https://docs.soundchecklive.io/features/gigs/live-page/schedule.md#choosing-whats-on-the-page).

> [accordion] 25. Does it show what's happening now and what's next?
>
> **Yes.** While the gig is live, the status card shows "Happening now" with a progress bar and "Up next" with its time, and the schedule marks rows **Now** and **Next**. See [What guests see](https://docs.soundchecklive.io/features/gigs/live-page/what-guests-see.md#status).

> [accordion] 26. Does it show times in the event's local time zone, whatever the guest's phone is set to?
>
> **Yes.** Every time shows in the gig's time zone (or your organization's when the gig has none), and the schedule says "Times are local to the venue." See [What guests see](https://docs.soundchecklive.io/features/gigs/live-page/what-guests-see.md#schedule).
>
> *Buyers ask this first.*

> [accordion] 27. If we run late, can the page show updated times without me editing every item?
>
> **Yes.** Set **Schedule status**, such as **Running 15 min late**. Guests see "Running about 15 min behind schedule", and now and next follow the delay; your run of show isn't changed. See [Status updates and running late](https://docs.soundchecklive.io/features/gigs/live-page/status-updates.md#schedule-status).

> [accordion] 28. Can I show set times for each act or stage at a festival or club night?
>
> **Yes.** Give each act a run of show section or item with its time and location, and the page lists them in time order with their times. See [The schedule on the page](https://docs.soundchecklive.io/features/gigs/live-page/schedule.md).

> [accordion] 29. Can guests build a personal schedule or favourite the sessions they want?
>
> **No.** Guests can't save or favourite items. A [guest page](https://docs.soundchecklive.io/features/gigs/guests.md#the-guest-page) shows each party a **Your schedule** card with the items your team put them on. See [What guests see](https://docs.soundchecklive.io/features/gigs/live-page/what-guests-see.md).

> [accordion] 30. Can guests add an item to their calendar?
>
> **Partly.** **Calendar** adds the whole event to the guest's calendar, from the first scheduled time to the last, with a link back to the page. It doesn't add single items. See [What guests see](https://docs.soundchecklive.io/features/gigs/live-page/what-guests-see.md#top-of-the-page).

> [accordion] 31. Can I show a countdown to the next moment, such as the first dance, doors or the headliner?
>
> **Partly.** The poster counts down in days ("Tomorrow", "In 3 days") and the status card shows "Up next" with its time. There's no minute-by-minute timer. See [What guests see](https://docs.soundchecklive.io/features/gigs/live-page/what-guests-see.md#status).

> [accordion] 32. Can I display the schedule on a screen at the venue, full-screen?
>
> **Partly.** Open the link in a browser on the screen's computer and make the browser full-screen; it refreshes every minute. The page is laid out for phones, and there's no dedicated display mode. See [What guests see](https://docs.soundchecklive.io/features/gigs/live-page/what-guests-see.md#refreshing).

> [accordion] 33. Can I show several stages or rooms side by side?
>
> **No.** The schedule is one list in time order. Each row shows its location, so guests can see which stage or room it's in. See [The schedule on the page](https://docs.soundchecklive.io/features/gigs/live-page/schedule.md).

## Status updates and announcements

> [accordion] 34. Can I post a live announcement, such as "Dinner is served" or "Shuttle leaves in 10 minutes", to the page?
>
> **Yes.** Type it in **Status note** and choose **Post note**. It shows as "Update from" your organization, with the time you posted it. One note shows at a time; a new one replaces the last. See [Status updates and running late](https://docs.soundchecklive.io/features/gigs/live-page/status-updates.md#status-note).

> [accordion] 35. Can guests get a push notification or text when I post an update?
>
> **No.** Soundcheck doesn't notify anyone when you post a note or a delay. Guests see it the next time their page refreshes, within a minute. Tell guests to keep the page open, or text them yourself for anything urgent. See [Status updates and running late](https://docs.soundchecklive.io/features/gigs/live-page/status-updates.md).

> [accordion] 36. Can guests choose to receive or mute updates?
>
> **No.** There's nothing to subscribe to or mute, because the page sends no notifications. Updates show only on the page. See [Status updates and running late](https://docs.soundchecklive.io/features/gigs/live-page/status-updates.md).

> [accordion] 37. Can I schedule announcements ahead of time?
>
> **No.** A note goes live when you post it. Draft your notes in advance and post each one from the app at the moment. See [Status updates and running late](https://docs.soundchecklive.io/features/gigs/live-page/status-updates.md#status-note).

> [accordion] 38. Can I post an urgent alert, such as weather, evacuation or a venue change, that shows at the top?
>
> **Partly.** The **Status note** shows in the status card at the top of the page, below the poster. It isn't styled as an emergency, and guests only see it when their page refreshes. Never rely on it for an evacuation; use the venue's PA and your safety plan. See [Status updates and running late](https://docs.soundchecklive.io/features/gigs/live-page/status-updates.md#status-note).
>
> *Buyers ask this first.*

> [accordion] 39. Can I pin an announcement?
>
> **Yes.** The status note stays on the page until you replace it or choose **Clear note**. See [Status updates and running late](https://docs.soundchecklive.io/features/gigs/live-page/status-updates.md#status-note).

> [accordion] 40. Can I see who has seen an announcement?
>
> **No.** Soundcheck doesn't track who opened the page or read a note. See [Status updates and running late](https://docs.soundchecklive.io/features/gigs/live-page/status-updates.md).

> [accordion] 41. Can a stage manager post updates from a phone during the show?
>
> **Yes.** Any gig manager can set **Schedule status** and post a **Status note** from the **Live page** card in the mobile app. See [Live page in the mobile app](https://docs.soundchecklive.io/features/gigs/live-page/mobile.md).

> [accordion] 42. Can I avoid flooding guests with too many notifications?
>
> **Yes.** The page sends no notifications at all, so guests are never flooded. They see your latest note and delay when they look. See [Status updates and running late](https://docs.soundchecklive.io/features/gigs/live-page/status-updates.md).

## Song requests

> [accordion] 43. Can guests request songs from the page?
>
> **No.** The live page has no song requests today. Before the event, the client fills in the **Music requests** form in the client portal with must-play, yes, off-list and do-not-play songs. See [Music requests](https://docs.soundchecklive.io/features/gigs/run-of-show/setlists/music-requests.md).
>
> *Buyers ask this first.*

> [accordion] 44. Can requests be limited to the band's repertoire or the DJ's library?
>
> **No.** Guests can't request songs from the page. The client's **Music requests** are matched against your song library, so you see which ones you already play. See [Music requests](https://docs.soundchecklive.io/features/gigs/run-of-show/setlists/music-requests.md).

> [accordion] 45. Can I turn requests on and off during the night?
>
> **No.** There are no guest requests to turn on or off. See [Music requests](https://docs.soundchecklive.io/features/gigs/run-of-show/setlists/music-requests.md).

> [accordion] 46. Can I add a do-not-play list so those songs can't be requested?
>
> **Partly.** The client's do-not-play list lives in **Music requests**, and a run of show song that matches one gets a warning. Guests can't request songs, so there's nothing to block on the page. See [Music requests](https://docs.soundchecklive.io/features/gigs/run-of-show/setlists/music-requests.md).

> [accordion] 47. Can guests upvote others' requests, so I see what the room wants?
>
> **No.** The page has no requests or voting. See [Music requests](https://docs.soundchecklive.io/features/gigs/run-of-show/setlists/music-requests.md).

> [accordion] 48. Can I see requests on my phone or tablet on stage in real time?
>
> **No.** There are no live guest requests. The client's music requests show in the app before the show. See [Setlists on mobile](https://docs.soundchecklive.io/features/gigs/run-of-show/setlists/mobile.md).

> [accordion] 49. Can I mark a request as played, queued or declined?
>
> **No.** Guest requests don't exist to mark. Add the client's requested songs to your sets in the run of show instead. See [Music requests](https://docs.soundchecklive.io/features/gigs/run-of-show/setlists/music-requests.md).

> [accordion] 50. Can the couple or client pre-request songs before the event, and can I see those separately?
>
> **Yes.** Send the client the **Music requests** form from the gig's **Forms**. Their must-play, yes, off-list and do-not-play songs show in the music requests panel, and requested songs are pinned in the song picker. See [Music requests](https://docs.soundchecklive.io/features/gigs/run-of-show/setlists/music-requests.md).

> [accordion] 51. Can guests leave a dedication or message with a request?
>
> **No.** Guests can't make requests. A client request can name a moment, such as **First dance** or **Last dance**. See [Music requests](https://docs.soundchecklive.io/features/gigs/run-of-show/setlists/music-requests.md).

> [accordion] 52. Can I stop spam or repeated requests from one guest?
>
> **No.** There are no guest requests, so there's nothing to spam. See [Music requests](https://docs.soundchecklive.io/features/gigs/run-of-show/setlists/music-requests.md).

> [accordion] 53. Can I export the requests afterwards?
>
> **No.** There are no guest requests to export. The client's music requests stay on the gig. See [Music requests](https://docs.soundchecklive.io/features/gigs/run-of-show/setlists/music-requests.md).

> [accordion] 54. Do requests feed into the setlist or the run of show?
>
> **Partly.** The client's music requests show in the run of show's song picker with their category, and do-not-play matches warn you. Guests can't make requests. See [Music requests](https://docs.soundchecklive.io/features/gigs/run-of-show/setlists/music-requests.md).

> [accordion] 55. Can I send played requests to Spotify or a playlist?
>
> **No.** Soundcheck imports songs from Spotify into your library, but doesn't send requests or sets to a playlist. See [Adding songs in bulk](https://docs.soundchecklive.io/features/gigs/run-of-show/setlists/importing-songs.md).

## Tips and payments

> [accordion] 56. Can guests tip the band or DJ from the page?
>
> **No.** The page has no tipping. Print your own Venmo, Cash App or PayPal QR code next to the live page's code if you take tips. See [What guests see](https://docs.soundchecklive.io/features/gigs/live-page/what-guests-see.md).

> [accordion] 57. Can a tip be attached to a song request?
>
> **No.** The page has neither tips nor requests. See [What guests see](https://docs.soundchecklive.io/features/gigs/live-page/what-guests-see.md).

> [accordion] 58. Where does the tip money go, and what fee does the platform take?
>
> **No.** Soundcheck takes no fee because the page has no tipping. Tips you collect through your own payment app go straight to you under that app's terms. See [What guests see](https://docs.soundchecklive.io/features/gigs/live-page/what-guests-see.md).
>
> *Buyers ask this first.*

> [accordion] 59. Can I connect my own Venmo, Cash App, PayPal or Stripe?
>
> **No.** The page can't link a payment account. Put your payment app's own QR code on your signage. See [What guests see](https://docs.soundchecklive.io/features/gigs/live-page/what-guests-see.md).

> [accordion] 60. Can I see tips per event and export them for tax?
>
> **No.** Soundcheck doesn't record tips. Use your payment app's reports, and ask your accountant how to handle tip income. See [What guests see](https://docs.soundchecklive.io/features/gigs/live-page/what-guests-see.md).

> [accordion] 61. Can I turn tipping off for a corporate or private event where it isn't appropriate?
>
> **Yes.** The page never shows tipping, so a corporate or private event's page has nothing to switch off. See [What guests see](https://docs.soundchecklive.io/features/gigs/live-page/what-guests-see.md).

## QR codes and signage

> [accordion] 62. Can I generate a QR code for the page?
>
> **No.** Soundcheck doesn't make a QR code today. Choose **Copy link** and paste the link into any QR code generator. The link stays the same until you issue a new code or take the page down. See [Codes and privacy](https://docs.soundchecklive.io/features/gigs/live-page/codes-and-privacy.md).
>
> *Buyers ask this first.*

> [accordion] 63. Can I download the QR in print quality (PNG, SVG, PDF)?
>
> **No.** There's no QR code to download. Most QR generators export SVG or high-resolution PNG from the copied link. See [Codes and privacy](https://docs.soundchecklive.io/features/gigs/live-page/codes-and-privacy.md).

> [accordion] 64. Can I have one permanent QR code that always points to my current event?
>
> **No.** Each gig has its own code and link. Print a new QR code for each event. See [Codes and privacy](https://docs.soundchecklive.io/features/gigs/live-page/codes-and-privacy.md#how-codes-work).

> [accordion] 65. Can I print a table card or poster with the QR and instructions?
>
> **No.** Soundcheck doesn't print signage. Make the card yourself with the QR code, the event code and "Open the link, or go to /live and enter the code". See [What guests see](https://docs.soundchecklive.io/features/gigs/live-page/what-guests-see.md#opening-the-page).

> [accordion] 66. Can I make different QR codes for different areas, such as tables, bar and stage, and see which gets scanned?
>
> **No.** Each gig has one code, and Soundcheck doesn't count scans. See [Codes and privacy](https://docs.soundchecklive.io/features/gigs/live-page/codes-and-privacy.md).

> [accordion] 67. Will the QR still work if I change the page's link?
>
> **Partly.** The link changes only when you choose **New code** or take the page down and publish again. Either way the old link stops working, so reprint the QR code. See [Codes and privacy](https://docs.soundchecklive.io/features/gigs/live-page/codes-and-privacy.md#when-a-code-stops-working).

> [accordion] 68. Can I put the QR code on an invitation for pre-event requests?
>
> **No.** Guests can't make requests from the page. You can print the page's link or code on invitations so guests can follow the schedule, and collect the couple's requests with the **Music requests** form. See [Music requests](https://docs.soundchecklive.io/features/gigs/run-of-show/setlists/music-requests.md).

## Guest engagement

> [accordion] 69. Can guests upload photos to a shared gallery from the page?
>
> **No.** The page has no photo uploads. Link guests to a shared album from your **Status note**. See [What guests see](https://docs.soundchecklive.io/features/gigs/live-page/what-guests-see.md).

> [accordion] 70. Can guests RSVP or confirm attendance from the page?
>
> **Partly.** The live page has no RSVP, and [guest pages](https://docs.soundchecklive.io/features/gigs/guests.md#the-guest-page) only show the RSVP your team sets on the guest list. [One-off guests](https://docs.soundchecklive.io/features/gigs/guests.md#one-off-guests) can answer from their own links, but they aren't added to the door list. See [Guests](https://docs.soundchecklive.io/features/gigs/guests.md).

> [accordion] 71. Can guests see a seating chart or find their table?
>
> **No.** The page has no seating chart or table finder. See [Guests](https://docs.soundchecklive.io/features/gigs/guests.md).

> [accordion] 72. Can guests answer a poll or Q\&A during a session?
>
> **No.** The page has no polls or Q\&A. See [What guests see](https://docs.soundchecklive.io/features/gigs/live-page/what-guests-see.md).

> [accordion] 73. Can guests leave a guestbook message?
>
> **No.** The page has no guestbook or comments. See [What guests see](https://docs.soundchecklive.io/features/gigs/live-page/what-guests-see.md).

> [accordion] 74. Can guests see a map of the venue with key areas marked?
>
> **Partly.** The page shows the venue's address with **Directions** to Google Maps, and each schedule row shows its location, such as "Garden terrace". There's no venue floor map. See [What guests see](https://docs.soundchecklive.io/features/gigs/live-page/what-guests-see.md#top-of-the-page).

> [accordion] 75. Can guests see the menu with allergen information?
>
> **No.** The page has no menu. A guest's meal choice shows on their [guest page](https://docs.soundchecklive.io/features/gigs/guests.md#the-guest-page) pass. See [What guests see](https://docs.soundchecklive.io/features/gigs/live-page/what-guests-see.md).

> [accordion] 76. Can guests see speaker or performer bios?
>
> **No.** The page shows schedule titles, times and locations only, never people. Put a performer's name in the item title if guests should see it. See [The schedule on the page](https://docs.soundchecklive.io/features/gigs/live-page/schedule.md).

> [accordion] 77. Can guests rate the event afterwards?
>
> **No.** The page has no ratings or feedback. See [What guests see](https://docs.soundchecklive.io/features/gigs/live-page/what-guests-see.md).

> [accordion] 78. Can I show sponsor logos on the page?
>
> **No.** The page shows only your organization's logo. See [Branding](https://docs.soundchecklive.io/settings/organization/setup.md#branding-email-and-notifications).

## On-screen and venue display

> [accordion] 79. Can I put the live schedule or now-playing on a TV or projector at the venue?
>
> **Partly.** Open the page's link full-screen in a browser on the screen; it shows now, next and the schedule, and refreshes every minute. It's laid out for phones, not a display mode, and it shows the current schedule item, not the song playing. See [What guests see](https://docs.soundchecklive.io/features/gigs/live-page/what-guests-see.md).

> [accordion] 80. Can I show song requests or a photo wall on a screen?
>
> **No.** The page has no requests or photos to show. See [What guests see](https://docs.soundchecklive.io/features/gigs/live-page/what-guests-see.md).

> [accordion] 81. Can I add the page as a browser source in OBS or a streaming tool?
>
> **Partly.** You can point a browser source at the page's link, but it's a full phone-style page, not a transparent overlay, and it can't be embedded in another website. See [What guests see](https://docs.soundchecklive.io/features/gigs/live-page/what-guests-see.md).

> [accordion] 82. Does the display recover on its own if the venue Wi-Fi drops?
>
> **Yes.** When a refresh fails, the page keeps showing the last update with "Showing the last update; we will keep trying to refresh.", and catches up on its own once the connection is back. See [What guests see](https://docs.soundchecklive.io/features/gigs/live-page/what-guests-see.md#refreshing).
>
> *Buyers ask this first.*

> [accordion] 83. Can I show the timer or a "starting soon" screen?
>
> **Partly.** Before the event the page shows a day countdown and "Starts with" the first item at its time. There's no clock timer or holding slide. See [What guests see](https://docs.soundchecklive.io/features/gigs/live-page/what-guests-see.md#status).

## Reliability and performance

> [accordion] 84. Will the page hold up when 2,000 people scan the QR at once?
>
> **Partly.** There's no cap on viewers, and correct codes never count toward the wrong-code limit, so a room on one Wi-Fi network isn't slowed down. Each phone checks for updates once a minute rather than holding a connection open. Soundcheck doesn't publish a load figure; for a very large event, contact [info@soundchecklive.io](mailto:info@soundchecklive.io). See [Codes and privacy](https://docs.soundchecklive.io/features/gigs/live-page/codes-and-privacy.md#wrong-codes).
>
> *Buyers ask this first.*

> [accordion] 85. Does the page load fast on a weak phone signal?
>
> **Partly.** It's a single text-first page with one optional poster image, and it refreshes once a minute rather than streaming. Soundcheck doesn't publish load-time figures. See [What guests see](https://docs.soundchecklive.io/features/gigs/live-page/what-guests-see.md).

> [accordion] 86. Does it work on old phones and every browser?
>
> **Yes.** It's a web page that opens in current mobile and desktop browsers with no app. See [What guests see](https://docs.soundchecklive.io/features/gigs/live-page/what-guests-see.md).

> [accordion] 87. Is the page accessible to screen readers and colour-blind guests?
>
> **Partly.** Status badges such as **Now**, **Next** and **Live** carry words, not just colour, and text on your accent colour is picked for contrast. Soundcheck hasn't published an accessibility audit of the page. See [What guests see](https://docs.soundchecklive.io/features/gigs/live-page/what-guests-see.md).

> [accordion] 88. What happens to the page if your service goes down during my event?
>
> **Partly.** A page that's already open keeps showing the last update and keeps retrying. New guests can't open it until the service is back. Keep a printed schedule at the door for big events. See [What guests see](https://docs.soundchecklive.io/features/gigs/live-page/what-guests-see.md#refreshing).

> [accordion] 89. Does the page show the last known schedule if the guest's signal drops?
>
> **Partly.** While the page stays open, it keeps the last schedule and says it's showing the last update. If the guest reloads with no signal, the page can't load. See [What guests see](https://docs.soundchecklive.io/features/gigs/live-page/what-guests-see.md#refreshing).

## Data, compliance and pricing

> [accordion] 90. What guest data does the page collect, and who owns it?
>
> **Partly.** Guests type only the event code; the page has no forms and asks for no name, email or phone number. The page shows your organization's gig data, which stays yours and comes with your workspace export. For Soundcheck's privacy terms or a data processing agreement, contact [info@soundchecklive.io](mailto:info@soundchecklive.io). See [Codes and privacy](https://docs.soundchecklive.io/features/gigs/live-page/codes-and-privacy.md).
>
> *Buyers ask this first.*

> [accordion] 91. Is there a cookie notice or consent where it's needed?
>
> **No.** The live page doesn't show a cookie notice of its own. If your client needs one, contact [info@soundchecklive.io](mailto:info@soundchecklive.io) before you share the page. See [Codes and privacy](https://docs.soundchecklive.io/features/gigs/live-page/codes-and-privacy.md).

> [accordion] 92. Can I collect guest emails for follow-up, with consent?
>
> **No.** The page doesn't collect emails. Keep guest contacts on the gig's guest list, imported from your RSVP tool. See [Guests](https://docs.soundchecklive.io/features/gigs/guests.md).

> [accordion] 93. Are minors' data or photos handled differently?
>
> **No.** The page collects no guest data or photos, so there's nothing to handle differently. Keep children's names out of schedule titles and status notes. See [Codes and privacy](https://docs.soundchecklive.io/features/gigs/live-page/codes-and-privacy.md).

> [accordion] 94. Can I delete all guest data after the event?
>
> **Partly.** The page stores no guest data. Choose **Take page down** to stop the code and clear your status note; deleting the gig removes its page entirely. See [Publishing and managing](https://docs.soundchecklive.io/features/gigs/live-page/publishing.md#taking-the-page-down).

> [accordion] 95. Is the live page included in my plan or an add-on?
>
> **Yes.** The live page is part of every plan, not an add-on. Publishing a new page is in early access while it rolls out; contact [info@soundchecklive.io](mailto:info@soundchecklive.io) to have it turned on. See [Subscription plans](https://docs.soundchecklive.io/settings/billing/plans.md).

> [accordion] 96. Is there a limit on guest views or connections?
>
> **No.** There's no cap on how many people open the page, and guests never use a seat. See [Subscription plans](https://docs.soundchecklive.io/settings/billing/plans.md).
>
> *Buyers ask this first.*

> [accordion] 97. Can I white-label the page so it doesn't show your brand?
>
> **Partly.** The page shows your logo, brand name and accent colour, on every plan. A small "Powered by Soundcheck" line always shows at the bottom, and the page runs on Soundcheck's address. See [Branding](https://docs.soundchecklive.io/settings/organization/setup.md#branding-email-and-notifications).

> [accordion] 98. Can an agency run pages for many clients from one account?
>
> **Partly.** Every gig gets its own page and code, so one organization can run pages for any number of clients. The branding is your organization's, not each client's. See [Publishing and managing](https://docs.soundchecklive.io/features/gigs/live-page/publishing.md).

> [accordion] 99. Can the page be linked from the client's own website or app?
>
> **Partly.** The client can link to the page's address, which stays the same until you issue a new code. It can't be embedded inside another site. See [Codes and privacy](https://docs.soundchecklive.io/features/gigs/live-page/codes-and-privacy.md).

> [accordion] 100. Is there an API or AI assistant connection to update the page?
>
> **Partly.** AI assistants connected through MCP can read a page with `get_live_page`: whether it's published, its link, delay, note and sections. They can't publish or update it; post updates in the Soundcheck web or app. See [MCP capability catalog](https://docs.soundchecklive.io/integrations/mcp-catalog.md).

## Related

> [card] [Live page](https://docs.soundchecklive.io/features/gigs/live-page.md)
>
> Start here: the ideas and a first publish

> [card] [Publishing and managing](https://docs.soundchecklive.io/features/gigs/live-page/publishing.md)
>
> The Live page tab, new codes and taking it down

> [card] [Status updates and running late](https://docs.soundchecklive.io/features/gigs/live-page/status-updates.md)
>
> Schedule status and status notes on the night

> [card] [Glossary](https://docs.soundchecklive.io/features/gigs/live-page/glossary.md)
>
> Live page terms, from event code to crew step


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.