Front integration guide

How to keep Front up to date

Find the Front knowledge base articles a change to your product made wrong, before your team links them in a reply or Autopilot repeats them.

Book a demo Audit your help center for free →

Keeping help centers accurate at

The short answer

What Front offers: Your Front help center has features like the Knowledge base report, draft and published statuses with view history, and Compose for Knowledge Base to help you write help center updates.
Where it stops: None of it can see when your product changes, so updates to your help center depend on a teammate noticing a launch or a customer reacting to a wrong article.
Where Solo fits: Solo reads your code, compares it with your Front articles, flags the ones a change made wrong, and drafts fixes your team approves.

On this pageShort answer

Why it matters

Why an accurate knowledge base matters

You ship a feature on Monday, the shared inbox hears about it by Friday, and the article still describes the old flow. Meanwhile customers can't self-serve, Front's AI answers from stale steps, and public articles show the wrong thing in search.

Reduce tickets with self-serve support

An article that matches your product lets a visitor finish the task and leave. A wrong one sends them to your chat widget or inbox with the same question, now with less patience.

Front's AI agents answer correctly

Copilot and Autopilot draw on your published Front articles, and Ask Your Knowledge Base hands them to teammates with a link. A stale article is repeated to customers and agents just as quickly as a good one.

Public articles show up correctly in search

Search engines and AI answer engines quote public articles, so one that no longer matches your product gives the wrong answer before anyone reaches your team.

Built-in tools

Front knowledge base maintenance tools, stage by stage

In Front, an article is read on the help center and also surfaced to agents and AI, so the tools around it are built for reach. They measure and polish articles well, but none of them can see that your product changed, which lets outdated content snowball.

Stage	Front's features	Missing features
01Know upcoming changes	Front has no feature for this stage, so notice of a change to your product has to come from outside the platform, like a product manager or a developer.	Nothing warns you that an article is about to become out of date. Front doesn't read your code or launch plans, so a change reaches the knowledge base only when someone mentions it.
02Identify outdated articles	The Knowledge base report (Professional plan and above) ranks articles by views and reactions and lists search keywords with click-through rates, while Topics groups conversations by why customers wrote in.	The Knowledge base report and Topics react to customers who already read or rated a bad article. None of it compares an article with your product.
03Draft updated copy	Compose for Knowledge Base drafts articles from bullet points, fixes grammar, and expands or condenses selected text (Professional plan and above).	Compose for Knowledge Base rewrites what the author gives it, so it has no context on what changed in your product and can't propose updated copy.
04Collaborate on updates	Articles move through Draft, Published and Published with pending changes statuses, and View history shows each revision's author and highlighted differences.	View history shows who edited and which text changed, not what is wrong, so reviewers still have to find out which change to your product prompted the edit.
05Publish changes	Publish puts an article live, and the AI features pick up published changes within minutes.	Publishing is a manual step. Nothing publishes an update when a feature flag turns on, so an article goes live on someone's schedule, not when your product changes.

With Solo

Knowledge base management with Solo on top of Front

Front can't see your codebase, so it can't tell when an article stopped matching your product. Solo reads both your code and the articles in your published knowledge base, flags the articles a change made wrong, and drafts fixes. A person on your team approves each one before anything reaches your help center.

What Solo adds to Front's built-in tools

Stage	Front without Solo	Front with Solo
01Know upcoming changes	Front has no feature for this stage, so notice of a change to your product has to come from outside the platform, like a product manager or a developer.	Solo reads your recent code changes on a daily or weekly schedule and tells you which articles they touch, so nobody has to remember to mention a launch.
02Identify outdated articles	The Knowledge base report (Professional plan and above) ranks articles by views and reactions and lists search keywords with click-through rates, while Topics groups conversations by why customers wrote in.	Solo compares your published articles with your code and flags only the ones a change clearly made wrong, with the reason and the commits behind it, before customers read them.
03Draft updated copy	Compose for Knowledge Base drafts articles from bullet points, fixes grammar, and expands or condenses selected text (Professional plan and above).	Solo drafts replacement text for the affected passage from your code change, and flags images that may no longer match your product.
04Collaborate on updates	Articles move through Draft, Published and Published with pending changes statuses, and View history shows each revision's author and highlighted differences.	Each flagged article opens as a review item with the old content beside the proposed change and the commits behind it, so reviewers start with the right ones.
05Publish changes	Publish puts an article live, and the AI features pick up published changes within minutes.	Your team approves each fix, and Solo can hold it until the feature flag is enabled before updating the existing article, so nothing changes without a person's approval and nothing goes live early.

Questions

Questions about Front and Solo

What support teams on Front ask before connecting Solo.

Does Solo replace Front?

No. Your articles stay in Front and keep their URLs. Solo reads the articles in your published knowledge base and suggests changes, and your team approves each one before it goes back to Front.

How do outdated articles affect Front's AI?

Copilot and Autopilot use your published articles as a knowledge source, and changes reach them within minutes. That works in your favor when an article is right and against you when it isn't. Agents who use Ask Your Knowledge Base get the same answer with a link to the article.

Can Solo publish a fix to Front on its own?

No. Solo suggests each change, and your team accepts, edits or rejects it before anything is sent out. When you add a new article, you choose whether it goes in as a draft or as published.

How do we update knowledge base articles after a product launch?

Start with the articles about the feature you changed, then the most viewed ones in the Knowledge base report, since a wrong article costs the most there. Check any article that collects unhelpful reactions or comments after a launch. Solo does the first part for you by comparing each of your code changes with your articles.