Keyboard shortcuts in the Ochre inbox
Every shortcut you need to live in the inbox without your mouse — navigation, replies, assignment, and global jumps.
The Ochre inbox is built for the keyboard. Most agents end up using a mouse twice a day: once to log in, once to take a screenshot. Everything else is faster from the home row.
The shortcuts that matter
Press ? from anywhere in the app to pop the cheat sheet. The list below is the same one we live by.
| Key | Action | | --- | --- | | J / K | Next / previous conversation in the list | | R | Focus the reply composer | | N | Focus the internal note composer | | F | Focus the forward composer | | E | Close the conversation | | T | Take over (assign to yourself) | | A | Open the assign-to picker | | ⌘↵ | Send the current draft | | / | Open the snippet picker inside the composer | | ? | Show the full shortcut sheet |
Jumping between views with G
The G key is a leader. Tap it, then a second key, to teleport across the app. We borrowed the pattern from Linear and Superhuman because once your hands learn it, you stop browsing — you arrive.
G I— InboxG K— Knowledge baseG A— AI agent dashboardG S— SettingsG R— ReportsG C— Customers
A few habits that pay off
J R type ⌘↵ is the four-keystroke reply. If you find yourself reaching for the mouse to click Send, you're paying a tax on every conversation. The first week feels deliberate; by week two, you'll do 60 conversations before realising you haven't moved your wrist.
E after sending closes the thread. If the customer's reply will need another touch, leave it open — E is for "I'm done here," not "send and pray."
T is the most underrated key in the inbox. It assigns the conversation to you and pulls it out of the unassigned pile in a single tap. Use it the moment you start typing a reply, not after.
What's not a shortcut (yet)
Tag editing, snooze duration, and bulk operations don't have single-key shortcuts inside a conversation — they're modal pickers reached through the toolbar or ⌘K. We'd rather a missing shortcut than a wrong one that destroys data, so we keep the keymap tight on purpose.
Was this article helpful?