All questions

After the survey you say what you saw, in the van. The AI extracts items and dimensions, applies your pricing rules and sends a branded PDF quote to your phone in 3 minutes.

Photos and voice notes are captured offline and processed on upload. The worksheet gets done on site instead of in the evening.

From the survey data it calculates a material list and standard hours from your own norms and checks the purchase list against stock.

From the completed work, photos and test reports the AI assembles the handover pack and warranty letter, with deadline tracking.

Photo receipt booking and voice worksheets in 1–14 days, the voice-to-quote flow in 15–35.

Yes. Twenty minutes, no obligation. You leave with a written scope and a fixed price whether or not we end up working together.

A first working version usually goes live in two to three weeks. Larger systems are split into phases so something is running early and paying for the rest.

It stays in your systems. We connect to your tools with your own credentials, process data in the EU wherever possible, and sign an NDA and data processing agreement before we see anything.

Whatever you already use: Google Workspace, Microsoft 365, HubSpot, Pipedrive, Billingo, Számlázz.hu, Shopify, WooCommerce, Slack, WhatsApp and most things that have an API.

A fixed price for the build, then a monthly fee that covers hosting, monitoring and improvements. No hourly surprises.

No. We need someone who knows the process. We handle the technical side and train your team before go-live.

Each automation carries a typical range of hours saved per week for the people doing that work by hand, taken from the 2026 AI Automation Market Report: email handling 2–3 hours a day, invoice admin 6–12 hours a week, quoting 5–10 hours a week, scheduling 15–25% of working time. The configurator sums the midpoints; the discovery call replaces them with your real numbers.

We do not publish list prices. Every project gets a fixed price after the free 20-minute call, then a flat monthly fee for running it. No hourly billing.

They follow the report's 35-day roadmap: days 1–14 for cheap, visible quick wins such as missed-call text-back and the review funnel; days 15–35 for the automations that give back daily hours such as inbox triage and booking reminders; day 36 onward for larger systems such as voice agents, invoice processing and lead generation.

No. Tabs only group the catalog; you can tick items from any tab and filter by function or level across all of them. The AI treats the whole selection as one package.

You get a summary, a tier, phases with every selected item placed, suggested additions and a next step. You can copy the list, share a link that preselects the same items, or send it with your details from the contact form. Nothing is stored on our side beyond the request.

No, and it is configured not to. It answers hours, prices, address, parking and booking; anything clinical gets a callback from a person.

Calls are disclosed as AI, recordings are kept only as long as you define, and every provider signs a data processing agreement. Health data is a higher-risk category, so we run a DPIA with you before go-live.

Yes; it is tuned on your own price list and confirms extracted quantities back to you before the quote goes out.

The missed-call text-back is the report's number one exactly for solo tradespeople: it replaces the receptionist you do not have.

Billingo, Számlázz.hu, Kulcs-Soft, RLB60, Odoo and SAP through their interfaces; older desktop systems via file import or a browser agent.

The AI reads and proposes; a bookkeeper approves. Nothing is posted without a human click, and that is written into your engagement letter.

No. It is a checklist-driven pre-read that flags clauses for a lawyer to review; the lawyer decides.

Documents are processed under a DPA with EU residency where available, never used for training, and access is scoped per matter.

With Cal.com, Calendly, Google Calendar and most salon systems that expose a calendar or an API.

Into Google Calendar, Calendly, Cal.com or a planner with an API; otherwise it books into a shared calendar you mirror.

Shopify, WooCommerce, Unas, Shoprenter, eMAG and Alza; GLS, DPD, Foxpost and Packeta on the courier side.

Yes, with a dedicated technical login and two-factor handled; every upload is logged with a screenshot.

Fewer than on voicemail. Callers stay when they get an immediate, useful answer and are told they can reach a person.

Yes: the agent takes calls on no-answer, after hours or when the line is busy, and warm-transfers when needed.

Not when grounded in your price list and told to say 'I don't know' outside it; we also log every conversation and review samples weekly.

Known spam numbers are filtered and no text is sent; unknown numbers get the message, which costs cents.

In SMEs it usually removes the tasks nobody wanted and frees people for revenue work. The report's figure is 30–45% of staff time spent on robot work.

Only if it also scores high on frequency and clarity. A painful but vague process is a bad first project; fix an easy, frequent one first and return to the painful one with credibility.

A fixed price that pays back within roughly three months from the measured manual cost. If the numbers do not support that, the scope is wrong, not the price.

Yes, with a warm transfer that passes the caller's name and reason, or by scheduling a callback if nobody is free.

Yes. Calls are forwarded to the agent on no-answer, after hours, or always, and the number stays yours.

The build can be, but maintenance usually is not: every interface update risks breaking the bot. Over a year, API-based AI automation is typically cheaper to run.

Handled the same way. The model reads German, English or Romanian invoices and returns the same field set; currency is captured and converted according to your accounting policy.

Yes, for judgement and compliance. What changes is that they stop typing and start reviewing, which is a better use of their hourly rate.

Often yes if it records calls or processes health, financial or other sensitive data at scale. For a booking agent at a hair salon, usually no, but documenting the assessment is still good practice.

Missed-call text-back and the review funnel. Both are single-workflow projects in the report's starter price tier: 200,000–500,000 HUF setup and 30,000–80,000 HUF a month.

The first, third, fifth and eighth were built for exactly that: tradespeople, doctors, consultants, salons. They replace a receptionist you do not have.

Mixed. The report blends international practitioner data (Reddit, YouTube, LinkedIn) with Hungarian agency figures; pricing and tool notes are specific to Hungary.

Automations run on servers, call paid AI and telephony APIs, and need someone watching for failures and tuning prompts. The retainer buys that; without it, systems silently rot.

We do not publish list prices; every project is quoted at a fixed price after the discovery call, with a flat monthly fee for running it.

Make to prototype fast without a server; n8n once volume grows or data must stay on your own EU server. Many projects start on Make and move to n8n.

Yes, if you have the bandwidth to review results. The order matters more than the calendar: cheap and visible first, then time savings, then the bigger builds.

Shopify, WooCommerce, Unas, Shoprenter and eMAG/Alza marketplaces via their APIs; the courier side covers GLS, DPD, Foxpost and Packeta.

Yes; that is the report's core example. The agent answers while your hands are busy and books into your calendar, for a fraction of a receptionist's cost.

No. A chatbot is one possible interface. AI automation covers any task where a model reads, decides or writes on your behalf, including back-office work nobody chats with.

A scoped first version typically goes live in two to three weeks, provided the process is documented and the tools it touches have APIs.

It can, which is why we give agents the narrowest permissions that do the job, log every action, and route low-confidence cases to a person before anything is written.

Yes. We recommend and configure a clear disclosure at the start of the call. It is required under the EU AI Act for AI systems interacting with people, and callers respond better when told.

Yes. The agent detects the caller's language in the first sentence and continues in it, or you can pin one language per phone number.

Website chat, Messenger, Instagram, WhatsApp Business, SMS, email and phone. The same assistant logic can serve several channels with channel-specific formatting.

Almost never. Workflow automation works with what you have. Replacing a tool is a separate decision, usually made later and for other reasons.

Not where legacy software has no API. It is now usually the last mile of a workflow rather than the whole solution.

Not with the commercial APIs we use, whose terms exclude customer data from training. We confirm this per provider in the data processing agreement.

As often as your source changes. We typically sync from a shared drive, Notion or your CMS on a schedule or on each edit.

Yes. Modern models read images directly, including phone photos of receipts, though sharper scans give higher accuracy.

Current engines do, including ő and ű, on reasonable-quality scans. Handwriting remains the weak spot.

Options in order of preference: a database connection, file import and export, or RPA that drives the interface. All three work; they cost more to maintain than an API.

When signed and verified, yes. We validate the signature on every incoming webhook and reject anything unsigned.

We write it so it is honest and useful: it confirms receipt, asks one or two relevant questions and names the person who will follow up. Most prospects prefer that to silence.

No, but they can be made rare and harmless: rare through grounding and scope, harmless by never letting the model act on uncertain information without a check.

For document processing, 2 to 8% after the first month. For support triage, 15 to 30% depending on how narrow the scope is. The share falls as rules are tuned.

It can be kept in the EU with the right provider settings, and where it cannot, standard contractual clauses apply. We set this per project and record it in the DPA.

Something a person would write: 'Hi, I'm with a customer and couldn't pick up. How can I help?' The AI then reads the reply, asks for the address and urgency, and offers two calendar slots.

For the first reply, yes, because it is automated. The human follow-up can come later; what matters is that the prospect hears back immediately.

Cal.com or Calendly for booking, Twilio or WhatsApp Business for messages, n8n or Make for the logic, and your existing calendar.

Yes, through the WhatsApp Business Cloud API with a verified business profile, which also lets you send order confirmations and tracking links.

The report's pattern is day 2, 7, 14 and a 'break-up' note on day 25, stopping the moment the prospect replies or books. 80% of deals close between the 5th and 12th touch, and most humans stop after one.

The invoice is held, the finance owner gets a one-line alert with the discrepancy, and approves or rejects with one click.

Yes. A technical user is created in the Online Számla portal and its credentials are used by the automation; no special licence is required.

The agent books a callback in the first free slot, confirms it by SMS, and logs the brief in the CRM.

Whisper and Deepgram handle Hungarian technical vocabulary and background noise well; the AI confirms extracted quantities back to the technician before the quote is sent.

PandaDoc, DocuSign, and for Hungarian legal weight the AVDH service; all have APIs the automation can drive.

For existing customers under legitimate interest, generally yes, with a clear opt-out. Any STOP reply blocks further messages automatically.

Asking everyone for feedback and offering the public link is fine; selectively blocking unhappy customers from Google is against Google's policy. The funnel asks everyone and simply adds a private channel for problems.

Yes; sheets are synced into a small warehouse first so questions run fast and consistently.

Handled with a dedicated technical account and an authenticator or SMS code the automation can read, agreed with the portal owner.

It is trained on your own past posts and speaks in your register; the human approval step catches anything off. Keyword stuffing and generic phrasing are explicitly avoided.

Wherever the owner already looks: WhatsApp, Slack, Teams or email. Phone-friendly, no dashboard to open.

Yes. Monitoring, retries and alerts are part of running the system, not an add-on.