50 shades of...Cases and Tasks
- Jim Walker
- May 9
- 5 min read
Updated: May 13
I have the great pleasure of working with so many Civica Cx sites, and one question that seems to come up fairly frequently is:
"Should I use Feedback, CRM or Generic for this process?"
This post is here to give you a good intro to the core Cases and Tasks functionality available within Cx Housing. Whether you’re configuring ASB, CRM, Feedback, or using the Generic module, making the right decision up front can save you time, budget, and effort later on.
🔍 Module Overview at a Glance
Module | Introduced in Version | What is it | Best For | Key Limitation |
Generic Cases | 16.3 | Workflow capability for managing non-contact-based processes | Organisation-specific process flows that don't fit in to a standard Cx wizard or have their own bespoke module | No ASB/Feedback-specific screens (e.g. legal, lessons learnt, costs, reviews ) |
CRM | 14.1 | Workflow for contact-centred processes | Contact centre requests, customer service centre type workflows | Same as above |
Feedback | 14.3 | Case and stage-based approach to complaints/compliments | Simple, linear complaints | Too rigid for complex workflows as it doesn't support the Task Path (flowchart). Most then look to Generic Cases |
ASB | 14.1 | Bespoke module for anti-social behaviour management | Full ASB workflows (complainants, legal, costs) | Rigid structure, not ideal outside ASB scope |
🧠 How They Work
Generic/CRM: Start with a case with a task path and then optionally add tasks manually.
Feedback: Uses sequential “stages” with embedded tasks (no paths).
ASB: Case holds complainant/perpetrator data and categories, with flow-based task assignment. Allows you to duplicate tasks if appropriate for contact associate types e.g Interview Complainant would be created for each Complainant
⚙️ Key Functionality Comparison
If I were to write down all the functionality this would be a very long document, but i've tried to highlight the key points and differences I think of when deciding what to use. It's also worth noting that even though something might not be natively available, you can always push the boundaries with features like Forms, Information Fields and Stored Procedures.
Case | Task | Case | Task | Case | Task | Case | Task | |
Case Creation |
|
|
|
|
|
|
|
|
Allow backdating of creation? | ❌ | - | ✅ | - | ✅ | - | ❌ | - |
Key Record (Entity) |
|
|
|
|
|
|
|
|
Link Case to multiple entity types? | ✅ | - | ✅ | - | ❌ | - | ✅ | - |
Supports 'Anonymous' Contact? | ❌ | - | ✅ | - | ✅ | ✅ | ❌ | - |
Link Task to multiple entity types? | - | ✅ | - | ✅ |
| ❌ | ✅ | - |
Task Creation |
|
|
|
|
|
|
|
|
Available Tasks (added manually by user) | ✅ | - | ✅ | - | ✅ | - | ✅ | - |
Automatic Tasks (not Task Path) | ❌ | - | ❌ | - | ❌ | - | ✅ | - |
Supports Task Path (introduced in v16.2, enhanced in 17.2HF1) | ✅ | - | ✅ | - | ✅ | - | ❌ | - |
Assignment |
|
|
|
|
|
|
|
|
Assign to User | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
Assign to Role | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
Auto Assigned to User | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | Inherits from case |
Auto Assigned to Role | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | Inherits from case |
Assign to Manager | ✅ | ✅ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ |
Auto Assigned to Manager | ✅ | ❌ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ |
Management |
|
|
|
|
|
|
|
|
Can Be Put On Hold | ✅ | - | ✅ | - | ✅ | - | ✅ | - |
Can Take Ownership | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ |
Tasks can be mandatory | - | ✅ | - | ✅ | - | ✅ | - | ✅ |
Forms as part of Task Path? | ✅ | - | ✅ | - | ✅ | - | ❌ | - |
Auto assign to Case Creator? | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ |
Case Owner Notification | ❌ | - | ✅ | - | ✅ | - | ✅ | - |
Automatic comms as part of path | ✅ | - | ✅ | - | ✅ | - | ❌ | - |
Supports delays (manual and conditional)? | ✅ | - | ✅ | - | ✅ | - | ❌ | - |
Auto closure after x days (or conditional)? | ✅ | - | ✅ | - | ✅ | - | ❌ | - |
Other |
|
|
|
|
|
|
|
|
Can Link Cases | ✅ | - | ✅ | - | ✅ | - | ✅ | - |
Supports scripts | ❌ | ❌ | ✅ | ✅ | ❌ | ❌ | ❌ | ❌ |
Notes | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
Information Fields | - | ✅ | - | ✅ | - | ✅ | - | ✅ |
Supports SLA (Targets) | ✅ | ✅ | ✅ | ✅ | ❌ | ✅ | ✅ | ✅ |
Can revise SLA Target? | ✅ | ✅ | ✅ | ✅ | ❌ | ✅ | ❌ | ❌ |
Escalation rules | ✅ | ✅ | ✅ | ✅ | ❌ | ✅ | ✅ | ✅ |
Allows attachments | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ |
User Defined page | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
Can Forms trigger case? | ✅ | - | ✅ | - | ✅ | - | ✅ | - |
Can Forms be done on Case? | ✅ | - | ✅ | - | ✅ | - | ✅ | - |
Can Forms be manually done on Task? | - | ❌ | - | ❌ | - | ❌ | - | ❌ |
Tasks can appear more than once in a case | ✅ | - | ✅ | - | ✅ | - | ❌ | - |
Security |
|
|
|
|
|
|
|
|
Case creation of type restricted by Role? | ✅ | - | ❌ | - | ❌ | - | ❌ | - |
Can be excluded from Portal (by Type) | ✅ | - | ✅ | - | ✅ | - | ✅ | - |
Can be excluded from Portal (individual cases) | ✅ | - | ✅ | - | ✅ | - | ✅ | - |
Manually set to Private to Owner | ✅ | - | ✅ | - | ✅ | - | ✅ | - |
Can be Managed by Owner only | - | ✅ | - | ✅ | - | ✅ | - | ❌ |
Feedback |
|
|
|
|
|
|
|
|
Multiple Stages | - | - | - | - | - | - | ✅ | - |
Close x days after stage completion | - | - | - | - | - | - | ✅ | - |
ASB |
|
|
|
|
|
|
|
|
Supports multiple concurrent Categories | - | - | - | - | ✅ | - | - | - |
Record Costs | ❌ | - | ❌ | - | ✅ | - | ✅ | - |
Lessons Learnt | ❌ | - | ❌ | - | ✅ | - | ✅ | - |
Incidents | ❌ | - | ❌ | - | ✅ | - | ❌ | - |
Reviews (Automated) | ❌ | - | ❌ | - | ✅ | - | ❌ | - |
Legal Action | ❌ | - | ❌ | - | ✅ | - | ❌ | - |
Key
✅It does it | - Its not applicable | ❌It doesn't do it |
🛠️ Other Modules Built on Case Framework
Civica Cx has also introduced various other licensable modules based on this same framework, take a look at the relevant release notes if you want to know more. I've not included the detail on these as they tend to be used by only a handful, and simply not relevant for most.
Home Buy – v15.3
Housing Options – v15.4
Homelessness – v16.3 (enhanced v18.11)
Estate Management – v17.1
Support – v16.4 (enhanced in 21.1)
💡 My Advice
If you’re:
If you're a smaller organisation (< 1500 properties), and want Complaints and aren't ferociously passionate about branching logic, I'd start with Feedback. Try it for a year, then move to Generic if you want more, don't start the other way round.
Building anything outside ASB start with Generic
Managing structured, contact-led requests? Use CRM
Needing to track ASB, stick with ASB
It's also important to avoid users rejecting the new processes because they're over complicated. Always start simple and get more complicated later.
👋 Need any advice ?
Need any pointers, give me a shout. Need all your cases building?....As politely as I can possibly say this, please find someone else! 😊)
Comments