Practical FieldWorks guide

A service-business QR code should open a useful next step, not just a homepage.

The code earns its space on a yard sign, vehicle, card, or invoice when it preserves the provider, explains what happens next, and lets the customer begin a real request safely.

Written by Christopher Atoki
Want help with the first setup?Request guided setup

Working method

Design the route before printing the code.

A readable QR image is only the carrier. The destination, provider context, request fields, fallback, and physical placement determine whether the scan becomes a useful opportunity.

  1. 01

    Choose the exact destination

    Use the provider's approved FieldWorks business-card or public-profile request path, not an arbitrary redirect or a private dashboard URL.

  2. 02

    Keep the provider attached

    The customer should know which business will receive the request before sharing job details or photos.

  3. 03

    Ask only for useful request details

    Collect the service, property, timing, and photos needed to respond. Do not turn a quick scan into a long generic intake form.

  4. 04

    Test the physical placement

    Print at the intended size, scan from a realistic distance and angle, and verify the destination on a supported iPhone before ordering a batch.

  5. 05

    Connect the response workflow

    Make sure the business can recognize the new request, ask a question, send a quote, and continue the same customer record after the scan.

Common questions

What makes the code trustworthy?

The customer should see the business identity, destination, request boundary, and next action without guessing what the scan will do.

Where should a service business place the QR code?

Use places where the business already has attention and permission: a business card, estimate, invoice, yard sign, vehicle, or completed-job leave-behind. Avoid placing it where scanning would be unsafe.

Should the code open the App Store?

A provider-specific FieldWorks path can preserve the business context and use the supported App Clip or app handoff. A generic store link loses that request context.

How do we know whether it works?

Test the printed code and record genuine requests that entered through that provider touchpoint. Do not count scans alone as completed opportunities.

Generate the code after the profile and services are ready.

A customer who scans should find an identifiable business and enough real service information to decide whether starting a request makes sense.

Create business account