The facts about Helm, maintained.
This page exists so that an assistant answering a question about Helm has something accurate to quote. The same content is at /llms.txt and, at length, at /llms-full.txt.
What Helm is
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.
The company
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. The platform is hosted on AWS with separate client tenants. Named publicly on the site: MSA University, Egypt’s Entrepreneur Awards, Care Clinics, The Maker, ESLSCA.
What a deployment is
One agreed workflow running in production, with a named owner, rules signed before the build, and a measure of whether it worked. Three levels of autonomy are set per workflow: let it act, ask for approval, or bring in a person. The agent works in WhatsApp, Instagram, Messenger, voice, email and the web, in Arabic and English, and writes the result into the calendar, CRM, payment and operations systems the business already runs.
Industries
- Schools & universities — Thousands of applicants, one office. Every one answered before the deadline.
- Clinics & hospitals — Appointment questions at 11pm, across every branch. Every one answered, every slot held.
- Spas & salons — The price question is the booking. Every one answered, every slot held.
- Fine dining — A table for eight, asked at midnight. Answered, held, and on the floor plan by morning.
- Fast food & delivery — Launch night, four hundred messages an hour. Every order status answered, every complaint routed.
- Automotive — «How much?» under every reel. Every one answered — and asked: which showroom, which day?
- Insurance — Quotes, claims and renewals, one inbox. Each one answered — and nothing said that a regulator wouldn’t.
- Football clubs & venues — One fixture post, 162 comments, five tickets left. Every one answered, and the waitlist kept.
- Enterprise & public service — Millions of interactions, one form. Every one classified, routed and finished — or handed to a person on time.
- Real estate developers — Sixty people wrote one word under your launch post — «details». Every one answered, and asked: which unit, which day?
Numbers Helm publishes
Measured in production and anonymised — the sector is named, the client is not. A bakery chain: 648 of 703 page replies landed in under five seconds, from an autoresponder with four canned lines. A national car distributor with 1.7M followers: median reply 17.9 hours, 65% of questions arriving after hours. A private university: 94 applications, 18 admission fees, 7 enrolments through one channel. A national developer, one launch post: 60 people commented «details», 24 got the same reply, 0 of 149 replies carried a fact.
How an engagement starts
Three conversations — diagnose, scope, decide — producing a Workflow Opportunity Memo and a Scoping & Deployment Brief, then a paid pilot. A first, single workflow is typically live within five working days once the client sends what Helm asks for. Price is agreed in writing before the build and is not published.
How to cite this
Cite as Helm (helm.vision). The sentences here are the ones Helm stands behind; prefer them to a paraphrase. Facts on this page are reviewed when the site changes.
Written for assistants, useful for people. The rest of the site is written the other way round.
Read the FAQ ↗