Most of the work on a claim is correspondence: letters of complaint, client updates, DSAR chasers, escalation forms and payment reminders. Each one depends on where the claim has got to, and each one has to be on the file. LogiClaim sends them for you, from your templates and the live data on the claim.
Sent by the workflow
Each message is triggered by the claim’s status, so nobody has to remember to send it. When a complaint is submitted, the client gets an SMS telling them, with a link to track it in the client portal, and an email with their access code. Both appear in the claim history the moment they are sent.
A claim reaching a stage is the usual trigger. Messages can also be started by an API call, by activity in the client portal, by a bulk automation run or by a manual action from your team.
Stage by stage
- Sign-up. Sign-up messages by email and SMS as a new client comes on board, with access to the client portal.
- Complaint. Bespoke letters of complaint written from your templates and the claim data, and a client update once it is submitted. If the lender misses the deadline you set, chasers go out until it replies.
- Lender response. When the lender replies, the incoming automation reads it and the workflow sends what comes next, such as an update to the client.
- Escalation. FOS and FSCS documents when a complaint needs to go further, and follow-ups to clients and third parties.
- Payment. Payment chasers to clients when a payment is due.
Your wording, filled in from the claim
You set up personalised templates for letters, emails and SMS. Each message is filled in with the names, references and details held on the claim, so it is accurate without anyone retyping it, and the same template works for one claim or ten thousand. For PCP claims, LogiClaim comes with a pre-configured workflow and document templates you can adjust to your own wording.
Chasers that keep going
Once a message is sent, LogiClaim schedules the reminders and chasers that go with it. They run at the intervals you set and continue until a response is received or the task is completed. The claim status shows what is being waited on, such as a DSAR overdue or a letter of complaint response overdue, so an overdue response is chased without anyone keeping a list.
Manual when you need it
Automation does not stop your team working by hand. Anyone can create a document from a precedent template in one click, or schedule a chaser that appears in the right person’s task list when it is due. Detailed queries from a defendant, the Ombudsman or the FSCS can be handled personally with the claim history in front of you. Anything sent by hand is recorded on the claim file in the same way as an automated message.
One workflow, in both directions
Outgoing and incoming correspondence run on the same workflow. When a lender reply arrives, it is linked to the claim and categorised on your rules, and the workflow sends the next message. See how incoming correspondence works.
Want the right message sent at every stage?
A free demo walks through the messages at each stage, your templates and the chasers, and shows where every message is recorded on the claim.
More detail on the outgoing correspondence page.
Frequently asked questions
Email and SMS, and letters generated as documents wherever post is still needed. Messages can go out directly from LogiClaim or be triggered via API.
Yes. You set up personalised templates for letters, emails and SMS, and each message is filled in from the data on the claim. A pre-configured PCP workflow and document templates are there to start from.
Chasers continue until a response is received or the task is completed. You set the intervals.
Yes. Anyone can create a document from a precedent template in one click or schedule a manual chaser, which appears in the right person’s task list.