Browse help topics for your current access role: public
Check mobile network, DND/SMS blocking, correct country code, OTP resend limit and whether the same number is already registered. Wait before requesting again.
It can happen in payment, booking, ticket or posting flows. Check status first before retrying and contact support if duplicate records appear.
Pending means waiting for action or verification, approved means accepted, rejected means not accepted with reason, cancelled means stopped, and completed means...
Send the page showing the issue, order/booking/ticket id, date/time and error message. Hide OTP, password, full card/bank details and private documents unless s...
Use official Koovira support channels shown on the site. Avoid sharing OTP, password or UPI/payment PIN for Koovira Credits top-up on WhatsApp or phone.
Wait for the normal response window, send one clear message in Koovira, then raise a ticket with reference id if there is no response or money/safety is involve...
Invoices depend on the module, seller/merchant setup and payment flow. Check orders, Koovira Credits transactions or booking invoice pages and raise a billing t...
Cancellation depends on module policy, merchant acceptance, time window, preparation/dispatch state and refund rules. Check the status before cancelling.
Yes, use ratings/reviews or support ticket flows. Write factual details, avoid abuse, and attach proof when reporting fraud, safety or quality issues.
Some data can be edited or hidden from settings, while transaction, invoice, safety and legal records may need retention. Contact support for account/data reque...
Use their own mobile number, explain OTP safety, avoid saving payment details without consent, and keep support/ticket details available.
Availability depends on active users, merchants, providers, pincode coverage and local launch status. You may still create profile, search, post or request supp...
The pincode may be outside active coverage, entered incorrectly, or missing from serviceable location data. Try nearby city selection or raise support for cover...
High demand, traffic, limited providers, surge, stock, hotel/event availability or merchant workload can change price/time. Confirm final amount before payment.
In most text fields you can type normal Hindi/Hinglish/local language, but official names, addresses, KYC and payment details should be accurate and readable.
Age rules depend on the module. Dating, payments, contracts, jobs and legal bookings may require adult consent or age eligibility.
Keep order/booking id, Credit Transaction id or top-up reference, chat messages, photos/videos, invoice, delivery proof, cancellation reason and timeline.
Suggestions may use your selected city, interests, profile, past actions and module context. You can change filters or privacy/settings where available.
Check if you are logged in, refresh once, verify mobile/location/Koovira Credits/escrow status, take a screenshot, and raise a ticket with a simple explanation.
Still stuck?How can we help?
