AI Employee
Understand customer mail. Check delivery records. Prepare a reply for approval. We are developing the AI Employee for this supported workflow – currently a local prototype with synthetic data, with no customer operation yet.
What you get for the price
The scope is described deliberately precisely. That way you can see before enquiring what is included and where an extension begins.
- Agree on a budget plan: case limits, AI usage, billing and a stop rule in writing before starting.
- Proposed scope: one delivery-status procedure, one customer mailbox, one read-only CRM/ERP source and one model provider. Agree on specific products and interfaces first.
- Proposed setup: agree on workflow, data mapping, permissions and reply templates; configure and verify each of the three connections separately.
- A responsible person reviews and approves every reply. Sending requires acceptance of the real mailbox connection.
- Support within an agreed scope: review errors, agree on changes and assess results together. Response times and case volume must be specified in writing.
Development status · 17 October 2026
Locally tested. Customer pilot still pending.
V31 is a local synthetic pilot using fictional data. Real test accounts and provider, customer, legal and production acceptance are still missing. The overall system is not release-ready.
Individual checks have passed. Overall validation and further business-process evidence remain open. A customer pilot can start only after these and the required external acceptance steps are complete.
Example: Where is my order?
Fictional example of the intended limited customer pilot. This does not establish a connected customer mailbox.
- 01
Receive an email
A delivery enquiry is assigned to a case. This requires a separately configured and verified mailbox input.
- 02
Read and match records
Match the customer and order against the approved CRM/ERP source. Missing or ambiguous details require a person to take over.
- 03
Prepare a reply
Draft a reply from the evidenced delivery status. No invented delivery date; sources and open questions remain visible for review.
- 04
Approve individually
A responsible person checks the recipient, facts and wording for this specific reply. They can correct or reject it.
- 05
Send after approval
Sending requires a real, verified mailbox connection and confirmed approval. Without it the reply stays a draft; sending errors need resolution.
Three connections, more than an API key
The customer mailbox, read-only CRM/ERP and model provider each require separate configuration and acceptance. Providers, permissions, data mapping, budget and failure handling belong in the agreed scope. An interface template alone does not establish a connection.
Who this package is for
For teams with recurring delivery enquiries, clear data sources and a person responsible for approval.
- Recurring delivery questions with an unambiguous customer and order reference.
- Teams that want to check replies against source records and approve each send.
- Businesses able to provide test access, a process owner and time for a limited pilot review.
How it works
Agree on scope
Specify one procedure, systems, case volume, responsibilities and budget in writing. Start with synthetic examples.
Validate connections
Configure mailbox, read-only CRM/ERP and model provider separately and verify them in real test accounts. Resolve privacy, contract and operating requirements.
Run a limited pilot
Start only after the required approvals. Approve every reply individually; measure errors, rework, costs and value. Decide on production release separately.
Deliberately not included
These boundaries prevent unexpected extra costs and make the package price easy to follow.
- No immediately available customer access: separate real test accounts and provider, customer, legal and production acceptance are still missing.
- No autonomous bookings, credit notes, cancellations or master-data changes in the proposed entry scope.
- No guaranteed time savings, completion rate or legal compliance. Value must be measured in a limited customer pilot.
- No unlimited usage or guaranteed round-the-clock support.
Useful extensions
Only if it suits your project – extensions are clearly stated before any work starts.
- Additional support and specific response times subject to scope and agreement.
- Additional mailboxes, data sources and procedures require their own scope, estimate and acceptance criteria.
- Write access and additional sending routes require separate technical and business validation.
Frequently asked questions
What has actually been verified?
A local prototype using fictional data with passing individual checks. Overall validation is not yet complete. Real test accounts and provider, customer, legal and production acceptance are still pending. The product is not yet released for customer operation.
Is an API key enough?
No. The customer mailbox, read-only CRM/ERP and model provider are three separate connections. Each needs account, permission, data mapping, failure-case and actual outcome checks. A template does not establish an operational connection.
When is an email sent?
In the proposed pilot, only after individual approval and through a real, verified mailbox connection. Without that connection the reply remains a draft. Ambiguous matches require manual clarification.
Who is the offer for?
This proposed pilot offer applies to the first 50 customers. Scope, case limits, support and contract terms must be agreed in writing before starting. No remaining-place count is stated. Setup is additional; customer release has not yet been accepted.
How are usage and extra costs handled?
Third-party licences and AI usage are additional. Agree on providers, billing, monthly budget, case limits and a stop rule before starting. Billing follows documented usage or provider rates; budget increases require prior approval. No unlimited usage.
Does this package fit your project?
Send a short enquiry. The package is already selected, so we can talk about the right scope straight away.
Enquire about AI Employee