Use the secure in-app path for delivery and account concerns. This page explains where to start and what SWYFT will never ask you to disclose.
Verified legal operator · In-app support active · Public support channel pending
01
Active delivery help
Open the active delivery in the Customer or Driver app and use its Support action. Keep the booking reference available. Do not post the recipient’s phone number, exact address, proof photo or payment reference on public channels.
02
Payment status
Trust only the verified status inside SWYFT. A GCash browser success page is not proof that a booking is paid. Never repeat a payment while verification is pending, and never share a PIN, OTP, password or full payment credential with a driver or support representative.
03
Account access
Use the app’s password-recovery flow for a lost password. Do not create another account to bypass an unresolved security review. Email-change and password-change security alerts are enabled for the controlled pilot.
04
Safety or emergency
For an immediate threat, accident, fire, medical emergency or crime in progress, contact the appropriate local emergency service first. SWYFT support is not an emergency-response service. After reaching safety, preserve the booking reference and relevant evidence for authorized review.
05
Verified support channel
The controlled pilot is operated by SWYFT NEXUS AI Technologies OPC. Pilot participants currently use authenticated in-app support. A permanent public support email and accountable contact have not yet been approved, so SWYFT will not publish an unmonitored address. The external rights-request gate remains locked until that channel is verified and monitored.