Tsallaka zuwa abun ciki

Warwarewa ta Atomatik: Mitin da Ya Fi Gaskiya

Dalilin da ya sa ma'aunin farashin enterprise na Threada shi ne automated resolution — aikin da aka kammala ba tare da mutum ya karba ba — kuma dalilin da ya sa auna sakamako ya fi gaskiya fiye da auna sakonni ko kujeru.

billing • pricing • work-orchestration • outcomes

Kowane tsarin farashi yana yin da’awa game da inda daraja take fitowa. Farashin per-seat yana cewa daraja ita ce access. Farashin per-message ko per-token yana cewa daraja ita ce activity. Duka suna da saukin aunawa, amma duka suna iya ba da lada ga abin da ba daidai ba — seat da ya shiga amma bai warware komai ba har yanzu yana biya; integration mai yawan magana da bai taba rufe case ba har yanzu yana tara kudi.

Threada yana auna abu da ya fi wahalar wasa da shi kuma ya fi kusa da manufar aikin: automated resolution.

Abin da yake aunawa

Automated resolution shi ne WorkItem ko runtime outcome da aka kammala ba tare da human takeover ko amsar operator da hannu ba. Aikin ya shigo, tsarin ya kai shi ga sakamako mai karewa, kuma babu mutum da ya shiga ya gama shi. Wannan shi ne unit da muke rahotawa a billing da usage dashboards, kuma shi ne unit da enterprise meter yake kirgawa.

Ma’anar an sanya ta da tsauri. Idan operator ya karbi aiki ya amsa da hannu, wannan ba automated resolution ba ne — assisted work ne, kuma bai kamata a kirga shi kamar platform ta rufe shi ba. Meter yana motsi ne kawai lokacin da platform ta yi aikin da gaske.

Me ya sa sakamako shi ne abin gaskiya da za a caje

Pricing unit ya kamata ya daidaita da yadda customer yake fassara nasara. A governed operations, nasara ba “mutane sun yi amfani da tool” ba ce, ko “model ya samar da rubutu da yawa” ba. Nasara ita ce routine work ya kammala daidai, kuma exceptions na gaske ne kawai suka isa ga mutum. Dalilin samuwar product gaba daya shi ne ya automate routine kuma ya route cases masu wahala ga mutane.

Caji ta automated resolution yana sanya incentive dinmu a bangare daya da wannan burin:

  • Ana ba mu lada ne idan aiki ya rufe, ba idan kawai yana juyawa ba. Model da ya samar da drafts goma da babu wanda zai iya aiki da su ba ya samun komai; resolution daya da ya tsaya a review yana da daraja.
  • Customer zai iya yin lissafi na gaskiya. Cost per resolved item lamba ce da operations leader zai iya kwatanta da cikakken kudin warware wannan item da hannu. Babu translation layer tsakanin “abin da muke caji” da “abin da muka ce za mu rage maka.”
  • Yana kin vanity metrics. Ba za ka iya kara meter ta hanyar aika karin messages ko kara seats ba. Hanyar da lambar take karuwa ita ce idan karin aiki ya warware da gaske.

Metering na gaskiya yana bukatar kirgawa ta gaskiya

Meter ba zai fi kirgawarsa gaskiya ba. Alkawura biyu suna rike namu daidai.

Na farko, muna kirga outcomes, ba fata ba. Ana rubuta resolution lokacin da WorkItem ya kai completed terminal state ta governed path — tare da receipt dinsa cikakke. Proposal da ya fadi a connector, ko item da operator ya ceci da hannu, ba a zagaye shi cikin resolved column. Lifecycle states suna fili, kuma meter yana karanta su da gaskiya.

Na biyu, muna bayyana transition din a fili. A ciki, usage a tarihi ya taba dogaro da message caps yayin da platform ke girma. Muna bayyana cewa wadannan caps suna map zuwa automated-resolution meter, kuma muna rahoto resolutions a usage dashboards maimakon boye unit din a bayan proxy. Kiran ainihin unit da sunansa — da nuna maka shi — bangare ne na records-and-receipts posture da ke mulkin sauran product.

Abin da free tier yake fada game da model

Free tier yana da iyaka na automated resolutions 1,000 da knowledge assets 100 a kowane wata, tare da daily document caps da aka samo daga monthly limit. Siffar wannan cap kanta magana ce: free tier yana da karimci a resolutions saboda resolutions su ne abin da ya dace ka gwada. Mun fi so ka gano ko platform tana rufe aikinka, ba ko tana iya daukar yawan seats ba.

Bayan volume, plans ya kamata a karanta su a matsayin capability bundles — zurfin governance, approval da policy controls, automation scope, connector classes, da compliance posture — ba kawai manyan lambobi ba. Meter yana fada maka yawan aikin da aka yi. Plan yana fada maka yawan iko da isa da kake da shi yayin yin sa.

Auna outcomes ya fi auna messages wahala. Yana bukatar platform ta ayyana, ta bi sawu, kuma ta tsaya bayan abin da “resolved” yake nufi. Muna ganin wannan wahala ita ce manufar. Meter da za ka iya tattaunawa a matakin line item meter ne da yake girmama buyer — kuma automated resolution lamba ce da operations team za ta iya karewa.