Skip to content

Service Request Intake for Jobber · Field Services

Every web lead in Jobber, emergencies called back first

Website and ad leads are sorted by job type and urgency, spam-checked and added to Jobber as requests. Full details hit Slack and the customer gets an acknowledgement.

Coming soon — waiting for Jobber approval $99 one-time · never renewsIncluded in Enterprise
Start free Get product updates

Can't be bought yet: waiting for Jobber approval. It opens for purchase on its own once approved.

  • Starts when your form or app sends it something
  • 2 AI steps
  • About 20 min to set up

Sound familiar?

The job, before and after this agent.

What it feels like today

  • “Retyping web form leads into Jobber one at a time.”
  • “An emergency lead looks the same as a gutter quote in the inbox.”
  • “Customers submit a request and hear nothing for hours.”

What you get with the agent

  • Job type from your services, urgency rated, service area checked and spam dropped.
  • Customer found in Jobber by email, phone or name, or added when new, with a request titled with job type, urgency and summary.
  • Full details posted to your dispatch channel in Slack, with emergencies marked call back now.
  • An acknowledgement email that says only what you promise, like your call-back times.

Before

A no-heat lead lands at 7am on Saturday. Nobody sees it until Monday's lead review.

After

The lead is in Jobber as a request, dispatch sees call back now in Slack, and the customer already has your acknowledgement.

How it works

The whole workflow, step by step.

Each service request from your website or ad lead forms is read by AI: job type (from your services), urgency, service area, spam and a summary with a call-back tip. Spam is dropped. Every real request is added to Jobber as a request on the customer's client (found by email, phone or name, or created when they're new), titled with the job type, urgency and summary. Jobber's request takes only a title, so the full details go to your dispatch channel in Slack, with emergencies marked “call back now”, and the customer gets an acknowledgement email that says only what you promise. It doesn't schedule visits or quote prices.

  1. TriggerNew service request
  2. AI stepClassify the request
  3. LogicSpam?
    • Spam:Spam dropped
    • Real request:Write the request title and replies
  4. OutputSpam dropped
  5. AI stepWrite the request title and replies
  6. App callPost the request in Slack
  7. OutputTeam told
  8. App callFind the client in Jobber
  9. LogicExisting client?
    • Existing client:Create the request
    • New client:Add the client
  10. App callCreate the request
  11. OutputRequest created
  12. App callAdd the client
  13. App callCreate the request
  14. OutputClient and request created
  15. LogicEmail address?
    • No email:No acknowledgement
    • Has email:Email the acknowledgement
  16. OutputNo acknowledgement
  17. OutputEmail the acknowledgement
  18. OutputAcknowledged

This is the workflow that opens in your workspace when you set the agent up. Every step can be edited.

  1. Step 1New service requestYour website form, landing page or ad lead form posts each new service request to the workflow's webhook URL.
  2. Step 2Classify the requestAI reads the request, picks the job type from your services, rates the urgency, checks the service area, spots spam and writes a summary for your CSRs.
  3. Step 3Spam?Spam is dropped; every real request goes on.
  4. Step 4Spam droppedSpam stays in the run history only; nothing is sent to Jobber.
  5. Step 5Write the request title and repliesAI writes the Jobber request title (type, urgency and summary), the full details for Slack and the acknowledgement email to the customer.
  6. Step 6Post the request in SlackPosts every real request with the full details to your dispatch channel; emergencies are marked “call back now”.
  7. Step 7Team toldThe run history keeps the Slack message.
  8. Step 8Find the client in JobberSearches your Jobber clients by the customer's email (or phone, or name).
  9. Step 9Existing client?A customer already in Jobber gets the request on their client; a new customer is added first.
  10. Step 10Create the requestCreates a service request on the existing client, titled with the job type, urgency and summary.
  11. Step 11Request createdThe run history keeps the Jobber request link.
  12. Step 12Add the clientAdds the customer to Jobber with their name, email and phone.
  13. Step 13Create the requestCreates a service request on the new client, titled with the job type, urgency and summary.
  14. Step 14Client and request createdThe run history keeps the Jobber client and request links.
  15. Step 15Email address?Customers with an email address get the acknowledgement; the rest are called back from the Slack details.
  16. Step 16No acknowledgementNo email address; the team calls back from the Slack details.
  17. Step 17Email the acknowledgementThanks the customer and says what happens next (your call-back times), with replies going to your office inbox.
  18. Step 18AcknowledgedThe run history keeps the acknowledgement email.

Example run

What goes in, and what comes out.

Example with fictional data

Comes in

Fictional lead: furnace out overnight, 36 degrees, newborn at home, Round Rock TX.

The agent produces

A new Jobber request titled Heating, emergency, with the summary; full details and a call-back tip in Slack; an acknowledgement email with your call-back time.

What you need

Everything it takes to run it.

About 20 minutes from purchase to live. A checklist above the canvas takes you through each step.

Plan

Included in Enterprise; on other paid plans it's $99 once. Agents run live on paid plans, from Basic ($39/mo).

Your AI key

Connect any of 14 AI providers on your own key. Your provider bills usage directly, at cost; we add no markup.

Apps

Checklist

  • A paid plan (agents run live on paid plans).
  • An AI provider key (Settings → AI Providers).
  • Jobber and Slack, connected in Settings → Integrations. Jobber is waiting for vendor approval, so this agent switches on once it's live.
  • Forms that can send new requests to a webhook URL.

Setup, about 20 minutes

  1. Connect your AI provider. The AI steps run on your own key (OpenAI, Anthropic, Google and more). Add one in Settings → AI Providers.
  2. Connect Jobber. Connect Jobber (Settings → Integrations → Jobber).
  3. Connect Slack. Connect the Slack workspace your dispatchers and CSRs use (Settings → Integrations → Slack).
  4. List your services and emergencies. Open “Classify the request” and replace the placeholder with your services, service area and emergencies.
  5. Add your business details. Open “Write the request title and replies” and replace the placeholder with your business name, call-back times, emergency line and sign-off.
  6. Pick the dispatch channel. Open “Post the request in Slack” and pick your account and channel. Invite the app to private channels first (/invite @Fluxo Flow).
  7. Pick your Jobber account. Pick your Jobber account in “Find the client in Jobber”, both “Create the request” steps and “Add the client”.
  8. Add your office inbox. Open “Email the acknowledgement” and enter the address customers' replies should go to.
  9. Test it with Dry Run. Press Dry Run: the agent runs on sample data with no messages sent and nothing written to your apps.
  10. Switch the trigger on. Open the trigger, switch the webhook on and copy its URL into your website and ad lead forms.

Is it a fit?

Who it's for, and what it won't do.

Built for

  • Home service businesses running Jobber
  • HVAC, plumbing and electrical shops
  • Owners answering leads between jobs

What it doesn't do

  • Jobber's create-request action takes only a title, so the full details go to Slack and the email, not into the request.
  • It doesn't schedule visits, assign technicians or quote prices.
  • It doesn't call or text the customer back.
  • A customer found by name only may match the wrong client: check the Slack details when there's no email or phone.

We list the limits up front so you can decide before you buy.

Price

$99 one-time

Per workspace. It never renews.

Coming soon — waiting for Jobber approval
  • Included at no extra cost on Enterprise.
  • Buying and running it live need a paid plan, from Basic ($39/mo).
  • Dry Run costs nothing: simulated AI and app calls, nothing sent.
  • AI usage is billed by your own provider, at cost. No AI credits to buy from us.
Start free Get product updates

One-time agent purchases aren't covered by the 30-day money-back guarantee. Refund policy

FAQ

Questions about Service Request Intake for Jobber.

Which apps does it need?

Jobber and Slack. A ServiceTitan version is also in the marketplace. The agent's page shows whether each app is ready to connect.

Why aren't all the details inside Jobber?

Jobber's create-request action takes only a title, so the title carries job type, urgency and summary and the full details go to Slack and the customer's email.

Could it match the wrong client?

Matching by email or phone is solid; a name-only match can be wrong, so check the Slack details when there's no email or phone. It doesn't schedule, assign or quote.

Setup and cost?

About 20 minutes once Jobber is connected. A one-time unlock that never renews; live runs need a paid plan and your own AI key.

Does it schedule the job?

No. It creates a request in Jobber for your team to assess, quote or schedule.

Why are the details in Slack and not Jobber?

Jobber's create-request action takes only a title, so the title carries the job type, urgency and summary and the full details go to Slack and the customer's email.

Is this a subscription?

No. Service Request Intake for Jobber is a one-time purchase of $99 per workspace and never renews. The Enterprise plan includes it at no extra cost. Running it live needs a paid plan (from Basic ($39/mo)), and your AI provider bills you directly for usage.

Can I test it before it touches real data?

Yes. Once it's set up in your workspace, Dry Run plays every step on sample data with simulated AI and app calls: nothing is sent and nothing in your apps changes. Switch the trigger on only when you're happy.

Service Request Intake for Jobber is almost ready.

Can't be bought yet: waiting for Jobber approval. It opens for purchase on its own once approved. Create a free account now and you'll find it on your Agents page.

Start free Get product updates