You shipped it. It works. Tickets are resolving. So why are customers leaving?

Gladly's 2026 Customer Expectations Report uncovered a gap that most CIOs don't see until it's too late: 88% of customers get their issues resolved through AI — but only 22% prefer that company afterward. Resolution without loyalty is just churn on a delay.

The difference isn't the model. It's the architecture. How AI is integrated into the customer journey, what it hands off and when, and whether the system is designed to build relationships or just close tickets.

Download the report to see what consumers actually expect from AI-powered service — and what the data says about the platforms getting it right.

If you're responsible for the infrastructure, you're responsible for the outcome.

Get the data

AWS quietly updated the terms for WorkSpaces AI features, and if you're using any of them for client work or proprietary development, your content is now training their models unless you've configured an opt-out.

The terms are explicit: when you use any WorkSpaces functionality identified as AI-powered, AWS can use that content to develop and improve their models. That's not buried in a footnote — it's in section 1.24 of the AWS Service Terms, which was updated to add WorkSpaces to a growing list of services operating under this framework.

WorkSpaces was added to the list of AWS services whose AI features are powered by Amazon Bedrock — and that matters because Bedrock-powered features come with a default data use agreement. Your content goes toward model improvement unless you configure an AI services opt-out policy through AWS Organizations.

The opt-out process is not a simple toggle. To stop AWS from using your WorkSpaces content for training, you need to: enable AI opt-out policies in AWS Organizations (a separate step from just having an org), craft a custom JSON policy document, and attach it. Three manual steps — and there's no dashboard confirmation that your policy is actually working once it's in place.

This is the third significant cloud platform in 2026 to extend AI training rights to workspace content by default. GitHub Copilot began using interaction data for training earlier this year (opt-out available for Free, Pro, and Pro+ users; excluded by default for Business and Enterprise). Microsoft 365 Copilot's terms follow a similar pattern. The move is consistent: vendors add AI features, those features collect training data, and the opt-out exists — but finding and configuring it requires deliberate effort most users never make.

AWS's opt-out mechanism has actually existed since 2023, but the addition of WorkSpaces to the covered services is the new development. If you set up an opt-out policy previously, it may already cover WorkSpaces depending on how your policy is scoped. Worth verifying.

If you're an agency, consultant, or solo founder running client work through Amazon WorkSpaces, review your AWS Organizations AI opt-out policy today. If you don't have one, set it up before your next WorkSpaces session. The compliance risk for NDA-covered work is real — and "I didn't know" isn't a defence your clients will accept.

Check your AWS Organizations settings and the AI services opt-out documentation linked below.

Trish @ StackDrift

StackDrift flagged this change today. Want vendor policy updates before they become your problem? Subscribe to Drift Intel for weekly roundups.