Frequently Asked Questions
Do not pay again immediately. Wait a few minutes, check Koovira Credits transactions, save the UPI reference id, and raise a billing support ticket if status does not update.
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
Invoices depend on the module, seller/merchant setup and payment flow. Check orders, Koovira Credits transactions or booking invoice pages and raise a billing ticket if missing.
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
Keep order/booking id, Credit Transaction id or top-up reference, chat messages, photos/videos, invoice, delivery proof, cancellation reason and timeline.
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
The file may be too large, unsupported, blurred or blocked by network/browser permission. Try JPG/PNG/PDF where allowed and avoid uploading private details unnecessarily.
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
Residents create complaints, society admin/staff assigns or updates them, and support can review status, updates and escalation if the society team does not respond.
Details: Complaint handling should preserve complaint id, unit, category, status, update history and any photos/documents. Platform support should not close a society complaint without society/admin context unless there is a platform-level issue.
Wait for the page to load, avoid pressing submit multiple times, switch to a stronger network, and retry after refreshing only if no payment or booking action is processing.
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
Pending usually means the request is waiting for KYC, approval, merchant acceptance, payment verification, assignment, stock/availability confirmation, or support review.
Steps: identify reference id → check latest status → check required documents → check payment or Koovira Credits → escalate if sla breached
Use report option or support ticket with post/profile link, screenshot, reason and any safety concern.
Details: Moderation should review content, author history, report reason, AI moderation logs where available and policy category before removing/restricting content.