Resolving a Discrepancy

Modified on Wed, 25 Sep, 2024 at 4:38 PM

In This Article

In this article, you will find comprehensive instructions on how to resolve a discrepancy.


What You Will Learn

1. Review Discrepancy Details 

2. Edit Ticket Information & Submit Resolution 


Who does this impact?

  • Generator operators


This article is step two (2) in the three step process of 'Managing a Discrepancy'. For support on how to complete the other two (2) steps, see below links to the support articles here:


1. Receiver Submits a Discrepancy

2. Generator Resolves the Discrepancy

3. Receiver Approves the Resolution


Instructions


1. Access the Ticket & Review Discrepancy Details

  • From the main page, navigate to the Load Verification bucket.
  • Select the ticket in Discrepancy status.
  • This will open up the ticket in a side panel, click on 'Submit Resolution'.



2. Edit Ticket Information & Submit Resolution

  • After reviewing the discrepancy details, click 'Ticket Information' to make the necessary changes
  • Make the changes to the ticket. For example, reclassify the waste.
  • Click 'Submit Resolution' to send the updated ticket back to the receiver operator.
  • If the receiver agrees with your changes, they will approve the resolution and enter the offload details (volumes and cuts). 
  • The ticket will return to Awaiting Approval status. Check out 'Approving a Ticket' article for support on how to approve the final ticket.


Conclusion

Congratulations! You have successfully resolved a discrepancy.


Additional Support

Can’t find what you’re looking for? Send our Customer Success team a request for additional support: Call us 1.833.639.0947, Text us 1.587.817.0455, Email us support@wiqtech.com.


Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article