This page keeps CRM documentation, AI settings, webhook routes, installer notes, and operator help from falling into old generic documentation links.
The CRM, public site, client portal, companion, and office nodes are different surfaces, but they should all route back through the same CreditSoft intranet.
What CreditSoft connects: public website, admin, intranet, CRM, client portal, companion, and office nodes.
Installers, update checks, license validation, local router, and the PWA shell.
Leads, roster, documents, reports, disputes, letters, and portal handoff.
Website leads, portal uploads, companion captures, Meta callbacks, and multi-office sync routes.
OpenRouter, Ollama Cloud, and OpenCode Zen provider settings used by the intranet assistant.
Release feed, installer packages, daily license heartbeat, and office package checks.
The CRM is embedded inside the intranet and uses CreditSoft's local API bridge for office workflows.
Lead nurture, onboarding follow-up, dispute reminders, payment nudges, and reactivation messaging.
CRM admin webhooks should point at the intranet API routes, not the generic CRM-only docs.
Website lead forms, portal uploads, browser companion captures, Meta callbacks, and multi-office node events should land on the office API. The CRM admin screen can show those routes, but the intranet owns the keys and sync logic.
POST /api/v1/clients POST /api/v1/clients/{cuid}/documents POST /api/v1/browser-companion/intake POST /api/v1/cluster-actions/apply POST /api/v1/cluster-db-events/receive GET /api/v1/meta/callback The assistant, CTO advice, letters, briefs, report review, and operational suggestions should use the provider selected in the intranet AI settings. CRM-only API keys are not the source of truth.
Links such as /resources#/user-guide/introduction now land on a real resources page. The hash can still point people into the guide without breaking the server route.