Author: Codex

  • What happens when Trish cannot answer?

    What happens when Trish cannot answer?

    What happens when Trish cannot answer?

    Short answer

    When Trish cannot find a confident answer, you can open related support articles or send the unanswered question to ORCHESTRIS support for review.

    Related articles

    • If Trish is not confident, choose related articles to open the best matched support category on support.orchestris.app.
    • This is useful when the wording is close but not exact.

    Send to support

    • Choose the send-to-support option when the related articles do not answer the question.
    • ORCHESTRIS logs the unanswered question, the approximate page, the role, the best matched category, and the match score.
    • Support can then turn that question into a new help article.

    Privacy note

    • Trish support logs are meant for support improvement, not private conversations.
    • Do not paste passwords, private API keys, or sensitive payment details into a support question.

    Related articles

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

  • How do I ask Trish a question?

    How do I ask Trish a question?

    How do I ask Trish a question?

    Short answer

    Open Trish from the portal, type a question in plain language, and Trish will search the ORCHESTRIS help center for the closest published answer.

    How to ask

    1. Click or tap Trish from the lower corner of the portal.
    2. Type the question the way you would ask a person, such as how do I invite a host or where do I find song requests.
    3. Choose a suggested question if one matches what you need.

    What Trish searches

    • Trish searches published ORCHESTRIS help-center articles and support posts.
    • Trish does not make up an answer if the help center does not contain one.
    • Answers should include a short response, related article links, and a button when there is a useful ORCHESTRIS screen to open.

    Better search phrases

    • Include the role or page when it matters, such as host planning card, workspace admin CRM, or guest song request.
    • Use feature words like event, timeline, Spotify, photobooth, CRM, form, automation, or mobile if the first search is too broad.

    Related articles

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

  • What should I do if a page looks wrong in dark mode?

    What should I do if a page looks wrong in dark mode?

    What should I do if a page looks wrong in dark mode?

    Short answer

    If a dark-mode page shows white containers, unreadable text, or mismatched card backgrounds, report the page, role, and screen size so the styling can be corrected.

    What to look for

    • White boxes inside a dark-mode page
    • White text on white backgrounds
    • Inputs or cards using old styles
    • Modal or lightbox backgrounds that do not match the rest of the portal

    Quick checks

    • Refresh the page.
    • Confirm dark mode is enabled from the account menu if your portal supports the toggle.
    • Check whether the issue happens on desktop, mobile, or both.

    Report details

    • Send the role, page URL, tab name, and a screenshot if possible.
    • Visual-only fixes may not need a new support article unless the feature behavior changes.

    Related articles

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

  • What information should I include in a support request?

    What information should I include in a support request?

    What information should I include in a support request?

    Short answer

    Include your workspace, role, page URL, what you expected, what happened, and any exact error text so support can reproduce the issue quickly.

    Include context

    • Workspace name
    • Your role, such as workspace admin, staff, host, guest, or app owner
    • The event name if the issue is event-specific
    • The page URL or the tab where the issue occurred

    Describe the issue

    • What you were trying to do
    • What you expected to happen
    • What actually happened
    • Any exact error message, loading behavior, or missing button

    Helpful attachments

    • Screenshots are useful for visual issues.
    • Short screen recordings are useful for scrolling, mobile, drag-and-drop, and save behavior issues.
    • Do not include passwords or private API keys in screenshots.

    Related articles

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

  • How do I stay signed in and refresh on mobile?

    How do I stay signed in and refresh on mobile?

    How do I stay signed in and refresh on mobile?

    Short answer

    Mobile and PWA sessions should remember trusted devices where possible, while still letting users refresh content without breaking the current event view.

    Session behavior

    • ORCHESTRIS should keep users signed in on trusted devices when the browser or app allows secure session storage.
    • Users may still need to log in again after clearing browser data, switching workspaces, or using a private browser session.

    Refreshing

    • Pull-to-refresh should reload the current content without unexpectedly opening the first planning card.
    • If the page reloads into the wrong section, return to the dashboard and reopen the event.

    Security

    • Do not rely on IP address or device recognition alone for secure access.
    • Magic links and saved sessions should still respect workspace, role, and event permissions.

    Related articles

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

  • How does mobile card navigation work?

    How does mobile card navigation work?

    How does mobile card navigation work?

    Short answer

    On mobile, planning cards should open in a focused card screen with a back control so users can complete one card at a time without losing their place.

    Card view

    • Tapping a planning card should open that card's details in place or in a focused mobile view depending on the current portal layout.
    • The back control should sit below the phone safe area so it is not hidden by the camera, time, or battery area.

    Scrolling

    • When a card is open, the page behind it should not scroll by mistake.
    • The active card content should scroll only when the card content itself is longer than the screen.

    Consistency

    • Mobile card controls should match desktop behavior for notes, songs, questions, and blur-save fields.

    Related articles

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

  • Why can’t I edit a planning card?

    Why can’t I edit a planning card?

    Why can't I edit a planning card?

    Short answer

    A planning card may be locked, not assigned to your role, hidden from guests, or part of an event status that limits editing.

    Common reasons

    • The workspace admin locked the card.
    • The event is pending or locked.
    • The card allows guests to view it but does not allow guest input.
    • The card feature, such as questions, notes, or songs, may not be enabled.

    What to check

    • Look for whether the card has questions, songs, or notes enabled.
    • Ask the workspace admin or assigned staff to confirm whether the card should be editable.
    • Refresh the page if a card appears blank or does not open correctly.

    Expected behavior

    • Descriptions added by templates or admins may be view-only for hosts and guests.
    • Response fields should blur-save when editing is allowed.

    Related articles

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

  • How do guests view and download event photos?

    How do guests view and download event photos?

    How do guests view and download event photos?

    Short answer

    Guests use the event Photos tab or gallery link to view photos they are allowed to access and download images from the event gallery.

    Photo access

    • The Photos tab should appear for hosts and guests only when photos are available or a photobooth has been connected to the event.
    • Photo access should be connected to the event instead of a separate unrelated gallery.

    Filtering

    • Guests can filter by the person who submitted a photo when that information was collected.
    • Future face recognition may help people find photos they appear in, but access should still respect event permissions.

    Downloads

    • Guests should be able to download photos from the gallery when downloads are enabled.
    • Workspace admins and staff should keep admin controls separate from the guest gallery experience.

    Related articles

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

  • How do I turn guest requests on or off?

    How do I turn guest requests on or off?

    How do I turn guest requests on or off?

    Short answer

    Guest requests can be enabled or disabled for an event without deleting requests that were already collected.

    What the switch controls

    • Turning guest requests on should reveal or enable the existing event guest link.
    • Turning guest requests off should hide or disable guest participation without erasing already collected data.

    Why this matters

    • Hosts may want to collect requests early, then turn off guest submissions closer to the event.
    • Staff still need the collected data after guest access is closed.

    Where requests appear

    • Guest song requests should appear in the guest requests area, with top requested songs first and the full request list below.

    Related articles

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