A Lead Assistant That Turns Visitors Into Qualified Enquiries

No, it complements it. Your form stays available for everyone who prefers to type themselves. The assistant sits in front of it as a low-threshold entry: it answers the open question from your website content, asks targeted follow-up questions and hands name, email, phone and request to your company inbox — with the conversation as context and with the files that were uploaded in the chat. If the record should go into your customer management system instead, the crm_lead adapter takes over in the Custom package; it writes and therefore requires confirmation. What gets handed over is shown to the visitor in plain text beforehand, and only their click triggers the transfer.

It asks follow-up questions tailored to your business, for example about need, scope, timeframe and, where it fits, budget. Which fields it collects you determine on the tool itself; a custom schema takes up to twenty fields, and a call with missing required fields is not executed at all. So you do not receive an empty enquiry but a lead with context in the mailbox of the business. Outward, an event is created in addition that your own systems can pick up. The bar against the double click sits in the database and not in the interface, and a second attempt reports the duplicate instead of an error. More under lead assistant.

Wherever you want: to an email inbox, to several responsible people or, in the Custom package, straight into your CRM. The lead is handed over in a structured way, including conversation context and request. Behind it sits a tool with its own kind and its own approval mode; for CRM there is an additional adapter that writes and therefore asks for confirmation. Every handover carries a one-time key made from conversation, tool and input: if the same request is triggered a second time, the system reports the duplicate instead of sending again. How the connection to your CRM and other systems works through defined actions is covered under tool control.

Yes, both. Anyone who would rather use the phone leaves a number and a preferred time: in every package the assistant takes this as an enquiry for your inbox, and in the Custom package the callback_note adapter also writes it into your system as a callback note; in both cases it asks first, because something is written. If an appointment should come of it, the appointment tool type takes over: it takes appointment requests, reschedules and cancels, and the kinds of appointment on offer come from your own list; a request becomes an appointment once your business confirms it, and if the visitor gave an email address, they then receive a confirmation email. On request the assistant names free times from your stored kinds of appointment — time windows, duration, lead time and buffer — minus the appointments already requested or confirmed in XICBOT; it does not compare them with an external calendar, and the calendar_availability adapter reads from your calendar only with a calendar connection set up in the Custom package. A request is only possible if the lead time fits and the moment falls into an approved window; occupancy is checked under a lock. An hourly run sends the reminder for the confirmed appointment by email, if an address is on file. More at the booking assistant.

Yes. Data protection is part of the build, not an afterthought: hosting in Germany, a data processing agreement, data sovereignty and a deletion concept; the answers are generated by a specialised model provider, also outside the EU on the basis of standard contractual clauses. Contact details are only captured when the visitor provides them in the conversation and only handed to the destinations you have defined. Before sending, the visitor reads in plain text what will be handed over — name, email, phone and request; only their click carries it out. Every call is then recorded in the log, with input, result and the path by which it was approved. The visitor address is not stored in plain text but as a tenant-specific digest. Details under privacy and hosting.

The lead assistant with structured lead handover and conversation analytics is part of the Pro package from 149 € per month net, plus a one-time setup from 2,900 € net. A captured lead carries a one-time key made of conversation, tool key and sorted input, so the same entry does not land twice as an enquiry in your inbox. Plain lead capture is often already covered by the Start package from 49 € per month net and 990 € net setup. Through the conversation analytics you see which enquiries arise and how many of them were handed over. All details are listed under pricing. All services can be cancelled monthly; there is no minimum term.