RECYNEX GO
Make every return easy to understand.
Plan the participant journey around eligible packaging, physical return confirmation and programme rules, whether it connects to an existing app or RECYNEX Go.
Make the return journey clear
Guide a participant from packaging instructions to a recorded handover.
Show what belongs
Match on-screen instructions to the approved packaging list.
Separate recognition from receipt
Use a verified physical event for downstream records.
Connect the right program
Scope the interface to an existing app or a new branded journey.
PARTICIPANT JOURNEY
Connect clear instructions to a confirmed return.
The participant interface should reflect the real equipment and packaging rules at the site.
Before the return
Show eligible packaging and the location of the intake.
During the return
Explain rejection and uncertainty without guessing at success.
After acceptance
Use the verified equipment event for records or a separately scoped incentive.
THE EXPERIENCE LAYER
Define the rules before the interface.
Eligible packaging
Show an accurate project-approved list and an understandable rejection path.
Confirmed events
Use equipment-verified acceptance events for any downstream record or incentive.
Program connection
Connect an existing app or define a new branded journey with clear identity and data responsibilities.
A clear return experience begins with the packaging rule. People need to know what can be returned, where to place it and what a successful handover means. RECYNEX Go describes the participant-facing layer of a project; its exact screens, identity flow and rewards are defined with the operator.
Participation without ambiguity
Recognition, mechanical acceptance and reward eligibility are separate decisions. The user journey must acknowledge the verified equipment event, support understandable exceptions and avoid suggesting an incentive was earned before the transaction is confirmed.
Work with an existing ecosystem
Many programmes already have a loyalty app or member portal. RECYNEX Connect can define the event boundary and let the existing system remain the participant home. Where a new journey is needed, we scope the interface, accessibility, language, consent and support flows as part of the implementation.
Decide what the participant needs to know
At a site, the most useful information is the accepted-container list, location, step-by-step instruction and truthful outcome of a return. A brand programme may also need identity, campaign eligibility and a reward status. Those features require programme rules and a verified event source; they should not be assumed from the cabinet alone. Share your existing app screens or proposed journey when you discuss a participant interface.
Turn your site brief into a configuration
Share the location, container stream, operating team and systems already in place.