AssureShift.in · Mover Portal v2 · support

Support — refunds you raise · complaints against you

Two different things, one hub. Refunds are the mover's own dispute — raised from a purchased lead in My Leads. Complaints are filed by the moving customer against the mover (today via customer care → logged by staff); the mover sees them here read-only, to know their standing. Movers don't raise or reply to complaints.

Complaints — against you · read-only

AssureShift · Leads
₹4,250
Support
ℹ️
Complaints are raised by the moving customer and handled by AssureShift. You can see them here to know your standing — you can't edit or reply.
Lead quality
Pune → Mumbai · logged 3 Jul
Open

Customer reported: "The team arrived 4 hours late and two cartons were damaged. No prior intimation."

🎧 AssureShift is reviewingReviewing

A resolved complaint (read-only detail)

AssureShift · Leads
₹4,250
Delayed service
Pune → Nashik · logged 28 Jun
Resolved
Customer's complaint

"Truck reached a day later than promised."

AssureShift resolution
Spoke to both sides — delay was due to a customer address change on the move day. No action against the mover. Marked resolved.
Resolutions are written by AssureShift staff. Repeated upheld complaints can affect a mover's priority and standing (staff-managed).
Two directions, don't conflate

Refunds are the mover's; complaints are the customer's

Corrected model:

  • Refund = mover → AssureShift, about a lead they bought ("bad/junk lead, credit me back"). Mover raises + tracks it. Backed by Refunds + the P5 disputes console.
  • Complaint = moving customer → about a mover, about a lead. Today logged by staff (customer calls care). Mover sees it read-only (status + the staff resolution). Backed by Complaints (read widened to the owning company).

Customer-raised complaints (self-service) arrive with the future customer login/portal — out of scope here.

Throwaway mock · mockup.csoul.cloud/as-leads-portal-v2/support.html · noindex