---
title: "ServiceTitan Is Ending Its Podium Integration: What Contractors Need to Know"
url: "https://fieldcamp.ai/blog/servicetitan-podium-integration-ending/"
date: "2026-08-13T09:04:35+00:00"
modified: "2026-09-09T16:40:48+00:00"
type: "Article"
resource: "https://fieldcamp.ai/blog/servicetitan-podium-integration-ending/"
timestamp: "2026-09-09T16:40:48+00:00"
author:
  name: "Jeel Patel"
categories:
  - "Industry News"
word_count: 5495
reading_time: "28 min read"
summary: "Updated 20 August 2026. Originally published 13 August 2026. This is a developing story and we'll keep updating it."
description: "ServiceTitan ends its Podium integration on September 15, 2026. What breaks, your four options, and why Podium now sells a field service platform of its own."
keywords: "servicetitan podium integration, Industry News"
language: "en"
schema_type: "Article"
related_posts:
  - title: "How to Cancel Podium (2026): Notice Period, Contract Terms & What It Costs"
    url: "https://fieldcamp.ai/blog/how-to-cancel-podium/"
---

# ServiceTitan Is Ending Its Podium Integration: What Contractors Need to Know

_Published: August 13, 2026_  
_Author: Jeel Patel_  

![Field service technician reviewing a tablet beside a service van, with ServiceTitan and Podium logos representing their software integration.](https://cms.fieldcamp.ai/wp-content/uploads/2026/08/Feature-Podium-1024x600.png)

**Updated 20 August 2026.** Originally published 13 August 2026. This is a developing story and we’ll keep updating it.

**The date is now firm: the integration ends on 15 September 2026.** ServiceTitan co-founders Ara Mahdessian and Vahe Kuzoyan set it in an email to customers on 12 August. Affected contractors are being offered discounts to move to a certified partner, or told to contact Podium about continuing without an integration.

*Three things have changed since our 17 August update. ServiceTitan has given its first formal on-record statement. Podium’s CEO has made a specific counter-claim about what ServiceTitan asked for in return. And Podium has launched [a field service management product of its own](https://homeservices.podium.com/features/fsm) — dispatch board, technician app, estimates, payments, reporting — which changes what this dispute is about. We’ve reworked the middle of this page accordingly. Correction: the delisting noted in our previous update was documented on 14 August, not 17 August.*

Contractors running ServiceTitan and Podium together received an email on 12 August announcing that the **ServiceTitan Podium integration** is ending. The notice came from ServiceTitan co-founders Ara Mahdessian and Vahe Kuzoyan, and it sets the cutoff at 15 September 2026.

If you’re one of them, you’re in the middle of your busiest season and have just been handed a project nobody planned for. This page covers what actually breaks when **ServiceTitan ends the Podium integration**, what your realistic options are, and how to sequence a switch without losing customer history.

**Disclosure:** FieldCamp is [field service management software](https://fieldcamp.ai/). We compete with ServiceTitan. We think that’s worth knowing before you read our take, and we’ve tried to write the page we’d want to find if we were the ones getting the email.

## What we know so far

Here’s what’s been stated publicly, and by whom. We haven’t independently verified any of it, so we’re attributing it rather than asserting it.

**From ServiceTitan’s email of 12 August:** the integration ends on 15 September 2026. ServiceTitan’s stated reason is that the existing integration no longer meets its **Marketplace standards**. The suggested remedy is switching to a different customer communication provider, with a discount offered for moving to a certified partner. The account that surfaced this publicly was [residential electrification contractor Brad Plunkett, writing on LinkedIn](https://www.linkedin.com/posts/bradleyplunkett_i-just-received-a-email-from-servicetitan-share-7493413510735933441-8BPs/).

![LinkedIn post from contractor Brad Plunkett announcing ServiceTitan is ending the Podium integration with four weeks notice in peak season](https://cms.fieldcamp.ai/wp-content/uploads/2026/08/image.png)**From ServiceTitan**, in a public comment responding to that post: “We tried to bring this partner into our certified program and opted not to move forward with their own certification.” The company said it understands the change is disruptive, said it wasn’t their first choice, and pointed contractors to their customer success managers and to [its App Marketplace update post](https://www.servicetitan.com/blog/app-marketplace-update). Brad Plunkett’s reply to that comment, in full: “Thanks but I don’t buy it. There’s clearly more to the story here.”

![ServiceTitan's public LinkedIn reply stating the Podium integration did not meet App Marketplace certification standards, with the contractor's response below it](https://cms.fieldcamp.ai/wp-content/uploads/2026/08/image-1.png)On 18 August, ServiceTitan gave its first formal on-record statement: “We recently made the decision to sunset our integration with Podium after Podium’s legacy agreement expired and they opted not to move forward with their own certification.” It added that “while many of our partners have become certified, Podium’s legacy integration is not in compliance with our Marketplace standards. We’re supporting every affected customer directly to minimize the impact on their business.” The company declined to comment beyond the statement.

Mahdessian’s LinkedIn post said it more plainly. Podium was under “a legacy partnership that had run its course”; it “had a path to continue partnership through this certification program, and we offered them certification on the same standards as others”; and “Podium opted not to certify. I won’t speculate as to why. But with the legacy partnership ending and no certified partnership going forward, we cannot continue the integration.”

That resolves an ambiguity we flagged in our original version. ServiceTitan’s first public comment was grammatically unclear about which company declined. Its formal statement is not: ServiceTitan says Podium declined.

**From Podium co-founder and CEO Eric Rea**, replying in the comments of the same post: Podium was “equally blindsided by this today,” has been “trying to meet with ST for months with no response from their team,” and has been a ServiceTitan partner for nine years. He put the number of shared customers at approximately 1,000. Notably, he did not dispute ServiceTitan’s right to end the arrangement — “I get that partnerships don’t last forever,” he wrote, “but to put ~1000 shared customers in a bind during one of the busiest times of the year makes zero sense.” At our original publication on 13 August, Podium’s own ServiceTitan listing was still live. As of 14 August 2026 it returns a 404, its replacement directory page returns a 404, and Podium no longer appears in [ServiceTitan’s own list of available integrations](https://help.servicetitan.com/docs/available-servicetitan-integrations). The delisting has now happened on both sides.

![Podium co-founder and CEO Eric Rea replying on LinkedIn that Podium was equally blindsided by ServiceTitan ending the nine-year integration partnership](https://cms.fieldcamp.ai/wp-content/uploads/2026/08/image-2.png)From Eric Rea, in an email to Podium customers on 13 August: “Over the last two years, ServiceTitan started changing the terms of our partnership. They wanted a substantial cut of revenue that ultimately comes out of your pocket, and they wanted us to agree to stop building anything that competed with them.” On the timeline: “About three months ago they became completely non-responsive, despite repeated attempts from our side. After months of silence, their response was a termination notice with 30 days to figure it out.” Rea has since said Podium “found out officially [at] the exact same time, the exact same day, as customers did” — the sourced version of the blindsided claim he first made on LinkedIn.

Rea also drew a distinction that matters more than the headline. Revenue sharing, he said, “wasn’t the hill we were going to die on. The hill we were going to die on is, ‘You can’t innovate.'” He characterised ServiceTitan’s position this way: “We can go copy anything that our partners do, but anything that our partners build that’s remotely close to what we already have, you can’t do.”

One verified fact supports his framing on the money. A Podium spokesperson has confirmed the original arrangement, struck nearly a decade ago, included no referral fee and no revenue sharing. Certification did not adjust an existing commercial deal. It introduced one where none had existed for nine years. The same integration also ran with Housecall Pro and ServiceFusion — Podium was never ServiceTitan-exclusive.

When we first published, those two accounts looked irreconcilable — one said a certification was offered and not taken up, the other said there was no response to repeated requests for a meeting — and we said so. With both companies now on the record at greater length, they reconcile better than they first appeared. They are not describing different events. They are describing the same disagreement from opposite ends, and the disagreement is not really about certification.

It’s worth reading ServiceTitan’s sentence closely, because it carries an ambiguity that matters here: “We tried to bring this partner into our certified program and opted not to move forward with their own certification.” Grammatically, the subject of “opted” could be either company. Read one way, Podium declined to certify. Read the other, ServiceTitan declined to proceed. The sentence does not settle which — and that is the exact fact a contractor being asked to replace their phone system would want settled. Both companies have since gone on the record at greater length — ServiceTitan in its 18 August statement, Rea in a customer email and an interview — and that ambiguity is now settled: ServiceTitan says Podium declined to certify. What neither company has described is the negotiation itself.

## Why this is really happening

Certification is the mechanism. Competition is the reason. Both companies have now said so in their own words, without either quite saying it.

Start with what Podium sells today. Its [field service management page](https://homeservices.podium.com/features/fsm) is titled “AI Operating System and Field Service Management Software for Home Services.” It describes a visual dispatch board with real-time technician availability, a technician mobile app, digital estimates built from a flat-rate price book with e-signature, tap-to-pay and text-to-pay, automatic maintenance-agreement renewals, customer profiles with equipment and service history, QuickBooks Online sync, and revenue and job reporting — all fronted by “Larry,” the AI employee Podium markets across its product. Its own FAQ puts the positioning beyond doubt. Asked “Does Podium’s FSM replace my current scheduling software?”, the answer is: “Yes. Podium’s FSM replaces your scheduling software, dispatch tools, and any disconnected apps you’re stitching together. Everything runs in one place.”

The page never mentions ServiceTitan. It doesn’t need to. That feature list is a field service management system, and field service management systems are what ServiceTitan sells.

Now read ServiceTitan’s own policy. The same [App Marketplace update post](https://www.servicetitan.com/blog/app-marketplace-update) it directed contractors to — published 24 June 2026, seven weeks before the Podium notice — carries a section headed “Competitive Offerings.” It sits under “ServiceTitan operating approach,” alongside “Fairness,” among the commitments ServiceTitan sets out for itself rather than in the list of requirements it imposes on partners. It reads in full:

> While some software companies explicitly forbid competitive products from their marketplace, we offer several Marketplace partners that provide capabilities that compete with parts of ServiceTitan’s capabilities. We believe such offerings add value for our customers, and welcome those partners because of that value, as long as they’re not leveraging the partnership and our support to gradually displace additional parts of ServiceTitan.

That is not a stray sentence. Seven weeks before sending the notice, in the document it then told affected contractors to go and read, ServiceTitan gave competitive partners a named policy section of their own. And the final clause is the story in one line. A reputation and messaging tool competes with *part* of ServiceTitan. A dispatch board, a technician app, a price book, estimates, payments and job reporting is *additional parts*. ServiceTitan’s Q1 FY27 results, reported 4 June 2026, showed revenue of $268.8M (up 25%) and non-GAAP operating margin more than doubling year over year to 15.2% — figures that cut against any reading of this as a company protecting a stagnant product.

Set that against Rea’s account and the two positions align almost exactly. ServiceTitan wanted Podium to “stop building anything that competed with them,” by Rea’s description. ServiceTitan’s published policy says partners may compete with parts of the platform but may not use the partnership to displace more of it. Those are the same requirement, described once by the party imposing it and once by the party refusing it. Rea says refusing it was the point. Eight days after publicly calling the shutdown a blindside, Rea posted on X, on 21 August 2026: “There is no competitor to ServiceTitan until the demo I saw from you guys today.” He has also said Podium crossed $100M in AI-agent ARR within 24 months, as of a 21 January 2026 post on his own account.

Neither company has said “this ended because Podium built an FSM,” and we are not asserting they did. We cannot see the negotiation. But if you are deciding what to do in the next few weeks, the simple reading serves you better than the complicated one: a platform ended an integration with a partner that had become a competitor, and the certification programme the partner had not joined was the mechanism for doing it. Everything both companies have said in public is consistent with that.

Two practical consequences follow, and they are the reason this section exists rather than sitting in a footnote.

This was not a paperwork problem that more goodwill would have fixed, so waiting for the two companies to patch it up before 15 September is a poor plan. Rea has said in a Facebook post that he is “still hopeful we can agree on a much more reasonable transition period,” and he may get one. Do not build your schedule on it.

And if you keep Podium, you are keeping a vendor that sells a replacement for your FSM and has been pitching it to contractors in your exact position. That is not a reason to avoid them — competing is legitimate, and their product may well suit you. It is a reason to know it before your renewal conversation rather than during it.

## What ServiceTitan’s Marketplace certification actually requires

The post ServiceTitan pointed contractors to is [“ServiceTitan’s App Marketplace — An Update,” published 24 June 2026](https://www.servicetitan.com/blog/app-marketplace-update). It’s worth reading the source rather than the summary, because most of it is reasonable and one part is not what contractors assume. It sets out the bar an app must clear, in ServiceTitan’s own words:

- **Security** — “Apps must be secure. They cannot unintentionally or nefariously siphon off sensitive data including (but not limited to): end-customer data, payment details, employee records, business financials, etc.”
- **Performance** — “Apps must be performant. They cannot generate excessive or unnecessary load on our infrastructure.”
- **Predictability** — “An app’s scope must be clear and reasonably defined.”
- **Data transparency** — “If partners are accessing data through the ServiceTitan API, they must also write back data to ServiceTitan.”
- **Revenue share** — “Partners must share in these costs through reasonable economic arrangements that are comparable to other industries.”

The first four are ordinary platform hygiene. Any serious software company would want them, and a marketplace that certified nothing would eventually fail the contractors who trust it.

The fifth is a commercial term, not a safety one — and it sits in the same list as the other four. That’s the part worth understanding, because it means “did not meet Marketplace standards” can describe a technical outcome or a commercial one, and from outside the negotiation there is no way for a contractor to tell which.

The commercial side is spelled out further in ServiceTitan’s [App Marketplace Program Guide](https://www.servicetitan.com/legal/app-marketplace-program-guide), the legal terms rather than the blog post. There, revenue share is described as a percentage of partner net revenue derived from the application, or a specified minimum fee, whichever is greater — and partners must maintain current payment status to preserve program benefits and certified status. **Certified status is contingent on paying.**

Two things are worth noting about the timing. That update post is dated 24 June 2026, roughly seven weeks before the Podium notice, so the framework isn’t new. And it makes no mention of Podium, or of any partner being removed. It says ServiceTitan has “already certified 14 partners across accounting, payroll, point-of-sale, e-commerce, CSR, and more.” A contractor sent there for an explanation of why their phone system is being disconnected will not find one.

We’re not claiming to know which applies here. We’re pointing out that the phrase can’t tell you — and that the distinction matters a great deal if you’re the one being asked to replace your phone system before 15 September.

### The AI clause nobody is citing

There is a third possibility, and it is in writing.

ServiceTitan’s [API Terms of Use](https://www.servicetitan.com/legal/api-terms) — last updated 15 April 2026, four months before the Podium email — place specific restrictions on partners whose applications use AI. Among the prohibited uses, a partner may not:

> permit any bots, robotic process automation (RPA), AI (whether agentic or otherwise), or similar automated technology (“AI System”) to independently determine which API endpoints to access, what Content to request or modify, or what actions to take through the APIs.

The terms go further:

> Any API calls made by or through an AI System must be limited to predefined operations within your Application’s Certified Scope and must not allow the AI System to autonomously expand, modify, or deviate from such predefined operations.

Disclosure is mandatory, and approval is discretionary:

> You must disclose to ServiceTitan whether your Application incorporates or relies upon any AI System at the time of registration and promptly upon any subsequent integration of an AI System.

> ServiceTitan reserves the right to impose additional conditions, restrictions, or Certification Requirements on any Application that incorporates an AI System, including requiring human authorization for write operations, if ServiceTitan elects to permit such use of an AI System at all.

Using an AI System with the APIs without that disclosure and approval “shall constitute a material breach of these Terms.” Separately, partners may not “use the APIs to collect data for creating training datasets for AI purposes.”

Read that one phrase again — “if ServiceTitan elects to permit such use of an AI System at all.” An agentic product’s core behaviour is deciding what to do next. A clause requiring every API call to stay inside predefined operations, with write operations potentially gated behind human authorization, is a hard ceiling on what an AI-first partner can build on top of ServiceTitan.

We are not asserting this is why the Podium integration ended. Neither company has said so. We are pointing out that “did not meet Marketplace standards” carries at least four possible meanings — a security or performance failure, a commercial disagreement over revenue share, an AI-scope restriction, or the competitive-displacement limit ServiceTitan set out in the same June post — and the announcement itself tells a contractor none of them. On the evidence now public, the fourth is the one both companies’ accounts point toward.

The bar is also demonstrably clearable by a company in Podium’s category. Hatch, an AI-driven customer communication platform that says it serves [“1,000+ ServiceTitan customers”](https://www.usehatchapp.com/blog/hatch-certified-servicetitan-app) — comparable scale, overlapping product — announced its certification in February 2026, having begun preparing when the programme was announced the previous September. Whatever happened between these two companies, “a customer communication partner cannot meet these standards” is not a supportable reading.

Keep reading [ServiceTitan Integrations in 2026: What Certification Changed](https://fieldcamp.ai/blog/servicetitan-integrations/) [How to Cancel Podium (2026): Notice Period & Contract Terms](https://fieldcamp.ai/blog/how-to-cancel-podium/) [How to Cancel ServiceTitan (2026): Contract Terms & Termination Fees](https://fieldcamp.ai/blog/how-to-cancel-servicetitan/) [Book a Demo](https://calendly.com/jeel-fieldcamp/30min)

## What actually breaks when the integration ends

This is the part the announcement doesn’t spell out, and it’s the part that determines how much work you’re facing. When a customer communication platform is disconnected from your FSM, you typically lose:

**Two-way sync of customer records.** New customers created in ServiceTitan stop flowing into Podium. Contact updates stop syncing in either direction. Your customer list in one system begins drifting from the other on day one. (If you want a sense of what a synced [customer record](https://fieldcamp.ai/crm/) should hold, our [customer data model documentation](https://docs.fieldcamp.ai/data-model/customers) lays out the fields that normally travel between systems.)

**Job-triggered messaging.** Any automation keyed to job status — on-my-way texts, appointment confirmations, reminders, post-job follow-ups — stops firing automatically. These are usually the highest-value messages you send, and they’re the first thing to break. Rebuilding them means rebuilding whatever [workflow automation](https://fieldcamp.ai/workflow-automation/) sat behind them.

**Automated review requests.** Review invitations triggered by job completion stop. If reviews are a meaningful part of your lead flow, this hits revenue on a lag of a few weeks, which is exactly when you’ve stopped watching for it.

**Conversation context inside ServiceTitan.** Message threads that surfaced against the customer record are no longer visible there. Your CSRs lose the history at the moment they need it — while the customer is on the phone. This is the single most underrated loss, and it’s why a [unified inbox](https://fieldcamp.ai/unified-inbox/) that sits on the same record as the job is worth more than most people price it at.

**Attribution.** Leads that came in through webchat or text stop being traceable to jobs and revenue.

What you generally do *not* lose: your phone number, your existing message history inside Podium, and your review profile. Those live with the comms provider, not the integration. This matters, because it changes the calculus — **the integration ending is not the same thing as Podium ending.**

## Your realistic options after ServiceTitan ends the Podium integration

There are four, and the right one depends on how much of your operation actually depended on the sync.

### 1. Keep both, run them unlinked

The lowest-effort path. Podium keeps working as a phone and messaging system. You lose automation and sync, and your CSRs do more manual work. Go in with your eyes open on one point: Podium now [sells its own field service management product](https://homeservices.podium.com/features/fsm), so the vendor you are keeping also sells a replacement for ServiceTitan, and you should expect that to come up. If you’re reconsidering Podium itself rather than just the integration, our [Podium review](https://fieldcamp.ai/reviews/podium/) covers pricing, contract terms and what users actually complain about.

**Makes sense if:** you’re mid-season, your Podium contract has real time left on it, and you were mostly using it as a phone system rather than an automation engine.

**Cost:** ongoing friction, and a customer list that drifts a little further out of sync every week.

### 2. Replace Podium with a certified ServiceTitan comms partner

Move to a communication platform that’s in ServiceTitan’s certified program. You keep ServiceTitan and keep the automation.

**Makes sense if:** ServiceTitan is working well for you otherwise, and comms is the only piece in question. If you’re less sure about that, our [ServiceTitan review](https://fieldcamp.ai/reviews/servicetitan/) covers pricing and fit in detail.

**Cost:** number porting, retraining CSRs, rebuilding automations and templates, and losing your review history on the old platform. Check your Podium contract before you commit — several contractors have noted they’re on annual terms that don’t end when the integration does. Certified options in the customer communication category do exist — Hatch announced its certification in February 2026 — but confirm any provider’s current certification status directly with ServiceTitan rather than relying on a published list, including this one.

Also worth asking directly, in writing: what is the certification status of the replacement, and what notice period would apply if it changed? You’ve just learned that this is a real question.

### 3. Rebuild the connection yourself

ServiceTitan has a public API. A middleware layer or custom integration can restore some sync.

**Makes sense if:** you have a technical resource and a specific, narrow workflow worth preserving. For a sense of what this work looks like in practice, our own [API reference](https://docs.fieldcamp.ai/api-reference) and [webhook documentation](https://docs.fieldcamp.ai/api-reference/webhooks) show the kind of event plumbing a two-way sync actually requires.

**Cost:** real development time, ongoing maintenance, and — importantly — it does not exempt you from the Marketplace rules that governed the original integration. Confirm what’s permitted before you build.

### 4. Move to an FSM where customer communication is native

Rather than reconnecting two systems, use one where messaging, webchat and the customer record live in the same product as jobs, dispatch and invoicing. There’s no integration to certify, and no third party who can be removed from the arrangement.

**Makes sense if:** this incident made you re-examine the dependency rather than just repair it, or you were already unhappy with your FSM for other reasons. Our [ServiceTitan alternatives](https://fieldcamp.ai/alternatives/servicetitan/) page is the wider comparison, and if you’re weighing the mid-market options specifically, [Jobber vs ServiceTitan](https://fieldcamp.ai/jobber-vs-servicetitan/) and [Housecall Pro vs ServiceTitan](https://fieldcamp.ai/housecall-pro-vs-servicetitan/) cover the two most common shortlists.

**Cost:** the largest migration of the four, and the wrong project to start in peak season without a plan, and if you are mid-contract [how to cancel ServiceTitan](https://fieldcamp.ai/blog/how-to-cancel-servicetitan/) sets out what leaving actually costs. If you’re considering it, the honest sequencing is: stabilise now with option 1, evaluate properly in the shoulder season.

This is what FieldCamp does, and we’d obviously like you to look at us. We’d rather say that plainly than pretend this section is neutral. Concretely, that means [two-way texting](https://fieldcamp.ai/unified-inbox/), webchat, email and calls land in one shared inbox against the customer record — see the [two-way text messaging](https://docs.fieldcamp.ai/inbox/two-way-text-messaging) and [inbox overview](https://docs.fieldcamp.ai/inbox/inbox-overview) docs — plus an [AI receptionist](https://fieldcamp.ai/ai-receptionist/) that answers the calls your team can’t ([setup guide](https://docs.fieldcamp.ai/inbox/ai-receptionist-setup-and-deployment)), an [online booking and chat widget](https://fieldcamp.ai/online-booking/) for your website ([install docs](https://docs.fieldcamp.ai/online-booking/adding-the-booking-widget-to-your-website)), and [invoicing with Stripe payments](https://fieldcamp.ai/invoicing-software/) ([payment setup](https://docs.fieldcamp.ai/payments/connect-stripe-for-online-payments-fieldcamp)).

![FieldCamp unified inbox showing a customer SMS thread alongside the customer's job history, with texting, webchat, calls and online booking in the same system as the job](https://cms.fieldcamp.ai/wp-content/uploads/2026/08/fieldcamp-unified-inbox-customer-communication-native-fsm.png-scaled.png)Texting, webchat, calls and email against the customer record — with the customer’s open, scheduled and completed jobs beside the thread. No connector in between.**And the honest limit:** FieldCamp ships a built-in review-request SMS — a system template our AI agents can send after a job, and one you can save your own variants of as [saved replies](https://docs.fieldcamp.ai/inbox/saved-replies). What we don’t do is auto-fire review invitations on job completion. And we don’t do Podium’s reputation product at all: we don’t monitor, aggregate, display or respond to reviews, and there’s no reputation dashboard. If review management rather than the request itself is what you bought Podium for, budget for a dedicated reputation tool alongside whichever FSM you land on. We’d rather tell you that now than after you’ve migrated.

## How to sequence the weeks before 15 September

**Week 1 — protect revenue.** List every automation that touches a customer: on-my-way texts, confirmations, reminders, review requests. For each one, decide whether it goes manual, moves, or stops. The review requests are the one people forget, and the one that costs money quietly.

**Week 1 — get your data out.** Export your customer list, message history and review data from Podium while your account is fully active. Do this before you make any decision. It costs an hour and it removes all the pressure from every subsequent step.

**Week 2 — call two people.** Your ServiceTitan CSM, to confirm your own cutoff date, to ask what certified options exist in this category, and to ask exactly what the switching discount covers. Your Podium rep, to ask what happens to your contract term now that the integration you bought it for is going away — [how to cancel Podium](https://fieldcamp.ai/blog/how-to-cancel-podium/) sets out the notice period, so you know the answer before you ask. Expect that second call to include a pitch for Podium’s own FSM. Take the meeting if you want it, but keep the contract question separate from it. Get both answers in writing.

**Week 2–3 — decide, don’t drift.** Drifting means arriving at the cutoff date with manual processes you never designed and CSRs inventing workarounds. Pick one of the four options above deliberately, even if the choice is “do nothing until October.”

**Week 4 — port and test before the deadline, not on it.** If you’re moving numbers, start early. Porting takes longer than anyone quotes, and doing it the week your integration dies is how you miss calls. If you’re moving to any new texting provider, budget time for **A2P 10DLC registration** as well — carrier registration for business texting is its own queue, and unregistered numbers get filtered. Our [A2P 10DLC and toll-free verification guide](https://docs.fieldcamp.ai/integrations/a2p-10dlc-and-toll-free-verification) explains what the carriers actually ask for, and it applies whichever platform you land on.

## The bigger question this raises

Whatever the specific facts here turn out to be, the structure is worth noticing.

A contractor chose ServiceTitan. They separately chose Podium. The connection between the two was governed by an agreement they weren’t party to, on terms they never saw, between two companies whose relationship they couldn’t observe. When that relationship ended, they got roughly thirty days’ notice and a suggestion.

Nine years of partnership. Roughly a thousand businesses. None of whom had a vote.

And there’s a compounding risk nobody prices at all: the partner in the middle can itself become a competitor to the platform. At that point the integration you depend on stops being a product decision and becomes a casualty of two vendors arguing about their own roadmaps. That appears to be what happened here.

You can think ServiceTitan is entirely within its rights — it is — and still conclude that depending on an integration you don’t control is a risk worth pricing. Most contractors have never priced it, because until the email arrives it costs nothing.

That’s the actual lesson, and it isn’t about Podium. It’s the same question worth asking of every connector in your stack, including ours: our [integrations page](https://fieldcamp.ai/integrations/) lists what we connect to, and our [full connections documentation](https://docs.fieldcamp.ai/integrations/apps-and-integrations-all-fieldcamp-connections) is public for the same reason — so you can check rather than assume. If you build on top of field service software commercially, our [partner program](https://fieldcamp.ai/partners/) terms are worth reading with today’s news in mind.

Not sure which option is yours?

If you’re working out what to replace, we’ll walk through your setup with you — including whether staying put is the right call this season.

[Book a Demo](https://calendly.com/jeel-fieldcamp/30min)

## Frequently asked questions

**When exactly does the ServiceTitan Podium integration end?**

15 September 2026. ServiceTitan co-founders Ara Mahdessian and Vahe Kuzoyan set the date in an email to customers on 12 August 2026. Confirm your own cutoff with your ServiceTitan CSM anyway — if the notice you received carries a different date, yours is the one that governs.

**Why is ServiceTitan ending the Podium integration?**

ServiceTitan’s on-record position, stated 18 August 2026, is that it sunset the integration after Podium’s legacy agreement expired and Podium opted not to move forward with certification, leaving the integration out of compliance with its Marketplace standards. Podium CEO Eric Rea says ServiceTitan wanted a substantial cut of revenue and wanted Podium to agree to stop building anything that competed with it, and that ServiceTitan went non-responsive for around three months before sending a termination notice. Both accounts point at the same underlying issue. Podium now sells a field service management product that competes with ServiceTitan, and ServiceTitan’s own June 2026 Marketplace policy says partners may not use the partnership to displace additional parts of its platform.

**Will I lose my phone number?**

No. Your number belongs to your Podium account, not to the integration. If you later move providers you can port it, but that’s a separate decision on your timeline. Budget extra time for A2P 10DLC re-registration if you do.

**Will I lose my existing reviews?**

Your review profiles on Google and elsewhere are yours and are unaffected. What stops is the automated request that goes out when a job is completed. Review history stored inside Podium stays in Podium — export it anyway.

**Can I keep using Podium after the integration ends?**

Yes. Podium continues to work as a standalone phone, messaging and reputation platform, and it now also sells a field service management product of its own. What ends is the automatic connection to ServiceTitan — and if you would rather leave than keep paying for the rest of your term, [Podium’s cancellation terms](https://fieldcamp.ai/blog/how-to-cancel-podium/) set out the notice you have to give.

**Does this mean Podium did something wrong?**

Nothing public supports that. Building a competing product is an ordinary commercial decision, not misconduct, and Podium says it declined certification precisely because it was unwilling to agree to stop competing. ServiceTitan is equally within its rights to decide who integrates with its platform. What you are looking at is two vendors with incompatible roadmaps and roughly a thousand contractors carrying the cost of the disagreement. Treat anyone who tells you there is a villain here with appropriate skepticism, us included.

**What are the best Podium alternatives for contractors?**

That depends on whether you need the reputation product, the phone system, or the messaging — most contractors bought Podium for one of the three and pay for all three. Podium now sells a fourth thing as well, a full field service platform, which is worth knowing before you price a renewal. Our dedicated breakdown of [Podium alternatives for contractors](https://fieldcamp.ai/alternatives/podium/) covers all three, and our guide to [ServiceTitan integrations and certification](https://fieldcamp.ai/blog/servicetitan-integrations/) explains why the connection ended in the first place. The practical first step is listing which of the three you’d actually miss.

**What are my options for keeping customer messaging connected to ServiceTitan?**

Three, in order of effort. Move to a certified ServiceTitan comms partner and keep the automation — CHIIRP is currently certified in this category. Run middleware to rebuild the sync yourself, which requires “The Works” package. Or move to an FSM where messaging is native, so there’s no connector to certify at all. Which is right depends on how much of your operation ran through the sync.

**Can middleware keep Podium connected to ServiceTitan?**

Partly. ServiceTitan has a public API and a middleware layer can restore some sync, but it isn’t the same arrangement. ServiceTitan classes these as “custom integrations” — unvetted, outside their support scope, and requiring the “The Works” subscription package to use. Confirm what’s permitted and what it costs before you build.

**What does “native” customer communication actually mean?**

That texting, webchat, calls and email arrive against the customer record inside the same system as the job — not synced in from a separate product. The practical difference is that there’s no integration in the middle for either vendor to switch off. [FieldCamp works this way](https://fieldcamp.ai/unified-inbox/); so do some other FSMs. It’s worth checking which of your current features are native and which arrive via a marketplace app, because only one of those is yours.

**Does FieldCamp integrate with Podium?**

No. FieldCamp includes customer communication natively — texting, webchat, calls and a shared inbox — so there’s no Podium connector to maintain. That also means we compete with Podium on part of its product, which is exactly the kind of thing you should factor in when reading our opinion on this story.

**I’m considering switching FSM entirely. Is now the time?**

Almost certainly not this month. Starting a full migration in peak season with a four-week clock is how you end up doing both badly. Stabilise your comms first, then evaluate properly when your calendar allows.

*FieldCamp is AI-native [field service management software](https://fieldcamp.ai/) with customer communication built in — two-way texting, webchat, calls and a shared team inbox in the same system as your jobs and dispatch. We’re used by [HVAC](https://fieldcamp.ai/hvac-software/), [plumbing](https://fieldcamp.ai/plumbing-software/) and [electrical](https://fieldcamp.ai/electrician-software/) contractors, among others. We compete directly with ServiceTitan, which is why we’ve tried to make this page useful whether or not you ever talk to us. If you want to walk through your specific setup, [book a call](https://fieldcamp.ai/book-a-demo/) — or read [how our pricing works](https://fieldcamp.ai/pricing/) first.*

**Related reading:**

- [ServiceTitan Review: Pricing, Features and Fit](https://fieldcamp.ai/reviews/servicetitan/)
- [ServiceTitan Alternatives and Competitors](https://fieldcamp.ai/alternatives/servicetitan/)
- [Jobber vs ServiceTitan](https://fieldcamp.ai/jobber-vs-servicetitan/)
- [Housecall Pro vs ServiceTitan](https://fieldcamp.ai/housecall-pro-vs-servicetitan/)
- [FieldCamp Unified Inbox](https://fieldcamp.ai/unified-inbox/)
- [FieldCamp AI Receptionist](https://fieldcamp.ai/ai-receptionist/)


---

_View the original post at: [https://fieldcamp.ai/blog/servicetitan-podium-integration-ending/](https://fieldcamp.ai/blog/servicetitan-podium-integration-ending/)_  
_Served as markdown by [Third Audience](https://github.com/third-audience) v3.6.1.1_  
_Generated: 2026-09-09 16:40:48 UTC_