Communicating with the farms
- First working version
- 2 h
Goal
An agent that understands the user’s objective, writes the emails to match, keeps the communication going, updates the calendar as meetings get agreed and creates a document with what to prepare for each one.
How it works
First the user explains to the agent what they want to get and which list of contacts to use. The agent pulls back what is already known about each centre and fills the gaps by searching online, to write a first email tailored to each contact.
The user reads the drafts to check everything is right and hits send.
Whenever the user asks (or automatically every 30 minutes), it goes back over the open conversations, works out what each reply is asking for and leaves the answer ready inside the right thread, in drafts again. When it is time to propose a date it looks at where the calendar has room, so it does not offer an hour that is already taken, and as soon as the meeting is agreed it creates it with the address, the contact and the agreed time.
To finish, it creates a preparation document per meeting: what has been said so far, what the centre works on and what is worth asking, for the user to read before walking in.
- Deliverable
- The drafts waiting in Gmail, each inside its own thread.
- The meetings created in the calendar with their address and contact.
- A preparation document per meeting: the history of the conversation, the context of the centre and the questions worth bringing.
- Stack
- Claude Cowork
- Gmail (MCP)
- Google Calendar (MCP)
- Claude web search
- Project memory
Why it matters
Keeping several conversations going at once is a basic pillar of a lot of jobs. Automating part of that while holding on to the context and the personal touch frees up time that is in short supply, and that time can go to work that adds more value.
What could come next
- 01Wire the calendar to the briefing, so moving a date updates both at once.
- 02A record of which emails got a reply and which did not, so the next round starts knowing what kind of message works.
- 03Update the ERP every time a conversation changes state, so the agreed meeting and what was said land where customers and opportunities are already managed, without anyone typing it twice.
Worth knowing
- legal
The agent prepares, the person sends. That is the rule everything else rests on: if a message goes to the wrong place or says the wrong thing, someone read it first. Sending is the one step worth leaving manual, however tempting it is.
- legal
Following the threads means reading the inbox, so the agent sees mail that has nothing to do with this campaign. Its access is worth narrowing to the conversations it is meant to handle.
- dependency
It depends on Gmail and Google Calendar both being connected. Lose one and that part of the job falls back to being done by hand.