Basecamp is available from the public integrations page at https://lengrowth.com/integrations.

Use Basecamp when the customer wants LenGrowth activity to stay close to the project workspace instead of living only inside LenGrowth.

The metadata for Basecamp says it is used for:

The owner summary says it keeps the growth strategy focused and simple within Basecamp projects.

That gives you the correct support framing. Basecamp is for a simple, project-led workflow where the team wants strategic updates and to-do alignment inside the project space they already use.

The Basecamp card uses the normal integrations page patterns:

When the card is opened, the setup copy says: Set up a Basecamp Chatbot and paste your Account ID below.

The input label is Basecamp Account ID.

After a successful connection, the card can show:

The integration metadata can also show Configured or Account ID saved locally, which is a helpful detail if the customer is asking whether the company profile already has the account saved.

Like the other integrations on the page, Basecamp belongs to the selected company. The integrations page does not connect in the abstract. It connects for the company that is active in the header.

If the user has no company selected, the page will ask them to select or create a company first. That is why support should always check the company context before troubleshooting the Basecamp connection.

The technical guidance in the product says the customer needs:

The setup instructions then say:

The product also says the setup takes about 5 minutes. That is useful if you are setting expectations in chat without overpromising speed or hiding the manual steps.

Once connected, the Basecamp integration unlocks two visible outcomes in the product:

The language here is intentionally narrow. It does not promise every possible Basecamp feature. It promises Campfire updates, the chatbot connection, and alignment with the project workflow.

If the customer is asking whether Basecamp supports broader project management, keep the answer tied to the actual code. The integration is about project-focused growth milestones and Campfire alerts, not about turning LenGrowth into a separate Basecamp clone.

Yes. The product metadata says it supports Basecamp 3/4 project access and the integration data says it works with modern Basecamp versions through chatbot and API infrastructure.

It is the project-level connection that lets LenGrowth interact with Campfires and keep the project aligned with growth updates.

The Basecamp experience is intentionally described as simple and focused. The product positioning says it uses a Project Heartbeat approach, which means it should send high-signal alerts rather than flooding the project with noise.

Do not answer that as a blanket yes unless the customer has actually linked the right project ID and bot setup. The connection is tied to the selected company and to the Basecamp project that is linked in the setup.

If you need a one-line explanation for chat, use this:

Basecamp is a workflow app on https://lengrowth.com/integrations that connects a selected company to a Basecamp project through a chatbot and Basecamp Account ID, so LenGrowth can post Campfire heartbeat updates and keep growth tasks aligned with the project's to-do flow.

If the customer cannot connect Basecamp, the product guidance points to a few specific checks:

If the card still shows disconnected, ask the customer to confirm that they entered a Basecamp Account ID and that the selected company is the correct one.

If the card is already connected but the setup still looks incomplete, the card will usually show the account as configured but not fully ready. In that case the issue is usually in the Basecamp-side project configuration, not in the LenGrowth page itself.