What the current Concierge does
The current ARUX Concierge uses local JavaScript rules and a service knowledge map to answer common questions, suggest pages, explain indicative pricing, provide basic troubleshooting steps, and prepare a conversation for optional hand-off to the contact form. It is not currently connected to a live generative AI model, a CRM, a booking calendar, email inbox, Razorpay merchant records or other private systems.
What it cannot do
- It cannot verify a payment, issue a refund, move money, edit a checkout, or guarantee a booking.
- It cannot access a customer account, inspect private data or resolve an external provider’s issue on its own.
- It cannot guarantee legal, medical, financial, advertising, ranking, sales or campaign outcomes.
- It does not replace a human review of proposals, contracts, regulated claims or consequential decisions.
How conversation sharing works
Chat content stays in the active browser page unless the visitor chooses “Share this conversation with ARUX”. The selected conversation is passed through temporary session storage to the contact form so the visitor can review and edit it. The contact form must then be completed and submitted with consent before the information is routed to the ARUX email address through the configured form service. Do not enter credentials, payment secrets or sensitive personal data.
Future AI or agent connections
If ARUX connects a hosted AI model, email, scheduling system, CRM or payment API in future, the site owner must first implement a secure server-side service, authentication, access controls, abuse protection, retention rules and an updated privacy notice. API secrets must not be placed in front-end JavaScript. Visitors should be told which provider receives data, the purposes, and whether conversations are retained or used for model training, to the extent known and required by law.
Human support and escalation
For an unresolved issue, use the contact form or email aruxcollections@gmail.com. For payment concerns, supply only the payment/order reference, amount/currency and date—never the full card number, CVV, password or OTP. ARUX should verify payment records through the merchant dashboard before confirming outcomes.
Limits and errors
The assistant may misunderstand ambiguous questions or give incomplete route suggestions. Verify prices, availability, legal obligations, payment status and project terms against the relevant published page, checkout and written confirmation. The site owner should monitor responses and update the knowledge guide when the service or terms change.
Updates
This statement must be updated before enabling a new AI provider or connecting any private data system. Last reviewed: 18 October 2026. Questions: aruxcollections@gmail.com.
Related policies
For an enquiry, email aruxcollections@gmail.com or use the project/contact form.