Citizen Case Management
Intake, triage, routing and resolution across departments.
- Multi-channel case intake
- SLA and escalation rules
- Cross-department handoffs
People need to know whether their request has been received and what happens next. We help public-service teams organise intake, case ownership, and status updates in Salesforce.
Fragmented case records and unclear request status make public service delivery harder to coordinate.
Map service journeys, case routing, permission requirements, and reporting before configuring the platform.
Reduce duplicate handling and manual status reporting while reviewing hosting and compliance requirements for your jurisdiction. Compare the current effort and running costs before deciding whether the change is worth making.
Discuss Your Requirements
Public sector projects fail on process, not technology. We spend the design effort on how a case actually moves between departments.
Intake, triage, routing and resolution across departments.
Portals where people can apply, track and resolve without phoning.
Configuration built for the scrutiny public bodies face.
End-to-end permit lifecycles with inspection and renewal.
Connect to the systems public bodies cannot simply replace.
The statutory and operational reporting you are required to publish.
We agree the first deliverable, review it with your team, and use that feedback to guide the next stage.
We map the service journey and every department that touches a case.
Case model, security architecture and compliance controls agreed up front.
Workflows and portals built iteratively with frontline staff.
Accessibility, security and audit review before anything goes live.
Ongoing support as policy and statutory requirements change.
Most engagements start with a short discovery call rather than a full proposal. RASPSYS LLP will review your compliance obligations and tell you what is realistically achievable.
We deliver for clients across the UK, US, UAE, Canada, and Australia - with teams that work in your time zone.
Audit trail and access control designed before configuration begins.
Public services must work for everyone; we test to WCAG, not assume it.
Delivery across the UK, US, UAE, Canada and Australia, each with its own regime.
The questions we are asked most often about Government Cloud.
It runs on infrastructure physically and logically isolated from the commercial cloud, with compliance accreditations public bodies require - FedRAMP in the US, and equivalent frameworks elsewhere. Functionally it is Salesforce; the difference is where it runs, who can operate it, and what has been certified.
Yes, and we treat it as a build requirement rather than a pre-launch audit. Public sector services generally have statutory accessibility duties. We test with keyboard navigation and screen readers during development, because retrofitting accessibility after a build costs several times more.
Usually, though this is where timelines move. Public bodies often run systems that predate modern APIs. We assess integration feasibility during discovery - sometimes through middleware, sometimes through scheduled file exchange where no API exists - before committing to a plan.
Retention policies are configured per record type, with automated disposal where the schedule allows it. For freedom of information requests, the audit trail and search make it practical to locate and extract what is in scope rather than trawling manually.
End-to-end Salesforce strategy, implementation and managed services.
You should be able to see what has been agreed, what is in progress, and what needs your input. Here is how we organise that work.
Have a workflow or backlog you would like us to look at? Tell us about it in an initial call.
Map one public-service request from submission to the final decision or response.
Identify which records need to move between systems, who owns them, and what should happen when an update fails.
Test the handoffs, status messages, and role-based access with the teams responsible for that service.
Show users how to complete their regular tasks and give the people maintaining the system a usable handover.
Keep unresolved requests and later ideas in a shared backlog, with a named owner and a reason for each priority.
Start with a piece of work you can assess on its own. We can then discuss a project, phased delivery, or ongoing support to fit the remaining workload.
Map one public-service request from submission to the final decision or response. Keep later additions in a separate backlog so the first phase stays manageable.
Your proposal should say what is included, what your team needs to provide, and what costs extra. Include licences and ongoing support in the comparison.
Agree who reviews the work and how they will check it. Record scope changes and confirm the handover before closing the project.
Tell us where the work gets stuck and what you have already tried. Bring an example if you can; it gives us a useful place to start.
Request a Scoped ProposalBook a free 30-minute call with a RASPSYS consultant.
We will map the service journey and where citizens currently get stuck.