Smarter Letters, Smarter Services: Transforming Customer Correspondence

Reducing Hard Coding Through Automation

A key design principle should be to minimise hard-coded content wherever possible.

Rather than embedding fixed information directly into templates, letters should retrieve information dynamically from the housing management system. This reduces the need for technical changes whenever business information changes and ensures correspondence always reflects the latest available data. By using data-driven parameters and intelligent text, letters can automatically adapt based on resident and tenancy information, including:

• Payment method
• Tenancy status
• Property information
• Vulnerability indicators
• Damp and mould records

This approach reduces maintenance, improves consistency, and creates a more personalised customer experience.

Empowering the Business

Not every change should require technical support.

Business-owned information such as office addresses, contact details, and service information should be maintained by the teams responsible for that content. Providing configurable fields enables business users to make routine updates without raising support requests, while appropriate governance ensures consistency and control.

Making Correspondence Intelligent

Technology alone will not deliver better correspondence.

Conditional logic allows paragraphs to be included or excluded automatically based on information held within the system. For example, payment instructions can differ depending on whether a resident pays by Direct Debit, while additional guidance can be included for vulnerable residents or where damp and mould cases are recorded.

The success of this approach depends on one important factor: high-quality data. Intelligent letters are only as effective as the information used to generate them.

Governance Is Essential

Modern correspondence should reflect a resident's individual circumstances rather than following a one-size-fits-all approach.

Some templates—particularly those supporting statutory or compliance processes—should remain tightly controlled, while others may require greater flexibility for operational teams.

Role-based security provides an effective way to manage this balance by ensuring only authorised users can amend templates where appropriate.

Consideration should also be given to where frequently changing content is maintained. Information such as legal wording or configurable timescales may be more effectively managed directly within templates, reducing formatting issues and simplifying future updates.

Creating a Single Source of Truth

Document management is another important consideration.

Rather than storing correspondence in multiple locations, organisations should aim for a single repository where documents can be securely managed, indexed, and retrieved. Integrating with a corporate document management solution, such as SharePoint, improves governance, accessibility, and long-term record management.

A clear document hierarchy should also be agreed, determining whether correspondence should be indexed against the property, tenancy, individual, or a combination of these to support efficient retrieval.

Taking a Pragmatic Approach to Go-Live

Transformation projects often require a balance between immediate delivery and long-term improvement.

One practical approach is to migrate the existing suite of letters for the initial go-live and then refine and standardise them during User Acceptance Testing (UAT) and subsequent project phases.

This enables the programme to maintain momentum while providing opportunities to introduce automation, improve governance, and enhance the overall quality of correspondence over time.

Looking Ahead