Frequently Asked Questions

First Prev show 14 of 231 Next Last

Offline or failed evidence can create disputes. Koovira needs the partner to keep the delivery status honest so support can resolve without false delivered or false failed attempts.
  1. Retry app/browser connection.
  2. Check camera permission.
  3. Ask receiver to retry secure link.
  4. Contact support if OTP is locked or expired.
  5. Use failed attempt only with correct reason.

Fake delivery attempts damage customer trust and merchant reputation. Koovira keeps delivery logs and evidence so repeated manipulation can be reviewed by support and padmin.
  1. Use the correct failed reason.
  2. Add clear notes if customer is unavailable.
  3. Do not mark failed without visiting the location.
  4. Respond to support verification if disputed.

Fake COD and high RTO damage merchant margins. Koovira is designed to make delivery attempts auditable, reduce blind dispatch decisions, and give merchants better context before accepting repeat-risk orders.
  1. Check buyer and order risk indicators.
  2. Use prepaid or protected payment where risk is high.
  3. Track failed attempts and NDR reasons.
  4. Escalate repeated fake delivery or fake COD patterns.

Courier delays and false delivery attempts often hurt the merchant even when the merchant shipped on time. Koovira separates commercial order status from courier execution logs and gives support/padmin an audit trail for escalation.
  1. Open shipment tracking from merchant delivery pages.
  2. Check AWB, webhook events, NDR, and delivery order status.
  3. Raise courier escalation if tracking and customer experience conflict.

Ecommerce may require owner unboxing and return evidence. Food and quick delivery need faster proof, delivery tracking, rider accountability, and issue reporting suitable to perishable orders. Courier and hyperlocal both feed the common evidence and status model.
  1. Select the correct delivery option for the order.
  2. Use hyperlocal for serviceable quick delivery.
  3. Use courier for regular or long-distance delivery.
  4. Follow module-specific issue rules.

Courier integration failure should not break the common delivery lifecycle. The shipment adapter can fail while the commercial order still needs transparent status, support notes, and customer/merchant communication.
  1. Verify courier vendor credentials and serviceability.
  2. Check courier_shipments status and response_json.
  3. Run or inspect tracking sync/webhook logs.
  4. Switch vendor or book manually where policy allows.
  5. Update delivery status with clear notes.

If hyperlocal and courier flows behave differently, customers and merchants get contradictory support answers. Koovira uses adapters for transport execution but keeps trust and evidence rules centralized.
  1. Treat logistics_orders as hyperlocal execution.
  2. Treat courier_shipments as courier execution.
  3. Use delivery_orders and order status history as common lifecycle records.
  4. Apply module-specific exceptions only where policy requires.

Koovira intentionally does not send a blind SMS OTP for protected delivery. OTP display depends on secure link status, receiver type, evidence requirements, rate limits, retry count, and expiry rules.
  1. Verify order status is out_for_delivery or reached_customer_location.
  2. Check order_delivery_links status and expiry.
  3. Check required evidence types.
  4. Check otp_gen_count, otp_locked_at, and wrong attempts.
  5. Regenerate or escalate only through approved support controls.

AI moderation is an assistive risk layer, not a blind final decision. It can flag tampering, missing product indicators, suspicious behavior, duplicate media, or inconsistent claims for human review.
  1. Check AI moderation log status.
  2. Review evidence manually.
  3. Check buyer, merchant, and courier history.
  4. Add support notes.
  5. Escalate before settlement or refund override.

Authorized receiver mode is designed for family members, office staff, security desks, receptionists, or assistants. It keeps order ownership with the actual customer and prevents someone else from opening the package, confirming product condition, or raising refund claims without owner review.
  1. Use Authorize Someone Else when courier reaches your location.
  2. Enter receiver name, mobile, and relationship.
  3. Share the generated receiver link.
  4. Receiver confirms sealed parcel and generates OTP.
  5. Order owner later completes unboxing.