Email Support Agent with Codex
Support mail does not arrive politely spaced out, it arrives in a clump the morning after a release. Codex is quick on well scoped work, and one ticket is about as well scoped as work gets: read the thread, search Notion, write one draft, stop. If your team already lives in OpenAI tooling, this is the harness nobody has to learn first.
Watch it work before it's live
Run a staged conversation — no account needed. The agent handles it for real while a simulated world answers its tool calls; nothing touches real accounts, and nothing is actually sent.
Adding two more seats before our audit on the 30th
Good morning, we are a six person accounting studio in Milan and we are on your team plan. Two colleagues join us on Monday and I need them in the account before a client audit on 30 August. Can I add the seats myself from the billing page, and does the price change straight away or at the next renewal? One more thing, will they be able to see the archived files from last year?
Set up in minutes
Using this template drops you into a guided setup. It asks exactly this, nothing else:
Connect Gmail
One sign-in. The agent acts through your account, scoped to what this template uses.
Connect Notion
One sign-in. The agent acts through your account, scoped to what this template uses.
Business name
The name your customers know you by, used in the greeting and sign-off of every drafted reply.
Support playbook
Your support policies in your own words - refund and cancellation rules, what you can and cannot promise, and the tone and sign-off you want on every reply. The agent may only answer from this and your knowledge base.
Kb notes
What lives in your Notion knowledge base and how to use it - which pages hold product docs, policies, and troubleshooting, plus anything in there that is out of date or off limits. The agent searches Notion before it writes a word.
Runs on Codex
Preselected for this page — connect your Codex account during setup, or switch to NoClick's built-in models with one click.
Watch it handle a test run
A staged conversation against a simulated world — then it’s live.
Why Codex for this agent
Fast on a bounded task
Every run has the same narrow shape and a hard stop at the draft. Concrete jobs like that are where Codex is at its best, which keeps the queue moving when twenty emails land at once.
Comfortable with the plumbing
Gmail threads and Notion search results come back as messy nested data before any of it becomes a sentence. Handling that layer cleanly is one of this harness's steadier habits.
Before you fork
It is a coding CLI, will the drafts sound like an engineer wrote them?
Tone comes from your playbook rather than the harness, and the agent is told to write like an email: greeting, one or two short paragraphs, your sign-off. Run the three staged tickets before pointing it at the real inbox, since that is where you hear whether the voice is yours. If it reads stiff, the fix is the playbook text, not a different agent.
Run it with a different agent
Put Email Support Agent to work on Codex
Free to start. Guided setup, a test run against staged conversations, and it's live.