How North Coast Stays built a scalable guest communication system to manage growth across Manchester and Liverpool with StayReply

North Coast Stays began as a small operation managing a handful of city centre apartments across Manchester. In its first two years, the business was run almost entirely by its two founders, who handled bookings, guest messaging, cleaner coordination, and owner reporting between themselves. The structure worked because the portfolio was small enough to hold in memory, and because guest communication volume was manageable through a shared inbox and a few WhatsApp groups.

As the portfolio grew past twenty properties, the business began to take on a different shape. Liverpool was added as a second market, and the company started signing agreements with landlords who owned multiple units rather than single apartments. The pace of growth accelerated, and within eighteen months the portfolio had grown from eighteen properties to seventy-four. The team expanded alongside it, with two full-time guest support staff, a dedicated operations lead, and a small network of contracted cleaners working across both cities.

The challenge was not the growth itself, but the speed at which guest communication volume scaled relative to the team. Each property generated a baseline of expected messages — pre-arrival enquiries, check-in instructions, mid-stay questions, and post-departure follow-ups — but the variability between guests meant that the actual volume could be two or three times higher than baseline during busy weeks. By the time the portfolio reached fifty properties, the team was responding to over four hundred guest messages per week, with significant peaks during weekends and city event periods.

The early manual workflows that had served the business well in its first years began to break down. Response times started to drift, particularly during evenings and weekends when only one team member was on duty. Guests who had asked the same question — about parking, Wi-Fi codes, late check-in procedures — were getting slightly different answers depending on who responded. The founders began spending an increasing portion of their time covering gaps in the guest support function rather than working on the growth of the business itself.

It was at this stage that the team began to look seriously at how to bring structure into their guest communication operation without slowing down the responsiveness that had become part of their reputation in the market.

Where complexity starts to compound

The operational issues that emerged at North Coast Stays were not the result of any single failure point. They were the cumulative effect of a business that had outgrown the informal systems it had been built on. What had worked at fifteen properties was no longer viable at sixty, and the team began to notice patterns that pointed to a deeper structural problem.

The most visible issue was inconsistency in guest messaging. Different team members handled the same situations in different ways, which meant that the experience a guest received depended heavily on who happened to be on shift. There was no shared library of approved responses, no documented escalation procedure for issues that required input from cleaners or maintenance, and no centralised view of what had been said to a guest across the lifecycle of their stay.

A few specific patterns emerged as the portfolio grew:

• Repeated questions about access, parking, and Wi-Fi were being answered individually each time rather than handled through a standardised pre-arrival flow

• Maintenance issues raised by guests were being communicated through ad hoc WhatsApp messages between team members, with no formal record of what had been reported or resolved

• Cleaner handovers between checkout and check-in were coordinated through a separate set of group chats, disconnected from the main guest communication system

• The shared inbox was being used by multiple people simultaneously, which led to occasional duplicate responses and missed messages

• Onboarding new team members required several weeks of shadowing, because most of the operational knowledge lived in the heads of the two founders and the operations lead

These issues did not cause any single major failure. What they did cause was a steady increase in the operational effort required to maintain the same level of service. The team was working harder to stand still, and the founders began to recognise that the business could not continue to scale without a fundamental rethink of how guest communication was structured.

Introducing structure without slowing teams down

When North Coast Stays began to evaluate StayReply, the priority was not to replace the team's existing workflows but to give them a foundation that could support the volume and variability the business was now dealing with. The goal was to standardise the parts of guest communication that were genuinely repetitive, while preserving the team's ability to respond personally to anything that required judgement.

The first phase of the rollout focused on the most common guest interactions. Pre-arrival messaging, check-in instructions, Wi-Fi and access information, and standard mid-stay follow-ups were moved into automated flows that triggered based on booking milestones. The team built out a library of approved response templates for the most frequent guest questions, which any team member could deploy with a single action rather than typing out from scratch each time.

The centralised inbox became the operational core of the new system. Every guest message, regardless of which channel it came in through, was routed into a single view where the team could see the full context of a guest's stay alongside the conversation. Assignment rules were introduced so that incoming messages were automatically allocated to the team member responsible for that property or that shift, which eliminated the duplicate-response problem that had been a persistent source of friction.

Escalation flows were built out for the situations that required input beyond the front-line guest support team. If a guest reported a maintenance issue, the message was tagged and routed to the operations lead alongside the original guest thread, so that the response back to the guest was always anchored in the same conversation. The same approach was applied to cleaner coordination, where checkout reports and access issues were brought into the same operational view rather than living in a separate set of chats.

The team was careful to roll out the new system in phases rather than all at once. Each new workflow was tested with a subset of properties before being deployed across the full portfolio, which gave the team time to refine the templates and routing rules without disrupting live operations.

From individual knowledge to shared systems

One of the most significant shifts at North Coast Stays was the move away from operational knowledge being held in individual heads. In the early stages of the business, the two founders and the operations lead had functioned as the institutional memory of the company. They knew which properties had quirks with their boilers, which buildings required specific access codes for the lift, and which landlords preferred to be contacted by phone rather than email. This knowledge was effective when the team was small, but it created a structural weakness as the business grew.

The transition involved translating this individual knowledge into shared systems that any team member could access and act on. Property-specific notes were built into the StayReply platform, attached to each listing and visible alongside every guest conversation. Escalation pathways were documented, so that when a guest reported an issue, the team member handling the conversation knew immediately who to involve and how. Standard operating procedures for common situations — late check-ins, lockouts, complaints about cleaning standards — were written out and made available within the platform itself.

The impact on onboarding was immediate. New team members who joined the business after the system was in place were able to handle guest communication independently within their first week, rather than requiring several weeks of shadowing. The operations lead noted that the time she spent answering internal questions from the team dropped substantially, because most of the information that team members needed was now available to them directly.

The broader effect was that the business became less dependent on the continuous presence of any individual. Holiday cover, weekend shifts, and out-of-hours support could now be handled by any team member, because the operational knowledge required to respond to guests was no longer locked into the experience of specific staff.

Improving coordination across teams

As North Coast Stays grew, the coordination challenges between guest support, cleaners, and maintenance became one of the most operationally demanding parts of the business. Each function had its own communication patterns, its own response times, and its own way of recording what had been done. When a guest reported an issue, the path from the initial message to a resolution often involved three or four separate conversations across different channels, with no single source of truth.

Bringing these functions into a shared operational view was one of the most consequential changes the team made. Cleaners were given access to a streamlined view of the platform that showed them their upcoming turnovers, any reports from the previous guest, and any specific instructions for that property. Maintenance issues raised by guests were logged directly against the property, with status updates visible to both the guest support team and the operations lead.

The effect was a noticeable reduction in the friction that had previously slowed down operational decisions. When a guest reported a problem with a kitchen appliance, the guest support team could see whether it had been reported before, whether a repair was already scheduled, and what the expected timeline for resolution was — all without having to message three different people to find out. The same was true for cleaner handovers, where issues identified at checkout could be flagged immediately and incorporated into the maintenance schedule before the next guest arrived.

Owner communication also became more structured. Landlords with multiple properties received consolidated updates rather than fragmented messages from different team members. When issues arose that required owner approval — significant repairs, refund requests, or property access for contractors — the conversation was anchored in a clear thread with the relevant context attached.

A system that evolves with the organisation

One of the considerations that shaped North Coast Stays' approach to StayReply was that the business was still in a phase of active growth. The team did not want to build a system that worked at seventy properties but would need to be rebuilt at one hundred and fifty. The emphasis was on creating workflows that could be iterated on rather than replaced.

As the portfolio has continued to expand, the team has refined the system in incremental ways. New property types — including a small number of larger group-stay homes that required different communication patterns from the standard city centre apartments — were brought in by adapting existing workflows rather than starting from scratch. Seasonal adjustments, such as the additional pre-arrival information required during winter months for properties without dedicated parking, were built into the automated flows without requiring a full restructure.

The operations lead has taken on the ongoing role of refining the workflows as the business evolves. New patterns that emerge from guest feedback or operational issues are translated into updates to the templates and routing rules, which means that the system continues to improve in step with the business rather than falling behind it.

The team's view is that the structure they have now is not a finished product. It is a foundation that supports the next phase of growth, and one that can be adjusted as the requirements of the business change.

Closing perspective

What North Coast Stays achieved with StayReply was not a transformation in the dramatic sense. It was a structural shift from a business that relied on the continuous effort of its founders to one that runs on systems that any team member can operate within. The portfolio has grown, the team has grown, and the operational complexity has grown — but the core function of guest communication has become more consistent and more manageable rather than less.

The business is now in a position to add properties without adding proportionate operational headcount, which was not the case before. Response times have stabilised, guest feedback on communication has become more consistent, and the founders have been able to step back from day-to-day guest support to focus on the longer-term growth of the company.