PaulRentACar Docs
Compliance

Complaint Management

Full complaint lifecycle from creation through resolution, including assignment, escalation, legal escalation, SLA tracking, and ownership history.

Overview

Complaint management is a critical compliance and customer satisfaction function. Every customer complaint — whether about vehicle condition, billing, service, or safety — must be tracked through a structured lifecycle with clear ownership, SLA deadlines, and audit trails. Complaints that involve legal risk are escalated to the Legal module with a full record lock.

Complaint List


Complaint Statuses

Every complaint moves through these statuses. No status can be skipped — each transition is logged with a timestamp, actor, and optional note.

StatusMeaningWho Sets It
openComplaint received, not yet assignedSystem (on creation)
assignedAssigned to a staff member or departmentBranch manager / Complaint coordinator
in_progressStaff actively investigating or resolvingAssigned staff
waiting_customerAwaiting customer response or informationAssigned staff
waiting_internal_departmentTransferred to another department (e.g., billing, fleet)Assigned staff
escalatedEscalated to management due to SLA breach or severitySystem (auto) or manager
legally_escalatedLegal risk identified — transferred to Legal moduleCompliance officer or Legal
resolvedResolution communicated and accepted by customerAssigned staff
closedComplaint finalized, no further action neededSystem (after resolution + grace period)

Complaint Creation

Complaints can be created from multiple channels:

ChannelHow It's Created
Customer portalCustomer submits form with category, description, and attachments
Phone callBranch staff creates complaint on behalf of customer
EmailSystem parses email into complaint ticket
Walk-inBranch staff creates complaint in person
Social mediaCustomer service team logs as complaint
InternalStaff member reports an issue proactively

Create Complaint

Required Fields at Creation

FieldRequiredNotes
Customer name and contactYesAuto-populated if customer exists in system
CategoryYesBilling, Vehicle, Service, Safety, Other
SubcategoryYesDepends on category (see below)
DescriptionYesMinimum 20 characters
Related reservation/contractNoLinks complaint to specific booking
Related vehicleNoLinks complaint to specific vehicle
AttachmentsNoPhotos, documents, screenshots
PriorityAuto-assignedBased on category and severity rules

Category and Subcategory Matrix

CategorySubcategories
BillingOvercharge, refund delay, incorrect invoice, payment failure, deposit not returned
VehicleBreakdown, cleanliness, damage not at checkout, feature not working, wrong vehicle
ServiceStaff behavior, long wait time, rude communication, unfulfilled promise
SafetyAccident, mechanical failure, insurance dispute, missing safety equipment
OtherGeneral feedback, suggestion, unresolved previous complaint

Complaint Assignment

Assignment Rules

RuleDetail
Auto-assignmentSystem assigns based on category → department mapping
Manual overrideBranch manager can reassign at any time
ReassignmentAny assignment change is logged with reason
Ownership historyEvery assignment change creates an ownership history record

Department Mapping

CategoryDefault Department
BillingFinance / Billing Team
VehicleFleet / Operations
ServiceCustomer Service
SafetyCompliance + Operations Director
OtherCustomer Service

Complaint Transfer

To transfer a complaint to another department:

  1. Open the complaint.
  2. Click Transfer.
  3. Select the target department.
  4. Enter a transfer reason (required).
  5. The complaint status changes to waiting_internal_department.
  6. The target department receives a notification.

Rule: A complaint can be transferred a maximum of 3 times. After that, it must be escalated to management.


Escalation

Automatic Escalation

The system automatically escalates complaints when:

ConditionAction
SLA warning breached (24 hours)Status changes to escalated, branch manager notified
SLA breach (48 hours)Status changes to escalated, operations director notified
Customer requests escalationStatus changes to escalated
Complaint involves safetyImmediate escalation to compliance officer

Manual Escalation

Branch staff can manually escalate by:

  1. Opening the complaint.
  2. Clicking Escalate.
  3. Selecting an escalation level (Team Lead, Branch Manager, Operations Director).
  4. Entering a reason.

When a complaint involves legal risk — such as personal injury, property damage claims, fraud allegations, or regulatory violations — it must be escalated to the Legal module.

TriggerExample
Personal injury claimCustomer or third party injured in rental vehicle
Property damage claimDamage to third-party property
Fraud allegationStolen identity, fake documents
Regulatory complaintGovernment agency, police report
Insurance disputeClaim denied, coverage disagreement
Customer threatens legal actionExplicit mention of lawyer or lawsuit
  1. Staff identifies legal trigger during complaint handling.
  2. Staff clicks Escalate to Legal.
  3. System prompts for escalation summary and supporting documents.
  4. Complaint status changes to legally_escalated.
  5. Record lock is applied — the complaint can no longer be edited by branch staff.
  6. Legal team receives notification and opens a Legal Case linked to this complaint.
  7. All further communication on this complaint goes through the Legal module.

Critical: Once a complaint is legally escalated, branch staff cannot modify, resolve, or close it. Only the Legal team has write access.


Resolution and Closure

Resolution

  1. Assigned staff clicks Resolve.
  2. Enters the resolution description (required).
  3. Selects resolution type:
    • Full refund
    • Partial refund
    • Credit note
    • Apology only
    • Vehicle replacement
    • Service recovery (complimentary upgrade, etc.)
    • No action required
  4. Customer is notified of the resolution.
  5. Customer has 72 hours to accept or dispute.

Closure

If the customer accepts (or does not respond within 72 hours):

  1. Complaint status changes to closed.
  2. Customer satisfaction survey is sent.
  3. Final audit log entry is created.
  4. Complaint data is retained per data retention policy.

If the customer disputes:

  1. Complaint status reverts to in_progress.
  2. Re-investigation begins.
  3. Maximum 2 dispute cycles allowed — after that, escalate to management.

Notes and Attachments

FeatureDetail
Internal notesStaff-only comments, not visible to customer
Customer-facing notesShared with customer via portal
AttachmentsPhotos, documents, audio recordings — max 10MB per file
Maximum attachments20 per complaint
File typesJPG, PNG, PDF, DOCX, MP3, MP4
ImmutabilityUploaded files cannot be deleted, only archived

SLA Tracking

SLA LevelWarningBreachEscalation Target
Standard complaint24 hours48 hoursBranch Manager
Billing complaint12 hours24 hoursFinance Lead
Safety complaint4 hours8 hoursCompliance Officer
VIP customer complaint8 hours16 hoursOperations Director
Repeat customer (3+ complaints)8 hours16 hoursBranch Manager

Ownership History

Every complaint maintains a complete ownership history:

FieldCaptured
Staff memberWho held the complaint
DepartmentWhich department
From / To timestampsWhen ownership started and ended
ReasonWhy the transfer occurred
Action takenWhat was done during that ownership period

This history is immutable and available for audit, quality review, and legal proceedings.


Callouts

Legal escalation locks the complaint record. This is a hard rule — no exceptions. The Legal team must manage legally escalated complaints through the Legal module.

Complaint data retention: All complaint records, including notes, attachments, and ownership history, are retained for 7 years from the date of closure, regardless of customer account status.

On this page