How long should a small business keep an enquiry that never became a customer?

Start from the purpose, not an arbitrary number

An enquiry can contain a name, phone number, email address, project details, location and sometimes an attachment. Once a prospective customer stops replying, those details may remain in a web form database, shared inbox, sales spreadsheet and messaging service. A Hong Kong government brief explains that Data Protection Principle 2 requires practicable steps to prevent personal data being kept longer than necessary for its purpose, and section 26 concerns erasure when data is no longer required, subject to stated exceptions. Neither point supplies one universal number of days for every abandoned enquiry. Set a reasoned period against the actual service purpose and any genuine related need, then make the systems follow it.

Define the boundary of the record before writing a rule. A price request still under discussion differs from a duplicate contact, an obvious spam message, a cancelled appointment or a complaint about work already performed. The latter may have another documented purpose and may need a separate record class. Do not label everything a lead so that it can be held indefinitely. Equally, do not delete a live request merely because one staff member has not answered it yet. Record what event starts the clock, what event changes status, and who is allowed to change the status. This makes the rule auditable when staff move on.

Find every copy and its owner

Trace the enquiry through the full workflow. The public form might email two staff members, create a CRM record and send an alert to a messaging app. A sales colleague might then export a spreadsheet for follow-up. List each store, the person who controls it, the service provider if any, and the deletion mechanism. Include offline printouts, attachments, archive mailboxes and routine exports. A policy applied only to the main CRM record leaves the other copies behind. A government reply also explains that where a processor handles personal data on a business's behalf, contractual or other means should address excessive retention by that processor.

Check what the person was told when data was collected. The purpose of replying to a service enquiry is not automatically the purpose of sending future promotions. A contact asking for a quotation should not silently enter an indefinite marketing list because a salesperson would like to keep options open. Separate contact preferences and lawful marketing decisions from the operational enquiry record. If a person gives new information or becomes a customer, document the new purpose and applicable record type instead of quietly resetting the old timer. This is also a chance to ask whether the original form needs every field it collects; less data makes future deletion simpler.

Write a defensible trigger and review rule

A usable schedule has at least four parts: record class, purpose, trigger event and disposal action. For an ordinary unconverted enquiry, a business could start from the last meaningful two-way contact, allow a clearly justified follow-up window, then move the record to deletion review. The chosen length is a business judgement to document, not a statutory figure supplied by this article. Consider the sales cycle, whether quotes remain valid, the likelihood of a legitimate reply, and any separate legal or dispute need. Avoid a timer based only on a staff note saying 'still interested' when the person has not communicated that interest.

Use a different status when there is a real pending decision. For example, a site design enquiry may pause while the prospect waits for board approval. The employee should record the evidence for that pause, a next review date and the narrow reason to keep contact details. A vague 'open' flag without a review date makes the retention rule meaningless. If the matter becomes a paid project, move required records to the customer or contract schedule and remove surplus exploratory details. If a complaint or legal hold arises, document who authorised that separate purpose and which specific records it covers; do not automatically retain every unrelated enquiry in the mailbox.

Work through one abandoned enquiry

Suppose a local retailer asks a web studio for a new catalogue site, receives a proposal, then says the project is postponed. The proposal, meeting notes and contact details exist in email, CRM and a shared quote folder. At the postponement, staff mark the enquiry as dormant and set a review based on the documented sales cycle. At review they check for a genuine subsequent reply, an unresolved obligation, and any distinct reason to retain a final quote record. If none applies, they delete the CRM entry and linked files, clear local exports and address mailbox copies under the documented process. The example shows the sequence; it does not prescribe a period.

The difficult case is a single email thread mixing an abandoned sales question with a later support complaint. Do not erase the complaint merely because the first question expired, or retain all attachments because one message has a continuing purpose. Split or tag the records by purpose where the system supports it, and keep only what the remaining purpose needs. If the system cannot separate them reliably, assign a manual review with restricted access and an end date, then improve the workflow. Record the decision without copying sensitive details into a new spreadsheet that itself becomes another unmanaged archive.

Make deletion observable and repeatable

Run the schedule in a controlled job or regular staff review, not just a sentence in a privacy notice. The process should identify due records, check exceptions, log the class and reason for disposal, and confirm the action in each relevant system. Keep a small audit record that proves a decision occurred without retaining the deleted enquiry's whole contents. Spot-check a sample against email, CRM, exports and processor records. If a deletion command fails, mark the item for repair rather than reporting completion. Decide separately how backup retention works and ensure restored systems cannot silently bring expired live records back into use.

Give the frontline team a practical escalation path. They need to know where to mark an enquiry closed, how to flag a legitimate hold, whom to ask about a mixed-purpose thread, and how to report a stray export. Managers should review exceptions and sample outcomes, especially after changing a CRM provider or adding automation. A detailed retention policy and an erasure policy covering digital and physical records make that work repeatable. The useful measure is whether staff can actually find and dispose of a due enquiry across its copies, not whether the organisation has chosen an impressively short number on paper.

A deletion review should include a challenge step. Ask whether staff are keeping a record because it is useful for a stated current purpose, or merely because storage is cheap and the person might return someday. The latter is weak reasoning under a purpose-based rule. The business may keep an anonymised count of enquiry categories for planning if the data is genuinely no longer identifiable, but it should not call a row anonymous while a small team can still reconnect it to an email address or unique project description. Document how the de-identification decision was checked.

A sensible implementation avoids unnecessary new copies. Instead of exporting every closed enquiry to an audit spreadsheet, log a record identifier, class, decision date, responsible role and disposal result, with access limited to the people who verify the process. Keep that audit log on its own justified schedule. When an external service has a deletion interface, test a sample and confirm what the vendor says about archived and backup copies; do not infer erasure from the disappearance of a row in your own dashboard. Escalate unclear provider terms before representing the workflow as complete.

Review the schedule after a real business change. A new enquiry form may collect photos or identity details that the old process never handled; a longer sales cycle may justify a different review trigger; a new processor may hold data in another region or archive. Update the collection notice, inventory, contract instructions and deletion checks together. The schedule should also be understandable to a customer asking what happened to an old enquiry: staff should be able to explain the purpose and current status without improvising a legal deadline. A well-run process is evidence of disciplined decisions, not a promise that every case has identical facts.