ZANUS AI FOR FIELD SERVICE & REPAIR — SERVICE REMINDERS
Maintenance-due reminders, seasonal tune-up campaigns, warranty-expiration notices, contract renewals — drafted by the AI from your own service history, in the customer’s language, queued for approval. The slow-season pipeline, built from records you already own.
Private tenant or your own server · unlimited technicians · your manuals never train a public model

Campaigns and sequences drafted from the service records — reminders, tune-ups, renewals — awaiting approval.
Units past the service interval, warranties expiring in 60 days, maintenance contracts up for renewal: audiences built from your own equipment and job history — no list ever exported.
The tune-up offer reads naturally in Spanish to the restaurant owner and in English to the property manager — your shop’s voice, their language.
Opt-outs and contact preferences are enforced by the system, not by memory. Every send is on the record.
The audience, the content and the sending all live in the same system as the service records — nothing leaves your tenant to reach a mailing platform. “Remind every customer whose unit we installed in 2021 that the compressor warranty ends this year” becomes a drafted, scheduled campaign in minutes.


Every outbound customer communication lands in the approval queue unless you designate the category as auto-send. The shop stays in control of every word that reaches a customer.
That is the point: the shoulder-season tune-up campaign is drafted from units due for service in exactly those weeks — reviewed by you, booked into the same calendars the AI phone uses.
No. Audiences, drafts and sends all happen inside your isolated tenant — your customer and equipment data is not shared with a mailing platform or anyone else.
← Previous: Automations · Sharing with a colleague? 📄 Get the PDF · ✉️ Email this page ·