An AI front office for plumbing and heating firms. It replies while the customer is still looking, gathers the details your engineer needs and offers only slots your team can keep.
Customer records, service rules, job history and delivery updates often live across a notebook, a spreadsheet and somebody's memory. Lavenity keeps them with the enquiry, ready for the next person and the next visit.
Website chat, email, WhatsApp, Telegram and Instagram land in the same queue. A customer who writes on one and sends a photo on another does not become two jobs.
A returning customer does not type their address again, and the engineer can see which boiler or appliance is there and what happened last time before leaving the yard. That saves a phone call and a search through old messages.
Each service carries a default time, the required skills, the zones and the questions to answer first. The time is a template your operator can adjust on the quote, and the AI never decides that a request is complete — your template does.
Every change is logged: what ran, on what, whether Ven or a person did it, and how it ended — including the ones policy refused. It is the record you want when a customer asks why they were told that.
Confirmations, quotes and job updates all carry a visible delivery status. If sending fails, Lavenity retries and shows you what happened, so you can fix it before it becomes a missed visit.
Enquiries in, requests qualified, visits confirmed, jobs completed. The report shows whether customer interest became work, not merely how quickly somebody sent the first reply.
Your office already handles all four. Lavenity takes on the typing, checking and chasing, while stopping short of any promise or decision that should still be yours.
Ven turns a vague message into a clear request: address, boiler or appliance, fault and access. Every detail shows whether the customer supplied it or Ven inferred it.
Ven proposes; your office team accepts or rejects each detail. Nothing is sent, promised or booked on a suggestion alone.
Availability comes from real working hours, skills, service zones and travel buffers — never from a guess. The hold on a slot expires on its own.
Confirming creates the job sheet and keeps the whole brief together — service, address, access, appliance and answers. Nobody has to rebuild it from a long message thread.
This is not a chatbot bolted onto a diary. Ven proposes a structured next step; Lavenity checks the current job, your permissions and your rules before it acts. That is why confirming twice still produces one booking, not a second van.
Every workspace starts in Observe, where Ven writes down what it would have done and changes nothing. You climb from there, one mode and one service at a time. The last three cards are on the roadmap and say so.
Observe records decisions without touching the request. Assist proposes for review. Qualify lets Ven collect the answers on its own. Book stays switched off until the scheduling tools are in Ven's hands, and the console will not let you pretend otherwise.
Working hours in your time zone, the postcodes you actually cover, and what happens to an emergency at 23:40. Lavenity checks all three before a slot is ever offered.
Coming soon
Two-way sync with Google and Microsoft will let outside commitments block a slot and put each confirmed visit into the calendar your engineers already check. Lavenity's own week view is live today; those connectors are next.
Coming soon
Ven drafts the quote from the service template and what it learned; a named person approves it before it goes anywhere. Nothing financially binding is ever sent autonomously.
Coming soon
Every confirmed job already publishes a domain event — the seam the field-service and accounting connectors plug into. The event is live; the connectors are being built on it.
Lavenity is an AI front office for plumbing, heating and other field-service firms. New enquiries from your website, email and messaging channels arrive in one inbox. Ven gathers the job details, your team checks what matters, and a confirmed visit becomes a clear job brief for the engineer.
A helpdesk is built to close conversations. Lavenity is built to turn an enquiry into booked work. It combines the shared inbox and reliable AI replies you would expect from a helpdesk with the practical steps your office handles next: gathering job details, checking availability, holding a slot and preparing the engineer's brief.
Not today. Ven gathers the details and proposes the next step, but a person confirms the appointment. Autonomous booking is deliberately kept off until every scheduling safeguard is in Ven's hands. We would rather be clear about that here than let you discover it after signing up.
Three ways, all on by default. Ven starts in Observe and changes nothing. Answers stay grounded in the knowledge you connect. And every write passes through a policy layer that checks state, permissions and version first — the model proposes, the application decides.
No. A slot is held with an expiry and confirmed against a database constraint rather than a check in application code. Repeated and concurrent confirmations return the same appointment and the same work order, which is proven by an integration suite that runs them in parallel against Postgres.
Website chat, email, WhatsApp, Telegram, Instagram, Facebook Messenger, Discord, Slack and SMS all arrive in the same queue, and your team replies in whichever channel the customer already used.
Start with one service, the questions you always ask, your working hours, the postcodes you cover and one engineer's availability. Most teams can set that up in an afternoon. Observe mode lets you see what Ven would do before you allow it to change anything.
Not yet. The native calendar, availability, confirmations and work orders are live today; Google and Microsoft sync, quotes with approval, and field-service connectors are on the roadmap. Every confirmed job already publishes an event, which is the seam those connectors will use.
Lavenity is built first for UK plumbing and heating firms: businesses where a new enquiry needs to become a properly qualified, scheduled job for an engineer. The same workflow also suits electrical, appliance repair, cleaning and maintenance teams.
Lavenity's privacy practices are built in line with the GDPR, and the front office treats addresses, photos, serial numbers and message content as personal and operational data. Data in transit is protected with TLS, access is role-based, the chat widget runs in an isolated iframe, and every write is auditable. Enterprise plans add custom data retention and a dedicated security review.
Yes. Every plan starts with a 14-day free trial, with no card details required. You can begin in Observe mode and see what Ven would have done before you switch on any automation.
Start with one real service and your own enquiries. You get 14 days free, and Observe mode changes nothing until you say so.