One mailbox you are willing to connect
A real one with real traffic. A quiet test mailbox produces a quiet, uninformative pilot.
START A CONNECT PILOT
Four weeks on your real work. The first one sends nothing at all.
A pilot is not a demonstration. We connect one of your mailboxes, load what is true about your business, set the boundary you are comfortable with, and let Connect work your actual queue — in draft only, until you have read enough of it to decide.
- No payment details, and no obligation at the end
- Draft-only until you explicitly enable sending
- Your own baseline numbers decide whether it worked
The four weeks, in order
- Scope callWhat work, which channels, which decisions stay with you
- Connect one mailboxThrough your provider's own authorisation
- Load what is trueProducts, policies, terms, the answers you already send
- Set the boundaryAutonomy mode, limits, and what always escalates
- Week 1 — draft onlyEvery reply prepared, none sent. You read them.
- Weeks 2–4 — release in stepsEnable sending where the drafts were already right
- Review against baselineResponse time, follow-up coverage, accounts touched
- Decide either wayContinue under a quotation, or stop with your data intact
Nothing here requires you to change how your team works. Connect joins the mailbox; it does not take it over.
WHAT TO BRING
Three things, and one of them matters most.
A pilot is limited by what it is given, so this is the honest list.
A short description of what you sell
The range, the way it is priced, the terms you offer. This becomes the knowledge Connect is allowed to answer from.
The one thing it must never say without asking
This single answer shapes the whole configuration. It is usually about price, about a delivery date, or about admitting fault.
If the third one takes you a while to answer, that is normal — and it is the most valuable half hour of the setup.
THE FOUR WEEKS
What actually happens, week by week.
Narrow on purpose. A pilot that starts with everything switched on is a pilot nobody can evaluate.
Setup
Mailbox connected, business identity set, knowledge loaded, autonomy and approval limits agreed. Typically two short working sessions rather than a project.
Draft only
Connect reads your real queue and prepares every reply. Nothing is sent. You read the drafts, correct what is wrong, and see precisely how it would have handled your week.
First release
Sending enabled for the categories the drafts were already right about — usually straightforward informational replies. Pricing and commitments stay behind approval.
Widen the boundary
More categories, and follow-up scheduling running on its own. If voice or WhatsApp are in scope, this is normally when they join.
Run it properly
A full week under the settings you have converged on, with the numbers being recorded against the baseline you started from.
Review and decide
Response times, follow-up coverage and accounts touched, compared with where you began — and a quotation, or a stop, on the strength of that.
You can stop at any point in this sequence. Disconnecting a mailbox ends Connect's access to it immediately, and your records remain yours.
HOW TO JUDGE IT
Decide on numbers you took before we arrived.
Take these four measurements in the week before the pilot starts. They are the whole argument at the end of it.
First response time
How long a customer waits for a substantive answer, not an acknowledgement — measured by channel.
How you would measure it: Median hours from message received to first real reply, before and during.
Follow-up coverage
The share of open quotes and conversations that actually got chased within a week.
How you would measure it: Open threads with a follow-up inside seven days, as a percentage.
Accounts actually touched
How much of your customer list had a real conversation this month, rather than sitting untouched.
How you would measure it: Distinct accounts with an outbound conversation in the period.
Escalation quality
Whether the things Connect stopped for were the right things — too many escalations is friction, too few is risk.
How you would measure it: Count of Needs You items, and how many you would have wanted handled automatically.
If these do not move, that is a result too, and a four-week one. We would rather you learn it here than a year into a contract.
WHAT A PILOT IS AND IS NOT
No small print worth burying.
A pilot that quietly becomes a contract is not a pilot.
What holds during a pilot
- No payment details are needed to begin, and starting one purchases nothing.
- Mailboxes are connected through your provider's own authorisation and can be revoked by you at any time.
- Draft-only is the starting posture; sending is enabled by an explicit decision of yours.
- Records created during the pilot are yours, and the Trust Centre documents retention and data rights.
- Any carrier or provider cost involved in running voice or WhatsApp traffic is named before it is incurred.
What a pilot will not do
- It will not prove a revenue number. Four weeks is shorter than most sales cycles, and we will not pretend otherwise.
- It will not include a bespoke ERP or CRM integration; that is separate scoped work, not pilot scope.
- It will not run on a mailbox with no real traffic — there is nothing to learn from an empty queue.
- It will not be extended indefinitely to avoid a decision. Four weeks is enough to know.
QUESTIONS
Before you send the request.
How do I start one?
Use the button on this page. It opens an email with the five things we need to know — business, what you sell, channels, rough volume, and the one thing Connect must never say without asking. A person replies; there is no queue system behind it.
Who is doing the setup work?
We do it with you, in working sessions rather than as a hand-off. The knowledge loading is the part where your involvement genuinely cannot be substituted.
What if the drafts are bad in week one?
Then the first week has done its job. Bad drafts are almost always thin knowledge, and that is fixable inside the pilot. If they are still wrong after correcting the knowledge, that is a real finding and we will say so.
Can we pilot phone or WhatsApp rather than email?
Email is the recommended starting channel because the feedback loop is fastest and nothing is spoken aloud to a customer while you are still calibrating. Voice and WhatsApp normally join in week three, and can be in scope from the start if that is where your work actually is.
What happens at the end?
A review against your baseline, and then a quotation if you want to continue. If you do not, the account is closed, your records remain yours, and there is nothing to cancel.
START A CONNECT PILOT
Send five lines. Get a working session.
The request below opens an email with the five things we need. Tell us the one thing Connect must never say without asking you — that answer shapes everything else.
- No payment details, no obligation, no contract at this stage
- Draft-only for the first week, by default
- Support@ConnectByJBRH.com reaches the same people