Connect by JBRH Open Connect

Keyboard and speed

The fastest way around Connect is the address bar. Every screen has a hash route — thirty-four of them — so #/needs-you or #/follow-ups typed or bookmarked goes straight there without a single click through a menu. The second fastest is asking the Connect Assistant for the record you want instead of navigating to the screen that holds it.

Status
Available What this means
Audience
both
In the app
#/home, #/needs-you, #/inbox, #/follow-ups
Last verified
Product version
6.3.2

Routes are the shortcut#

A hash route is part of the address, so it can be typed, bookmarked, opened in a second browser tab, and put on a phone's home screen. Three or four bookmarks covering the screens you use daily removes most of the navigation from a working day.

RouteScreenWhen
#/needs-youNeeds YouThe first thing most mornings
#/inboxConversationsReading a thread across every channel
#/follow-upsFollow-upsWhat is due, including task items
#/callsPhoneCall records, transcripts, line health
#/autonomyWhat Connect May DoChanging a mode or a scope
#/autonomy-auditDecision LogAnswering 'why did that happen'
#/dataDataThe grid over the thirteen record sheets
#/activityActivityWhat went out without you

Ask rather than navigate#

The Connect Assistant reaches the same records the screens do, through a set of tools rather than a search box — sixty-six of them, of which about half only read. Asking for a person's history, an outstanding draft, a file's contents or what is due today usually beats finding the screen that shows it, particularly when the answer spans two screens.

  • It keeps browser-style tabs, each with its own conversation, record, draft, files and scroll position — so a half-finished question survives an interruption.
  • The status line tells you what it is doing and how many steps it has taken, with a compact stop control rather than a row of stage indicators.
  • What it is told about the screen you are on is checked against the database before it is trusted, so an answer is grounded in records rather than in what a panel happened to be showing.
  • Its rights are narrower than yours: it cannot set pricing and cannot clear a do-not-contact entry, whatever you ask it.

Speed that is not the keyboard#

Most of the waiting people notice in business software is the software reading more than it needs to. Connect's screens are built to keep that cost flat as a workspace grows rather than climbing with it — the Home screen was reduced from 133 database statements to 15 and stays there, and the triage strip and workspace console went from 83 and 89 statements to 11 and 17, flat with page size. What that means for you is that a big workspace opens as fast as a small one.

The other kind of speed is not repeating your own work. Saved views on the data grid keep a filter, a sort and a column arrangement you would otherwise rebuild each time; standing instructions stop you re-editing the same sentence; a memory at the contact tier stops you explaining the same customer twice.

What this page will not pretend#

There is no published table of global keyboard chords in this manual, and inventing one would waste your time more thoroughly than having none. Where a screen offers its own keys, the screen is the place they are shown — a grid cell that responds to the usual spreadsheet keys, a text field that submits the way text fields do. Learn the routes, which are stable and documented, rather than guessing at chords.

One control is worth locating with your eyes before you need it in a hurry: the runtime switch in the application shell, which stops Connect acting immediately and changes no settings. Knowing where it is beats knowing any shortcut.

Questions#

Can I bookmark a specific conversation or record?

Routes address screens rather than individual records, so a bookmark reliably returns you to a screen. For a specific person or deal, asking the Assistant by name is quicker than hunting for a link you saved a fortnight ago.

Does typing a route skip any permission check?

No. Navigation is a request like any other, checked by the same three layers of isolation — the allowlist in the middleware, the workspace kernel, and row-level security in the database. A route you may not reach answers with a refusal rather than showing you anything.

Is there a command palette?

The Assistant is the closest thing, and it is more capable than a palette because it acts on records rather than only jumping to screens. Whether a particular build also offers a keyed palette is a question for the screen in front of you rather than for this page.