Connect an AI assistant to set up your CRM

Start with get_setup_guidance and inspect_company_setup. Explain your services, people, lead sources, scheduling, production process and existing data. Unknown facts stay open rather than becoming invented prices, consent or assignments. Existing accounts need a gap review, not a reset.

Use list_setup_templates, preview_setup_template and apply_setup_template. Seven packs cover roofing, general remodeling, painting, bathroom remodeling, flooring, windows and doors, and handyman services. The same engine powers Get started in the web app.

Preview returns exact additions, existing settings retained and conflicts. Apply uses that preview hash. Repeating a pack or adding another trade reuses stable identities and shared workflows. Existing customizations are preserved. Message templates, rules, queues and sequences remain inactive; installation sends nothing and does not replay customer history.

New administrator connections include setup, job/service operations, imports and contractor workflows by default. Direct control lets your assistant apply requested setup, edit contacts and operational records, review valid imports and explicitly activate validated automation drafts. Saving a draft does not activate it.

You can disable capabilities and choose Require my approval for setup changes, imports and automation activation. Existing keys keep their selected scopes and review policy until their owner changes them. Approval mode directs the assistant to the relevant CRM review page.

Use get_contact and update_contact to correct names, email, phone, postal address and notes. Exact revisions prevent overwriting newer edits and the timeline records changed values. Changing a number clears consent for the new number. Assignments, appointment results and financial amounts use their dedicated tools.

Preview imports, reconcile duplicates and relationships, and preserve opt-outs and source evidence. A phone number or historical message is not new consent. Imports and setup tools do not send follow-ups.

Only an active company administrator can create a connection in Settings → AI setup. Connections last 30 days and are tied to the company and administrator. The key is shown once; store it in the assistant’s secure credential field, not in ordinary chat.

For compatible remote MCP clients use https://app.kineticview.io/api/mcp with bearer-token authentication. OAuth-only clients are not supported by this connection. Local stdio clients can use scripts/mcp-server.mjs with KINETIC_VIEW_URL and KINETIC_VIEW_AI_TOKEN in secure environment storage. Both transports use the same tools and connection policy.

External AI connections do not expose provider credentials, manufacture consent, bypass opt-outs or process charges. Staff changes require the separate Allow team management capability on an active administrator-owned connection. Roster creation, invitations and login access are different actions. Informational help and guided setup never grant staff login. Provider connections and a real customer-journey test need independent evidence.

Revoke a connection if it is exposed or no longer needed. Every request checks expiry, revocation, active administrator status, company and capability scope. Unauthorized requests need a valid connection; stale previews or revisions need a fresh read and review. Do not retry blindly after a message or import without checking whether it succeeded.

External AI/MCP connections remain separately scoped integrations. Setup and help in this app use deterministic questions and published guides, not a chat model. A connection capability never authorizes an informational help reader to change records.