A spreadsheet is a full integration.
Everything VoiceScout does runs off what we know about your customers, not off which software you happen to own. If the answer is in a spreadsheet, it works. If it is in Jobber, it works. If it is only in your head and on the calls she answers, that works too.
Do I have last-service dates for these people?A question about data. It has the same answer whether that date arrived in a spreadsheet, from a field-service system, or from a call she took herself at nine at night.
Is Jobber connected?If any part of this product could tell which software filled a field, that would be a bug in it. Software makes the data arrive automatically. It never makes a play possible.
You are never one integration away from the thing you bought.
The usual shape of this category is a feature list with padlocks on it: the win-back campaign needs the CRM, the reminders need the scheduler, and the quote on the wall assumed you had both. We built ours the other way round, and wrote the rule down before there was anything to break it.
Read the plays it buys you on the playbook library. Every one of them names what it needs, in plain words, at the bottom of its card.
- Bring a customer list, get a win-back campaign A file with phone numbers and last-service dates is the whole requirement. Nothing has to be connected to anything.
- Bring nothing, and she starts filling it in herself Every call she answers writes down who rang, what they wanted and whether you may text them back. That is a customer list building itself while you work.
- Connect something later and nothing changes shape The same plays keep running on the same rules. What a connection changes is how the facts get here (one less thing to remember to send us), never which features you are allowed.
What each play actually needs before it can run.
Not a vendor. A fact. Here is every automatic message she sends and the one thing that has to exist first.
Scroll the table sideways to see every column.
| The play | What has to exist | Where that can come from |
|---|---|---|
| Missed call | A call that rang outAnd a number to reply to. | Us. Nothing to connect: it happens on your own line. |
| Estimate follow-up | An estimate request she tookWhich is a recording and a transcript, not a tick box. | Us. She captured it on the call. |
| Appointment reminder | A visit timeThe one thing on this list she cannot produce herself today. | A field-service system, or an uploaded schedule. |
| Review request | A finished job, and your review linkGoogle's or Facebook's. Yelp forbids asking, so we refuse that one. | Your own answer at setup, plus either source of the job. |
| Mail follow-up | A postcard scan that became a conversationWith a phone number said out loud in it. | Us. This one needs the card and the phone line to be the same company. |
| Win-back | Last-service datesAnd a phone number, which is how a person is identified here. | A spreadsheet with a date column. That is the entire requirement. |
The reminder is on that list with an honest gap beside it on purpose: she takes estimate requests and does not put appointments into a calendar, so until a schedule reaches us from somewhere there is nothing to remind anybody about. The full playbook library →
Three ways the data reaches us today. All of them end in the same place.
Downstream of this section, nothing knows which one you used, and the fourth card is the one we have not finished, said out loud rather than left off the page.
She collects it herself
The cheapest integration is no integration. Every call she answers records who rang, what they asked for, the address she checked, and the permission you have to text them back, against a customer record that merges by phone number as it goes.
- Starts on day one, with nothing to set up
- The permission is recorded beside the number, not assumed
- The questions she could not answer come back as a list you can work through
Your spreadsheet
Export your customers from whatever holds them (QuickBooks, an old scheduler, a fifteen-year-old Excel file) and hand it over. We match your column headings rather than making you rearrange them, and show you what we found before a single row is stored.
- Column headings matched automatically; nothing has to be renamed
- A ready-made template with an example row already filled in, if you would rather start from one
- A preview first: how many rows have a phone number, and which columns were ignored
The phone number is the identity, so a row without one cannot be loaded. We tell you how many those are instead of quietly dropping them.
Jobber
The connection is built: you press Connect in your portal, approve us on Jobber's own screen, and the quotes and visits you raise in Jobber start arriving on a loop, filed exactly like a request she took at two in the morning, so the follow-up runs on both without anybody choosing which is which.
- You approve it at Jobber, and you can disconnect from the same screen
- Reconnecting under the wrong Jobber login is refused, by name, rather than mixing two businesses together
- If it ever stops working, the screen says so: it never shows “connected” over nothing
- Nothing is written back into Jobber, and a draft quote is left alone until the homeowner has actually seen it
We are switching this on one account at a time rather than announcing it, because it has not yet run on enough real Jobber accounts for us to call it finished. Two honest limits while it is early: it brings customers and quotes, not service history, so a win-back still wants a file, and syncing somebody's customer list is not permission to text them, so a Jobber customer who has never contacted you is left alone on purpose.
A webhook into your own system
The shape is agreed and some of it has been built before: your leads posted to a web address you own the moment a call ends (your own software, or a catch hook on something like Zapier or Make), signed, so your end can prove the message came from us.
- What works today: the lead reaches you by email as the call ends, and by text once your texting is switched on, and everything is in the portal
- What is not true yet: there is no self-serve webhook screen, and no public API
We would rather this line read like this than have you plan a build around it. If a live feed into your own system is what decides the sale, say so. That is how it gets prioritised, and we will tell you honestly where it is that week.
An API for agencies: there is no public API today, and we would rather say that than publish a page of endpoints nobody can get a key for. If you run marketing for a lot of home-service businesses and you need one, tell us what it has to do. That conversation is how it gets built.
“Send us the file” is not a polite way of saying no.
It is the path we expect most businesses to take, so it is built like a real one. You upload a customer list; we read the headings, tell you what we understood, and wait. Only when you have seen the count does anything get stored.
What a row is worth depends on what is in it. A phone number alone makes someone
contactable. A last-service date makes them a candidate for a win-back: customers we
have not seen in a year
is a question your file can answer and your memory
cannot.
And the honest part: a list you exported in January cannot tell us anything about June. When the newest evidence behind a group of customers is stale, a campaign reports how many people it is unsure about instead of assuming they are still lapsed.
Sample data, illustrative
That is the integration. Extra columns are welcome and unread ones are named back to you. Ray has no date, so no play that depends on one will pick him up, and nothing will pretend otherwise.
Three things this page could have implied, and doesn’t.
No calendar sync
She captures the estimate request and hands it to you complete. She does not write appointments into Google Calendar or Outlook, and a reminder can only go out for a visit time that reached us from somewhere else.
No logo wall
You will not find a grid of software badges here. We connect to Jobber, to a file, and to a web address you own. Everything else on a page like this one would be a logo we borrowed to look bigger.
No two-way write-back
What comes from Jobber comes toward us. We do not create or edit anything inside your field-service system, and we would tell you before that changed.
If the thing you need is missing from this page, it is worth asking anyway: it is a short list on purpose, and what gets built next is decided by what customers keep asking for. Ask for it →
Tell us what you already use. We’ll tell you what it changes.
Usually the answer is “nothing you have to do first”. Fifteen minutes is enough to work out which plays your data can already run and which ones would be waiting on something.
Or start at the other end and hear her answer a call. The demo is a live conversation in your browser, about ninety seconds.