By Lauren Mitchell, field-service CRM operations lead with 9 years of experience managing intake, sales pipelines, booking workflows, and lead attribution
Last reviewed: July 21, 2026
FieldPulse can capture prospective customers through its Booking Portal, Zapier, Engage phone lines, Angi, and manual entry, then organize them through a custom sales pipeline. Before creating a customer or scheduling work, confirm whether the inquiry already produced a lead, customer, or job record.
This independent guide is not operated by or affiliated with FieldPulse.
Do that first. Skip entering the same prospect again because one record is missing from the screen currently open.
What is FieldPulse lead management?
FieldPulse is field service management software for customer records, scheduling, jobs, estimates, invoices, payments, and field operations. Its lead tools help a service business capture inquiries, classify their source, assign next steps, and move prospects through a sales process before or alongside scheduled work.
A single inquiry may create several related records:
- Lead
- Customer
- Job
- Booking request
- Pipeline status
- Lead source
- Estimate
- Follow-up task
Those records are not interchangeable.
A lead represents an opportunity. A customer record holds the person or company history. A job represents operational work. A Booking Portal submission may create or schedule activity depending on the company’s setup.
The main risk is duplication. An office employee creates a customer from a phone call, then a web booking arrives under the same email. Another employee later creates a second job because the first one is unscheduled.
Search every layer first.
How the Booking Portal captures prospects
FieldPulse’s Booking Portal can be embedded into a company website. Prospects can select services, request estimates, provide contact information, and choose available appointment times without leaving the site. FieldPulse says booking information is stored in its CRM, while confirmations can be sent to the customer and the business.
The portal can collect:
- Contact details
- Requested service
- Appointment preference
- Additional intake information
- Estimate request details
That does not mean every submission should be treated as confirmed revenue.
A prospect may request a time that still requires internal review. The selected service may not match the actual problem. The address could fall outside the company’s service area.
Check the resulting record before dispatching.
The portal page also describes automatic scheduling and real-time availability. The exact workflow depends on the services, appointment durations, team availability, and rules configured by the business.
Do not promise that every submitted time is final unless the company has tested its actual configuration.
Booking request, customer, or job?
The first troubleshooting question is: What did the intake method create?
Some channels create only a lead. Others may create a customer and job together. A Booking Portal workflow may add activity directly to the schedule, while a manual inquiry may remain in a sales pipeline until someone qualifies it.
Use this record map:
| Record | Primary purpose |
|---|---|
| Lead | Tracks a potential sale or service opportunity |
| Customer | Stores contact details and relationship history |
| Job | Holds scheduled or unscheduled operational work |
| Pipeline status | Shows where the prospect is in the sales process |
| Lead source | Records where the opportunity originated |
A missing item may simply be located in another area.
For example, FieldPulse’s Zapier walkthrough says imported prospects are stored under Company Settings, Customers, and Leads. An employee searching only the main customer list may assume the import failed.
Check Leads first. Skip recreating the prospect as a customer until the imported record has been located.
How the Custom Sales Pipeline works
FieldPulse’s Custom Sales Pipeline can be enabled under Company Settings, Features & Plugins, and Custom Sales Pipeline. Pipeline stages are managed under the Customers settings area, where administrators can add, edit, or delete statuses.
A business might use stages such as:
- New inquiry
- Contact attempted
- Qualified
- Site visit needed
- Estimate sent
- Follow-up
- Won
- Lost
The exact labels belong to the company.
Keep them action-based.
A stage called “Interested” does not tell an employee what to do. A stage called “Estimate follow-up due” is clearer.
FieldPulse lets users open a customer, assign a Pipeline Status, enter Next Steps, and save the customer. The By Pipeline view then sorts customer cards into status columns and displays the next step and the amount of the most recent estimate. Cards can be dragged into another column to change their pipeline status.
The drag action changes data. It is not merely visual organization.
Do not move cards during a sales meeting unless the new stage reflects the actual customer state.
Why a won or lost lead disappears
FieldPulse states that customers marked lost or completed for one week no longer appear on the By Pipeline page. Their pipeline status remains stored on the customer record.
That is a specific source of confusion.
A salesperson closes an opportunity, checks the pipeline later, and assumes the customer was deleted. The card has aged out of that view.
Open the customer record.
Skip creating a replacement because the card is absent from the board. Search by customer name, contact details, or another stored field and inspect the pipeline status on the profile.
The pipeline is a working sales view. It is not the complete customer database.
Next Steps need an owner and date
FieldPulse provides a Next Steps field when assigning a pipeline status.
A useful next step is concrete:
- Call Tuesday after 2 p.m.
- Send revised estimate after equipment pricing arrives.
- Confirm site access with property manager.
- Close if no response by August 3.
“Follow up” is incomplete.
A pipeline can look full while no one knows which prospect needs attention today. The status tells the team where the opportunity stands; the next step tells someone what to do.
Assign ownership in the company’s normal process. Skip relying on a note without an employee responsible for it.
One short line is enough.
How Angi leads enter FieldPulse
FieldPulse’s Angi integration is enabled under Company Settings, Features & Plugins. Setup requires the Angi Service Provider ID and can include a default Job template. FieldPulse says connection can take two to three business days.
Once activated, a new Angi lead creates both a Customer Record and Job Record in FieldPulse.
FieldPulse checks the email address to determine whether the lead already exists as a customer. When no match exists, a new customer is created and assigned to the company’s founding Admin user. The record receives Angi as its Lead Source, an Angi tag, and notes containing the information collected through Angi.
The corresponding job follows one of two paths:
- A selected default template creates the job using that template.
- No selected template creates an unscheduled, unassigned job.
The job also receives an Angi tag. Its workflow can come from the selected template or the default workflow for unassigned and unscheduled jobs.
This automation is convenient. It can also hide work.
Check unscheduled and unassigned jobs first when Angi inquiries exist but do not appear on a technician’s calendar.
Email matching can still produce duplicates
The Angi integration checks email addresses when deciding whether a customer already exists.
That match is useful but not perfect.
A returning customer may submit a spouse’s email, a new business address, or a mistyped address. The system may reasonably create another customer because the emails differ.
Review:
- Customer name
- Service address
- Phone number
- Existing sites
- Existing contacts
- Email address
- Prior job history
Do not merge records solely because the names look alike. Two people can share a name, and a commercial location may have several legitimate contacts.
The correct priority is search broadly, compare the history, then follow the company’s duplicate-record procedure.
Zapier leads appear in a separate area
FieldPulse’s official Zapier example uses a new Google Sheets row as the trigger and Create Lead as the FieldPulse action. The source fields are mapped into FieldPulse lead fields, the action is tested, and the Zap is then activated. Imported leads appear under Company Settings, Customers, and Leads.
A successful test does not guarantee a usable lead.
A mapped first name can be correct while the service address is blank. A combined name may land in the wrong field. A request date may be mistaken for a confirmed appointment.
After testing, open the lead inside FieldPulse and inspect:
- Name
- Contact route
- Address
- Requested service
- Source
- Notes
- Assigned next action
Skip activating a large automation because Zapier displayed Test was Successful! The test proves the action ran, not that the business meaning is correct.
Lead sources need consistent definitions
Lead Source helps a business compare where prospects and jobs originated. FieldPulse can also assign a lead source automatically through an Engage phone number. Administrators select the phone line, enable Automatically Designated Lead Source, choose a configured source, and save the setting.
When a customer profile is saved through Engage, the source associated with the dialed line is added automatically and appears in Engage reporting.
That works only when phone numbers are used consistently.
A number labeled Google Ads should not also be placed on an organic-search landing page, printed postcard, and service vehicle unless the business accepts blended attribution.
Define sources narrowly:
- Google Ads
- Organic search
- Angi
- Referral
- Existing customer
- Direct call
- Website booking
Skip using both “Web,” “Website,” and “Online” unless those labels intentionally mean different channels.
A messy source list produces a precise-looking report with weak information underneath.
Lead source is not the whole customer journey
A prospect may see an advertisement, visit the company website, leave, receive a referral from a neighbor, and later call a tracked phone number.
FieldPulse can record the source attached to the record or phone line. That source is useful operational evidence. It is not necessarily a complete multi-touch marketing history.
State the reporting rule plainly.
For example: “Lead Source represents the channel recorded when the customer profile was created.” That is more defensible than claiming it proves which marketing interaction caused the sale.
FieldPulse’s job-management materials include reporting by Lead Source, which makes consistent entry important for later analysis.
Check source accuracy before reallocating advertising spend.
Why a lead has no scheduled work
A lead can remain unscheduled because it has not been qualified, the intake channel created an unscheduled job, the requested service is unclear, or no employee has taken ownership.
Check:
- Pipeline status
- Next Steps
- Customer assignment
- Existing job records
- Job schedule
- Job template
- Notes from the source channel
- Service area and availability
Do not schedule directly from a vague note such as “AC issue.”
The office may need the equipment type, address, urgency, access conditions, or customer preference before selecting a technician and duration.
The lead record should collect enough information to make the next decision. It does not need to contain every technical detail before the first call.
Converting a prospect without losing attribution
When the prospect becomes active work, preserve the original source and intake details.
The customer record should remain connected to the job, estimate, and later invoice. Notes from Angi, a Booking Portal, or another source may explain what the customer originally requested.
Do not replace the source because the customer later contacted the company through another channel.
A useful conversion review includes:
- Correct customer profile
- Correct service site
- Original Lead Source
- Pipeline status
- Current Next Steps
- Job or estimate created
- Assigned owner
- Contact preferences
Then move the pipeline status deliberately.
“Estimate sent” should follow an actual sent estimate. “Won” should follow the company’s agreed sales event, such as accepted work, not merely a promising phone call.
FieldPulse pricing and support
FieldPulse uses customized, seat-based pricing rather than publishing one universal amount for every configuration. Booking Portal, lead management, Engage, integrations, and other capabilities should be confirmed in the current package and quote.
The FieldPulse website lists customer support at (469) 382-5668, and its Help Center directs users to the published support email or in-product chat.
Before reporting a missing lead, note:
- Intake source
- Customer name
- Email and phone used in the source record
- Approximate submission time
- Lead Source
- Pipeline status
- Whether a customer or job was also created
- Assigned user
- Job template, when relevant
Do not include credentials or unnecessary private customer information.
Frequently asked questions
Does FieldPulse have a sales pipeline?
Yes. Custom pipeline statuses and a column-based pipeline view are supported.
Where do Zapier leads appear?
Under Company Settings, Customers, and Leads.
Why did a closed lead disappear?
Won or lost customers stop appearing on the pipeline page after one week, but the status remains on the customer record.
Does the Booking Portal create customers?
FieldPulse says the portal collects lead details and stores new prospect information in its CRM. The resulting scheduling behavior depends on the configured booking workflow.
What does the Angi integration create?
A Customer Record and Job Record. Without a default template, the job is created unscheduled and unassigned.
Why was a duplicate customer created?
The incoming record may have used a different email or another identifying detail. Compare the address, phone, contacts, and prior history before changing either profile.
Can phone calls receive an automatic Lead Source?
Yes. Engage can assign a configured source based on the phone line the customer called.
What should be checked before converting a lead?
Confirm the existing customer, service site, source, pipeline status, next step, duplicate records, job or estimate, and the employee responsible for follow-up.
