No. This is a build-to-order extension. ECOSIRE builds it for your specific provider and Business Central version, then installs it as a signed per-tenant extension on your environment. If you would rather we publish it through your own AppSource account or as a managed app, we can structure delivery that way — just tell us during scoping.

A typical single-provider build (one of RingCentral, Twilio, or Vonage) with standard click-to-dial, screen pop, and call logging runs about 2 to 4 weeks from the kickoff call where we confirm your provider, environment, and matching rules. Multi-provider support, Dataverse sync, or custom matching logic can extend that, and we give you a firm estimate before any work starts.

Out of the box we build against RingCentral (RingOut), Twilio (Programmable Voice), and Vonage (Voice API). If you use another cloud PBX or CPaaS provider with a REST API and webhook support, we can scope it — the architecture (codeunit HTTPS call out, webhook receiver in) is provider-agnostic.

Every build includes a post-deployment support window for bug fixes and provider re-configuration. Because Microsoft ships Business Central updates twice a year, we also offer ongoing version-compatibility maintenance so the extension keeps working across BC releases. You hold the source code either way, so you are never locked in.

The core extension targets Business Central. If your team also works in Dynamics 365 Sales, we can add an optional sync so logged calls flow into Dataverse activities via the Power Platform, keeping a single view of customer interactions across both systems. That's scoped as an add-on.

Provider credentials and OAuth tokens are stored in Business Central Isolated Storage or a secured setup table protected by a dedicated permission set — never hard-coded into the extension. Inbound webhook endpoints are authenticated, and all provider calls go over HTTPS.