# Feedback, Support & Roadmap How you shape CoreReflex: chat support, bug reports, generation votes, feature requests, and the honest public runway. Your signal is not a black hole. It feeds product priority and (for bugs) a **human-reviewed repair loop**. **On this page** - [Chat assistant & human support](#chat-assistant--human-support) - [Report a bug](#report-a-bug) - [Request a feature](#request-a-feature) - [Vote on generations (make the models smarter)](#vote-on-generations-make-the-models-smarter) - [Public roadmap](#public-roadmap) - [Feature upvotes (shipping)](#feature-upvotes-shipping) - [How feedback makes the product self-healing](#how-feedback-makes-the-product-self-healing) - [Privacy & safety](#privacy--safety) - [Related pages](#related-pages) --- ## Chat assistant & human support The **chat bubble** (bottom-right) appears on the marketing site, docs, pricing, blog, and your **dashboard**. | What you can do | How | |---|---| | **Ask a product question** | Type it. Answers stream live and are **grounded** in docs and product pages (source chips when available). | | **Talk to a human** | **Talk to a human** → email, name, what you need → **Request human**. Keep typing in the same thread; staff replies appear in the widget. | | **Open a support ticket** | Same form → **Create ticket**. The team follows up by email; one chat conversation maps to at most one ticket. | | **Rate a reply** | Thumbs on assistant messages help us improve grounding and tone. | Conversations persist on your device for the session. When a human resolves the thread, the widget hands you back to the AI assistant. More walkthrough: [Getting Started: The chat assistant](getting-started.md#the-chat-assistant). --- ## Report a bug The fastest path: 1. Open chat → describe **what you did**, **what you expected**, and **what happened**. 2. Choose **Talk to a human** or **Create ticket**. 3. Prefer **bug** language in the subject (“Cut failed after export”, “Render stuck at 90%”) so the ticket is categorized correctly. You can also email support if your team has a dedicated address from onboarding; chat is preferred because it attaches the conversation transcript automatically. **Tips for a fixable report** - Workspace and approximate time (browser timezone is fine). - Browser + whether dashboard or editor (`editor.corereflex.com`). - Project / composition name or a shareable link if you have one. - Screenshots or the exact error text. Never paste passwords or API keys. **What happens next (high level)** - A **support ticket** is filed for the team. - For **bug** (and some generation-failure) tickets, CoreReflex also opens an internal **repair brief** so engineering can investigate with a structured write-up. Fixes ship only after a **human reviews a pull request**. Nothing auto-merges into production from chat alone. --- ## Request a feature You can request a capability today in any of these ways: 1. **Chat.** Describe the job you need (“I need multi-avatar dialogue on slides”) and **Create ticket**. Use words like **feature request** or **I wish** so it lands in the feature category, not the bug queue. 2. **Human handoff**, if you want a conversation about priority or pricing fit. 3. **Generation feedback**: if the gap is “this model output is wrong,” use thumbs-down with a short reason (below); that steers quality routing, not the public roadmap board. The **public feature board** is live at **[/roadmap](/roadmap)**. Submit a titled request (signed in), **upvote** once per account, and see status (open → planned → building → shipped). Chat tickets and generation votes still feed quality and support; the board is the product-priority signal. --- ## Vote on generations (make the models smarter) On generated video and image work, **upvote / downvote** (where the product shows it) is not vanity: - **Upvotes** strengthen what your workspace treats as good style and craft for future prompts and director grounding. - **Downvotes** reduce the chance similar weak routes win when models are close. - Votes never train a third-party foundation model on your private assets without your enterprise agreement; they improve **routing and your workspace’s own preference memory** inside CoreReflex. Leave a short **reason** when you downvote (“hands wrong”, “off brand color”). That text is gold for support and for quality work. --- ## Public roadmap **→ [Interactive board: upvote & submit](/roadmap)** **→ [Shipped / finishing status (Coming Soon)](coming-soon.md)** The board is vote-ranked product signal. Coming Soon lists: - What recently **shipped** and where to use it. - What is **still finishing**, with plain status (including GPU-gated own models). - A **roadmap at a glance** table, with no fake “coming soon” buttons that do nothing. Themes on the forward runway (product language, not engine names): | Theme | What you get over time | |---|---| | **Native-stack generation** | Lower-cost CoreReflex image, video, long-form, and talking presenters as hardware comes online | | **Richer voice** | More languages, expressive delivery, and clone options you control, still CoreReflex-branded | | **Talking presenters** | Photo or persona → speaking clip on the timeline, with consent gates | | **Ingest & repurpose** | Paste a public video link (where allowed), long→shorts, reference-style briefs | | **Faceless & research films** | Stronger one-brief → editable film paths on CoreReflex’s stack | | **Capture** | Desktop / meeting audio into Cut | | **You shape the queue** | Feature board + upvotes; bugs from chat into the repair loop | Nothing on the roadmap promises a locked file as the only output: generations and pipelines keep landing as **editable projects** you can open in the studio. --- ## Feature upvotes (shipping) **Live today** - Chat → ticket with feature / general category. - Generation thumbs up/down. - Roadmap page + docs feedback via chat. **Live: public feature board** Open **[corereflex.com/roadmap](/roadmap)** (or `/roadmap` on your deployment): 1. Browse planned and community-requested capabilities. 2. **Upvote** when signed in (one vote per account per item; click again to remove). 3. Submit a short request (title + optional detail); sign-in required. 4. Status badges: *open* · *planned* · *building* · *shipped* (shipped items may link a guide). From the **chat bubble**, use **Report a bug** (repair path) or **Request a feature** (ticket + optional “Submit to roadmap” when signed in). **Rules of the board (so it stays useful)** - One vote per user per item; no vote buying. - Duplicates may be merged by staff into the clearest title. - Security-sensitive or illegal requests are removed. - Upvotes inform priority; they do not replace engineering judgment, safety, or legal constraints. Narrative runway (what’s finished vs gated): [Coming Soon](coming-soon.md). --- ## How feedback makes the product self-healing CoreReflex is built so the product **learns from real use without going rogue**: | Signal | What it improves | Guardrail | |---|---|---| | Chat Q&A | Docs grounding and FAQ gaps | Answers decline when nothing is grounded | | Bug ticket from chat | Engineering repair brief + human-reviewed PR | **Never auto-merge**; owner reviews | | Generation up/down | Model routing + workspace style memory | Scoped to your workspace / platform quality, not silent third-party training | | Feature request / future upvotes | Roadmap ordering | Public status, no fake ship dates | | Failed generation report (in product) | Ticket with job/run ids for staff | Linked diagnostics, no credit games | “Self-healing” means **faster, structured repair and smarter defaults**, not an unattended agent rewriting production without a person in the loop. --- ## Privacy & safety - Do not put passwords, full API keys, or payment card numbers in chat. - Support transcripts may be used to fix your issue and improve the product experience under our [Privacy](/privacy) policy. - Likeness, voice clone, and persona work still require **consent** flows in the product. Chat cannot bypass those gates. --- ## Related pages - [Coming Soon / Roadmap](coming-soon.md): the public runway. - [Getting Started](getting-started.md) covers chat assistant basics. - [Plans & Billing](plans-and-billing.md): what each plan includes. - [User guide home](README.md) is the full map of live features. Have something you need yesterday? Open the chat bubble and say so. That is the fastest path into both support and the product queue.