Keep your company moving.
Even when you are not.

It connects multiple steps across your company, such as intake, planning, administration, follow-ups and reporting. The goal is one controlled process, not just a standalone chatbot.

No. A chatbot can be one part of the solution, but the system can also connect forms, email, calendars, CRM, documents, tasks, dashboards and existing business software.

Automation can absorb repetitive workload that is otherwise spread across one or more roles. The exact impact differs by company. We focus on released capacity, fewer errors and better follow-up, while important decisions remain human-controlled.

Examples include lead follow-up, customer service, appointments, planning, tasks, documents, reminders, quotation preparation, administrative preparation and management reporting.

Not by default. Useful existing systems are preferably retained and connected. We only recommend an alternative when a system is technically blocking, unsafe or structurally too limited.

Usually within two to six weeks. Timing depends on scope, data quality, API availability, access to systems and the speed of feedback.

A defined base implementation with a process assessment, up to three primary workflows, up to five standard integrations, testing, dashboarding, documentation, training and thirty days of aftercare. Deviations are quoted in advance.

Build and management of an agreed base environment, monitoring of critical workflows, periodic optimisation and small changes within scope. The subscription is not an unlimited development agreement.

The first phase includes analysis, configuration, development and testing. The term spreads that investment and provides enough time to operate and improve the workflows responsibly.

Not by default. External licences, model usage, messaging, hosting and API consumption are specified in advance and paid separately or contracted directly by the client.

For a one-time implementation, you receive the agreed custom configurations and documentation after full payment. External platforms, open-source components and licences remain subject to their own terms. Generic KocaExpress platform components are transferred only when explicitly agreed.

Not for high-impact actions. Payments, contracts, price deviations, sensitive communications and data deletion require human approval or are blocked.

Critical workflows receive error detection, logging and alerts. Depending on the process, execution is paused, retried safely or handed to an employee.

No system is automatically GDPR-compliant. We configure data use, access rights and vendor choices with GDPR in mind. The client remains responsible for its legal basis, privacy notices and internal procedures.

That depends on the selected vendor and configuration. Where possible, we select business services where training use can be restricted or disabled. The chosen data flows are documented before implementation.

No. We do not provide general revenue or savings guarantees. We prepare a grounded scenario based on hours, volumes, costs and the realistically automatable part of the process.

Yes. A limited pilot is often the safest route. After a successful first workflow, the system can be expanded in stages.

After the minimum term, the package can be ended according to the agreed notice period. Exit, handover and any exports are defined contractually in advance.

No. You mainly need to know how the business process should work, who makes decisions and which exceptions occur. We handle the technical configuration and handover.