Documentation
Eight sections covering how the platform is organised, how to build a workflow, and what SwiftCase can be told to do on its own. Written for the person configuring the system, not the person buying it.
How SwiftCase organises work, how to create your first task, and how to find it again.
Building and changing the processes your work runs through, without writing code.
Capturing the data your process depends on, and reusing it everywhere else.
Clients, team members, roles, passwords, two-factor authentication and the audit trail.
Everything that records what happened on a case, and who was involved.
Templates that fill themselves in, and the two ways to send email from SwiftCase.
What happens on its own when a task reaches a status, and how to control the timing.
Building your own reports, reading the management information, and telling everyone something.
The pages here describe SwiftCase as it ships. Because every installation is configured to a different process, customers also get documentation specific to their own workflows, statuses and roles through the platform itself.
If you are evaluating SwiftCase, book a demo and we will walk you through the platform against your process rather than ours.
Documentation covers how the platform works. These cover what to do with it.
Our support team can help with configuration questions, troubleshooting, and best practice for your particular use case.