The website is down
Failure, HTTP 500 error, missing files, damaged database, or a broken state after an update or previous contractor.
Recovery and stabilisation
Vis-Sol services
From recovering an existing website to a dedicated VSA instance.
We do not start with a list of technologies. We establish what is not working, what must be preserved and what outcome is required. Then we choose the smallest professional scope that can deliver a useful result.
Working model
Diagnosiscurrent state and risk
Scopeone primary outcome
Developmentthe next step follows the result
Choose your current situation
You do not need to know the formal name of the service.
Select the situation that best describes the problem. Each one leads to a primary scope and a concrete first action.
The website works but is outdated
It is slow, weak on mobile, has outdated content or problems with SEO, forms or analytics.
Modernisation and updateYou need a new website
A new brand, a new offer, a new information architecture or a service designed from the start for future VSA integration.
New VSA-ready websiteThe process no longer fits inside a website
You need authentication, roles, data, statuses, a panel, CRM, dashboard or internal tool.
Application or panelYou want an assistant on an existing website
VSA should answer from company knowledge, collect leads, structure service requests and guide users through the site.
VSA ConnectYou want to validate automation first
One process is repetitive, but you need evidence of value and clear metrics before production.
VSA PilotThe pilot is ready for production
You need a dedicated instance, Dashboard, modules, limits, data, monitoring and clear Vis-Sol responsibility.
VSA InstanceYou need ongoing care
Updates, backups, monitoring, fixes, website development and maintenance of VSA knowledge or modules.
Maintenance and development01 / emergency situation
Website recovery and stabilisation.
First we secure what still exists. Only then do we repair structure, configuration and operation. A redesign must not come before regaining control over the service.
- inventory of files, database, domain and configuration
- recovery from backup, archive, database or available materials
- repair of paths, SSL, forms and core dependencies
- removal of obsolete copies, logs, old environments and abandoned projects
Outcomecontrol before development
01Secured databackup of the available state02Stable productioncritical functions are operating03Clean structureno abandoned copies or environments04Risk reportwhat still requires modernisation
Modernisation without chaospreserve what still has value
01AutoAuditproblems and priorities02Change planwhat to improve and what to rebuild03Implementationperformance, mobile, SEO, forms04Measurementverify the result after changes
02 / existing service
Website modernisation and update.
If the foundation is useful, we do not rewrite everything by default. We repair the architecture, performance and critical user paths, updating only the layers that block further development.
- code, CMS, PHP and dependency updates
- responsiveness, accessibility, performance and technical SEO
- content, forms, analytics and conversion points
- preparation for future VSA Connect integration
03 / new foundation
A new website or VSA-ready service.
The project starts with the objective, audience and action the user needs to complete. Technology is selected later.
Concept and architecture
Information structure, sections, user paths, content, FAQ and conversion points.
Design and implementation
Responsive interface, code, backend, forms, SEO, analytics and testing.
VSA readiness
Connect integration points, structured knowledge, events, routing and room for Leads or Service modules.
04 / process and data
Web application, panel or internal tool.
When authentication, roles, data, statuses and approvals are required, a standard website stops being the right tool. We design the solution around the real workflow.
- process map and data model
- roles, permissions and user panel
- validation, statuses, reports and integrations
- option to connect VSA modules
When an application makes sense
Datamust be stored and searchable
Rolesdifferent users access different functions
Workflowthe case moves through statuses and approvals
05 / VSA on an existing website
VSA Connect — a communication layer connected to company knowledge.
VSA Connect links a client's website or system with its dedicated VSA instance without transferring VSA Core source code to the client. The widget, endpoint and routing are assigned to the correct instance, approved knowledge sources and handoff scenarios.
Connect
Widget, live key, handshake, origin control and communication with the correct tenant.
Knowledge
Import, organisation and control of the information VSA is allowed to use.
Scenario
Questions, leads, service intake or another defined workflow segment with an agreed escalation path.
Navigation
Opening the correct modules and guiding the user through the website without guessing routes.
VSA Pilotone process, clear criteria
01Current statetime, frequency, errors02Boundarieswhat VSA does and what remains human03Testknowledge, scenarios, exceptions04Decisionstop, improve or deploy
06 / proof of value
VSA Pilot for one process.
VSA Pilot validates one process in a real environment before a production instance is launched. Calculate the process value before the pilot. It answers whether the use case saves time, improves completeness and keeps responsibility within the agreed boundaries.
07 / production
VSA Instance and production modules.
VSA Instance is an isolated platform instance assigned to one organisation and provided with a Dashboard, communication layer and selected active modules. After value is confirmed, it receives its own configuration, data, logs and agreed functions.
Isolated instance
Dedicated tenant, configuration, knowledge, limits, logs and communication channels.
Dashboard and modules
Knowledge, Leads, Service, Documents, Monitor and functions made available to the client.
Managed service
Technology, security, monitoring and VSA Core development remain on the Vis-Sol side.
08 / ongoing responsibility
VSA Care — maintenance, updates and development.
VSA Care covers maintenance, monitoring, updates, backups and development of an active instance. It establishes responsibility for fixes, availability, security, knowledge and continued module development.
- availability monitoring and diagnostics
- backups and recovery procedure
- security, content and integration updates
- configuration and tuning of VSA settings, knowledge, scenarios and modules
Principle
Monitorbefore a user reports a failure
Updatebefore technical debt accumulates
Developbased on real data and needs
Next step
Describe the current state. Vis-Sol will point to one appropriate direction.
You do not need to choose a package or technology. Explain what works today, what does not and what outcome you need.