Signing. Doux it.
The link isn't broken. Here's what is. The signing record read line by line, the packet proven, the most likely cause named, and the same link resent with three plain steps.
“The link is broken.” The agent panics and rebuilds the packet. The client now has two links, signs neither, and the deal stalls for a week.
The signing record, read line by line. Proof the packet works. The most likely cause, and how sure. The same link, resent with three plain steps. Signed and paid, on the file.
How it runs.
- Reads the signing record line by line: sent, opened, started, saved, payment reached. Marks where it stops.
- Proves the packet: someone else signed the same build, or your own test. Separates your agency's opens from the client's.
- Names the most likely cause, and how sure it is.
- Resends the same link with three plain steps, copies the agent, and writes a one-line note ending with the hands-off rule.
- Watches until the record shows signed and the payment shows received.
What it touches.
Why it matters.
A stuck signature usually turns into panic. The agent rebuilds the packet, the client gets two links, and the deal stalls. With the kit it is diagnosed from the evidence in minutes, and the answer is usually the same: the link was never broken.
The most common cause is the link opening inside an email app's built-in browser, where a drawn signature or the payment page can fail. Then a drawn signature that never saved on a small screen. Then an expired or older link, a blocked payment step, or the wrong email address.
DouxProcess reads the record, proves the packet and writes the fix: the same link, three plain steps for the client, and a short note for the agent. A licensed person approves anything that changes the policy.
Where it stops.
- Never edits, voids or rebuilds a working packet while a client is in it. It resends the same link.
- Never tells the client the link is broken when the record says it works.
- Says “confirmed” only when the client or the record says so. Otherwise “most likely”, with the evidence.
- Never takes card or bank details by phone, text or email. The client pays on the payment page.
- Never blames the client. The fix is steps, not a lecture.
- Never promises coverage starts before the signature and the payment are both received.
Straight answers.
How does it know the packet works?
From proof, not hope: another client who finished the same build, and how fast, or your own test in a normal browser. If the packet works, this is one client's anomaly. Fix it, don't panic over it.
What are the three steps the client gets?
Open the link in the phone's main browser, not the email app. If drawing the signature doesn't work, type the name. Finish the date, then pay. Same link, plain words, the agent copied.
Why not just send a new packet?
Editing, voiding or rebuilding a packet mid-signing resets what the client started and sends a second link. Now there are two, and the client signs neither. The same link, resent, is the fix.
What about the opens from my own team?
It separates them. Opens from the agency's own checks are marked as yours, so the record shows only what the client did.
When is it done?
Only when the record shows signed and the payment shows received. Until then it keeps watching and says what will show next.
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 stuck packets 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: paste the client's message and the signing record. You get the verdict, the timeline, the most likely cause, the client email and the note for the agent.
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 agent's email. Click inside it, Ctrl+A, Ctrl+C (Cmd on a Mac).
- Paste it in the chat.
- The client's text: screenshot it on the phone and attach it.
- Documents (or Sent) › the client's packet.
- Activity (or History, Audit trail).
- Download it as PDF, or screenshot the whole list.
- Attach it in the same chat.
- In the same list, find another client who finished the same packet.
- Screenshot that row and attach it.
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.