# Connect

Connect — in full, **Connect by JBRH** — is one application that reads a business's incoming messages across email, WhatsApp, SMS and phone, decides what to do about each one, drafts the reply and sends it under rules the business sets. It is built and operated by JBRH Digital Solutions, and the current product version is 6.3.2.

- **Status:** Available
- **Audience:** both
- **In the app:** #/home
- **Last verified:** 2026-09-10
- **Canonical:** https://connectbyjbrh.com/docs/glossary/connect/

## The scope of the name

Connect names the whole application, not a module of one. The mail fetch, the reasoning loop, the phone engine, the prospect research, the relationship records, the approval queue and the screens a person works in are one codebase and one deployment. There is no separate email product and no separate voice product to buy; a workspace turns channels on and off, and what it turns on is the same Connect.

The public site is `connectbyjbrh.com` and the application lives at `/app`. Signing in is Google OAuth and nothing else — there is no password login to look for, which is the single most common cause of a first-time reader concluding they have the wrong URL.

| Name | Refers to |
|---|---|
| Connect by JBRH | The product, in full, on a first mention |
| Connect | The same product, in running prose and in the interface |
| JBRH Digital Solutions | The company that builds and operates it |
| Connect Assistant | The in-app assistant inside Connect — a part, not a synonym |

## One product, two audiences

There is one feature set. Every capability reachable by the platform operator is reachable by a customer over the same implementation; there is no customer-only feature and, with two deliberate exceptions about running the platform rather than using it, no operator-only feature. What differs is commercial: a customer's use is bounded by their plan's allowance, and the [Owner](/docs/glossary/owner/) workspace has no plan.

This matters to a reader because it makes the manual honest about screenshots and route names. When a page says a screen exists, it exists for both. When something is genuinely restricted, the page says so and says why. [Tenant](/docs/glossary/tenant/) covers the customer side of that split, and [One implementation, two audiences](/research/two-audiences-one-implementation/) covers the engineering that keeps it true.

## What Connect is confused with

Three confusions are worth spending words on, because each one leads a reader to expect the wrong thing from the product.

**A chatbot on a website** — A chatbot waits on one page for a visitor to open it. Connect works a business's existing mailboxes and numbers: it reads what arrives at the address customers already write to, and it acts whether or not anyone is watching a screen. The Connect Assistant is chat-shaped, but it is the way *you* talk to Connect, not the way a customer does.
**An autoresponder or a rules engine** — An autoresponder matches a pattern and emits a canned message. Connect grounds a reply in the workspace's own [Knowledge](/docs/glossary/knowledge/) and [Memory](/docs/glossary/memory/), records what it decided and under which rule, and holds the reply for a person when [Autonomy](/docs/glossary/autonomy/) says a person decides. Rules exist in Connect, but they constrain a judgement rather than replace one.
**An inbox plug-in** — Connect does not sit inside a mail client. It holds its own canonical records — threads, messages, contacts, calls — and writes back to the provider where that makes sense. Its view of a customer therefore spans channels a mail client cannot see, which is what [Customer 360](/docs/glossary/customer-360/) names.
**The retired name** — An earlier internal name for the product is retired. It survives in a few code identifiers and environment variables that were never renamed, and seeing one of those is not evidence of a second product.

## Where the boundaries actually are

Connect does not do everything a page could imply. Call recording exists as a model and a capability flag but is not enabled on the live carrier. Transferring a live call to a human is written and gated on provider capability rather than finished. Outbound SMS depends on a provider that carries SMS, which the live carrier does not. Prospect research never guesses an email address. Each of those is stated on the page that owns it rather than softened into a general claim here.

## Questions

### Is Connect one product or a suite?

One. Email, phone, WhatsApp, prospecting, relationships and follow-ups are features of a single application sharing one set of records, which is why a phone call and an email to the same person land on the same relationship without an integration step.

### Who operates Connect?

JBRH Digital Solutions builds and runs it. That company also uses Connect for its own work, in a workspace called the Owner — the same code, with no plan attached to it.

### Does Connect train a model on a workspace's data?

No. Model calls carry the material needed to answer the piece of work in front of them; a workspace's mail is not training data, and no page in this manual claims otherwise.

## Related

- [Glossary](https://connectbyjbrh.com/docs/glossary/)
- [Digital employee](https://connectbyjbrh.com/docs/glossary/digital-employee/)
- [Connect by JBRH](https://connectbyjbrh.com/docs/product/)
- [Getting started with Connect](https://connectbyjbrh.com/docs/getting-started/)
- [One implementation, two audiences](https://connectbyjbrh.com/research/two-audiences-one-implementation/)

## What this page is based on

- docs-source/sources/GENERAL.md §1 — what Connect is
- `docs-source/facts.py` — PRODUCT_VERSION, BRAND, OPERATOR, FORBIDDEN_CLAIMS
- docs-source/sources/GENERAL.md §10 — sign-in and security