Requests — The Lead Record | FieldCamp

The FieldCamp Requests record captures incoming service inquiries and leads. See its fields, sales pipeline stages, and how a request converts to work.

A Request is the front door of your field service business. It captures an incoming service inquiry — a call, a website booking, a referral, a walk-in — before it becomes committed work.

Each request belongs to one customer and holds what you need to qualify the lead: the service address, how and when the customer wants to be reached, what they are asking for, and an estimated value.

Every new FieldCamp account ships with the Requests record already enabled, connected to your customers, and running a default sales pipeline, so a new inquiry can be inspected, quoted, and won without any setup.

When the lead is ready to become real work, a request converts in one move into an estimate, a job, or an invoice — carrying its details across so nothing is re-keyed.

From there, the record bends to your business: add your own fields, redefine the stages, and arrange the request page to match how you actually intake work.

What a Request captures

The Request page shows a focused, lead-oriented set of fields. They group into a few natural categories — the customer and where the work is, how and when to reach them, what they want, and how you are working the lead.

The table below lists the fields that appear on a request out of the box.

Field	What it is
Client	The customer the inquiry is for. Required.
Request number	The lead's identifier.
Source	Where the inquiry came from — manual entry, online booking, import, or migration.
Stage	Where the request sits in the sales pipeline.
Service address	Where the work would be done.
Contact phone	The number to reach the customer on.
Preferred contact method	How the customer wants to be reached — phone, email, text, or any.
Availability date 1	The customer's best day for an assessment.
Availability date 2	Another day that works for them.
Start date	When the work could begin.
Start time	The start time for the work.
End date	When the work could end.
End time	The end time for the work.
Any time	Marks the request as not tied to a specific time of day.
Schedule later	Marks the request to be scheduled at a future point.
Assigned to	The team member working the lead.
Requirements	What the customer is asking for.
Internal notes	Notes for your team that stay internal.
Tags	Labels for grouping and filtering requests.
Estimated value	The expected value of the work, shown at a glance.

The fields above are the ones the Request page shows.

FieldCamp also keeps a few details behind the scenes for a request — such as the line items used to estimate its value, the customer name and email copied onto the record, and the bill-to customer when someone else pays — that support quoting and conversion without appearing as editable fields on the page.

The Request pipeline

Every Request moves through a default sales pipeline, from a brand-new inquiry through to a won or lost outcome. Some moves are manual actions a salesperson takes; the won outcomes happen when the request is converted into real work.

The flow below shows the default stages and the named actions that move a request between them.

The stages read as the life of a lead:

New Request

Every inquiry starts here. A new request must name a customer before it can move forward. Requests can be created by hand, captured through online booking, or brought in from an import.

Unscheduled and Overdue

A request waiting for a time to be set sits in Unscheduled. If a request you meant to follow up on slips past its date, it shows as Overdue so it does not get lost.

Inspection Scheduled and Inspection Complete

When the work needs a site visit before you can quote, the request moves to Inspection Scheduled, then to Inspection Complete once the assessment is done.

Quote Created and Quote Sent

Creating a quote moves the request to Quote Created. Sending that quote to the customer moves it to Quote Sent, and the pipeline waits on the customer's answer.

Converted

When the customer says yes, converting the request into real work moves it to Converted — the won outcome, and a final stage.

Lost, Cancelled, and Duplicate

A request can end as Lost — No Response or Lost — Rejected when the quote does not land, Cancelled when the customer drops it, or Duplicate when it repeats another.

Each is final, and a lost or cancelled request can be reopened back to New Request if the customer comes back.

Every move between stages is recorded, so you can always see who advanced a lead and when.

Turning a Request into work

The point of a request is to become committed work. From the request page, one action turns the lead into the next record and carries its details across.

A request can be quoted into an Estimate, turned straight into a Job, or billed directly as an Invoice — and FieldCamp keeps a link back to the request on each, so you always know which lead the work came from.

Read the conversions outward from the request:

Convert to Estimate builds a quote from the request and moves the request to Quote Created. When that estimate is sent, the request advances to Quote Sent on its own.
Convert to Job turns the lead straight into a scheduled one-off job and moves the request to Converted — the path for work that needs no formal quote.
Convert to Invoice bills the request directly and moves it to Converted — useful for simple, agreed work.

An estimate created from a request can itself go on to become a job or an invoice, so a lead that starts as a quote still flows all the way through to paid work.

Conversion copies the customer, the service address, and the line items forward, so the estimate, job, or invoice starts already filled in. See Estimates & Invoices and Jobs for what each record does next.

On the Request page

This page comes with an out-of-the-box layout, built from building blocks. If you want to customize the blocks — reorder, add, hide, or group the sections below — you can. See Record layouts & building blocks.

The Request page is a single Details tab — a wide main column for working the lead and a sidebar for the at-a-glance facts. It reads top to bottom as the story of the inquiry.

The main column carries:

Header — the customer name, a stage pill, and the request's actions: Convert to Estimate, Convert to Job, Convert to Invoice, Duplicate, Call, SMS, and Delete.
At a glance — the key numbers: estimated value, current stage, days open, and urgency.
AI summary — a written summary of the request.
Your availability — the customer's best day and an alternate day for an assessment.
Scheduling — start and end, any-time, and schedule-later options.
Requirements — what the customer is asking for.
Internal notes — your team's private notes on the lead.
Attachments — files added to the request.
Line items — the priced services and products used to estimate the request's value.

The sidebar carries a Details group (source, customer, urgency, assigned team member, and preferred contact method), a Contact info group with the contact phone, the service Address, and a Custom properties section for any fields you add.

Make it your own

The Request record is the starting point, not the limit. Each part of the record can be tailored without disturbing the conversions and connections underneath.

Custom stages

Rename, reorder, add, or remove the pipeline stages so the lead flow matches how your team actually qualifies and wins work — for example a "Site Survey Booked" stage between New Request and Quote Created.

Custom fields

Add your own fields to the Request and they appear in the Custom properties section. A roofing company can capture roof type and square footage; a pest-control company can record the pest and property size right on the lead.

Connected records

A request converts into a job, estimate, or invoice — each one a fully connected record with its own fields, stages, and page.

Built for any size

The same Request record serves a single-truck operator and a multi-location franchise. A one-person plumbing business works leads with the default pipeline as-is: a call comes in, a request is created, and one tap turns it into a scheduled job.

A growing electrical contractor adds a few custom fields and an inspection stage to qualify larger work. A multi-location or franchise operation runs the same intake pipeline at every site, with each location's leads kept under its own structure.

Residential or commercial, the record is the same set of building blocks — ready on day one, and yours to tailor.

Customers

The customer a request is for. One customer can have many requests.

Estimates & Invoices

A request can be quoted into an estimate or billed directly as an invoice.

Jobs

A request can be turned straight into a scheduled job.

Stages & workflows

How the request pipeline is defined, and how to reshape it for your process.