- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-05-2025 05:52 PM
Hi all,
I am trying to determine my options for the scenario below.
Scenario
We have a new case type extended from sn_customerservice_case. Within this case type we have the need to retrieve additional information from other parties when required etc. We would need to ask some specific questions to receive the data we need and capture on the case. The resources being asked for information are not intended to have a fulfiller role.
We have a playbook that triggers off this case and have looked at using a questionaire but it seems a bit limited in what it can do (i.e. make a question mandatory dynamically). We also do not want to give agent access to the users who are to provide this information.
Last piece of information about the scenario is that we have a customised workspace for users to work on these cases and the request for information should be visible in there.
Questions
- What options are there for handling this type of scenario?
Steps taken already
- Have copied our existing work to a sandbox environment for experimentation
- Googling lead me to case tasks (however not sure if this is the best option).
Thanks in advance.
Solved! Go to Solution.
- Labels:
-
Customer Service Management
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-27-2025 04:42 PM
What we did in this situation:
The CSTASK table is not extendable so we decided to put our tasks there. The tasks have some information defined on them by the parent but no custom fields have been added to the table.
Instead to handle triggers of a playbook off the cstask we used values of the parent case Service Offering and parent case starts with 'ALPCS'.
In this way we get a sub task off our custom case type without having to replicate the cstask table but can still control how the playbook triggers.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-27-2025 04:42 PM
What we did in this situation:
The CSTASK table is not extendable so we decided to put our tasks there. The tasks have some information defined on them by the parent but no custom fields have been added to the table.
Instead to handle triggers of a playbook off the cstask we used values of the parent case Service Offering and parent case starts with 'ALPCS'.
In this way we get a sub task off our custom case type without having to replicate the cstask table but can still control how the playbook triggers.
