Landscaping Software

Landscaping offices receive requests that vary by customer, property, season, and type of work. A homeowner may report an overgrown lawn or ask about spring cleanup. A commercial contact may request service at one of several managed properties. A property manager may report fallen branches after a storm or ask about a future planting project. Intake staff need to distinguish what the customer reported from what the business has inspected, approved, or scheduled.

Roll On Call provides records for that handoff. Staff create customer and job records, separately select the requested service location, enter reported scope, and choose relevant notes or instructions. Dispatchers make scheduling, crew assignment, rescheduling, and geographic decisions using their own knowledge and business procedures. Authorized team members may later record status and completion context based on communication from the field. These are records rather than automated findings. The Roll On Call overview describes the broader dispatch workspace.

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.

Residential customers, commercial contacts, and property managers bring different recordkeeping needs. A homeowner may request service at the home where they live, while another customer may coordinate care for a rental property. A commercial contact may speak for one location, and a property manager may report requests for several addresses. Staff create the customer record and enter the contact details supplied to the business. They also decide which person should be contacted under the business's own authorization and communication procedures.

A customer record can hold relationship context, while jobs and separately selected service locations describe individual requests. Staff should keep general contact notes distinct from property-specific access instructions and current job scope. The landscaping business confirms those matters before acting. This record structure is also discussed in the field service CRM overview, which explains how customer context can accompany dispatch records without replacing the company's agreements or decision process.

One customer record may relate to several physical properties. A property manager might request mowing at one address and cleanup at another. A residential customer may call about a primary home and later report work at a rental. Staff can create service-location records separately from the customer and select the intended location when creating a job.

The selection remains a staff action. Staff confirm the address and relationship through company procedures before selecting it. Dispatchers can consider selected locations when making their own geographic and schedule choices, but the map context is not route planning. The multi-location management page provides more context about keeping customer and worksite records distinct.

Customers may report details that affect a visit, including a gate, an entry point, parking instructions, an on-site contact, pets, or an area where work is restricted. Staff can enter these details as notes associated with the relevant record. A dispatcher then chooses which notes or instructions to include for a particular job. Selection matters because a property note may not apply to every visit, and an older instruction may need confirmation before reuse.

Notes reproduce information selected by staff. They do not verify that a gate code still works, parking is permitted, a contact will be present, a pet is secured, or a restricted area is marked. They also do not identify hazards. Critical or sensitive instructions may call for direct confirmation rather than reliance on an earlier record. Staff should update the record when the customer reports changed conditions.

One-off requests can include mowing, yard cleanup, pruning, planting, an irrigation observation, storm debris, seasonal preparation, or a broader project inquiry. Intake staff create a job, select the service location, and record what the customer reported. They can add notes about access, the relevant area, a contact at the property, or timing requested by the caller.

Neutral attribution is useful. For example, a record can state that the customer reported a damaged limb rather than presenting that report as a professional assessment. Qualified people acting under the business's procedures inspect the site, evaluate feasibility and safety, define any proposal, and obtain needed approval. The record can still be used for staff-led scheduling and assignment of an appropriate next visit. Related administrative use cases appear on the solutions overview.

Recurring mowing, edging, cleanup, and bed-maintenance work still requires active decisions by the landscaping business. The company decides what an agreement requires, whether another visit should be created, who may perform it, and when it fits the seasonal workload. Staff can use Roll On Call to create the customer and job records that represent those decisions. They select each service location, choose a schedule, assign a crew, and revise the record when plans change.

Staff monitor the calendar, customer communication, workload, equipment, and conditions through their own processes. If weather or another issue affects a plan, people decide whether and how to reschedule. The customer management section explains related customer-record practices. Contract terms, renewal, frequency, customer notices, and missed-visit follow-up remain business responsibilities.

A customer may ask for mowing in a defined area, cleanup near an entrance, or pruning away from a walkway. Another may ask that a bed, shrub, pet area, or newly planted section not be disturbed. Staff can enter the request in the customer's words and select instructions relevant to the job. This gives the assigned team the reported scope and location context without turning the customer's observation into a technical conclusion.

The landscaping business reviews the reported scope, checks current conditions, determines qualifications and safety requirements, and decides what work is authorized. If staff learn that the request has changed, they can update the job context or create another record as appropriate. The entry remains a record of human communication and decisions, not a specification, estimate, or quality standard.

Planting and enhancement conversations often begin with an incomplete idea. A customer might ask about a new bed, replacement plants, mulch, or changes to a particular area. Staff can record that inquiry, its selected service location, the customer's preferences, and relevant access notes. A job record may then represent a staff-scheduled consultation or other visit, provided the business has decided that step is appropriate.

Those activities remain with the landscaping business and its qualified people. If the business later chooses to perform work, staff may create distinct job records for planned visits and add selected instructions. People determine the sequence, equipment, materials, crew qualifications, and relationship between those visits.

Irrigation information may arrive as a customer report or as communication from a team member. The customer might describe a broken sprinkler head, pooling water, a dry area, or a controller concern. Staff can record the observation, the reported area, and the service location.

The landscaping business decides whether it offers the requested work and who is qualified and authorized to inspect or perform it.

Storms and seasonal changes can produce a concentrated group of requests. Customers may report branches, debris, blocked access, leaf accumulation, or preparation work at residential or commercial properties. Staff can create each job, select its location, preserve the reported scope, and add relevant access or contact notes. The resulting job records let dispatchers review the requests while applying the company's own intake, safety, priority, and customer-communication procedures.

People review seasonal workload and decide which jobs to accept, schedule, assign, defer, or reschedule. Weather monitoring, site assessment, safe access, equipment selection, licensing, and follow-up remain business responsibilities throughout storm and seasonal work.

Dispatchers can review jobs and their selected service locations, including location context shown on the dashboard. They apply their own knowledge of the service area, seasonal workload, customer commitments, travel considerations, and constraints. A person chooses the schedule and crew assignment for each job. If circumstances change, a person also decides whether to move the job, change the crew, contact the customer, or take another action.

They also do not confirm that a crew can reach or complete a job within a particular period. Dispatch remains a human decision informed by sources and procedures outside the platform as needed. The dispatch management overview explains how recorded locations, schedules, and assignments fit into this staff-led process.

After making those checks through company procedures, a dispatcher can record the selected crew assignment.

If availability changes, staff review the situation and update the assignment or schedule manually.

An authorized user can send a job brief containing job context chosen by staff. That context may include the selected service location, reported scope, and notes or instructions such as an access point, gate information, parking direction, property contact, pet note, or restricted area. Staff decide what is relevant and appropriate to include. They should follow company privacy and communication procedures when handling sensitive access details.

The business decides when direct contact or confirmation is necessary, especially for schedule changes, urgent issues, or safety information. The technician communication overview discusses standard briefs as one part of staff-led coordination rather than a substitute for company communication procedures.

Some cleanup, planting, seasonal, or other project work may involve more than one visit. Staff can represent the visits with distinct job records. For each one, a person selects the service location, chooses a schedule, records reported or staff-selected context, and assigns a crew. Notes may refer to related work, but staff decide how the records correspond and which information should be carried into each visit.

Staff create, schedule, assign, and reschedule each record when the business decides to proceed. Agreement administration, design approval, material readiness, site readiness, and follow-up stay outside these dispatch records. The field workforce management page provides further context for scheduling across separate jobs.

Staff can review prior jobs associated with a customer and selected service location. Earlier records may show reported scope, the schedule and crew that staff selected, access notes chosen for a visit, status, or completion context. That history can inform questions during intake. For example, staff might ask whether a previously reported gate issue, pet instruction, parking limitation, or restricted area still applies.

History remains a collection of earlier human entries, not verified current property information. Staff confirm important details through the business's normal communication and site procedures, then update or select notes for the new job.

Authorized team members can record a job status based on information available to the team. They can also enter textual completion context reported through field communication. If the team reports that a planned task was not finished or that another visit may be needed, office staff can preserve that context and decide what action to take. Scheduling or rescheduling remains a staff choice rather than an automatic response to the entry.

Status and completion context are human-recorded administrative information. The landscaping business handles field supervision, review, customer communication, and any follow-up. See the job management overview for more about job records and human-entered updates.

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.

Roll On Call's landscaping use is centered on records and deliberate staff actions. Staff create customer and job records, separately select service locations, preserve reported scope, and choose notes or instructions relevant to a visit. People make schedule, crew assignment, rescheduling, and geographic decisions.

Teams considering adjacent use cases can visit the industries directory, the plumbing dispatch page, or the field service management software guide.