Customer Complaint Intake for General Contracting
Customer Complaint Intake is the structured process for handling any negative feedback, concerns, or complaints from clients that are broader than specific warranty defects. It covers how complaints are received, documented, categorized, and routed for follow-up in a consistent, professional way. The process distinguishes between routine concerns and serious issues that may affect safety, reputation, or legal risk. When followed, it ensures that complaints are heard, tracked, and addressed systematically instead of informally or inconsistently.
Define complaint types and intake criteria
Step 1: List typical complaint scenarios
Brainstorm with project managers, customer service, and field staff to list common complaint scenarios (for example, dissatisfaction with communication, perceived schedule delays, quality concerns outside warranty, billing disputes, behavior of personnel). Write these down in simple terms.
Step 2: Group complaints into logical types
Organize scenarios into a small set of complaint types such as “Communication,” “Schedule,” “Quality,” “Cleanliness,” “Billing/Financial,” and “Conduct/Professionalism.” These types will be used later for categorization and reporting.
Step 3: Define what must be logged as a complaint
Decide and document which situations must always be logged (for example, any written complaint, any request to “speak to a manager,” repeated dissatisfaction, or threats of legal action or bad reviews). Make these requirements explicit.
Step 4: Clarify what can be handled as informal feedback
Identify minor, one-time comments that can be handled informally (for example, a single remark about muddy boots that is corrected immediately) and document examples so staff can distinguish these from true complaints.
Step 5: Document criteria in a short reference guide
Create a one-page reference that describes complaint types and gives examples of what must be logged. Use clear language and real-world examples rather than abstract definitions.
Step 6: Train customer-facing staff on complaint definitions
Review the guide with office staff, project managers, and superintendents so everyone understands when and how to treat feedback as a formal complaint.
Receive and acknowledge complaints across all channels
Step 1: Identify main complaint channels
List all ways complaints may arrive: dedicated client service email, main phone line, project manager’s phone, superintendent on site, website forms, social media, and in-person conversations at meetings or walkthroughs.
Step 2: Route complaints to a central point
Establish a rule that any complaint received by any staff member must be forwarded to a designated complaint intake inbox or person, even if that staff member also helps address the issue. Communicate the inbox or person clearly to all staff.
Step 3: Use a standard acknowledgement script
Prepare a short script for verbal and written acknowledgment, such as “Thank you for bringing this to our attention. I’m going to document your concerns so we can review and respond properly.” Train staff to use this wording or something very close.
Step 4: Capture basic contact and project details immediately
As soon as a complaint is recognized, record the client’s name, project address, phone/email, and how they contacted you. Even if you do not have time for full intake, capture these basics so nothing is lost.
Step 5: Avoid arguing or defending in the moment
Coach staff to listen, acknowledge, and gather information without arguing or pushing back. The goal at this stage is to understand and document, not to win a debate.
Step 6: Inform the client of next steps in simple terms
Tell the client that there is a defined process to review complaints and that someone will follow up after the concern is documented and routed, giving a reasonable timeframe for that first follow-up (for example, “within one business day”).
Collect detailed client and project information
Step 1: Open the standard complaint intake form
Use a pre-built intake form (paper or digital) that prompts you for all required fields such as client name, project name, job number, address, and primary contacts.
Step 2: Confirm spelling of names and contact info
Ask the client to spell their name and email address, and repeat phone numbers back to them. This avoids errors that can block future communication.
Step 3: Capture project identifiers
Ask for any job numbers, lot numbers, or project names they have from contracts or previous emails. If the client does not know, note that and plan to look it up later using address and client name.
Step 4: Record preferred contact method and best times
Ask whether they prefer phone, email, or text for future communication about this complaint, and note the times of day when they are easiest to reach. Enter this into the intake form.
Step 5: Note any decision-makers or other stakeholders
Ask whether anyone else should be copied on future communications (for example, spouse, property manager, or business partner) and record their names and roles.
Step 6: Link to existing records in your systems
Once the call or meeting is over, match the collected info to an existing project in your project management or accounting system and note the project reference in the complaint form.
Capture complaint details, impact, and desired outcome
Step 1: Ask the client to describe their concern in their own words
Invite the client to explain what they are unhappy about without interruption. Let them finish before asking clarifying questions, and take notes using their language as much as practical.
Step 2: Clarify specific events, dates, and people involved
Ask targeted follow-up questions: when did this start, how many times has it happened, and who from your company was involved. Record dates, names, and any key milestones (for example, “missed inspection on May 12”).
Step 3: Identify how the issue impacts the client
Ask how the situation is affecting them (for example, “We can’t use our kitchen,” “We feel we are not being told the truth,” “Our business operations are disrupted”). Note both practical and emotional impacts.
Step 4: Ask what resolution the client is seeking
In plain language, ask, “What would you consider a fair resolution?” or “What would you like to see happen next?” Record their answer without committing to it yet.
Step 5: Separate facts from feelings in your notes
In your written summary, clearly distinguish factual events from emotions or opinions (for example, “Client states we missed two scheduled meetings,” versus “Client feels ignored.”). Both matter, but they serve different purposes.
Step 6: Summarize back to confirm accuracy
Read back a brief summary of the concern, impact, and desired outcome, and ask if you captured it correctly. Make corrections based on the client’s feedback.
Assess complaint severity, risk, and urgency
Step 1: Define severity levels and risk factors
Work with leadership to define clear severity levels (for example, Low, Medium, High, Critical) and the risk factors for each (safety hazards, legal threat, risk of public reviews or media, project stoppage). Document these in a simple reference.
Step 2: Review complaint facts against severity criteria
Look at what the client reported and compare against your severity definitions. Check for triggers such as “threatened to sue,” “mentioned contacting media,” “work stopped,” or “safety hazard.”
Step 3: Consider project status and stakeholder visibility
Note whether the issue occurs on an active job or completed project, and whether key stakeholders (for example, developers, architects, corporate tenants) are paying close attention. This can raise the practical urgency of handling the complaint.
Step 4: Assess client tone and escalation potential
Consider the client’s tone and history: are they calm and patient, or visibly angry and mistrustful? Have they escalated before? This does not change the facts, but it affects how quickly you need to respond to avoid further escalation.
Step 5: Assign a preliminary severity and urgency level
Based on criteria and judgment, assign a severity level and note any deadline for initial response (for example, “respond same day,” “respond within 2 business days”). Record this in the complaint form.
Step 6: Flag high-risk complaints for immediate review
If a complaint meets High or Critical criteria, immediately notify the appropriate manager or leadership as per company policy, regardless of normal intake timelines.
Review related project, warranty, and communication history
Step 1: Open the project record in your systems
Using the project identifier from intake, open the job in your project management, CRM, or accounting system. Make sure you have permission to view all relevant information.
Step 2: Review contract, scope, and key milestones
Skim the contract summary, original scope of work, major change orders, and schedule milestones. Note any significant delays, scope disputes, or cost changes that might relate to the complaint.
Step 3: Scan prior communication logs and emails
Look for previous emails, call logs, or meeting minutes involving this client, especially around the timeline of the complaint. Note any promises or commitments that were documented.
Step 4: Check warranty and service history
If the project is completed, review warranty cases or service calls that have already occurred. See if similar concerns were raised previously and how they were handled.
Step 5: Identify any patterns or misunderstandings
From the history, note patterns such as repeated rescheduling, repeated questions about the same topic, or unclear written explanations that might have contributed to the complaint.
Step 6: Summarize contextual findings in the complaint record
Add a short contextual note to the complaint form summarizing key background points, so whoever handles resolution can quickly see the bigger picture.
Log complaint in centralized tracking system
Step 1: Open the complaint tracking system or log
Access your CRM, issue tracking tool, or standardized spreadsheet where all complaints are recorded. Ensure you are using the official, shared system.
Step 2: Create a new complaint record
Start a new entry and fill in basic fields such as client name, project, date received, and intake source (phone, email, meeting, etc.).
Step 3: Enter detailed complaint summary
Copy or type the clear summary of the complaint, including what happened, impact, and desired outcome. Avoid emotional language of your own; stick to either the client’s words or neutral descriptions.
Step 4: Add severity, type, and priority fields
Set the complaint type (from your defined list), severity level, and any priority or risk flags. These fields will drive routing and reporting later.
Step 5: Attach supporting documents and references
Upload or link emails, photos, meeting notes, and any relevant project documents so the full context is accessible from the complaint record.
Step 6: Save the record and verify assigned ID
Save the complaint and confirm that the system has generated a unique ID or reference number. Note this ID in your intake form and in any future communication with the client.
Set expectations and explain the complaint handling process
Step 1: Prepare a simple explanation of your process
Draft a short explanation of your complaint handling steps—intake, internal review, proposed response, and follow-up. Keep the language simple and avoid heavy internal terminology.
Step 2: Inform the client of review and response timeframe
Tell the client when they should expect an initial substantive response (not just acknowledgment), based on the severity and type of complaint (for example, “within 2 business days for most issues, sooner for urgent matters”).
Step 3: Clarify that more information may be requested
Explain that the person handling the complaint may reach out for more details or documents to fully understand the situation, and that this is part of the process, not a delay tactic.
Step 4: Explain how updates will be provided
Tell the client whether updates will come by phone or email, and who will be their main point of contact going forward. Provide the name and role if already known, or explain that an assigned person will introduce themselves.
Step 5: Avoid making promises you cannot keep
Do not promise specific outcomes (such as refunds or free work) at this stage. Emphasize that the company will review the complaint carefully and respond with proposed next steps.
Step 6: Document what you told the client
In the complaint record, note the timeframe and process you explained, so future staff understand the expectations that have been set.
Assign complaint owner and escalation path
Step 1: Identify appropriate owner based on type and severity
Using your complaint types and severity levels, determine whether the owner should be a project manager, customer service lead, operations manager, or member of leadership. Use a simple matrix or guideline to make this decision consistent.
Step 2: Assign the complaint to the chosen owner in the system
Set the “Owner” or “Assigned To” field in your complaint tracking system and ensure the owner receives an automatic notification or an explicit email outlining their new assignment.
Step 3: Define escalation thresholds
Document when and how the complaint should be escalated—for example, if no progress is made within a set number of days, or if the client raises legal threats or media involvement.
Step 4: Record escalation path in complaint record
In the complaint notes, state who the next level of escalation is (for example, “If unresolved after 5 business days, escalate to Operations Director”) so anyone reviewing the case later can follow the path.
Step 5: Notify the assigned owner with a brief summary
Send a concise internal message to the new owner summarizing the complaint, severity, and any deadlines or special sensitivities. Include a link to the full complaint record.
Step 6: Update complaint status to reflect handoff
Change the status from something like “Intake – Open” to “Assigned – Under Review” to indicate that the complaint has moved out of intake and into active handling by an owner.
Send formal complaint acknowledgment to client
Step 1: Use a standardized acknowledgment template
Prepare a company-approved template that includes the company logo, a polite thank-you for the feedback, the complaint reference number, and a brief description of the next steps.
Step 2: Customize the template for this complaint
Fill in the client’s name, project address, the complaint ID, and a short neutral summary of the main concern. Avoid taking sides or assigning blame in this summary.
Step 3: Include information about assigned owner
State the name and role of the person who will be handling their complaint (if known) and how to contact that person or the general customer service line if needed.
Step 4: Restate expected response timeframe
Remind the client when they can expect a more detailed response or proposed resolution, based on what you discussed during intake.
Step 5: Provide instructions for additional information
Invite the client to reply with any documents, photos, or clarifications they think may help your review, and include the correct email address for sending this information.
Step 6: Send and log the acknowledgment
Send the email or letter and note the date and method in the complaint record. Attach a copy of the sent message to the complaint file so anyone reviewing the history can see exactly what was communicated.
👈 Use this SOP template inside Subtrak
Edit with AI. Customize in seconds. Store and share all your SOPs and checklists in one place.