This is a concise English adaptation. Read the full Spanish edition for the complete analysis, tables, and reporting context.
The practical takeaway
Map every source: forms, calls, events, messaging, campaigns, and referrals. Record what arrives, where it is stored, who responds, and the expected response time. Stop the sequence when the person responds, books, opts out, or changes status. Checked October 18, 2026: Google requires SPF or DKIM for senders to personal Gmail accounts. For senders exceeding 5,000 daily messages to those accounts, it requires SPF, DKIM, and DMARC, plus one-click unsubscribe and a visible unsubscribe link for marketing and subscribed messages. These channel requirements do not establish permission to contact a lead. Test replies, bounces, opt-outs, and duplicates before activation, including messages queued in another system. Preserve source, need, contact details, applicable permission, owner, status, and next action. Measure effective contacts and opportunities alongside response time.
Keep these points in mind.
- Centralize incoming leads before building sequences.
- Prioritize fit and intent, not only arrival time.
- Stop reminders when someone responds and preserve the conversation in the CRM.
Sources in the original edition
- Source 1: commission.europa.eu (opens in a new tab)
- Source 2: support.google.com (opens in a new tab)
Turn the idea into a useful workflow.
Identify a recurring task, define its owner, and decide what a good result looks like.
Take the free automation assessment