Argon SR
🚨 Action Needed
— SRs need attention
📅 Today
Created —
Delivered —
Revenue —
📈 This Month
Recent service requests
📋 All Actionable SRs
Loading…
↔ Tap any step below to navigate freely — your data is preserved
01Vehicle
02Issues
03Warranty
04Sign-off
Vehicle identification
Owner
📒🔖 Tally Search (ledgers, serials & transactions)
＋
Job dates & odometer
Job type
☐
Scheduled Service
— leave off if Unscheduled
Job flags (select all that apply — independent of schedule)
Paid Checkup
Accident Job
Repeat Job
📎 Supplement/s Attached
Check if additional sheets are physically attached to this SR
Verification photos
Vehicle verification
VIN Plate
Odo IN
Overall (Before)
VIN and Odo photos required for warranty claims
Service requests / issues
Diagnosis
Additional info
Warranty claim proposed
Warranty claim decision
Approved
Rejected
Other
Estimates
After checkup
After checkup
Chargeable items Part code → price auto-fill
Grand Total₹0.00
Reception condition
Tap codes that apply: D Damage · S Scratch · M Missing · N Not Working
Completion
Job technical records
Before / After — Job related
After Repair
Part Replaced
Job Record
Damage Detail
Odo OUT
Signatures
Customer / Representative — IN
Customer / Representative — OUT
Argon Mobility — OUT
Terms & Conditions: Customer/Owner acknowledges removal of all valuable items before handover to Argon. Responsibility of vehicle during trial/test rests with Customer/Owner. Initial estimates are indicative; actual estimates provided after checkup. For Battery/Range issues, Argon Mobility may use alternate odometer methods — such readings are final. Customer agrees to inspect vehicle before delivery; claims not entertained after delivery. Warranty as per user manual.
Export:
Filter export by date below
📊 My Stats
Loading…
📅 My Day — needs attention
—
Loading…
📈 My Week — throughput (last 8 weeks)
Loading…
💼 My Month — revenue & job mix
Loading…
👥 Top Customers (last 90 days)
Loading…
✏️ My Corrections (last 30 days)
Loading…
🔍 Self-Audit — SRs LAB
Catch your own data-entry gaps before anyone else does. Click any SR to see field-by-field grading.
Week:
SRs in week
—
Avg score
—
Need attention
—
How to read this:
✓ OK
·
? Not Sure (filled, looks odd)
·
✗ Not Okay (filled wrong)
·
— Missing (blank, required at this state)
📅 Schedule Follow-up Audit LAB
Loading…
📋 Today's Report LAB
End-of-day summary for manager. Copy and send via WhatsApp.
SR Lifecycle — State Reference
Click any state below to see what it means and what to do next.
Two paths from Issue Reported
When a customer reports an issue, the SR can take one of two paths depending on whether they want a quote first or just bring the vehicle in. Both paths are valid — choose what fits the customer behaviour. Estimate can also happen during service, not only before.
Path A · Estimate First (customer wants quote before bringing vehicle)
Issue Reported → Checkup Estimate → Checkup Scheduled → Checkup Complete →
Issue Confirmed → Estimate Generated → Estimate OK → Raise for Approval →
Approved → Vehicle In → … (service phase)
Issue Confirmed → Estimate Generated → Estimate OK → Raise for Approval →
Approved → Vehicle In → … (service phase)
When: Customer asks "how much will this cost?" before committing.
Path B · Direct Vehicle In (customer brings vehicle, estimate later)
Issue Reported → Vehicle In → Waiting Job Completion → Service Complete →
Waiting Payment → Ready to Deliver → Delivery Complete → Complete
Waiting Payment → Ready to Deliver → Delivery Complete → Complete
When: Customer just wants the work done — estimate is captured during Service Complete (charge items + grand total). This is the common path.
Closure paths (four distinct types — pick the right one)
Cancel Service: Pre-vehicle-in only. Customer changed their mind before bringing the vehicle in. Goes to Cancel Service Processing → either refund (Cancel Complete) or no refund (Non Issue, can reopen).
Return Without Repair: Vehicle has arrived but customer pulls out before significant work. Diagnostic fee may apply.
Payment Dispute Close: Post-service, customer refuses to pay. Force-close, escalate to management.
Cancelled (Correction): Not a real cancellation. Used when an SR was created by mistake (duplicate, wrong customer, etc.). Use the "⚠ Mark Duplicate" button on the SR panel. This kind never counts toward revenue, cancellation rate, or any business metric — it's only a data-quality marker.
How to tell them apart: Did the customer actually have a service request that didn't go through? → use one of the first three (real cancellations, customer-driven). Did an advisor enter wrong data or duplicate an SR by mistake? → use Cancelled (Correction). The dashboard's "Cancelled this month" counter only includes the first three. Cancelled-correction is tracked separately in Self-Audit so the team can spot data-entry patterns.
Note: The state list above pulls live from
statemachine.js. Anytime the state machine changes, this Help page updates automatically. The Dashboards → State Machine tab shows the same data with live record counts.
Common Questions
How to advance an SR?
Click the SR in Records → the blue state bar at the top shows transition buttons. Move through states in order.
How to change date IN?
Open SR → 📅 Change Date button in header. A reason is required. The original SR is preserved as cancelled, and a new one is created with the correct date and a fresh ID.
What is trial mode?
All data goes to argon-trial.db (completely separate from production). IDs start with T-. Safe to practice — production is never affected.
What counts as Open?
Any SR not in Complete, Cancelled, or Non Issue. Closed = terminal states only.
Can I edit an SR after creation?
Yes — each state unlocks specific fields. Open SR → ✏ Edit This SR button (visible only for states where editing is allowed).
Search Serials
Enter serial number, customer name, or voucher number
Admin
Sort:
Loading…
Loading…
⚠ Date Anomaly Review
SRs created with backdated entries — review weekly
🧾 Unpunched Invoices
SRs closed 3+ days ago with no matching Tally invoice
Loading…
—
Total Users
—
Active
—
Inactive
—
Admins
System
App version loading...
DB location data/argon.db
Zoho Checking…
Sync —
⚙ Dealer Settings
TALLY BRIDGE API KEYS
Create keys in tb.swiftcurrent.in → Admin → API Keys. Admin key: role=admin. Advisor key: role=advisor. Leave blank to use .env fallback.
📱 SS COMMS WEBHOOK KEYS
Keys from ss.swiftcurrent.in. Each webhook has its own key. Leave blank to disable that notification.
⚡ Tally Pipelines
📒 Ledgers
—
🔖 Serials
—
🧾 Transactions
—
📒 Tally Ledger Search
🔧 Technicians
Loading…
📋 Release History
Loading…