---
title: "Release 5.18.8"
description: "SLA starts again for tickets created from chats and emails, the similar contacts search finds cards that share a phone number, and Fast Line Pro knowledge base exports and imports can be run back to back."
---

# Release 5.18.8

Release 5.18.8 is built on version 5.18.7 and includes all of its changes. They are described in the [release 5.18.7 notes](/en/releases/5.18.7.md).

Below is only what is new in 5.18.8: SLA starts again for tickets created from a chat or an email, the similar contacts search shows cards it used to miss, and Fast Line Pro knowledge base exports and imports are no longer blocked after the first job.

## Please note

- **SLA is not started automatically for tickets that already exist.** The fix applies to new tickets. For open tickets created from a chat or an email earlier, you can start SLA with the **"Update SLA"** button in the ticket card. The ConnectiveOne team can run a bulk start for the whole instance on request.
- **Manual search by a short part of a phone number returns nothing.** If you enter fewer than seven digits of a phone number, the list of similar contacts stays empty until the seventh digit is entered.
- **An export error may take a while to disappear.** If a knowledge base export or import failed with "Export error" shortly before the update, the error disappears on its own no later than 24 hours after the update.

## Tickets

**Fixed**

- **SLA starts again for tickets created from chats and emails.** Since version 5.16.0, tickets created by a bot scenario (converting a chat to a ticket) or from an incoming email did not get the "First response time" and "Time to close" SLA metrics.
  - **Before:** instead of timers, the ticket card showed "Configure SLA for this ticket topic", although SLA was configured. Tickets created manually by an operator worked correctly.
  - **Now:** SLA starts for all new tickets as before.
  - For tickets created before the update, see "Please note".

## Client card

**Fixed**

- **The similar contacts search finds cards linked through a shared phone number.** A client's call and email could end up in two cards with the same number: a phone card (no email) and an email card (the same phone and an email).
  - **Before:** "Search similar contacts" and the similar contacts preview found the phone card from the email card, but found nothing from the phone card.
  - **Now:** the search works in both directions. Contacts found through a similar card are shown with match marks ("phone", "email", "username"), and a contact found only by its channel link also appears in the results.
  - In manual search, the match marks also light up for the cards found by the entered value. A search by a phone fragment shorter than seven digits returns nothing.
  - The system still does not merge existing duplicate cards on its own: this is done manually.

## Fast Line Pro

**Fixed**

- **Knowledge base exports and imports can be run back to back.** One job per user at a time still applies.
  - **Before:** after the first export or import, all further attempts by the same user within a day failed with "Export error". Applying an import did not work at all under these conditions.
  - **Now:** after a job finishes, the next one can be started right away, and applying an import works.
  - If the knowledge base runs on an older version of the Fast Line Pro service, after a chunk text is changed the semantic search may keep finding it by the old wording and not by the new one for some time. Full-text and keyword search find the new text. A manual chunk edit in the interface behaves the same way.

## Related documentation

- [Release 5.18.7 notes](/en/releases/5.18.7.md)
- [View ticket SLA metrics](/en/operatorline/how-to/view-ticket-sla.md)
- [Search and merge similar contacts](/en/broadcastusers/how-to/search-and-merge-similar-contacts.md)
- [Export and import knowledge base chunks](/en/fastlinepro/how-to/export-import-kb-chunks.md)