Integration Directory

This path is for scenarios where lead or customer information needs to be recorded and carried forward inside the Integrated CRM in BasisPanel. The CRM capability is active and public, and it can support customer and sales processes within BasisPanel.

Migration from an existing CRM is a separate service delivered after assessment and a defined SOW. Ongoing synchronization with an existing CRM is also treated as Custom work within a defined SOW.

No third-party CRM or connector is currently approved for public listing as a Ready connector. The directory therefore does not name an external CRM as prebuilt or guaranteed.

The core connection between BasisAssistant and the Ticketing module in BasisPanel is already available. For a live use case, intent, ticket schema, fields, routing rules, roles, and workflow are configured around the customer scenario rather than rebuilding the connection from zero.

Tickets can be created, categorized, routed, and followed up within the rules and data structure defined for the scenario. Access to ticket information remains role-based.

A Ready path here does not mean there is a prebuilt connector for every third-party ticketing product. Requirements outside standard configuration are reviewed as a separate technical scope.

The approved connection is between BasisAssistant and the internal Workflow Engine used in the Manzoomeh ecosystem. Within a designed workflow and permitted access scope, BasisAssistant can trigger defined actions and receive workflow status or results.

This path is available in Enterprise plans. The Workflow Engine must be active, the relevant workflow must already be designed, and the required roles and access levels must be in place.

This Ready status applies to the internal Workflow Engine. A prebuilt public connection to external BPMS products is not part of this page scope.

Two standard deployment methods are approved for this path: an assistant Widget on a website and a Dedicated Assistant Page.

The Widget is installed with a dedicated embed code on any website that can run JavaScript or embed code. It may run on an authorized domain or subdomain. A subdomain is therefore a location where the Widget can run, not a separate deployment method.

The Dedicated Assistant Page is hosted on Manzoomeh infrastructure. Direct API connection is a separate technical integration path and is not presented as a third standard website deployment method.

The primary Ready destination is the Task/Project module inside BasisPanel. Within the user’s permitted role and project scope, the assistant can work with tasks, retrieve status, and use project information according to the defined schema and policies.

This capability is delivered as an Add-on. BasisAssistant and the Task/Project module must be active, and the project, roles, permissions, and required schemas need to be prepared.

The assistant does not autonomously choose deadlines or priorities without an explicit input or defined system rule. External task or project systems are handled as project-based integrations through the destination API after technical compatibility review.

API and Webhook capabilities are available for supported customer scenarios. APIs can be used to exchange approved data and execute permitted operations in BasisPanel, while webhooks can send supported events to another system when a defined event occurs.

Access depends on an active Workspace, an eligible plan, an authorized technical or management role, valid credentials, and technical approval where required. Documentation and test access are controlled rather than assumed to be public and anonymous.

Public fixed limits for request volume, payload size, event count, or endpoint count are not stated on this page. Deeper or bespoke third-party integrations may require a separate technical review, mapping, and project scope.