How to Submit Feature Requests and Feedback

Taking a moment to think through your feedback makes it more likely to be addressed. Consider:

Is this a new feature request or an enhancement?

• Feature request: "Add the ability to grade assignments using AI-generated rubrics"

• Enhancement: "Make the grading feedback template include a space for positive feedback first"

Is your request feasible?

• ✅ Good: "Allow students to save drafts of their prompts before submitting"

• ❌ Less helpful: "Make http://boisestate.ai understand exactly what I'm thinking"

Is it specific enough?

• ✅ Specific: "Add a 'Copy to clipboard' button for AI responses so I can paste them into other documents"

• ❌ Vague: "Make it easier to share responses"

Does it solve a real problem?

• ✅ Problem-focused: "When I grade 30 essays, I have to type the same feedback repeatedly. A template system would save time."

• ❌ Opinion-based: "The interface should be different"

Have others asked for this too?

• If yes, mention it: "Multiple faculty have asked about batch processing"

• If you're the only one, that's fine too—state it clearly

Here are examples of well-written requests that are likely to be taken seriously:

Example 1: Feature Request (with problem context)

Example 2: Enhancement Request (with use case)

Example 3: General Feedback (with suggestion)

Step-by-step process:

1. Log in to http://boisestate.ai

   • Go to https://boisestate.ai

   • Sign in with your Boise State credentials

2. Locate your profile menu in the top-right corner

   • Look for your initial (first letter of your name)

   • This appears as a small circle or box in the upper right

   • Click/tap on it to open the dropdown menu

3. Select "Feature Request" from the dropdown

   • You should see options including "Settings," "Feedback," etc.

   • Look for "Feature Request" or "Send Feedback"

   • Click on it to open the feedback form

4. The feedback form will open

   • You'll see fields for different types of input

   • The form is submitted to OIT (Office of Information Technology)

   • Staff responsible for http://boisestate.ai review all submissions

5. Fill out the form completely:

   a) Select a Category

   • Choose one:

     • Feature Request: You're requesting brand new functionality that doesn't currently exist

     • Enhancement: You're suggesting an improvement to existing functionality

   • If unsure, make your best guess and explain clearly in the comments

   b) Add a Clear Title

   • Examples:

     • "Add ability to schedule prompts for later processing"

     • "Improve search functionality in chat history"

     • "Allow exporting conversations as PDF"

   • Be specific (not "Make it better")

   c) Describe Your Request

   • Explain the problem you're trying to solve

   • Describe what you'd like to see

   • Include how this would help you or your work

   • Mention if other people have asked for this too

   d) Provide Context (optional but helpful)

   • How frequently would you use this feature?

   • How would it improve your workflow?

   • Are there similar features in other tools?

   • What's the impact if this isn't implemented?

6. Submit the form

   • Click/tap Submit or Send

   • You should see a confirmation message

   • A ticket will be created for review

7. What happens next?

   • Your request is added to the feedback queue

   • OIT staff will review your submission

   • You may or may not receive direct feedback

   • Requests are prioritized based on demand, feasibility, and alignment with institutional goals

   • Popular or critical features are prioritized

DO:

• ✅ Be specific. Instead of "Make it faster," describe the exact slowdown: "Searching 500 conversations takes 5+ minutes; I'd like it under 10 seconds"

• ✅ Include context. Explain why you need this feature and how it would help

• ✅ Focus on the problem, not the solution. Rather than "Add a button here," say "I need a faster way to export conversations"

• ✅ Provide examples. Show how other tools solve this problem, or show what you're trying to accomplish

• ✅ Be realistic. Request features that are technically feasible and aligned with the tool's purpose

• ✅ Mention impact. How many people need this? How often would you use it? How much time would it save?

• ✅ Be respectful and professional. Frame feedback constructively

DON'T:

• ❌ Be vague. "The interface is confusing" doesn't help. "The conversation history sidebar is hard to navigate because there's no search" is better.

• ❌ Demand or complain. Feedback is more likely to be acted upon when it's collaborative in tone

• ❌ Submit duplicate requests. Check if someone already requested something similar before submitting

• ❌ Include multiple unrelated requests. Submit separate requests for different ideas

• ❌ Request features outside http://boisestate.ai 's scope. (e.g., "Integrate with every possible platform" isn't realistic)

• ❌ Include sensitive information. Don't paste student data, SSNs, or confidential content

Example of a strong feedback comment:

"I frequently use http://boisestate.ai to grade student writing (about 50 submissions per week). Right now, I copy feedback from http://boisestate.ai and manually paste it into Canvas comments one by one, which takes about 3 hours per week. If there were a way to export multiple responses as a CSV or directly integrate with Canvas, I could reduce that time to 15 minutes. I know other faculty who would benefit from this too."

We welcome all kinds of feedback. Here are categories we actively review:

Performance & Speed

• "Loading conversations takes too long"

• "Search across chat history is slow"

• "API requests frequently timeout"

Usability & Interface

• "I can't find the settings menu"

• "The feedback form is confusing"

• "A dark mode would reduce eye strain"

Workflow & Efficiency

• "I repeat the same prompt 50 times; a template system would help"

• "I need to export conversations for record-keeping"

• "Batch processing would save me hours per week"

Integration & Compatibility

• "Integration with Canvas gradebook would streamline grading"

• "API support for [specific use case] would enable automation"

• "Support for [file format] would improve data analysis"

Accessibility & Inclusion

• "The text is too small for accessibility"

• "Screen reader support doesn't work well with the conversation interface"

• "Keyboard navigation would help users who can't use a mouse"

Academic Integrity & Policy

• "We need better ways to mark AI-generated content"

• "Documentation about proper attribution would be helpful"

• "Integration with plagiarism detection would support academic integrity"

Documentation & Support

• "The help article about [topic] is confusing"

• "I'd like a video tutorial for [feature]"

• "A quick reference guide would be useful"

General Praise

• Yes, positive feedback is welcome too!

• Tell us what's working well

• Share success stories

Misconception 1: "My feature request will definitely be implemented"

Reality: All requests are reviewed and prioritized, but not all are implemented. Decisions are based on:

• Demand (how many people want it?)

• Feasibility (how hard is it to build?)

• Alignment with institutional goals

• Available resources and timeline

Misconception 2: "I need to submit this multiple times to get attention"

Reality: Submitting duplicates doesn't help. Instead:

• Submit once with full context

• Mention if other people have requested this

• Describe the impact clearly

Misconception 3: "Feedback is only for bugs"

Reality: We welcome all kinds of feedback:

• Feature requests and enhancements

• User experience suggestions

• Documentation improvements

• General praise and success stories

Misconception 4: "I'll get a response to my feedback"

Reality: While some requests receive follow-up, OIT may not respond to every submission. Your request is still reviewed and considered.

Misconception 5: "My feature will be built this week"

Reality: Feature development takes time:

• Requests are reviewed and prioritized

• Development must be scheduled

• Testing and deployment take time

• Check the http://boisestate.ai roadmap (if available) for timelines

Q: How long does it take for my request to be reviewed?

A: Requests are reviewed on an ongoing basis. You may not receive direct notification, but your feedback is logged and considered during planning meetings. Check back periodically for updates.

Q: Can I see the status of my feature request?

A: The feedback system doesn't currently provide tracking numbers or status updates. If you want to follow up, contact LTS@boisestate.edu with details of your request.

Q: What's the difference between a feature request and an enhancement?

A:

• Feature request: Completely new functionality (e.g., "Add a calendar integration")

• Enhancement: Improvement to existing features (e.g., "Make search faster")

If unsure, make your best guess and describe your idea clearly.

Q: Can I submit feedback about the feedback form itself?

A: Yes! If you find the feedback form confusing or have suggestions for it, mention that in your submission or email LTS@boisestate.edu.

Q: Should I contact IT directly instead of using this form?

A: Use the form for feature requests and enhancements. For technical issues, bugs, or urgent problems, contact the IT Help Desk directly.

Q: Can I request features for other Boise State tools?

A: This process is specifically for http://boisestate.ai . For other tools, contact the respective department or support team.

Q: What if I have a feature request but I'm not sure it's feasible?

A: Submit it anyway! Let OIT staff decide on feasibility. Include what you're trying to accomplish and why you think it would help. They'll evaluate it.

Q: Can I request a feature that would only benefit me personally?

A: Yes, but requests that benefit multiple users or solve common problems are prioritized. Explain your use case clearly so the team can evaluate the broader impact.

Q: Is there a roadmap showing planned features?

A: Check the Teaching & Learning Tools Confluence page for any public roadmap. If not visible, contact LTS@boisestate.edu to ask about upcoming features.

Q: How many people need to request a feature for it to be considered?

A: There's no magic number. Even requests from a single person are reviewed. However, if multiple people request the same thing, it's more likely to be prioritized.

Q: Can I suggest improvements to http://boisestate.ai 's documentation?

A: Absolutely! Use the same feedback form. Select "Enhancement" and describe what documentation would be helpful or what's confusing about current docs.

This guide is for feature requests and feedback. If you have a technical problem, use a different process:

Direct Link to Contact the Boise State Help Desk.

Understanding the process helps set realistic expectations.

Step 1: Submission (You do this)

• You fill out the form and submit

• You receive a confirmation (usually immediate)

Step 2: Review (OIT staff)

• Your feedback enters a queue

• OIT staff review submissions regularly

• Requests are categorized and assessed for feasibility, demand, and alignment

Step 3: Prioritization (OIT leadership)

• High-impact, frequently-requested items are prioritized

• Quick wins (easy to implement) may move faster

• Major features requiring significant development are scheduled

Step 4: Development (Engineering team)

• Approved features are added to the development roadmap

• Timeline depends on complexity and resources

• Quality assurance and testing occur before release

Step 5: Release

• Features are deployed to all users

• Announcements are sent (if you subscribed to updates)

• Documentation is created

Key point: Even if your feature doesn't get implemented, your feedback informs product strategy and demonstrates user needs.

If many people want the same feature:

Rather than everyone submitting identical requests:

1. Designate one person to submit the request with full context

2. In the request, mention: "Multiple faculty have requested this" (or include specific numbers)

3. Provide examples: Show how different people would benefit

4. Share the feedback link with colleagues so they know a request is already in

5. Encourage them to contact OIT if they want to add details or use cases

This approach:

• ✅ Shows strong demand (multiple people care)

• ✅ Provides diverse perspectives

• ✅ Prevents duplicate submissions

• ✅ Demonstrates institutional priority

Example in request: "I submitted this on behalf of our department's biology faculty (8 instructors). We all need batch processing for grading. Here are specific use cases from different classes: [list examples]"