Customer Complaint Intake for General Contracting

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.

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.

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.

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.

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.

Review the guide with office staff, project managers, and superintendents so everyone understands when and how to treat feedback as a formal complaint.

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.

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.

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.

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.

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.

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”).

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.

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.

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.

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.

Ask whether anyone else should be copied on future communications (for example, spouse, property manager, or business partner) and record their names and roles.

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.

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.

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”).

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.

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.

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.

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.

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.

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.”

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.

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.

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.

If a complaint meets High or Critical criteria, immediately notify the appropriate manager or leadership as per company policy, regardless of normal intake timelines.

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.

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.

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.

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.

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.

Add a short contextual note to the complaint form summarizing key background points, so whoever handles resolution can quickly see the bigger picture.

Access your CRM, issue tracking tool, or standardized spreadsheet where all complaints are recorded. Ensure you are using the official, shared system.

Start a new entry and fill in basic fields such as client name, project, date received, and intake source (phone, email, meeting, etc.).

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.

Set the complaint type (from your defined list), severity level, and any priority or risk flags. These fields will drive routing and reporting later.

Upload or link emails, photos, meeting notes, and any relevant project documents so the full context is accessible from the complaint record.

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.

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.

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”).

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.

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.

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.

In the complaint record, note the timeframe and process you explained, so future staff understand the expectations that have been set.

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.

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.

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.

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.

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.

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.

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.

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.

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.

Remind the client when they can expect a more detailed response or proposed resolution, based on what you discussed during intake.

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.

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.