Frequently Asked Questions

Core365 is a multi-tenant business operations platform connecting customer and project information with departmental workflows. Teams coordinate sales, project execution, field service, purchasing, financial operations, training, and related administration within one environment. Each organization operates within its tenant, with supported configuration and permission controls. Core365 is not a traditional general-ledger ERP, and it does not replace every specialized external system. The appropriate workflows and available capabilities depend on the industry, configuration, and licensed arrangement.

Core365 is an operations platform, not a traditional general-ledger ERP or complete accounting suite. Finance365 provides operational invoicing, receivables, payment administration, and job costing, while Commissions365 prepares compensation information. General-ledger accounting remains with the organization's dedicated accounting system. Any external accounting integration must be scoped to the supported implementation rather than assumed to be universal or automatic.

Core365 supports renewable energy, roofing, home automation and security, and pest control operations. Renewable energy teams can use EPC365 to coordinate intake, engineering, permitting, installation, activation, funding, and service. Security and other home service teams use applicable field sales, service, purchasing, and administration workflows; EPC365 is not their universal project management module. Industry-specific processes and available configurations should be confirmed for the organization rather than assumed identical across industries.

Core365 modules work with connected customer, project, employee, and operational information according to the supported workflow. For example, Forms365 can collect project documentation, Procurement365 can associate materials with a job, and Service365 can retain the relationship between service work and the original customer. EPC365 coordinates renewable energy handoffs while specialized modules provide their own capabilities. Not every action triggers every other module, and permissions, configuration, and release status determine what is available.

EPC365 coordinates the renewable energy customer and project lifecycle from lead acquisition through ongoing service. Shared records, project phases, departmental consoles, and queues connect intake, site surveys, engineering, permitting, interconnection, procurement, installation, inspection, PTO, activation, and funding. Supported events and conditions can move work between departments when configured requirements are met. Tenant administrators configure supported settings; advanced requirements may need Core365 development. Professional review, utility decisions, and lender authorization remain necessary.

EPC365 can move projects between departmental queues through supported events and configured milestone conditions, but not every transition is automatic. Some phases require authorized user action, verification, or approval. Organizations can configure supported phase durations, notifications, and overdue indicators to make outstanding work visible. Queue inclusion and removal follow business rules, so an empty queue does not guarantee successful completion or that all exceptions have been resolved.

The Core365 Customer Connect Portal is a customer-facing platform that gives homeowners visibility into their solar project, from the initial milestones through installation, activation, and service. Customers can track project milestones, review scheduled visits, access available documents and agreements, download equipment specifications, view text messages and permitted phone call recordings, submit referrals, and request service. When configured by the company, customers can also review and approve engineering plansets. Portal access, visible information, document availability, and customer actions are controlled by each tenant's configuration and permissions.

Service365 connects office staff, dispatchers, technicians, and customers through service tickets, scheduling, dispatch, field documentation, and follow-up workflows. Native iOS and Android apps support field activity. Eligible technicians can claim Flex Tickets under company assignment and service-area rules; dispatchers may also assign work directly. GPS and customer notifications depend on configuration. Service365 manages ongoing service rather than replacing EPC365's renewable energy lifecycle coordination, and Core365 does not perform physical service work.

Step365 is Core365's field sales and canvassing module and is included with Core365 as a standard module, without a separate module subscription. It supports field sales and territory-oriented work within the connected platform. Applicable workflows and access depend on company configuration and permissions. Organizations should confirm their territory management and canvassing requirements during implementation rather than assume that every field-sales feature or external system is supported.

Forms365 supports configurable operational forms with drag-and-drop fields, required-field rules, validation, nested conditional visibility, repeatable sections, and multi-section layouts. Supported customer and project information can prepopulate fields. Forms remain connected to the relevant records and configured workflows, giving teams structured information for operational decisions. Submission actions may save information, notify users, or update supported phases depending on configuration; not every form automatically advances work or updates source records.

Forms365 supports mobile collection and supported offline completion with later synchronization through the Core365 mobile experience. Field teams can capture applicable information while working with customer and project records. Offline availability and field behavior depend on the supported form and workflow; they are not identical for every field or action. Synchronization requires connectivity and is not guaranteed to be immediate. Do not assume automatic GPS capture, signatures, or unlimited storage for every form.

Procurement365 connects purchasing, vendor purchase orders, materials, warehouse inventory, and associated project costs. Supported orders can originate manually, from a bill of materials, configured milestones, or replenishment needs. Inventory functions cover receiving, allocations, warehouse or crew transfers, physical counts, and low-stock notifications. Vendor invoice OCR can extract supported information for purchase-order and project association. This does not establish automatic invoice approval, three-way matching, supplier integrations, or guaranteed equipment availability.

TPS365 manages third-party work and RFQ workflows, while Vendor365 manages vendor profiles, compliance documentation, and portal access. TPS365 can send RFQs to multiple vendors and organize responses and service activity. Applicable compliance issues create staff warnings and supported overrides rather than universal automatic assignment blocking. Quoted, EPC invoice, and homeowner invoice amounts depend on configuration. TPS365 is not a payment processor and does not itself execute vendor payments.

Vendor365 organizes vendor profiles, compliance documentation, and portal access connected to Core365 workflows. Supported vendor invoice and payment requests can be reviewed, approved, or denied by authorized users, with amounts, methods, statuses, and portal payment history available according to permissions. Vendor365 is distinct from TPS365's management of third-party work. Recorded payment status is not execution of a bank transfer, and documentation workflows do not independently guarantee vendor compliance.

Customers maintain the authority, utility, and HOA reference information in Spark365, Core365's Service Provider & Regulatory Knowledgebase. Organizations enter, import, review, and update requirements used in AHJ and permitting, utility interconnection, and HOA workflows. Core365 can identify the applicable AHJ and display the requirements the customer has recorded. Spark365 is not an independently verified legal database, and it does not guarantee regulatory compliance, permitting approval, or automatic updates when requirements change.

Coral365 manages company and individual licensing and registration information, jurisdictional requirements, expiration dates, and renewal work. Teams can track affected projects and use supported warnings, restrictions, renewal assignments, and follow-up workflows. Customers remain responsible for entering, reviewing, and maintaining the applicable requirements. Coral365 is included with Core365, but it does not independently verify legal obligations, automatically discover every regulatory change, or guarantee that every noncompliant sale or project is blocked.

Lender365 centralizes project-linked financing information, lender settings, stipulations, change orders, credit expirations, and funding milestones. Dedicated funding queues make outstanding coordination work visible. Integration capabilities vary by lender, program, and implementation; some actions require manual work or an external lender portal. Enabling a lender setting does not establish an API connection. Core365 does not independently originate, approve, modify, or fund loans, and queue completion does not establish lender approval or disbursement.

Finance365 supports operational invoicing, accounts receivable, collections follow-up, payment administration, and job costing. Supported project and purchasing information can provide visibility into revenue, materials, labor, subcontractor costs, and margins. Recorded payments, invoice balances, and vendor payment workflows help teams manage financial work, but they do not execute banking transactions. Finance365 is included with Core365 and is not a general ledger, full accounting replacement, bank-reconciliation system, or payroll and statutory tax-filing service.

QuickBooks integration is custom-developed to the customer's requirements rather than a standard turnkey Finance365 feature. Synchronization scope, data ownership, and the source of truth are determined during implementation. Organizations should confirm the records, direction of exchange, supported workflows, and development scope before relying on a connection. Core365's operational invoicing and job costing do not establish universal automatic accounting synchronization or replacement of the dedicated general ledger.

Commissions365 calculates sales compensation under configured plans and prepares payment information; it does not process payroll or disburse funds. Supported plans can combine flat, percentage-based, tiered, split, role-specific, and multi-level compensation, with bonuses, deductions, and milestone-based eligibility. Authorized users can manage supported adjustments and export commission-payment information for an external provider. Eligibility does not mean payment has been issued. The organization and its selected provider remain responsible for payment execution and applicable payroll obligations.

The Commissions365 Bank is an internal compensation ledger and visibility interface, not a financial institution or deposit account. Salespeople can review supported earned, pending, and paid commission information, project-linked transactions, adjustments, reimbursements, and chargebacks. Managers and administrators see information within their assigned permissions. The Bank does not hold money, transfer funds, issue debit cards, or provide banking services. Paid history represents recorded compensation information rather than proof that Core365 executed a payment.

HR365 is a lightweight HRIS included with Core365 for employee records, onboarding, documentation, hourly timekeeping, attendance, and leave administration. Supported leave workflows include requests, approvals, balances, accrual, carryover, and holiday settings according to configuration. Attendance exceptions follow company rules and require human review for employment decisions. HR365 does not automatically discipline or terminate employees, provide complete benefits administration, or process payroll. Sales compensation belongs to Commissions365 rather than HR365's hourly timekeeping workflows.

HR365 geolocation is configurable and associated with supported clock events, not continuous employee GPS monitoring. Organizations can use applicable clock-in and clock-out information alongside worked hours and attendance records when geolocation is enabled. The supported behavior depends on company settings and permissions. Attendance flags are information for authorized managers to review; they do not independently establish an infraction or make disciplinary decisions.

Learn365 is Core365's included learning management system for employee onboarding and training, without a separate module subscription. Teams can organize courses and resources from videos, documents, and links by department, team, or user, and review learner progress and badges. Mobile learning is part of the Core365 mobile experience rather than a separate Learn365 app. Iris is a complementary, optional AI knowledgebase agent; Learn365 does not establish automatic AI course generation or replacement of every specialized LMS.

DocuVault365 is Core365's own electronic signature and document workflow system, not a DocuSign integration. Supported capabilities include PDF preparation, reusable templates, configurable fields, Core365 data mapping, multiple signers, defined signing order, reminders, and desktop or mobile browser signing. Completed documents can remain associated with relevant records, and permitted users can review signing history and audit information. DocuVault365 has a separate annual license; it does not guarantee universal legal enforceability, unlimited storage, or advanced identity verification.

Analytics365 provides departmental operational consoles and an Executive Console for KPI and performance visibility. Renewable energy examples include intake, engineering, compliance, installation, procurement, inspection, activation, service, finance, and funding. Available consoles and metrics depend on the industry and configuration. Leaders can examine supported operational trends, targets, and business performance across relevant organizational views. Analytics365 provides performance visibility rather than replacing EPC365's project handoffs or the underlying work managed by specialized modules.

Authorized administrators can configure supported Analytics365 KPI targets and thresholds, while users can select available Executive Console KPIs. Supported forecasts use targets and configurable projection formulas to estimate performance; they are not predictive machine-learning guarantees. Selected consoles and KPIs support drilldowns and relevant breakdowns, depending on the metric. These views help managers investigate changes and bottlenecks, but not every KPI has the same details or interactive behavior.

Supported Analytics365 KPI views combine AI with configured business rules to explain performance changes and recommend actions. Insights help authorized managers interpret operational information and decide what to investigate or do next. They do not replace human judgment, independently correct business operations, or guarantee improved results. Commentary and supporting detail are not available for every KPI, and the organization should confirm which consoles and metrics support these capabilities.

Reports365 is a separately offered custom reporting capability alongside Analytics365's built-in consoles, KPIs, and performance scorecards. Supported reporting lets users choose fields, apply filters and conditions, save configurations, and export results from supported Core365 records. Reports365 remains Early Access, available to select customers and expanding. Availability and the licensed arrangement should be confirmed before purchase; it is not a replacement for dashboards or an automatically included entitlement with every other module.

Automations365 is a separately offered configurable workflow automation capability beyond Core365's built-in operational triggers. Built-in events may advance supported project phases or notify users according to configuration; Automations365 provides additional supported workflow automation. Automations365 is an optional paid add-on that lets you create advanced workflows using supported events, conditions, and actions. The initial release has been completed, and tenant access is being prepared. Automations365 will cost $499 per month when enabled, with the charge added to your existing Core365 bill. Automations365 is not yet available for general tenant activation. It does not establish arbitrary no-code integrations, universal access to every external API, or automatic resolution of every operational exception. New integration requirements may still require technical scoping and development.

AI-assisted engineering plan review remains Early Access, not a generally available autonomous compliance engine. Core365 is introducing review support to help renewable energy teams identify potential drawing inconsistencies, missing information, and design concerns in electrical diagrams, equipment specifications, module layouts, and plan consistency. Findings support qualified CAD and engineering review. They do not replace licensed professionals or authorities having jurisdiction, guarantee engineering accuracy or electrical code compliance, or ensure permitting approval.

Iris is an optional, separately priced AI knowledgebase agent that complements Learn365's structured training. Its confirmed role is helping users access organizational knowledge; the precise supported sources and workflows should be confirmed for the implementation. Iris expansion remains In Development and is not a newly released agent. Do not assume automatic course generation, indexing of every document, access to every tenant record, or unconfirmed recommendations. Learn365 remains an included standard module regardless of whether Iris is licensed.

Core365 AI Agents and AI-assisted features have distinct roles, release statuses, and supported workflows; they are not universally available in every module. AI Agents are optional, separately priced offerings. The organization should confirm the selected agent, sources, actions, and availability before purchase or implementation. Engineering plan review is Early Access, Iris expansion is In Development, and Service365 photo analysis is Planned. AI output supports appropriate human decisions and must not be treated as a guarantee of accuracy, compliance, or business results.

Contact365 connects supported calling and messaging services with customer, project, and other supported Core365 records. Provider capabilities and recording behavior depend on the service and configuration. Unmatched or ambiguous interactions require authorized review and manual linking rather than universal automatic matching. SMS DNC queues help teams review communication restrictions but do not independently guarantee legal compliance. Contact365 does not replace provider services or establish unconfirmed AI replies, transcription, sentiment analysis, or autonomous customer interactions.

Integrations365 supports inbound, outbound, or bidirectional exchange according to the provider's capabilities, API, implementation, and workflow. Currently listed providers have working integrations, but their logos do not establish every possible feature or universal real-time synchronization. Authorized administrators or Core365 may help activate supported connections depending on credentials and agreements. Most new integrations require technical scoping and custom development. Integrations365 is distinct from Automations365 and does not promise that every external system can be connected without development.

Admin365 supports tenant setup and ongoing administration, including roles, individual overrides, supported field and action permissions, organizational access, security settings, branding, communications, and operational configuration. Authorized administrators manage the settings available to their tenant and can review supported settings history. Managing an existing integration setting is not creating an arbitrary no-code connector. Available controls depend on configuration and permissions; Admin365 does not guarantee universal enforcement, automatic rollback, immutable audits, or a particular compliance certification.

Organizations should confirm their required tenant access controls and security settings with Core365 during implementation. Admin365 provides supported role, field, action, and organizational access configuration, together with applicable security settings. A public product description is not proof that a particular control is enabled for every tenant or that a certification or regulatory requirement is met. Requirements involving retention, identity, data handling, integrations, and administrator permissions should be reviewed for the actual deployment rather than assumed from generic claims.

Standard Core365 modules are included with Core365, including Learn365 and Step365, rather than billed as separate standard module subscriptions. The platform includes unlimited users and projects and native iOS and Android apps under its arrangement. Automations365, Reports365, and AI Agents are separately priced optional offerings. DocuVault365 has a separately billed annual license. Inclusion does not mean unlimited messaging, storage, external API consumption, or third-party services; applicable licensing and supported usage should be confirmed before purchase.

The separately billed annual DocuVault365 license supports unlimited users, documents, signatures, and templates under its licensed arrangement. It is not presented as per-user, per-document, or per-signature billing, and no public amount is stated here. This license is distinct from standard Core365 module inclusion. Unlimited document and signature entitlement does not establish unlimited storage, every identity-verification service, or universal legal compliance. Confirm the arrangement and implementation requirements directly with Core365.

Core365 implementation should be scoped around the organization's industry, workflows, data, permissions, and supported integrations. Supported tenant settings can be configured, while advanced workflows and most new integrations may require Core365 development. Data ownership, exchange direction, and external-system responsibilities should be agreed for the implementation. A fixed timeline, migration scope, training package, or price is not established by this FAQ; those details require confirmation for the organization's requirements.

Core365 does not independently approve or fund loans, execute payroll or bank payments, provide a general ledger, file taxes, or guarantee permitting, regulatory compliance, or installation quality. It coordinates supported operational workflows and makes records, requirements, and outstanding work visible. Professional decisions, customer-maintained requirements, external providers, and authorized approvals remain part of the process. Configuration and AI-assisted information do not mean every exception resolves automatically or that every specialized external system can be removed.