What happens after a call
When a client-facing call is recorded in your call tools (Gong or Fireflies), Omega picks it up within a couple of hours, matches it to the right client, and puts it to work in three ways — no setup or button press required.
Matching is deliberately careful: internal meetings are filtered out, and a call that can't be confidently matched to one client is skipped rather than filed under the wrong one.
If a client's call is missing: a common cause is the call's CRM account in Gong. When Gong links a call to an account that isn't an Omega client, Omega leaves the call out rather than guess, even if the client's own people were on it. Open Client settings → Notifications: the Call matching card lists those calls with the Gong account they carry. If the account is wrong, ask your Gong admin to fix it. If it's another name for this client (a legal or parent company name, say), add it as an alias there. An alias sends every future call under that account to this client, so only add one that really is this client. After either fix, the next sweep picks up calls from about the last two days.
1. A summary in Slack
Each matched call posts a Call intelligence summary to the client's Slack channel — the one saved in the client's notification settings. If the client has no channel saved, the summary posts to the team's default channel instead, so it's never lost.
The summary covers the call title, date, duration, and who was on it, then the substance: what happened on the call and what's coming next, with a link straight into the client's cockpit in Omega.
2. Action items become signals
Commitments made on calls have a way of evaporating. Omega turns each call's action items into pending signals on the client's Workflow board, gathered in a collapsed "action items from calls" section so they don't crowd the scan findings.
Click one to open the normal signal view — from there you can queue it for an agent, discuss it with the team, or dismiss it, exactly like any other signal.
3. Call notes join the client's memory
Every processed call also saves a call-notes memory to the client's shared memory: a concise brief of the call plus its next steps, stamped with the call's name and date. That memory travels everywhere the client's context goes — chats, scans, agent runs, and reports all work with an awareness of what was actually said on recent calls.
You can see and manage these like any other memory:
Open Settings from your profile menu and stay on Client settings.
Pick the client with the client picker.
In the Memories card, call-derived entries appear alongside everything else Iris has learned — edit anything that's wrong, or remove entries that shouldn't inform future work (removal is reversible).
Tip: After a call where plans changed — a new promo, a shifted goal, a paused channel — glance at the client's Memories. The call notes will usually have captured it, and it's worth confirming the record matches what was decided.
Note: Call summaries only post for clients whose performance data is connected in Omega — the summary links into the client's cockpit, so it waits until there's a cockpit worth landing on. If a client's calls aren't showing up, check their data sources in nova first.