How to Set Up an Automated Daily Sales Opportunity Report in Codex

Consistent, for an agent, looks like this: every day at a time you set, Codex reviews every meeting you had, identifies every client where a cross-sell or upsell exists that you did not address, creates an offer around that opportunity, drafts a personalized email for that specific person based on that specific conversation, and sends you the full report. You wake up to it. You did nothing to trigger it.

That automation is available to you today, with a single voice note or typed prompt, as long as your meeting notes are connected.

This post walks you through exactly how to build it, what mistakes will stop it from working, and where the progression goes once you trust it enough to remove yourself from the loop entirely.

For the complete framework behind all of this, read the full Codex setup guide.

Why Business Owners Keep Missing the Same Revenue

The problem starts here: after a one-hour call, when you are tired and moving on to the next thing, the subtle signal in the middle of the conversation,the client who mentioned they are struggling with something you solve,does not make it to your action list. It stays in the transcript, which you never go back and read.

You know cross-sells exist. Every business owner does. The mechanism that converts that knowledge into a revenue action consistently,that is what is missing.

Agents do not get tired after a long call. Codex does not skip the audit because the afternoon got busy. It reads every transcript, flags every signal, and creates the offer,every time, without exception.

Watch me explain this live to see how I walked through this automation during the original training session.

What You Need Before This Works

The automation cannot run if Codex cannot see your conversations. Your meeting notes provider has to be connected via Plugins before anything else.

In Codex, navigate to Plugins in the top left. Find your meeting notes tool,Fireflies, Google Meet, whatever you use,and connect it. After connecting, verify access by asking Codex directly: "Can you see my meeting notes? What is in them?" A vague or empty answer means the connection is incomplete and the automation will produce nothing. For a walkthrough of how Codex's Plugins work and what to check before trusting them, read what a plugin actually is and why connecting one is not enough on its own.

If your meeting note tool is not listed in Plugins, ask Codex: "My meeting note taker is [name]. Please pop up whatever browser screen is needed to get the API key so you can connect to it." It will walk you through the process.

Fix every row before setting up the automation. An automation built on incomplete access will run on schedule and produce nothing useful. Learn how to configure Codex permissions correctly before moving forward.

First, Make Sure Your Notetaker Is Agent-Friendly

One prerequisite deserves its own note: not every meeting notetaker is built for an agent. Before you rely on this automation, make sure yours exposes the full transcript and bulk export, not just a plugin, and test it before you trust it. I compared the main options, Otter, Fireflies, Zoom, Google Meet, and Read AI, and gave a test prompt in which AI notetaker actually works with your agent.

The Automation Setup: Word for Word

Once meeting notes are connected, setting up the daily report takes a single prompt. You can type it or use voice. Here is what I described on the live,adapt the time and specifics to your business:

"At the end of each day at 8 PM, review the full transcript of every meeting I had that day, not just the summary. If you identify any upsell or cross-sell opportunities I may have missed, identify those opportunities, create an offer around them based on my business and current goals, draft an email approach for that specific client based on that specific call, and email me a full report."

Codex will set up the automation and confirm it. From that point, it runs daily without you triggering it.

A few things that make this prompt work:

• "At the end of each day at 8 PM" gives it a defined trigger time rather than leaving it open-ended
• "Based on my business and current goals" is why the agentic home base matters,without it, Codex has no context for what an appropriate offer looks like
• "That specific client based on that specific call" produces a personalized draft rather than a generic template
• "The full transcript, not just the summary" forces it to read the whole conversation. Notetakers and agents both tend to fall back on the auto-summary, and the small, easy-to-miss signals are exactly what the summary drops

Add specifics as you want them. You can tell it which email to send the report to, how you want the opportunity breakdown structured, or whether you want a separate section for current clients versus prospects.

The Three-Stage Progression You Cannot Skip

The automation above is Stage 2. You receive the report. You review the opportunities and the draft emails. You decide which ones to act on. You are in the loop, but Codex is doing the work.

Stage 3 is where Codex identifies the opportunity, creates the offer, contacts the client directly, and includes a Stripe payment link,no report, no review, no approval from you.

Most business owners try to jump from zero to Stage 3 without running Stage 2 long enough to understand where the agent gets it right and where it needs refinement. That is how agents make expensive mistakes.

Trust is built through a sequence. Here is what each stage requires:

Stage 1,See the output: Run the audit manually first. Paste the Meeting Notes for Sales Opportunities skill from the Skills Dashboard into Codex and let it analyze the last 14 to 21 days of your conversations. Plan for four to five minutes of runtime,it is pulling calendar events, meeting notes, and transcripts across the full window. Read every line. Observe without acting. You are learning what the agent sees before you rely on its judgment.

Stage 2,Approve actions: Set up the daily automation as described above. Every evening, you get the report. Review the opportunities. Act on the ones that look right. Run Stage 2 for a minimum of two to four weeks before considering the next step.

Stage 3,Autonomous execution: After two to four weeks of reviewing reports, you will know the patterns Codex consistently gets right. For those specific contexts,clients it reliably flags, offer types it frames accurately, tone it matches correctly,update the automation to remove the report step and authorize direct outreach.

Learn more about connecting your meeting notes via Fireflies and Google Meet and running the initial audit before building the daily automation.

What the Advanced Version Actually Looks Like

After describing Stage 2 during the live, I walked through what Stage 3 looks like in practice. You update the automation with language like this:

"At the end of each day, review my meeting notes. If you identify any cross-sell or upsell opportunity I may have missed, create an offer for that client, contact them directly with the offer, and include the payment link."

At that point, Codex runs a complete revenue cycle on its own,identification, offer creation, outreach, and payment request,without you in the loop.

The prerequisites for that version go beyond trust. Codex needs to be connected to your email to send the outreach. It needs Stripe connected to include the payment link. It needs your home base to know what offers exist and how they are priced. Every gap in access is a step where the automation stalls.

The automation itself is a single prompt. Making it run completely depends on everything built before it. Read the full setup guide for building your agentic home base if that foundation is not yet in place.

Beyond the Sales Report

The same foundation, your meetings made readable, powers more than a sales audit. The same agent can review every client call and write you an internal progress report plus a client-facing recap, so you track progress and keep clients informed without doing it by hand. I broke that build down step by step, including the per-client milestone baseline, consent, guardrails, and where it all lives, in how to automate client progress reports and client comms with Codex.

Common Mistakes That Break This Automation

Running it before meeting notes are connected. The automation will trigger on schedule and have nothing to analyze. You will get a report saying Codex found no meetings,not because there were none, but because it cannot see them.

Expecting an instant output. During the live, the audit ran for four minutes and thirty-five seconds across a real meeting history. Checking on it thirty seconds after triggering it and concluding it is broken is a common mistake. Let it run.

Skipping the home base. With no context on your offers, Codex will produce something generic or ask clarifying questions in the report,which defeats the purpose of an automation running while you are not watching. Build your home base first.

Setting approval policy to "untrusted." With that setting active, every micro-action requires your sign-off. The automation will stop at step one and wait for permission. You will return in the morning and find it has not started. Change approval policy to "on request" before running anything on a schedule. Full permissions configuration is in step 05.

Key Takeaways

• The daily sales opportunity report is a single prompt that runs on schedule,meeting notes connected, home base built, and permissions set correctly are the only prerequisites
• The progression from "receive a report" to "agent contacts the client autonomously" has three non-skippable stages; running Stage 2 for two to four weeks is what earns Stage 3
• Every missed cross-sell and upsell from the last 14 to 21 days of calls is sitting in transcripts right now,Codex surfaces them in under five minutes once it has access
• When the automation breaks, the problem is almost always a connection gap, not a prompt quality problem

Every missed cross-sell from the last three weeks of calls is sitting in a transcript right now. You put it there. The only thing missing is the agent that reads it.

Back to the full Codex setup guide