Intertwined evolves based on teacher feedback. Many of the features in the platform today exist because teachers asked for them. Here's how to make your voice heard.
Reporting a Bug
A bug is when something in the platform isn't working as it should. Examples:
A button that doesn't respond to clicks
A page that won't load
Data that displays incorrectly
A simulator behavior that doesn't match documentation
An error message you don't understand
How to report a bug:
Email [email protected] with:
1. A clear subject line e.g., "Bug: Gradebook not updating after assessment completion"
2. Description of the issue What's happening, and what you expected to happen instead.
3. Steps to reproduce Walk through exactly what you did, in order, leading up to the bug. Example:
Opened classroom "Personal Finance – Period 1"
Clicked Gradebook tab
Selected Course "Personal Finance Core Foundations (2e)"
Selected Unit "1. Financial Responsibility"
Noticed that student Evan Johnson's grade for "Wants vs. Needs" shows 0% despite him telling me he submitted
4. Environment details
Browser (Chrome 130, Safari 17, etc.)
Operating system (Mac, Windows, Chromebook)
Device type (laptop, tablet, phone)
5. Screenshots or screen recording A picture is worth a thousand words. Capture the bug visually whenever possible. Screen recordings are even better for interaction bugs.
6. Impact and urgency
How many students or classrooms are affected?
Does it block teaching?
Is there a workaround?
The more complete your bug report, the faster we can investigate.
Requesting a Feature
A feature request is a suggestion for something new or improved. Examples:
"It would be helpful if I could bulk-delete assignments"
"I'd love an integration with [specific LMS]"
"Can the Gradebook show class median in addition to class average?"
"I wish I could differentiate assignments by student"
How to request a feature:
Email [email protected] with:
1. A clear subject line e.g., "Feature Request: Bulk-delete assignments"
2. The problem you're trying to solve Don't just describe the feature — describe the underlying need. Example: "At end of year, I have 80+ old assignments cluttering my Assignments tab. Deleting them one at a time takes 30 minutes."
3. Your proposed solution What would the feature look like? Be as specific or as open as you like.
4. How often it matters Daily? Weekly? End-of-year only? Frequency affects priority.
5. Workarounds you've found If you've found a way to accomplish your goal without the feature, mention it. This helps us understand whether the request is a blocker or a nice-to-have.
6. Whether other teachers have similar needs If you've talked to colleagues who've expressed the same need, mention it. Multi-teacher requests get higher priority.
What Happens After You Submit
For bugs:
Support acknowledges receipt within the response window for your plan tier
Engineering investigates and reproduces the bug
A fix is prioritized based on severity and impact
You're notified when the fix is deployed
The fix appears in your portal automatically — no action needed on your end
For feature requests:
Support acknowledges receipt within the response window for your plan tier
Product team reviews the request and adds it to consideration list
Highly requested or strategically important features get added to the roadmap
You may be invited to beta test or provide additional input
When the feature ships, you're notified
Not every feature request gets built. Our team balances individual requests against broader product strategy, technical feasibility, and resource availability. But every request is read, considered, and contributes to our understanding of teacher needs.
Voting for Existing Requests
If a feature you want has been previously requested by another teacher, your voice still matters. Adding your support to existing requests signals demand to the product team. Mention any features you've heard discussed (in webinars, with other teachers, in the support center) and we can connect your support to existing tickets.
Beta Testing
Some teachers are invited to beta test new features before public release. Beta testers:
Get early access to upcoming features
Provide feedback that shapes the final release
Influence the direction of the platform
To be considered for beta testing, mention your interest when contacting support or your Account Manager.
Public Roadmap
Intertwined doesn't currently publish a full public roadmap, but key upcoming releases are typically discussed in:
Live training webinars
Account Manager check-ins (Plus/Pro/District)
Product announcement emails
The "Stronger Together" and similar promotional initiatives
If you have a specific question about whether a feature is planned, ask support or your Account Manager directly.
Recognition
Teachers who contribute particularly valuable feedback are often recognized in:
Webinar shout-outs
Case studies and success stories
Beta tester credits in release notes
Speaking opportunities at education conferences
If you're passionate about contributing, let us know — we love working closely with engaged teachers.
Related articles:
12.1 Getting Help
12.2 Requesting a Live Training Webinar
12.4 Talking to Your Dedicated Account Manager