Shared innovation
Reusable workflow, reliability, interface, and security improvements are developed in the shared EmpireOS product. Approved improvements can then benefit participating deployments.
INVENTED BY NEVADA EMPIRE
Shared Innovation.
Private Data.
Bring approved improvements to your dialer while keeping your company’s operating data separate from every other customer. EmpireSync is Nevada Empire’s own technology for shared innovation and private company operations.
Included in Empirical Edition · $169 per seat/month. Company data isolation applies to both editions.
Shared progress.
Your own private workspace.
Approved improvements for your company’s EmpireOS deployment.
Concept illustration. Data imports are reviewed and controlled by your team.WHAT MAKES EMPIRESYNC DISTINCTIVE
Your improvements can strengthen the platform.
EmpireSync is more than a feature list. It is an operating model for how EmpireOS improves, how those improvements reach your company, and how your information stays separate.
Company control
Your onboarding plan records the update schedule, approval contact, maintenance window, verification steps, and rollback owner before enrollment is confirmed.
Private operations
Sharing a better product does not require sharing another company’s lead lists, customer records, recordings, credentials, or operating configuration.
HOW IT WORKS
From a useful improvement to an approved release.
Choose EmpireSync during onboarding
Request enrollment, continue without it, or ask our team to walk through the options. Your choice becomes part of your setup checklist.
Agree on your release and privacy plan
Identify the company’s administrators, data owner, permitted connections, maintenance window, and recovery process.
Review and test the shared improvement
The change is integrated into the shared product and checked before release. Your company’s private data and configuration remain within its deployment.
Deploy under the agreed controls
Confirm the approved release, backups, health checks, and rollback plan. Your team verifies the workflows that matter before the release is accepted.
For example
A better callback workflow can become an approved shared product improvement. Your callback records, customer names, phone numbers, and recordings stay in your own company’s environment.
THE PRIVATE-DATA BOUNDARY
Be clear about what is shared.
Shared through the product
- Approved features and interface improvements
- Reliability, security, and support improvements
- Reusable workflow capabilities and release checks
Private to your company
- Leads, contacts, CRM records, calls, and recordings
- Users, passwords, API keys, and carrier credentials
- Reports, sales records, branding, and company configuration
Hosting and access
Licensed customer-controlled deployments require company-owned infrastructure and restricted vendor access. Your onboarding team verifies ownership, access, storage, and recovery controls before launch.
Support and operational reporting
Support uses customer-generated, redacted bundles. Approved metadata reporting may include deployment-level totals such as calls and talk time; it excludes customer content and individual call records. Your calling, CRM, and other configured providers still receive the information required to deliver their services.
BRING YOUR OWN DATA
From PostgreSQL to your EmpireOS workspace.
Our practical guide explains how to obtain a PostgreSQL database, load company lead data, export the records you approve, and import them into the dialer.
Your files or CRM→Your PostgreSQL database→Reviewed CSV→EmpireOS lead import
Open PostgreSQL & EmpireOS setup guide →Already have a suitable CSV? You can use EmpireOS’s importer directly. A separate source database is optional.
COMMON QUESTIONS
Know what you are choosing.
Is EmpireSync required?
No. You can request enrollment, continue without EmpireSync, or discuss it first. Declining EmpireSync does not remove your company’s data isolation. Agree on the alternative update process with our team.
Does another customer get access to our information?
EmpireSync distributes approved product improvements. It does not pool company databases or provide one customer access to another customer’s operating information.
Does selecting “Yes” switch it on immediately?
No. The onboarding screen saves a preference. Enrollment, release controls, and the privacy boundary are confirmed during implementation.
Will every request become a shared feature?
Requests are reviewed for usefulness, feasibility, security, and fit with the shared product. A request is not a delivery commitment; scope and timing are agreed separately.
Can we connect an existing database automatically?
The documented self-service lead workflow uses a reviewed CSV export and field mapping. Using PostgreSQL as the operational EmpireOS datastore requires a separate implementation and migration plan. The data guide explains both paths.
Build your setup around your company.
Discuss your privacy requirements, current systems, and the release process that fits your team.
Start your company onboarding →