Frequently asked questions

Power CRM is a GoHighLevel marketplace app. It installs into your GoHighLevel agency and adds the operating layer the CRM does not have: configurable client onboarding, AI-assisted data capture, documents, meetings, calendars, custom data and fax — all synced two ways against GoHighLevel contacts, custom fields and custom values.

No. It runs on top of GoHighLevel and treats it as the source of truth. Every write Power CRM owns is reconciled back into the CRM. If you removed Power CRM tomorrow, your data would still be in GoHighLevel where your workflows expect it.

Install it from the GoHighLevel marketplace and authorize it against your agency. You choose which locations to connect. From there the app discovers your sub-accounts on its own, backfills historical data if you ask it to, and keeps the OAuth connection alive with a token-refresh worker. The full walkthrough is in the setup guide.

Power CRM is priced per agency, against the number of GoHighLevel sub-accounts you run and the modules you switch on. We do not publish a tier table because a 6-location agency and a 300-location SaaS reseller are not the same product. Tell us your setup and we will quote it on a call.

Power CRM accesses your GoHighLevel data through the OAuth scopes you grant at install — contacts and their custom fields, location custom fields and custom values, calendars and appointments, users, and the objects the modules you enable require. It caches that data to serve reads instantly and to queue writes durably. The full detail, including sub-processors and deletion on uninstall, is in the privacy policy.

Power CRM handles GoHighLevel’s app.uninstall webhook. On uninstall we stop all sync workers for that account, revoke the stored OAuth tokens, and delete the cached CRM data for the affected locations. Your data in GoHighLevel itself is untouched — it was always the source of truth.

It is a configurable ladder rather than a single vendor: Claude, OpenRouter, the Anthropic API, an internal gateway, or OpenAI. Each request can run on a standard or an advanced model. Reasoning models that do not support forced tool selection are detected and handled automatically, so a model change does not break field generation.

It is grounded before it generates. The app crawls the client’s own website into a local knowledge base and passes it as context along with every other field on the record, and during generation it can call a Google Business lookup and a domain lookup to check facts. Generated values still carry a status and go through your review flow before they count as approved.

Yes, safely. Per-field client visibility controls exactly what an account-level user can see and edit, so a client can complete their own onboarding fields without ever seeing your internal notes, scope or margins.