Endorsements. Doux it.
Policy changes turned into clean carrier submissions, followed up until issued and filed when they land. Endorsement processing for independent agencies.
Add a truck. Drop a driver. Change an address. Three emails. Two portals. One forgotten follow-up. One very unhappy client.
The request becomes a clean change. Submitted to the carrier. Followed up until it's issued. Filed the minute it lands.
How it runs.
- Reads the change request, however it arrives.
- Pulls the policy and writes the exact change.
- Submits it to the carrier, through the portal or by email.
- Follows up on schedule until the endorsement is issued.
- Checks it against the request, files it, and sends it to the client once you sign off.
What it touches.
Why it matters.
Policy changes never stop. A truck added. A driver dropped. A new location. A higher limit for a job that starts Monday. Each one is a request, a submission, a follow-up and a filing.
The follow-up is where it breaks. The carrier never answers. Nobody follows up. The client believes the truck is covered. It is not.
DouxProcess turns every change into a clean submission with everything the carrier needs, then follows up on schedule until the endorsement is issued. When it lands, it checks the endorsement matches what was asked, files it and sends it to the client once you sign off.
Where it stops.
- Never tells a client a change is covered until the carrier confirms it.
- Binding stays with a licensed person. Always.
- Checks the issued endorsement against the request. Mismatch? You hear about it.
- Premium changes are shown to you before the client is billed.
- Every submission and every follow-up is logged with a timestamp.
Straight answers.
What kinds of changes does it handle?
Vehicles, drivers, equipment, locations, additional insureds, limits, addresses and named insured changes. Anything that is a policy change request.
Can it bind the change?
No. It prepares the change and submits it. A licensed person approves anything that binds coverage, within the carrier's authority.
Can my client get ID cards the same day?
When the carrier issues them, yes. It requests them with the change and sends them to the client once you approve.
How often does it follow up with the carrier?
On the schedule you set. Every two business days is a good start. Overdue changes come to you before they become a problem.
Does it update my agency management system?
Yes. The change, the endorsement and the premium adjustment are recorded on the policy.
Take the recipe.
The procedures this workflow runs on, written as one file. Load it into Claude, ChatGPT or Gemini and run it on your own change requests today.
Watch it installed: Claude · ChatGPT · Gemini
Downloads open after you sign the kit license: you build it, you run it, you answer for it.
How to load it. Nothing to install.
- Claude: Settings, Capabilities, Skills, Upload skill. Pick the .zip.
- ChatGPT: start a Project or a custom GPT and paste the .md into its instructions.
- Gemini: make a new Gem and paste the .md into its instructions.
- Then use it: paste in the email or attach the PDF. You get a table and drafts back. You approve. You send.
Before the first run
Installing it is half the job. The first run needs these from your own systems. Gather them first: a minute or two each.
- Open the email.
- Click inside the message. Press Ctrl+A, then Ctrl+C (Cmd on a Mac).
- Paste it in the chat. Attach anything that came with it.
- Search for the client and open it.
- Policies › the policy (for example, commercial auto) › Documents.
- Download the current declarations and the schedules the change touches (vehicles, drivers, locations) as PDF.
- Attach them in the same chat.
Nothing to connect, no password to share: you copy one thing and download the other. Not in your system? Get it from the carrier's website. Never from memory.
On its own it reads what you paste in and drafts the work. Want it wired into your mailbox, management system and carrier portals? The builder kit teaches your programmer every step: database, passwords, approvals, deployment. Or let DouxProcess run it for you.