Knowledge base

You start in drafts-only mode, and you graduate to send after approval once you trust it.

Now, here's the part that changes everything, and that's the knowledge base.

So you can upload up to a hundred documents about how you run your business, your return policy, your shipping preferences, your reply rules, your product FAQs, your SKU guidelines, your SOPs, and then you attach them to any workflow.

So the workflows search those docs at runtime and act on your rules instead of generic Amazon answers.

Immediately obvious details on the pricing page.

One I was going to mention is it does call out that if you're using integrations like agent call or bedrock knowledge bases.

I was just going to ask about that.

Is that still a thing? Is it still something you need to do? But the reason I ask is because they're called out as separate costs, of course, because they're different services.

So the CX Designer has its own knowledge management or knowledge base area that is currently separate.

I think that most likely it will be brought together at some point so that it can use your existing knowledge bases, whether that's S3 or through one of the connectors, but at the moment it is separate.

Okay.

And agent core, again, so with the integrations What I was hoping was that my existing agent called gateways would be exposed within the CX designer, so they'd be easy to use.