“Didn’t we fix that villa in March?”
Nobody scrolls back nine months through a group chat. Repeat faults disappear inside the noise.
Built and used daily on a 228-villa community
TT3 maintenance operations · UAE
Log a job in eight seconds. Prove it a year later.
A technician types a block, a unit and one familiar word. TT3 turns it into a routed, timestamped job with a name against every step—on a low-cost Android, one-handed, even without signal.
Works offline
No app store
Your Google account
Type it the way your technician would
No form. No perfect English required.
Live parser
Start typing to see what gets logged…
Sample estate routing. Nothing is submitted.
Ready offline
~8 secTypical job entry
OfflineQueues and syncs
1 tapMonthly report
100%Your data ownership
What you are replacing
A WhatsApp group, a notebook and a spreadsheet
That combination works until somebody needs to search it, count it or use it as evidence.
“How many A/C calls last month?”
There is no reliable number—only a feeling, usually assembled at the end of the month from memory.
“We attended that same day.”
A chat log full of voice notes is not a clean record to place on the table at contract review.
In the field
Built for the technician holding the tools
Field staff do not complete eleven fields. They type what they would have said aloud, check the result and tap once.
- Jobs entered without signal stay safely queued on the phone.
- They sync automatically when service returns—no re-entry.
- The app installs from a link. No app store, APK or IT rollout.
Real TT3 staff interface. The job is captured first; signal can catch up later.
Proof of work
Every job carries its own history
Not a status field somebody can overwrite. A sequence, stamped as it happened, with a name against each step.
- Job loggedLogged by Rashid
- Routed to Sitewide FMAuto-assigned from the Block 4 mapping
- Work startedAccepted by Imran · 1h 45m after logging
- ResolvedClosed by Imran with a note
This is the record you send when a contractor remembers the sequence differently.
Real TT3 job history, with the original names, timestamps and notes kept together.
How it works
From fault found to review-ready record
The workflow is intentionally short because every extra step becomes a reason not to use it.
Type the shorthand
Block, unit and familiar fault words. The parser identifies the location, category, urgency and note.
Route automatically
The first matching rule sends the job to the correct site team, contractor or warranty provider.
Measure the outcome
Every handoff is timestamped. The month closes with performance, misses, repeat locations and a full job list.
Routing
It adapts to the way your estate is already organised
A/C on an external contract. Everything else in-house. Warranty work leaving the site team immediately. Different teams across different blocks. Each is a rule, not a development project.
# sample estate
default → the site team mapped to that block
Leak → Blue Harbour Services (warranty, wherever it occurs)
default → the site team mapped to that block
Leak → Blue Harbour Services (warranty, wherever it occurs)
Rules are read in order and the first match wins. Anything unmatched goes to the block’s default team.
You can add a contractor, block, job type or keyword yourself on every plan. Changes take effect immediately and are not billed as change requests.
The monthly report
The document you take into contract review
At renewal, you should know exactly how each contractor performed against the response times you agreed—not reconstruct it from chat history.
58Jobs logged
51Resolved
2Target missed
97%Within target
| Company | Jobs | Avg first touch | Avg to resolve | Missed | Within target |
|---|---|---|---|---|---|
| Ridgeline Technical | 29 | 1h 26m | 8h 54m | 1 | 97% |
| Sitewide FM | 25 | 1h 46m | 5h 12m | 1 | 96% |
| Blue Harbour Services | 4 | 5h 57m | 8h 21m | 0 | 100% |
Swipe to inspect the full table
Both misses remain visible in the report. One is marked excused because the tenant was travelling and the villa could not be accessed. Reasons are recorded; misses are never quietly removed.
What else the report surfaces
- Repeat locations and recurring fault types
- Busiest block and weekly job volume
- Longest job still open
- Every job in the period, one per line
Real TT3 statistics screen. The same figures stay live throughout the month.
Tenants
A request page residents can actually use
One link. No login, app or account. A tenant picks the problem, enters the villa number and the request lands in the same queue as staff jobs.
The tenant page is Arabic-first and right-to-left, with English alongside. Requests are clearly marked as resident-submitted.
The staff app is English today. An Arabic staff interface is available through an extended setup.
The supplied tenant page, shown 1:1—not a marketing reconstruction.
Focused by design
A maintenance record, not an oversized property platform
The boundary is deliberate. It keeps the product fast in the field, easy to support and clear about what it owns.
What TT3 is built to do
Capture jobs, route responsibility, preserve the audit trail, monitor response targets, expose repeat faults and export the record.
What stays outside the product
Service charges, payments, accounting, gate passes, photo attachments and custom third-party integrations. Data mirrors to a Google Sheet you own.
Ownership
Your account
Your export
Your continuity
The system sits in your name, not behind mine
You receive your own Google project, database and Sheet. You are not one tenant inside somebody else’s platform.
The core project and data stay under credentials your organisation controls.
Every job, timestamp and note remains available in a format Excel can open.
If support ever changes, the app does not automatically switch off and the records do not move.
Price
One setup fee, then support based on response time
Never priced per villa. The setup covers the estate; the monthly tier covers how quickly support needs to answer.
One-time setup
From AED 5,000
Up to 300 units on one site, block and contractor mapping, your logo, up to 15 accounts and one on-site training session. Multiple sites, an Arabic staff interface or historical spreadsheet migration are quoted before work begins.
AED 350 / month
- First response
- 2 business days
- Coverage
- Sun–Thu, business hours
- Channel
- Email and WhatsApp
- On site
- Quoted per visit
AED 750 / month
- First response
- 4 working hours
- Coverage
- Sun–Thu, 8am–8pm
- Change requests
- One a week, up to two hours
- On site
- One visit a year
AED 1,500 / month
- First response
- One hour
- Coverage
- Seven days, emergency line
- Change requests
- Two a week, front of queue
- On site
- Two visits a year + new-staff training
Standard is about AED 25 a day. Judge that against the administrator time currently spent reconstructing calls and retyping them into a spreadsheet.
Changing sites, contractors, job types, keywords and users is unlimited, immediate and included on every plan.
Before you ask
Straight answers to the usual questions
Our technicians barely read English.
They need a number, another number and a fault word they already use. During setup, the exact words your team says—including Arabic, Urdu and Hindi terms—are added as recognised keywords.
What happens if support is no longer available?
The project and data sit in your own Google account. Nothing is hosted only on the supplier side, so your records remain with you and the system can be handed to another developer.
Does it need internet?
Not to log a job. Offline entries are held on the phone and sync when service returns. A connection is needed to see other people’s latest jobs and generate the report.
We already have a spreadsheet that works.
Keep it. TT3 mirrors data to a Google Sheet you own. The difference is that the sheet is filled at the moment the fault is found, by the person who found it, rather than reconstructed later.
How long does setup take?
The usual process is a mapping session for blocks, contractors and keywords, followed by configuration and on-site training. From agreement to live use is normally around two weeks, depending on stakeholder availability.
Can we get our data out?
Yes, at any time. Jobs mirror to your Google Sheet as they happen, and the monthly report exports as a PDF.
Do you handle service charges or payments?
No. TT3 records maintenance work and contractor performance; it does not handle money or accounting.
What if we need something the product does not do?
Ask. Product improvements go into one shared queue and, when built, ship to every customer. Private one-off versions are avoided because they create fragile, difficult-to-support systems.
Talk directly
No sales team. You speak to the person who builds it.
Share the size of the estate and the number of contractors. You will get a direct answer on fit, likely setup scope and the sensible support tier.
No mailing list. No account creation. The button prepares a WhatsApp message using the two selections.