Messaging Centre Route Change (v0.1.55)

⚠️ Action Required — The messaging centre URL has changed. Direct links using the old pattern will 404 unless a redirect is configured.

Overview

Starting in v0.1.55, the messaging centre is served from a new unified route. The previous route embedded accountType and personOID directly in the URL path. The new route is a flat, company-scoped path — account and conversation state are discovered dynamically after the page loads.

Old vs. New Route

Old route (broken)

/:company/:accountType/messaging-centre/:personOID

Example:

/letmcletting/LettingsTenant/messaging-centre/abc123

New route

/:company/messages

Example:

/letmcletting/messages

What the New Route Does Differently

• No accountType param — the page resolves the user's account type at runtime.
• No personOID param — conversation targeting via URL is not supported. The page dynamically discovers available accounts and messages on load.
• Single entry point — all user types (tenants, landlords, buyers, etc.) share the same route under their company prefix.

Impact

Scenario	Impact
Users following bookmarked old links	404 (unless redirect is added)
Emails / SMS containing old links	404 (update links to new path)
In-app navigation (updated)	Unaffected — updated to new route
Opening a specific conversation by URL	Not supported — users must select the conversation from the list

How to Fix Broken Links

1. Add a redirect in next.config.ts

This is the fastest fix to prevent 404s for anyone following an old link:

// next.config.ts
module.exports = {
  async redirects() {
    return [
      {
        source: '/:company/:accountType/messaging-centre/:personOID',
        destination: '/:company/messages',
        permanent: false,
      },
    ];
  },
};

permanent: false (HTTP 307) is recommended over a permanent redirect (HTTP 301) while the new route is still being verified, so browsers do not aggressively cache the redirect.

Limitation: The personOID value is silently dropped. Users land on the messages page but cannot be deep-linked to a specific conversation.

2. Update any external links

If your agency has sent links via email templates, SMS, or third-party systems, update them to the new pattern:

https://yourdomain.com/:company/messages

Known Limitation: No Deep-Link to a Conversation

The new unified messaging page does not accept a personOID or any conversation identifier in the URL. This is by design — the page manages conversation state internally after dynamically resolving the user's accounts. There is currently no supported way to link directly to a specific conversation thread via URL.

If deep-linking to specific conversations is a requirement, raise it as a feature request against the messaging centre.

Verification Checklist

Before promoting v0.1.55 to production:

• Confirm next.config.ts redirect is in place
• Test that an old-format URL redirects to /:company/messages without a 404
• Confirm the messages page loads correctly for all account types (tenant, landlord, buyer, etc.)
• Update any email or SMS templates that contained old messaging-centre links