In plain English
A simple CRM workflow should create one reliable lead record, preserve source and consent, assign a named owner, show the next action and support a backup route. It should track qualification and sales outcomes with clear definitions, while allowing authorised people to correct, pause or complete the process when automation or data fails.
Which fields does the first lead record need?
Capture only the information needed to identify the enquiry, respond safely and route it correctly. Typical fields include a stable reference, contact details, company, requested service, message, source page, campaign values, privacy acknowledgement, marketing choice, owner, status and next action. Required fields should have a clear operational reason; extra friction and unused personal data create cost and risk.
Keep controlled values for goals, stages and outcomes so reports do not split one concept across many spellings. Allow notes for context, but do not bury essential routing in free text. Record when and how a value changed if it affects ownership or reporting. The lead record should be usable by the person responding, not designed only for a dashboard.
How should ownership and follow-up work?
Assign an owner as soon as the lead is accepted and create a visible due action. The routing rule can use service, location, account relationship or availability, but it needs a deterministic fallback. Alerts should identify the record and required action without exposing more personal information than the recipient needs. Escalate unassigned and overdue records to a named backup.
Follow-up tasks should reflect the customer's request and the business's staffed coverage. Use reminders to support human action, not to generate repeated messages without context. Make it easy to pause a sequence when the customer replies, opts out, is unsuitable or reaches a final outcome. Manual recovery is part of the design, not evidence that the workflow failed.
Where should consent and channel permissions appear?
Store the service-response basis separately from optional marketing consent. Record the wording or version presented, the person's choice, timestamp and source. Apply suppression and opt-out rules before sending promotional communication. South African direct-marketing operations should be designed against POPIA and the Information Regulator's current guidance with qualified advice for the business's circumstances.
Channel permission should travel with the contact when tools are connected. An email address captured for a quote should not silently become permission for unrelated SMS, WhatsApp or email promotion. Restrict exports, integrations and user access to what the approved purpose requires. Document processors and retention so the workflow can support the privacy notice rather than contradict it.
Sources for this section: Guidance notes.
How does the workflow improve marketing decisions?
Use stable stages to return lead quality and sales outcomes to the marketing review. Campaign parameters can help identify referring activity, while customer conversations and sales records add context that analytics cannot observe. Keep attribution confidence visible. The CRM should answer what happened to the enquiry before it is asked to prove why every sale occurred.
Where appropriate and approved, deeper outcomes can be imported to advertising platforms. Google explains that offline conversion systems connect later actions with prior ad interactions. That integration is optional and comes after reliable records, consent and account controls. A small business gains more from complete ownership and outcome fields than from a complex automation that nobody can audit or recover.
Sources for this section: Collect campaign data with custom URLs, About offline conversion imports.
Official references
- Guidance notes (Information Regulator South Africa)
- Collect campaign data with custom URLs (Google Analytics Help)
- About offline conversion imports (Google Ads Help)