Author: Codex

  • How do I create an automation?

    How do I create an automation?

    How do I create an automation?

    Short answer

    Create automations from the Automations area of the CRM board you want the rule to watch, then build the rule as a sentence using a trigger and an action.

    Learn moreHow do CRM automations work?How do CRM boards, groups, and columns work?

    Where to start

    • Open the CRM board that should run the automation.
    • Choose Automations, then choose Create Automation.
    • The automation belongs to that board unless you choose an action that moves or connects the item to another board.
    Learn moreHow do CRM automations work?How do CRM boards, groups, and columns work?

    Build the sentence

    • Choose the trigger first, such as a status changing, a row moving groups, a form submission arriving, or a date being reached.
    • Choose the action next, such as moving the item to another group, sending an email, creating a workspace, preparing a document, or updating another column.
    Learn moreHow do CRM boards, groups, and columns work?How do CRM automations work?

    Before turning it on

    • Confirm the column, group, board, and email template selections are correct.
    • Use a test lead before relying on the automation for a real client workflow.
    • If the automation references a column, ORCHESTRIS should keep using the stable system key even if the visible column name changes later.
    Learn moreHow do CRM boards, groups, and columns work?How do CRM automations work?

    Related articles

    How do CRM automations work?Learn moreHow do CRM boards, groups, and columns work?Learn moreHow can an automation create a workspace and send a magic link?Learn more

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

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

    Learn moreWhat happens when Trish cannot answer?What information should I include in a support request?

    What to include

    • Your role
    • Workspace name
    • Event name if relevant
    • Page URL
    • Device or browser
    • What you clicked
    • What happened
    • What you expected
    Learn moreWhat information should I include in a support request?

    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.
    Learn moreWhat happens when Trish cannot answer?

    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.
    Learn moreWhat should beta testers report first?

    Related articles

    What happens when Trish cannot answer?Learn moreWhat information should I include in a support request?Learn moreWhat should beta testers report first?Learn more

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

  • What is the Trends area for?

    What is the Trends area for?

    What is the Trends area for?

    Short answer

    Trends is planned as a research area for event styles, social media ideas, music, dances, and planning inspiration across platforms.

    Learn moreWhat are campaigns during beta?How do clients and guests request songs?

    Planned use

    • Search by platform or content type.
    • Filter by age range, date span, or trend category where available.
    • Use trend results for event planning inspiration, music ideas, social content, and client conversations.
    Learn moreHow do clients and guests request songs?

    Beta expectation

    • Trends may be expanded over time as reliable data sources and permissions are confirmed.
    • If a trends feature is visible but incomplete, report what platform or filter you were expecting to use.

    Third-party note

    • When a trend depends on another platform's rules or API, ORCHESTRIS should link to that platform's official documentation rather than copying steps that may change.

    Official third-party resources

    ORCHESTRIS links to official third-party documentation for setup details so vendor-specific guidance stays current.

    Related articles

    What are campaigns during beta?Learn moreHow do clients and guests request songs?Learn moreWhat should beta testers report first?Learn more

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

  • What is the Weather area for?

    What is the Weather area for?

    What is the Weather area for?

    Short answer

    Weather is intended to help event teams monitor forecast-sensitive events and make better readiness decisions for outdoor or travel-heavy work.

    Learn moreHow do I create an event?How do task readiness items differ from planning cards?

    When Weather matters

    • Outdoor ceremonies
    • Rooftop events
    • Tent events
    • Travel-heavy event days
    • Events with weather-sensitive equipment or load-in timing

    How to use it during beta

    1. Check the event date and venue location first.
    2. Use weather as a readiness reference, not as the only decision-maker for event logistics.
    3. Report any event where the weather section does not pull the expected location or useful forecast details.
    Learn moreHow do I create an event?What should beta testers report first?

    Workflow idea

    • Future readiness tasks can use weather context to remind staff to confirm rain plans, covered setups, load-in timing, or backup locations.
    Learn moreHow do task readiness items differ from planning cards?

    Related articles

    How do I create an event?Learn moreHow do task readiness items differ from planning cards?Learn moreWhat should beta testers report first?Learn more

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

  • How should I use Inventory?

    How should I use Inventory?

    How should I use Inventory?

    Short answer

    Inventory is for tracking gear, supplies, and resources that may be assigned to events or checked before staff handoffs.

    Learn moreWhat are task boards for?How do task readiness items differ from planning cards?

    What to track

    • Speakers
    • Lighting
    • Photo booth gear
    • Microphones
    • Computers or controllers
    • Display equipment
    • Decor, signage, or other event supplies

    How Inventory supports planning

    1. Inventory can help staff confirm that the right equipment is connected to the right event.
    2. It can also support readiness tasks, staff handoffs, and future package-based equipment suggestions.
    Learn moreWhat are task boards for?How do task readiness items differ from planning cards?

    Beta reporting

    • If an inventory field or workflow is missing, report what item type you were trying to track and how you expected to assign it to an event.
    Learn moreHow do task readiness items differ from planning cards?

    Related articles

    What are task boards for?Learn moreHow do task readiness items differ from planning cards?Learn moreHow do I prepare a workspace for beta testers?Learn more

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

  • How do Packages and Add Ons work?

    How do Packages and Add Ons work?

    How do Packages and Add Ons work?

    Short answer

    Packages and Add Ons are for organizing the services, upgrades, and optional extras a workspace offers so they can later connect to events, CRM leads, and proposals.

    Learn moreHow do CRM boards, groups, and columns work?How can an automation create a workspace and send a magic link?

    What to add

    • Core event packages
    • Photo booth add-ons
    • Lighting upgrades
    • Ceremony audio
    • Planning add-ons
    • Travel or staffing extras
    • Any repeatable service a workspace sells
    Learn moreHow do I prepare a workspace for beta testers?

    How this connects later

    1. Packages can help CRM leads track service interest.
    2. Event records can use package information for planning, staffing, inventory, and future agreement generation.
    3. Campaigns and automations can eventually use package data to guide follow-up.
    Learn moreHow do CRM boards, groups, and columns work?

    Beta setup tip

    • Keep package names clear and consistent so testers can understand what should be selected or attached to an event.
    Learn moreHow do I prepare a workspace for beta testers?

    Related articles

    How do CRM boards, groups, and columns work?Learn moreHow can an automation create a workspace and send a magic link?Learn moreHow do I prepare a workspace for beta testers?Learn more

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

  • What is the Vendors area for?

    What is the Vendors area for?

    What is the Vendors area for?

    Short answer

    Use Vendors to keep venue partners, photographers, caterers, planners, and other event partners organized so their details can be reused across events.

    Learn moreHow do I create an event?How do I edit an event timeline?

    What belongs in Vendors

    • Venue contacts
    • Photographers and videographers
    • Caterers
    • Florists
    • Planners
    • Rental companies
    • Any partner whose details may be reused across events
    Learn moreHow do I create an event?

    How Vendors should help events

    1. Vendor details can reduce repeated typing when creating or updating events.
    2. As the CRM and event workflows expand, vendor records can support autofill, event documents, and planning handoffs.
    Learn moreHow do I create an event?What should beta testers report first?

    Beta note

    • During beta, use Vendors as a central reference area and report any missing fields that would make real event planning easier.
    Learn moreWhat should beta testers report first?

    Related articles

    How do I create an event?Learn moreHow do I edit an event timeline?Learn moreWhat should beta testers report first?Learn more

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

  • What should I do if an event or timeline change does not save?

    What should I do if an event or timeline change does not save?

    What should I do if an event or timeline change does not save?

    Short answer

    If an event, timeline card, question, note, or song does not save, pause before refreshing, click or tap out of the field once, then check whether the change appears on another view.

    Learn moreHow do I edit an event timeline?How do hosts and guests use the planning portal?

    Expected save behavior

    • Most ORCHESTRIS fields should blur-save when you click or tap out of the field.
    • The screen should not jump to the top or reload just because a field saved.
    • Card data should remain in place after refreshing.
    Learn moreHow do I edit an event timeline?How do hosts and guests use the planning portal?

    Quick checks

    • Click or tap outside the field once.
    • Wait a moment for any retry status to clear.
    • Refresh only after giving the save action time to finish.
    • Check the same event from the workspace admin side when a host or guest entry seems missing.
    Learn moreHow do hosts and guests use the planning portal?How do I edit an event timeline?

    What to report

    • Field type
    • Card name
    • Role
    • Event name
    • Exact value that disappeared
    • Whether the issue happened after pressing save, clicking out, dragging, or refreshing
    Learn moreWhat information should I include in a support request?How do I edit an event timeline?

    Related articles

    How do I edit an event timeline?Learn moreHow do hosts and guests use the planning portal?Learn moreWhat information should I include in a support request?Learn more

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