Skip to content

AI Assistants

An AI assistant that guides your customers.

Help customers clarify their needs, compare products or services and take the next step. We connect approved company data, business rules and permitted integrations, with defined action and approval boundaries.

Neuropathic System — Store AI assistantIllustrative scenario · scripted animation, not a live assistant
Sara

Hi! I'm Sara, the store's assistant. I can help you choose and check availability. What are you looking for?

I need a coffee machine for our office. There are 10 of us.

Sara

Sure. Beans or capsules? And what budget do you have to start with?

Beans, up to €700.

Data from the store system · 2 matching products

Sara

I have two options for a 10-person office. Both grind fresh beans and have a large water tank.

Automatic coffee machine A

Ceramic grinder · 2.2 l tank

€649In stock

Automatic coffee machine B

Two bean hoppers · 2.5 l tank

€699Ships in 2 days

I'll take the first one. Can you prepare the order?

Sara

Done. I've prepared the cart. You confirm the order after reviewing the summary.

Cart awaiting your approval

1 item · €649

Review and confirm
Write a message…

The assistant proposes; company systems supply transaction data. The customer approves. This illustration does not create a cart or order.

Where it fits

Products, services and customer support.

We design assistants around a defined customer process: clarifying a need, comparing options and helping the customer take the next step. The scope is agreed for your business.

Product selection

Help customers compare catalog items, assemble compatible sets and review alternatives using approved product data.

Services and B2B

Collect requirements, help select a service or solution and prepare a qualified enquiry for your team.

Customer support

Use approved service knowledge to clarify a problem and suggest the next step, or pass the case to an employee.

Separate from the system for employees: a customer-facing assistant receives only the data and actions approved for its role, not internal employee permissions.

The customer journey

Clarify, compare, verify, then act.

The conversation is the interface. Product logic, company rules and permitted integrations determine what the assistant can offer and do.

  1. 01

    Clarify the need

    Ask for the requirements and constraints that matter to this choice, without collecting unrelated information.

  2. 02

    Compare suitable options

    Find products or services in approved sources, explain differences and identify missing information.

  3. 03

    Check business data

    Retrieve prices, availability and terms from the connected company systems. Missing or failed checks must not become invented answers.

  4. 04

    Confirm the next step

    Present the selection for review. Depending on the agreed integration, continue to a cart, enquiry or employee. Purchases and other consequential actions require the defined approval.

Architecture and boundaries

The language model is not the source of transaction data.

We separate conversation, product selection, business rules, authorized data sources and action execution. An integration does not grant unrestricted access.

A bounded domain does not eliminate model errors. We define evaluation cases, fallback behaviour and reviewable records for the agreed scope.

Core Logic
  • Conversation
  • Product and service logic
  • Company systems
  • Action control
  • Failure and handover
Explore the system architecture

Scope of implementation

Choose the capabilities the process needs.

These are implementation scopes, not a promise that every assistant performs transactions.

01

Knowledge assistant

Answers from approved company knowledge, with source references and a defined response when evidence is missing.

02

Product and sales assistant

Clarifies needs, compares options and helps select a product or service within your offer and rules.

03

Transactional assistant

Connects the conversation to permitted actions in company systems, subject to access checks, validation and approval.

Before launch

Define the data, permissions and evidence.

We begin with a bounded process and representative data. Integrations and acceptance criteria are agreed before implementation.

Approved domain

Specify the catalog, knowledge sources, supported questions and exclusions. The assistant does not answer as a general-purpose AI.

Data and actions

Agree any catalog, CRM, calendar, cart or API integration separately, including who may read or change each resource.

Evaluation and handover

Test selection quality, unsupported requests, stale data, unavailable integrations and approval requirements. Agree records and employee handover.

Often called sales chatbots, these systems are defined here by their process, data and action boundaries. Payment remains with the agreed store or payment system.

Which decision could you make easier for your customer?

Describe your offer, available data and the next step you want to support. We will agree on a suitable pilot and its boundaries.