Skip to content
CoreSpeak

Repair requests are captured in full while your technicians are out.

In technical service, whoever would answer the phone is usually on site. CoreSpeak takes down the fault, collects what a visit needs in a fixed order and the job appears in your team's calendar.

From fault report to calendar

  1. 01

    Fault report

    Device, fault and any error code are taken; the code is read back to the caller to confirm it.

  2. 02

    Time window

    A convenient time window is agreed and confirmed with the customer.

  3. 03

    Calendar

    The job shows up in the dashboard's week view, on the right day and window.

Device / brand
Kombi
Fault
Sıcak su yok
Error code
F28
Area
Kadıköy
Time window
Per 10:00–12:00
Customer
Kerem Er
Phone
0505 ••• •• 63
Status
Service ticket created

Sample records with fictional names. Field values stay in Turkish, as the caller said them.

Weekly view

Service jobs appear in the dashboard's week view by day and time window, with the district on each job.

MonTueWedThuFriSatMorning 09–12
Air conAtaşehir
DishwasherAtaşehir
BoilerKadıköy
BoilerAtaşehir
Midday 12–15
BoilerKadıköy
Air conKadıköy
Afternoon 15–18
Washing machineÜsküdar
FridgeÜsküdar
Sample data.

What the assistant asks

The order is the same on every call, and no ticket is opened with details missing.

  1. 1Device type and brand
  2. 2Description of the fault
  3. 3Error code on the display, if any (read back to the caller to confirm)
  4. 4District
  5. 5A convenient time window
  6. 6Full name and phone number
  7. 7Summary and confirmation

Other frequent calls

“When is the technician coming?”
The assistant passes the question and the caller's details to your team as a note, and your team gets back to them.
“Is this covered by warranty?”
It only passes on the warranty information your business has defined; if unsure, it takes a note.
“How much will it cost?”
If a fee is defined it quotes it; otherwise it takes a note so your team can call back.

Try it with your own call scenario.