Every client. Every system they run on.
Servora runs the whole client relationship and the technology behind it. Win the work, answer tickets on the clock, then reach into the client's computers, phone system, accounts, domains and backups from the same record, with every change previewed, approved and reversible.
In use every day. We run Servora across the businesses we own: restaurants, offices, service companies and manufacturing, from the first call with a client to the invoice.
- DealMoved to AcceptedOwner and stage history kept
- ProposalVersion 2 accepted in the portalWritten in French, revision approved
- TicketWorkstation will not join the networkResponse clock running
- Remote supportFront desk PC restartedApproved first, then confirmed back online
- TimeSite visit approvedParts and the client's signature attached
A client is sold, served and billed by different tools.
In most service businesses each stage of the relationship lives in its own system, and each handoff loses something. The technical side is worse: remote access, monitoring, backups, phones, accounts and domains each have their own console, and none of them knows which client it belongs to.
- SellUsually a spreadsheet or a sales tool
Lost at the handoffWho promised what, and why the client said yes.
- ProposeUsually a document and an email thread
Lost at the handoffWhich version the client actually accepted.
- SupportUsually a help desk
Lost at the handoffThat this client is in the middle of a project.
- DeliverUsually a project tool
Lost at the handoffWhat was sold, and what changed since.
- BillUsually accounting software
Lost at the handoffWhich hours and approved changes are billable.
Company, people, deals, proposals, tickets, projects, time and email conversations are kept together with the client's computers, phone system, accounts, domains and backups. Each stage reads what the stage before it wrote.
The same record, read four ways.
Pick a moment in the relationship. Each view below is drawn with fictional data; the list beside it is what the product does at that moment.
Qualified
Proposal sent
Accepted
- Leads convert to clients with a duplicate check on the web domain.
- Every deal keeps its history: amount, stage and owner changes, with views for overdue and stale deals.
- Proposals are versioned, a revision needs an approved version or an owner's recorded reason before it goes out, and proposals can be written in English or French.
- Forecasts show the weighted pipeline, deal aging and how fast deals move between stages.
- Tickets arrive by email and through the portal, sorted into queues, with request, incident and change types and parent and child links.
- Response and resolution clocks run on business hours.
- A service catalog, a knowledge base, and a satisfaction survey once a ticket is resolved.
- Internal notes stay separate from the replies the client sees.
- Projects on a board and a roadmap, attached to the client they belong to.
- Change requests the client approves in the portal; approved, priced changes become unbilled work.
- Time is submitted and approved, with utilization reports.
- Site visits record parts and the client's signature, and a summary goes to the portal.
- Clients sign in with a password or a code sent to the email address they were invited with.
- They see their own tickets, projects, proposals, documents and help articles.
- Proposals and change requests are approved where the client already is.
- Every email conversation stays on the client's record.
Reach any computer, straight from the ticket.
Every computer you look after is enrolled against the client it belongs to. A technician opens it from the ticket they are already working on, sees its health at a glance, and fixes the problem without a drive to the site.
- Screen sharing and terminal
Take over the screen with the user's consent, or work unattended where the client has agreed to it in writing.
- One-time support codes
For a computer that is not enrolled: a code that works for 15 minutes to 4 hours. Session links expire after 30 minutes.
- Hardware consoles
Reach a server's own screen and keyboard, even when it will not start. Every launch is recorded.
- Enrollment links
One link per computer or per site, with an expiry date and a use limit, and revocable at any time.
- System details, running processes and services, with end task and service start, stop and restart.
- Event logs and installed software, with installs, updates and removals.
- Network and security status, printers and their drivers.
- Browse the computer's files and run a reviewed script.
Know first. Fix it before the call.
Servora watches every enrolled computer, server and network device and ties each alert to the client it affects. A failing check opens one ticket, not one a minute, and warranties are flagged 60 days before they end.
- 1A check fails
Disk space on the dental group's file server crosses its critical line.
- 2Is it planned?
Inside a maintenance window, or muted for 4 hours, 24 hours or 7 days, it stays quiet.
- 3Is something upstream already down?
Checks can depend on each other, so a dead switch raises one alert, not twenty.
- 4One ticket, on the client's record
The alert opens a ticket once, with the device and the check attached, and the response clock starts.
A backup only counts once it has been restored.
Every backup job is tracked against its client: when it last ran, when it last succeeded, and when someone last proved it restores. A job that goes quiet is flagged long before anyone needs it.
A job with no success in 48 hours is flagged, and the threshold can be set per job.
The date of the last proven restore sits next to every job, so an untested backup is visible.
A failed or stale job raises an alert on the client's record, and the retention policy is kept with it.
Every client's phone system, run from their record.
Each client's phone system is mapped to their company, with its extensions, numbers and seats. A change shows exactly what will be different before it is made, checks run before anything is written, and every change can be undone.
- Extensions, numbers and seatsListed per client, next to their tickets and contracts.
- Create or edit an extensionFrom a request, with the result previewed first.
- Route a numberSend a main line to a person, a ring group or after-hours voicemail.
- Disable or re-enable a lineNeeds a manager's approval.
- Down and call quality alertsA phone system that drops or sounds poor opens a ticket like any other device.
- The number belongs to this client's phone system
- Every extension in the group exists
- Nothing has changed since the preview
Accounts, licences and sign-in, checked every day.
Connect a client's Microsoft 365 or Google Workspace and Servora reads their users, multi-factor coverage and licences, then lists what needs attention. The fixes are right there too, each one previewed, approved, read back and reversible.
- Preview
- Approve that preview
- Apply
- Read back
- Undo if needed
Domains that never lapse. Search that keeps climbing.
Servora watches each client's domains, DNS records, certificates and mail settings, and changes DNS the careful way. On the same record it tracks how the client's website performs in search, and turns the gaps into a plan the client can follow.
- Draft
- Test run
- Approve
- Apply
- Verify
- Roll back
Mail (MX), name server (NS) and text (TXT) records, and the domain itself, need a second approver. A change only applies if nobody has touched the zone since it was approved.
- Almost page one"brand identity studio", position 11
- Seen, rarely clickedThe services page
- Losing groundThe portfolio page
- Proposed
- Approved
- Done
- Measured
Powerful tools, careful hands.
Restarting a server, routing a phone number, changing a DNS record or blocking an account all follow the same path. The person asking sees a preview, the person approving signs off on that exact preview, and Servora reads the result back and keeps the way to undo it.
Health, logs, processes and settings. Nothing changes.
Everyday fixes, recorded against the ticket.
Restart, shut down, install or remove software.
The approver reads the whole script before it runs.
- 1Preview
What will change, before and after.
- 2Approve that preview
Approval is tied to the exact change shown.
- 3Second approver
For the riskiest changes, a second person signs.
- 4Apply
Only if nothing moved since the preview.
- 5Read back
Servora checks the result really took.
- 6Undo
The way back is kept with the change.
AI drafts ticket replies and suggests when to escalate; a person sends. When an assistant acts, it acts as a named staff member with their own time-limited access, and waits for the same approvals. Passwords and secrets are removed before anything reaches it.
Everything a client needs, on one record.
Sales, service, delivery, operations and the client portal in one platform, so your whole team works from the same history.
In Servora
- Companies, contacts and leads, with activities and commitments
- Deals and forecasts, with full stage and owner history
- Proposals, versioned with approval rules, in English or French
- Service desk with queues, response and resolution clocks
- Service catalog and knowledge base
- Satisfaction surveys after a ticket is resolved
- Remote support, with screen sharing, consoles and one-time codes
- Monitoring with maintenance windows, dependencies and warranty dates
- Backups with stale flags and restore tests
- Phone systems, with extensions, numbers, routing and alerts
- Microsoft 365 and Google Workspace users, sign-in and licences
- Domains, DNS, certificates and mail settings
- Search performance with a plan and a monthly report
- Projects on a board and a roadmap, with client-approved changes
- Time submitted, approved and reported
- Site visits with parts and signatures
- Client portal for tickets, projects, proposals and documents
- Shared email conversations kept on the record
- Shared client files, with a 30-day trash you can restore from
- Roles across 19 modules, each set to none, read, write or manage
- Client reports: service status, quarterly reviews, and monthly monitoring, backups, search and phones
- Assessments: security baseline, executive assessment, technical audit, network and Wi-Fi
- Shared as a PDF in the client portal, with a fingerprint anyone can verify
- Automation health: failures become tickets, expiring credentials are tracked
Built for how you work
- One history per clientEach stage reads what the stage before it wrote.
- Proposals in English or FrenchWritten in the language the client reads.
- Clocks on business hoursResponse and resolution are measured on your hours.
- Previewed, approved, reversibleChanges to client systems show a preview, wait for approval and keep a way back.
- Invitation-only accountsYour team decides who gets in, and what each person sees.
- Works on a phoneThe application adapts to any screen, in the office or on site.
Nobody signs up. Everyone is invited.
Apart from a sign-in screen, this page is the only public part of Servora. The application and the client portal open to people your team has invited, and each person sees what their role allows.
No way in
- Visitors see this page and a sign-in screen, nothing else.
- A demo request reaches our team, not the application.
Invited, then given a role
- An owner or admin sends the invitation.
- The role decides the starting access: Owner, Admin, Sales manager or Salesperson.
- Each of the 19 modules can be set to none, read, write or manage, and only an Owner can make someone an Owner.
Invited to their own portal
- The client is invited at the address on their contact record.
- They sign in with a password or a code sent to that address.
- The portal shows their own company's work, nothing else.
Book a demo.
We show Servora running on fictional data, and how it would fit the way your team works.
Where clients, requests, projects, hours and client systems live now, and where they get lost.
The client record and the operations tools on this page, in the running product.
How Servora would fit your clients, your services and your team. If it is not the right tool for you, we will say so.