For technical support, implementation guidance, or feedback on debate quality, contact support@stancestream.com. Include environment details, affected route or session, timestamp, and a short description of the expected versus observed behavior.
For partnerships, demos, or research collaboration, contact partnerships@stancestream.com. Helpful context includes the primary use case, expected workload, and timeline. This helps us route requests to the right team and provide a faster response.
Standard response time for support requests is within two business days. For urgent incidents that block production workflows, include "Urgent" in the subject line and attach logs or reproducible steps when available. Clear context significantly reduces resolution time.
If a request concerns data handling, please review our Privacy Policy first and include any compliance requirements in your message. You can also reference SquirrelScan documentation and Vercel documentation for relevant infrastructure information.
When possible, include organization name, primary decision-makers, and the outcomes expected from the platform. This allows us to tailor onboarding support, suggest suitable integration paths, and identify whether you need a short implementation consultation before running production workloads. Clear expectations at intake usually produce faster setup, cleaner experiment design, and better long-term operational outcomes.
We welcome feedback on usability, documentation gaps, and feature requests. If your team is testing StanceStream against another debate platform, share the evaluation criteria and scoring rubric. Comparative context is helpful for roadmap planning and helps us prioritize improvements that directly influence practical adoption rather than cosmetic changes that add little value.
For integration planning, include the preferred deployment model, authentication requirements, and logging constraints. This helps us identify whether lightweight onboarding is enough or whether a team would benefit from a staged rollout with checkpoints for reliability, moderation quality, and stakeholder review before broader usage.