Support copilot preview
Prepared for the Spectrum team
Support copilot preview
Prepared for the Spectrum team
A working demo, not a slide deck
Every article your team has written about WatchDog stations, FieldScout meters and SpecConnect, turned into something a grower can ask a question of at 5am before the irrigation window, or on a Saturday when a frost alert did not arrive. It answers from your documentation, and when it cannot, it hands your team the case with the details already collected.
Live and answering right now, built on your 39 published articles
The 5am check, the weekend frost event, the station that went quiet on a Sunday. That is when the questions arrive.
The live copilot
Tap a question to copy it and open the chat, then push on it. Try to break it. It answers only from your knowledge base, so when the documentation does not cover something it will say so rather than invent an answer.
The chat opens from the button in the bottom corner of this page.
Your published help documentation: 39 articles across all 7 categories, including the weather station troubleshooting guide, Bluetooth and device key errors, SMS alert opt-in, custom reports, the FieldScout app guide, account and subscription questions, and the API articles.
It links the article it answered from, so a customer can read the source and your team can see exactly which page did the work.
What it works from
Every one of the 39 articles your team has published is in here, across all seven categories, with the source link attached to the answer. A sample of what it can already walk somebody through:
When it cannot answer
Order status, an RMA, warranty, pricing, anything the documentation does not cover, or a customer who simply wants a person. It stops guessing, collects what your team would have had to ask for anyway, and passes it over.
One question at a time, the way your documentation is written.
Illustrative example. Nobody on your team starts a hard case from zero, and nobody asks the customer to repeat themselves.
On your site
Your marketing team already put a chat window on specmeters.com. This replaces what sits behind it. Same corner, same habit for your customers, an answer instead of a routing form.
SpecConnect Support
Answers in secondsYour homepage exactly as it is today, with the copilot shown in place. Nothing about the site itself changes.
Prefer to talk?
A support rep that picks up at 5am, walks one step at a time, spells out the phone number instead of reading links, and collects the details before it hands a real case to your team. Same knowledge as the chat, same refusal to guess.
Tap the microphone to start. It asks permission first, nothing records until you do. Speak normally, and interrupt it if it runs long. On a phone, open it in its own tab instead, since iOS blocks microphones inside embedded frames.
Why this matters
Tech support runs Monday to Friday, 8:00 to 4:30 central, by phone. Growers and turf managers work dawns, evenings and weekends. That is not a staffing failure, it is arithmetic.
168
125.5
39
Phone support runs Monday to Friday, 8:00 to 4:30 central. A week has 168 hours.
| Channel | Hours covered per week | Share of the week |
|---|---|---|
| Phone support today | 42.5 | 25% |
| With the copilot | 168 | 100% |
The other 125.5 hours are when frost events, dawn irrigation checks and weekend problems actually happen.
When someone with years of troubleshooting in their head leaves, the answers leave with them. Everything the copilot knows lives in your knowledge base, in writing. Every article your team improves makes it permanently better, and the next hire arrives to a system that already knows the answers.
"How do I add a user" and "why is my report timing out" stop reaching a person. What does reach them arrives triaged: name, product, serial, the issue, and what has already been tried. Fewer interruptions, and a faster start on the cases that genuinely need a human.
Where this can go
"Is my station online right now?" and "when does my subscription expire?" answered from your own live data, through the customer API your documentation already describes.
The voice version of this, picking up when the office is closed, collecting the details and passing real cases to your team by morning.
One that puts live SpecConnect data and this copilot front and center. Glad to show you what that could look like.
Over to you
Every gap you find is a note about what to sharpen. If your team wants to see how it is wired, or how it would handle your own edge cases, we will walk through it in twenty minutes.