Workflow automation solution
Customer onboarding automation
Coordinate customer information, documents, decisions and system setup through one visible onboarding workflow. Reduce chasing and re-entry while preserving the human and regulatory decisions that require accountable judgement.
What customer onboarding automation should achieve
Customer onboarding automation should move an accepted customer or application to a clearly defined ready state. It can coordinate structured capture, document requests, validation, internal reviews, approvals, account creation, service configuration, access invitations and customer communication.
The workflow should show what is complete, what is missing, who owns the next action and which system contains the authoritative record. Faster form submission is not enough if setup, verification or activation still waits in an invisible queue.
01
Fragmented onboarding creates delay before value
- sales, operations, finance and compliance keep separate checklists;
- customers provide the same details through several channels;
- documents are requested without clear status or expiry;
- internal teams wait for one another without owned due dates;
- records are created inconsistently across CRM, billing and service systems;
- exceptions depend on personal follow-up; and
- the customer cannot tell what happens next.
02
Design the path around a verified ready state
Define ready state by customer type. It may require a signed agreement, verified information, an approved credit or risk decision, billing setup, assigned service owner, configured product and successful access. Do not mark onboarding complete until the required downstream actions are confirmed.
03
Combine customer experience with internal coordination
Capture
Progressive information
Ask for the right information at the right stage and reuse verified data.
Evidence
Document exchange
Show requirements, receipt, review status, expiry and resubmission clearly.
Work
Owned internal tasks
Route finance, operations, risk and service actions with due dates and exceptions.
Activation
Verified provisioning
Create accounts, permissions and service configuration with confirmation and recovery.
A customer self-service portal can provide the external journey while a workflow service coordinates internal tasks and systems.
04
Model regulated checks only where they actually apply
Some South African accountable institutions must perform risk-based customer due diligence, record keeping and related controls under the FIC Act. The Financial Intelligence Centre's Guidance Note 7 explains concepts including establishing and verifying clients, beneficial ownership, ongoing due diligence and risk management programmes.
Do not copy a generic FICA checklist into every onboarding process. Confirm whether the organisation and activity are in scope, which checks are required, who may decide, which evidence must be retained and when enhanced review is needed. Keep policy ownership with the accountable business and its advisers.
| Workflow responsibility | Human or policy responsibility |
|---|---|
| Collect required information and evidence | Define what is required and why |
| Run supported verification steps | Approve providers, thresholds and exceptions |
| Route risk-based review | Make accountable acceptance or rejection decisions |
| Preserve decision and evidence references | Set retention and access policy |
05
Limit personal information and access throughout onboarding
- collect each field for a defined onboarding purpose;
- separate optional marketing preferences from required service processing;
- restrict customer, staff and service-provider access by role and record;
- avoid sending sensitive evidence as ordinary email attachments;
- protect temporary files, exports, logs and support tools;
- define operator responsibilities and breach handling;
- set retention and deletion rules for successful and abandoned applications; and
- support correction and data-subject processes where applicable.
Use the Information Regulator's POPIA resources and obtain appropriate advice for the specific onboarding activity.
06
Name one owner for every record and state
| Record | Possible owner | Workflow responsibility |
|---|---|---|
| Opportunity and relationship | CRM | Receive accepted start and write onboarding outcome |
| Application and tasks | Workflow service | Coordinate status, rules, assignments and exceptions |
| Documents | Controlled document store | Manage metadata, review state, access and retention |
| Billing account | Finance or ERP platform | Create once and verify the returned identifier |
| Service account and access | Product or identity platform | Provision safely and reconcile failures |
Use supported APIs or controlled adapters and design every create action for retries. Read how to build a workflow on an existing ERP or CRM.
07
Deliver one customer type and one ready state first
- Choose a representative customer segment and onboarding trigger.
- Map customer steps, internal tasks, decisions and system updates.
- Define required evidence, privacy purpose and exception ownership.
- Prototype the highest-risk verification and provisioning integrations.
- Pilot with real edge cases and a manual recovery path.
- Measure time, completion, missing-information cycles and setup failures.
- Expand to another segment only when its rules justify the variation.
Use the workflow automation service for orchestration and the document intake automation solution when evidence processing is the main bottleneck.
Sources and scope
Primary references
- Financial Intelligence Centre, Guidance Note 7
- Information Regulator South Africa, POPIA resources
- FIC Act duties apply to defined accountable institutions and activities. This page is operational design guidance and not legal advice.
Questions
Frequently asked questions
What is customer onboarding automation?
Customer onboarding automation coordinates data collection, document exchange, verification, internal tasks, decisions, system setup and customer communication from an accepted opportunity or application to a verified ready state.
Should customer onboarding be fully automated?
Not always. Automate repeated capture, validation, routing, reminders and system setup. Keep people at material risk, eligibility, exception and relationship decisions.
Can onboarding connect to CRM, finance and service systems?
Yes. A workflow can use the CRM as the opportunity source, collect approved information, create or update finance and service records, provision access and write the verified outcome back to the owning systems.
Does every onboarding workflow require FICA checks?
No. Customer due diligence duties under the FIC Act apply to accountable institutions and relevant activities. Other businesses may have different contractual, risk or regulatory checks. Confirm the specific obligation before designing the workflow.
How should onboarding success be measured?
Measure end-to-end time, customer completion, missing-information cycles, manual touches, exception age, setup errors, activation and the time until the customer reaches the intended first value.
Improve customer onboarding
Bring the customer types, required information, checks, systems and ready-state definition.
LCR can help map the onboarding journey and build the smallest workflow that produces a verified operational outcome.