A caller joins your list only if they said they wanted to
A Zap that catches our webhook can add the contact to an audience and tag what they rang about. The catch needs a paid Zapier plan. Consent is your job, and it is not optional.
Caller
“You're closed for the season by the looks of it. Can you email me when the spring dates open up?”
What happened next
- Caller's email captured and their request noted on the call
- Contact added to the Spring Waitlist audience with a season tag
- Consent recorded, because she asked to be emailed in her own words
How GreetKeeper connects to Mailchimp
Three states, and we publish the one that is true rather than the one that reads best.
| Tool | How it connects | What that means |
|---|---|---|
| Mailchimp | Through Zapier |
What Mailchimp is
Mailchimp is email marketing software. You keep an audience, you tag the people in it, and you send campaigns to segments built from those tags.
Its Zapier app can add or update a subscriber in an audience, apply tags, and set the subscription status. Status is the field that matters most here.
Mailchimp also handles unsubscribes for you. Once someone opts out there, they stay out, and a later Zap will not quietly put them back in.
What gets added, and when it should not be
A contact in one audience, with tags, and only when the caller agreed.
The contact carries the caller's email, their name and a tag describing what they rang about. Tags are how you segment later, so use a small fixed set rather than inventing one per call.
Only add someone who agreed to hear from you. A caller asking a question is not a caller asking for your newsletter. Wire the Zap so it fires on an explicit yes, not on every finished call.
The safest setup uses a consent flag the AI captures on the call. If that flag is false, the Zap stops. That single filter is the difference between a list you can mail and a list that generates complaints.
Setting it up properly
The consent step is first because it is the one people skip.
Decide what counts as consent and train the AI to ask
Write the exact question you want asked, such as whether they would like emails about new dates. Capture the answer as a field you can filter on.
Catch the webhook and filter before the Mailchimp step
The Zap begins with Webhooks by Zapier on Catch Hook, and GreetKeeper posts to the address it gives you. Add a filter straight after it. Let the Zap continue only when consent is true and an email address exists. Everything else stops there, which is the correct outcome.
Connect Mailchimp and choose the audience and tags
Pick the audience, then set the subscription status deliberately rather than accepting the default. Apply one tag naming the source as phone, plus one for the topic.
Test with your own address and then unsubscribe yourself
Confirm the contact arrives with the right tags and status. Then unsubscribe and place a second call, to prove the Zap does not resurrect an opted-out person.
The rules you still own
Questions about Mailchimp and GreetKeeper
Should every caller go on the list?
No. Only add someone who agreed to hear from you during the call. Filter the Zap on an explicit consent field, and let everyone else pass through untouched.
What if the caller is already unsubscribed?
Mailchimp keeps them unsubscribed. An add attempt will not silently re-subscribe them, which is exactly the behavior you want. Test this yourself before going live.
Can the tag say what they rang about?
Yes, and it is the most useful part. Map a small set of topic tags so you can later mail only the people who asked about one thing.
What Zapier plan does this take?
A paid one. Our call reaches Zapier as a webhook, caught by Webhooks by Zapier, and Zapier counts that app as premium. No GreetKeeper Zapier app exists yet.