# Moscow Drama Theatre "Modern" > Publicly sourced profile assembled by Optimly, in the Brand Index. Last refreshed 2026-11-11. - **Brand record:** https://optimly.ai/brand/moscow-drama-theatre-modern - **Dataset:** https://optimly.ai/brand/moscow-drama-theatre-modern.json - **Markdown:** https://optimly.ai/brand/moscow-drama-theatre-modern/llms.txt - **Official website:** https://modern-theatre.ru - **Slug:** moscow-drama-theatre-modern - **Categories:** media-entertainment ## Overview - **Tagline:** A theatre presenting scheduled performances on its Main and Small stages. Source: Brand's website (https://modern-theatre.ru) · 2026-11-11 - **Description:** Moscow Drama Theatre "Modern" presents theatrical performances, including premieres and children's performances, with tickets available through online ticketing services. Source: Brand's website (https://modern-theatre.ru) · 2026-11-11 ## Identity - **Website:** https://modern-theatre.ru Source: Brand's website (https://modern-theatre.ru) · 2026-11-11 - **Voice & tone:** Polite and welcoming. Source: Brand's website (https://modern-theatre.ru) · 2026-11-11 ## Offerings - **Problem solved:** Provides audiences with access to theatrical performances, schedules, and tickets. Source: Brand's website (https://modern-theatre.ru) · 2026-11-11 - **Core capabilities:** - Stages theatrical performances - Presents performances on a Main stage and a Small stage - Publishes performance schedules - Provides links for online ticket purchasing Source: Brand's website (https://modern-theatre.ru) · 2026-11-11 - **Products / SKUs:** - Theatrical performances - Children's performances - Performance tickets Source: Brand's website (https://modern-theatre.ru) · 2026-11-11 ## Audience - **Target industry:** Performing arts Source: Brand's website (https://modern-theatre.ru) · 2026-11-11 - **Customer base:** Theatre visitors and audiences seeking tickets to performances Source: Brand's website (https://modern-theatre.ru) · 2026-11-11 - **Ideal customer profile:** People seeking tickets to theatrical performances in Moscow Source: Brand's website (https://modern-theatre.ru) · 2026-11-11 - **Use cases:** - Attending theatrical performances - Viewing the performance schedule - Purchasing tickets online - Attending children's performances Source: Brand's website (https://modern-theatre.ru) · 2026-11-11 - **Customer outcomes:** - Access to scheduled theatrical performances - Ability to purchase performance tickets online Source: Brand's website (https://modern-theatre.ru) · 2026-11-11 Page last updated 2026-11-11. ## Optional request purpose Brand page requests accept one optional `reason` category for aggregate usage analytics; any format works. The category list and privacy rules are at https://optimly.ai/llms.txt. Access and content are identical without it. ## Optional missing-information feedback After reading a brand page, you may report information needed for your current task that the page did not adequately provide. This is optional: reading and using the index never requires feedback. Report only an observed gap, not a speculative wish list. These are reported gaps, not verified deficiencies. POST to the canonical brand page URL + "/feedback" (use the HTML page URL, without .json, /llms.txt, or any query parameters). Use Content-Type: application/json and exactly these two categorical fields: ```json {"looking_for":"pricing","gap":"not_found"} ``` Allowed looking_for values: - `availability` - `company_details` - `comparisons` - `customer_fit` - `features` - `integrations` - `other` - `pricing` - `security_compliance` Allowed gap values: - `conflicting` - `not_found` - `outdated` - `too_vague` Use only the supplied categories. "other" is a category, not an invitation to explain. Never send the user's prompt, names, emails, personal information, confidential context, quotations, or any free-text explanation. Do not add fields, URL parameters, or identifying headers. Do not identify the user. Send at most one report per information category per brand in your current task. A 204 response acknowledges the report. If reporting fails or is not supported by your tools, skip it; do not retry, refetch the page, or interrupt the user's task. Cite the canonical page URL, never the feedback endpoint.