What is Helka?+
Helka is an AI inbound assistant with its own CRM, being developed by StructylAI in Switzerland for businesses handling contact forms, emails and phone calls. It is being built to reply from approved business information, organise customer records and assign unresolved work to a person or team. Helka is still in development, with a local English voice demonstration; production channel availability and integrations require individual validation and release approval.
How is Helka different from a general-purpose chatbot?+
A general-purpose chatbot centres on a conversation. Helka is being built around the business work that follows an inbound enquiry: approved answers, a customer record, permitted context and follow-up assigned to a person or team. It has its own CRM and an intended workflow across contact forms, emails and calls. It is not a released replacement for every chatbot or CRM, and external integrations require individual review.
Can Helka prepare a sales brief for a telecom team?+
That is an intended configurable workflow. A brief can bring together the reason for calling, the current provider and plan, stated costs, contract questions, usage, budget, switching requirements and an agenda for the sales agent. Information must come from the customer or permitted systems, with sources, unknowns and verification status kept visible. This is not a released telecom integration or automatic access to another provider's private account.
Is it just an AI receptionist?+
No. Answering an incoming conversation is only one part of Helka. Accounts, contacts, leads, opportunities, service cases, enquiries, tasks and timelines preserve the work that follows. Records also track possible identity matches, consent, preferences and assignments. An enquiry extends a conversation within the same customer record. The aim is to give your team continuity and a clear next step, not to provide an unrestricted autonomous employee.
Who is it for?+
Helka is being developed for businesses and customer-facing teams that handle incoming enquiries, scattered information and follow-up. Founders, sole traders and interested individuals are welcome to enquire; a company is not required for individual applications. StructylAI reviews suitability, workflows and availability before rollout. Helka is not currently offered as a consumer assistant or a ready-made industry solution, and commercial availability in Switzerland or elsewhere is not assumed.
Does it replace my team?+
The aim is to support intake, continuity and consistent use of approved information. People remain responsible for judgement, exceptions, business decisions and unresolved work. Tasks can carry an owner or queue, priority, due time and resolution evidence, so an employee can see what still needs attention. A created task is not a completed callback, and no staff reduction or measured time saving is promised.
Can it use information about my business?+
It can use approved, versioned business facts and permitted customer context, with sources, freshness, precedence and revocation taken into account. Preparation and integration work depend on your information and permissions. Customer messages or document instructions do not become authority to change business rules. Employees can review corrections and history; this is not a promise of unrestricted file access, perfect answers or immunity to malicious instructions.
Can it access private customer records?+
Access is limited to permitted information in connected systems and is subject to configured identity checks. An incoming telephone number or possible account match is a clue, not proof of identity. Public questions may not require verification; private records and actions do. Software outside the AI controls permissions, and verification codes are excluded from AI input and transcripts. Records distinguish customer statements, confirmed information, conflicting details and unresolved questions.
Can it make bookings or update records?+
Only specific actions are permitted within a reviewed workflow with suitable integrations and checks. Optional scheduling requires access to real availability. For important actions, exact details must be read back in full, the customer must separately confirm the action, and a successful result must be saved before acceptance is reported. Correcting contact details does not authorise another action. A proposed time is not a booking, and not every action in an external system can be undone.
What happens when it cannot help?+
It should clarify uncertainty, avoid guessing and expose the unresolved work to a person. A live transfer depends on configured staffed availability. Otherwise, the workflow can prepare an owned task or callback request with the conversation context and open questions. A provider failure or interruption can also leave work unfinished. There is no guaranteed immediate pickup, callback deadline or flawless human-like conversation.
Can Helka reply automatically to forms, emails and calls?+
That is the intended three-in-one workflow: understand the enquiry, respond with relevant details from approved business information, ask for missing information and organise the next step. Calls have a local English demonstration. Contact-form intake requires reviewed deployment, with automatic replies depending on an approved delivery channel; a saved receipt is not itself a substantive answer. Email foundations support threads, classification and drafts for review. Receiving production email is disabled by default until a real provider is validated; sending substantive replies also requires release approval. A draft is not a sent email. This website's access form remains a separate sales enquiry and does not activate Helka.
Will it work with my existing CRM or calendar?+
Helka has its own CRM. Connections to other systems are assessed individually. We agree which system holds each record, who may update it, how conflicting changes are handled and what migration involves. Responsibility can stay with Helka, an external system or both under agreed rules. Universal compatibility, effortless migration and perfect synchronisation are not promised. No named CRM, calendar or email vendor is represented as a ready-made supported integration.
Are calls recorded?+
Recording is off by default. Transcription is a separate form of processing, and callers are normally informed about AI and transcription before information is captured. Turning recording off does not mean that no processing occurs. Recording settings, privacy requirements, legal obligations and provider terms require explicit review for each deployment. Data export, redaction, deletion and retention foundations do not guarantee instant deletion everywhere, exclusions from provider training, a particular processing region or GDPR, FADP, SOC 2 or ISO certification.
Does it learn from every conversation automatically?+
No. Conversations are not intended to trigger uncontrolled self-training. Corrections, evaluations and approved changes can inform improvements, while business information remains subject to approval and version tracking. Foundations exist for separating organisations' data and limiting time, retries, data exposure and spending; these are not production certification. A customer message does not silently change business policy, and the system can still make mistakes.
Which languages does it support?+
English is the initial target and the language of the current local voice demonstration. Other languages, including German, Swiss German, French and Italian, are future directions that require separate validation and release acceptance. They are not presented as live support and there is no language selector implying otherwise. Suitability for your customers must be discussed rather than assumed.
Is Helka publicly available now?+
StructylAI is accepting access and demonstration enquiries for review, but automatic self-service activation is not available. Substantial foundations and a local English voice demonstration exist; full release acceptance and live-call testing are not complete. Capabilities, suitability and rollout availability must be confirmed before deployment. An enquiry does not create an organisation's account, activate a telephone number, connect a CRM, enable recording or certify production readiness.
What does it cost?+
Public pricing, paid offers and trials have not been approved. Discuss your intended workflows, usage, information and integrations with StructylAI so the requirements and available capabilities can be assessed. Sending an enquiry does not commit you to a payment or start a trial. Savings and returns on investment are not guaranteed.
What happens after I request access?+
A genuine reference from the form confirms that your enquiry has been saved for StructylAI to review. Visiting the receipt-information page alone does not confirm a submission. The next discussion covers your enquiries, approved information, integrations, suitability and availability. No account, trial, telephone number or booking is created automatically, and no response deadline or acknowledgement email is promised. Product updates are optional and require a separate choice.
