Trust and safety

MerchantPilot is a preview beta built around merchant control, human oversight, and separated provider setup.

WhatsApp commerce involves customer conversations, product information, order details, broadcasts, and operational decisions. Public trust copy stays conservative until legal, provider, and launch reviews are complete.

Business isolation

Merchant workspaces must remain separate.

MerchantPilot is designed around separate business contexts for products, FAQs, conversations, orders, broadcasts, settings, and lead review.

Access should be limited to authorized users for the relevant business.
Operational states should support traceability and review.
Public lead forms do not create tenant workspaces or subscriptions.

Credential protection

Provider credentials must stay out of public copy and commits.

MerchantPilot should use dedicated MerchantPilot environment configuration for future provider setup. Secrets, tokens, Meta app details, webhook secrets, and payment keys must never be exposed in public pages or documentation.

Final privacy, retention, deletion, transfer, and data processing language requires legal review.

Human oversight

AI supports the merchant; it does not take final control.

MerchantPilot helps with repetitive answers, product recommendations, order capture, and follow-up context while merchants remain responsible for fulfillment, sensitive cases, and final decisions.

Responsible boundaries

No overclaiming in regulated or sensitive workflows.

MerchantPilot should not claim autonomous handling of payments, delivery, refunds, prescriptions, diagnosis, legal decisions, financial advice, or regulated approvals.

WhatsApp / Meta roadmap

Dedicated provider assets remain a cutover requirement.

Public copy does not claim Meta approval, partner status, live WABA activation, or reuse of Chioma provider assets. Live provider setup remains a separate approved slice.

MerchantPilot is provided by WORKNEX LIMITED.

For preview, access, safety, privacy, or company questions, contact the team before sharing sensitive operational details.