Fieldd

Despite the pricing page’s no-lock-in message, the terms require thirty days’ written cancellation notice and confirmation from support. Subscriptions are billed in advance, and the terms exclude a pro-rata refund for the current period. Branded-app orders have a separate six-month commitment and a stated build time of at least thirty days.

Check payment charges against the applicable regional agreement. The payments page advertises 2.9% for card-not-present transactions, while the USA terms add a fixed $0.30 component. The terms also describe a 0.5% convenience fee for third-party gateways in the US and Australia. Confirm a complete rate schedule before selecting a processor.

If a crew takes a card payment on an external terminal, Fieldd says that reader is not directly integrated with its Worker App. The external provider processes the charge; staff can then record the completed payment against the Fieldd job using the External Payments setup. For a fictional no-charge job, ask who verifies the terminal's payment confirmation, who records it in Fieldd and how the office reconciles the two records before treating the job as paid. Confirm the selected account's roles and payment setup; a Fieldd job entry alone does not show that Fieldd processed the external card transaction.

If Fieldd Route Optimization is enabled, a job already assigned to a route cannot be rescheduled or given a different worker directly; Fieldd says it must be removed from the route first. For a fictional route and job in a walkthrough, ask who removes the stop, changes the booking or assignee, and checks that the route, calendar and job card reflect the new plan. Confirm that Route Optimization is unlocked for the chosen account and how any customer notice is handled; the guide does not prove a notification was sent or a real job changed.

Fieldd separates worker time entry from approval. Its View Timesheets Only permission lets workers clock in and out without editing logs, while Edit Timesheets lets designated foremen or managers enter and change logs. After a worker saves a timesheet to the CRM, administrators can approve or reject it and mark it Paid. With fictional hours in a walkthrough, ask who may correct a submission, who approves it and what separate payroll record would confirm a wage transfer; Fieldd's Paid label alone does not prove money moved.

Fieldd's estimate acceptance choice changes who schedules the follow-up job. Its Help says E-Signature Only lets the customer sign acceptance while administrators schedule the appointment; Self Schedule lets the customer approve and choose a date and time online. If a customer approves by phone, staff can select Approve; Fieldd then shows Est. Won and an Add Job step. In a fictional no-send walkthrough, ask who checks acceptance, who books the work and where the scheduled job appears. A signature or Est. Won status alone does not prove a job was booked.

Fieldd's Zapier guide lists outgoing events for updated bookings and new payments, while its incoming Create Order path can create a Fieldd job and is listed for Scale plans and above. Before relying on an automation, use fictional events to ask which system starts it, whether the selected plan includes incoming actions, and who catches failed or duplicate runs before a job or payment record is trusted. The guide does not establish that a particular Zap is configured, delivered once or reconciled.

Fieldd's customer subscription guide separates how often a package charges from its Service Schedule toggle and booking frequency. The guide says enabling that schedule automatically schedules recurring jobs; in its CRM flow, staff set the billing schedule before Charge & Activate. For a fictional no-charge package, ask which cadence charges, whether service scheduling is enabled, and who verifies the first visit after activation. A recurring charge or a saved package alone does not establish that a customer subscription is active or that visits were booked.

Fieldd's service-area guide separates drawing an online-booking zone from assigning a worker to it. Workers can cover different zones on different days using Dynamic, or more than one zone each day using Fixed; the guide warns that customers cannot book online in a zone with no assigned worker. With a fictional address and date, check both zone coverage and worker assignment before promising online booking. The guide does not establish actual availability for a particular address or day.

Fieldd's worker permissions separate customer online booking from office scheduling: Available for Customer Hub asks whether customers can schedule with a worker online, while Available for bookings in CRM/App asks whether admins can schedule jobs with that worker. The guide also says a bookable worker should be assigned to a City & Zone. In a fictional no-booking check, compare both permissions and zone assignment before assuming a worker appears in both channels. The guide does not establish that a particular worker has an open slot on a chosen day.

Fieldd's Customer Intake Form can collect client questions and uploads stored within the client's account. The guide says clients can see the form in their online or app profile and update their information. In a fictional no-upload review, ask which details need to be collected, who checks client changes before a visit, and which fields can be left out. The guide does not document retention, field-level access, change alerts or tested privacy controls.

For fielddPAY USA disputes, Fieldd's guide says evidence can be uploaded through the Disputes Dashboard and sent to the card issuer; job timelines, photos, checklists, signatures and messages may support a response. The issuing bank decides the outcome. In a fictional no-dispute check, ask whether a questioned charge can be tied to the right job record and who reviews the supporting material before submission. The guide does not guarantee recovery or show a tested dispute.