Phones. Doux it.
Someone's out. Switch the phones in minutes, not a support ticket. The exact clicks from your own phone system's screens, a new menu instead of the everyday one, a four-point read-back, and an undo that points the line back.
Your CSR calls in sick at 7:40 AM. The phones ring out. Voicemail fills up. Somebody edits the everyday menu to get through the day, and nobody remembers how to put it back.
A high-volume greeting, word for word. Press 1 to hold, press 2 for a call back. A new menu, never the everyday one. The undo written down before the switch. Every caller on one ranked call-back list.
How it runs.
- Confirms who is out, who may take calls, the wait to quote and the menu the line goes back to.
- Writes the greeting word for word: high call volume, estimated wait 15 minutes, press 1 to hold, press 2 for a call back.
- Lays out a new high-volume menu. The everyday menu is never edited.
- Gives the exact switch and the exact undo, then has you read back four things.
- Turns the call log and voicemails into a ranked call-back list. End of day: the undo and the read-back.
What it touches.
Why it matters.
Changing call handling is usually the hard part. A support ticket, a wait, and a wrong setting a client finds for you. With the kit it is a standard switch: it reads your own phone system's screens, gives the exact clicks, has you read back four things, and the undo is pointing the line back.
The person who answers your phone calls in sick. The phone keeps ringing. Callers hold with no idea how long, hang up, and call back three times. Or the menu gets edited in a hurry, and a week later it still tells callers you are short-staffed.
At an agency, a missed call is a claim nobody heard about, a certificate a job site is waiting on, a payment about to lapse.
DouxProcess writes the greeting, plans the hold and call-back menu, and gives you the exact clicks to switch it and to undo it. Then it turns the day's call log and voicemails into one ranked list: claims first, then cancellations and proof of insurance, payments, new quotes, everything else. A licensed person makes every call back.
Where it stops.
- Never touches your phone system. You make the switch. It gives you the clicks.
- Builds a new menu. Never edits the everyday one. The undo is pointing the number back.
- Never rings anyone who said no. Not even for the urgent ones.
- Promises only the wait you can keep. Nobody holds longer than the greeting says.
- Nothing is live until you read back four things: where the number routes, what press 1 does, what press 2 does, and who it rings.
- Never tells a caller they are covered. A licensed person makes every call back.
Straight answers.
Does it change my phone system?
No. It writes the greeting, lays out the menu and gives you the exact clicks, in the words your own phone system uses. You make the switch. Send it a screenshot of your call handling: it never guesses a menu name or an extension.
What does the caller hear?
High call volume, the estimated wait you set (for example 15 minutes), press 1 to stay on hold, press 2 for a call back. Under 25 seconds. No promise of coverage, prices or outcomes.
How is the call-back list ranked?
Claims, accidents and losses first. Then cancellations, lapses and proof of insurance needed today. Then payments, new quotes and everything else. Earliest call first inside each level. Repeat callers move up.
What about missed calls with no voicemail?
They still get a row. A missed call is a call back too.
How do I put it back?
Point the main number back at the everyday menu. The undo is written down before the switch, with the menu's name or extension. At the end of the day you get the undo checklist and the read-back that proves the everyday menu is back.
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 call log today.
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: tell it who is out and paste your call handling. Paste the call log and voicemails as the day goes. You get the greeting, the menu, the switch and the undo, and the ranked call-back list.
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.
- Sign in to the admin page.
- Phone numbers › your main number. Screenshot where business hours route.
- Auto attendants › that menu. Screenshot what each key does.
- Attach the screenshots.
- Reports › Call log › Today.
- Download (PDF or a spreadsheet).
- Attach it. Paste voicemail transcripts too.
- Type them, for example:
Dana's out all day. Arlo takes calls, not me. Quote a 15 minute wait. Back to normal tomorrow. Set up the phones and tell me who to call back first.
The assistant never touches your phone system. It writes the plan; you make the switch in your phone admin page, click by click, then read back four things. The undo: point the number back. Delete nothing. Not an admin? Ask whoever runs your phones to sign in with you.
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.