Sales and operations, connected on a single record.
Switch between CRM and ATS modes under a single login. Settings, team databases, and client records stay shared, so a won sales lead becomes an active operational client job with no duplicate entry.
pipeline stages
New to Completed, one status vocabulary
login
ATS and CRM share the same client record
audit trail
every route stop edit attributed and timestamped
Unified CRM and ATS Mode Synchronization
The top-right profile dropdown offers ATS and CRM as full application modes, plus Log Out, from the same account. Picking CRM does not open a separate product or a separate login: it swaps the nav from the dispatch-oriented ATS (Dashboard, Feed, People, Prospects, Job Orders, Message, Report, Settings) to the client-acquisition nav below, while Settings, Team and Client records stay the same underlying data.
Dashboard · Feed · People · Prospects · Job Orders · Message · Report · Settings
Dashboard · Feed · Prospects · Leads · Route List · Calendar · Users Tracking · Message · Report · Settings
The Company, Team and Clients screens under Settings are shared by both modes. A client won by a CRM lead becomes the same Client record a dispatcher assigns Job Orders against in ATS mode, and the same reps and locations set up once in Team and Locations apply on both sides — the same Job Orders a staffing agency dispatcher works a candidate against.
Structured Six-Stage Sales Pipeline Tracking
From first contact to a completed contract, every lead in the pipeline reads the same status vocabulary, so sales, ops and finance all know exactly where a deal stands.
Lead Details
Location, Lead Type (e.g. Cold), Date, Company Name/Phone/Fax, Street Address/City/State/Zip, Company Email, Website, Assigned To, Assigned To 2, Sales Manager, Contact Name/Number/Position, Number of Employees, Industry Type, Source Type, Source Type Details.
Other Details
The contract-scoping form: Required Number Of Associates, Shift, Office Servicing, General Labor %, Over Time %, Clerical %, Rollover %, plus Sick Days, Holidays and Vacation, each with a separate Billed figure.
Contacts
A multi-contact table per lead: Full Name, Position, Contact Number, Extension, Email, Client Interest, and a Decision Maker flag, with call and delete actions per row.
Appointments
A per-lead calendar view, the same UI as the main Calendar, scoped down to just this company's scheduled visits.
Status Logs
The same edit-by-edit audit trail pattern used on Route List records: every status change, who made it and when, on this lead specifically.
Pre-Win Contract & Margin Scoping
Every lead captures the fields a staffing contract actually needs: the workforce mix percentages a client is asking for, and the PTO billing terms that will apply once the deal converts. That scoping travels with the lead, so nothing gets re-negotiated from scratch once it reaches Credit Check.
General Labor %, Over Time %, Clerical % and Rollover % are captured as real fields on the lead record, alongside Required Number Of Associates, Shift and Office Servicing. Sick Days, Holidays and Vacation each carry a separate Billed figure too, so the PTO terms a client is sold on are the same terms that show up on their invoice later.
Daily Route Auditing & Activity Logging
A field-sales rep doesn't get a new record for every stop. Route List holds one record per rep per date, and stops get added to it as a dynamically-editable "Pipeline" list, each one tracked independently for status, whether it was visited, a phone number and a visit time.
A rep's Route List record can carry multiple stops added and edited over the course of a day. Every change to every stop, who added it, who updated it and when, is captured in a timestamped Status Log on that same record.
Users Tracking gives a live map view of where reps are and what appointments they have, alongside the Route List record itself.
Audit trail is per-stop, not just per-record.
Multi-Route Consolidation & Edit Logging
A rep can have several stops mapped against a single date without that ever becoming several records: one Route List record per rep per date holds every stop, added, removed and re-added over the course of the day, each edit attributed to whoever made it. Full detail on how a field-sales territory reads this record is covered on that industry page.
| Time | Who | Event | Detail |
|---|---|---|---|
| 4:53:45 PM | Tushar Kothari | Route List: Created | Lead: Alondras Warehouse, Closet Warehouse |
| 4:54:14 PM | Tushar Kothari | Lead: Removed | Lead: Alondras Warehouse |
| 4:54:26 PM | Tushar Kothari | Lead: Updated | Lead: Alondras Warehouse (re-added) |
| 4:55:43 PM | Kevin Davis | Lead: Visited | Lead: Closet Warehouse. Note: "meet with Jenny" |
| 6:20:03 PM | Tushar Kothari | Lead: Updated | Lead: Western Square (third stop added) |
The admin (Tushar Kothari) creates and edits the route's stops. The rep himself (Kevin Davis) marks his own visit, with his own note. Both actions land in the same log, attributed to the person who actually did them, not merged into one generic "updated" entry.
The resulting Route Details tab shows all three stops with Pipeline Status, Visited Yes/No, a phone number, and, for the visited stop, an exact visit time plus a "Visited Photo" link, a photo-plus-timestamp pattern for verifying a sales-rep visit actually happened.
In-App Calling & Messaging, Carrier-Agnostic
Every prospect and client call is logged with duration and a playable recording, directly on that person's record, in both directions. Hirebase ships the calling, logging, recording and playback experience in-product; the telephony provider underneath is a configurable layer, connected to whatever carrier your region or organization prefers.
Call Out logs an admin-placed call, with notes and a recorded playback, into that contact's call history.
Call In logs a call received from the contact, attributed, timestamped and recorded the same way.
Recorded Playback — each call-log entry carries its own duration and an embedded, playable recording, so a manager can review what was actually said without asking the rep for a recap.
Per-Contact Message Thread — a dedicated thread per worker or contact keeps the written conversation in one place, separate from the call log but attached to the same underlying record.
Because CRM and ATS share the same record (see Unified CRM and ATS Mode Synchronization above), a call logged against a lead or a worker follows that record wherever it goes next. The same framework backs the employee-facing communication log covered on Safety & Incident Management.
Integrated Calendar & Real-Time Roster Map
Route List and the Leads pipeline are the core of the day-to-day work, but two more CRM-mode nav items back them: a standard scheduling view, and the live map that shows those schedules playing out in real time.
A standard month, week, day and agenda view with a location filter. Every lead has its own Appointments tab that reuses this exact calendar UI, scoped to just that company, so a rep's day and a single client's appointment history are the same underlying schedule viewed at two different levels.
A live map with a four-state legend: Appointment Open, Appointment Completed, Appointment Rejected, and User Last Location. It is the same real-time rep-location tracking used on the operations side, applied here to sales appointments specifically rather than employee attendance.
Route List and Pipeline activity also feed two Report-tab views built specifically for field sales: a Mileage Report (log in/out time, routes visited, pipelines, done appointments, miles) and a Sales Performance Report (total, new and completed pipelines, conversion rate, called-in/called-out counts, and routes visited versus not visited) per rep.
The same record,
from lead to placement.
We will map Hirebase to your compliance framework,
your ERP and your region.