Category: Contact Support

ORCHESTRIS support articles for Contact Support.

  • How do I report beta feedback from the portal?

    How do I report beta feedback from the portal?

    How do I report beta feedback from the portal?

    Short answer

    Use Trish or the report-a-problem area to describe what happened, where it happened, and what you expected so the ORCHESTRIS team can reproduce the issue.

    What to include

    • Your role
    • Workspace name
    • Event name if relevant
    • Page URL
    • Device or browser
    • What you clicked
    • What happened
    • What you expected

    When to use Trish

    • Ask Trish first when the issue may already have a help-center answer.
    • If Trish cannot answer, choose the send-to-support option so the unanswered question is logged and emailed to support.

    When to use report-a-problem

    • Use the report tool for visual bugs, broken buttons, save failures, layout issues, or workflows that need a product change instead of a support answer.

    Related articles

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

  • What should beta testers report first?

    What should beta testers report first?

    What should beta testers report first?

    Short answer

    Beta testers should prioritize access problems, save failures, broken buttons, confusing workflows, mobile layout issues, and anything that blocks completing a real event.

    Highest priority

    • Login or magic-link problems
    • Events, planning cards, CRM rows, forms, or songs not saving
    • Buttons that appear clickable but do nothing
    • Critical errors, blank pages, or endless loading
    • Mobile screens where controls are hidden behind the phone safe area

    Medium priority

    • Confusing labels
    • Missing help text
    • Dark-mode contrast issues
    • Unexpected page jumps or scroll behavior
    • Features that work but feel hard to understand

    Lower priority

    • Small wording preferences
    • Purely visual polish that does not block the workflow
    • Ideas for future features that do not affect the beta workflow.

    Related articles

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

  • 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.

  • 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 contact ORCHESTRIS support?

    How do I contact ORCHESTRIS support?

    How do I contact ORCHESTRIS support?

    Short answer

    Use Trish first for help-center answers. If Trish cannot answer, send the question to support so the team can review it and improve the knowledge base.

    Best way to ask

    • Include what you were trying to do, the page you were on, the workspace or event involved, and what happened instead.

    Unanswered Trish questions

    • If Trish cannot find an answer, choose the send-to-support option. ORCHESTRIS should log the question for the owner team and send an email notification to support.

    Why this matters

    • Every unanswered question helps build a stronger support article so the next person can get an immediate answer.

    Related articles

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