Activity After Exclusion? What to Share With Support
An existing-customer checklist for reporting new observations after completed exclusion work, without assuming a repair failed or a warranty claim is covered.
New wildlife activity after completed exclusion work is a reason to record what you have noticed and contact the appropriate support route. It is not, by itself, proof that a repair failed or that a warranty claim is covered. Keep those questions separate from the observations you can report.
For an existing Critter-Ridder customer, the practical starting point is a clear set of project records, notes about the new activity, and the details needed to find the service file. This checklist explains what to gather before making contact. It does not determine the cause of activity, interpret warranty terms, or decide what work should follow.
1. Locate the records for the completed project
Look for the written project scope, completion record and any related correspondence you already have. Keep the original documents together so that your account of the earlier work stays connected to its actual record. If you have an inspection report or photographs supplied with that project, include those with the same group of materials.
Make a short note of the service address and the date the work was completed, if that date appears in your records. Do not replace a missing document with an estimate of what you think it said. You can explain that a record is unavailable when you contact support. Gathering documents is preparation for review, not a decision about what the project or warranty covers.
2. Describe exactly what you noticed
Write a plain description of the new observation. For example, distinguish a sound you heard from an animal you actually saw. If you are uncertain about a detail, say that it is uncertain. A concise account can retain that uncertainty without turning it into a species identification, a diagnosis or a statement that earlier work has failed.
Identify the location as clearly as you can from your existing observations: which room, side of the building or nearby feature was involved? Keep separate observations separate. Activity reported near one part of the property should not be described as confirmed activity throughout the building. The purpose of the note is to communicate what you noticed, rather than to establish an explanation.
3. Keep the timing attached to each observation
Record when you first noticed the activity and when you noticed it again. If you know only the approximate date or time, label it as approximate. You do not need to make the account sound more precise than your recollection allows. A dated list is a practical way to avoid mixing several observations into one event.
If you already made notes at the time, preserve them alongside the summary you send. Distinguish those original notes from details added later from memory. You can also say whether a description refers to one observation or several. This is simply a way to present your information clearly; the timing does not establish a cause, repair failure or coverage decision.
4. Note later building work or damage without assigning a cause
Include known building work or damage that occurred after the exclusion project was completed. State what changed, where it occurred and any date you can support from your records. Keep the description factual. If you do not know whether a change is related to the new observation, leave that connection as unknown.
This note is not a request for you to diagnose the building or decide who is responsible for the activity. It also does not establish whether later work affects a particular warranty question. You are supplying context for the team to review with the project file. Avoid turning the sequence of two events into a conclusion that one caused the other.
5. Prepare the details needed to locate your file
Critter-Ridder's current existing-customer support instructions ask for your full name, phone number and complete service address. Have those details ready with the project records and observation summary. Use the address where the earlier work took place, and make clear which property your request concerns if you have records for more than one address.
Check that the callback details you provide are the ones you want the team to use. Keep the support request focused on the relevant property and observations rather than adding unrelated project information. These details help identify the file for review. Providing them does not establish an appointment, a response deadline, a finding or an approved warranty claim.
6. Use the current existing-customer support route
Find the current contact instructions under Existing Customer Warranty Support. Use that route when asking about the earlier project, rather than assuming that a general inquiry and an existing-customer support request follow the same path.
The published instructions say the team locates and reviews the file before responding. Submit the project and observation details as a request for that review. Do not treat sending the information as confirmation that the new activity is connected to completed work. The team reviews the file and condition before determining the appropriate next steps.
7. Keep the warranty question with its written source
If you have a question about the warranty, identify the question and keep the project documents available. This checklist deliberately does not restate the warranty's terms, limitations or exceptions. The definitive warranty information and your written project records belong with that discussion; a general article is not a coverage determination.
New activity and a covered claim are separate matters. Nothing in an observation log, a photograph or this preparation checklist proves that the earlier repair failed or that a particular response is included. Avoid treating a suspected explanation as a finding. Ask the support team about the records and the review rather than drawing a contractual conclusion from a new sighting.
8. Send a clear summary and leave next steps for review
Before making contact, check that your summary includes the earlier project records you found, the new observations with locations and timing, any known later building work or damage, and the contact details for the service address. Mark missing information plainly. Keep your original records so that the summary does not become a replacement for them.
For an existing project, begin with the support instructions linked above. If your question instead concerns requesting an inspection, the website also provides an inspection-request page. State what you are asking about without assuming a diagnosis, a repair failure, coverage or a particular service outcome.
Common questions
Preparing an Existing-Customer Support Request
What records should I gather before contacting support?
Gather the written project scope, completion records and related correspondence you already have. Keep any supplied inspection report or photographs with those records. Note the service address and dates supported by the documents, and identify anything you cannot locate.
Does new activity automatically mean a covered warranty claim?
No. A new observation alone does not establish a repair failure or a covered claim. Record what you noticed and use the existing-customer support route. Leave the cause, coverage question and next steps for the appropriate review.
How should I describe later changes to the property?
State the building work or damage you know occurred, its location and its timing if known. Do not diagnose a cause or assume that a later change explains the activity. Mark an uncertain connection as uncertain.
Where should an existing customer contact Critter-Ridder?
Use the current Existing Customer Warranty Support instructions on the inspection-process and warranty page. Have your full name, phone number and complete service address ready so the team can locate the project file for review.
Related guidance