Outcome codes
When the call ends, the assistant records the result with an outcome code (sonuc_kodu) and a short note (sonuc). Codes come from a fixed dictionary: neither the assistant nor the console can write a code that isn’t in it. If the call ends without a code, the outcome is inferred automatically from the masked transcript (sonuc.kaynak: "otomatik"); even then only one of the purpose’s codes can be chosen, and the code stays empty if it can’t be determined.
Common codes (always on)
Section titled “Common codes (always on)”| Code | Meaning |
|---|---|
cozuldu | Resolved during the call |
talep_acildi | A request was opened |
geri_arama | The customer wants to be called at another time (appointment) |
musait_degil | The customer wasn’t available |
yanlis_numara | Wrong number |
aranmak_istemiyor | The customer doesn’t want to be called (the number goes on the do-not-call list) |
Purpose-specific codes
Section titled “Purpose-specific codes”Picked in the purpose editor.
| Group | Codes |
|---|---|
| Cart | satin_alacak (will buy), kupon_verildi (coupon given), fiyat_vazgecti (dropped over price), baska_yerden_aldi (bought elsewhere), ilgilenmiyor (not interested) |
| Complaint | sikayet_kaydedildi (complaint recorded), telafi_kabul (accepted compensation), memnun (satisfied), memnuniyetsiz (dissatisfied) |
| Return / order | bilgi_verildi (informed), islem_yapildi (action taken) |
| Technical | servis_yonlendirildi (sent to service), bilgi_toplandi (information collected) |
memnun and memnuniyetsiz require a satisfaction score from 1–5; the assistant cannot record them without asking for it.
Where you see the outcome
Section titled “Where you see the outcome”- The Outbound calls list and request detail (audit trail: each check step, its time and decision).
GET /api/v1/aramalar/{arama_id}→sonuc_kodu,sonuc. API →- The
arama.sonucwebhook event. Webhooks →
A call that ends with geri_arama doesn’t count towards repeat protection; the customer can be called again at the time they gave.
© 2026 Erusoft