Consent-Aware Family Engagement in Aged Care with Dynamics 365 Customer Insights

Aged care providers carry a distinctive communication burden. Families expect timely, accurate updates about their loved ones, while residents retain the right to control who receives information about their care and how they are contacted. Meeting both expectations at once requires a communication platform that treats consent as a first-class concept rather than an afterthought, and that can coordinate messages across email, SMS, and other channels without losing track of who has agreed to what. Dynamics 365 Customer Insights, and specifically its Journeys capability, offers a Microsoft-native way to orchestrate these interactions while keeping consent and privacy obligations at the centre of the design.

This article examines how aged care organisations can apply journey orchestration and consent management to improve family and resident engagement. It is written for the technical architects and service leaders who must translate regulatory expectations into working systems. The focus throughout is on practical patterns that respect the privacy obligations Australian providers operate under, rather than on marketing outcomes or generic engagement theory.

Why consent must anchor family communication

In aged care, the person receiving a message is often not the person whose information is being shared. A resident may nominate one family member as a primary contact, restrict updates from another relative, and consent to clinical information being shared with a substitute decision-maker but not with the wider family. These relationships change over time, and they must be recorded, honoured, and auditable. Treating consent as a static tick box at intake fails to capture this reality and exposes providers to complaints, regulatory scrutiny, and loss of family trust.

Australian providers work within obligations set by the Privacy Act 1988 and its Australian Privacy Principles, alongside the standards administered under the aged care regulatory framework. These require that personal and sensitive information is collected and used only for purposes the individual has agreed to, and that people can understand and revoke their consent. A communication system that cannot demonstrate the lawful basis for each message it sends creates operational and reputational risk. Anchoring family engagement in explicit, revocable consent is therefore not merely good practice but a condition of operating responsibly.

How Customer Insights journeys support consent-aware orchestration

Dynamics 365 Customer Insights Journeys allows organisations to design communication flows that respond to real events and to the contact preferences held against each individual. Consent in the platform is expressed through compliance profiles and contact points, which capture whether a given email address or phone number may be used and for which topics. When a journey attempts to reach a family member, it can evaluate these settings and suppress messages where consent is absent or has been withdrawn. This means the same journey logic can serve many families while still respecting the specific permissions attached to each relationship.

The event-driven nature of journeys suits aged care communication patterns well. A change in a resident's care plan, an upcoming care conference, or a scheduled activity can trigger a tailored sequence of messages to the nominated contacts, using the channels each contact has approved. Because journeys branch on data and preferences, a provider can route clinical updates only to authorised decision-makers while sending general wellbeing news to a broader, separately consented audience. This separation of topics and audiences is where consent-aware orchestration delivers genuine value, because it lets providers communicate more often without communicating inappropriately.

Designing journeys that respect privacy and audit obligations

A sound design begins with a clear model of the relationships and permissions that govern each resident. Architects should map the roles that exist, such as primary contact, additional family contact, and substitute decision-maker, and define which topics each role may receive. These roles and their associated consents should be stored as structured data in Dataverse so that journeys can query them reliably and so that changes are captured with a full history. Recording who granted or revoked consent, when, and through what channel gives the organisation the evidence it needs to respond to enquiries and audits.

Equally important is designing for the moments when consent changes or is uncertain. Journeys should default to withholding a message when the relevant permission is missing rather than assuming agreement, and they should provide clear, accessible ways for recipients to update their preferences. Preference centres and unsubscribe handling built into Customer Insights can be configured to reflect the specific topics an organisation communicates about, giving families meaningful control rather than an all-or-nothing choice. Regular review of journey logic, message content, and consent records helps ensure that the system continues to reflect current obligations and the wishes of residents and their families.

Bringing it together within a Microsoft-native environment

Because Customer Insights sits within the broader Microsoft cloud, aged care providers can integrate engagement journeys with the systems that already hold resident and staff information, subject to appropriate access controls. Identity and access can be governed through Microsoft Entra, and data residency and security can be managed within the provider's existing tenant governance. This reduces the number of disconnected tools handling sensitive information and makes it easier to apply consistent security and privacy controls across the environment.

The wider benefit is a communication capability that scales with the organisation while keeping consent verifiable at every step. Families receive relevant, respectful updates through the channels they have approved, staff spend less time on manual outreach, and leaders gain confidence that engagement activity aligns with regulatory expectations. Providers considering this path should begin with a focused pilot around a single well-understood communication scenario, validate the consent model thoroughly, and expand only once the governance and audit practices have proven sound in operation.

References

• Consent management in Dynamics 365 Customer Insights - Journeys
• Australian Privacy Principles, Office of the Australian Information Commissioner