Website, CRM, messengers and calendar work together.

An enquiry lands in the CRM, a message with the right person, a booking request is checked against the calendar, a reply is drafted.

Find what can be automated Write on WhatsApp

A price after a review of your process

One enquiry – three systems

Enquiry from the website“Repair needed by Friday”
AI sorts iturgent · repair
CRMtask created
Calendarfree: Tue, 10:00
Messengerdraft reply – for you to check

Example

4 scenariosexamples below – your process may differ
€0the first talk about your process
1 reviewdata, access rights, API limits
On requestthe price follows the review

Four scenarios

Examples, not a fixed list: the review shows what can be automated in your business.

	Starts with	The system	A person	Result
Website enquiry → CRM	A visitor sends the form	Creates a card with the topic and contact and notifies the person in charge	Calls or writes back	No enquiry gets lost in the inbox
Message → the right person	An e-mail or a messenger message	The AI recognises the topic and urgency and passes it on	Answers; sorts out unclear cases	What is urgent is seen at once
Booking request → calendar	A customer asks for a time	Checks the request against the calendar and offers free slots	Confirms the booking, where agreed	Less back and forth about times
E-mail → draft reply	An incoming e-mail or request for a quote	The AI drafts the reply or the quote	Checks it and sends it	Nothing goes out unchecked

What you get

A review of your process: Which data is needed, who has which rights, what the APIs of your systems allow and where the process has exceptions.
Scenarios that run by themselves: Each shows what starts it, what the system does and what stays with a person.
No enquiry lost when something fails: If the CRM or the mailbox does not answer, the enquiry waits in a queue and is sent again; the person in charge is notified and can handle it by hand.
The AI prepares – a person decides: A reply or a quote goes to the customer only after your team has checked it, if you decide so.

How it works

First the review – then the price.

You
You show us how the process runs today
We
We review the processdata, access rights, API limits, where a person is needed
We
We send a proposalscope, deadline, price
You
You approve and grant access
We
We build and testincluding another system failing
You
You accept the work

You decide

Where it matters, the decision stays with a person.
Access rights are agreed before we start.
Your systems and data stay yours.

Price

On request

First we review the process – then we name the scope, the deadline and the price of building it. If the review itself is paid, we name its price before it starts.

Find what can be automated

In the quote before we start

What exactly will be done
The deadline
The price
What it does not include

Priced separately

Licences of your systems
Support after launch
Changes when the process changes

Questions before you buy

Where does the work start?

With a free talk about your process. Then the review: how the process runs, which systems take part and where a person is needed. If the review is paid, we name its scope and price beforehand.

Will it fit our CRM?

That depends on its API, rights and limits. We find out in the review – before the proposal; we do not promise in advance that it fits any CRM.

Will the AI answer customers by itself?

Only where you have allowed it. Draft replies and proposals are checked by a person.

What if a system does not answer?

The enquiry is not lost: it waits in a queue and is sent again; the person in charge is notified and can handle it by hand.

What if the process changes?

We adjust it – as a one-off task or under a support contract.

Shall we talk about your process?

Tell us which task you want to solve. We suggest a fitting first step and explain what the price is made of.