1. Client Information

We use these details to identify the customer, confirm the primary website, and know who may approve business, content, and technical integration decisions during setup.

2. Website & Hosting Environment

We need this information to choose the correct installation method, determine where the AI Engineer application and its database will run, and identify technical restrictions that could block the chatbox, APIs, scripts, or customer-hosted components.

Website platform / CMS

Installation location

3. Appearance & Branding

These details allow us to match AI Engineer to your corporate identity and define how users will see and open the chat interface on your website.

Display mode

Chat presentation

4. Languages

We use this information to configure browser-language detection, internal translation, answer language, and protected technical terminology so product names and engineering terms remain accurate.

Language options

5. Whitelisted Knowledge Sources

AI Engineer should search only information that your company has approved. Please list every website or domain that may be used as a trusted web source. Websites not included on this whitelist will not be treated as approved company knowledge.

Whitelist rule: only websites explicitly listed here are approved web knowledge sources. Add all corporate sites, brand sites, document portals, distributor locators, or other web properties that AI Engineer is allowed to search.

Approved source types

6. Q&A Database

Approved Q&A can provide immediate, consistent answers to recurring questions. We need to know what approved material already exists, how it is supplied, who approves it, and the confidence threshold required before an existing answer is reused.

Existing approved Q&A

7. Products & Brands

This defines the products AI Engineer is expected to recognize and discuss. It also establishes whether model names, competitor products, comparisons, and discontinued products may appear in answers.

Product rules

8. Engineering Scope

We use this section to define what engineering work AI Engineer is permitted to support and which technical disciplines may be required when interpreting an application or routing a question to the correct expert logic.

Required engineering disciplines

9. Required Application Questions

These requirements tell AI Engineer which application data must be collected before giving a reliable technical answer. Information already supplied in the question, an uploaded attachment, approved Q&A, or approved knowledge should not be requested again.

10. Answer Rules

This section controls which sources may contribute to an answer, how detailed responses should be, and any company-specific wording, validation, citation, or response rules that must always be followed.

AI Engineer may use

Preferred answer level

11. Restricted / Escalated Questions

We need to know which subjects must not receive a normal automated answer. These settings define when AI Engineer should stop, limit its response, or direct the user to an authorized person or department.

12. Documents, Downloads & PDF

This determines which supporting documents may be shown with an answer, how many related files or links should appear, and whether users may generate a branded PDF of the technical response.

13. Distributor / Supplier Routing

If answers should identify a local supplier or distributor, we need the approved data source and location method. These rules also determine how multiple brands and shared distributors are presented without duplicate supplier entries.

14. User Registration & CRM

We use this information to configure which user details are collected, whether verification is required, when usage limits apply, and whether qualified interactions should create or route leads into your CRM.

15. API Configuration

AI Engineer may use external AI services for defined processing steps. We need to know which providers are approved, who owns the API accounts and billing, the permitted budget, and any corporate security restrictions on external processing.

16. Data Storage & Privacy

This section defines what information may be stored, where persistent data must reside, how long it may be retained, and what privacy or deletion requirements must be built into the customer installation.

17. Administration & Acceptance

We need to know who will administer the system, which controls they require, and which functions must be tested and accepted before go-live. This creates a clear handover and acceptance basis for the finished installation.

18. Additional Information

Use this section for requirements, constraints, workflows, integrations, terminology, or approval rules that are important to your organization but are not covered elsewhere in the form.