--- title: What a Concierge App Waiting Until the Weekend Taught Us About Timing an Emotional Ask description: Discover how timing an emotional prompt in a concierge app transformed user engagement. Learn why when you ask matters as much as what you ask. image: https://weareaffective.com/hubfs/learning-centre-images/what-a-concierge-app-waiting-until-the-weekend-taught-us-about-timing-an-emotional-ask.webp --- [Skip to content](https://weareaffective.com/learning-centre/what-a-concierge-app-waiting-until-the-weekend-taught-us-about-timing-an-emotion#main-content) [![we\_are\_affective\_logo\_200](https://weareaffective.com/hs-fs/hubfs/we_are_affective_logo_200.png?width=175&height=48&name=we_are_affective_logo_200.png "we_are_affective_logo_200")](https://weareaffective.com) - [Home](https://weareaffective.com) - About Us - [Our Story](https://weareaffective.com/about) - [How We Work](https://weareaffective.com/how-we-work) - Our Services - [App Planning & Strategy](https://weareaffective.com/app-planning-strategy) - [App Design](https://weareaffective.com/app-design-agency) - [App UX Design](https://weareaffective.com/app-ux-design) - [App UI Design](https://weareaffective.com/app-ui-design) - [App Technical Architecture](https://weareaffective.com/app-architecture) - [Existing App Audits](https://weareaffective.com/app-audit) - [Case Studies](https://weareaffective.com/case-studies) - [Pricing](https://weareaffective.com/pricing) - [Learning Centre](https://weareaffective.com/learning-centre) - [Get Started](https://weareaffective.com/get-started) Expert Guide Series # What a Concierge App Waiting Until the Weekend Taught Us About Timing an Emotional Ask Table of Contents Moving home ranks among the most emotionally loaded experiences a person can have. The logistics alone are exhausting, and underneath them sits something harder to name: the strange mixture of excitement, anxiety, grief, and hope that comes with leaving one place and arriving in another. Someone moving into a new flat after a separation feels nothing like someone buying their first property after years of saving. And yet, for decades, building management apps have treated both people identically, handing them a full directory of information on day one and expecting them to engage with it. > The timing of a notification shapes whether it is read, and how the product feels to live inside. We were asked to design a concierge app for residents moving into a premium residential development, and one of the first things we did was refuse to do what every comparable product does. We did not surface all the information at once. We did not give users the recycling locations, the fire procedures, the local area guides, and the gym booking system in a single onboarding dump. Instead, we treated the timing and sequencing of information as an [emotional design problem, and what came back from user research](https://weareaffective.com/user-psychology-app-design), focus groups, and A/B testing confirmed that the decision was right. Residents who received delayed, context-sensitive notifications reported measurably lower stress levels than those who did not. This article is about what we learned building that system, and why the principle behind it matters far beyond property apps. ## Why Timing Is a Design Decision, Not a Default Product teams spend a great deal of energy on what to say to users and almost no energy on when to say it. The notification copy gets revised, the onboarding screens get tested, the feature set gets debated. But the moment of delivery is usually left to a default setting or a rough rule of thumb: two days after sign-up, one week after purchase, the morning after account creation. This is a mistake, and it is a mistake that compounds over time. A message that arrives at the wrong moment does not simply fail to land. It actively damages the relationship. The user does not think "that was not quite the right time." They think "this app is pestering me" or "I have no idea why I am receiving this." The emotional register shifts from supported to pressured, and that shift is hard to reverse. Timing is also not one decision. It is a set of decisions layered on top of each other: time of day, day of week, days since a specific event, the user's current context, and whether they have already encountered a related piece of information. When those layers are designed deliberately, the result is [a product that feels like it knows the user](https://weareaffective.com/learning-centre/why-do-some-apps-feel-like-they-were-made-just-for-you). When they are left to default, the result is a product that feels indifferent to them. Before setting any notification schedule, write down the emotional state your user is most likely to be in when that notification arrives. If you cannot describe that state with some confidence, the timing has not been designed yet. ## The Concierge App: What the Brief Actually Asked For The original brief was straightforward, at least on the surface. The client wanted a concierge app for residents of a high-end residential block, mostly high-net-worth individuals, that would give everyone in-app access to everything they needed so they would not have to speak to the concierge directly. The reasoning was efficiency: if residents could find answers themselves, the concierge could focus on physical tasks rather than fielding the same questions repeatedly. We pushed back on this framing fairly early. Not because digital self-service is wrong, but because the brief treated the concierge as a problem to be bypassed rather than a relationship worth cultivating. Focus groups we ran during the discovery phase confirmed that the real issue was not access to information. It was connection. Residents in the building did not know their neighbours, did not know the concierge as a person, and had no particular reason to engage with either. The app, as originally conceived, would have made that worse. So [the product strategy shifted](https://weareaffective.com/learning-centre/what-belongs-in-a-product-strategy-before-you-talk-to-a-development-team). We kept the self-service functionality for the mundane and transactional: maintenance requests, fire drill procedures, package collection, gym booking. But we repositioned the concierge as a human relationship worth encouraging. We gave each concierge a personal profile in the app, listing topics they enjoy talking about, football, motorsport, whatever was genuine, and explicitly inviting residents to have those conversations in person. The logic was simple: if the app handles the forgettable, it frees up space for the memorable. ## UX/UI design built around *real* psychology We design app interfaces around how people actually think and behave. User research, psychology-driven UX/UI design and technical specs delivered as one complete package. [See how we work](https://weareaffective.com/how-we-work) [Get started](https://weareaffective.com/get-started) No commitment ## What Focus Groups Revealed About Move-In Behaviour To design the notification timing system, we needed to understand [how people actually behave when they move into a new property](https://weareaffective.com/learning-centre/what-a-development-team-actually-needs-to-know-about-the-user-before-sprint-one). Not how they say they behave, and not how property managers assume they behave. How they actually behave, which meant focus groups and scenario research before we wrote a single line of logic. One finding that shaped everything was the role of arrival time. Someone who arrives at a new flat in the morning is likely to start unpacking that day. Someone who arrives in the evening will almost certainly not unpack until the next day. This sounds obvious in hindsight, but it has real consequences for notification timing. If the app sends a message about recycling locations the morning after move-in, that message lands at a very different moment depending on when the resident arrived. > Someone arriving on a Wednesday evening and someone arriving on a Saturday morning are not at the same point in the same journey. We also looked at household composition. A single person moving alone takes longer to unpack than a couple, and a family of four is a different story again. The number of people in a household is not just a demographic detail. It changes the pace of the settling-in process and therefore the point at which different types of information become useful and relevant rather than intrusive. The focus groups also included people from social housing, not the target market for this product, but genuinely useful because they showed us something about community that the brief had not anticipated. What those groups demonstrated was that the conversations worth having were not transactional. They were deeper, more personal, and those were the ones that built a genuine sense of belonging. That finding reinforced the strategic direction: let the app carry the transactional load so that the human conversations can be the ones that actually matter. ## Building a Dynamic Timing System From Real Behaviour Armed with what the focus groups told us, we designed a notification system that was [dynamic rather than fixed](https://weareaffective.com/learning-centre/5-things-that-make-the-difference-between-so-so-apps-and-stellar-apps-what-your-). The standard approach in this kind of product is a static schedule: two days after move-in, send the recycling information, one week after move-in, send the local area guide. It is simple to build and easy to explain to a client. It is also largely wrong, because it assumes every resident's move-in experience follows the same rhythm. Our system used two primary variables to determine when each notification should fire. The first was the time of arrival at the property. The second was the number of occupants. From those two inputs, the system calculated a likely unpacking timeline and scheduled each notification to arrive at a point when the information it carried would actually be useful. When designing a timing system for any lifecycle notification, identify the real-world event that makes the information relevant, and use that as your trigger point rather than a fixed number of days from sign-up. The recycling information, for example, was tied to an assumption about when boxes would be empty and ready to dispose of, which varied depending on arrival time and household size. Local area recommendations were tied to the first weekend after move-in, on the reasoning that this was when a new resident was most likely to have time and mental space to explore. Neither of these was a guess. Both came directly from what focus group participants described about their own move-in experiences. The result was a system where two residents moving in on the same day could receive their notifications in a different order and at different times, and both sequences would be right for them specifically. ## The Weekend Rule and the Unboxing Window Two timing decisions from the concierge app are worth describing in detail because they illustrate the logic cleanly. The first is what we came to think of as the weekend rule. If a resident signed up midweek, the system held back any notifications about exploring the local area until the following weekend. The reasoning was straightforward: a person who has just moved in on a Tuesday or Wednesday is not going to walk around discovering local coffee shops and parks on a Wednesday evening. They are unpacking, sorting utilities, and recovering. The weekend is when that kind of exploration becomes natural, so the weekend is when the suggestion belongs. The second is the unboxing window. We assumed that a resident would still have cardboard boxes to deal with for a day or two after move-in. Sending recycling information on the first morning would be premature. Sending it a couple of days later, when the boxes were more likely to be empty, put the information exactly where it was needed. This is not a complex piece of logic. But it requires someone to have thought carefully about what a resident's physical and emotional situation actually looks like, day by day, rather than treating "post move-in" as a single undifferentiated state. The system also factored in whether residents had children, promoting child-friendly local features to families at relevant moments. Again, the data point was simple. The effect on how the product felt was not. ## What the A/B Testing Confirmed We ran A/B testing and user research with real residents to compare the delayed, dynamic notification approach against the standard approach of delivering information upfront. The results were clear. Residents who received the delayed notifications reported measurably lower stress levels than those who received everything at once. This matters because stress reduction was not a metric anyone had put on the brief. The client was measuring engagement, app usage, and resident satisfaction in a general sense. But the stress finding told us something more specific: the timing system was not just improving usability, it was [changing the emotional experience of moving into the building](https://weareaffective.com/learning-centre/how-to-read-a-user-session-recording-for-emotional-signal-rather-than-task-compl). The app was participating in a genuinely difficult transition and making it slightly easier, rather than adding to the cognitive load of an already demanding period. The perception of notifications also shifted. In the group that received everything at once, notifications were experienced as demands or alerts, something requiring attention or action at a moment when the resident had no bandwidth for either. In the group that received delayed, context-sensitive notifications, the same type of message was perceived as helpful and anticipated. Residents described it as feeling like the app knew what they needed, and was waiting for the right moment to offer it. That is a fundamentally different emotional relationship with a product, and it is almost entirely the result of timing. Research from [Wisernotify](https://wisernotify.com/blog/push-notification-stats/) suggests that sending notifications during a user's preferred time window can increase open rates by up to 40 per cent. The emotional dimension we observed goes further than open rates, but the direction of travel is consistent: timing is not a secondary consideration. ## When the Right Message Arrives at the Wrong Moment There is a version of this problem that appears in almost every product category, not just residential apps. A user installs a fitness app and is immediately asked to rate it before they have completed a single workout. A retail app sends a push notification about a sale at 2am. A charity app asks for a donation on the welcome screen before the user has understood what the organisation does. In each case, the content of the message is not the problem. The timing is. And the timing fails because nobody designed it. It defaulted to whatever was easiest to build or whatever the platform recommended, without anyone asking: what is this user's emotional state right now, and is this the moment they will be receptive to this ask? One of the clearest versions of this we have encountered is app rating prompts that fire on the first open. The user has not yet experienced anything. The rating they give is meaningless, and the prompt itself signals that the product team is more interested in their own metrics than in the user's experience. A rating prompt earns its place when it appears after a genuinely positive moment, after a booking confirmed, a goal reached, a problem solved. At that point, the user has something real to say, and they are in the emotional state that produces honest positive feedback. Map your notification schedule against your user's emotional journey, not just their functional journey. Ask where they are likely to feel good about the product, and put your highest-trust asks at those points. ## The Transferable Principle for Consumer Brands The concierge app was a specific context, premium residential, high-net-worth residents, a genuinely significant life event as the trigger. But the principle that made the timing system work is not specific to property. It applies to any product where users arrive in a particular emotional state that changes over the [first days and weeks of use](https://weareaffective.com/learning-centre/why-product-owners-should-write-the-users-second-session-before-the-first-one). Consider the difference between these two scenarios. | Trigger event | User's emotional state on day one | What belongs on day one | What belongs on day seven | | --- | --- | --- | --- | | Moving into a new home | Overwhelmed, tired, excited | Basic orientation, nothing more | Local exploration, community features | | [Starting a new fitness programme](https://weareaffective.com/learning-centre/fitness-app-trends-2026-what-users-really-want-from-their-workout-apps) | Motivated but uncertain | First session, clear and short | Progress tracking, social features | | Signing up after a health scare | Anxious, seeking reassurance | Calm, reassuring information | Habit-building features, goal setting | The pattern holds across all three. The first day is rarely the right moment for the full product. It is the moment for the minimum that makes the user feel safe and capable. The fuller picture comes later, when they have settled, built some confidence, and have the mental space to engage with more. According to [Business of Apps](https://www.businessofapps.com/marketplace/push-notifications/research/push-notifications-costs), [78 per cent of users churn in the first week](https://weareaffective.com/learning-centre/why-most-business-apps-fail-and-how-your-digital-business-can-avoid-the-same-fat) after installation when brands do not have a clear engagement strategy built around push notifications. The timing system we built for the concierge app was precisely that kind of strategy, designed around real behaviour rather than arbitrary defaults. ## Conclusion The concierge app project confirmed something we had long believed but had not yet tested at this level of rigour: notification timing is an emotional design decision, and treating it as a technical default is a meaningful failure of care. When the timing is right, a notification does not feel like an interruption. It feels like the product has been paying attention. The weekend rule and the unboxing window are small decisions on paper. But they changed how residents experienced the first weeks in their new home, and they changed how those residents related to the product. Stress levels were lower. The notifications were perceived as helpful rather than demanding. The app felt human because it behaved the way a thoughtful person would: waiting until the right moment, rather than saying everything at once. The same discipline applies to any product that asks something of its users, whether that is a rating, a permission, a personal detail, or a decision. The question is what you are asking, and whether this is the moment the user is ready to be asked. Building that kind of timing into a product takes research, focus groups, real behavioural data, and the willingness to push back on the default. It is work that most briefs do not include and most timelines do not protect. But the outcomes, lower stress, higher engagement, a product that feels like it is on the user's side, are worth the effort. If you are thinking about how timing and emotional state interact in your own product, [let's talk about your notification strategy](https://weareaffective.com/get-started). ## Frequently Asked Questions Why does the timing of a notification matter so much? A notification that arrives at the wrong moment does not simply go unread. It can actively damage the relationship between the user and the product, shifting how the app feels from supportive to intrusive. Once that emotional shift happens, it is difficult to reverse. What was the core problem with how most concierge apps handle onboarding? Most concierge apps surface all available information on day one, treating every resident identically regardless of their circumstances or emotional state. Someone moving after a separation and someone buying their first home are in entirely different headspaces, and a single information dump serves neither of them well. What did the team do differently when designing this concierge app? Rather than releasing all information at once, the team treated the timing and sequencing of content as an emotional design problem. Notifications were delayed and made context-sensitive, so residents received information when they were most likely to be ready for it. Did the approach of delaying notifications actually make a measurable difference? Yes. Residents who received delayed, context-sensitive notifications reported measurably lower stress levels compared to those who did not. This was confirmed through user research, focus groups, and A/B testing. What layers of timing does a well-designed notification system need to consider? Timing is not a single decision but a set of overlapping ones, including time of day, day of week, days since a specific event, the user's current context, and whether they have already encountered related information. When these layers are designed deliberately, the product feels like it genuinely understands the user. How should a product team approach setting a notification schedule? Before deciding when to send any notification, the team should be able to describe the emotional state the user is most likely to be in when it arrives. If that cannot be articulated with some confidence, the timing has not yet been properly designed. What was the original client brief, and why did the team push back on it? The client wanted an app that gave residents self-serve access to everything they needed, primarily to reduce direct contact with the concierge. The team challenged this framing because efficiency alone is not a sufficient design goal when the people using the product are navigating a significant and emotionally complex life event. Does the principle behind this approach apply beyond property or concierge apps? According to the team, yes. The idea that emotional context should shape when information is delivered is relevant to any product where users are going through a meaningful transition or decision. The concierge app was the test case, but the underlying principle is broadly applicable. ## Related Articles [![We Are Affective](https://weareaffective.com/hubfs/we_are_affective_logo_mark.svg)](https://weareaffective.com) 20-22 Wenlock Road London, N1 7GU United Kingdom +44 20 4572 8062 [hello@weareaffective.com](mailto:hello@weareaffective.com) Services [App planning & strategy](https://weareaffective.com/app-planning-strategy) [App design](https://weareaffective.com/app-design-agency) [App UX design](https://weareaffective.com/app-ux-design) [App UI design](https://weareaffective.com/app-ui-design) [App technical architecture](https://weareaffective.com/app-architecture) [Existing app audits](https://weareaffective.com/app-audit) Legal [Privacy policy](https://app.termly.io/policy-viewer/policy.html?policyUUID=b8fa9921-7518-4fb5-8ddd-9dc7f5977ed2) [Terms](https://app.termly.io/policy-viewer/policy.html?policyUUID=8b6a6ad5-91bd-4176-a5f7-6d36b0398f70) Case studies [TravAI](https://weareaffective.com/case-studies/travai) [Meditech](https://weareaffective.com/case-studies/harley) [WorkingWeight](https://weareaffective.com/case-studies/workingweight) [SkinSync](https://weareaffective.com/case-studies/skinsync) [Three Lochs](https://weareaffective.com/case-studies/three-lochs) [Drift](https://weareaffective.com/case-studies/drift) About us [Our Story](https://weareaffective.com/about) [How We Work](https://weareaffective.com/how-we-work) Guides [Creating an app](https://weareaffective.com/how-to-create-an-app) [Building an MVP](https://weareaffective.com/building-an-mvp) [Cost and budgeting](https://weareaffective.com/app-development-cost) [App technology](https://weareaffective.com/app-development) [Planning and strategy](https://weareaffective.com/app-planning-strategy) [User research](https://weareaffective.com/app-user-research) [Onboarding design](https://weareaffective.com/app-onboarding-design) [User psychology](https://weareaffective.com/user-psychology-app-design) [Launch and growth](https://weareaffective.com/app-launch-growth) Copyright © 2026, weareaffective.com. All rights reserved.