An autoresponder sends a prepared email automatically under a configured rule.

GetResponse describes automatic messages following subscription, with several messages possible in a cycle.

What starts the response

Mailchimp separates a flow’s trigger from its actions. A send-email action sends the designed email when a contact reaches that step.

Mailchimp’s triggers apply to events after activation. An old contact record alone does not demonstrate that a new entry event occurred.

Fictional signup plan

Fictional print-workshop plan: a new signup for workshop updates should receive a prepared welcome note explaining those updates.

Fictional signup response
CaseChosen handlingCheck
New signupSend the welcome noteInspect entry and email action.
Old contact recordLeave entry unresolvedFind the event that would start this plan.

The workshop coordinator checks the event before treating the old record as a new signup.

Names vary by platform

GetResponse distinguishes its cycle-based Autoresponders from its Automation workflows. It says that creating a workflow based on autoresponder messages does not switch those autoresponders off.

Check both active configurations before assuming the earlier sending process has stopped. Product labels alone do not establish the rules.

Check status

Mailchimp’s paused flows stop adding contacts and progressing existing contacts until reactivated.

Keep the rule, message and current status with a named owner. Recheck them when the promised information changes.

Sources

GetResponse: Autoresponder Messages

GetResponse: Autoresponders and Automation

Mailchimp: Automation Flows

Mailchimp: Send Email Actions