---
title: "Claim communications"
description: "The emails a customer receives during a claim, when each one is sent and by whom, and how to put them in your own words."
---

Your customer hears about a claim through a small set of emails, each tied to a moment in the claim. Read this page to know what your customer will be told and when, and how to rewrite the wording in your own voice.

## Emails your customer receives

Every email carries the claim number in its subject, so a reply lands on the same claim.

| Email | Listed in the editor as | Sent when | Sent by |
|---|---|---|---|
| Acknowledgement | **We've got your claim** | The claim is filed, from the portal or from a confirmed email. It confirms receipt and promises nothing else. | Automatic, once per claim |
| Request for information | **We need something from you** | Review cannot go further without something only the customer can give (a clearer photograph, a missing detail, a product that does not match), or an adjudicator has a question of their own. One email lists everything outstanding. | A person |
| First reminder | **A first nudge** | Day 3 after the request, with items still outstanding | A person |
| Second reminder | **A second nudge, before we close** | Day 7. It names the date the claim will be closed if nothing arrives, and how long a reply will still reopen it. | A person |
| Closed for no reply | **Closed for now** | A person closes the claim because the customer has not replied. The claim closes as **Closed, no reply**. | A person |
| Approval | **Approved** | The claim is approved. The email names what the customer gets, for example a replacement or a repair. | A person |
| Settled | **Settled** | The replacement or repair has been delivered and the claim is marked fulfilled | A person |
| Decline | **Declined** | A person declines the claim and picks the reason. The wording for each reason is fixed. | A person, always |

Only the acknowledgement goes out by itself. Every other email is prepared as a draft on the claim, and a person presses **Send message**. One person can prepare a draft and another can send it.

Reminders count from the moment the request was actually sent. A reminder lists only what is still outstanding: if the customer has sent two of three items, it asks for one. If everything has arrived, there is nothing to send. The portal tells you when a reminder is due; a person decides to send it.

Sending a request for information marks the claim as waiting on the customer. Preparing the draft does not. See [How a claim moves](/claims/overview).

## When your customer replies

Customers reply to the address the email came from. The reply is matched by the claim number in the subject and added to the claim as a follow-up, and any attachments are kept as evidence on the claim. A reply on a claim closed for no reply, inside the window the customer was promised, reopens the same claim.

## Write the emails in your own words

Your organisation can rewrite any customer email except the decline. Until you do, your customers receive SureBright's wording.

<Steps>
  <Step title="Open the editor">
    In the Adjudicator Portal, open **Communication**. Only an org admin can change wording.
  </Step>
  <Step title="Pick an email">
    Choose one under **Messages**. Each is tagged **Your wording**, **SureBright's** or **Fixed**.
  </Step>
  <Step title="Edit the wording">
    Change the **Subject** and the **Message**. Both are needed. **Compare with SureBright's** shows what you have changed.
  </Step>
  <Step title="Check the preview">
    **Preview** shows the email as it would be sent, filled in with an example claim, along with any warnings about your text.
  </Step>
  <Step title="Save">
    Click **Save wording**. Every future email of that kind uses your wording. Emails already sent are unaffected.
  </Step>
</Steps>

To go back to SureBright's wording, click **Load the default** and then **Save wording**.

<Warning>
The decline cannot be rewritten by any organisation and is tagged **Fixed**. Its wording is set for each decline reason, and it is always sent by a person. You can read it in the editor.
</Warning>

### Insert claim details with merge fields

You edit wording, never facts. A merge field is a placeholder that is filled in from the claim when the email is sent, for example `{{customerName}}`.

- Each email has its own list of fields. The editor shows them beside the text and marks which are already in your wording. Click one to insert it.
- Every claim email offers `{{claimNumber}}`, `{{customerName}}` and `{{productName}}`.
- Anything that is a list or that differs from claim to claim comes as a ready-made block, for example the list of items still outstanding, or the sentence that differs between a replacement and a repair. Write around the block and it stays correct for every claim.
- There are no conditions, loops or formulas. You cannot save wording that uses a field the email does not have.
- Spaces inside the braces are fine: `{{ customerName }}` works. An optional detail that is missing leaves a gap, never the word "null".

### Go back to an earlier wording

Every save keeps the wording it replaced. The editor lists them under **What this used to say**, each with the time it was saved and who saved it. From there you can:

- **Edit this version** to load it back into the editor. Save to put it back in use.
- **Use this version** to put it back in use straight away.
- **Name this version** so you can find it again.
- **Remove this version** to take it off the list. The wording your customers were sent under it stays on record.

<Note>Early access. The **Communication** editor is in the Adjudicator Portal, which is enabled per organisation. Ask your SureBright contact. Once saved, your wording applies whichever team sends the email.</Note>

## Can your team be copied on claim emails

Claim emails go to the customer at the email address on the order, and the customer's replies are added to the claim. To follow a claim:

- Read it in the Adjudicator Portal, where every email sent and every reply is on the claim's **Timeline**. See [How a claim moves](/claims/overview#what-you-see-as-the-merchant).
- Without the portal, email [support@surebright.com](mailto:support@surebright.com) with the claim number and ask for an update.

If you would like a member of your customer service team copied on a customer's claim emails, ask your SureBright contact.

## What a customer email never contains

Each email can only use the claim details listed for it. A customer email never carries an assessment, a confidence score, an internal note, a staff member's name or the contract's money figures.

## Related

- [How a claim moves](/claims/overview): the stages behind each email.
- [Filing a claim](/claims/filing-a-claim): how a claim starts and what the customer is asked for.
- [Merchant adjudication](/claims/merchant-adjudication): who sends the emails for your organisation.
- [Adjudicator Portal](/claims/adjudicator-portal): where drafts are sent and wording is edited.
