CRM foundations
Agree on fields, ownership, consent and data quality before adding workflows that will only reproduce gaps and inconsistencies at greater speed.
Go to chapter ↓CRM & Automation
Automation for the process, not the relationship
Straightforward guidance for customer data, lifecycle communication and responsible automation.
FocusCRM & Automation
Best forCRM, sales and lifecycle teams
Intended outcomeUseful automation without impersonal journeys
Three working areas
What this guide helps you decide
Start with reliable customer data and clear lifecycle decisions, then automate the repetitive work while preserving human judgment where it matters.
Lifecycle and lead management
Define lifecycle stages, hand-offs and useful triggers so messages respond to real customer behaviour rather than arbitrary campaign dates.
Go to chapter ↓Automation with human oversight
Keep people involved in exceptions, sensitive decisions and quality review, with a clear route to pause or correct an automated process.
Go to chapter ↓The practical answer
What to do first
Good automation begins with clean definitions, a lawful data basis and clear lifecycle decisions. Automate repeatable actions only after ownership and exceptions are understood, keep people in sensitive decisions and make every journey easy to stop, correct and audit.
Chapter 1
CRM foundations
Agree on fields, ownership, consent and data quality before adding workflows that will only reproduce gaps and inconsistencies at greater speed.
A CRM is a shared operating record, not an address book. Define required fields, acceptable values, lifecycle stages, ownership and retention before connecting more tools. Collect only information with a clear purpose and record the lawful basis, source and consent evidence where relevant.
Actions to take
- Create a field dictionary with purpose, owner and retention rule.
- Remove duplicates and define one source of truth.
- Record consent and lawful-basis evidence in an auditable form.
Chapter 2
Lifecycle and lead management
Define lifecycle stages, hand-offs and useful triggers so messages respond to real customer behaviour rather than arbitrary campaign dates.
Map the customer lifecycle in observable states: enquiry received, qualified, proposal sent, customer active, renewal due. A trigger should respond to a meaningful change or need. Time-based sequences can help, but they should stop when the person acts, objects or no longer belongs in the journey.
Actions to take
- Map lifecycle stages and hand-offs with sales and service.
- Trigger messages from meaningful customer behaviour.
- Add suppression rules for customers who act, object or become ineligible.
Chapter 3
Automation with human oversight
Keep people involved in exceptions, sensitive decisions and quality review, with a clear route to pause or correct an automated process.
Use human review for high-value exceptions, vulnerable customers, complaints and decisions with material effects. Monitor delivery, errors, opt-outs and downstream outcomes. Every workflow needs an owner, a documented purpose, a test record and a reliable kill switch.
Actions to take
- Assign an owner and failure alert to every workflow.
- Route sensitive cases and exceptions to a person.
- Review errors, complaints and business outcomes at a fixed interval.
Decision table
Weak signals versus a stronger system
| Decision | Weak approach | Stronger approach |
|---|---|---|
| Collect data | Store everything in case it is useful | Collect defined fields for a stated purpose and retention period |
| Build a journey | Send a fixed sequence to every lead | Use lifecycle state, behaviour, suppression and exit conditions |
| Score leads | Hide the formula in the tool | Use explainable signals and review bias and false positives |
| Govern workflows | Assume automation keeps working | Assign ownership, monitoring, audit history and a kill switch |
Working checklist
Ready to put into practice?
Use this as a review, not a score. Any unchecked item is a useful next conversation for the team.
- 01Every field has a purpose and owner.
- 02Consent and lawful basis can be evidenced.
- 03Lifecycle definitions are shared by marketing and sales.
- 04Workflows have exit and suppression rules.
- 05Sensitive decisions receive human review.
- 06People can object, unsubscribe or request correction easily.
FAQ
Questions teams ask in practice
Do we always need consent to process CRM data?
No. Consent is one lawful basis among several, and the correct basis depends on the purpose and relationship. Direct electronic marketing has additional rules; obtain qualified advice for the specific use.
What should be automated first?
A frequent, stable and low-risk process with clear inputs and an obvious exception route—often internal reminders or data-quality checks before customer-facing persuasion.
Can lead scoring be fully automatic?
It can assist prioritisation, but teams should understand the inputs, test for unfair exclusions and retain human review where the decision materially affects a person.
Primary references
Sources and further reading
The guide is editorially independent and uses official sources for technical, regulatory and measurement claims. Apply legal guidance to your specific situation.
- 01CNPD — Consent ↗
Portuguese authority guidance on when consent is appropriate and what makes it informed and specific.
- 02CNPD — Right to object ↗
Official explanation of the unconditional right to object to direct marketing.
- 03EDPB — Data protection guide for small business ↗
European guidance covering lawful processing, rights, security and practical SME responsibilities.
