sample internal document · 4 sections indexed
Council CRM response guidelines (sample)
Sample document. Every figure below is invented.
Tree Truck publishes none of this, and a council should not. It was written for this demo to stand in for the plain-English guidelines an office manager works to when replying to a council tree complaint: the tone rules, the things never to say, and the shape of a reply. The rules below follow the structure of the guidelines the business already uses; the wording is written for this demo, so the seats have something real-shaped to read. Nothing here is a claim about Tree Truck.
Readable from: Manager, Accounts. Every other seat is refused this document by name.
Section 1
Tone: professional, neutral, and never defensive
Every reply is written in a professional and neutral tone, calm and factual, whatever the tone of the complaint. Acknowledge the concern clearly and early, in the resident's own terms, before any explanation. Do not argue with the account given, and do not correct it in the reply unless a factual correction is necessary to answer the question. Keep sentences short and avoid contract language a resident has no reason to know. Never write anything that reads as though the complaint is a nuisance, and never imply the resident should have contacted somebody else, even where they should have. The reply is written on behalf of a contractor working under a council contract, so it carries the council's standing as well as the company's.
Section 2
The four things a reply never does
A reply never admits liability. Where damage or fault is alleged, the reply records that the matter has been referred for inspection and says nothing about cause, responsibility or cost. A reply never promises a specific outcome to a resident, and never states that a tree will be pruned or removed before an inspection has been carried out and the decision made. A reply never promises anything outside the contract, including timeframes, works or attendance the contract does not provide for. And a reply only cites a clause of the specification or a council policy that has actually been supplied: if the clause is not to hand, the reply describes the standard in general terms or says the position will be confirmed, and it does not reconstruct the wording from memory. A cited clause that turns out not to say what the reply said it said is worse than no citation.
Section 3
Safety, inspection and the council's own position
Where safety or public risk is involved, the reply leads with it and says what is being done about it, including any temporary measure taken on site. Where there is any uncertainty about the condition of a tree, the reply recommends inspection or further assessment rather than an opinion. Reflect the council's published position rather than inventing one: health and safety comes first; inspections run on a structured cycle and further work may depend on that assessment; decisions weigh community benefit and the long-term health of the tree collection; and removal is considered where it is necessary, not solely because a tree is inconvenient to one property. Where the council's published policy is that it will not act on a category of complaint, say so plainly and say who the resident can talk to about it.
Section 4
The shape of the reply, and who sends it
A reply follows the same seven parts every time: a subject line carrying the CRM reference number, an acknowledgement of the concern, a short summary of the issue as reported, the relevant contract or policy context where it has been supplied, the action taken or proposed, the next steps with a timeframe where one can honestly be given, and a professional close with a contact point. Nothing is sent automatically. Every draft is read and approved by a person before it leaves, and the approval is recorded against the case, because the reply is a position taken on behalf of the business and on council work. A draft is a starting point for the person who sends it, not a decision the system has made.