Partner Voice for ISPs

No more paperwork after a job.
Dispatch finally sees who has what.

It's not a dictaphone. A technician says one sentence — Partner Voice turns it into a closed work order, an outage report and a task, pushes them into your system and texts affected customers. From the van, up a ladder, even with no signal. It saves hours of retyping and the revenue of jobs that slip through the cracks.

The problem we solve

Retyping in the evening

Technicians type jobs into the system after hours — or it never happens at all.

Outages in someone's head

Service calls and faults are reported by phone and from memory → nothing traceable, no SLA.

Dispatch in the dark

"Who's where and what's pending?" only by calling around. The company rests on one person.

How it works

1
The technician dictates

After a job they say what they did — on the phone or in chat. Transcription runs on the device, even offline.

2
A structured work order appears

Customer, task, materials, measurements (dBm attenuation, Mbps), status and next step — clean and complete.

3
It flows into your system

Output to ticketing / spreadsheet / CRM, and tasks to people via WhatsApp or Telegram with a Done button.

For every role

RoleWhat they get
Field technicianCloses a job by voice in 20 s, not in the evening at a desk. Works offline — transcription right on the phone.
Dispatch / NOCAn outage report → a structured incident (area, severity, customers affected, ETA) + a task for the technician.
SupportAfter a call, dictate a summary → a note in the ticket + a suggested follow-up email.
Owner / ops"Who has what", outage status and what's overdue — a morning push. The company no longer rests on one person.

Why it fits ISPs

📴 Offline in the field

Transcription right on the phone — write it up in a cabinet with no signal, sync catches up. Audio never leaves the device.

🛠️ ISP vocabulary

Understands the jargon: FTTH, GPON, OLT/ONT, splitter, dBm attenuation, RX/TX, drop…

🙅 No company-wide rollout

Only the technician and dispatcher dictate. Everyone else just gets tasks in chat — no install, no login.

🔌 Connects to what you have

Ticketing / field-service / spreadsheet / CRM. We don't replace your system — we add a voice layer on top.

FTTHGPONOLT/ONTdBm attenuationsplitterdropoutageSLA

Integrations — it fits your operations

Voice is just the input. The value is what happens next — automatically, without retyping.

📱 SMS to customers on an outage

From one sentence about an outage, PV sends a bulk SMS to affected customers via your gateway (Twilio, SMSbrána.cz, your own). Fewer calls to dispatch.

📡 Monitoring → incident

An alert from Zabbix / UISP opens an outage in PV on its own. Dispatch assigns a technician, who closes it by voice. A closed NOC loop.

🔌 ISPadmin & your system

Jobs and outages flow as a ticket into ISPadmin or via webhook into anything (Splynx, UISP, ticketing, your own). We don't change your system.

📷 Photos, history, SLA

Photo with a job, history by address, an /pv sla overview (job/outage counts, MTTR, technician performance). Proof for the customer and management.

TwilioSMSbrána.czZabbixUISPISPadminSplynxWebhookSlack · Telegram · WhatsApp

What it saves

⏱️ Hours every week

No more evening retyping of jobs. The technician speaks, the record writes itself and is in the system instantly.

💸 Lost jobs

Nothing slips through — every job is a closed, traceable work order with measurements and a photo.

📉 Fewer calls to dispatch

Customers get an SMS on an outage and a link to report faults themselves. Dispatch gets peace to work.

Pilot — the fastest proof

1 ISP · 3–5 technicians + 1 dispatcher · Telegram bot + ISP vocabulary · 2 weeks.

The metric: closing a job by voice instead of retyping it at night + dispatch sees status in one view. Does it keep running after the pilot? Then you have a solution, not a project.

Price: one-time €25 per company (base) · 2 weeks free · no setup fee.

Optional PRO subscription €8/month for the full kit (all AI modes, sync, overviews).