Clear numbers.
Aligned expectations.
No interpretation.
SignalOps is operations software for authorized retail dealers. Reps log sales on the floor. The store view updates in real time, and ownership sets policy from the same record. Voice, internet, accessories, and every other goal stay visible without side math.
Post the sale once.
SignalOps keeps one row from the counter to the district view.
Reps post shorthand from the floor. The parser tokenizes the string. It validates the row against the right goal types and checks the 30 minute duplicate window. If the store is offline, the row stays on the device until background sync can send it.
Post the row in shorthand
Type 2v 1u 1 fiber500. The parser turns the string into line items so the rep stays at the counter.
Run the eligibility checks
The row is checked for internet eligibility and FirstNet eligibility. Lead entry is verified. Duplicate detection uses a 30 minute window.
Count it in the open month
When the month is OPEN the row counts toward store and user goals. Sensitive edits write to audit_log. That includes voids, month locks, PIN resets, and district changes.
Keep working when the store drops offline
SignalOps keeps the row on the device until service comes back. The row syncs then. If two copies disagree, the live record wins.
Authorized retail dealer work stays in one app.
From the parser to the district view.
A rep sale feeds rep credit, store totals, district rollups, and admin policy from the same write. Users who work more than one store change context in one tap.
The parser speaks dealer shorthand
Type 2v 1u 1 fiber500. The parser turns shorthand into line items. One write feeds the ledger the store is reading.
Sensitive changes stay on the record
The audit log records transaction edits and voids, month locks, PIN resets, and district changes.
Switch stores in one tap
Users with access to more than one store change context without starting over. The store month stays attached to the active context.
Offline first
Sale entry stays on the device when service drops. It syncs the moment the store comes back. If two copies disagree, the live record wins.
Month state is explicit
Months stay OPEN or LOCKED. Store managers control the switch.
Goals at store or rep level
Set monthly targets by store or by rep. Goal types cover Voice, AIA, Fiber, UPS, Data, PPD, TV, CRU, FirstNet, TPU, Revenue, Accessories, and NewAct.
Eligibility checks on every row
Internet eligibility and FirstNet eligibility are checked on the row. Lead entry is required, and duplicate detection uses a 30 minute window.
Rep, store manager, district manager, admin.
Each one gets the right view.
SignalOps keeps one record. The view changes by role.
Post the sale and see your count
Built for the rep on the floor.
- Post from a phone
- Track store or user goals
- See commission on the posted row
- Keep working offline
Run the store from the live view
Store managers see what changed today and coach from the real row count. They control whether the month is OPEN or LOCKED.
- Coach from the live row count
- Edit store goals for the month
- Void or correct a transaction
- Reset PINs and lock the month
Compare every store in the district
District managers read across every assigned store. They compare rankings and follow month state from one screen.
- Read across the full district
- Compare goal pace by store
- Open the same row each store is reading
- Watch month state by store
Set access and org policy
Admins manage users and district assignments. They also control org settings that shape access.
- Manage users and store access
- Move stores between districts
- Review login failures in security_events
- Trace sensitive changes in audit_log
Store switching is a platform feature for users who work more than one assignment. The active context follows the user from store to store.
Every query stays scoped to the store.
Sensitive writes land in audit_log.
SignalOps treats operational data the way you treat the floor. Carefully, with a paper trail. Queries stay parameterized, the session is checked on every request, and each role sees only the store it is reading.
- Encrypted in transit and at restOperational data is protected on the wire and in storage. Receipt images are protected the same way.
- Queries stay parameterizedReads and writes use parameter binding, not string-built SQL. Standard practice, written into the way the app talks to its records.
- Session is checked on every requestThe server validates the session before it reads data or accepts a write. Stale sessions are cleared at the edge.
- Role decides what you can touchRep, store manager, district manager, and admin each have a defined scope. The same record is filtered to the role reading it.
- Every query stays scoped to the storeReads and writes stay inside the store the user is currently on. Cross-store access is refused.
- The trail covers the sensitive stuffTransaction edits and voids, month locks, PIN resets, and district changes are written to the audit trail. Login failures are tracked separately.
The card keeps the event, actor, store, and payload together so a store can trace a sensitive change later.
Dealer FAQ
What is SignalOps?
SignalOps is operations software for authorized retail dealers. It covers sales tracking, goal management, eligibility checks, and store reporting.
How is SignalOps different from the spreadsheet we use now?
SignalOps keeps sales tracking, goal math, eligibility checks, and month state in one record. The store and district are reading that same row instead of passing a spreadsheet around.
Do reps need an account before they log sales?
Yes. An admin creates the user and store access first. The rep signs in with an identifier and a PIN or password.
What if a rep is offline?
Entries queue on the device. They sync in the background when the connection returns, and the server wins if two copies disagree.
Who controls OPEN and LOCKED months?
Store managers do. They set the month state for the store, and the audit log records when it changed and who changed it.
How do district managers see across stores?
A district manager has read access to every store in the district. SignalOps rolls the numbers up at district level and keeps the store rows visible underneath.
See your store rules inside SignalOps before rollout.
SignalOps is built for the way you actually run your sales floor. Reps land at sale entry. Every transaction is auditable. Every month closes on the same rhythm.