Your meeting ends with three follow-ups: update the brief, message the project lead, and create a ticket. Before you start any of them, you’re already due on another call. The calendar invite left out the homework. That’s the gap the ++Highlight beta++ is built to close.
++Highlight++ is everything in your working world, in one place. It connects your apps, meetings, and screen, creating a single command center for understanding your work and proactively moving it forward.
Here’s what that looks like in practice: a place to check the context, find answers, and review drafts for the apps where you’ll use them.
1. Bring Your Work Into One Command Center
Start with the tools you use each day: your calendar, documents, project tracker, and chat. Highlight can use those connections alongside captured meetings and screen context, so you don’t have to paste the same background into each request.
In the side panel, you’ll find upcoming meetings, reminders, prepared drafts, and Chat, so you can handle meeting prep and follow-ups in one place.
Screen Context & App Integrations
Connect tools such as Slack, Google Docs, Notion, Linear, Ashby, and GitHub. Those connections give Highlight access to the documents, messages, and project records you work with. Screen context adds what you’re looking at in the apps and windows you allow it to see.
Say you’re comparing a campaign dashboard with a launch brief. The chart on your screen can reveal a detail that isn’t obvious from the brief alone, like the campaign or date range under discussion. Highlight can use that detail alongside the document and captured conversation to prepare a more relevant update. You don’t have to describe every tab before it can help.
Highlight Chat: Answers Without the Digging
Nobody’s handing out prizes for remembering the exact filename. You should be able to ask “What’s holding up the launch?” without first hunting down the brief, copying a Slack thread, and recapping your last meeting.
Highlight Chat can draw on your connected apps, your captured meetings, and the screen content you’ve allowed it to see. Those sources can inform the same answer, so you don’t have to assemble a background packet before every question. For example:
- Find an open question: “What do I still need to confirm with design before the landing page goes live?”
- Catch up after time off: “What changed in the launch doc and the Slack channels I follow?” For meeting context, ask about calls you attended and Highlight captured.
- Prepare for a call: “What did we leave unresolved in my last sync with Priya?” Check the earlier discussion and open commitments before you join.
2. Turn Conversations Into Staged Actions
The ++follow-up after a meeting++ often means translating one conversation into several formats. Actions prepare those individual drafts for you.
From a captured meeting or the context in your connected tools, Highlight can prepare the next step for the appropriate destination. The draft appears in Ready for You, where you can check it before it’s sent or saved.
- After a campaign review: You agree to test a new headline before changing the rest of the page. Highlight drafts the brief update in Google Docs and a Slack message explaining the change to the designer.
- After an operations check-in: Your team agrees on next month’s onboarding plan. Highlight drafts the checklist in Notion and a Slack update with the dates and owners discussed on the call.
- After a customer research call: Highlight organizes the feedback into a Notion summary and drafts an internal update. You check that observations and customer quotes match what was actually said.
3. Keep Track of the Promises You Make
“I’ll send the revised mockups tomorrow” sounds small enough to remember. So do all the other things you promised before lunch. An informal promise can ++get buried in Slack++ long before it becomes a task.
Highlight can identify commitments in meetings it captures and surface follow-ups when it reviews connected sources, such as through your daily brief or a Skill you configure. Slack and email aren’t monitored continuously. You can also ask Chat to check for outstanding requests.
A reminder keeps the source conversation close, so “send the mockups” doesn’t become another task with no explanation. Open the source to check the recipient, request, and deadline. You can edit reminders, snooze or dismiss them, and add your own in the panel.
4. Set Up Recurring Workflows with Skills
If a useful follow-up becomes a regular process, you can turn it into a Skill. That saves you from ++maintaining a DIY automation++ for a sequence you already know.
Describe the process in Highlight Chat, work through the result, and ask it to “++turn this into a Skill++.” Specify the source material, destination tools, format, and any rules that should guide the output.
You can run a Skill from Chat, on a schedule, or through supported meeting and app events. For example:
- Weekly hiring update: Gather the candidate feedback available in Ashby and draft a Slack summary of the open decisions. Set it to run before your hiring sync.
- Campaign planning: Turn notes from your recurring planning call into a Notion brief and a Slack update, using the sections and level of detail your team expects.
- Engineering handoff: Collect the issue, relevant discussion, and triage instructions for a Claude Code review. Configure the workflow so you can check the ticket details and handoff before it proceeds.
5. Check the Work Before It Goes Out
A follow-up that’s nearly right still needs your judgment. Before approving it, check the recipient or channel, any dates, and the facts the draft relies on.
Open a prepared Action in Ready for You to review the draft. You can edit it, ask Highlight for a revision, or dismiss it. Emails, messages, and tool updates wait for your approval before they’re sent or saved.
You also ++choose which apps, websites, and windows Highlight can access++. Connecting a tool doesn’t give it permission to see information you can’t access yourself.
Try It on Your Next Follow-Up
Bring Highlight into your next meeting and connect the tools where the follow-up belongs. It can get the brief update started, draft the message a teammate is waiting for, and catch the promise you made just before everyone signed off.
That’s a head start on the work that usually waits until you’ve found a spare half hour. When the process repeats, a Skill can get those same steps underway again with the next conversation’s context.
++Try Highlight++ and see what happens when the context you’ve already created starts doing some of the work.
