Order help
Senders can submit help requests for sent orders. Travelers can submit help requests for any job or active order.
Help and support
Vahos includes help request flows for senders and travelers, notification support, AI chatbot guidance, and support service escalation.
Read-only information about how app support is represented in the current product.
Senders can submit help requests for sent orders. Travelers can submit help requests for any job or active order.
The AI chatbot can help with pricing, safety, and app usage questions.
The support service can escalate help requests by email when the issue needs follow-up. Contact support@vahos.app.
Support can relate to FCM registration, notification inbox, unread badge, and mark-as-read behavior.
Help topics include live location status, nearest station, ETA summaries, and larger route maps.
Pickup OTP and delivery OTP questions can be tied back to the order record and status.
Answers for the sender, traveler, and receiver experience. If an order needs attention, submit an in-app help request with its details.
Vahos supports senders who create parcel requests, travelers who carry eligible jobs, and receivers who are linked to an order through their phone number.
The service is designed around supported Mumbai local-train stations across the Western, Central, and Harbour lines, with eligible local doorstep pickup and drop options.
No. A receiver is identified by the phone number entered on an order. A logged-in user can see received orders when their account phone matches that receiver phone.
Senders and travelers sign in using a WhatsApp OTP and accept the Terms & Conditions and Privacy Policy before using the app.
Check that the phone number and country code are correct, confirm your WhatsApp connection, then try again. If the issue continues, use support from the app.
Vahos is for small parcels that comply with the Terms. Parcels must be safe to carry on public transport and must not contain prohibited, illegal, dangerous, perishable, high-value restricted, or flammable items.
The current sender flow limits package weight to 5 kg. The parcel should fit safely in a standard backpack or small handheld bag; the Terms list a maximum size of 45 cm × 35 cm × 20 cm.
Senders capture inner-item and sealed outer-package photos before handover. These form package evidence for the order and help document the parcel condition.
Select pickup and drop stations and platforms, enter the package and receiver details, upload package evidence, review the quote, and complete payment to place the request.
Eligible Local Doorstep orders can use Google address search plus building, unit, and contact details. Senders can save and reuse addresses for future orders.
Core rail pricing is calculated from the station distance between the selected pickup and drop. Doorstep service can also include first- and last-mile charges. The final quote is shown before payment.
Business accounts can provide business and GSTIN details for verification. Any configured business discount applies only after verification and only to eligible Local Doorstep deliveries; it is shown before payment.
A paid order is broadcast to eligible nearby travelers. The sender can follow the matching status and receives order updates as a traveler is assigned and the delivery progresses.
The app considers travelers near the pickup station, generally within about 2 km, and may also consider the sender location when it is available.
The order remains available for matching while eligible travelers are nearby. The app can refresh matching and supports rebroadcasting where available; use order help if you need assistance.
Cancellation is available through the order flow when permitted by its current delivery stage. The order shows its cancellation and refund status, including any applicable refund timing.
During active delivery, senders can view order status, route maps, and traveler live location when it is being shared. ETA alerts and status updates can also appear in notifications.
Once a traveler is assigned, the order can show their contact details for pickup or delivery coordination.
After a completed delivery, the sender can submit a rating and an optional comment from the order experience.
Choose the traveler role, complete the requested profile details, submit Aadhaar/DigiLocker KYC, provide payout information, and enable the required app permissions.
KYC helps create a more accountable marketplace. Travelers may see a verification warning or limited job access until their identity verification is completed.
Location is used to show jobs close to a traveler, support delivery tracking during an active job, and help senders see trip progress. It is not intended for inactive/offline tracking.
Travelers can open the jobs marketplace to review nearby available orders, their pickup distance, route, package details, and payout before accepting.
Yes. Eligible job cards show the traveler payout before acceptance, and the traveler area includes potential, earned, and wallet summaries.
The order moves to the traveler’s active transit experience. Follow the pickup and drop details, coordinate with the sender or receiver when necessary, and complete the required handovers.
The app’s active-work flow is designed around completing accepted delivery work responsibly. Review your active deliveries and availability before accepting another job.
Ask the sender for the pickup OTP and enter it in the active order. A successful verification moves the parcel into transit.
Coordinate the final handover with the receiver, collect the delivery OTP, and enter it in the active order. Successful verification completes the delivery and updates payout status.
Do not share or guess OTPs. Use the order’s Help action as soon as possible and include the delivery stage and issue details so support can review the order.
Traveler screens show in-progress, completed, and cancelled work alongside payout status. Completed jobs are reflected in the wallet/ledger according to the order’s payout state.
The sender enters the receiver’s phone number on the order. When it matches a logged-in account, received orders and relevant delivery notifications can be shown.
The sender completes the order payment. The receiver’s role is to coordinate final handover and provide the delivery OTP when requested.
The order’s delivery OTP is part of the sender/receiver handover flow. The receiver should share it only with the traveler at the final delivery point.
Travelers can call the receiver for final-handover coordination. Contact details are shared only as needed to complete the delivery.
The traveler should not mark delivery complete without the delivery OTP. The sender, receiver, or traveler should raise an order help request with the current situation.
They are separate one-time codes for the two controlled handovers: pickup OTP confirms collection from the sender, while delivery OTP confirms final handover to the receiver.
No. Only share the relevant OTP when the traveler is present and the handover is ready to be confirmed. Never share an OTP in response to an unsolicited message or call.
Location appears only when the traveler has an active trip, has granted the required permissions, and a recent GPS update is available. Check the order again shortly or use Help if it remains unavailable.
Confirm that device notifications are allowed for Vahos and that the app has completed notification registration. You can still check the in-app notification inbox for updates.
Senders and travelers can share their referral code. Rewards are credited only when the invitee completes the qualifying action—for example, a sender’s first paid completed order or a verified traveler’s first completed trip.
Open the order and choose Help. Select the issue type, add useful details such as the current stage and what happened, then submit the request. Support receives the relevant order context.
For delivery issues, use the in-app Help flow first. You can also contact support@vahos.app. Privacy and deletion requests are handled under the Privacy Policy.
Download the app to access order-aware support and updates.