Designed for
For HVAC and field-service companies with 3–25 technicians who want to replace manual follow-up with a clear path from request to collection.
HVAC maintenance and field-service companies across the region
Field Tek: dispatch, job sheets, and maintenance history in the field
Field Tek is a scheduling and dispatch system for HVAC maintenance and field-service companies with 3–25 technicians, and it follows each job from request to invoice. Each service request goes to an available technician, who documents the work with photos and checklists, and the invoice is issued before the technician leaves the site.
Dispatch dashboard
Technician mobile app
No-app customer portal
Operating brief
What Field Tek brings under control
HVAC maintenance and field-service companies across the region
From service-request intake to an electronic invoice on-site before the technician leaves — built with field-service partners across the region. An Arabic-first system scope for HVAC maintenance companies: request intake, dispatch board, field execution with job evidence, quotes, and local invoices. Confirm available workflows and demonstration access with the team; we make no customer-results or automatic-compliance claims before each business is configured and measured. In short, Field Tek: dispatch, job sheets, and maintenance history in the field.
Core workflow
A request comes in, dispatch assigns an available technician, the job is documented with photos and checklists, then the electronic invoice is issued before leaving the site.
Confirm Field Tek availability for maintenance intake, technician dispatch and work evidence in your company. Review devices, connectivity, record exports and demo scheduling before rollout; maps and payments are not assumed active.
System modules
What the system delivers
Dispatch dashboard
01Receive service requests and assign them to an available technician with live job status.
Technician mobile app
02Job details and site context, checklists, before/after photos, and sync on poor connectivity.
No-app customer portal
03A signed link for request status, quote approval, invoice, and feedback — without forcing a customer app install.
Local invoicing and collection
04Quotes and electronic invoices with local payment paths, and e-invoicing wiring when credentials are ready — no compliance claims before legal setup.
From daily work to decision
How Field Tek works in practice
01
A working day on the system
Proposed Field Tek review scenario: a supervisor receives a maintenance request, assigns a technician and reviews work evidence before closure and collection. Ask to exercise reassignment, declined work and missing parts rather than only viewing a dashboard. Verify each step in the demonstrated version; this example does not imply immediate rollout availability.
02
Market and operating fit
Review Arabic technician terminology and capture of photos, parts and time on actual device types. Test weak connectivity and storage/sync limits if included in the offer. Maps, payments, invoicing and external integrations require written availability, fee and dependency confirmation; a requirement is not proof of implementation.
03
What it replaces
Compare current dispatch messages with a clear owner, status and completion evidence. Define acceptance for job closure and corrections, including who may change price or remove an attachment. Measure repeat visits and incomplete jobs where feasible, but do not promise a reduction before observing real operation.
04
Buying and rollout notes
Before expansion, agree a pilot scope and acceptance criteria suited to the team. Test duplicate assignment, repeated photo upload, lost connectivity during save and reopening closed work. Agree supervisor/technician permissions, work-log exports and outage responsibility. Confirm support, prices and availability before committing.
Frequently asked questions
Beachhead ICP: Jordanian companies with 3–25 technicians and hundreds of jobs per month. Very small solo operators may not fit the first phase economically.
Field Tek
Plan a clearer workflow for your field team
Let’s map a service request from assignment to visit and documentation, and identify the permissions and information your team needs.