Keep Podium. Change what it plugs into.
Your number, your message history and the after-hours texting that books half your work all stay exactly where they are. Fieldproxy connects to Podium and becomes the field service system underneath it: leads land as jobs, dispatch updates go back out, and the review request fires when the technician closes.
If you run Podium with ServiceTitan
ServiceTitan notified shared customers in August 2026 that the Podium integration is being switched off, with roughly four weeks of notice. Around a thousand contractors are affected. Podium keeps working. The wiring between the two does not.
What you actually lose, and the four ways outText comes in at 9pm → customer created → job dispatched → review requested
The loop most contractors bought Podium for, closed end to end
Conversation starts
Webchat, a missed call text back, or an after-hours message. The customer replies to a number they already know.
Customer created
Fieldproxy receives the Podium webhook, checks the contact against records you already hold, and creates the customer or lead without duplicating anyone.
Job dispatched
It becomes a real job on the board, assigned by your rules, in the technician's mobile app with the history attached.
Customer kept in the loop
On-my-way texts, reminders and the post-job review request go back out through Podium, triggered by what actually happened in the field.
What runs today, and what we build with you
We would rather you knew the difference before you signed than after
Running in production now
- Podium OAuth connection with token refresh, so the link does not quietly expire
- Podium webhooks received and acted on the moment a conversation starts
- New contacts looked up against the Podium contacts API and enriched
- Customers and leads created in Fieldproxy, deduplicated against your existing records
- The Podium contact id stored on the Fieldproxy record so the two systems stay linked
- Podium attributes mapped onto your own fields, whatever you happen to call them
Configured to your process at onboarding
- Outbound messages through Podium on job events: on-my-way, confirmations, reminders
- Review request fired when the technician closes the job, on your timing and wording
- Which conversations create a job automatically and which wait for a human to look
- How Podium conversations appear on the customer record your office actually opens
- Lead source and attribution reporting, so you can tell what Podium is really returning
Fieldproxy is configured per company rather than shipped as one fixed product, so this half is built to your process during onboarding instead of being a switch you either get or do not.
Why contractors keep Podium and move the rest
The number is the asset
Your customers have that number saved. Your trucks and yard signs carry it. Changing the field service system behind it costs you nothing your customers can see. Changing the number does.
After hours is where the work is
For a lot of shops, a large share of new work orders start as a text nobody was awake for. That is the flow to protect first, before anything else in a migration.
A connection you do not own can be cut
August 2026 was the reminder. When your messaging depends on two vendors staying friendly, you are exposed to a decision neither you nor your customers get a vote on.
Questions we get asked
Does Fieldproxy integrate with Podium?
Yes. Fieldproxy connects to Podium through Podium's OAuth API and webhooks. New Podium contacts and conversations, including webchat and after-hours texts, create matching customers and leads in Fieldproxy automatically, deduplicated against records you already hold. The Podium contact id is stored on the Fieldproxy record, so the two systems stay linked instead of drifting apart. This runs in production today for Fieldproxy customers.
The ServiceTitan Podium integration is ending. Can I keep Podium?
Yes. Podium is not going anywhere and neither is your number, your message history or your after-hours texting. What ended is the connection between Podium and ServiceTitan. If Podium is booking your jobs, the cheaper change is usually the field service system underneath it, not the messaging tool your customers already reply to.
What gets synced between Podium and Fieldproxy?
Inbound: new Podium contacts and conversations become customers, leads and jobs in Fieldproxy, with the Podium contact attributes you care about mapped onto your own fields. Outbound: job events in Fieldproxy trigger the messages that go back through Podium, such as on-my-way texts, appointment reminders, confirmations and a review request when the technician closes the job. The outbound half is configured to your process during onboarding rather than shipped as a fixed template.
Do I have to replace Podium to use Fieldproxy?
No. Plenty of Fieldproxy customers keep Podium as their phone and messaging layer. Fieldproxy does also ship its own AI text agent, so if you later decide Podium is expensive for what you use it for, you can consolidate. That is a decision you make afterwards, not a condition of switching.
I am under contract with my current field service software until next year. Is it too early to move?
No. Because Fieldproxy is configured per company rather than sold as a fixed product, it can run alongside your existing system and take over the parts that just broke, which is usually the messaging, the customer sync and the reporting. You move the rest at renewal instead of paying two full stacks or waiting nine months with a broken workflow.