Call purposes

Every outbound call belongs to a purpose. The purpose tells the assistant why it is calling, how to run the conversation, which tools it may use and which codes to record the outcome with. Purposes are edited on Outbound calls → Purposes and need Outbound calls in your plan.

Purpose fields

Field	Rule	Description
Key (anahtar)	starts with a lowercase letter; lowercase letters, digits, _; 2–40 characters	Used by integrations (e.g. sepet_kurtarma). Cannot be changed later
Name (ad)	at least 2 characters	Shown in the console and the button
Type (tur)	hizmet (service) or ticari (commercial)	See below
Goal (hedef)	up to 300 characters	The call’s goal, one sentence
Instructions (yonerge)	20–4000 characters	How the assistant talks on this call
Greeting (karsilama)	10–400 characters	The first sentence; validated in code
Enabled tools (araclar)	up to 30	Tools the assistant may use for this purpose
Outcome codes (sonuc_kodlari)	from a fixed dictionary	Common codes are always on; you pick purpose-specific ones. Outcome codes →
Coupon rule (kupon_kurali)	optional	Coupons →
İYS check (iys_kontrolu)	zorunlu (required) or gerekmez (not needed)	If not set, derived from the type: commercial → required, service → not needed
Topic tag	optional	Added to every completed call for this purpose
Active	—	No new request can use an inactive purpose (unknown_purpose)

Type: service and commercial

• Service (hizmet): orders, complaints, returns, technical support. Sales tools (cart, product suggestions) are always off; by default no İYS consent is needed. A coupon rule, if any, must have the purpose telafi (compensation).
• Commercial (ticari): sales and campaign calls (e.g. abandoned carts). By default the call does not start unless the customer has CALL consent in İYS. Sales tools are enabled only if both the request-time and current type are commercial. A coupon rule, if any, must have the purpose satis (sales). Commercial purposes are available when Carts is also on in your plan.

İYS and legal responsibility

The İYS check is a separate decision per purpose and belongs to the company admin; whoever starts the call (console user, button or API) cannot change it per request. If you turn off the İYS check on a commercial purpose, the console warns you: legal responsibility for those commercial calls lies with your company. The do-not-call list applies to every call regardless of the İYS setting.

Greeting rules

The greeting is validated before it is saved:

1. Only these placeholders: {ad} (first name), {urun} (product), {siparis_no} (order number), {asistan} (assistant name), {firma} (company).
2. It must identify the caller: the {firma} placeholder or your company name.
3. It must include a recording notice (e.g. “görüşmemiz kaydediliyor” — “this call is recorded”).
4. It must end with a question (e.g. “Şu an uygun musunuz?” — “Is now a good time?”).

Example:

Merhaba {ad}, ben {asistan}, {firma} adına arıyorum. {siparis_no} numaralı siparişinizle ilgili kısa bir konu var; görüşmemiz kalite için kaydediliyor. Şu an uygun musunuz?

The console Preview shows the greeting with sample values, including how it reads when there is no order or product.

The callback purpose

A purpose with the key geri_arama is special: automatic callbacks after a failed transfer and callback appointments the customer asks for during a call use it. If it is missing, the transfers page shows a warning. Callbacks →

Which assistant calls?

Chosen under Settings → Outbound calling → Assistant that makes outbound calls; if empty, your company’s first published assistant calls.