Skip to content

Service Request Intake · Field Services

Every web lead sorted, and emergencies called back first

Website and ad leads are sorted by job type and urgency, checked for service area and spam, and sent to your ServiceTitan booking queue. Emergencies hit Slack at once.

Coming soon — waiting for ServiceTitan approval $99 one-time · never renewsIncluded in Enterprise

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

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

Sound familiar?

The job, before and after this agent.

What it feels like today

  • “A no-heat call from last night is still sitting in the web lead queue.”
  • “CSRs read long messages just to work out what the customer needs.”
  • “Spam form fills clutter the booking queue.”

What you get with the agent

  • Job type picked from your own list of services; urgency rated emergency, urgent or routine.
  • Service area checked and spam dropped before it reaches your CSRs.
  • A two-line summary and call-back tip on every real request in ServiceTitan's booking queue.
  • Emergencies like a gas smell, flooding or no heat in freezing weather posted to your dispatch channel in Slack for an immediate call-back.

Before

7am: the furnace is out, it's 36 degrees, there's a newborn at home. The lead waits behind a pile of spam until a CSR gets to it at 9.

After

The lead is flagged emergency, dispatch sees it in Slack with a call-back tip, and it's already in ServiceTitan's queue with a clean summary.

How it works

The whole workflow, step by step.

Receives each new service request from your website, landing page or ad lead forms through a webhook. AI picks the job type from your services, rates urgency (emergency, urgent or routine), checks your service area, drops spam and writes a two-line summary with a call-back tip. Every real request goes to ServiceTitan's booking queue for your CSRs to confirm and schedule, and emergencies such as a gas smell, flooding or no heat in freezing weather are also posted to your dispatch channel in Slack for an immediate call-back. It doesn't pick a technician or time slot, and it doesn't contact the customer.

  1. TriggerNew service request
  2. AI stepClassify the request
  3. LogicSpam, emergency or normal?
    • Spam:Spam dropped
    • Emergency:Alert the team in Slack
    • Normal:Add it to the ServiceTitan booking queue
  4. OutputSpam dropped
  5. App callAlert the team in Slack
  6. App callAdd it to the ServiceTitan booking queue
  7. OutputEmergency queued
  8. App callAdd it to the ServiceTitan booking queue
  9. OutputQueued

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, emergency or normal?Spam is dropped; emergencies are posted to Slack for an immediate call-back and still go to the booking queue; everything else goes straight to the booking queue.
  4. Step 4Spam droppedSpam stays in the run history only; nothing is sent to ServiceTitan.
  5. Step 5Alert the team in SlackPosts the emergency, the customer's phone and address and the CSR tip to your dispatch channel so someone calls back now.
  6. Step 6Add it to the ServiceTitan booking queueSends the emergency to ServiceTitan's booking queue, marked EMERGENCY, for your CSRs to book.
  7. Step 7Emergency queuedThe run history keeps the request, the classification and the ServiceTitan booking ID.
  8. Step 8Add it to the ServiceTitan booking queueSends the request to ServiceTitan's booking queue with the job type, urgency and summary, for your CSRs to confirm and schedule.
  9. Step 9QueuedThe run history keeps the request, the classification and the ServiceTitan booking ID.

Example run

What goes in, and what comes out.

Example with fictional data

Comes in

Fictional lead: furnace stopped last night, 36 degrees, newborn at home, 15-year-old unit, home all day, from a local services ad.

The agent produces

Heating, emergency, inside your service area. A two-line summary with a call-back tip, sent to the booking queue and posted to your dispatch channel.

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).
  • ServiceTitan (with the app connected and a booking provider set up by your admin) and Slack.
  • 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 ServiceTitan. Connect ServiceTitan with the tenant ID, client ID/secret and app key from Settings → Integrations → API Application Access in ServiceTitan.
  3. Connect Slack. Connect the Slack workspace your dispatchers and CSRs use.
  4. List your services and emergencies. Open “Classify the request” and replace the placeholder with your services, service area and emergencies.
  5. Pick the emergency channel. Open “Alert the team in Slack” and pick your account and channel. Invite the app to private channels first (/invite @Fluxo Flow).
  6. Set the ServiceTitan booking queue. Open both “Add it to the ServiceTitan booking queue” steps, pick your ServiceTitan connection and enter your booking provider ID.
  7. Test it with Dry Run. Press Dry Run: the agent runs on sample data with no messages sent and nothing written to your apps.
  8. 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

  • HVAC, plumbing and electrical shops on ServiceTitan
  • CSR teams handling web and ad leads
  • Service managers who own after-hours response

What it doesn't do

  • It doesn't create jobs or pick a technician or time slot: CSRs confirm each request in ServiceTitan's booking queue.
  • It doesn't call or text the customer back.
  • ServiceTitan only for now: Jobber and Housecall Pro versions aren't available yet.
  • Coming soon until ServiceTitan is approved.

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 ServiceTitan 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.

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

FAQ

Questions about Service Request Intake.

Which apps does it need?

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

Does it book the job?

No. CSRs confirm each request in ServiceTitan's booking queue and pick the technician and time slot. It doesn't call or text the customer.

What if it misjudges urgency?

You define the services and emergencies it looks for, and you can Dry Run it on sample leads first. Every real request still lands in the queue for a CSR.

Setup and cost?

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

Do you have a Jobber or Housecall Pro version?

Not yet. This version sends to ServiceTitan.

Is this a subscription?

No. Service Request Intake 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 is almost ready.

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