Assessment & Planning: Understand your business workflow and requirements. This phase can take from 1 to 2 weeks, depending on complexity.
Installation & Setup: Installing the software on your systems, configuring basic settings. Typically takes a few days to a week.
Customization & Integration: Tailoring features to your specific needs, possibly integrating with existing systems. This phase varies greatly but often spans 2 to 6 weeks.
Training & Testing: Educating staff and performing trial runs. Usually about 1 to 2 weeks.
Configurable Modules: Customer management, scheduling, billing, and reporting can often be tailored.
Custom Fields & Data Entry Forms: Usually supported to match your business workflows.
Workflow Automation: Can be customized to automate specific tasks.
API & Integrations: EZBIS Office often supports integrations with other software via APIs.
Setup Fees: Initial setup or configuration can range from \500 to \2,000+, depending on complexity.
Training & Support: Ongoing support might be billed as a monthly subscription (~50−50−200/month) or per incident.
Maintenance & Updates: Usually included within support contracts, but some may be paid yearly or based on custom developments.
Custom Development: If you need significant features, there could be extra charges for development work.
Initial Training: Usually includes on-site or online sessions covering core features and workflows, often lasting 1-3 days.
User Manuals & Documentation: Comprehensive guides and tutorials are typically provided.
Ongoing Support: Can include helpdesk services via email, phone, or live chat, often bundled in support packages.
Training Updates: As new features are released, EZBIS may offer refresher courses or webinars.
Data Encryption: Both at rest and in transit, typically using industry-standard protocols (SSL/TLS, AES encryption).
Access Controls: Role-based permissions to restrict data access.
Regular Security Audits: To identify and mitigate vulnerabilities.
Backup & Recovery: Routine data backups with disaster recovery options.
Compliance: Depending on cloud or on-premises deployment, EZBIS may adhere to standards like GDPR, ISO, or local regulations.
Release Schedule: Usually quarterly or biannual updates, but this can vary.
Update Management: Updates are often automated or delivered via download, with notifications sent to users.
Change Logs: EZBIS typically provides documentation on new features and bug fixes.
Ownership: Typically, the business owns its data, not EZBIS.
Data Export: EZBIS usually allows exporting data in common formats (CSV, Excel, SQL dumps) for migration or backup.
Portability: Policies should specify the ease of migrating data to other systems, emphasizing data portability.
Flexibility: EZBIS Office generally allows scaling based on license count, user seats, or modules used.
Upgrade Options: You can typically add more users/modules in existing contracts, with some providers allowing pro-rata billing.
Downgrade Policies: Reducing licenses or features may be subject to notice periods and possible fees, depending on the contract terms.
Renewal Terms: Contracts are often annual, auto-renewing unless canceled within a specific notice window (e.g., 30-60 days before renewal date).
Cancellation Policies: Usually require written notice; early termination may incur penalties or fees, depending on the contract (sometimes a percentage of remaining fees or a fixed charge).
Refunds: Refund policies vary, with some providers offering pro-rated refunds if canceled early.
Notice Period: Clear terms specify how far in advance you must notify EZBIS of intention not to renew or cancel.
EZBIS Office
By EZBIS Office
