Make a dossier for each contact-form mail
When a customer writes to you through the contact form on your site, this workflow makes a dossier on that customer, so whoever answers knows who they are. When the person wrote before, it adds the new mail to their dossier.
What it does
Section titled “What it does”- It reads the new form mail. A mail that is not from a customer gets no dossier.
- An AI step finds out who wrote: a new person, or a person with a dossier already. The same person can write from more than one address.
- Web searches look for the person, their company, the company’s news, and signs that the company uses one of your competitors.
- It reads your CRM to see whether the person was your customer before and canceled.
- An AI step writes the dossier in six parts:
- who the customer is: name, role, and what public sources say;
- the company: what it does, its headquarters, size, and owner or stock listing;
- what their mails say: what they want, numbers and dates;
- the company’s news of the last 90 days, each with its date and link;
- signs that the company uses one of your competitors, with links, and how strong each sign is;
- whether they were your customer before, with the plan, the dates and the reason they canceled.
- The workflow makes a new Google Doc, or updates the existing dossier with what changed.
One run handles one mail. It has 2 AI steps and 3 web searches.
What you fill in
Section titled “What you fill in”You give these in the build chat:
- the mail address and the subject of your contact-form mails;
- the Drive folder of your dossiers;
- the names of your competitors;
- the field of your CRM that says whether a contact was a customer.
What it needs
Section titled “What it needs”- Gmail, Google Drive and Google Docs, from one Google account that you connect;
- HubSpot, connected as a ready connector;
- web search, which Toolscaled gives every workflow. A web search costs credits.
Where the result goes
Section titled “Where the result goes”One Google Doc for each customer in your dossier folder, named “Customer dossier: <name> (<company>)”.
Why it runs by itself
Section titled “Why it runs by itself”Contact-form mails come at any time, and the person who answers needs the dossier before the reply. The workflow starts on each new form mail, so the dossier is ready when someone opens the mail. What starts a run shows how to start a workflow on new mail.
How it was built
Section titled “How it was built”One chat in claude.ai with the Toolscaled connector: about 45 minutes of Claude’s work in five parts, over 22 hours. The chat stopped at gaps in Toolscaled, for example a folder that Claude could not list. We fixed each gap and released the fix between the parts. The record of the first four parts holds 6 messages from the person. The fifth part is not stored. The person typed these messages. We replaced the mail address and the names of the competitors with brackets. The [bench] tag marks the test data.
-
Use Toolscaled. When a customer writes to us through the contact form on our site, I want a dossier on that customer, so whoever answers knows who they are. We sell Toolscaled; our competitors are [four automation tools].
The form mails come to [form address] with the subject “[bench] Contact form: …”. There are 10 waiting now. Go through them oldest first. For each mail, find the customer’s dossier in my Google Drive folder “Toolscaled benchmark/Customer dossiers” (a Google Doc named “Customer dossier: <name> (<company>)”). The same person can write from more than one address. If there is none, create one with six parts:
- who the customer is: name, role, and what public sources say about them (finding nothing is fine; never use a namesake),
- the company: what it does, headquarters, size, owner or stock listing,
- anything of note from their mails: what they want, numbers, dates,
- recent news of the company from the last 90 days, each with date and link,
- signs that the company uses [one of the four], from public sources with links, and how strong each sign is (a company that only offers its own app on their marketplace is a vendor there, not a user),
- whether they were our customer before and canceled: our HubSpot contacts have a Customer status (active or canceled) with the plan, dates and the cancel reason.
If a dossier exists, add the mail and update what changed; never make a second dossier for the same person. A mail that is not from a customer gets no dossier. Don’t read LinkedIn pages.
After these 10, I want this to run by itself for every new form mail.
-
It’s not empty, there are already 3 dossiers in it. I’ve now given Toolscaled access to all my Google Drive files, so you should be able to see the folder and what’s in it. Please go ahead.
-
Please try again, the folder should be visible now.
-
Please try again, the folder should be visible now.
-
Yes, write them. No mails to anyone, please; dossiers only.
-
They look fine. Yes, please go ahead and set it up so it runs by itself for each new form mail.
Claude did the 10 mails once in the chat and showed each dossier before it wrote any file. After the person’s yes, it wrote them to Drive and saved the workflow, with the trigger that starts it on each new form mail.
The numbers
Section titled “The numbers”We ran the workflow on 11 test mails from 9 people that the build chat never saw. A full pass makes 8 new dossiers and updates 1. The grade counts 6 parts for each of the 9 people: 54 parts a pass, 270 parts in 5 passes. How we measured gives the method.
| Workflow | |
|---|---|
| Time | 106 s a mail; 25.9 min of run time for the 11 mails |
| Cost | 281 credits for the 11 mails, about $0.53 |
| Parts right, of 270 | 242 right, 0 wrong, 22 partial, 6 missing |
| Same answer in 5 passes | 43 of 54 parts |
The agent that did the same task from the same request stopped after 1 of the 9 dossiers, so this page has no comparison. Its one dossier had all 6 parts right.
The build chat cost about $5.66 at list price for its first four parts, and your chat plan pays for it.