FieldproxyIntegration guide ยท Podium

Podium for the conversation, Fieldproxy for the job, and the review request when it's done

Fieldproxy connects to Podium through Podium's OAuth API and webhooks. New Podium contacts and conversations, including webchat and after-hours texts, become customers and leads in Fieldproxy, checked against the records you already hold so nobody is duplicated, with the Podium contact id kept on the record. From there the lead becomes a job, is dispatched and completed in Fieldproxy, and the job's events (on my way, reminders, confirmation, and a review request when the technician closes the job) go back out through Podium. Your number, your message history and your webchat stay in Podium.

Fieldproxy is AI-native field service software, set up around your workflow and live within a day. It replaces your field service software; Podium can stay your messaging layer. One price per company, unlimited users.

See your Podium conversations become jobs

Tell us how work arrives through Podium today. We connect it to an account shaped like your operation.

Book your demo

60 minute video call ยท Step 1 of 2: your details, then pick a time

Number of employees

If you ran Podium with ServiceTitan

ServiceTitan told shared customers in August 2026 that its Podium integration was being switched off. Podium kept working; the connection between the two did not. What broke, and your options.

What syncs

What runs now, and what is set up with you

Built on Podium's OAuth API, its webhooks and its contacts API. The inbound half runs in production. The outbound half is configured to your process during onboarding, because which texts go out, when and in what words differs from one company to the next. We would rather you knew the difference before you sign.

ObjectDirectionWhenStatus
Podium contactsPodium โ†’ FieldproxyWhen a new contact arrives by webhook, it is looked up through Podium's contacts API and created as a customer, or matched to one you already hold.Running now
Conversations (webchat, texts, after-hours)Podium โ†’ FieldproxyA new conversation creates a lead, with the Podium attributes you care about mapped to your own fields.Running now
Podium contact idStored in FieldproxyKept on the Fieldproxy customer, so the two records stay linked instead of drifting apart.Running now
Lead to jobInside FieldproxyWhich conversations create a job automatically, and which wait for a person to look.Set up per account
On-my-way, reminder and confirmation textsFieldproxy โ†’ PodiumSent through Podium when the matching job event happens in Fieldproxy.Set up per account
Review requestFieldproxy โ†’ PodiumSent through Podium when the technician closes the job, on your timing and wording.Set up per account
Conversations on the customer recordPodium โ†’ FieldproxyHow Podium conversations appear on the customer record your office opens.Set up per account
Lead source and attributionInside FieldproxyReporting on which jobs and revenue started as a Podium conversation.Set up per account

The workflow

Podium reviews and messages after a job, step by step

The loop most contractors bought Podium for, closed end to end. The rules for each step are agreed at setup.

  1. 1

    The conversation starts in Podium

    Customer

    Webchat on your website, a text to your number, or a message after hours. The customer replies to a number they already know.
  2. 2

    The customer and lead are created

    Fieldproxy, from the Podium webhook

    The contact is looked up through Podium's contacts API, checked against the customers you already hold, and created or matched. A lead is created with the details mapped to your fields, and the Podium contact id is stored.
  3. 3

    The lead becomes a job

    Office, or a rule

    Simple requests can become a job straight away; anything that needs a quote or a look waits for a person. Which is which is your rule.
  4. 4

    The job is scheduled and dispatched

    Dispatcher, helped by the Dispatch agent

    The Dispatch agent suggests who should go by skills, location and free time. The dispatcher approves, and changes can be undone. A confirmation goes out through Podium.
  5. 5

    The customer hears when the technician is on the way

    Fieldproxy, sent through Podium

    A reminder before the visit and an on-my-way text, from the same Podium number the customer has been messaging.
  6. 6

    The job is done and closed in the app

    Technician, Android or iOS

    GPS check-in, the checklist for the job type, photos, parts and the customer's signature. The invoice can be paid on the spot with Tap to Pay or later by payment link.
  7. 7

    The review request goes out

    Fieldproxy, sent through Podium

    When the technician closes the job, the review request is sent through Podium, on your timing and wording. Reviews are collected on Podium's side as before.

See a real Podium conversation turn into a real job on your setup.

Get Demo

What stays where

Podium for messaging. Fieldproxy for the field service work.

The number is the asset. Your customers have it saved and your vans carry it. Changing the field service system behind it costs nothing your customers can see; changing the number does.

Stays in PodiumLives in Fieldproxy
Your business number, and your customers' message historyCustomers, sites and service history, linked to the Podium contact
Webchat on your website and the Podium inboxLeads, quotes and jobs, and the rules that turn one into the other
After-hours texting and Podium's own featuresScheduling, dispatch with approval and undo, and the technician app
Review collection on Podium's sideThe job event that triggers the review request, and when it fires
Podium's own products, such as reviews, payments and inbox, if you use themInvoices, payment links, Stripe and Tap to Pay, and the accounting sync

Keeping Podium

Podium stays your messaging layer: the number, the inbox, webchat and reviews. Fieldproxy sends the job events that tell it when to message.

Or Fieldproxy's text agent

Fieldproxy has its own AI text agent that answers inbound texts and emails against your real data, with approval before anything goes out. Some companies use it instead of a separate messaging tool; that is a choice, not a condition.

A connection you own

When your messaging depends on two other vendors staying on good terms, a decision you had no part in can cut it. Here the connection is between your Podium account and your Fieldproxy account.

Worked example

A 9 pm text at a demo plumbing company

Demo data with fictional names. Bayside Plumbing has used Podium for years: the number is on every van and most new work starts as a text.

  • Monday 9:04 pm: Hannah Lee texts Bayside's Podium number: the water heater is leaking.
  • Monday 9:04 pm: Fieldproxy receives the webhook, finds Hannah is a past customer at 22 Shore Lane, and adds a lead to her existing record. No duplicate is created.
  • Tuesday 7:45 am: the office turns the lead into a job. The Dispatch agent suggests technician Luis Ortega for 10 am; the dispatcher approves, and Hannah gets a confirmation through Podium.
  • Tuesday 9:35 am: Luis taps on my way. Hannah gets the text from the same Podium number.
  • Tuesday 10:02 am: Luis checks in by GPS, replaces the valve, records photos and the part, and Hannah signs and pays with Tap to Pay.
  • Tuesday, after close: the review request goes out through Podium at the time Bayside chose. The job shows in the lead source report as a Podium job.

Setup

Connected and live within a day

You approve the Podium connection. The Fieldproxy team does the rest with you.

  1. 1

    A working session on how work arrives

    Which Podium conversations should become leads or jobs, which texts you send today, and when the review request should go out.
  2. 2

    Connect Podium

    Approve the OAuth connection from your Podium account. Webhooks start arriving straight away.
  3. 3

    Map contacts and attributes

    Podium attributes are mapped to your own Fieldproxy fields, and the matching rules for existing customers are checked against your data.
  4. 4

    Set up the outbound messages

    On-my-way, reminders, confirmations and the review request, each tied to a job event, with your timing and wording.
  5. 5

    Test with real conversations, then go live

    Send a few real messages through, run the jobs on a phone, and check what goes back through Podium. Your existing customers and jobs come across with free, assisted migration.

Fit

Who this is for, and when it isn't the right fit

A good fit when

  • A meaningful share of your jobs start as a Podium conversation, especially after hours.
  • You lost the link between Podium and your field service software, or never had a good one.
  • Review requests go out by hand, or go out before the work is really finished.
  • You want to know which jobs Podium actually brings in.

Not the right fit when

  • Podium is a small part of how work arrives. A manual process may be enough.
  • You want to keep your current field service software and only add a Podium sync. Fieldproxy replaces the field service tool rather than sitting on top of one.
  • You need every outbound message working on day one with no setup conversation. The outbound half is configured with you.

See it built around how your team already works.

Get Demo

Straight answers

Podium and field service: questions we get asked

Does Fieldproxy integrate with Podium?
Yes. Fieldproxy connects through Podium's OAuth API (with token refresh, so the link doesn't quietly expire) and webhooks. New Podium contacts and conversations, including webchat and after-hours texts, create customers and leads in Fieldproxy, deduplicated against records you already hold, with the Podium contact id stored on the Fieldproxy record. That part runs in production.
What goes back to Podium?
Job events in Fieldproxy trigger the messages that go out through Podium: on-my-way texts, appointment reminders, confirmations and a review request when the technician closes the job. This half is set up per account during onboarding, on your timing and wording, rather than shipped as a fixed template.
Can the review request go out only after the job is really done?
That is the point of triggering it from Fieldproxy. The request is tied to the technician closing the job, and the job type's checklist decides what has to be done before it can close. The timing and wording are set up per account.
Do I have to replace Podium to use Fieldproxy?
No. Fieldproxy replaces your field service software; Podium can stay your messaging layer. Fieldproxy also has its own AI text agent that answers inbound texts and emails against your real data. Some companies keep Podium, some use the text agent, and that choice doesn't have to be made at the same time as the switch.
The ServiceTitan Podium integration ended. Can I keep Podium?
Yes. Podium itself kept working; what ServiceTitan switched off was the connection between the two. If Podium is how much of your work arrives, changing the field service system underneath it keeps the number and history your customers know. Our ServiceTitan page sets out what broke and the options, including ones that don't involve us.
Will Podium contacts create duplicate customers?
New contacts are checked against the customers you already hold before anything is created, and the Podium contact id is stored on the record, so the same person messaging again lands on the same customer.
Can every new conversation become a job automatically?
You decide. Which conversations create a job straight away, and which create a lead that waits for a person to look, is set up per account.
I'm under contract with my current field service software. What should I do?
Plan the switch for your renewal date, not around it. Fieldproxy replaces the field service tool rather than running on top of it, so the cleanest path is to set up and test Fieldproxy with your Podium account, move your data with free, assisted migration, and go live when the contract ends. Setup itself is live within a day.
Can I see which jobs Podium brought in?
Lead source and attribution reporting is set up per account, so you can see which jobs started as a Podium conversation.
What does Fieldproxy cost if we keep Podium?
Fieldproxy is one price per company with unlimited users. Podium's plan is billed by Podium.

Related

More on messaging, reviews and switching

See every connection on the integrations page, or work with your customers and jobs from Claude, ChatGPT or Copilot through Fieldproxy's MCP server.

Keep Podium. Change what it plugs into.

Show us your Podium setup. We connect it to a Fieldproxy account shaped like your operation and you watch a real conversation become a job.

Get Demo

Live within a day. Free, assisted migration. Unlimited users on one price per company.