Refund timing depends on module policy, escrow/hold status and Koovira Credits ledger. Normal in-platform refunds are Koovira Credits reversals/credits. Bank/UPI/card reversal applies only when a KooviraCredit add-money top-up itself failed or needs gateway reversal.
Simple steps: Check login and correct mobile number -> Check selected city, pincode, filters and internet connection -> Do not repeat Koovira Credits/booking submit buttons blindly -> Take screenshot with reference id and date/time -> Raise support ticket if Koovira Credits, escrow, safety or stuck status is involved
Location permission, saved address, city/pincode filter, sparse local data or broad fallback search may be causing wider results.
Details: Update location, check filters, allow browser location if comfortable, and try a precise pincode/locality. Support should check if location/pincode data exists for that module.
It can happen in payment, booking, ticket or posting flows. Check status first before retrying and contact support if duplicate records appear.
Simple steps: Check login and correct mobile number -> Check selected city, pincode, filters and internet connection -> Do not repeat Koovira Credits/booking submit buttons blindly -> Take screenshot with reference id and date/time -> Raise support ticket if Koovira Credits, escrow, safety or stuck status is involved
Use the relevant Koovira entry page, complete any required login/KYC/setup step, then follow the module action such as posting, booking, ordering, messaging or managing records.
Steps: open entry → confirm login → complete required profile → perform primary action → check status
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 involved.
Simple steps: Check login and correct mobile number -> Check selected city, pincode, filters and internet connection -> Do not repeat Koovira Credits/booking submit buttons blindly -> Take screenshot with reference id and date/time -> Raise support ticket if Koovira Credits, escrow, safety or stuck status is involved
Yes, use ratings/reviews or support ticket flows. Write factual details, avoid abuse, and attach proof when reporting fraud, safety or quality issues.
Simple steps: Check login and correct mobile number -> Check selected city, pincode, filters and internet connection -> Do not repeat Koovira Credits/booking submit buttons blindly -> Take screenshot with reference id and date/time -> Raise support ticket if Koovira Credits, escrow, safety or stuck status is involved
Take clear photos immediately, keep bill/order id and raise complaint from the order page or support.
Simple steps: Do not panic or repeat risky action -> Save proof and reference id -> Use official Koovira support or module page -> Wait for normal SLA if applicable -> Escalate if money, safety or fraud is involved
Use the relevant Koovira entry page, complete any required login/KYC/setup step, then follow the module action such as posting, booking, ordering, messaging or managing records.
Steps: open entry → confirm login → complete required profile → perform primary action → check status
Yes, use ratings/reviews or support ticket flows. Write factual details, avoid abuse, and attach proof when reporting fraud, safety or quality issues.
Simple steps: Check login and correct mobile number -> Check selected city, pincode, filters and internet connection -> Do not repeat Koovira Credits/booking submit buttons blindly -> Take screenshot with reference id and date/time -> Raise support ticket if Koovira Credits, escrow, safety or stuck status is involved
Use Hotels/StayGo to search stays, check offers, book rooms, manage invoices and contact property support.
Details: Hotels and StayGo is part of Koovira's multi-module ecosystem. The usual flow is: user opens the module, searches or creates a request, checks trust/profile details, communicates inside Koovira, completes Koovira Credits/booking/posting where required, tracks status, and raises support with reference id if something goes wrong.