How to Submit Feedback or a Complaint

Feedback and complaints can be submitted from the Quick Actions panel available on almost every module's home dashboard — meaning you never need to navigate to a separate, hard-to-find app to raise an issue.

Complete step-by-step process:

1. On any module dashboard, locate the Quick Actions panel (typically on the right side, next to Quick Access Applications).
2. Choose the option that best matches your need:
   • Feedback — for general suggestions or comments about your experience with the portal or a specific process.
   • Complaint — for a specific operational issue, such as a vendor dispute, a delayed shipment, or a process failure.
   • Report Bug — for a technical or system issue, such as a page not loading correctly or incorrect data displaying.
   • Integration... — for requests related to connecting external systems or data sources to the portal.
3. Click the relevant icon to open its submission form.
4. Fill in the details as specifically as possible — include reference numbers (PR, PO, ASN, or Vendor Code) wherever relevant, since this dramatically speeds up investigation.
5. Attach any supporting evidence (screenshots, documents) if the form allows.
6. Submit — your entry is logged and automatically routed to the relevant internal team for review.

Choosing the right category — a practical guide:

• Use Feedback when you have a suggestion for improvement but nothing is actively broken or wrong.
• Use Complaint for issues involving a person, process, or vendor — for example, "Vendor X's shipment arrived three days late without prior notice."
• Use Report Bug strictly for technical glitches in the portal itself — for example, "The Submit button on the Create PR screen doesn't respond."

Why writing specific, detailed submissions matters: A complaint like "Order is a problem" gives the reviewing team almost nothing to act on. A complaint like "PO #100000455 from Vendor Ross Controls was quoted for 5-day delivery but has not arrived after 9 days, no update received" gives the team an immediate, actionable starting point.

A template you can reuse for high-quality complaint submissions: "[What happened] — [Reference number: PR/PO/ASN/Vendor Code] — [When it happened] — [What you expected instead] — [Any impact/urgency]. " Following this simple structure consistently produces complaints that are resolved faster than free-form, vague descriptions.

Frequently Asked Questions

Is there a difference in how urgently Feedback vs. Complaint items are handled? 

Yes, typically — Complaints, especially those involving active orders or vendor disputes, are generally prioritized for faster response than general Feedback suggestions.

Can external vendors also submit complaints, or is this internal-staff only? 

Both — the Quick Actions panel is generally available across roles, allowing vendors to raise issues about the portal or process just as internal staff can.

What happens if I submit the wrong category (e.g., a Complaint that should have been a Bug Report)? 

The reviewing team can typically re-route it internally, though submitting under the correct category from the start speeds up the right team seeing it first.

Can I attach a screenshot or document to a Complaint? 

Most feedback/complaint forms support attachments — check the specific form for an upload option, similar to other document-upload fields across the portal.

Will I be notified when my Feedback or Complaint is reviewed?

Updates are typically communicated back through the same Feedback & Complaints area or via your notification bell, depending on your organization's configuration.

Is it better to submit one detailed complaint or several smaller ones for related issues? 

One well-structured, detailed complaint covering the full context is generally more effective than multiple fragmented submissions about the same underlying issue, since it gives reviewers the complete picture in one place.