A list provides context
A list subscription can begin a sales workflow. GetResponse campaignId identifies a list. A list name alone does not establish a Meta campaign, acquisition cost or sales attribution.
One person may belong to several lists. List membership and an enquiry event should not create multiple copies of that person.
Use the existing connection
Open Integrations and GetResponse in an authorised Ermission organisation. Use the existing secure API-key form and list selection. Never put credentials in a chat or customer note.
After importing, check the available operation state, contacts and source history. A partial result or error requires investigation rather than an assumption of completeness.
- Confirm the organisation and account.
- Select permitted lists.
- Run the available manual import.
- Review contacts, sources and conflicts.
- Plan the next action in the existing CRM.
Verify numbers and identity
Phone data may be stored in recognised fields such as home_phone, mobile_phone and work_phone, depending on the source. Do not guess missing values.
Normalisation must not guess a country or overwrite conflicts automatically. A shared number or ambiguous match needs investigation.
A historical import is not an automatic call
Distinguish a fresh subscription from a data update, list movement or resubscription. Re-importing a contact does not create a new paid lead.
The current Ermission scope does not activate an automatic scheduler or AI call after import. Contact eligibility, telephony and the agent need separate activation. Start with an assigned customer and one task.
Sources and product scope
Prepared with AI assistance and checked against the current implementation and cited sources. Product availability may change; check the linked scope.