Last verified: October 7, 2026
What You Can Now Do
Context Memo customers can now see their custom navigation names and icons reflected in the browser title and on the Calls page. If you renamed a nav item to match your team's internal vocabulary, that label now travels with you: into the browser tab, into pinned tabs, into browser history, and into every heading and reference on the Calls page. The practical change is small and daily. You stop translating between what your workspace calls something and what the product calls it, which matters most when you have eight tabs open across scans, memos, and calls and you're identifying the right one by tab title alone.
Where It Is in Context Memo
Custom navigation names and icons are configured where you already set them, in your navigation settings. What's new is where those values render. Open any page and check the browser tab: the title now reads with your custom label instead of a generic one. Open the Calls page and the nav label, icon, and in-page references all use your configured name. No new settings screen was added. Existing configurations are picked up automatically.
How to Use It
- Open your navigation settings and set the name and icon you want for each nav item. Use the term your team actually says in Slack, not the default. Save.
- Reload the app and look at the browser tab. The title reflects your custom name. If you work with pinned tabs, the favicon and title now match your configuration, so the tab is identifiable without clicking it.
- Go to the Calls page. Confirm the nav label and icon match what you set, and that in-page headings and references use the same name. This is the surface where mismatches were most visible before.
- Check your browser history or bookmarks for a Context Memo page you visit often. Entries created from this point forward carry your custom title, which makes keyboard-driven navigation (address bar search) land on the right page.
- If you share workspace access with colleagues or agency partners, point them to the renamed items once. Because the label is consistent across nav, tab title, and Calls page, you won't need to explain which default name maps to which internal term.
Why We Built It
Custom navigation labels were not appearing consistently across all parts of the product, which meant customers configured a name once and then saw generic or mismatched names depending on where they were. The cost was small per instance and constant in aggregate: teams second-guessing whether they were on the right page, onboarding conversations spent explaining that two different names refer to the same thing, and browser tabs that all looked alike during a workflow that regularly spans several at once. Naming is part of how a team trusts a tool. When a product disagrees with itself about what something is called, that trust erodes quietly.
What It Does Not Do Yet
This release covers the browser title and the Calls page. Custom names and icons now persist across those surfaces alongside your navigation; if you find a view where a default label still appears, that's a gap rather than intended behavior, and it's worth reporting so we can extend coverage. Browser titles are also subject to how each browser truncates long strings, so a very long custom name may be clipped in a narrow or pinned tab. Shorter labels read better in that context.