Conversations power your business. But when they stay buried in transcripts and emails, they create extra work, slowdowns, and errors.
Enter the Extract Tool—your shortcut to turning conversations into action.
The Extract Tool is a specific tool for Hatch AI that allows you to define and extract structured data from AI-powered voice, SMS, and email conversations—then send that data to your CRM, calendar, or any other system via webhooks.
“Structured data” may sound like a fancy term 💅 but it really just means that it is packaged in a way that can be sent to and used by other systems.
In short, there are three parts:
✍️ Define. The Extract Tool in Hatch is used to define which information to collect (e.g., lead name, contact info, address, appointment date).It’s important for a communication platform to be able to take data in from other systems, but even more important for it to be able to send data back out to those systems as well. The Extract Tool for AI enhances Hatch’s “data out” functionality, which:
In other words: your team saves time, eliminates errors, and puts conversation data to work instantly.
The Data Extract tool makes it easy to pull important information from conversations your AI has with customers — and then send that data wherever you need it, like a CRM or email notification system. Here are two common ways our customers use it:
Imagine your AI CSR is chatting with a customer who’s interested in booking an appointment.
Here’s how you could automate the follow-up process:
Your AI CSR chats with the customer
The AI naturally gathers key details during the conversation — like their name, email, phone number, address, and preferred appointment time.
Extract the important info
Data Extract tool pulls those specific details automatically, so you don’t have to manually copy and paste them later.
Send the data to Zapier
The extracted information is sent to Zapier through a Webhook.
Zapier updates your CRM
In Zapier, you can create actions like:
Result: Your CRM stays up-to-date without any manual work, and your team can focus on serving customers instead of data entry.
Maybe you just want to be notified whenever there’s a new customer conversation.
Your AI CSR chats with the customer
As before, the AI gathers details like their name, email, phone number, address, and appointment time — plus the conversation transcript.
Extract the details you care about
Use Data Extract to capture this information automatically.
Send the data to Zapier
The extracted details are passed to Zapier via Webhook.
Zapier sends you an email
Set up Zapier to generate an email that says something like:
Subject: New Customer Conversation
Body: Includes the customer’s info and a transcript of the conversation.
Result: You and your team get instant notifications so you can follow up quickly.
With the Extract Tool, Hatch AI agents aren’t just conversing with your customers — they’re embedded in your workflows, your systems, and your data. This is what it looks like to have a truly integrated AI CSR: one that not only engages customers naturally, but also connects across platforms to keep your business moving with speed, accuracy, and insight.
What information can you tell the Extract Tool to extract?
Anything that you can put a clear definition around. For example: Name, address, phone number, issue they’re experiencing, entire transcript.
How descriptive do we need to be when creating the description for each extracted piece of information?
Be as descriptive as possible. For something like phone number, it’s pretty straightforward. But if you want to extract the whole conversation transcript you’d say something like “A transcript is the back and forth messaging between the bot and the customer. When creating the transcript you’ll want to prefix each line with who is speaking “bot” or “human”
Where can you send the information to?
Anything that has an API connection. So, another app or middleware
How quickly does this information get sent to a CRM?
The information will be sent to the CRM instantly.
Where would it appear in the CRM?
The power of sending the information to a middleware like Zapier is that you can define exactly what information goes into which field.
What if you have multiple bots?
The “conversation completed” trigger for the webhook is going to hit that webhook any time a conversation is completed. If you want the webhook to send information to another system only for conversations completed with one particular bot, you would create that rule in your middleware (for example, “if bot’s name is X…”)
Can we have it send data over that wasn’t part of the conversation? e.g., how much the lead cost?
Not with the current functionality, but it is possible. Many use cases are possible with this new feature, so let us know what you’re looking for and that will help us to prioritize what new capabilities we build out.