RingCentral
Analytics → Reports → Call Log. Set the range to the last 90 days, include inbound and outbound, then Export to CSV.
We will tell you exactly how many jobs you are losing and what they are worth. Free, no commitment, you keep the report either way.
This is a low ask on purpose. A call log is timestamps and durations — when a call came in, whether it was answered, how long it lasted, and whether someone called back. It is not financial data. We are not asking for invoices, revenue, bank records, card data, or customer names. If your export happens to include a customer name column, delete it before you send it; the audit does not use it.
One CSV export covering your last 90 days. Include inbound and outbound calls — the outbound rows are how we can see the callbacks your own team already makes, which is a large part of what the report measures.
If some of those columns are missing, send it anyway. We will tell you what we can and cannot measure from what you have, in writing, before doing anything else.
Menu names move between versions. If the exact path below does not match your screen, look for “call log,” “call history,” or “call detail” and export the last 90 days.
Analytics → Reports → Call Log. Set the range to the last 90 days, include inbound and outbound, then Export to CSV.
NextOS admin → Analytics → Call History. Choose the last 90 days, keep all call types, and download the CSV.
Ooma Office Manager → Reports → Call Logs. Select the last 90 days for all extensions and export.
Vonage Business admin → Reports → Call Logs (or Company Call Summary). Last 90 days, all users, export to CSV.
Reports → Call Log (or Phones → Call History). Last 90 days, include inbound and outbound, export. Job records are optional — see the note below.
Reporting → Calls (or your connected phone provider inside Housecall Pro). Last 90 days, export to CSV.
Calls → filter to the last 90 days → Export. Keep the answered column; it makes the read cleaner.
Any call-detail export from your carrier works, as long as it carries a date/time, direction, the other party’s number, duration, and whether the call was answered. If you are unsure, send it — we will tell you within a day whether it is readable.
A note on ServiceTitan and Housecall Pro. Those systems also hold job records. If you choose to include them, the report can compare returned calls against jobs that were actually booked, which makes the conversion figure yours rather than declared. If you would rather not, the audit still runs on the call log alone and says plainly which parts came from your records and which came from what you told us.
A written report built entirely from your own 90 days. Every figure in it is a measurement of what your business already did.
The report is yours. If you read it and never speak to us again, that is a legitimate outcome and the report is still correct.
This audit is a baseline. It documents what your business did over your own prior 90 days. If you go on to work with Vectrion, the change in booked jobs is measured against your own prior 90 days — your history, never an industry average, never a number from someone else’s case study.
A baseline comparison is not a causal claim. It does not prove that Vectrion caused any single job, and this report will never say that it does. Separating cause from coincidence takes a randomised holdout and far more time than a buying decision deserves. That holdout runs quietly in the background from day one and produces its answer when the answer is real. We do not promise a date for it, and nothing you are ever billed for depends on it.
You send your last 90 days of call logs. Vectrion reads them and returns a written report: how many calls went unanswered, how many were called back, how long the callbacks took, and what that pattern is worth in jobs at your own ticket sizes. It is free, there is no commitment, and you keep the report whether or not you ever work with Vectrion.
Timestamps and durations. A call log export shows when a call arrived, whether it was answered, how long it lasted, and whether an outbound call went back to the same number. That is enough to measure a missed-call pattern. Vectrion does not need financial records, invoices, card data, or customer names to produce the audit.
Then the audit is not available to you, and that changes which pricing track fits — not whether Vectrion will work with you. There is a flat track that requires no baseline and no measurement at all. Sharing data selects the pricing model. It never decides eligibility.
Against your own documented history. The audit establishes what your business did before Vectrion: your missed-call volume, your callback rate, your callback speed, and your own booked-job conversion on returned calls. After Vectrion starts, the change in booked jobs is compared against that baseline. It is a comparison to your own prior 90 days. It is not a claim that Vectrion caused each job.
No date is promised. A randomised holdout runs quietly in the background and can eventually separate what Vectrion caused from what would have happened anyway, but an honest causal result at contractor call volumes takes far longer than a buying decision should. Vectrion will not pretend otherwise, and will not gate a bill on it. When that proof is genuinely ready, it arrives as a bonus, not as a promise with a deadline.
You will get the report back either way. If you have not tested your own line yet, start there instead — it takes no data at all.