Business Central Support

Functional questions, configuration and posting issues, permissions, workflows, reporting, data guidance, integrations, extensions, job queues, user questions, update readiness and planned improvements can be supported where they fall within the agreed support scope.

Each support plan includes a defined pool of hours for its stated validity period. Those hours are used for standard functional and technical Business Central support. If the included hours are fully consumed before the plan validity ends, additional support hours can be purchased at a price discussed and mutually agreed before extra work begins. Any new requirement, customization, report, integration, extension or enhancement is treated as a separate Change Request and estimated for approval before work begins.

Yes. A support engagement can combine process and configuration guidance with technical assistance for extensions, APIs, integrations, jobs, permissions and environment issues. The required resource mix is agreed during onboarding.

Yes. We can first review the current setup, extensions, integrations, open issues, access and available documentation, then define an appropriate support scope and any knowledge-transfer or remediation work needed before ongoing support begins.

Priority can be based on business impact, affected users, available workaround and the agreed support arrangement. Exact response targets or escalation rules should be defined in the applicable support agreement.

Minor agreed configuration, reporting or extension changes may be handled within the support arrangement where appropriate. Larger developments, integrations or process changes should be separately scoped so design, testing, deployment and commercial responsibilities remain clear.

Leaforge can discuss remote support for customers and partners in other regions. Working hours, communication channels, coverage requirements and commercial terms should be agreed before the support engagement begins.

Review your users, modules, extensions, integrations, request history, internal Business Central capability, operational calendar and improvement priorities. From that assessment, define the appropriate engagement term, request process, coverage and governance model.

If the requirement involves significant new development, a substantial new report or workflow, complex integration, major automation or a change that needs separate design and testing, it should normally be scoped as Customization rather than treated as routine support.

If the business is replacing its ERP, redesigning major processes, migrating substantial data, rolling out multiple companies or introducing a broad new Business Central solution, use the Full Implementation route rather than support capacity.