Setting Up Requests and Workflows
We set up what happens after a new request comes in. We move the form data to the right system, set up notifications, connect online booking, and link services together. Larger changes are broken into stages and carried out within the monthly scope.
What can be set up
We set up where a request goes and what happens next
We move the form data into a CRM, a spreadsheet, or another agreed system.
We set up a notification for the responsible person whenever a new request comes in.
We connect online booking along with the related notifications, if the business needs it.
We link services together wherever they allow the required data to be transferred securely.
Before starting, we determine what result is needed, which systems are involved, and what access and data are required. Larger setups are split into stages. This work runs within the monthly scope of Digital Komplett or Digital Komplett Plus. Paid plans for CRM, telephony, booking services, and other paid systems are billed separately. Below you can see the status of one such process setup as an example. The percentages show the progress of each stage.
Requests transferred without manual work
Notifications sent without manual work
Automatic assignment of requests
Data entered without manual work
Examples from our work
What we've already built for other companies
Want requests to be easier to handle?
Tell us what happens after a request comes in. We'll look at which steps can be linked together.
FAQ
Frequently asked questions about automation
Automating request handling links together steps that would otherwise be done by hand. A request from the website, for example, can be transferred into a CRM or spreadsheet, trigger a notification to the responsible person, and set off the next agreed step.
Yes, as long as the CRM supports a suitable connection method. Before setup, we check the technical capabilities, access, and data fields, then define which information should be transferred from the form to the CRM.
Yes. After a new request comes in, a notification can be set up for the responsible person, or another agreed scenario. The notification channel depends on which services the business uses and what they support technically.
Yes. A suitable booking service can be connected, along with the related steps and notifications. If the booking service is paid, its subscription is billed separately from the work done by Illia BizTech.
Whether an integration is possible depends on the specific system, its API, and the available connection methods. That's why, before starting work, we check the CRM, telephony, booking service, or other tool, and only then confirm how the data transfer will work.
The cost depends on the number of systems, the logic involved, and the scope of the setup. The work runs within the monthly scope of Digital Komplett or Digital Komplett Plus, and larger integrations are split into stages. Paid plans for external services are billed separately.
If the issue lies in a system we built or took over after review, it's covered by support. For a critical issue during business hours, the first response comes within four working hours — though that's not a guarantee the issue will be fully resolved within that time.
The current process needs to be described, the necessary access provided, and it needs to be defined which data should be transferred between systems. If the work involves sensitive data, we clarify how it will be processed and transferred before setup begins.
Illia BizTech sets up the transfer of requests and connects the website to CRM, forms, telephony, online booking, and other systems a business uses to stay in touch with customers. The task usually doesn't start with picking a new piece of software, but with the existing process: where a request comes from, where staff currently move the data, who should be notified, where customer data lives, and which steps after a request are still handled by hand. Individual steps can then be linked through existing integrations, APIs, webhooks, and other available ways of exchanging data. If a business is already using HubSpot, Pipedrive, Zoho CRM, Google Sheets, Make, Zapier, n8n, or another service, we first check its technical capabilities, access, and required fields. The name of the platform itself is not a limitation — what matters is whether the existing system offers a suitable way to connect and whether the desired scenario can be implemented reliably.
After a form on the website is submitted, a new request can, for example, automatically create an entry in the CRM, save the contact details and source of the request, assign it to the right person, and send the matching notification. In another setup, the website can be connected to online booking, a calendar, telephony, email, or an SMS service. If information is currently moved by hand between email, a spreadsheet, and a CRM, it's often possible to remove just that one step first, rather than changing how the whole business operates. For companies in Germany, this fits requests for services, consultations, on-site appointments, bookings, price inquiries, and similar cases. For larger projects, we split the process into sections in advance — form, data transfer, CRM, notifications, and testing. Access and working accounts stay with the client's company wherever possible. If a new system is added later, or the logic of handling requests changes, it can be connected as its own step once we've checked the technical possibilities and the available monthly volume.