One Partner. Total Security. — Operations System
(928) 782-1551 · 1275 S Pacific Ave, Yuma, AZ 85365
Serving Arizona since 2004
⚡ AI-Built Demo ⛁ connecting…
0
Open Tickets
0
Active Projects
0
Unbilled Billable Hrs
0
Open Leads
0
True Hrs This Week
$0
Invoiced + Paid

Project Hours — Quoted vs Actual actual = true hours from tickets

Recent Tickets

TicketCustomerTechTrue / BilledBilling

Customer / Lead Master Database search name, contact, phone, email, address

ID / CompanyContactPhone / EmailType · StatusCreated

📨 Sales Inbox web form + email inquiries → one-click lead

➕ New Customer / Lead controlled form — techs use this via the agent too

Lead pipeline: New → Contacted → Quoted → Won/Lost. Customers: Active / Inactive. Leads auto-convert to Active customers on first dispatch.

Quote Management QUO-YY-#### · Accepted quotes convert to projects with one click

QuoteCustomerAmountHoursDateStatus

➕ New Quote

Draft → Sent → Accepted/Declined. Accept & Convert creates the project with the quoted hours and links the quote reference.

Contract & SLA Management SLA targets surface on every ticket for covered customers

ContractCustomerTypeMonthlyTermSLA response (P1/P2/P3)Status

➕ New Contract

Schedule — 7-Day Board dispatched tickets + project start dates · click a chip to open · calendar sync on roadmap

Unscheduled / Open Work Queue open tickets — what techs will see in Telegram each morning

Task Management internal to-dos linked to projects, quotes, or tickets

TaskAssigneeDueLinked toCreated

➕ New Task

IT Documentation · Knowledge Base · Runbooks one searchable library, three document types

DocTypeCustomerTagsUpdated

➕ New Document

Runbooks are what the Telegram agent will read back to techs on site ("how do I recover this NVR?") — same library, conversational delivery.

Projects PRJ-YY-#### · reopen any completed project for warranty / follow-up

ProjectCustomerLead TechQuotedActualRemain% UsedStatus

➕ New Project Request techs can request via agent; office approves

📋 Work Order

👷 Technician Roster cost rate = internal payroll · bill rate = customer-facing

TechnicianPositionCost rateBill rateStatus

Dispatch Preview

Select a customer and at least one technician.

Dispatch creates an open ticket per tech (TKT-YY-####) and, in production, pushes the work order to their Telegram. The tech closes it out from the truck — via this site's mobile-friendly ticket form or conversationally with the agent.

Ticket Log every time entry = unique TKT-YY-#### · edit = logged correction

TicketDateTechCustomerTypeTrue / BilledStatus

⏱ New Time Entry / Ticket mobile-friendly tech form

⚖️ This Entry — True vs Billed

True time (payroll)
0.00 hr
Billed time (customer)
0 hr
Rounding uplift
Labor cost (true × cost rate)$0.00
Labor revenue (billed × bill rate)$0.00
Entry margin$0.00

Billing Report Filters billing status persists — stop mid-billing and come back later

Billing Report

TicketProjectCustomerTechTrue hrsBilled hrsMaterials UsedWork DescriptionBillableBilling Status
Invoice requires the Customer filter set to one customer.

⚙️ Rate Settings

Timesheet Report payroll uses TRUE fractional hours

Roadmap: PTOHolidaysOT after 40 hrs/wkPay-period presets
TechnicianPositionTotal Hours (true)Billable HoursNon-Billable HoursBilled to CustomersEst. Labor Cost

Detail tickets in selected range

TicketDateTechCustomerWork typeTrueBilledBillable

Report Filters applies to all reports below · submitted tickets only

0
True Hrs (payroll)
0
Billed Hrs (customer)
+0
Rounding Uplift
$0
Revenue
$0
Labor + Mat. Cost
$0
Gross Margin

Revenue & Margin by Technician

TechnicianTrueBilledUplift $RevenueCostMargin

Revenue by Customer

CustomerTicketsBilled hrsRevenueMargin

Hours by Work Type billable vs non-billable mix

Work typeTicketsTrue hrsRevenueBillable

Pipeline & Project Health

ProjectQuotedActual% UsedStatus

The conversational path for ticket close-out. The tech gets the dispatched work order in Telegram and the agent collects everything the ticket form requires — start/end time, work type, materials (required, N/A allowed), description, status after visit — logging true fractional hours for payroll and rounded-up billed hours automatically. Same database as the web form.

DT
DiegoTech Field Agent
bot

🧠 Live extraction

Waiting for conversation…

📦 Staged ticket payload → QuickBooks / Halo

// JSON payload will appear here

DiegoTech Operations — Production Architecture

This demo implements the workflows validated in the Google Sheets/Forms/Apps Script prototype on a scalable footing. Full technical scope in TELEGRAM_AGENT_SCOPE.md.

📞
Lead / CustomerSearched or created in master DB (controlled form, also tech-accessible)
📁
Project or Service CallPRJ-YY-#### with quoted hrs, scope, status history — or one-off ticket
🚚
DispatchTech from roster (position, cost/bill rates) · work order → Telegram
🎫
Ticket TKT-YY-####Web form or agent: times, work type, materials (req'd), description, visit status
⚖️
Dual timeTrue hrs → payroll · Billed hrs (round-up) → invoice · uplift tracked
📗
Billing → QuickBooksPersistent billing statuses; draft invoices after office approval

Platform Coverage Matrix the 17 target areas → where each lives today

AreaWhere in the appStatus
Service desk / ticketingTickets / T&E + Dispatch — TKT-YY-#### lifecycle, corrections, visit statusesLive
Lightweight CRMCRM & Sales — lead pipeline (New→Won/Lost), customers, created-by auditLive
Sales inboxCRM & Sales — web/email inquiries, one-click convert to leadLive
Quote managementQuotes — Draft→Sent→Accepted/Declined, one-click convert to projectLive
Project managementProjects — quoted/actual/remaining hrs, status history, reopen for warrantyLive
Contract managementContracts · SLA — terms, monthly value, covered servicesLive
SLA managementContracts · SLA — P1/P2/P3 response targets, auto-surfaced on tickets for covered customersLive
SchedulingSchedule — 7-day board + open work queueLive calendar sync roadmap
Task managementTasks — assignees, due dates, linked to PRJ/TKT/QUO recordsLive
IT documentationDocs · KB — per-customer network maps, credentials pointers, environment docsLive
Knowledge baseDocs · KB — searchable articles with tagsLive
Unified runbooksDocs · KB — Runbook type; agent reads them to techs on site (phase 2)Live
Business reportingReports — revenue/margin by tech, customer, work type; uplift; pipeline; project healthLive
Invoice managementBilling — persistent statuses, filtered reports, branded draft invoicesLive
Time tracking (QB Online)Dual-time engine live everywhere; true hrs → QBO TimeActivityEngine live · QBO sync scoped
Automated billing (QB Online)CSV export today; draft-invoice push via QBO APIScoped — phase 3
Service automationRules engine: warranty→non-billable, lead auto-convert on dispatch, round-up billing, materials-required gate, SLA badges, Telegram agent close-outLive · expanding

Business rules encoded

  • IDs: tickets TKT-YY-#### · projects PRJ-YY-#### · customers/leads CL-YY-####, all sequential per year.
  • Billable logic: Warranty, Admin, Training, and DiegoTech Internal work types default non-billable; everything else billable (overridable per ticket).
  • Dual time: true fractional hours (payroll, project actuals, costing) and billed hours rounded up to the next whole hour (invoice).
  • Materials required on every ticket — "N/A" accepted, blank rejected.
  • Billing statuses persist (Not Invoiced → Pending → Invoiced → Paid) so billing can be done in sittings.
  • Projects reopen for warranty/follow-up; every status change is kept in history.
  • Corrections: ticket edits are flagged and timestamped, never silently overwritten.

Roadmap (placeholders visible in app)

  • Scheduling / calendar sync — dispatch board → Google Calendar/Outlook; tech sees open work queue in Telegram.
  • Mobile app — this site is already mobile-friendly; a PWA or AppSheet-style wrapper is the upgrade path.
  • QuickBooks integration — true hrs → TimeActivity, billed lines → draft Invoice, statuses sync back (Invoiced/Paid).
  • Payroll — PTO, holidays, OT after 40 hrs/week, pay-period presets on the Timesheet report.
  • Owner dashboards — margin by tech/customer/work type, rounding-uplift capture, project burn-down.