What is the best way to keep an outsourced support team up to date?

Keep one place where the current answer lives and update it as part of every release. Delete old answers from macros and help articles, test the vendor's agents on likely questions, and give them one contact in product. Ingesto keeps that one place current by reading the Slack, email and docs where changes are announced.

Should we run release training for the vendor every week?

Only for big changes. Most weekly changes are small, like a pricing tweak or a permission change, and they never make it into a training session. Agents need a current written answer they can look up while they're on the ticket.

Why do agents keep sending outdated answers after we update the docs?

Because the old answer usually lives somewhere else too, most often in a macro or saved reply. Search for the old behaviour after every change and fix every copy. Ingesto flags documents that contradict a newer change so you know where to look.

Should the outsourced team be in our Slack?

They can be, but don't rely on it. Slack is good for asking questions and bad for finding the current answer. Give them one channel to ask product, and keep the answers themselves in your knowledge base.

All guides

Guide21 September 20266 min read

How to keep an outsourced support team up to date when your product changes every week

Five steps to keep an external support team current when you ship every week, using one example: moving a feature to a different pricing plan.

Sami SIngesto

The short answer

Keep one place where the current answer lives, and update it as part of every release, before customers notice the change. Then delete the old answer from macros and saved replies, check the vendor's agents can find the new one, and give them one person in product to ask. Ingesto keeps that one place current for you by reading the Slack, email and docs where changes get announced.

The example we'll use

Say that on Tuesday you move single sign-on from the Pro plan to the Business plan. Existing Pro customers keep it until renewal. Product posts about it in #releases, the pricing page is updated, and that's it.

On Wednesday a Pro customer asks your outsourced team whether they're losing SSO. The agent searches the help center, finds an article saying SSO is included in Pro, and says yes, it's included. Now a customer has been told something wrong, in writing.

Nothing about that is unusual. The change was announced, just not where the agent looks. Each step below would have stopped it.

Step 1: Keep the answers in one place, not in Slack

Slack is where changes get announced. It's a bad place to look up what's true today, because nobody scrolls back through three weeks of #releases before answering a ticket. That's true for your own team and it's worse for a vendor, who often isn't in your Slack at all.

So pick one place that holds the current answer, and have your team and the vendor both work from it. In the SSO example, that's a single "Which plans include SSO?" answer that says Business, with the rule for existing Pro customers.

The catch is that the facts live all over the place: pricing in a sheet, policy in Notion, the renewal rule in an email thread between product and finance. Copying all that into one knowledge base by hand every week is exactly the job that gets skipped when things are busy.

Where Ingesto fits

How Ingesto handles step 1

Ingesto builds that one place from the tools you already use: Slack, Microsoft Teams, Gmail, Outlook, Google Drive, Notion, Sheets, PDFs, your website and past customer conversations. When product posts the SSO change in #releases, Ingesto updates the answer about which plans include SSO, and flags the help article that still says Pro so its owner can fix it.

Your team and the vendor ask the same questions and get the same answer, with the Slack message or doc it came from and its date. If your agents draft replies with an AI assistant, Ingesto gives it the same answers over API and MCP.

Get started Book a demo

Step 2: Write each change the way an agent would ask about it

Engineering release notes say things like "moved SSO entitlement to business tier." An agent needs to know what the customer will ask and what to say back. For the SSO change, that's:

"Am I losing SSO?" Not until your renewal date. After that, SSO needs the Business plan.
"Can I keep it if I stay on Pro?" No. Point them to the upgrade page, or to their account manager if they're on an annual contract.

Two or three lines like that for every release, including the small ones like a permission change or a button that moved. Someone on your side should own writing them, and product should agree that nothing customer-facing ships without one. If product ships changes without telling support, no process further down will fix that.

Step 3: Delete the old answer

Most teams stop after updating the docs, and the old answer goes out anyway. In the example, the help article still said SSO was in Pro, and there's probably a macro called "SSO setup" that says the same thing.

For every change, search your macros, saved replies, help articles and pinned messages for the old behaviour, and fix or remove them. It takes ten minutes, and it's the step that actually stops the wrong answer reaching a customer.

Step 4: Test the vendor with real questions

Before the change goes live, send the vendor's team lead the two or three questions from step 2 and ask their agents to answer them using only your knowledge base. If they can't find the answer, you've found a gap before a customer did.

A few days after launch, read five or six tickets about the changed feature. If the old answer still shows up, trace where the agent got it from and fix that source.

Step 5: Give the vendor one person to ask

Your own agents can walk over to product and ask. An outsourced agent can't, so they guess or wait. Give the vendor's team lead one named contact in product and a place to post questions, and answer them quickly.

Those questions are useful. Each one shows you something your knowledge base doesn't cover yet, so add the answer there and not just in the reply.