On this page
Where a client gets lost The record, read four ways Remote support Monitoring Backups Phone systems Microsoft 365 and Google Workspace Domains and search Every action, approved What is in it Who gets in Book a demo
Business platforms
TruePOS MERIDIAN ROVE RYVO Hello Servora Tally Confetti
Connected locations
Chirp Lumi Lookout
Documents and knowledge
Scribble Flip Folio Lex The full portfolio For franchisors
Services
Digital Transformation
The company
Main site Technology self-audit Book a demo
ServoraClient relationships and service delivery

Every client. Every system they run on.

CRM Proposals Service desk Remote support Monitoring Backups Phones Domains Search Client portal

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.

Sell · Serve · Operate · Inform Invite-only · Built by NoLimits
01Where the story breaks

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.

Five handoffs, one clientIllustrative - not a screenshot
  1. Sell
    Usually a spreadsheet or a sales tool

    Lost at the handoffWho promised what, and why the client said yes.

  2. Propose
    Usually a document and an email thread

    Lost at the handoffWhich version the client actually accepted.

  3. Support
    Usually a help desk

    Lost at the handoffThat this client is in the middle of a project.

  4. Deliver
    Usually a project tool

    Lost at the handoffWhat was sold, and what changed since.

  5. Bill
    Usually accounting software

    Lost at the handoffWhich hours and approved changes are billable.

ServoraOne record from the first call to the invoice draft.

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.

02Four moments with one client

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.

PipelineIllustrative - fictional data

Qualified

Law office
Managed IT
Distributor, two warehouses
Network refresh

Proposal sent

Dental group
Version 2 in review
Accounting firm
Help desk

Accepted

Design studio
Invoice draft created
What it does
  • 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.
03Remote support and screen sharing

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.

Remote console - Front desk PCIllustrative - not a screenshot
Front desk PC
Dental group · Laval clinic
Online
Processor
12%
Memory
61%
Disk
88%
Running for
6 days
ProcessProcessorMemory
Practice management4%1.2 GBEnd task
Print spooler38%310 MBEnd task
Web browser6%840 MBEnd task
Share screen Terminal Restart service Restart computer: needs approval
Fictional data. The layout explains the idea; it is not the product screen.
  • 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.
04Monitoring

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.

Fleet health - three clientsIllustrative - not a screenshot
Dental group1 critical
Law officeAll healthy
Distributor, two warehousesMaintenance window
HealthyWarningCriticalPlanned work
Fictional data. The layout explains the idea; it is not the product screen.
  1. 1
    A check fails

    Disk space on the dental group's file server crosses its critical line.

  2. 2
    Is it planned?

    Inside a maintenance window, or muted for 4 hours, 24 hours or 7 days, it stays quiet.

  3. 3
    Is something upstream already down?

    Checks can depend on each other, so a dead switch raises one alert, not twenty.

  4. 4
    One ticket, on the client's record

    The alert opens a ticket once, with the device and the check attached, and the response clock starts.

05Backups

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.

Backup jobs - Dental groupIllustrative - not a screenshot
JobLast resultRestore test
Practice database
Nightly · kept 90 days
Succeeded 02:14Tested 12 days ago
File server
Nightly · kept 90 days
Stale: 52 hoursTested 41 days ago
Workstation images
Weekly · kept 8 weeks
Succeeded SundayRestore test due
Imaging archive
Nightly · kept 1 year
Failed: ticket openedTested 9 days ago
Fictional data. The layout explains the idea; it is not the product screen.
Stale after 48 hours

A job with no success in 48 hours is flagged, and the threshold can be set per job.

Restore tests on record

The date of the last proven restore sits next to every job, so an untested backup is visible.

Failures become tickets

A failed or stale job raises an alert on the client's record, and the retention policy is kept with it.

06Business phone systems

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.

On every phone system
  • 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.
Change request - route a numberIllustrative - not a screenshot
Send the main number to the front desk group
Dental group · main line 514 555 0100
Before
Rings reception, extension 201
After hours: voicemail
After
Rings the front desk group: 201, 202 and 205
After hours: voicemail
  • The number belongs to this client's phone system
  • Every extension in the group exists
  • Nothing has changed since the preview
ApplyUndo stays available
Fictional data. The layout explains the idea; it is not the product screen.
07Microsoft 365 and Google Workspace

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.

Findings - Law officeIllustrative - not a screenshot
Multi-factor sign-in
38 of 42 people
2
Administrators without multi-factor sign-in
The accounts that can change everything else
Fix now
3
Disabled accounts still holding a licence
Former staff, still on the invoice
Review
5
Licences paid for and unused
Assigned to nobody
Review
Fictional data. The layout explains the idea; it is not the product screen.
People
Create a userSend a password reset linkBlock or unblockSign out everywhereOffboard and restore
Access
GroupsLicences
Mail and files
Message traceInbox rulesHand over a departing user's files
Every change
  1. Preview
  2. Approve that preview
  3. Apply
  4. Read back
  5. Undo if needed
08Domains and search

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.

Domains - Design studioIllustrative - not a screenshot
Registration
Warns at 30 days, critical at 7
Renews in 23 days
Certificate
Warns at 14 days, critical at 3
Valid 61 days
Mail settings
Checked so mail arrives and is not spoofed
MXSPFDKIMDMARC
DNS records
Watched, with every change kept in history
Unchanged
A DNS change
  1. Draft
  2. Test run
  3. Approve
  4. Apply
  5. Verify
  6. 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.

Fictional data. The layout explains the idea; it is not the product screen.
Search - last 28 daysIllustrative - not a screenshot
Clicks from search
1,284
Mobile page speed
Good
Opportunities
  • Almost page one"brand identity studio", position 11
  • Seen, rarely clickedThe services page
  • Losing groundThe portfolio page
The plan
  1. Proposed
  2. Approved
  3. Done
  4. Measured
A monthly report goes to the client. Servora reads the website; it never edits it.
09Every action, approved

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.

Level 0
Look

Health, logs, processes and settings. Nothing changes.

Level 1
Routine

Everyday fixes, recorded against the ticket.

Level 2
Approved first

Restart, shut down, install or remove software.

Approval required
Level 3
Scripts

The approver reads the whole script before it runs.

Approval required
  1. 1
    Preview

    What will change, before and after.

  2. 2
    Approve that preview

    Approval is tied to the exact change shown.

  3. 3
    Second approver

    For the riskiest changes, a second person signs.

  4. 4
    Apply

    Only if nothing moved since the preview.

  5. 5
    Read back

    Servora checks the result really took.

  6. 6
    Undo

    The way back is kept with the change.

AI help, under the same rules

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.

10What is in 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

Clients and sales
  • 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
  • Service desk with queues, response and resolution clocks
  • Service catalog and knowledge base
  • Satisfaction surveys after a ticket is resolved
Operations
  • 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
Delivery
  • Projects on a board and a roadmap, with client-approved changes
  • Time submitted, approved and reported
  • Site visits with parts and signatures
Clients and access
  • 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
Reports and automations
  • 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.
11Who gets in

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.

The public

No way in

No public sign-up
  1. Visitors see this page and a sign-in screen, nothing else.
  2. A demo request reaches our team, not the application.
Your team

Invited, then given a role

Invitation from an owner or admin
  1. An owner or admin sends the invitation.
  2. The role decides the starting access: Owner, Admin, Sales manager or Salesperson.
  3. Each of the 19 modules can be set to none, read, write or manage, and only an Owner can make someone an Owner.
Your clients

Invited to their own portal

Invitation to one email address
  1. The client is invited at the address on their contact record.
  2. They sign in with a password or a code sent to that address.
  3. The portal shows their own company's work, nothing else.
12See it running

Book a demo.

We show Servora running on fictional data, and how it would fit the way your team works.

The demo
01
How your team works today

Where clients, requests, projects, hours and client systems live now, and where they get lost.

02
Servora on fictional data

The client record and the operations tools on this page, in the running product.

03
Whether it fits

How Servora would fit your clients, your services and your team. If it is not the right tool for you, we will say so.

We reply from a real address, and we do not add you to a mailing list.

This sends one email to our team. Nothing is created in Servora.