Clear answers about AT AI.

AT AI is a governed customer-assistance platform for commerce businesses. It combines a website assistant, approved business knowledge, conversation history and controlled reporting in one tenant-isolated system.

It is designed for commerce teams that want to improve product discovery and customer answers while maintaining clear control over data, actions and access.

AT AI is built around your approved sources, business permissions and operating model. It is designed to stay within defined boundaries rather than act as an unrestricted general-purpose assistant.

It can help visitors discover products, answer product-detail questions, explain approved policies and retain conversations for authorised review and reporting.

No. The initial commerce integration is intentionally read-only. Order changes, catalogue updates and other write operations are outside the first release.

It should clearly say when reliable information is unavailable and guide the visitor toward an approved next step or human contact.

The platform direction includes English, Hindi, Hinglish and Dutch. Language readiness is validated for each assistant before activation.

Answers are grounded in configured sources such as approved business knowledge and an authorised commerce product profile. Access remains scoped to the relevant tenant and department.

Your authorised team can maintain the approved source content. Updated or retired knowledge follows a controlled content lifecycle so the assistant uses the current source of truth.

No. Organisation, user, knowledge and conversation access is designed around tenant isolation, with additional department and role boundaries where configured.

Authorised users can review conversation history and configure bounded summary reporting. Delivery follows tenant and department access rules.

Raw transcripts are excluded from summary email by default. Reporting is designed to share useful insight without unnecessarily distributing sensitive conversation content.

Email recipients must be configured and verified. Delivery events are auditable, and access follows the same organisational permissions as the platform.

Role-based permissions, tenant boundaries and department scope determine what an authenticated user can access. Operational settings are versioned and managed through controlled workflows.

No. Voice recording remains off until appropriate legal policy, consent language and operational controls are approved.

The platform is designed for bounded retention, channel and usage settings. Final policies are agreed and validated before an external pilot.

A focused pilot includes a hosted website assistant, one approved Magento connection profile, agreed usage limits, direct onboarding and a structured feedback review.

The current design-partner pilot is planned for approximately four to six weeks, depending on integration readiness and agreed success measures.

A business owner, approved product and policy sources, clear customer use cases, and team members who can validate answers and participate in pilot reviews.

Contact AT AI to discuss your store, customer questions and desired outcome. We will confirm whether the current pilot is a good fit before any activation.