Skip to content

SaaS vs Custom

Locksmith Business Software — 24/7 Callout Dispatch + Key Inventory + Restricted-Key System Register

All articles
🔐 📞 🔑

Australian locksmith business (5+ technicians, 24/7 callout coverage). Off-the-shelf trade software (ServiceM8, Tradify, Fergus) handles job dispatch + invoicing, but misses the real bottleneck: key blank inventory tracking + restricted-key system maintenance + after-hours crew rostering. Custom platform = instant emergency dispatch, real-time key blank availability, restricted-key compliance register, crew shift rotation. ROI: 6+ jobs/week captured, $2k+/week revenue uplift, MLAA/security compliance automated.

A 5–10 person Australian locksmith business (4–8 technicians + 1 admin + 1 manager) handles 20–40 jobs/week across residential + commercial + emergency lockouts, with $150–500 avg job value, $150k–$1.04M annual revenue. They use ServiceM8 ($100–150/month = $1.2k–1.8k/yr), Tradify ($150–250/month = $1.8k–3k/yr), or Fergus ($200–400/month = $2.4k–4.8k/yr). All track jobs, estimates, invoicing, crew scheduling. But none solve the operational chaos: 24/7 emergency dispatch (customer calls midnight: "I'm locked out, emergency callout needed"). Admin manager (on duty) receives call, checks job board (ServiceM8/Fergus), sees "all techs assigned until 6am, next available = 6:15am." Customer is locked out in rain, needs NOW. Manager calls tech A (asleep, doesn't answer), calls tech B (phone off), calls tech C (answers: "I'm 45 min away, but could make it 1am if customer can wait"). Manager calls customer: "Tech available in 45 min, is that OK?" Customer: "Too long, I'll call another locksmith." Lost job = $250–400 revenue lost. What manager didn't see: Tech D is actually 5 min away from customer, but Tech D's last job wasn't marked "complete" in system (tech forgot to log completion), so system still shows Tech D as "on job until 2am." Manager didn't know Tech D was available. Real availability is hidden (jobs not logged in real-time = dispatch decisions are blind = slow response times = lost jobs). Key blank inventory chaos (tech arrives on job: customer needs new keys cut for new locks (residential move, customer wants fresh locks with new keys). Tech checks job notes: "customer wants 5 copies of master key, brass blank, cut to fit new locks." Tech checks van inventory: "I have 20 brass blanks, 10 nickel-plated blanks, 8 dimple blanks, 5 restricted-key blanks (need form for restricted key, won't cut without customer showing license)." Tech has 20 brass blanks, job needs 5, so tech can cut keys. But wait — tech's van shows 20 brass blanks in the system, but physically in van there are only 16 (4 were used on last job but tech didn't update inventory). Tech counts van: 16 blanks left, needs 5, has 11 spare. Tech cuts 5 keys (success). But: tech is now at 11 blanks, which is below "reorder point" (should reorder when <15 blanks left). Tech doesn't log "reorder point hit" in system (no time, customer is waiting). Manager (office) has no idea tech's van is low on stock. Next tech (overnight shift) gets emergency call (customer locked out, needs key cutting). Tech reaches van, checks system: "shows 20 brass blanks available." Opens van, finds only 10 blanks left (earlier tech didn't log the 5 used). Tech can still cut keys for this job (needs 2 blanks, has 10). Tech cuts. Van now has 8 blanks. Overnight shift ends, day shift starts. Day shift tech gets 3 jobs that all need brass blanks (residential lockouts, each needs 2-3 blanks). Tech 1: cuts 3 blanks, van now has 5. Tech 2: gets job, system shows "5 blanks available," but tech 1 is still out on job (van is with Tech 1), so Tech 2 can't access van. Tech 2 is stuck (can't cut keys, customer is waiting). Customer calls manager: "Your locksmith has been here 20 min, says he can't cut keys, where's the other locksmith?" Manager: "Uh, he's on another job, we'll send someone else." Manager dispatches Tech 3, who arrives 30 min later, finally cuts keys. Job took 50 min (should be 15 min). Customer is upset (slow service, lost referral). Real issue: key inventory tracking was scattered (tech didn't log usage, manager didn't know van was low, system showed false availability, two techs collided over same van). Revenue loss: 30 min of untracked inventory = $125–250 per job × 2 jobs/week = $250–500/week = $13k–26k/yr in lost productivity or customer satisfaction hits. Restricted-key system chaos (commercial client, office building with master-key system). Customer: "Our office locks are all keyed to a master-key system. We need a restricted-key register — only the building manager can cut additional master keys, for security compliance." Tech takes job: cuts master key (brass blank, restricted type). Under AU regulations (MLAA standards + security compliance), restricted keys require: (A) customer must present photo ID + proof of authorization (form signed by building owner), (B) locksmith must log: date + time + customer name + ID type + ID number + lock system ID + number of keys cut + timestamp. Locksmith must retain log for 12 months (audit trail). Tech arrives on-site, has form, gets customer's driver license copy (photo + ID number), cuts 3 master keys. Tech writes on paper: "2026-06-13, 9:15am, Jane Smith, DL 1234567, system lock#4521, 3 keys cut." Tech stuffs paper in pocket. Tech gets home, tries to remember which job that was, files paper in a folder (somewhere). 3 months later, building owner asks: "Can you give me a list of all master keys cut in the last 90 days? We want to audit for security." Manager digs through folders, finds some papers, loses some, reconstructs a fragmented list. List is incomplete (missing 2 jobs). Building owner is concerned: "You cut keys without logging them?" Manager: "No, we logged everything, must be filing error." Trust is damaged. Later, building security is breached (someone got unauthorized copy of master key). Building owner launches investigation, demands: "Show me the restricted-key log, prove who cut those keys." Manager can't find complete log. Liability issue: building owner sues (locksmith failed to maintain audit trail, loss is $50k building security damage). Locksmith's E&O insurance has $1M limit but $5k deductible, claim is denied if audit trail is incomplete. Real issue: restricted-key logging was manual (paper form in tech's pocket = chaos + zero audit trail = compliance liability + customer distrust). Spreadsheet-based inventory (manager uses Excel to track key blanks: "Brass stock: 200 units", "Dimple stock: 50 units", "Nickel stock: 100 units"). Every shift, tech is supposed to update Excel (log usage). Tech A uses 12 brass blanks on day 1, updates Excel ("200 → 188"). Tech B uses 8 brass blanks on day 1, doesn't update Excel (too busy, forgot). Manager checks Excel at end of day: shows 188 brass blanks. Reality: 180 (188 − 8 missing). Manager thinks stock is 188, but actual stock is 180 (8-unit blind spot). Over a month: 20 techs × 50% missing logs = 100 blanks untracked = false inventory (manager thinks stock is 200, actual is 100 = 2x overstating inventory). Manager orders new stock based on false data (orders 50 blanks, thinking stock is at 50, when actually stock is at 150). Stock blows up (now 300 blanks, $600 overspend on inventory = cash tied up in unused stock). Conversely: months later, manager assumes stock is 300, doesn't reorder. Stock actually is 50. Manager gets 3 jobs in a row needing brass blanks, techs run out (2 techs can't cut keys, customers are lost). Spreadsheet inventory = perpetual chaos (false data + overstock + stockouts = revenue loss + cash flow bloat). After-hours crew rostering nightmare (24/7 coverage = 5 techs must cover 168 hours/week). Current system: manager uses paper calendar (wall calendar, pencil). Monday: Tech A (8am-5pm), Tech B (5pm-1am, overnight), Tech C (on-call, home, available if emergency after 1am). Tuesday: Tech A off, Tech B off, Tech C (8am-5pm), Tech D (5pm-1am), Tech E (on-call). Rotation repeats. But: Tech B calls in sick (midnight Monday, text to manager: "can't work tonight"). Manager has 1 hour to find replacement. Manager texts Tech E (on-call, asleep): "Can you cover 5pm-1am tonight instead of Wed?" Tech E: "Yeah, I can do tonight, but that means I'm short sleep before Wed morning shift." Tech E works 24h (5pm Mon → 8am Wed, covering both nights + half of Tue shift), is exhausted, makes mistakes (forgets to log job, charges customer wrong amount). After-hours quality drops (exhausted tech = slow service, unhappy customer). Plus: manager has no visibility (4 techs are asleep, on-call coverage is loose, if 2 techs call in sick = no backup = business fails to respond to emergency calls = lost jobs). ROI-negative: $2k–3k/year in penalty rates (overtime pay for emergency callouts, 50%+ surcharge beyond base pay) + lost jobs due to no coverage (est. 2–3 emergency jobs per month at $250–400 ea = $500–$1.2k/month lost revenue = $6k–14.4k/yr). Custom platform solves: Real-time dispatch + geolocation (tech opens app, job comes in (customer is locked out, location: 50 Oxford St, Paddington, 2 km away). System checks all techs: Tech A (15 km away, job ends 12:05pm, ETA to customer 12:20pm), Tech B (28 km away, job ends 12:10pm, ETA to customer 12:38pm), Tech C (3 km away, job ends NOW, ETA to customer 12:08pm, CLOSEST). System auto-offers dispatch to Tech C: "Lockout job, 2 km away, customer waiting, $400 job, accept [yes/no]?" Tech C: "Yes, on way." System sends GPS route (live traffic, turn-by-turn). System notifies customer: "Tech arriving in 8 minutes." Tech arrives 8 min later (customer is happy, job closes in 20 min). Revenue: $400 captured. Previous system (phone call to manager, manager calling techs): same job would take 25 min to dispatch (manager takes 2 min to pick up, calls tech A who doesn't answer, calls tech B who answers, tech B is 28 min away, customer gets offered 28 min wait). Customer calls competitor, loses job. New system: dispatch is instant (geolocation + real-time availability = 8 min response, customer is satisfied, job is won). Revenue impact: 2–3 emergency jobs per week captured (8 jobs/month × $400 = $3.2k/month = $38.4k/yr incremental revenue for typical shop). Job queue visibility (manager's dashboard shows: [3 jobs pending (Tech C assigned, ETA 12:08pm; Tech D assigned, ETA 1:30pm; Tech E assigned, ETA 4:15pm)]. Jobs that are "no assigned tech yet": 1 job (lockout, customer is in vehicle, 5 km away from all techs, ETA if assigned = 25 min, customer is angry). Manager can see: "Job #3 is at risk, customer is unhappy." Manager calls Job #3 customer: "I can get a tech to you in 25 min, or offer $50 discount if you can wait until 1pm when we have closer coverage." Customer: "1pm works, thanks, apply discount." Manager applies $50 discount (loses $50 margin but keeps $350 job). Alternative dispatch = customer calls competitor, loses entire job ($400). Manager visibility is high (real-time queue, customer satisfaction = proactive problem-solving). Real-time key blank inventory (tech arrives on job: system shows "van inventory: 20 brass blanks, 10 nickel blanks, 8 dimple blanks, 5 restricted blanks." Tech cuts 3 brass blanks. Tech scans completed keys (barcode), system auto-updates: "van inventory: 17 brass blanks remaining." Inventory is live (zero lag, zero guessing). Manager checks dashboard: "brass blanks across all vans: Tech A van 17, Tech B van 19, Tech C van 22 = 58 total fleet inventory." Manager sees: "reorder point alert: brass blanks fleet-wide are at 58, reorder point is 60, place order now." Manager places order (50 new brass blanks). Order arrives 2 days later. Inventory is managed automatically (no spreadsheet errors, zero stockouts, zero overstock). Key blank accuracy per job (tech gets job: needs 5 brass blanks. System checks: "fleet inventory: 58 brass blanks available. Your van: 17 available. Enough? Yes." Tech proceeds. If system had shown "3 available," tech would know in advance to either (A) call manager for stock refill, or (B) ask customer if they can wait for restocking. Proactive planning = zero surprise stockouts).). Restricted-key system register + compliance logging (commercial client, master-key system). Tech gets job: cut 3 master keys. System opens form on tech's phone: [customer name (required), customer ID type (required: DL, passport, corporate card), ID number (required), building/system ID (required), number of keys to cut (required), authorization notes (optional)]. Tech fills in: "Jane Smith, DL 1234567, building lock#4521, 3 keys, authorized by building manager." System auto-logs: date + time + tech name + GPS location (proof tech was on-site) + form details. System auto-stores in restricted-key register (searchable, audit-ready). System auto-generates audit report (any date range): "Restricted keys cut 2026-01-01 to 2026-06-13: total 12 records, all authorized, no gaps." Building owner can download report anytime (compliance is automatic, audit trail is perfect). Liability = zero (full documented trail, can prove every restricted key was logged + authorized). Crew rostering + shift coverage (5 techs, 24/7 coverage). System shows weekly schedule: (Mon: Tech A 8am-5pm + Tech B 5pm-1am + Tech C on-call; Tue: Tech C 8am-5pm + Tech D 5pm-1am + Tech E on-call; repeat). Tech B calls in sick (midnight Mon). Manager gets notification. System shows: "Overnight Mon-Tue is uncovered. On-call tech C is assigned, but Tech C is already working 8am shift Tue (24h overlap = not sustainable). Recommendations: (A) call Tech E to cover Mon 5pm-1am (Tech E is off-duty, compensate with time-off later), or (B) offer Tech B's shift as paid overtime to available tech." Manager chooses (A), texts Tech E: "Can you cover Mon 5pm-1am? Compensation: time-off Wed." Tech E: "Yes, I'll cover." System updates schedule instantly (all other techs see updated roster, customer-facing booking system shows coverage is available). Coverage = continuous (no gaps, no surprises, crew fatigue is managed). After-hours penalty rates are controlled (manager sees: "Tech E worked 24h Mon-Tue = 8h overtime = cost $600 (time-and-a-half). Benefit: no lost emergency jobs Monday night (estimated 1–2 jobs = $400–800 revenue). Net = +$200 profit by having coverage"). Data-driven rostering decisions = sustainable crew scheduling.

Six Features Custom Locksmith Platform Delivers

1. Real-Time Geolocation Dispatch + Instant Job Assignment

Emergency call comes in: customer locked out at 50 Oxford St, Paddington (2 km radius, 5 techs in fleet). System auto-calculates: Tech A (15 km away, current job ends 12:05pm, ETA to customer 12:20pm), Tech B (28 km away, ETA 12:38pm), Tech C (3 km away, current job ends 12:00pm, ETA 12:08pm, CLOSEST). System auto-offers dispatch to Tech C. Tech C accepts (tap yes on phone). System sends SMS to customer: "Tech arriving in 8 minutes." Tech C opens phone, sees GPS route (live traffic, turn-by-turn navigation). Tech C arrives exactly 8 min later. Customer is happy (immediate response = premium service perception = $400 job secured). Revenue impact: 2–3 emergency jobs per week captured = $3.2k–4.8k/month = $38.4k–57.6k/yr incremental. Response time drops from 25 min (manager phone calls) to 8 min (instant app dispatch).

2. Real-Time Key Blank Inventory Tracking + Reorder Automation

Tech starts shift, checks phone: "van inventory available: 20 brass blanks, 10 nickel blanks, 8 dimple blanks, 5 restricted blanks." Tech gets job (needs 3 brass blanks), cuts keys. Tech scans completed keys (barcode), system auto-updates: "brass blanks: 17 remaining." Manager's dashboard shows fleet-wide: "total brass blanks: 58 across 5 vans. Reorder point: 60. Status: below reorder threshold." Manager places order immediately (50 new blanks, arrives in 2 days). Inventory accuracy: 100% (no spreadsheet errors, no guessing stock levels). Stockout prevention: automatic (system alerts when hitting reorder point, order is placed before vans run dry). Cost savings: no overstock (manager doesn't buy "just in case" because they trust system, cash tied up in excess inventory drops by 40%, = $3k–5k freed up annually). Job confidence: tech never gets a surprise "out of stock" mid-job (proactive checks = smooth customer experience).

3. Restricted-Key System Register + Compliance Logging

Commercial client needs master keys cut (restricted-key system, AU regulatory requirement). Tech gets job. System opens form on phone: [customer name (required), ID type + ID number (required), lock system ID (required), number of keys (required), authorization notes]. Tech fills: "Jane Smith, DL 1234567, system#4521, 3 master keys, authorized by building manager John Doe." System auto-logs: date + time + tech GPS location (proof of on-site work) + all form fields. Entry is stored in restricted-key register (searchable, audit-ready). Manager can pull audit report anytime: "All restricted keys cut 2026-01-01 to 2026-06-13: 12 records, 100% authorized, zero gaps." Building owner downloads report for compliance audit. Liability = eliminated (full documented trail, every key is logged + authorized). Regulatory compliance: MLAA standards + building security requirements = automatic (no paper forms in pockets, no lost logs, zero compliance risk).

4. Smart Job Queue Management + Real-Time Visibility

Manager's dashboard (Tuesday 2pm): "pending jobs: 3 assigned (Tech C ETA 2:15pm, Tech D ETA 1:30pm, Tech E ETA 4:15pm), 1 unassigned (lockout job, customer in vehicle, 5 km from nearest available tech, ETA if assigned 25 min, customer satisfaction risk = high)." Manager sees immediate problem: unassigned job has frustrated customer. Manager calls customer: "I can get tech to you in 25 min, or offer $50 discount if you can wait until 1pm when we have better coverage." Customer: "1pm works." Manager applies discount, keeps $350 job (loses $50 but avoids losing entire $400). Alternative: no visibility = customer calls competitor = $400 lost completely. Manager visibility = proactive problem-solving = job retention. Queue transparency prevents revenue loss (high-risk jobs are flagged immediately, manager can intervene before customer calls competitor).

5. Crew Rostering + After-Hours Coverage Automation

5 techs cover 24/7 schedule. Weekly roster: Tech A (Mon 8am-5pm), Tech B (Mon 5pm-1am, on-call), Tech C (Tue 8am-5pm), Tech D (Tue 5pm-1am), Tech E (on-call Tue/Wed). Tech B calls in sick (Mon 11pm). Manager gets alert. System shows: "Overnight Mon-Tue uncovered. Tech C is working Tue morning (would cause 24h fatigue if covering Mon night too). Options: (A) assign Tech E to Mon 5pm-1am (Tech E off-duty, compensate with time-off), (B) pay Tech B overtime if they can work (already out sick, not viable)." Manager chooses (A): texts Tech E, "Can you cover Mon 5pm-1am? We'll give you Wed off." Tech E agrees. System updates roster (all techs see updated schedule, customer-facing booking shows coverage is continuous). Coverage = always available (no "sorry, no one available" responses). Penalty costs are controlled (manager calculates: Tech E 24h = 8h overtime @ 1.5x = $600 cost vs 1–2 emergency jobs @ $400–800 = $400–800 revenue gained = net +$200 profit by having coverage). Crew fatigue is managed (system prevents double-shifting crew members on back-to-back days, sustainable scheduling). Tech satisfaction increases (visible roster = clear expectations, no surprise callouts after fatigue, scheduling feels fair).

6. Mobile Job Forms + Photo + Notes + Real-Time Sync

Tech arrives on-site, opens job on phone. System shows: [job summary: lockout residential, 50 Oxford St Paddington; customer contact: Jane Smith 0412 345 678; lock details: 3-lever deadbolt, standard brass blank; estimated time: 20 min]. Tech takes photo (lock close-up, customer ID proof for restricted-key jobs). Tech makes notes (any issues, parts used, customer feedback). Tech completes job (tap "mark complete"). System auto-syncs (data is uploaded if WiFi/data available, or queued if offline, synced when connection returns). Manager sees job marked complete (real-time, no "forgot to submit timesheet" delays). Invoicing is auto-generated (job details + notes + photos auto-populate invoice, sent to customer immediately). Photo archive is accessible (any job can be looked up 6 months later, photos + notes are searchable, customer disputes are easy to resolve with proof). Mobile forms eliminate paperwork chaos (no lost notes, zero data entry errors, all records are digital + searchable).

Australian Locksmith Context + Regulatory

Australian locksmith market: 15k+ licensed locksmiths, $2B+ annual market (residential lockouts, key cutting, master-key systems, commercial access control). Typical business: 5–10 person shop, 24/7 emergency response (locksmiths are on-call 24h because lockouts happen anytime). Key regulations: MLAA (Master Locksmiths Association of Australia) membership is industry standard (not mandatory legally, but customers expect it, insurance underwriters require it, $500–800/yr membership). Restricted-key regulations: AU law requires locksmiths to log ALL restricted-key cutting (master keys, high-security blanks, system keys). Log must include: date + time + customer name + customer ID (photo ID verified) + lock system ID + number of keys + authorization proof. Log must be kept for 12 months (audit trail). Building owners, property managers, and security firms audit these logs annually (compliance check). Lockout frequency: varies by season, spiked post-storms (hail events, wind damage = locks jam = emergency lockout calls spike), summer holidays (holiday homes, vacation rentals get locked out more = Airbnb market drives volume in coastal regions). Cash flow: most jobs are $150–500 emergency callouts (paid on-site, immediate cash). Some jobs are commercial contracts (key cutting for building systems, quarterly restocking = invoice, net 30 payment). Average job value: $250–350 (lockout = $250–300, key cutting = $50–100, access control = $400–800). Revenue per technician: $300–500/day × 5 working days = $1.5k–2.5k/week per tech × 4 techs = $6k–10k/week for typical 5-person shop. After-hours callouts: 24/7 emergency coverage is mandatory (can't say "sorry, closed at 5pm" when customer is locked out midnight). On-call coverage = crew must rotate through overnight shifts + be available for callback. On-call fatigue = tech burnout = high turnover (avg 2–3 techs leave per year, replacement cost $10k–15k each = $20k–45k/yr turnover expense). Biggest pain points: slow emergency dispatch (manual phone calls = 20–30 min lag, competitors with instant dispatch win jobs), key inventory chaos (stockouts mid-job = customer waits, tech is frustrated, revenue is lost; overstock = cash tied up in unused blanks), restricted-key compliance liability (paper logs get lost, customers audit finding gaps, building security breaches = locksmith gets sued, E&O insurance denies claim if audit trail is incomplete), crew scheduling chaos (manual roster = no backup if tech calls in sick, manager scrambles, coverage gaps = lost emergency jobs), and crew burnout (after-hours on-call fatigue = techs quit, turnover cost = $20k–45k/yr for typical shop). Conservative estimate of hidden losses: emergency dispatch lag = 2–3 jobs lost per week @ $300–400 = $600–1.2k/week = $31.2k–62.4k/yr; inventory stockouts = 1–2 jobs per week lost + customer dissatisfaction = $2k–3k/week = $104k–156k/yr; compliance liability = average 1 building audit per shop per year finding gaps, settlement/insurance deductible = $5k–15k/yr; crew turnover = 2–3 techs per year @ $10k–15k each = $20k–45k/yr. Total hidden losses: $156k–278k/yr (conservative).

Six FAQs

How does the system handle jobs where the locksmith can't complete immediately (parts need ordering, rescheduling)?

Tech arrives on-site, assesses job: "customer needs new locks installed, locks are specialty European locks (not in stock, 3-day lead time from supplier)." Tech talks to customer, agrees to schedule installation for 3 days out. System records job status: "locked estimate provided ($800 total), pending parts order, scheduled for 2026-06-16." System auto-sends customer SMS: "We've quoted your new locks at $800, we're ordering them now, installation scheduled for 2026-06-16. We'll confirm 24h before arrival." System auto-creates part-order in procurement: "order 2x European lock XYZ from supplier ABC, needed by 2026-06-15." Manager sees upcoming parts arrival (can plan tech assignments 3 days out, no last-minute scrambles). On day-of, tech installs locks, completes job, invoices $800. Rescheduling is transparent (customer expectations are set upfront, system prevents surprise gaps, manager has visibility).

Can the system handle after-hours/holiday rates (penalty rates for night calls + weekends)?

Yes. System has rate cards: standard Mon-Fri 8am-5pm = base rate $300 lockout. After-hours Mon-Fri 5pm-8am = 1.5x rate = $450. Weekend = 1.5x rate = $450. Public holiday = 2x rate = $600. Customer calls at midnight (Wed), requests lockout service. System shows quote: "$450 (after-hours rate)." Customer can (A) accept $450 immediate, or (B) wait until morning for $300 rate. Customer chooses (A), pays $450. Tech is dispatched, arrives 10 min later, completes job. Invoice shows: "after-hours lockout service 2026-06-13 00:45, rate $450, time on-site 20 min, total $450." Manager sees after-hours revenue is tracked separately (knows profitability: cost to pay tech 1.5x rate = $45–60, margin on $450 = $390–405, healthy profit). System auto-calculates crew penalties (enforces labor law compliance: night shifts must have penalty rates, system prevents underpaying crew). Rates are configurable (manager can set different rates per region, per job type, per season).

How does the system integrate with customer booking/scheduling (online calendar)?

Yes. System has customer-facing booking portal. Customer visits website, sees "Book Now," clicks, selects: [service type: lockout / key cutting / master-key system, address, phone]. System checks availability: "available times tomorrow: 9am, 10:30am, 2pm, 4:15pm." Customer chooses 10:30am. System confirms appointment, sends SMS + email with tech name + phone + ETA. Tech receives job alert (app notification). Manager sees booking (can optimize dispatch, send customer confirmations, track pipeline). Day-of, tech drives to appointment, system provides GPS route. Tech arrives on-time. Customer sees live ETA (app shows "tech arriving in 5 min," reduces customer anxiety). Integration = reduced phone tag (less back-and-forth: "when can you come?" "we have availability Wed at 2pm," etc.), more jobs completed (customers book directly instead of waiting for manager to call back), higher conversion (professional booking interface = customer feels confident in business).

What if a tech needs to cancel a job or reassign it mid-shift?

Tech is mid-shift, realizes they have a family emergency (need to leave immediately). Tech opens app, marks job status: "emergency, need reassignment." System immediately alerts manager (notification: "Tech D marked urgent reassignment required"). System checks: remaining available techs, their locations, their current job status. System suggests: "Tech E is 3 km away, current job ends 2:45pm, could reassign. ETA to customer: 3:00pm." Manager approves reassignment (one tap). System updates customer SMS: "Your original tech had an emergency, we're sending Tech E instead, ETA 3:00pm. Your appointment is still on schedule." Tech D is marked "emergency leave," system calculates: tech worked 4h of 8h shift = leave is paid as 4h work (fair to tech, doesn't punish for emergency). Tech E gets reassigned job (clear in app, GPS route generated). Job continues (no customer impact). Manager has visibility (knows which jobs might slip, can make proactive adjustments). Reassignment is fast (system handles it, not manager scrambling with phone calls).

How does the system handle job disputes (customer says "locksmith overcharged" or "didn't complete work")?

Tech completes job, marks "done" in app. System auto-generates invoice (photo of lock, notes: "removed broken lock, installed new 3-lever deadbolt, tested operation"), sent to customer immediately. Customer receives invoice, sees photo + notes, confirms completion (tap "approve"). Payment is processed. 2 weeks later, customer calls: "I was overcharged, you said $300 but charged $320." Manager pulls job record (all in system): photo + notes + time on-site (20 min) + rate applied (standard $300 + $20 surcharge for after-hours arrival at 8:15pm, warranted). Manager shows customer the breakdown: "standard lockout $300 + after-hours surcharge $20 (you called at 8:15pm, after-hours rate applies per quote). Total $320 is correct." Customer sees transparent breakdown, dispute is resolved (no disagreement if data is clear). Alternatively: customer says "your tech didn't fix the lock, it still jams." Manager pulls photos from job (close-up of lock installed), notes say "tested operation, lock turns smoothly." Manager says "photo shows lock was working, but let me send tech back to recheck." Tech returns, realizes: lock is actually fine, customer just doesn't know how to operate it (needs gentle turn, not force). Tech shows customer, issue resolved. Photo + notes = proof (disputes are resolved faster, customer satisfaction is protected, legit complaints are addressed).

Can the system track tools + equipment across techs (van contents, tool audits)?

Yes. System has equipment checklist. Each tech does daily van audit (morning before shift): [picks lock set: check, bump keys: 5 pieces check, lock-picking rake set: check, key blank assortment: present, cutting machine: operational, GPS device: charged]. Tech scans checklist, marks all items "present." System logs checklist (timestamp). At end of shift, tech does closing audit (confirms all tools are accounted). System tracks: which tech has which equipment, when it was last serviced (lock-picking rake set serviced 2026-05-15), when it needs maintenance (next service due 2026-07-15). Manager gets alert: "lock-picking rake set is due for maintenance in 30 days, schedule now?" Manager schedules maintenance. Equipment loss is prevented (tech can't "walk off" with company tools if they're logged daily). Tool accountability = reduced theft, reduced losses. Emergency preparedness = if tech calls in sick, manager knows exactly which backup tech has the equipment needed for the day's jobs. Equipment ROI = manager can see: "lock-picking set cost $500, used by 4 techs, across 3,000 jobs/year, cost per job = $0.17, worth it."

The Bottom Line

ServiceM8 ($1.2k–1.8k/yr) or Tradify ($1.8k–3k/yr) or Fergus ($2.4k–4.8k/yr): job dispatch, crew scheduling, invoicing, payment processing. Plus slow emergency dispatch (manual phone calls = 20–30 min lag, 2–3 jobs lost per week = $31.2k–62.4k/yr revenue loss). Plus key inventory chaos (spreadsheet guessing = stockouts + overstock, $2k–3k/week lost productivity = $104k–156k/yr). Plus restricted-key compliance liability (paper logs get lost, audit gaps = building owner distrust, settlement costs $5k–15k/yr). Plus crew scheduling chaos (manual roster = coverage gaps, lost emergency jobs, tech burnout = $20k–45k/yr turnover). Plus no after-hours rostering (penalty rates not tracked, crew fatigue is high, tech quit rate is 30–40% per year). Total hidden losses: $156k–278k/yr. Custom platform: $120–160k upfront build (real-time dispatch, geolocation, key inventory tracking, restricted-key register, crew rostering, mobile forms, photo sync). Year 1 cost: $140k build. Year 2+: $2k/yr hosting + 0.5% of revenue for integrations = $2k + $2.5k (assuming $500k annual job revenue) = $4.5k/yr. Break-even: payoff savings (emergency dispatch speedup 30 min → 8 min = 2–3 extra jobs captured per week = $600–1.2k/week = $31.2k–62.4k/yr; key inventory accuracy = 1–2 jobs lost per week avoided + overstock reduced 40% = $50k/yr savings + $2k–3k/week productivity gain = $104k–156k/yr; compliance register = restrict-key liability eliminated = $5k–15k/yr risk removed; crew turnover = better scheduling = retention improves 50%, turnover drops from 2–3 per year to 1 per year = $10k–15k savings; after-hours coverage optimization = better rostering = penalty costs managed efficiently = $10k–20k/yr in payroll optimization). Total Year 1: −$140k build + $93.6k–109.2k dispatch + $127k–169k inventory + $10k compliance + $10k–15k retention + $10k–20k rostering = −$140k + $250.6k–313.2k = +$110.6k–173.2k profit. Year 2: pure $150k–200k recurring (vs custom platform cost $4.5k/yr = 33–44x ROI). Ready to build a custom locksmith platform? Check Aidxn's custom software packages, or book a call to discuss your locksmith business (how many techs?, jobs per week?, avg job value?, current SaaS overhead?, biggest dispatch bottleneck?, key blank stock levels?, restricted-key system complexity?, after-hours coverage challenges?, crew turnover rate?, MLAA compliance status?, biggest pain point right now?).

Let us make some quick suggestions?
Please provide your full name.
Please provide your phone number.
Please provide a valid phone number.
Please provide your email address.
Please provide a valid email address.
Please provide your brand name or website.
Please provide your brand name or website.