# Helm — the long version > Custom AI workflows for businesses. Checked 25 September 2026. Canonical source: https://helm.vision/ Helm builds, governs and runs custom AI workflows for organisations where thousands of people write in and one team answers. The agent reads the message in the customer’s language, follows rules agreed and signed before it is built, and finishes the job — books the appointment, collects the deposit, files the claim, routes the exception to a named person — inside WhatsApp, Instagram, Messenger, voice, email and the web, and writes the result into the systems the team already runs. **Key terms**: AI customer service agent, AI agent for WhatsApp, WhatsApp Business API automation, Instagram DM automation, AI appointment booking, AI receptionist, lead qualification agent, AI agent for clinics, AI agent for schools and universities, AI agent for real estate developers, AI agent for restaurants, omnichannel customer messaging, Arabic and English AI agent, AI workflow automation with human approval, customer service automation Egypt, AI agent for the Gulf, AI agent for insurance, AI agent for car dealerships ## What Helm is Helm is a workflow deployment company, not a chat widget and not a chatbot builder. A Helm deployment is one agreed workflow, running in production, with a named owner, rules signed before the build, and a measure of whether it worked. The conversation is the interface; finishing the job is the product. The distinction that matters commercially: a support tool routes a message to a person, and a chatbot answers a question. A Helm agent completes the transaction — the slot is held in the real calendar, the deposit is taken, the claim is filed, the lead record exists in the CRM with the answer attached — or it stops and hands the work to a named person with everything they need. ## How a workflow runs 1. **Work comes in.** A message, a document, a comment, a form, a call. WhatsApp, Instagram, Messenger, voice, email, web. 2. **The agent works.** It reads in the customer's language, applies the rules from the scope, reads and writes the systems of record, and decides whether it may act. 3. **Work moves forward.** The action is taken, or approval is requested, or a person is brought in with context. Either way there is a next step and someone owns it. ### Autonomy, set per workflow before deployment - **Let it act** — approved answers, available slots, routine updates. Allowed. - **Ask for approval** — a commitment, a change, an exception to the rule. Review. - **Bring in a person** — named owner, full context, a clear next step. Handoff. The rulebook is agreed before deployment, and the next action is visible to the team. ### Languages Arabic and English are the working languages, including Egyptian Arabic and Gulf dialects; the live demo on the site also starts in Spanish, French and German. The agent replies in the language the customer wrote in. ## Industries ### Schools & universities https://helm.vision/industries/schools-universities/ Thousands of applicants, one office. Every one answered before the deadline. What we counted: A private university: 94 applications, then 18 admission fees paid, then 7 enrolments — through one channel, counted end to end. What Helm asks for to start: your admissions calendar. ### Clinics & hospitals https://helm.vision/industries/clinics-hospitals/ Appointment questions at 11pm, across every branch. Every one answered, every slot held. What we counted: Median wait for a human reply before Helm, on our own accounts: 1h36 · 53% of messages arrive when the office is shut. What Helm asks for to start: your appointment book. ### Spas & salons https://helm.vision/industries/spas-salons/ The price question is the booking. Every one answered, every slot held. What we counted: Price questions are the most common message a salon receives, and most arrive after closing. What Helm asks for to start: your price list. ### Fine dining https://helm.vision/industries/fine-dining/ A table for eight, asked at midnight. Answered, held, and on the floor plan by morning. What we counted: Large-party requests arrive overnight; a deposit rule removes the no-show. What Helm asks for to start: your reservation book. ### Fast food & delivery https://helm.vision/industries/fast-food-delivery/ Launch night, four hundred messages an hour. Every order status answered, every complaint routed. What we counted: A bakery chain: 648 of 703 page replies landed in under five seconds — an autoresponder with four canned lines. Fifty-five were typed by hand, median 46 minutes. What Helm asks for to start: last Friday's inbox. ### Automotive https://helm.vision/industries/automotive/ «How much?» under every reel. Every one answered — and asked: which showroom, which day? What we counted: A national car distributor, 1.7M followers: median reply to a customer question 17.9 hours, with 65% arriving after hours. What Helm asks for to start: your price list and your showrooms. ### Insurance https://helm.vision/industries/insurance/ Quotes, claims and renewals, one inbox. Each one answered — and nothing said that a regulator wouldn’t. What we counted: First notice of loss arrives on WhatsApp now, and the documents can be collected in the thread. What Helm asks for to start: your claims flow. ### Football clubs & venues https://helm.vision/industries/football-clubs-venues/ One fixture post, 162 comments, five tickets left. Every one answered, and the waitlist kept. What we counted: A 1,000-capacity venue: 162 comments on one post, more than the next seventeen posts combined. What Helm asks for to start: your fixture list. ### Enterprise & public service https://helm.vision/industries/enterprise-public-service/ Millions of interactions, one form. Every one classified, routed and finished — or handed to a person on time. What we counted: Reach-a-human within the SLA is the number that matters, and every route is visible as a chip. What Helm asks for to start: your contact form. ### Real estate developers https://helm.vision/industries/real-estate/ Sixty people wrote one word under your launch post — «details». Every one answered, and asked: which unit, which day? What we counted: A national developer, one launch post: 60 people wrote «details», 24 got the same reply, and 0 of 149 replies carried a fact. What Helm asks for to start: your launch calendar. Four of the ten industries have no counted entry yet. Those pages say so rather than borrowing a number from somewhere else. ## Numbers counted in production Anonymised: the sector is named, the client is not. Counted, never modelled. - A bakery chain (fast food & delivery): 648 of 703 page replies landed in under five seconds — an autoresponder with four canned lines. Fifty-five replies were typed by hand, median 46 minutes. - A national car distributor (automotive), 1.7M followers: median reply to a customer question 17.9 hours, with 65% of questions arriving after hours. - A private university (schools & universities): 94 applications, then 18 admission fees paid, then 7 enrolments, through one channel, counted end to end. - A national developer (real estate), one launch post: 60 people commented «details», 24 got the same reply, and 0 of 149 replies carried a fact. - Clinics, on Helm's own accounts: median wait for a human reply 1h36, and 53% of messages arriving when the office is shut. ## The engagement ### Three conversations - **Diagnose.** One recurring workflow: its volume, its current process, the cost of the gap. Output: a Workflow Opportunity Memo. - **Scope.** The systems, the information, the approval boundaries, the named owner, the baseline. Output: a Scoping & Deployment Brief. - **Decide.** A paid pilot with delivery milestones and the evidence that will judge it. ### What gets agreed before any build - The workflow: what starts the job, and what counts as finished. - Systems and information: where the agent reads, acts, and writes the result. - Baseline and success measure: what happens today, what should improve, how it is measured. - Authority: what the agent may do, what needs approval, what it must hand off. - Ownership: the person responsible for the workflow and for each exception. - Commercial and delivery terms: price, milestones, review dates, and the terms for a change in scope. ### Timing A first, single workflow is typically live within five working days once the client sends what Helm asks for — a price list, an appointment book, an admissions calendar, a fixture list. Broader scope, integrations, or enterprise security review take longer. The written pilot agreement defines the milestones. ### Sizing - **Launch** — one agent, one workflow, a clear owner. - **Scale** — several agents, connected teams and tools, deeper integration. - **Enterprise** — scoped deployment with security review, procurement and integration requirements planned in. ### Price Agreed before build, in writing, against the scope. Helm does not publish a price list, and there is no self-serve plan. ## Frequently asked ### Do we need a proof of concept first? The paid pilot is the focused evaluation. We agree the workflow, its boundaries, and how success will be assessed before implementation. ### What if our data is not ready? Scoping identifies what is available and what needs preparation. A sheet, calendar, price list, or published FAQ may be enough for a focused first workflow. ### Who runs it after launch? Helm’s engagement model includes a named engineer and ongoing review of the workflow. Support, reporting, and ownership are confirmed in the scope. ### Can you guarantee business results? Delivery milestones and measurement are agreed up front. Business results also depend on data, the workflow, and team adoption. Review and restructuring terms belong in the written agreement. ### What does procurement need to know? Helm Vision OÜ is registered in Estonia. The platform is hosted on AWS, with separate client tenants. Deployment-specific security, data handling, export, and enterprise source-code escrow requirements can be discussed during scoping. ### Which channels does Helm work in? WhatsApp, Instagram, Messenger, voice, email and the web. Work is written back into the calendar, CRM, payment and operations systems the business already runs. ### Does it speak Arabic? Yes — Arabic and English are the working languages, and the agent replies in the language the customer used. ### Is this a chatbot? It answers like one and is bought by people searching for one, so the honest answer is: the conversation looks familiar, the product is not. A chatbot answers a question. A Helm workflow finishes the job in the system of record, or hands it to a named person. The rules are agreed and signed before the build, and what the agent may decide alone is set per workflow. ### How is it different from a helpdesk or a chat widget? A helpdesk organises work for people to do. Helm does the work, inside the channel the customer already used, and escalates by design rather than by default. ### Can it take a payment or a deposit? Yes, where the workflow calls for it — a booking deposit is one of the standard patterns, and the rule that triggers it is agreed in scoping. ### What happens when it does not know? It stops. The workflow names who receives the exception and what context goes with it. Silence and invention are both treated as failures. ### What about our data? Helm Vision OÜ is registered in Estonia and the platform runs on AWS with separate client tenants. The AI disclosure, privacy policy, DPA and subprocessor list are published at https://helm.vision/ai-disclosure, https://helm.vision/privacy, https://helm.vision/dpa and https://helm.vision/subprocessors. Deployment-specific data handling is agreed in scoping. ### Who is behind Helm? Helm Vision OÜ, registered in Estonia, with operators in Madrid and Toronto and engineering in Cairo. Clients run in Europe, North America, the Gulf and Egypt. ### How do we start? Describe the workflow at https://helm.vision/pilot/, or send the one file the industry page asks for. The first conversation is a diagnosis, not a demo. ## Pages - https://helm.vision/ — Helm: custom AI workflows for your industry - https://helm.vision/pilot/ — the engagement: three conversations, two documents, a paid pilot - https://helm.vision/brand/ — how Helm writes and what it will not say - https://helm.vision/industries// — one page for each of the ten industries above