Summary
Business Challenge
Maintenance requests typically included only an address and a brief description. Equipment details, warranties, previous repairs, and service recommendations were scattered across CRM records, manuals, spreadsheets, and office conversations.
The assigned technician had to reconstruct each unit’s history upon arrival or contact the dispatcher. Missing information delayed diagnosis, increased return visits, and made handoffs between team members inconsistent.
What We Did
WiserBrand implemented a WhatsApp-based maintenance assistant connected to Zoho CRM.
The assistant gave the maintenance team one conversation for pre-visit information, job-specific questions, and service updates. Zoho CRM remained the operational system of record, eliminating the need for a separate maintenance application.
1
Connected Property and Maintenance Records
WiserBrand organized Zoho CRM around properties, units, equipment, vendors, maintenance jobs, and service history.
Manuals and warranty documents stored in Zoho WorkDrive were linked to their corresponding units or assets.
2
Automated Request Intake and Review
Requests from Zoho Mail and Zoho Desk were matched to the relevant property before a maintenance job was created.
Missing details, ambiguous addresses, and uncertain matches were routed to a dispatcher.
3
Captured Updates and Preserved Human Control
Service notes, photos, and parts used were submitted through WhatsApp and added to the corresponding CRM record.
The maintenance team retained responsibility for diagnosis, repair decisions, safety, and job completion.
4
Delivered Briefings and Answers Through WhatsApp
Before each visit, the assigned technician received a summary containing:
- Property, unit, and access information.
- Equipment model, installation date, and warranty status.
- Previous repairs, recurring faults, and parts used.
- Existing recommendations and unresolved issues.
Follow-up questions could address previous repairs or information from equipment manuals. Property-specific answers were drawn from CRM records and linked documents; general technical guidance was identified as information that requires verification.
