What Connect by JBRH is
Connect by JBRH is a Digital Business Employee: one application that reads a business's email, answers its phone, handles WhatsApp, keeps a single record per person and follows through on what was promised. It is not a chatbot attached to an inbox and not a CRM you fill in by hand. What it may do without being asked is a per-channel setting you control.
One worker, not five features#
The useful comparison is a competent employee rather than a tool. An employee who answers the phone also remembers the email thread from last week, knows the customer had a problem in March, and chases the quote they promised on Friday. Connect is built the same way round: the channels feed one set of canonical records — threads, messages, contacts — and every channel reads from the same relationship.
That is why the product is a single application rather than an inbox assistant plus a phone bot plus a CRM. A reply drafted on email can cite what was said on a call; a call can raise a follow-up that drains on WhatsApp; a person's whole history across every channel is one view, called Customer 360.
The channels, honestly stated#
| Channel | Status | What that means today |
|---|---|---|
| Available | Gmail via Google OAuth, Microsoft Graph, or any IMAP/SMTP server. Several mailboxes per workspace, each with its own role and autonomy. | |
| Phone | Available | A carrier leg for the PSTN, plus an optional realtime speech-to-speech engine a workspace opts into. |
| Available | Inbound webhook, person resolution, conversation continuity and replies under the same autonomy rules as any channel. | |
| SMS | Foundation | Inbound handling, STOP and suppression work. Outbound depends on a provider that carries SMS — the live carrier does not — and in India on DLT registration. |
| Softphone | Available | A person's own line in the browser, over SIP. |
The Phone screen says plainly that the live carrier carries no SMS rather than presenting a message thread that cannot send. That pattern — telling you what is unavailable instead of failing quietly — is worth recognising early, because you will meet it again.
What it keeps for you#
- Memory at four tiers — workspace, channel, endpoint, contact — resolved narrowest first, readable and erasable at every tier.
- Knowledge: sources your business supplies, which answers are grounded in, and the facts extracted from them.
- Relationships: one person, one record, however many addresses and numbers they use.
- Follow-ups: dated commitments on a channel, with the reason attached, including a
taskchannel that is work for a person and is never sent by anything. - An audit trail of what was decided, by what, under which rule, and what happened — including refusals, because a refusal is a decision.
What it is not#
- Not an autopilot you cannot stop
- The runtime switch halts Connect immediately without changing any setting, and every channel has an
offmode. - Not a replacement for judgement
- Pricing, contentious replies and anything a rule holds go to a person. The Assistant's own rights are deliberately narrower than yours — it cannot set pricing or clear a do-not-contact entry.
- Not a lead-list vendor
- Prospecting researches organisations from evidence. It never guesses an email address; an address it cannot evidence is left blank rather than invented.
- Not a second CRM over your data
- The
#/datagrid edits records through the services that own them, so a change made in a cell obeys the same rules as a change made on the record's own screen.
Questions#
Is this a chatbot?
No, and the distinction is practical rather than pedantic. A chatbot answers the message in front of it. Connect keeps state between messages, across channels and across months: it knows what it promised, it chases it, and it records who approved what. The in-app Connect Assistant is the part that feels like chat, and it works over the same records rather than a transcript.
Does Connect train a model on my business data?
No. Your knowledge, memory and mail are used to ground answers for your workspace, not to train a model. Workspace isolation is enforced three separate times — an allowlist in the middleware, the SQLAlchemy workspace kernel, and row-level security in PostgreSQL.
Who operates it?
JBRH Digital Solutions builds and runs Connect. The operator's own workspace uses the same code as every customer workspace, which is the mechanism that keeps the two honest: a defect in the shared implementation shows up in both.