These answers are intentionally conservative about Meta requirements, WhatsApp setup, AI limitations, merchant responsibility, pricing review, and legal review gaps.
MerchantPilot is an AI WhatsApp commerce copilot for merchants. It helps businesses answer customer questions, recommend products, capture orders, manage customer conversations, and run broadcasts while keeping the merchant in control.
MerchantPilot is not positioned as a generic chatbot builder. It is designed around merchant workflows such as products, FAQs, customer conversations, order capture, broadcasts, and operational visibility.
Yes. MerchantPilot is designed for WhatsApp-first merchant operations. Setup requirements depend on approved WhatsApp and Meta configuration for the merchant.
In many cases, WhatsApp setup depends on number eligibility, Meta account configuration, and whether the number can be connected through the required business setup.
MerchantPilot AI replies are grounded in merchant-managed products, FAQs, AI settings, and conversation context where available.
No AI system should be treated as perfect. Merchant data quality affects response quality, and merchants should keep products, FAQs, and operating rules accurate.
MerchantPilot can support order capture when a customer confirms buying intent, including selected product, customer information, delivery location, and order notes where supported.
MerchantPilot should not be marketed as automatically processing final payments unless the specific payment workflow is implemented and reviewed.
Final prices are not defined in the C2 content package. Prices, quotas, billing provider, taxes, accepted payment methods, and cancellation terms require dedicated billing and legal review before launch.
MerchantPilot is positioned for international merchants in supported regions. Public copy avoids assuming one country, currency, phone prefix, payment provider, delivery provider, or tax treatment.
MerchantPilot is designed as a multi-tenant platform where each business workspace must remain isolated. Public messaging reinforces separated merchant workspaces and business data.
Data deletion, export, and retention options should be described according to final product implementation and legal policy. Until finalized, contact support for account and data requests.