Connector approach
TradeVulcan connects to supported systems through workspace setup, provider access, app-specific mapping, and health checks where available.
Trust and security
Security and control for connected contractor workflows.
TradeVulcan is designed to keep credentials server-side, respect workspace permissions, and give operators clean workflow context without exposing connector noise.
Clear, specific security claims.
We describe the controls in place, what depends on your connected systems, and where your team keeps responsibility.
Data handled
The data should match the workflow, not sprawl everywhere.
TradeVulcan apps should only use the data needed to recover calls, book visitors, follow up, publish proof, manage reviews, measure performance, or support approved AI workflows.
CRM and connector records for supported workflows
Customer, lead, estimate, job, call, and message context
Local proof photos, descriptions, service areas, and publishing settings
Performance facts, scorecards, goals, and workspace activity history
Billing, subscription, app access, and account metadata
Operating controls
Security is part of setup, not a buried afterthought.
Workspace permissions
Workspace access and role-based views help separate owner, manager, operator, setup, and admin work across app and dashboard surfaces.
Credential handling
Provider API keys, OAuth credentials, and connector secrets are handled server-side through connector settings and should never be pasted into public docs or support chat.
Messaging responsibility
SMS, email, review, and AI voice workflows should be configured with consent, opt-out language, send windows, and workspace-specific approval rules.
Audit and history
Supported admin, connector, billing, and app workflows keep event history or audit records so operators can review setup, syncs, and important changes.
Billing basics
Checkout, subscription, and billing portal flows use the configured billing provider. Payment details should be managed through secure billing pages.
AI and messaging guardrails
AI assistance should support operators, not surprise customers.
AI voice and drafting workflows should be enabled per workspace or app, not assumed globally.
Operators should review business rules, escalation paths, transfer rules, and sensitive topics before go-live.
The AI should not promise pricing, appointments, or service outcomes unless the configured workflow can support that action.
Support and security contact
Need a security review before launch?
Use the support or sales path to review connector access, messaging consent, AI controls, proof publishing, and go-live checks for your workspace.
Start security reviewTrust and security
Built to support secure, permissioned contractor workflows.
Your team sees clean customer and workflow context. Credentials stay server-side, access follows workspace permissions, and AI or messaging steps use operator-approved rules.
Permissioned workspaces
TradeVulcan is built around workspace access, roles, and app-specific views so teams can separate setup, manager, and operator work.
Server-side credential handling
Connector credentials and provider secrets are handled server-side through connector settings and are not shown in normal manager UI.
Consent-aware messaging
SMS, email, AI voice, and review workflows should be configured with opt-in, opt-out, send windows, and human review rules that fit the workspace.
Clean customer context, not connector noise
Managers see the customer, job, workflow, and next step through normalized facts, snapshots, audit history, and sanitized records.