Brokerage Switching Season: What a Chat Handles

Between early September and the turn of the year, the rhythm inside an insurance brokerage shifts noticeably. The German Insurance Association publishes its regional classes, October brings the premium invoices, and anyone who wants to switch their motor policy at the turn of the year has to observe the agreed notice period. In the 2027 regional statistics, which the association published in September 2026, the motor third-party liability class improves in 63 (GDV) and rises in 46 (GDV) of Germany's 413 (GDV) vehicle registration districts. For a brokerage this means considerably more enquiries within a few weeks, with unchanged staffing. This article shows which part of that an AI assistant can take on cleanly - and where the line runs towards advice-bound intermediation, which stays with a human.

Enlarge graphic

Labels in the illustration

• Enquiry volume per calendar week, schematic
• Usual cut-off 30 November
• September
• October
• November
• December
• January
• 1
• 2
• 3
• 1
• Initial disclosure
• Role, register, remuneration
• before the first data field
• 2
• Enquiry complete
• Vehicle, no-claims, expiry
• contact with consent
• 3
• Appointment with the broker
• Advice and documentation
• stay with the human

Switching season at the brokerage

Why autumn has a rhythm of its own in a brokerage

The regional classes reflect the claims record of the registration districts and are calculated once a year (GDV). In the 2027 regional statistics, motor third-party liability classes move upwards for 46 (GDV) districts with 4.8 million (GDV) drivers and downwards for 63 (GDV) districts with 5.2 million (GDV) people. In the remaining 304 (GDV) districts with more than 32 million (GDV) drivers, the class stays unchanged. Third-party liability has 12 (GDV) classes, partial cover 16 (GDV) and comprehensive cover 9 (GDV). Anyone who opens an invoice in autumn and sees a different classification than the year before has a concrete reason to question their own contract - and gets in touch.

For the correct reading, a second sentence from the same source matters more than any single figure: the regional statistics are non-binding for insurance companies and may be applied to new contracts as well as to existing contracts at the main renewal date, as a rule 1 January (GDV). A changed class is therefore not an automatic premium jump but one factor among several. Precisely this distinction is the first point at which explanatory work piles up in the office. The enquiry reads almost verbatim as "why is it getting more expensive?", and the answer is rarely a single number. It hangs on the tariff, the vehicle, the no-claims class and the insurer's annual adjustment.

For day-to-day operations this has two consequences. First, the backlog of enquiries does not run towards a single day but towards several cut-off dates that differ from contract to contract. Second, the date is unsuitable as a blanket answer. Anyone who confirms a deadline in chat or on the phone without knowing the main renewal date of the specific contract produces a statement that may not hold up. An automated assistant can handle this distinction cleanly because it phrases it as a condition rather than a commitment: it asks for the expiry date on the policy, records the answer and hands it over together with the enquiry. What could have been a shaky answer becomes a data point that gets checked.

What actually lands in the inbox during these weeks

The enquiries of the switching season are remarkably uniform. They differ in tone, hardly in substance. Once the categories are cut cleanly, it quickly becomes visible which part needs expertise and responsibility and which part is an answer followed by data collection. The following breakdown comes from what brokerages receive as written first contacts during these weeks - regardless of whether the contact arrives via a form, an email or a chat window.

• Understanding a premium increase: "My invoice is higher than last year, why is that?" The answer points to tariff adjustment, vehicle type class, regional class and no-claims class - and to the fact that the regional statistics are non-binding for insurers (GDV).
• Checking the deadline: "Until when can I give notice?" This depends on the insurance period and the agreed notice period (Section 11(3) of the Insurance Contract Act), not on a calendar date from a search engine.
• Extraordinary right of termination: After a premium increase, the question of an extraordinary right of termination arises. That is a case for review with documents and running deadlines, not a chat topic.
• Requesting a comparison: "What would I pay elsewhere?" This is where intermediation begins, and with it the intermediary's duty to advise and document (Section 61(1) of the Insurance Contract Act).
• Submitting documents: Vehicle registration document, last policy, proof of the no-claims class, change of keeper. Pure groundwork that an assistant can structure and complete.
• Arranging an appointment: The wish for a conversation, often expressed outside office hours and coupled with the expectation of getting a time slot right away.

The scale of the market can be read from the intermediary register. As at 1 July 2026 it listed 47,244 (DIHK) insurance brokers licensed under Section 34d(1) of the German Trade Regulation Act, and 178,810 (DIHK) intermediaries and advisers across all categories. Whether a brokerage gets through the season calmly is rarely decided by the number of enquiries. It is decided by the share of them that is already complete when a human reads them for the first time. How strongly response time feeds through to the outcome is described in the article on response time to incoming enquiries.

The line: pre-qualification is not advice

The point at which automation projects in the intermediary business go wrong is rarely the technology. It is the division of roles. The law assigns the advice to the intermediary, not to a tool: they must ask the policyholder about their wishes and needs, advise them and state the reasons for every piece of advice given; this is documented as well (Section 61(1) of the Insurance Contract Act). This duty cannot be delegated to a chat transcript. It is tied to a person who stands behind the outcome and produces the documentation if there is a dispute.

There is also a particularity that is easily overlooked in the brokerage business: the insurer's duty to advise under Section 6 of the Insurance Contract Act does not apply where the contract is brokered by an insurance broker (Section 6(6)). Responsibility therefore rests entirely with the brokerage. An assistant that produces sentences such as "this tariff suits you" or "that gives you sufficient cover" creates exactly the expectation that a human then has to answer for. The technical answer to this is unspectacular: such statements belong outside the assistant's answer space, as a hard rule in the system rather than a style note in a handout.

Which details make an enquiry complete

Between "I am interested in motor insurance" and a workable enquiry there are usually five to seven follow-up questions. Asked during the conversation, each one costs calendar time. Asked beforehand, the conversation moves from data collection to advice. The assistant does not ask at random but in the order in which the details build on one another - and it stops as soon as the next answer would require an assessment. These six fields carry most of the preparation.

These six fields are not an application. They are the difference between an enquiry that costs a half-hour slot in the calendar and one that is decided in ten minutes. The last field is decisive: without documented consent to being contacted, the record cannot be used for a callback, no matter how complete the rest is. How that consent can be obtained and logged in the course of a conversation without tearing the dialogue apart is covered in the article on consent in chat. The reasoning behind the field order is set out in the article on qualifying enquiries via chat.

Initial disclosure: what has to be said first

Anyone who wants to broker the conclusion of insurance contracts on a commercial basis requires a licence from the competent Chamber of Industry and Commerce (Section 34d(1) of the Trade Regulation Act) and is obliged to have themselves entered in the intermediary register without undue delay after taking up the activity (Section 34d(10)). At the first business contact, certain details must be disclosed to the policyholder (Section 15(1) of the Insurance Mediation Ordinance). The ordinance lists them individually. For a chat window the first items matter most, because they have to be visible before any data collection.

• Surname and first name as well as the business address of the trader (Section 15(1) of the Insurance Mediation Ordinance).
• The role: insurance broker, tied insurance agent or insurance adviser, in each case with the licence basis under Section 34d of the Trade Regulation Act.
• The entry in the intermediary register and a note on how that entry can be verified.
• Whether advice is offered.
• The type of remuneration and whether it is payable directly by the customer or included in the premium as commission.

Three handover points between assistant and office

An assistant in the intermediary business is not a device that handles an enquiry from beginning to end. It is one section in a chain with three clearly defined handover points. Each point has a trigger, a defined content and a recipient. Writing the three points down once also produces the acceptance test cases and the basis for later analysis.

The third point is the most important and the one most often built wrongly. Where the assistant detects a question aimed at suitability, recommendation or assessment, its remit ends - but the conversation does not. It records the question verbatim, confirms the handover and captures the contact channel and time window. What has to be arranged technically and organisationally so that the handover does not end in an unattended mailbox is set out in the article on handover to staff. Without this point, exactly the impression arises that was meant to be avoided: a machine producing advice-like sentences.

The appointment is the outcome, not the conversation

During the season the calendar is the scarce resource, not the expertise. A conversation that starts with complete details is shorter and leads to a decision faster than one that begins with reading out the vehicle registration document. That is why the sensible end point of an automated dialogue in the intermediary business is as a rule an appointment - with an attached data record, not an offer. The booking assistant takes the request for the slot, the lead assistant fills it with the details that carry the conversation.

What happens outside office hours

Premium invoices are read in the evening, not in the morning. That is exactly when the impulse to do something arises, and exactly when nobody is in the office. In that window the assistant takes on no advice but two sober tasks: it answers factual questions from the knowledge base and collects the details that will carry the conversation the next morning. The caller does not lose the claim to a conversation - it simply arrives prepared.

Expectations here are well measured. In a representative survey commissioned by the digital association Bitkom, 62 percent (Bitkom) of online shoppers said they would prefer to turn to a quickly reachable human contact when a problem arose; 36 percent (Bitkom) wanted automated help. The figures come from online retail and cannot be transferred one-to-one to a brokerage, but the direction is clear enough to derive a design decision from it: the assistant is the route to a human, not the substitute for one. A dialogue that says so openly and offers the handover visibly meets less resistance than one that pretends to be the final stop.

The use of such systems has arrived in the mainstream. According to a Bitkom survey, 41 percent (Bitkom) of companies with 20 or more employees were using artificial intelligence, while a further 48 percent (Bitkom) were planning or discussing its use. Anyone starting out in the intermediary business is therefore not entering uncharted territory but a route whose pitfalls are known: unclear roles, a knowledge base without a maintenance process, and an assistant answering questions nobody assigned to it.

Data, documentation and the rest of the file

In the intermediary business, every enquiry produces a data record that goes beyond name and email address: vehicle data, contract numbers, in some cases details of claims histories. Three requirements for the build follow from this. First, purpose limitation: the assistant collects what is needed for the handover, not what would be interesting. Second, traceability: the transcript is stored so that it can be reconstructed which detail was given when. Third, location: where transcripts and attachments sit is a question that should be answered before the first conversation, not after the first incident. The framework for this is set out under data protection and hosting.

This is to be kept strictly separate from the advice documentation under Section 61(1) of the Insurance Contract Act. The chat transcript is not advice documentation and must not be filed as such. It is an annex: the prehistory of an enquiry showing which details the prospect provided themselves and at which point the handover took place. Keeping this separation clean costs an hour during setup and spares the uncomfortable question later of whether a machine gave advice. At the interface to the back-office system it becomes a question of fields - what is needed for that is set out under integration.

The knowledge base that has to be current in autumn

An assistant is only as good as what it is allowed to read. During the switching season part of that stock changes within a few weeks, and it does so predictably. The following list is not a recommendation for the whole year but the short version for September to January. Scheduled once, it does not have to be reinvented each year.

• Initial disclosure under Section 15(1) of the Insurance Mediation Ordinance as a separate item, with the current register number and the note on how the entry can be verified.
• Explanatory text on regional and vehicle type classes, with the note that the regional statistics are non-binding for insurers and are applied at the main renewal date (GDV).
• Deadline logic phrased as a condition: insurance period, agreed notice period, main renewal date - without a blanket date (Section 11(3) of the Insurance Contract Act).
• Document checklist for a switch, using the labels that appear on the documents rather than internal abbreviations.
• Availability and appointment windows for the season, including the weeks in which the office is more thinly staffed.
• Stop rules: which questions end the assistant's remit and lead into the handover.

The maintenance effort for this is manageable once it has an owner. Without a named owner, a knowledge base ages first exactly where it is read most. Anyone settling who updates what and at which interval will find the proposal for it in the article on the maintenance process for the knowledge base. A second, related case concerns questions for which the assistant finds nothing: how such a zero-result case can be caught instead of being booked as an abandonment is set out in the article on zero-result search.

What remains after 1 January

The switching season is the occasion, but not the only case. A change of vehicle, a move to another registration district, a change of keeper, a business registration or a property purchase produce the same structure: an enquiry with high intent that is incomplete before the conversation. What is built under pressure during the season carries on afterwards without pressure. The effort arises once, the benefit spreads across the year.

This becomes measurable through three figures that can be read off without additional tooling: the share of enquiries arriving at the office with complete mandatory fields, the share of dialogues that end in an appointment, and the list of questions for which the assistant found nothing. The third figure is the most useful, because it dictates the next maintenance step instead of leaving it to guesswork. How that analysis can be run without a large apparatus is shown by conversation analytics. And where a brokerage has workflows that fit no standard pattern, they belong in custom functions rather than in a compromise.

Frequent questions