Deployment & Integration Services
Configure BasisAssistant around a defined business use case, with the knowledge, response rules, and deployment channel your organization needs.
If you already know what the assistant needs to do and have the required data ready, you can move directly into deployment.
We define the project scope, prepare the required knowledge structure, and configure BasisAssistant around the approved requirements. After internal testing and customer acceptance testing, the assistant is launched on the agreed channel. A pilot is not a mandatory prerequisite for this service.
If the problem, use case, and core data are clear, a pilot is not a mandatory first step.
This service is designed for organizations that already know how the assistant will be used and have the information required to begin. In that situation, the project can move directly into project-scope definition and BasisAssistant configuration.
If the problem, data, or success criteria still need validation, a limited pilot may be a better first step before full deployment. The difference is project readiness: a pilot validates the use case; this service delivers an agreed deployment.
The core process starts with understanding the use case and continues through testing, training, launch, and initial monitoring.
The base package follows a defined framework, while implementation details can vary with the use case and the size of the organization. At the beginning of the project, we establish what the assistant is expected to do, which knowledge and rules it will use, and how the deployment will be evaluated.
BasisAssistant is then configured around those decisions. This keeps the project boundaries clear and separates the core deployment from new requests that fall outside the agreed project scope.
You do not need to migrate your existing website simply to start this service.
BasisAssistant can be deployed on one standard channel or across a combination of approved channels, depending on the project. If your current website stays in place, the assistant can be added without requiring a full website migration.
Deployment across multiple websites or domains can also be provided within the standard deployment framework. When a website widget or connection code is used, Manzoomeh Negaran handles its installation as part of this service.
Good configuration depends on reliable information and clear ownership on the customer side from the start.
Deployment is not only a technical task. Your organization needs to provide reliable sources, the required access, and the people responsible for project decisions so that the assistant’s knowledge, rules, and acceptance criteria are based on approved information.
Each stage produces the information or approval needed to move into the next one.
The project follows a staged process. We first review the business problem and organizational readiness. We then define the project scope and acceptance criteria before design and configuration begin. The assistant is tested internally and then reviewed by the customer before launch.
Define the problem, use case, and people responsible for the project.
Review the required knowledge sources, data, access, and other project inputs.
Define what will be delivered and how it will be approved.
Prepare the knowledge structure, response rules, conversation flow, roles, and required settings.
Review technical and content behavior before customer testing.
The customer reviews the agreed scenarios and acceptance criteria.
Train the responsible users on the relevant parts of the deployment.
Launch the assistant on the approved channel.
Review early operation and make corrections that fall within the agreed project scope.
Close the project against the approved project scope and acceptance criteria.
The customer provides the required information and approvals; Manzoomeh Negaran carries out the agreed deployment work.
Responsibilities are separated from the beginning so both sides know which information and approvals must come from the customer and which activities are part of Manzoomeh Negaran’s implementation work.
Activating the assistant is not enough; the acceptance criteria for the project must first be reviewed.
Customer user acceptance testing is required before go-live. The assistant is considered ready for launch when the acceptance criteria relevant to the agreed project scope have been reviewed and accepted.
A separate written sign-off for go-live is not a universal requirement. However, the user acceptance testing outcome and the agreed acceptance criteria must be confirmed before launch.
A Human Handoff path and other work outside the base package are included only when they have been defined under a separate project scope or statement of work.
Work outside the base project scope is reviewed, defined, and priced separately.
The base package on this page is designed for configuring and deploying BasisAssistant. Some requirements are project-specific or development-specific and are therefore handled separately rather than being automatically included.
The BasisAssistant subscription is also separate from the development and deployment fee. Integration, custom development, and long-term support are priced separately. No fixed project price is stated on this page.
Item |
Status |
|---|---|
Base development and deployment package |
Included in the standard scope |
Initial training |
Included in the standard scope |
Initial monitoring and corrections |
Included in the standard scope |
Human Handoff flow design |
Separate statement of work |
Additional training |
Separate from the base package |
Custom documentation |
Separate from the base package |
Integration |
Separate from the base package |
Custom development |
Separate from the base package |
Long-term support |
Separate service or package |
BasisAssistant subscription |
Separate from the development and deployment fee |
New work outside the agreed project scope |
Change request with separate pricing |
Project timing depends on the actual project scope, available resources, and deployment conditions.
A fixed public delivery timeframe is not stated for this service. The implementation timeline is defined after reviewing the project scope, available resources, deployment channels, and integration requirements.
Data readiness, required access, and customer participation can also affect the schedule.
Initial monitoring and support after go-live are included in the standard package. Long-term support is provided separately. No general public service-level agreement (SLA) is stated for this service; support terms and any applicable service levels are defined in the project scope or contract.
The quality of the outcome depends on reliable sources, a clear project scope, and active participation from both sides.
A custom assistant is more dependable when it works with reliable knowledge, clear rules, and a defined area of responsibility. For that reason, this service is delivered within clear project boundaries.
No. If the use case and required data are already defined and ready, you can move directly into the development and deployment service. A pilot is useful when the problem, data, or success criteria still need limited validation.
No. This service is for configuring and deploying BasisAssistant around a defined customer use case. Custom development or new product capabilities are not part of the base package and are reviewed separately.
No. Website migration is not a general requirement for this service. BasisAssistant can be deployed on your existing website. Standard deployment options also include a website widget, dedicated link, subdomain, standalone chat page, or internal panel.
Yes. Deployment across multiple websites or domains can be provided within the standard deployment framework. The required channels are defined in the project scope.
No. Designing the Human Handoff path is handled under a separate statement of work. If it is added to the project, the relevant testing criteria and deliverables are defined as part of that work.
No. Integration is outside the base package and is reviewed separately. Whether a connection can be implemented also depends on valid API access and the technical access available for the target system.
A fixed public delivery timeframe is not stated for this service. The implementation timeline is defined after reviewing the project scope, available resources, deployment channels, and integration requirements.
No. The BasisAssistant subscription is separate from the development and deployment fee. Integration, custom development, and long-term support are also priced separately.
Initial monitoring and support after go-live are included in the standard package. Long-term support is provided separately. Any applicable service-level commitments are defined in the project scope or contract.
Healthcare, legal, financial, and human resources use cases are only offered after assessment and project-scope definition. In these areas, the assistant does not replace professional human judgment.
Before deciding on deployment, open Manzoomeh Negaran's AI chat and see a sample of the type of interaction a custom assistant can provide.
View a Sample AssistantSee a sample assistant conversation and get a clearer sense of the type of interaction this service is designed to configure and deploy.
