CX Guidelines Update: Authentication and Consent Changes

🚀 Updated CX Artefacts and Requirements for Authorise 🚀 🗓️ 24 September 2025 We’ve just released updated CX artefacts and requirements for Authorisation to disclose https://lnkd.in/gDRb-XDq and Amending authorisation https://lnkd.in/gWDSfJtB These updates reflect the latest work across several key consultations and change requests: 📘 Consultation Drafts 🔹CD367: March 2025 Rules – Draft Standards https://lnkd.in/gsP65kxc 🔹CD369: Redirect to App – Draft Standards https://lnkd.in/g-gSB4x9 🛠️ Change Requests 🔹CR693: CX Guidelines | Historical date ranges for Authorisations https://lnkd.in/gKRXQHyq 🔹CR700: CX Guidelines | Redirect to App (R2A) CX Guidelines Changes https://lnkd.in/gpfwqC9q 🔹CR701: CX Guidelines | Data Language Standards changes stemming from CD367 https://lnkd.in/gPgEyJwj 🔹CR702: CX Guidelines | Required and voluntary data – Authorisation https://lnkd.in/gHJ6gXy2

❓Have you ever just stopped using a product without complaining?   - You abandon a mobile app after a clunky update, but never leave feedback. - You switch your internet provider after slow speeds, without warning them. - In chat queues, customers silently drop off rather than wait — no ticket, no trace. - Research shows this “silent abandonment” hides the real volume of customer loss.   👉 For CX pros, this means churn often happens invisibly — not in surveys, but in silence.   Frame This: The most dangerous churn is the one you never hear about.   Proactively tracking usage patterns, wait times, and drop-offs gives a clearer view than feedback alone. Because silence doesn’t mean satisfaction — it often means goodbye.

❓Have you ever just stopped using a product without complaining? - You abandon a mobile app after a clunky update, but never leave feedback. - You switch your internet provider after slow speeds, without warning them. - In chat queues, customers silently drop off rather than wait — no ticket, no trace. - Research shows this “silent abandonment” hides the real volume of customer loss. 👉 For CX pros, this means churn often happens invisibly — not in surveys, but in silence. Frame This: The most dangerous churn is the one you never hear about. Proactively tracking usage patterns, wait times, and drop-offs gives a clearer view than feedback alone. Because silence doesn’t mean satisfaction — it often means goodbye.

🚀💡 Can New Technology Drive Higher Customer Satisfaction Levels? 💡🚀 Absolutely! New technology can significantly enhance customer satisfaction by improving the speed, quality, and accessibility of services. For example, AI chatbots can provide instant customer support 24/7, reducing wait times and increasing responsiveness. Personalization algorithms can tailor recommendations and content to individual preferences, enhancing the user experience. Mobile apps streamline transactions, making purchases and interactions convenient. Each technological advance helps companies understand and meet customer needs more effectively, leading to increased satisfaction and loyalty. 🚀 Free Session 👉 http://tinyurl.com/PC-FREE #CustomerSatisfaction #TechInnovation #BusinessGrowth

Retail is evolving rapidly. Customers expect faster service, personalized recommendations, and seamless experiences — while store associates need tools that simplify their work, reduce errors, and speed up operations. A Chat Agent in the #Dynamics365 Store Commerce App makes this possible. By embedding a conversational interface directly into the #POS system, store associates can interact using natural language, just like chatting with a colleague. Microsoft Senior R&D Solution Architect Srinath Sundaresan walks through a sample implementation using React, TypeScript, and Commerce Runtime, showing how you can bring AI-powered conversations to your store environment. Check it out today: https://lnkd.in/ghw9RKNf #StoreCommerce #AgenticAI #FastTrack #MsDyn365

One survey response, but it highlights common pain points we see across public Level 2 and DC fast charging: 1️⃣ If your network requires an app download to start a charge, you’re going to frustrate drivers. A failed login or account setup = a failed session. At ChargeMate, when drivers are given a choice, they use a web-based checkout over a native app 3:1. 2️⃣ Drivers are reluctant to call support. It feels effortful, they don’t want to wait on hold, and often a charging stop is optional -- so they just leave. That’s why we see up to 5x higher engagement with AI chat support compared to calling and talking to voice assistants or humans. Both #1 and #2 lead to churn, negative reviews, and lost revenue. But solutions don’t have to be complicated -- a card reader with secondary "scan-to-pay" guest checkout experience offers drivers an easy and secure way to start charging.

🚀 Big News for App Builders & Businesses! InstaCódigo is excited to announce our new integration with Retently (formerly Promoter.io)! 🎉 Now, collecting and acting on customer feedback has never been easier. Automatically trigger surveys based on user behavior, get real-time insights, and turn feedback into data-driven decisions that boost satisfaction and retention. 💡 Why it matters: Automate feedback collection Gain instant visibility into trends Optimize products & services Streamline workflows Whether you’re scaling your app or improving your service, this integration helps you understand your customers better and act faster. 👉 Read more: https://lnkd.in/dFkGM-9U #InstaCódigo #Retently #CustomerFeedback #NPS #CX #AppGrowth #Automation #DataDriven #TechIntegration

One problem I see a lot in real-time mobile apps is not what you track, it’s how you track it. Poor location update strategies (high-frequency updates + high accuracy by default) turn “real-time” into “battery drain + angry users.” Why it matters • Users uninstall or disable features when your app kills the battery. • Servers get flooded with noisy updates; analytics and billing become meaningless. • Token/network failures during background sync lead to lost data and confusing UX. A real example from my work at Omzfield: we shipped a real-time location feature and initially sent every tiny position update to the server, users complained about battery drain and crash reports rose. After tuning our approach we cut runtime and improved engagement. A pragmatic solution (what I actually do) 1. Pick the right accuracy, don’t default to “highest” unless you need meter-level precision. 2. Use timeInterval + distanceInterval to throttle updates (e.g., every 10s or every 25–50m). 3. Batch and compress updates on the client; send fewer, higher-quality points. 4. Use foreground services (Android) or background-fetch patterns only when needed. 5. Smooth on the server, merge bursts and ignore tiny jitter. 6. Gracefully handle auth: refresh tokens in axios interceptors so background syncs don’t fail silently. 7. Monitor and iterate: add lightweight telemetry (success/failure per update, battery impact). Why this works • Less churn: less battery use and fewer crashes. • Batching + server smoothing = clearer analytics and cheaper processing. • Resilient auth + retries = reliable background sync and better UX. If you build location-aware apps, try tuning accuracy + distance/time intervals before adding complexity. Small config changes often give big wins. Want the checklist I use when reviewing a real-time feature (accuracy, intervals, batching, foreground handling, token resiliency)? Reply “checklist” and I’ll drop it here.

Every time we are engaged to develop a new app, portal, or automation, we encounter a common issue: the data is all over the place - Duplicate records - Broken IDs - Information scattered across systems While data work incurs costs, it's important to recognise that you will always pay for data quality; the timing and method may vary. Clean data simplifies processes, making everything cheaper, faster, and less painful. Its the necessary grunt work behind every successful app, product launch, or automation. Showoff were the data guys before it was cool - get in touch if you have a data problem 🤝