Author: Codex

  • What should I do if a timeline card does not open on mobile?

    What should I do if a timeline card does not open on mobile?

    What should I do if a timeline card does not open on mobile?

    Short answer

    If a mobile timeline card does not open, refresh the page, try another card, and report the role, device, event, and whether the page stopped accepting taps afterward.

    Quick checks

    • Refresh the event page.
    • Try another card in the same timeline.
    • Try opening the same card on desktop if available.
    • Confirm the card is visible to your role.

    What should happen

    • On smaller screens, opening a card should move to a focused card detail view or open a clean mobile-friendly card panel.
    • The back control should be reachable below the phone camera and status area.
    • The page behind the card should not scroll while the card is open.

    What to report

    • Device model
    • Browser or app
    • Role
    • Event name
    • Card name
    • Whether tapping stopped working after the card failed to open

    Related articles

    Last updated for the ORCHESTRIS 2.0 support knowledge-base rollout.

  • How do archived photobooths work?

    How do archived photobooths work?

    How do archived photobooths work?

    Short answer

    Used photobooths should move to an archived area so active setup stays clean while event galleries remain available from the linked event.

    Why archive

    • Archiving keeps the workspace photobooth list focused on active or upcoming use.
    • It prevents old sessions from looking like current add-ons.

    What should stay available

    • Workspace admins and assigned staff should still be able to access the event gallery.
    • Hosts and guests should still be able to view allowed event photos from the event Photos tab or gallery link.

    What should not happen

    • Archiving should not delete event photos.
    • Archiving should not remove photos from the event record.
    • Archived sessions should not confuse users into thinking an old photobooth is active.

    Related articles

    Last updated for the ORCHESTRIS 2.0 support knowledge-base rollout.

  • How do I test a photobooth before an event?

    How do I test a photobooth before an event?

    How do I test a photobooth before an event?

    Short answer

    Create or open the linked photobooth, upload or capture test photos, verify the live display rotation, then remove test photos before guests use it.

    Before testing

    • Confirm the photobooth is linked to the correct event.
    • Set the background image, QR code size, QR position, border options, and display text.
    • Launch the display in the screen orientation you plan to use at the event.

    Test flow

    • Scan the QR code.
    • Capture or upload a test photo.
    • Confirm the new photo appears in the live rotation without refreshing.
    • Confirm the background image still appears between photos if that display mode is expected.

    Clean up

    • Use the admin gallery tools to remove test photos from display or delete them before the event starts.
    • Confirm host and guest galleries show only the photos that should be available.

    Related articles

    Last updated for the ORCHESTRIS 2.0 support knowledge-base rollout.

  • Why can’t a guest request songs?

    Why can’t a guest request songs?

    Why can't a guest request songs?

    Short answer

    Guests can request songs only when guest access is enabled, the event is active, and the planning card is both guest-visible and song-enabled.

    What to check

    • Guest requests are turned on for the event.
    • The guest is using the guest link.
    • The card is marked so guests can view it.
    • Song selection is turned on for that card.
    • The event is not locked in a way that blocks guest input.

    Spotify is not required

    • If Spotify search is unavailable, guests should still be able to use manual song entry when the card allows song requests.
    • Manual entries are useful for remixes, private edits, live versions, or songs that do not appear in search.

    What to report

    • Send the event name, card name, role, and whether the Spotify search, manual input, or entire song section is missing.

    Related articles

    Last updated for the ORCHESTRIS 2.0 support knowledge-base rollout.

  • What can a guest do in an event?

    What can a guest do in an event?

    What can a guest do in an event?

    Short answer

    Guests only see guest-enabled event areas, such as allowed planning cards, guest song requests, and photo galleries when those features are enabled for the event.

    Common guest access

    • View guest-visible event information.
    • Request songs on song-enabled guest cards.
    • Heart other guest song requests when guest voting is available.
    • View and download event photos when the gallery is available.

    What guests should not see

    • Workspace admin settings
    • Staff-only tabs
    • Billing
    • Internal documents
    • Cards that are not marked for guest viewing

    If guests cannot participate

    • Confirm guest requests are turned on.
    • Confirm the specific card is guest-visible and song-enabled if the guest is trying to request music.
    • Confirm the event link is the guest link, not a host or staff-only route.

    Related articles

    Last updated for the ORCHESTRIS 2.0 support knowledge-base rollout.

  • What can a host edit in an event?

    What can a host edit in an event?

    What can a host edit in an event?

    Short answer

    A host can edit the event planning fields that are enabled, unlocked, and available under the event's current status. Admin-only descriptions and locked cards should not be editable.

    Usually editable

    • Enabled questions
    • Enabled notes fields
    • Song requests on song-enabled cards
    • Account profile details
    • Guest-request controls when the workspace allows hosts to manage them

    Usually not editable

    • Template descriptions
    • Admin-only internal notes
    • Locked cards
    • Staff-only event status controls
    • Workspace admin settings

    Status matters

    • Active events can allow host editing.
    • Pending or locked events should limit editing to staff according to the workspace workflow.

    Related articles

    Last updated for the ORCHESTRIS 2.0 support knowledge-base rollout.

  • What should I check before inviting a client or host?

    What should I check before inviting a client or host?

    What should I check before inviting a client or host?

    Short answer

    Before sending a host link, review the event details, status, timeline, visible cards, guest-request setting, documents, and any features the host should use.

    Event details

    • Confirm event name, date, time, venue name, location, and maps link.
    • Check that the event status allows the host to edit if they need to complete planning.

    Planning visibility

    • Open the timeline and confirm the correct cards are visible to hosts.
    • Lock any cards the host should not edit.
    • Make sure notes and questions only appear where they are supposed to.

    Links and features

    • Copy the generated host link from the event.
    • Turn guest requests on or off according to the event workflow.
    • Confirm documents, photos, photobooth, or music features only appear when they are meant to be used.

    Related articles

    Last updated for the ORCHESTRIS 2.0 support knowledge-base rollout.

  • How do I prepare a workspace for beta testers?

    How do I prepare a workspace for beta testers?

    How do I prepare a workspace for beta testers?

    Short answer

    Before inviting beta testers, confirm branding, event templates, staff access, host links, guest settings, core documents, and any add-ons being tested.

    Workspace setup

    • Confirm branding and logo placement.
    • Check account and company information.
    • Confirm staff profiles and staff types.
    • Review docs, packages, inventory, and music connection if those areas are being tested.

    Event setup

    • Create at least one test event with a timeline.
    • Generate host and guest links.
    • Assign staff if staff workflows are being tested.
    • Enable only the features the tester should use.

    Support setup

    • Make sure Trish is visible unless the tester is specifically testing the hidden state.
    • Ask testers to use Trish first, then send unanswered questions to support when the answer is missing.

    Related articles

    Last updated for the ORCHESTRIS 2.0 support knowledge-base rollout.

  • How do CRM and campaigns connect?

    How do CRM and campaigns connect?

    How do CRM and campaigns connect?

    Short answer

    CRM data should help campaigns know who to contact, what event or lead data to use, and which workflow stage should trigger communication.

    CRM source data

    • Lead name
    • Email address
    • Event type
    • Event date
    • Status or group
    • Assigned owner
    • Package or service interest

    Useful campaign triggers

    • When a lead submits a form
    • When a lead moves to a specific group
    • When an event is created
    • When an event date is approaching
    • When a planning item needs attention

    Safety checks

    • Campaigns should preview recipients before sending.
    • Email templates should be reviewed before being automated.
    • Do not send test emails to real clients unless the campaign is clearly ready.

    Related articles

    Last updated for the ORCHESTRIS 2.0 support knowledge-base rollout.

  • What are campaigns during beta?

    What are campaigns during beta?

    What are campaigns during beta?

    Short answer

    Campaigns are planned as CRM-connected email and outreach workflows. During beta, use them for testing how leads, clients, and event workflows should trigger communication.

    Campaign purpose

    • Campaigns should eventually help send structured outreach connected to CRM stages, event dates, client status, or internal workflow triggers.

    Beta expectation

    • Campaign tools may be available in phases while email sending, templates, and CRM triggers are tested.
    • Do not rely on a campaign for a live client communication unless the workspace has already verified the workflow end to end.

    What to test

    • Whether campaign pages load correctly
    • Whether templates save
    • Whether CRM-related triggers are clear
    • Whether the right audience would be selected before sending

    Related articles

    Last updated for the ORCHESTRIS 2.0 support knowledge-base rollout.