ChatGPT and Codex training for insurance brokers and media companies in Cologne

Many texts a day, each a little different

An insurance broker answers the same questions many times a week: which document is missing, what a policy covers, when a premium changes. A media team writes teasers and newsletter texts from each article. Most of these texts follow a pattern, and the details change each time.

ChatGPT can write the pattern. It cannot know the details, and a wrong policy number or date in a client letter costs trust. The training shows your teams how to build templates that ask for the details and how to check them before a text goes out.

The ChatGPT track: templates for recurring texts

• A custom GPT or a project for each text type, with your tone and your standard phrases.
• Placeholders for client and policy data, so the template never makes them up.
• A short check per text type: the facts a person confirms before sending.
• For media teams: teasers and newsletter texts from an article, with names and quotes checked against the source.
• Which data may go into ChatGPT, as your data protection officer decides.

The Codex track: your own code base

• An AGENTS.md with the commands that build and test your code.
• Database migrations: Codex writes them, a person approves them.
• Your existing test suite runs after each change Codex makes. Where there is none, Codex writes the first tests.
• Review of each agent change in your Git host before merge.
• Checks that a script enforces before a tool call, described on AI agents under the same rules as humans.

A template brief for one text type

Before a text becomes a ChatGPT template, your team fills in one brief for it. The example is a broker’s letter that asks a client for a missing document.

1. Name: request for a missing document.
2. Used when: a claim or an application lacks a document.
3. Input: client name, policy number, the missing document, the deadline.
4. Output: a letter of at most 150 words in German, with the formal “Sie”.
5. Tone: friendly and short, without legal phrasing.
6. Never: invent a deadline, a policy number or a statement about coverage.
7. Check before sending: name, policy number, document and deadline against the client file.
8. Owner: the person who updates the template when the process changes.

Who I am

I am Michael Wutzke, an IT architect in Frankfurt. At Policen Direkt, a company in the German secondary market for life insurance, I was project manager and web developer for the web portals of the group. Today I build software with Codex and Claude for a client and teach at Claude Hacker House. I am also interested in open-source AI models that a company runs on its own servers. Details: Career stages.