Everything that records what happened on a case, and who was involved.
The Note action lets someone add a note to a task, which is logged automatically for the rest of the team to refer back to. Add it from the Forms & Actions tab by dragging Note into the status.
The On Hold action puts a task on hold in one click and captures the reason in the box provided. Drag On Hold into the status, add any explanatory content, and set who can see it. As with every other action, visibility rules can keep it hidden until it is relevant.
Every task carries a log of what has happened to it: status changes, answers saved, notes added, emails sent, documents generated. Entries can be added manually as well, so a phone call or a decision taken offline still lands in the same place as everything else.
The log is the reason a case can answer the question that matters in a complaint or an audit, which is not what the current status is but how it got there.
A case relationship describes how a person relates to a particular case rather than to the system as a whole. The same user might be the case owner on one case, an expert on another and a client contact on a third.
Relationships are tied to user types, which is what makes note and form visibility workable. Setting a note to be visible to a relationship means the right people see it on the cases where they hold that relationship, and nobody has to maintain a list by hand.
Flags mark tasks for reasons that do not fit a status, and can be searched with has one of, has all of, and does not have. RAG status shows whether a task is inside its deadline, approaching it or past it, and can be driven automatically by amber and red alert events.
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.
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.