# Feedback

Your feedback helps make <code class="expression">space.vars.productName</code> better. Whether you've found a problem, have an idea for improvement, or just want to share your experience, we want to hear from you.

***

## Reporting a Problem

If something isn't working correctly:

1. **Check the** [**Troubleshooting**](/end-user-guide/pos-overview/troubleshooting.md) **and** [**FAQ**](/end-user-guide/faq.md) **pages first.** The solution might already be documented.
2. If the issue persists, report it to your **manager** or **IT team** with the following details:
   * What you were trying to do.
   * What went wrong (include the error message if there was one).
   * When it happened (date and time).
   * Screenshots if possible.
   * Steps to reproduce the issue.

See [Getting Help](/end-user-guide/faq/getting-help.md) for more tips on writing a useful bug report.

### What Counts as a Problem?

* Buttons or features that don't work.
* Error messages appearing unexpectedly.
* Data that looks wrong (wrong prices, missing orders, incorrect totals).
* Pages that won't load or load very slowly.
* Things that worked before but suddenly stopped working.

***

## Suggesting a Feature or Improvement

Have an idea that would make your work easier? Great! Here's how to share it:

1. **Talk to your manager.** They can evaluate whether the suggestion aligns with business needs and pass it along to the right team.
2. **Be specific.** Instead of "make it better," try something like:
   * "It would be helpful if I could search orders by product name, not just order number."
   * "The font size on the POS screen is hard to read on our tablets — a larger option would help."
   * "It would save time if there was a 'Reorder' button on the order list page, not just the detail page."
3. **Explain the benefit.** Why would this change help? How often would you use it? What problem does it solve?

### Good Suggestion Examples

> "When I'm processing returns, I have to scroll through a long list of items to find the one being returned. It would be really helpful to have a search bar on the return screen."

> "I'd love a quick-action button on the dashboard for 'Start New Sale' — right now I have to click POS in the sidebar, which takes an extra step."

> "Could the system remember my last-used shipping method? I almost always choose Standard, and reselecting it every time adds up."

***

## Sharing Positive Feedback

If something works really well or you appreciate a recent improvement, share that too! Positive feedback:

* Helps the team know what's working and what to keep.
* Motivates the people building and maintaining the system.
* Can be as simple as telling your manager, "The new order history filters are really useful."

***

## Feedback Channels

Depending on your company's setup, you may have one or more of these options:

| Channel           | Best For                                                                                        |
| ----------------- | ----------------------------------------------------------------------------------------------- |
| **Your manager**  | General feedback, feature suggestions, business process improvements                            |
| **IT support**    | Technical issues, bugs, system errors                                                           |
| **Feedback form** | If your company provides a built-in feedback form, use it — submissions go directly to the team |
| **Team meetings** | Bring up suggestions during regular team check-ins                                              |
| **Email**         | Write to your designated support or feedback email address                                      |

> **Tip:** If you're not sure where to send feedback, start with your manager. They'll know the right channel.

***

## What Happens with Your Feedback

When you submit feedback:

1. **It's reviewed** by your company's administration or IT team.
2. **Problems** are investigated and prioritized based on severity and how many people are affected.
3. **Feature suggestions** are evaluated for feasibility and business value.
4. **Changes are made** in future updates. Your administrator may inform you when a change related to your feedback is released.

Not every suggestion can be implemented right away, and some may not be feasible. But every piece of feedback is valuable and helps shape the direction of the product.

***

## Thank You

Taking the time to share your feedback — whether it's a problem report, a suggestion, or a compliment — makes <code class="expression">space.vars.productName</code> better for everyone. We appreciate it.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.in8sync.com/end-user-guide/faq/feedback.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.