Locksmith Software

A locksmith office may receive a residential lockout, a storefront door problem, a vehicle key request, and a planned rekey inquiry within the same hour. Each caller describes the situation differently, and the first description may be incomplete. The office needs a consistent way to separate what the customer reported from what a locksmith later confirms at the site. It also needs to connect that description to the right customer, service location, requested timing, and staff instructions.

Roll On Call supports that administrative work with customer and job records. Office users can select a service location, enter notes and instructions, choose scheduling details, and make a technician assignment. A job brief can carry selected job information to the assigned technician. Staff can then record job status and completion context as updates are reported.

Good intake preserves uncertainty. “Key turns but door will not open” is more useful than an office employee declaring that a mortise case has failed. “Caller says keys are on the front seat” should remain a customer statement until the technician inspects the vehicle. This distinction helps the assigned professional prepare questions without treating an unverified account as a diagnosis, promise, or authorization.

Dispatchers should use direct contact to confirm technician availability and changing field conditions. Roll On Call provides the record around that process.

Texts to technicians and customers go out from your business number on Team and Pro, which include integrated phone and SMS with one included number. Solo does not include integrated phone or SMS, so a Solo owner works from the job record and calls or texts from their own phone.

For a reported lockout, begin with the callback number and exact service location. Confirm whether the address is a residence, business, vehicle location, gate, or another access point. Record the caller's own description of the locked opening and where the caller will meet the technician. Apartment building name, unit number, parking level, cross street, entrance, gate instructions, and an on-site contact can matter more than a broad street address.

Ask enough practical questions to support a safe handoff. Is a child, vulnerable person, animal, active appliance, medical issue, traffic exposure, severe weather, fire, or suspected break-in involved? Dispatchers should follow the company's safety and emergency escalation policy, including directing a caller to emergency services when appropriate.

Keep authorization separate from access details. The locksmith business decides which identification, ownership, tenancy, management approval, registration, or other evidence is required, who may inspect it, and when the work must stop. Those checks should be directly confirmed under the business's procedures and applicable law.

Before assignment, read back the address, callback number, reported opening, and meeting point. Tell the technician which facts are reported and which instructions came from the office. Avoid promising an arrival time until the dispatcher has directly coordinated with the technician. If conditions change, staff can revise the notes or schedule and communicate the change. See emergency service management for the broader operating approach.

Automotive intake should identify both the vehicle and its physical surroundings. Staff can record the caller-reported year, make, model, body style, and key situation. Useful wording distinguishes keys visible in the cabin from keys reported in a trunk, a key broken in a lock, a key that turns without starting, or a request for another key. The description belongs in notes as the caller's account, not as a confirmed repair scope.

Location details deserve equal care. Record the lot name, garage level, space number, nearest entrance, highway direction, mile marker, or safe meeting point when the caller provides it. Ask whether the vehicle is in moving traffic, on a shoulder, inside a restricted garage, or subject to towing. The business's safety procedure should govern whether and how a technician attends.

Do not promise opening, cutting, duplication, ignition work, or programming from intake alone. Vehicle configuration, condition, security systems, damage, and the evidence presented at the scene may change what is lawful or technically feasible. The business must choose a properly qualified technician, confirm authorization under its procedures, and let that technician determine the service after inspection.

Residential work often begins as a planned request after a move, tenant change, lost key, hardware problem, or security review. Create the job under the customer and select the property where service is requested.

Intake notes can capture the customer's count of exterior doors, cylinders, deadbolts, knobs, sliding doors, mailbox locks, or gates. Record reported symptoms precisely, such as a key sticking, latch not retracting, deadbolt binding when the door is closed, loose trim, or a key broken in the cylinder. For a rekey inquiry, note how many keys the customer requests and whether they have mentioned keyed-alike operation, while leaving the final count and compatibility for on-site confirmation.

Staff may type relevant reported observations into notes. The dispatcher separately confirms whether the assigned technician has the qualifications, tools, and parts the business expects for the appointment.

At a rental, condominium, estate, or recently purchased property, the company's authorization process is still required. Prior customer history is not current permission. Appointment notes should identify who plans to attend and any building access instructions, while direct checks establish whether that person may authorize the work. Use the selected schedule as the office's plan, then handle changes through human communication. Our job management solutions page explains the related job-record workflow.

Commercial requests need location detail beyond the company name. A customer may manage many branches, suites, campuses, or managed properties. Select the service location and record the building, floor, suite, door identifier, entrance, loading area, or gate described by the caller. Include the on-site contact and access hours supplied for that visit, especially when a technician must check in with security or facilities staff.

Describe the request without turning it into a technical conclusion. A caller might report a closer leaking, panic hardware not latching, a lever sagging, an electric strike making noise, or a key no longer operating a suite. Record which side of the opening is affected, whether the door closes and secures, and whether the condition changes during business hours. The technician must inspect code, fire-rating, egress, alignment, power, and hardware conditions before recommending work.

Master-key, restricted-key, safe, and access-related requests can carry elevated authorization and documentation requirements. The locksmith company decides which approvals, key-control records, identification, site rules, permits, and qualified personnel are required. For account organization, see customer management.

After-hours work benefits from a short, written call procedure. Capture the caller's name and callback number, exact location, reported lock or key problem, people at the scene, safe meeting point, and any hazard the caller mentions. Ask whether the request concerns a residence, business, vehicle, safe, gate, or common area. Record the requested timing, but do not convert the caller's preference into a promised response.

The person taking the call should apply the company's escalation rules. Reports involving a child in danger, medical concern, fire, active crime, unsafe roadside position, domestic dispute, or forced-entry damage may require emergency services or another response before locksmith work.

Consult the business's on-call plan and contact the relevant technician directly. Confirm that the technician accepts the assignment, has the qualifications the business requires, and understands the location and reported scope. Fatigue, travel conditions, competing calls, and specialist needs are human considerations.

If an answering service creates the record, use a clear handoff procedure for missing details, declined work, cancellations, and calls held for the next business day. Direct voice confirmation is prudent whenever the business needs proof that a person has received the assignment. See field workforce management for related coordination practices.

Assignment is a decision made by the dispatcher, not a software recommendation. The dispatcher reviews the selected service location, requested schedule, reported scope, instructions, and status of other jobs. They then directly confirm the technician's workload, current circumstances, qualifications, equipment, and willingness to take the call according to company procedure.

The dashboard and map provide context from recorded jobs and selected service locations. Live technician location is enabled at launch, so the map can show where technicians are, but it does not show traffic conditions, plan a route, or predict actual arrival time, and device-reported location is not guaranteed to be exact. A status entered by a team member is only as current as the last human update. When timing matters, contact the technician rather than inferring availability from a pin or status.

Reassignment should include two conversations: one with the technician and one with any customer whose plan changes. Staff can update scheduling and assignment details after those decisions. Notes can record a gate contact, parking restriction, requested call-ahead, or instruction to check in at reception. They should not contain assumptions about legal access or technical feasibility. The dispatch management overview describes the shared board in more detail.

After a dispatcher has made and confirmed an assignment, a job brief can send selected job details to the technician's mobile number. A useful brief identifies the customer, selected service location, schedule, callback or site contact, reported request, and selected instructions. Keep the wording factual. “Caller reports broken key in rear door cylinder” is preferable to an office diagnosis or a promise of a specific repair.

Review the destination and content before sending. A selected service address may still need a unit, suite, garage level, entrance, or meeting point. Sensitive information should be handled under the company's privacy and security policy. Do not put alarm codes, safe combinations, key-control information, or personal data into a text merely because a notes field exists. The business decides what may be shared and with whom.

Use direct contact for confirmation when timing, safety, authorization, or a change in plan requires a response. More communication guidance appears in technician communication.

Field findings often differ from the phone description. A reported lock problem may involve door alignment, damaged hardware, an access-control component, or a different opening altogether. The technician should communicate the actual condition through the business's procedure. An authorized team member can then enter relevant notes and select the job status that reflects the team's current understanding.

Do not treat a status as independent evidence of arrival, work performed, quality, or completion. Roll On Call displays what a user recorded. If the office needs confirmation, staff must obtain it directly and update the record.

Notes are most useful when they identify the source and next decision. For example, record that the technician reported a damaged component, that the customer requested a return visit, or that the office needs to confirm parts through its own process. Avoid presenting an unconfirmed possibility as an approved change. If scope, cost, or authorization changes, the business should obtain the required customer approval outside any assumptions created by the record.

When the visit is done, the office or the crew lead turns the job into an invoice. The customer, service address and line items come straight from the job, so nobody retypes them.

Customers can pay the invoice by card through Stripe, and the job shows whether it is sent, paid or overdue. The office sees which finished work is still open without checking a separate spreadsheet.

Roll On Call covers invoicing and collection for the work itself. Bookkeeping, payroll and tax stay in the accounting software the business already uses.

Repeat customers create both useful context and a risk of mistaken assumptions. A property manager may request work at several buildings, while a retailer may have different contacts and access hours at each branch. Staff-created customer records and associated service locations help the office choose the property discussed on the current call. Confirm it verbally, especially when street names, unit numbers, or branch names are similar.

Prior jobs and notes can show what staff previously recorded, including earlier reported issues, selected locations, scheduling context, and completion comments. History can help a dispatcher ask better questions: Is this the same rear entrance? Has the tenant changed? Is the site contact still current?

For every sensitive request, the locksmith company applies its current identity and authorization process. This is particularly important for eviction-related work, employee departures, master-key changes, restricted keys, safes, occupied homes, and vehicles. Applicable law, contracts, site policies, and the company's qualified personnel govern the decision to proceed. The field service CRM page describes how customer and service records support this continuity.

A sound locksmith workflow begins with disciplined intake, continues through a deliberate assignment, and ends with a documented handoff. The office should know who reported the request, where service is requested, what was said about the lock, door, safe, or vehicle, and which person made each day-to-day decision. Clear records support those conversations, but they do not replace them.

Roll On Call's role is limited and practical: staff create customer and job records, select a service location, enter reported context and selected instructions, choose scheduling details, assign a technician, send job briefs, and record job status, completion context, and invoice and payment status. Each entry depends on a person gathering information or making a decision.

Before adopting any dispatch process, define who may accept calls, assess safety, verify identity and authority, approve sensitive work, judge urgency, confirm technician qualifications, change a schedule, communicate with customers, and update completion or payment context. Define a second path for failed contact, changed addresses, no-access visits, disputes, and after-hours escalation. These are business procedures, not platform decisions.

Review records for stale contacts, ambiguous locations, unnecessary sensitive information, and unsupported promises. Maintain separate systems and controls for payments, billing, invoices, and accounting.

With those procedures in place, the shared job record can serve as a working reference from initial call through final office follow-up. Explore the broader industries overview, core solutions, the home page, or the guide to field service management software.