AI Engineer Configuration

Configure AI Engineer Around Your Organisation.

AI Engineer is a fully configurable technical AI platform that can be integrated into virtually any website and adapted to your products, technical knowledge, customer journey, sales structure and support organisation.

Configure Your AI Engineer →
AI Engineer — Client Configuration +
Match your technical workflow
Control approved knowledge sources
Connect customers with the right expertise

Designed for Your Website Environment

AI Engineer is not limited to WordPress and is not simply a standard chatbot with different branding.

Any Website Platform

WordPress, TYPO3, Adobe Experience Manager, HubSpot, custom-developed websites and other enterprise web environments.

Corporate Integration

The interface can be configured around your existing branding, website structure and customer-facing experience.

Company-Specific Behaviour

The system can be adapted to your products, technical rules, sales structure, support organisation and internal workflows.

More Than Visual Customisation

AI Engineer can match your corporate identity while also adapting its technical behaviour to the way your organisation operates.

Brand & Interface

Logos, colours, typography, button styles, borders, corner shapes, dimensions and transparent or solid interface elements.

Desktop & Mobile

Responsive layouts, question and answer presentation, mobile behaviour, chat positioning and screen usage.

Customer Interaction

Help functions, contact options, technical guidance, support requests and human handover can all be configured.

Functionality Built Around Your Business

AI Engineer can be configured as a technical customer-guidance and support layer rather than a generic chatbot.

  • Technical product selection
  • Application engineering assistance
  • Troubleshooting
  • Product comparison
  • Customer qualification
  • Missing-information identification
  • Product and equipment identification
  • Technical document retrieval
  • Approved website searches
  • Manufacturer-specific knowledge
  • Distributor and supplier lookup
  • Regional sales routing
  • Human support requests
  • Technical enquiry handover
  • Product literature recommendations
  • Manufacturer video recommendations
  • Multilingual questions and answers
  • PDF generation
  • Frequently Asked Question databases
  • Knowledge retention from experienced personnel
The objective is not to install a generic chatbot. It is to configure an AI Engineer that reflects your products, technical knowledge, sales organisation, support structure and preferred customer journey.

Your Knowledge. Your Rules.

AI Engineer can operate with a controlled combination of approved information sources.

Digital Sources

Your website, approved external websites, product pages and other controlled manufacturer information.

Technical Documentation

Manuals, datasheets, application guides, installation instructions, maintenance documentation and technical literature.

Internal Knowledge

FAQs, selection data, training material and knowledge supplied by experienced application engineers and product specialists.

The available sources and rules governing their use can be defined specifically for your organisation. This allows AI Engineer to prioritise approved company knowledge rather than relying solely on unrestricted public AI information.

From Technical Question to the Right Action

AI Engineer can guide the customer through a structured technical process and determine what should happen next.

Understand

Clarify the application, equipment, operating conditions, objective and missing technical information.

Analyze

Use approved knowledge, engineering logic, structured information and company-specific rules.

Guide

Provide product guidance, troubleshooting support, technical information or recommended next actions.

Escalate

Route qualified enquiries to Sales, Application Engineering, Product Specialists or the appropriate distributor.

Integration With Your Organisation

The workflow adapts to your organisation rather than requiring your organisation to adapt to the software.

Technical & Commercial Routing

  • Route enquiries to Sales
  • Escalate complex applications to engineering
  • Identify the appropriate product specialist
  • Locate the nearest distributor
  • Direct customers to the correct department

Complete Context Handover

  • Forward the original question
  • Include the AI-generated answer
  • Include missing application information
  • Include uploaded files
  • Provide relevant technical documentation

Why the Intake Form Is Detailed

Every manufacturer, distributor and engineering organisation works differently. A serious technical AI implementation cannot therefore be configured from only a few generic questions.

Company & Technology

Company information, website platform, CMS environment, corporate branding, mobile behaviour and integration requirements.

Products & Knowledge

Products, brands, applications, documentation, approved sources, internal knowledge and manufacturer-specific information.

AI Behaviour

Required functions, missing-information rules, answer behaviour, languages, geographic requirements and escalation limits.

Sales & Support

Distributor structure, regional routing, sales contacts, human handover and application-engineering escalation.

Customer Experience

Question flow, technical guidance, contact options, PDF generation, reporting and user-interface requirements.

Company-Specific Functions

Additional workflows, integrations or technical functions unique to your products, markets and organisation.

Client Configuration

Configure Your AI Engineer

Complete the detailed configuration form below. The information provided will be used to define the required implementation and identify any areas that should be discussed before configuration begins.

Please provide as much information as possible.
Not every question will apply to every organisation. Leave non-applicable items blank where appropriate.

AI Engineer – Client Configuration Form

Please complete the information required to prepare your AI Engineer chatbox and website integration.

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.