Good questions. Clear answers.

muwkl is a B2B AI agent platform in development. It is designed to connect customer conversations with approved information and authorized actions in existing business systems, with human oversight.

No technical background is needed to start a conversation with us. Bring one workflow and tell us where its information lives. We’ll discuss the setup with you; connecting a particular business system may involve its developer or provider.

We’re working towards the complete service through focused, assisted pilots. Share your workflow, systems and expected conversation volume so we can discuss availability, scope and pricing. There is no published price list or guaranteed launch date here.

The complete customer-facing service is still in development. The intended first onboarding model is assisted and developer-led, beginning with one bounded workflow and a supervised pilot. Pricing and launch timing have not been announced.

muwklWA is being built to bring your agent into customer conversations on WhatsApp. muwklMind is being built as a chat workspace for thinking, drafting and asking a chosen agent to take a connected action. They serve different moments: talking to your customers, and working with your agents.

Model selection is part of the muwklMind experience we’re building. The walkthrough uses generic model profiles to explain the interaction. Specific providers, models and their availability will depend on the workspace setup; this page does not announce a supported model catalog.

No. You can explore the interfaces, change a model profile and follow an agent’s steps using fictional conversations. The website walkthroughs do not send WhatsApp messages, call a model or change your business records.

We start by checking what your system can expose through an API or a supported adapter. Then we agree the exact reads and actions your agent needs. Each connection needs implementation and testing; naming a software category does not mean every product in it has a ready-made connector.

Bring a recurring customer request, the system that holds its live records, and any policies your team uses to answer it. Also decide who can approve changes and when a person should take over. You can describe these in ordinary business terms.

Arabic is central to the product’s direction, including language, interface and right-to-left layout. This website has complete Arabic and English versions. The language and terminology needed for your customer workflow should be reviewed during setup and testing.

Define its role, approved information and permitted operations. Reading a record and changing it are separate capabilities. Review any required approvals and the point for human involvement before widening the workflow.

An interrupted connection can leave the result unknown. Check the recorded state before retrying so a second attempt does not accidentally repeat the action. A successful-looking reply alone is not evidence that the business record changed.

Yes, human involvement is part of the workflow you define. Agree which requests need review, what the agent must leave to your team, and what context they need to continue. The exact handoff depends on the connected channel and setup.

No. Important protected facts and action confirmations are intended to use validated evidence, but free-form language can still contain mistakes. Source-backed information also depends on the quality of the underlying source.

The documentation describes the current development API contracts: authentication, agents, conversations, message identity and error handling. Use the environment and access supplied during setup. Start with a read request before connecting operations that change records.

Keep the workspace API key on your server. Your website or mobile app should talk to your own backend, which makes the authenticated request. Use a key with only the scopes and agent access the integration needs.

No. Message admission and completed work are different states. Use the conversation and turn records to inspect processing and outcomes. In particular, an HTTP 202 response does not confirm a completed business action or delivery to the customer.