OpsIQ Nyaraka za

ya kujenga, kuendeleza na Urefu wa urefu OpsIQ.

Hii ni orodha kamili kwa ajili ya OpsIQ Kuanzisha bidhaa, kukimbia msaada, configure AI, kusimamia CRM, kufunga widget, kujenga viunganisho, wito REST API, kupokea webhooks, programu za soko la mfuko, na kufanya kazi kupelekwa kwa kujitegemea.

Mwongozo wa WatejaMwongozo wa UsimamiziMwongozo wa DeveloperCRM kumbukumbu ya kumbukumbuKuunganisha SDKya ya APIKujitegemea
Ufafanuzi

Maelezo ya Kitabu hiki

Kila kitu kila OpsIQ Je, katika sehemu moja: jinsi kila screen kazi, jinsi ya kuunganisha mifumo yako mwenyewe, na jinsi ya kujenga juu yake. Kuanza mahali popote, sehemu kufuata utaratibu sawa kama sidebar admin.

Ufafanuzi
Ramani ya ramaniKitabu cha mkono kinaandaliwa karibu na bidhaa ya OpsIQ, kufuatia agizo sawa kama sidebar ya admin.Ramani ya ramaniOpsIQ Bidhaa ya bidhaaAUDIENCEWafanyakazi waya kununuaWaendelezajiRUNWasimamizi waMaisha ya kazi ya VIEWMatumizi ya OpsIQBidhaa za Screens na workflowsPamoja naKuongeza kasi OpsIQMawasiliano ya simu, APIs na kwa milomo yaPamoja naKazi ya Opera OpsIQUsalama, Kuingiliana na KuhamishwaPamoja naMarejeo ya kumbukumbuKamati ya, API Mikataba ya Mtandao wa YahookPamoja na1CHOOSE AUDIENCEWafanyakazi au developer2FOLLOW THE UISehemu ya kioo OpsIQ3USE SOURCE TRUTHHali ya maisha inatokana na ujenzi
Kitabu cha mkono kinaandaliwa karibu na bidhaa ya OpsIQ, kufuatia agizo sawa kama sidebar ya admin.
Mwongozo wa Mafunzo ya Portal

Tumia msimamizi aliyejitolea na mwongozo wa msanidi programu kwa usanifu wa Portal, kurasa, vipengele, preview, Kituo cha Msaada, utambulisho, SCIM, kutolewa kwa serikali, upanuzi, uhamiaji na vyeti.

Fungua Mwongozo wa Studio ya Portal

Nini cha kufanya hapa

Kuendesha bidhaa

Kila screen katika admin: analytics, kuishi chat, tiketi,CRM, msingi wa ujuzi, Ujasusi wa Tovuti, matangazo na akaunti ya mteja. Nini kila ukurasa hufanya, idadi inamaanisha nini, na nini cha kufanya wakati wanaonekana vibaya.

Kuunganisha mifumo yako

widget tovuti, mailboxes barua pepe, inbound na outbound webhooks, na maktaba ya kontakt kwa majukwaa kama Shopify, WooCommerce, WHMCS Zendesk, Stripe, Slack na Gmail.

Kujenga mwenyewe yako mwenyewe

Wajenzi wa Connector kwa viunganisho vya msimbo, Hatua & Triggers ikiwa ungependa kutumia viunganisho wakati wote, na REST API na kila hatua, upeo na msimbo wa kosa.

Fanya kazi hiyo

Majukumu na ruhusa, usalama, cron, uchunguzi, backups, na wote mwenyeji na kujitegemea kupelekwa.

Ambapo kuanza

1
Kama wewe ni kuendesha OpsIQ Siku ya

Soma sehemu za skrini katika utaratibu wa sidebar. Kila moja inafungua na ukurasa ni kwa ajili ya, hivyo unaweza kuacha haraka kama una nini unahitaji.

2
Kama wewe ni kuongoza

Ongeza Mipangilio, Usalama, Utambuzi, Cron na Uzalishaji. Hizi ni sehemu zinazoamua ikiwa kila kitu kingine kinaendelea kufanya kazi.

3
Kama wewe ni kujenga uhusiano

Kuanza katika Connectors, kisha Connector Builder, kisha REST API Soma kwa makini, na utaona kila kitu. OpsIQ Unaweza kuzungumza na mfumo mwingine.

💡
Vitu viwili vinabadilika kile unachokiona. Ruhusa za kujificha kurasa za jukumu lako haziwezi kufungua, kwa hivyo sehemu iliyoelezwa hapa inaweza kukosa kutoka kwenye ubao wako. Waulize msimamizi kuangalia nafasi yako. Na viunganisho hubeba lebo ya ukomavu wa Uzalishaji, Beta, Preview au Template; ujenzi unaoendesha na kontakt yake inaonyesha ni mamlaka ambayo unayo, sio ukurasa huu.
Kuanza hapa

Nini maana ya nini OpsIQ Kufanya kwa ajili ya biashara yako

OpsIQ Ni jukwaa kamili la uendeshaji wa biashara ya AI. Inabadilisha analytics yako, mazungumzo ya moja kwa moja, Helpdesk, CRM, zana za SEO, middleware ya ushirikiano, na jukwaa la msanidi programu na admin mmoja wa umoja ambapo kila chombo kinashiriki mazingira sawa ya mteja. 8-12 Bidhaa za SaaS, wewe kufunga OpsIQ Fanya kila kitu kwa kutumia skrini moja.

Jukwaa la
OpsIQ Jukwaa la umojaUbongo wa AI kuu umeunganishwa na kuzungumza moja kwa moja, CRM, tiketi, Ushauri wa Site, matangazo na analytics.Kuishi chatKukuzaCRM ya juuMtandao wa IntelTiketi za tiketiUchambuziOpsIQya BRAIN1ONE WORKSPACEKila kitu katika admin moja2SHARED BRAINMazingira ya Wateja3ANYWHEREWingu au mwenyeji binafsi
OpsIQ Ni jukwaa moja na mazingira ya mteja mmoja, kila chombo kinalisha, na hutumiwa na, ubongo huo wa AI.

Kila kitu kila OpsIQ · Kwa maelezo zaidi

Uchambuzi wa tovuti na akili ya mgeni

Ufuatiliaji wa Wageni wa Muda

Kila ukurasa mzigo, bonyeza, kitabu, na tukio urambazaji ni alitekwa katika muda halisi. Angalia ambaye ni kwenye tovuti yako hivi sasa, ni kurasa gani wao ni viewing, muda gani wanatumia, na wapi wanatoka, wote bila cookies tatu.

Ziara ya logi na vikao

Historia kamili ya kila mgeni na kifaa, kivinjari, mfumo wa uendeshaji, nchi, jiji, rejea, vigezo vya UTM, ukurasa wa kutua, na azimio la utambulisho.

Rekodi ya kikao

Uchezaji wa mtindo wa muda wa vikao vya wageni vilivyochukuliwa. Angalia hasa watumiaji walifanya nini: harakati za panya, clicks, vitabu, mabadiliko ya ukurasa, na uunda mwingiliano. Tumia kutambua masuala ya UX, kuelewa pointi za kushuka, na kuthibitisha mtiririko wa uongofu.

Chakula cha kuishi

mkondo wa wakati halisi ya shughuli za wageni kama inavyotokea. Angalia maoni ya ukurasa, kuanza kwa gumzo, nyaraka zilizowasilishwa na ishara za nia kusasishwa kila sekunde chache. Chuja kwa nchi, kifaa au mwongozo ili kuzingatia sehemu maalum za trafiki.

Orodha ya Juu

Kurasa zilizowekwa kwa ziara, wakati wa ushiriki, kiwango cha bounce, uongofu, na shughuli za msaada. Tambua maudhui yako ya juu na kurasa ambazo zinahitaji kuboresha.

Geo intelligence ya

Nchi, mji, na maeneo ya kuvunjika kwa ramani. Kifaa na usambazaji wa kivinjari, uchambuzi wa chanzo cha trafiki, ufuatiliaji wa injini ya utafutaji, na ufahamu wa kupenya soko.

Intiv ya funnel

Kufuatilia ishara za nia ya wageni (kutembelea ukurasa wa kwanza, kurudi mara kwa mara, mifumo ya kuvinjari nyaraka, na ushirikiano wa msaada) kutambua wageni ambao wanaweza kununua, churn, au wanahitaji msaada.

Jaribio la B

Tumia vipimo vya mgawanyiko kwenye tovuti yako moja kwa moja kutoka kwa OpsIQ. Unda anuwai, kuweka ugawaji wa trafiki, kufafanua malengo ya uongofu, na kupima umuhimu wa takwimu. Hakuna chombo cha upimaji wa nje kinachohitajika.

JavaScript Ufuatiliaji wa makosa

Kukamata mteja upande wa JavaScript makosa kutoka tovuti yako moja kwa moja. Angalia ujumbe wa hitilafu, dalili za stack, vivinjari vilivyoathirika, hesabu za mzunguko, na kurasa ambazo zinawasababisha. masuala ya mbele ya Debug bila ufuatiliaji tofauti wa kosa.

Matukio ya

Kila tukio lililofuatiliwa (maoni ya ukurasa, matukio ya desturi, mwingiliano wa mazungumzo, maoni ya fomu, ununuzi) katika logi inayotafuta, kuchuja na metadata kamili.

Mauzo na ubadilishaji

Kufuatilia maagizo, mapato, marejesho, upyaji wa usajili, na kusababisha uongofu kwa vyanzo vya trafiki, kampeni, na safari za wageni. dashibodi za Mapato na kulinganisha kipindi na uchambuzi wa mwenendo.

Viongozi wa

Wageni wa hali ya juu wanaotambuliwa na mwelekeo wa tabia. Score inaongoza kwa kuzingatia ziara za ukurasa, wakati kwenye tovuti, mzunguko wa kurudi, ushirikiano wa msaada, na ishara za desturi. Feed inaongoza moja kwa moja kwenye bomba la CRM.

Uchambuzi wa Tovuti (SEO na uchambuzi wa maudhui)

Tovuti ya kutambaa

kutambaa moja kwa moja ya tovuti yako nzima kugundua kurasa, kuchunguza viungo kuvunjwa, kupata missing meta tags, kuangalia picha maandishi alt, kuthibitisha canonical URLs, na ramani muundo wa tovuti yako. Ratiba crawls kuendesha kila siku, wiki, au juu ya mahitaji.

Ukaguzi wa SEO

Uchambuzi kamili wa kiufundi: alama za kasi ya ukurasa, mwitikio wa simu, Core Web Vitals, SSL hali ya cheti, minyororo ya kuelekeza tena, kugundua maudhui duplicate, uchambuzi wa kina wa kutambaa, na uthibitisho wa data uliowekwa.

Ukaguzi wa Maudhui

Tathmini kila ukurasa kwa ubora wa maudhui, hesabu ya neno, alama ya usomaji, wiani wa maneno, muundo wa kichwa, uwiano wa ndani / nje wa kiungo, na freshness. Kutambua yaliyomo nyembamba, kurasa za duplicate, na mapungufu ya maudhui.

Utafutaji wa AI-powered

Tafuta tu kwenye maudhui yako yote ya tovuti. Waulize maswali ya lugha ya asili kuhusu maudhui yako na kupata majibu ya ukubwa wa AI na marejeo ya ukurasa wa chanzo.

Ufuatiliaji wa SERP

Kufuatilia rankings yako search injini kwa maneno muhimu lengo katika Google na injini nyingine. kufuatilia mabadiliko ya nafasi baada ya muda, kulinganisha dhidi ya washindani, na kuona ambayo kurasa cheo kwa ajili ya masharti ambayo.

Utafiti wa Keyword

Kugundua fursa za neno la msingi kulingana na maudhui yako, uchambuzi wa mshindani, na data ya kiasi cha utafutaji. Pata mapendekezo kwa mada mpya ya maudhui, tofauti za mkia mrefu, na malengo ya ufanisi wa yaliyomo.

Uchambuzi wa Backlink

Kufuatilia maelezo yako ya kiungo cha inbound. Angalia maeneo ambayo yanaunganisha na wewe, kufuatilia viungo vipya na vilivyopotea, kuchambua usambazaji wa maandishi ya nanga, na kutambua fursa za kujenga kiungo.

Mtandao wa SEO

Kwa biashara na maeneo ya kimwili: kuona mwonekano wako wa utafutaji wa ndani katika gridi ya kijiografia. Angalia jinsi rankings yako zinatofautiana kwa eneo, umbali kutoka kwa biashara yako, na nia ya kutafuta.

Maelezo ya Biashara ya Google Sync

Unganisha wasifu wako wa biashara ya Google OpsIQ Maoni ya Sync, machapisho, Q & A, picha, na maelezo ya biashara. Kusimamia GBP yako orodha kutoka ndani OpsIQ Jibu kwa maoni, kuchapisha machapisho, na kufuatilia ufahamu.

Taarifa zilizoandaliwa

Ripoti za SEO zilizoendeshwa na uchambuzi zinazalishwa kwenye ratiba yako (kila siku, kila wiki, kila mwezi). Ripoti ni pamoja na mabadiliko ya cheo, mwenendo wa trafiki, masuala ya kiufundi yaliyopatikana, na utendaji wa maudhui. pato la White-label linapatikana kwa mashirika.

Msaada wa AI-powered

Wateja wa chat

Semalt Anajibu Maswali ya Wateja kwenye Tovuti Yako 24/7 Kutumia msingi wako wa ujuzi, data ya jukwaa iliyounganishwa (mipangilio, akaunti, usajili), na mafunzo ya desturi huchochea. Inasaidia watoa AI wengi: Claude (Anthropic· GPT-4o (kwa Kiingereza:OpenAI), Gemini (Google), na Grok (xAI).

Msaidizi wa msaidizi

Copilot ya AI ndani ya jopo lako la admin ambayo husaidia kuandika majibu ya tiketi, rasimu ya mawasiliano ya wateja, kuchambua mwenendo wa msaada, kuangalia data ya mteja katika majukwaa yaliyounganishwa, na kutekeleza vitendo kupitia mfumo wa kontakt.

Ujuzi wa msingi

AI ni msingi katika makala yako ya msingi wa maarifa, viingilio vya FAQ, nyaraka za bidhaa, na data ya jukwaa iliyounganishwa. Haijibu kutoka kwa habari yako halisi ya biashara au inazidi wakati haijulikani.

Auto-mkono kwa binadamu

Wakati AI haiwezi kutatua swali, inagundua kuchanganyikiwa, au mteja anauliza mwanadamu, inapeana moja kwa moja kwa timu yako na muktadha kamili wa mazungumzo. kushuka kwa wakati / kurudi kwa AI.

Mafunzo ya haraka

Andika maelekezo tofauti yanayochochea AI inayoshughulikia wateja na usimamizi wa AI. sauti ya kudhibiti, mipaka, sheria za kuongeza, mada zilizozuiliwa, na tabia maalum ya biashara.

Historia na ukaguzi

Kila mazungumzo ya AI ni watumiaji na maelezo kamili ya ombi / majibu, matumizi ya ishara, ufuatiliaji wa gharama, mtoa huduma aliyetumiwa, na toleo la mfano. Tathmini mazungumzo ili kutambua mapungufu ya mafunzo na kuboresha usahihi wa AI.

Ufahamu wa

Uchambuzi wa moja kwa moja wa mifumo ya mazungumzo ya AI. Tazama maswali ya kawaida, viwango vya azimio, mzunguko wa handoff, kuridhika kwa wateja na mada, na maeneo ambayo AI inahitaji mafunzo bora.

Mahali pa kazi ya AI-config

Kila tovuti iliyounganishwa / nafasi ya kazi inaweza kutumia mtoa huduma wake wa AI, mfano, joto, bajeti ya ishara, na mafunzo. Kampuni ya SaaS inaweza kutumia Claude kwa bidhaa kuu na GPT-4o kwa chapa ya sekondari.

Kuundwa kwa AI na BYOK

Mbili: Kuwa makini katika mambo yako.API Tumia kichwa chako mwenyewe (na kisha chagua moja) OpenAI/Anthropic Google/XAI / Google API muhimu kwa udhibiti kamili juu ya uteuzi wa mfano na gharama). Wote ni darasa la kwanza, kila kipengele hufanya kazi na hali yoyote.

Bajeti ya Serikali na Udhibiti wa Gharama

Weka bajeti za kila mwezi, mipaka ya mazungumzo kwa kila mtu, na tahadhari za usawa wa chini. Fuatilia matumizi kwa mtoa huduma, kwa nafasi ya kazi, na kwa mazungumzo. kuzuia gharama za kukimbia na dari ngumu.

tiketi za ndege na Helpdesk

Mfumo wa tiketi ya Taifa

Msaada kamili na idara, vipaumbele (chini / kati / juu / haraka), hali, ufuatiliaji wa SLA, maelezo ya ndani, majibu ya wateja, vifungo vya faili, na mazungumzo yaliyofungwa. Hakuna msaada wa nje unaohitajika.

Tatu na kwa auto-reply

AI moja kwa moja huharibu tiketi zinazoingia na idara na kipaumbele. Wezesha auto-reply kwa idara salama. Miradi ya AI na hutuma majibu baada ya kuchelewa kwa kusanidi (default: 2 dakika) ili wanadamu waweze kuingilia kati kwanza.

Email ya Intifent

Unganisha sanduku la barua (Gmail, IMAP, au mtoa huduma maalum) ili kuunda tiketi moja kwa moja kutoka kwa barua pepe zinazoingia. Majibu ya barua pepe za taarifa ya tiketi update thread ya tiketi.

tiketi ya ndege embed

Embed portal ya tiketi inayoendana na wateja kwenye tovuti yako. Wateja wanaweza kuwasilisha tiketi, kuona historia yao, kujibu tiketi za kufungua, na kuangalia hali, wote alama kwa kubuni yako.

tiketi ya ndege

Kuchanganya duplicate tiketi katika thread moja. Tiketi iliyoboreshwa kuonyesha [Merged] juu ya mstari wa mada. Historia yote ya mazungumzo imehifadhiwa katika tiketi ya kuishi.

Kurudi kwa AI

Baada ya wakala wa kibinadamu kuchukua tiketi, tumia "Rudi kwa AI" ili kuruhusu AI irejeshe moja kwa moja kwenye tiketi hiyo. Inafaa wakati sehemu inayofaa ya binadamu imetatuliwa lakini mteja ana maswali ya kufuatilia ambayo AI inaweza kushughulikia.

Ndani ya Box Copilot

Usimamizi wa tiketi ya AI-uliosaidiwa kutoka kwa mtazamo wa inbox. copilot inapendekeza majibu, inafupisha historia ya mazungumzo, inapendekeza kazi za kipaumbele / utoaji, na inaweza kutekeleza vitendo kwenye majukwaa yaliyounganishwa.

Chat na msaada wa wakati halisi

Chat ya inbox

Kuzungumza kwa wateja wa wakati halisi ilisimamiwa kutoka kwenye kikasha cha umoja. Angalia mazungumzo yote ya kazi, utambulisho wa mteja, historia ya mazungumzo, na mapendekezo ya AI. mawakala wengi wanaweza kushirikiana kwenye mazungumzo.

Kanuni za mazungumzo ya bure

Ujumbe wa mazungumzo ya Trigger kulingana na tabia ya mgeni: wakati kwenye ukurasa, maalum URL alitembelea, kitabu kina, kurudi ziara kuhesabu, nia ya kutoka, au matukio desturi. mfano: kuonyesha ujumbe wa msaada baada ya 60 Sehemu ya pili kwenye ukurasa wa bei.

Chat ya kirafiki

Ya customizable chat widget iliyoingia kwenye tovuti yako. Inasaidia AI chat, kuishi wakala kuzungumza, tiketi ya kuwasilisha, maarifa msingi search, na mgeni utambulisho.

Uchunguzi wa CSAT

Kukusanya wateja kuridhika ratings baada ya mazungumzo na mwingiliano tiketi. kubuni tafiti na maswali yako mwenyewe, mizani rating, na kufuatilia prompts. Matokeo kulisha katika utendaji wa timu na AI ufahamu.

Utafiti wa barua pepe baada yachat

Baada ya mazungumzo kumalizika, wageni wenye barua pepe inayojulikana wanaweza kupokea barua moja yenye jina na muhtasari wa AI wa kile kilichoshughulikiwa na bonyeza "Je, ni rahisi?" Ndiyo / Hapana. Mara baada ya thread, saini viungo vya matumizi moja, kila mtu anayetuma watumiaji, na matokeo yanabaki kwenye ukurasa wa maoni kama ishara yake mwenyewe kando ya nyota za kuzungumza.

Maoni ya mtumiaji loop

Kila kitu cha maoni ambacho kinabeba mtu kinawaonyesha: jina, barua pepe, bonyeza-kupitia safari yao kamili ya wateja na mawasiliano ya CRM, na majibu ya moja kwa moja au majibu ya AI-draft yaliyowekwa katika historia yao halisi.

Kuandika kwa AI

Kutenga AI kuandika msaidizi kwa ajili ya kutunga rasimu barua pepe, tiketi majibu, matangazo, na mawasiliano ya wateja. Matumizi yake mwenyewe haraka (si ubongo chat) kwa ajili wa kitaalamu biashara kuandika.

CRM ya kwanza

Kituo cha CRM

screen moja kuonyesha nzima CRM hali yako: bomba thamani, mpango kasi, kazi ujao, katika hatari mikataba, shughuli wakala, na AI mapendekezo.

Mawasiliano na makampuni

Kusimamia mawasiliano ya wateja na maelezo kamili: jina, barua pepe, simu, kampuni, vitambulisho, hatua ya mzunguko wa maisha, historia ya mazungumzo, historia za tiketi, historia yako ya ununuzi, na mashamba ya desturi.

Mipango na Bodi ya Bomba

Bodi ya mpango wa Kanban-style na hatua za customizable. Drag mikataba kati ya hatua, maadili yaliyowekwa, kuwapa wamiliki, kufuatilia tarehe za karibu, na kuona thamani ya bomba katika kila hatua. mabomba mengi yanasaidiwa.

Kocha wa

AI inachambua kila mpango na hutoa kufundisha: ishara za hatari (mnyama wa utulivu, mshindani aliyetajwa, wasiwasi wa bajeti), mapendekezo ya hatua inayofuata, kushinda uwezekano, na kupendekeza muda wa kufuatilia.

Utabiri na taarifa

Utabiri wa mapato kulingana na data ya bomba, viwango vya kihistoria vya karibu, na ripoti za mpango. Ripoti ni pamoja na bomba kwa hatua, na mmiliki, na chanzo, viwango cha uongofu, ukubwa wa wastani wa mpango, na urefu wa mzunguko wa mauzo.

Wakala wa Kutarajia (SDR)

Kutazamia kwa AI-powered ambayo hutambulisha wateja wenye uwezo kutoka data yako ya mgeni, ishara za kuongoza, na shughuli za jukwaa lililounganishwa. Inapendekeza malengo ya kufikia, inaandaa ujumbe wa awali, na alama za ubora wa kuongoza.

kufuatilia-up mfululizo

Utaratibu wa ufuatiliaji wa hatua mbalimbali: barua pepe, kusubiri, barua pepe , majibu ya kuangalia, kuenea. Kufafanua mlolongo kwa ajili ya mwongozo mpya, mikataba iliyokwama, baada ya ununuzi wa hundi-ins, na kampeni za upya.

Maisha ya rafu na uhifadhi

Kufuatilia hatua za mzunguko wa maisha ya wateja (kuongoza, matarajio, mteja, churned) na mabadiliko ya kiotomatiki. Wakala wa uhifadhi anafuatilia ishara za churn na anaonyesha kuingilia kati.

Wakala wa Data

Wakala wa AI ambao unaendelea kusafisha na kuimarisha data yako ya CRM: anwani za deduplicates, hujaza maeneo yasiyoonekana, inathibitisha barua pepe, huweka majina ya kampuni, na bendera zinashikilia rekodi.

Kujenga CRM yangu

Asili lugha CRM Configuration: kuwaambia AI nini mchakato wako mauzo inaonekana kama na hujenga hatua yako bomba, mashamba desturi, templates mpango, na sheria automatisering.

CRM Afya ya kuangalia

Ukaguzi wa moja kwa moja wa ubora wako wa data ya CRM: anwani za duplicate, mikataba bila hatua zifuatazo, mabomba ya stale, habari za mawasiliano iliyopotea, na ukamilifu wa data.

Imani ya Uinjilishaji

Udhibiti wa mamlaka ya ngazi tatu kwa kila wakala wa CRM AI: Autopilot (AI hufanya kazi kwa kujitegemea), Copilot(AI inapendekeza, kupitishwa kwa binadamu), na Mwongozo (AI inaangalia tu). Weka piga kwa wakala, kwa aina ya hatua, na kwa kizingiti cha thamani ya mpango.

Wafanyakazi wanne wa

CRM anaendesha mawakala wa AI maalum wanne: Steward (ubora wa data), SDR (kutabiri, Kuzidisha (kuzuia wakati), na mchambuzi (ripoti na ufahamu). Kila wakala ana mazingira yake ya kupiga simu ya Trust.

Kuunganisha na Ushirikiano

Mawasiliano ya awali-Convent

Kamili-kwa-kutumia connectors kwa Shopify, WooCommerce, BigCommerce, Magento 2, PrestaShop, OpenCart, osCommerce, WordPress, WHMCS, Zendesk, Stripe, Amazon SES, Postmark, Resend, SendGrid, Mailgun, Gmail IMAP, Slack, na Google Biashara Profile. Kila connector huleta jukwaa maalum AI vitendo, maarifa, na data sync.

Mjenzi wa Kiunganishi

Kujenga viunganisho vya desturi kwa jukwaa lolote, hakuna msimbo, AI-kusaidiwa, au msimbo kamili. mjenzi anaunga mkono REST na GraphQL APIs, OAuth mtiririko wa msimbo wa idhini, webhook auto-registration na Stripe na mipango rahisi ya saini, pagination (offset, ukurasa, mshale, na kichwa cha kiungo), orodha / ugaidi mabadiliko, mazingira ya hatua nyingi, na ufungaji wa soko.

Kuunganishwa kwa Linking

ConnectorBuilderAI husaidia kujenga viunganisho: kuelezea kile unachotaka na inaonyesha vitendo, anaandika washughulikiaji wa ombi, na ramani API majibu. Hushughulikia uthibitishaji, utangulizi, na utunzaji wa makosa moja kwa moja.

OAuth Kuunganisha kwa yoyote ya kontakt

Huduma ya In-app OAuth mtiririko wa idhini ambayo inafanya kazi na kontakt yoyote. msaada wa PKCE, usimamizi wa hali ya tovuti-scoped, refreshors moja kwa moja ishara.OAuth Vigezo na Masharti ya OpsIQ Inashughulikia mtiririko.

Uwezo wa usafiri (platform wide extension)

Waunganishaji hawana tu kuongeza vitendo vya jukwaa. Wanaweza nguvu vipengele vya msingi kupitia uwezo "buses".Mkononi anatangaza uwezo (calendar, utajiri, esign katika CRM; orodha ya ndani, cheo_data katika Tovuti Intelligence; web_analytics katika Analytics; malipo_mtoaji katika Malipo; barua pepe_sy katika Mailbox;_ mkutano wa video katika Comms) na kutekeleza njia yake ndogo iliyowekwa; OpsIQ Inagundua kupitia Uwezo wa Usajili na waya ndani ya UI, Wateja 360 Wakati wa muda, na vitendo vya AI. Waunganishaji kadhaa wanaweza kutoa uwezo sawa na hakuna lock-katika. Angalia viunganisho / PLATFORM_CONNECTORS.md.

Kuwekwa kabla ya vs soko tier

Waunganishaji wanaishi katika moja ya tiers mbili. viunganisho vya kabla (viungo /) ni usajili wa kazi nje ya sanduku, huhifadhiwa kwa kumbukumbu tu isiyo na msingi na mtoa huduma aliyetumiwa zaidi kwa uwezo (kwa mfano Kalenda ya Google, Gmail, Profaili ya Biashara ya Google). Viunganisho vya Soko (mchanganyiko wa soko_connectors/) hugunduliwa lakini inert mpaka imewekwa, kwa mfano Microsoft 365 Kalenda, Outlook, DocuSign, Stripe, GA4, SerpApi, Zoom. Kila daraja linaunda orodha ya soko ili UI na AI inaweza kusababisha "kusanidi kutoka sokoni" (kuongeza-kuweka) wakati uwezo hauna mtoa huduma tayari, kamwe kifungo kilichovunjika.

Biashara ya Masoko

Kuwasilisha yako ya kontakt kwa ajili ya OpsIQ Picha zote na Wizara ya Mambo ya Ndani ya Nchi.json ya maarifa.json Kazi ya Recipes.json, na nyaraka zilizosainiwa. Soko la soko linaunga mkono viunganisho vya bure na vilivyolipwa na bili ya rasilimali nyingi.

Kuunganisha

Waunganisho wote ni cryptographically saini kwa ajili ya uthibitisho wa uadilifu. Signing ni checked wakati wa kufunga. Tumia chombo cha kujiuzulu_all_connectors ili kusaini tena baada ya sasisho.

SmartLookup

Declarative fuzzy-matching mfumo kwa ajili ya vitendo kontakt. kufafanua sheria kuangaliaup na OpsIQ mechi maswali user kwa vyombo jukwaa kutumia fuzzyScore na smartRank algorithms. mfano: find_country( "germ") mechi Ujerumani na 88.9% kujiamini.

mikataba ya utekelezaji

Mkuu waOpsIQ APIKujiandikisha kwa kila kujiandikishaJSONOperesheni kama hatua inayojulikana. Tumia meta.hatua kwa mikataba ya jumla ya kuishi na kamili; vifurushi vya kontakt vinatangaza vitendo vyao vya muuzaji kupitia ActionExecutor umoja.

Maelekezo ya Kuunganisha

Maelekezo ya kazi yaliyojengwa kabla ambayo yanachanganya vitendo vingi vya kontakt katika kazi za kawaida za biashara. mfano: "Wakati utaratibu mpya unakuja kwenye Shopify, kuunda tiketi, update CRM, na tuma arifa ya Slack."

Maarifa ya sync

Waunganishaji hutangaza mada ya ujuzi ambayo inaingiliana na msingi wa maarifa ya AI. Makala maalum za msaada wa Jukwaa, miongozo ya kuanzisha, na hatua za kutatua shida zinapatikana moja kwa moja kwa AI bila kuingia kwa maarifa ya mwongozo.

Programu ya Developer

ya ya API

Moja ya majina JSON API Kusimamia kila mtumishi aliyesajiliwa JSON Operesheni hiyo, pamoja naAPI Uthibitishaji wa muhimu, kutengwa kwa nafasi ya kazi, mawanda, kupunguza kiwango, idempotent anaandika, OpenAPI, na mkusanyiko wa Postman uliozalishwa.

Webhooks

Nje ya mtandao kwa ajili ya matukio yote makubwa: maagizo, ankara, usajili, tiketi, chats, inaongoza, usajili wa mtumiaji, na kutelekezwa gari. utoaji Async kupitia foleni ya kazi, reofftry maonyesho, ulinzi SSRF, na auto-disable baada ya kushindwa kwa mfululizo 15

Mtandao wa Yahoo

Kila webhook iliyo nje imesainiwa na HMAC-SHA256. kuthibitisha saini kwenye mwisho wako wa kupokea ili kuhakikisha uhalali wa wavuti. tukio la kuaminika_id kwa usindikaji wa idempotent.

Widget ya SDK

JavaScript SDK kwa ajili ya kufuatilia widget na azimio utambulisho, desturi tukio ufuatiliaji, programu chat kudhibiti, na ukurasa maalum Configuration. kufunga maelekezo kwa React, Vue, Next.js, WordPress, Shopify Kwa hiyo, tuli HTML.

Plugins na SDK

SDKs ya upande wa seva na Plugins kwa mifumo ya kawaida. WordPress Plugin ya mwenyeji, WHMCS Moduli, na Maktaba ya Ushirikiano wa PHP / Node.js.

Matukio ya matukio API

Push matukio ya desturi katika OpsIQ kutoka nyuma yako: ununuzi, ishara, matumizi ya kipengele, makosa, au tukio lolote la biashara. Matukio yanaonekana katika ratiba ya wageni na kulisha katika uchambuzi na mazingira ya AI.

Waigizaji wa filamu za Kibongo

Kujenga workflows ya automatiska inayotokana na matukio: tiketi mpya, kuzungumza kuanza, mgeni kutambuliwa, hatua ya mpango iliyopita, au tukio la desturi. Triggers kutekeleza vitendo vya kontakt, kutuma webhooks, rekodi za update, au kuwajulisha timu yako.

API Ujenzi wa jengo

Maoni API na webhook mjenzi ndani ya admin. Configure pointi mwisho, maombi ya mtihani, kukagua majibu, na integrations debug bila kuondoka OpsIQ.

Timu na Utawala

Udhibiti wa Upatikanaji wa Msingi

Majukumu matatu: Mmiliki (upatikanaji kamili, bili, eneo la hatari), Msimamizi Kamili (miradi yote isipokuwa kulipa na eneo la Hatari), na Wakala ( idara zilizopewa tu, hakuna ufikiaji wa mipangilio). Kurasa zote nyeti zinakabiliwa na jukumu.

Timu ya utendaji wa dashibodi

Mmiliki na dashibodi kamili ya Admin-tu kuonyesha nyakati za azimio, usambazaji wa mzigo wa kazi, kushughulikia kina, kuvunjika kwa channel, uchambuzi wa mwenendo, kufuata SLA, CSAT na wakala, viwango vya kufungua tena, rollups za timu, na masaa yenye shughuli nyingi. Imesasishwa wakati halisi.

Usimamizi wa uwepo na ufuatiliaji wa mtandaoni

Muda halisi ambao-ni-online widget katika admin urambazaji. Heartbeat makao uwepo kutambua (60 ya pili, 300-Kuongeza kasi, baada ya kujifungua 120 Angalia ni nani mmiliki wa wavuti kwa sasa na kwenye kurasa gani.

Mipangilio ya nafasi za kazi

Kila tovuti iliyounganishwa (nafasi ya kazi) inaweza kuwa na usanidi wake wa AI, mipangilio ya kontakt, idara za tiketi, chapa, na sheria za uendeshaji. defaults za Global zinaenda kwenye nafasi za kazi ambazo hazizidi.

Usimamizi wa tovuti nyingi

Kusimamia tovuti nyingi kutoka kwa admin moja ya OpsIQ. Kila tovuti ina ufuatiliaji wake mwenyewe, data ya mgeni, na usanidi.

Mfumo wa template ya barua pepe

Vidokezo vya barua pepe vinavyoendeshwa kwa mawasiliano yote ya automatiska: arifa za tiketi, nakala za mazungumzo, barua pepe za kuwakaribisha, mipangilio ya nenosiri, na tahadhari za mfumo. Edit HTML templates kuishi preview, chips variable ({{customer_name}}, {{ticket_id}}), na udhibiti wa jumla.

Uagizaji na usafirishaji

Kuagiza mawasiliano, tiketi na makala maarifa kutoka CSV/JSON Data ya mgeni wa nje, ripoti za uchambuzi, na kumbukumbu za CRM.Uhamiaji wa data kwa uhamiaji kati ya mifumo.

Usalama, utekelezaji na shughuli

Biashara ya Enterprise Enterprise SSO

OIDC (OpenID Connect) ishara moja na muda wote: ugunduzi, idhini, wito, uthibitisho wa saini ya JWKS, userinfo, usajili wa kikoa, utoaji wa JIT, na walinzi wa hali. SAML msaada wa usanidi.

GDPR Ufuatiliaji wa data

Kujengwa katika DSAR (Data Subject Access Ombi) utunzaji: kuuza nje na kufuta data ya wateja katika mifumo yote. Data ngazi ya mawasiliano erasure kufunika vikao, tiketi, chats, kumbukumbu CRM, na magogo barua pepe. idhini usimamizi na sera za uhifadhi.

IP Kuzuia na ulinzi wa nguvu za kikatili

Block maalum IPs au inatofautiana kutoka kupata tovuti yako au admin. moja kwa moja kufungwa baada ya configurable kushindwa kuingia majaribio. Kushindwa kuingia kumbukumbu na IP, timestamp, na wakala mtumiaji.

Viongozi wa HSTS na Usalama

HTTP Strict Usafiri Usalama, ruhusa-polisy headers, na salama cookie Configuration. Kupelekwa binafsi inaweza kuongeza viongozi wa CSP kupitia usanidi seva.

Mtandao wa wavuti wa nje

Ulinzi wa SSRF huzuia webhooks za kibinafsi / data IP Utoaji wa Async unazuia mwisho wa polepole kuzuia programu yako. Auto-disable baada ya kujifungua 15 Kushindwa kwa mfululizo huzuia taka za rasilimali kwenye mwisho wa mwisho.

Nafasi ya Kazi ya Kutengwa

Strict data kutengwa kati ya nafasi za kazi. Wageni, tiketi, mazungumzo, kumbukumbu CRM, na mazungumzo AI ni mawanda kwa workspace yao. kuvuja data Cross-nafasi ni kuzuiwa katika tabaka swala.

Usimamizi wa Mzunguko wa Billing

Msaada kwa ajili ya kila mwezi, robo mwaka, nusu-mwaka, kila mwaka, kila baada ya miaka miwili, na maisha billing mzunguko. Fedha normalization kwa njia za multi-fedha. FX ubadilishaji juu ya malipo kupokea kwa ajili sahihi mapato ripoti.

Cron na mipango ya automatisering

Mfumo wa cron uliojengwa kwa kazi zilizopangwa: kizazi cha ripoti, kusafisha data, upyaji wa usajili, sasisho za mafunzo ya AI, syncs za kontaktries za unganisho, na retries ya mtandao. uchunguzi wa afya na viashiria vya onyo.

Sera za uhifadhi wa data

Kufafanua jinsi vikao vya muda mrefu wa wageni, nakala za mazungumzo ya AI, historia ya mazungumzo ya akili, na kumbukumbu za tukio zinahifadhiwa. Kusafisha moja kwa moja data ya umri ili kusimamia uhifadhi na kuzingatia sera za kuhifadhi.

Maambukizi na afya

Dashibodi ya afya ya mfumo inayoonyesha hali ya cron, uunganisho wa database, hali ya mtoa huduma wa AI, afya ya kontakt, viwango vya utoaji wa wavuti, na matumizi ya kuhifadhi. Maonyo kwa masuala ya usanidi na vikwazo vya utendaji.

Nani ambaye ni nani ambaye OpsIQ Ni kwa kuwa

Biashara ya E-commerce

Maduka ya Stores

Weka kila mgeni kutoka kutua kununua. Hebu AI jibu "wapi ni amri yangu?" kwa kutumia kuishi Shopify/WooCommerce/ BigCommerce data. Kusimamia tiketi za msaada na AI auto-reply. kuendesha bomba la mpango kwa jumla na B2B inaongoza. Mapato ya mapato kwa vyanzo vya trafiki na kampeni. Kufuatilia kutelekezwa kwa gari na kazi ya kupona.

SaaS na makampuni ya programu

SaaS

Kufuatilia ishara za jaribio na kupitishwa kwa kipengele na replay ya kikao. Track ambayo kurasa za nyaraka zinabadilisha. Msaada wa Automate na AI msingi katika yako API Docs. Kusimamia mapato ya usajili na mikataba ya upanuzi katika CRM.Kuunganisha jukwaa lako la kulipa (Stripe, WHMCS) kwa kufuatilia MRR halisi wakati. Tumia wakala wa maisha ya CRM ili kugundua na kuzuia churn.

Wafanyakazi wa kujitegemea na wafanyakazi wa kujitolea

Shirika la

Kutoa analytics nyeupe-label na bandari za msaada kwa wateja. Track inaongoza katika maeneo mengi ya mteja kutoka admin mmoja. Tumia bomba la CRM kusimamia matarajio na mradi husababisha. Kujenga viunganisho vya desturi kwa majukwaa ya mteja kutumia Mjenzi wa Connector. Kuzalisha ripoti za SEO zilizo na Site Intelligence.

Hosting na Miundombinu

Kukaribisha

Chini WHMCS ushirikiano na 80+ AI hatua kwa ajili ya lookup ili, usimamizi wa huduma, DNS, na provisioning. Auto-kujibu maswali ya kawaida hosting kutumia makala maarifa msingi. Track server hali ukurasa ushirikiano. Kusimamia tiketi msaada wa kiufundi na AI triage. Matumizi billing mzunguko ngazi kwa ajili ya kila mwezi kupitia maisha mipango hosting.

Kusaidia biashara nzito

Msaada wa msaada

Deflect 40-70% ya maswali ya kurudia na mazungumzo ya AI yaliyojengwa katika msingi wako wa ujuzi. tiketi za njia kwa idara ya kulia na AI triage. Kufuatilia utendaji wa timu na nyakati za azimio, kufuata SLA, na CSAT na wakala. Tumia AI kuandika kwa ajili ya kuandika rasimu ya majibu ya kitaaluma.

Timu za masoko na SEO

Masoko ya masoko

Suite kamili ya Ujasusi wa Tovuti: kutambaa, ukaguzi wa kiufundi wa SEO, uchambuzi wa maudhui, ufuatiliaji wa cheo cha SERP, utafiti wa maneno, ufuatiliaji na gridi ya ndani ya SEO. usimamizi wa Wasifu wa Biashara ya Google. Ripoti za maandishi nyeupe-label kwa wateja. upimaji wa A / B umejengwa katika widget ya kufuatilia. Kampeni ya mchango katika njia zote.

Wachezaji wa timu ndogo na wachezaji

Mwanzo wa Startups

Kuanza na tu kufuatilia na kuzungumza, bure kuongeza. Kisha kuongeza tiketi wakati kupata msaada kiasi. kurejea kwenye CRM wakati wewe kuanza kuuza. OpsIQ kutoka kwa mtu mmoja hadi mwingine kufanya kila kitu 50 Timu ya shughuli za mtu na RBAC, idara, na ufuatiliaji wa utendaji wa haraka.

Biashara na Multi-brand

Kampuni

Biashara ya Enterprise Enterprise SSO na OIDC kwa uthibitishaji wa kati. Kutengwa kwa nafasi nyingi za kazi kwa bidhaa tofauti au migawanyiko.Ushirikiano wa AI wa Per-workspace na watoa huduma tofauti na mifano.Maendeleo ya kontakt na usambazaji wa soko. GDPR Utekelezaji wa sera, na sera za uhifadhi data.

Nini maana ya nini OpsIQ Badilisha

Google Analytics+ Hotjar + Plausible

Analytics kamili ya tovuti na ufuatiliaji wa mgeni, replay kikao, rankings ukurasa, akili ya geo, funnels nia, uongofu, matukio, majaribio A / B, na kufuatilia makosa ya JS, wote wa faragha-kirafiki, wote katika jukwaa moja.

Intercom + Drift + Tidio ya Tidio

AI-powered wateja kuzungumza na maarifa grounding, multi-kutoa msaada AI, auto-handoff kwa binadamu, sheria proactive chat, historia ya mazungumzo, CSAT tafiti, na tiketi uumbaji kutoka chat.

Zendesk + Freshdesk + Help Scout

Mfumo wa tiketi ya asili na idara, vipaumbele, SLA, AI triage, auto-reply na kuchelewa kupangiliwa, kuingizwa kwa barua pepe, tiketi ya kuingia, kuunganisha tiketi, copilot inbox, na Kurudi kwa uwezo wa AI.

HubSpot + Pipedrive + Salesforce

AI-kwanza CRM na mawakala wa nne maalumu AI (Steward, SDR, Retention, Mchambuzi), Trust Dial udhibiti wa uhuru, bodi ya bomba, kufundisha mpango, utabiri, mlolongo, usimamizi wa mzunguko wa maisha, na lugha ya asili CRM Configuration.

Ahrefs + SEMrush + Moz

Ujasusi wa tovuti na kutambaa kwa automatiska, ukaguzi wa kiufundi wa SEO, uchambuzi wa maudhui, utafutaji wa AI, ufuatiliaji wa cheo cha SERP, utafiti wa maneno ya msingi, uchambuzi ya backlink, gridi ya ndani ya SEO, na ripoti za maandishi nyeupe.

Zapier + Kufanya + Custom Media

Kuunganisha SDK Pamoja na 25+ viunganisho vya kabla ya kujengwa, Connector Builder (hakuna-code / AI-assisted / full-code), OAuth mtiririko, webhook auto-registration, katalogi kubwa ya kontakt hatua ufafanuzi kwamba kuwa executable tu wakati kiunganishi husika ni imewekwa, kuwezeshwa, configured na kuthibitishwa, SmartLookup, soko, na saini paket.

Meneja wa Akaunti ya Google Business Profile

Full GBP kontakt: usimamizi wa ukaguzi, kuchapisha baada ya, usimamizi wa Q & A, upakiaji wa picha, maelezo ya biashara, ufuatiliaji wa ufahamu, na majibu ya tathmini ya AI-powered, yote kutoka ndani OpsIQ.

Vifaa vya template ya barua pepe

Vidokezo vya barua pepe vinavyoendeshwa na usajili na mhariri wa kuona, hakiki ya kuishi, chips za kutofautiana, udhibiti wa mpangilio wa kimataifa, na usanidi wa kila tukio kwa mawasiliano yote ya automatiska.

Usimamizi wa Timu ya Dashibodi

Utendaji wa timu iliyojengwa: nyakati za azimio, mzigo wa kazi, kufuata kwa SLA, CSAT na wakala, viwango vya kufunguliwa tena, masaa ya shughuli nyingi, ufuatiliaji wa uwepo wa wakati halisi, na kuvunjika kwa sehemu.

GDPR Vifaa vya Ufuatiliaji

Asili ya Native DSAR kushughulikia, kufuta data katika mifumo yote, usimamizi wa idhini, sera za uhifadhi, na njia za ukaguzi, zilizojengwa kwenye jukwaa, hazikufungwa.

Vitabu viwili

Kulipwa kwa kupelekwa

OpsIQ Inaendesha miundombinu iliyosimamiwa. Operesheni ya Bidhaa ni sawa; miundombinu, sasisho na salama zinashughulikiwa na mwendeshaji wa mwenyeji. Kitabu hiki cha mkononi kina nyaraka za hati OpsIQ Muda wa kukimbia badala ya masoko au akaunti ya kibiashara hutiririka.

Mfumo wa kujitegemea

Ufungaji wa OpsIQ kwenye seva yako mwenyewe kwa udhibiti kamili juu ya data, chapa, sasisho, na ushirikiano.Inahitaji PHP 8.4+, MySQL 5.7+ au ya MariaDB 10.3+, HTTPS, na zaidi ya hayo OpsIQ Umoja wa Ulaya - Msaada WHMCS Kuunganisha kama moduli ya addon. uhuru kamili wa data.

Kupendekeza kwa ajili ya kusoma

1
Mwanzo wa haraka

Fuata maagizo haya 30- dakika kuanzisha mwongozo wa kupata kufuatilia, kuzungumza, na AI ya msingi kufanya kazi kwenye tovuti yako.

2
Dashibodi na analytics

Jifunze jinsi ya kusoma data yako ya mgeni, kuanzisha replay kikao, kutambua inaongoza, na kuelewa mwelekeo wa trafiki.

3
Tovuti ya Intelligence

Tumia kutambaa kwako kwa SEO kwanza, angalia afya yako ya kiufundi, na uanzisha ufuatiliaji wa cheo cha SERP kwa maneno yako muhimu.

4
Tiketi na msaada

Kuanzisha idara, usanidi auto-reply na AI, kuunganisha ingestion ya barua pepe, na kutoa mafunzo kwa AI yako kushughulikia maswali ya kawaida.

5
CRM

Kuandaa mawasiliano, kujenga bomba yako, configure mawakala AI, kuweka ngazi ya Trust Dial, na basi AI kocha mikataba yako.

6
Kuunganisha na zana za developer

Kuunganisha jukwaa lako la e-biashara / kuwezesha, kujenga viunganisho vya desturi, kuanzisha webhooks, na kuunganisha kupitia REST API.

💡
Mpya ya OpsIQ Kuanza na Quick Start mwongozo hapa chini. Unaweza kuwa na kufuatilia na msingi AI chat mbio katika chini 30 dakika moja.
Kuanza hapa

Mwanzo wa haraka 30 Dakika ya dakika

Fuata hatua hizi ili kupata OpsIQ kukimbia. Kila hatua hujenga kwenye moja ya awali. Mwishoni, utakuwa na ufuatiliaji wa mgeni, mazungumzo ya AI, na msaada wa tiketi ya msingi.

Kuundwa
Orodha ya haraka ya kuanzaOrodha ya usanidi wa uongozi inayoonyesha kufunga widget, kuunganisha jukwaa, mafunzo ya AI, timu ya kukaribisha na kuishi, na 60 asilimia ya maendeleo ya sekta hiyo.Kupata kuanzasetupKuweka OpsIQ Wizi wa widgetIMEFANYIKAKuunganisha jukwaa (WHMCS, Shopify)IMEFANYIKAKufundisha AI yako kwenye maudhui yakoIMEFANYIKAKuajiri timu yakoAngalia na uishi maisha yaMaendeleo ya3 Kwa upande wa 5 · 60%1STEP 1Kusanya widget2STEP 2Kuunganisha na Treni3STEP 3Kujiandaa na kwenda kuishi
Njia ya dakika ya 30: kufunga widget, kuunganisha jukwaa, treni AI yako, alika timu, kisha nenda kuishi.

Kwa kuwa 30 Dakika ya kuweka

1
Kuhamisha leseni yako

Ingiza msimbo wako wa leseni katika sanduku OpsIQ Nenda Mipangilio, ingiza ufunguo wa leseni inayotolewa kwa ufungaji huu, na bonyeza Activate. Unapaswa kuona beji ya kijani "Active".

2
Weka utambulisho wako wa biashara

Nenda Mipangilio na kujaza jina lako la biashara, sekta, timezone, sarafu ya default, na masaa ya msaada. Habari hii hutumiwa na AI wakati wa kujibu maswali ya wateja na kwa uchambuzi wa ripoti za ufahamu wa eneo la wakati.

3
Chagua mtoa huduma wa AI

Nenda kwa usanidi wa AI na uchague mtoa huduma wako: Claude (Anthropic· GPT-4o (kwa Kiingereza:OpenAI), Gemini (Google), au Grok (xAI) kuingia kwako. API Muhimu ikiwa unatumia ufunguo wako mwenyewe, au tumia AI iliyosimamiwa ikiwa inapatikana kwenye mpango wako. bonyeza "Uunganisho wa jaribio" ili kuthibitisha.

4
Kuweka widget ya kufuatilia

Go to Connected Sites, copy the tracking snippet, and paste it before the closing </body> tag on your website. Visit your site in a private browser, then check the Live Feed in OpsIQ. You should see yourself as a visitor within 15 seconds.

5
Kuunganisha jukwaa yako

Ikiwa unatumia Shopify, WooCommerce, WHMCS, au jukwaa lingine linaloungwa mkono, nenda kwa Waunganishaji, pata jukwaa lako, ingiza sifa za kuingia, na bonyeza Connection Test. Hii inatoa ufikiaji wa AI ili data, maelezo ya wateja, na muktadha wa usaidizi.

6
Kuajiri timu yako

Nenda kwa Timu, bonyeza Kualika, ingiza barua pepe zao na jukumu (Owner, Full Admin, au Wakala). Mawakala wanaweza tu kupata idara unazowapa. Wamiliki na Wasimamizi Kamili kuona kila kitu.

njia ya haraka iwezekanavyo.5 Dakika ya muda)

Hatua ya hatua 1· Kuundwa kwa widget

Nakili snippet kutoka maeneo yaliyounganishwa na kuiweka kwenye tovuti yako. Hii inakupa kufuatilia mara moja.

Hatua ya hatua 2· Kuwawezesha watu

Nenda kwa Configuration AI, kuchagua mtoa huduma, kuingia ufunguo wako, na kuokoa. AI chat sasa ni kazi kwenye tovuti yako.

Kufanya hivyo

Sasa una ufuatiliaji wa mgeni na mazungumzo ya AI. Unaweza kuongeza tiketi, CRM, na viunganisho baadaye.

Siku ya Siku 2Fanya kuwa na manufaa

Kuongeza ujuzi

Nenda kwenye msingi wa ujuzi na kuongeza 5-10 Makala kuhusu maswali yako ya kawaida. AI hutumia haya kujibu wateja kwa usahihi.

Kujenga idara

Nenda kwenye tiketi na uunda angalau idara za 2 (kwa mfano, "Soko" na "Kusaidia").

Andika haraka yako

Nenda kwenye Mafunzo ya AI na kuandika AI ya Wateja ambayo inaelezea biashara yako, sauti, na sheria za kuongeza.

Jaribu mazungumzo

Fungua tovuti yako katika kivinjari cha kibinafsi na kuzungumza na AI kama mteja. Angalia kwamba majibu ni sahihi na sauti ni sawa.

Wiki ya wiki 1Kujenga operesheni yako

Kuunganisha email

Weka sanduku la barua (Gmail, IMAP, au kontakt ya mtoa huduma) kwa hivyo barua pepe za wateja zinaunda tiketi moja kwa moja.

Kujiandaa kwa ajili ya auto-reply

Kuwezesha tiketi kwa ajili ya huduma salama. kuweka 2Kuchelewa kwa dakika ili binadamu aweze kuingilia kati kwanza.

Uchambuzi wa analytics

Angalia Dashibodi ya kila siku. Angalia hesabu ya wageni, kiwango cha bounce, kurasa za juu, na mauzo ikiwa ufuatiliaji umeunganishwa.

Kuanza CRM yako

Fungua CRM na kuruhusu OpsIQ Ingiza anwani kutoka kwenye majukwaa yako yaliyounganishwa. Tathmini bodi ya bomba.

Mwezi wa mwezi 1: Optimiza ya

Historia ya AI

Angalia historia ya AI kila wiki. Tafuta majibu mabaya, maswali yaliyokosa, na fursa za kuongeza maarifa.

Kuongeza Kanuni za Uendeshaji

Unda kanuni: ikiwa mgeni yuko kwenye ukurasa wa bei kwa ajili ya 60+ sekunde, kuonyesha ujumbe chat kuuliza kama wanahitaji msaada.

Kujenga uhusiano wa kontakt

Ikiwa unatumia jukwaa ambalo halina kontakt iliyojengwa, tumia Mjenzi wa Kuunganisha ili kuunda moja.

Kuundwa kwa Webhooks

Unganisha OpsIQ kwenye zana zako za ndani kwa kutumia webhooks ya outbound kwa tiketi, kuzungumza, na matukio ya mauzo.

Ninawezaje kupakua faili na kutumia tu?+

Ndio, mtoa huduma wa AI ni chaguo. OpsIQ inafanya kazi kama jukwaa la uchambuzi safi na jukwaa la tiketi bila AI. Unaweza kuwezesha AI baadaye wakati uko tayari.

Ninawezaje kuongeza viungo vya ziada na kuviongeza baadaye?+

Ndio. Waunganishaji hutajirisha AI na data maalum ya jukwaa, lakini OpsIQ inafanya kazi bila yao. Kuanza na kufuatilia na kuzungumza, kisha kuunganisha majukwaa wakati inahitajika.

Nini ikiwa bado hatuna tovuti?+

Unaweza bado kutumia OpsIQ kwa tiketi, CRM, na ushirikiano wa timu. widget ya kufuatilia ni hiari.

Jinsi ya kujua kama kadi ya mkopo imewekwa vizuri?+

Tembelea tovuti yako katika kivinjari cha kibinafsi / kisichojulikana. kisha angalia OpsIQ Chakula cha kuishi, unapaswa kuona ziara yako inaonekana ndani ya 15 Ikiwa sio, angalia: (1) Je, ni sahihi kwa matumizi sahihi? (2) Je, tovuti yako ni sahihi? (3) Ni blockers ya matangazo au viongozi wa CSP kuzuia script.

Kuanza hapa

Ramani ya bidhaa

OpsIQ sio kipengele kimoja. Ni admin operator, widget tovuti, safu ya msaada wa AI, mfumo wa tiketi / kusaidiadesk, CRM kamili na mawakala wanne wa AI , Suite ya Akili ya Tovuti, jukwaa la uunganisho na soko, na uso wa msanidi programu. Hapa ni kila sehemu inayo.

Usimamizi wa

Dashibodi, malisho ya moja kwa moja, logi ya mgeni, vikao, replay kikao, kurasa za juu, akili ya geo, funnel ya nia, kumbukumbu ya matukio, majaribio ya A / B, kufuatilia makosa ya JS, mauzo na uongofu, inaongoza, AI (kikosi cha amri, mawasiliano, makampuni, mikataba, bodi ya bomba, kufundisha mpango, utabiri, ufuatiliaji, mzunguko wa maisha, msimamizi wa data, Kujenga CRM yangu, CRM config, afya ya CRM, CRM API), tiketi, sanduku la mazungumzo, sheria za uendeshaji, tafiti za CSAT, rasimu za barua pepe, masanduku ya barua, usanidi wa AI, mafunzo ya AI, historia ya AI , ufahamu wa akili, msingi wa ujuzi, viunganisho, Connector Builder, soko, maeneo yaliyounganishwa, usimamizi wa timu, utendaji wa timu , mipangilio, uchunguzi, na leseni.

Bidhaa za Kuingiliana kwa Wateja

widget ya kufuatilia tovuti (analytics beacon + chat + tiketi embed + maarifa msingi kutafuta), mteja AI chat, bandari ya kuwasilisha tiketi, mgeni utambulisho wa kushughulikia, upakiaji faili, widget utafiti CSAT, na kituo cha msaada kwa wateja.

CRM ya kwanza

Command center, mawasiliano, makampuni, mikataba, bodi ya bomba na drag-na-kuacha, AI kushughulikia kocha (ishara hatari, ijayo bora-hatua, uwezekano wa kushinda), utabiri mapato, wakala wa uchimbaji (SDR), automatisering kufuatilia mfululizo, maisha na usimamizi wa kudumisha, data mtumishi wakala (dedup, tajiri, kuthibitisha), Kujenga yangu CRM (kiingereza asili setup), CRM Configuration, CRM ukaguzi afya, Trust Dial (Autopilot / Copilot / Manual kwa wakala), mawakala nne maalumu (Steward, SDR, Uhifadhi, Mtaalamu), na CRM API na webhooks.

Tovuti ya Intelligence Suite

Inatembea tovuti, ukaguzi wa kiufundi wa SEO (kasi, simu, Core Web Vitals, SSL, redirects, data muundo), ukaguzi wa maudhui (uhesabuji wa neno, usomaji, wiani wa maneno, muundo wa kichwa), utafutaji wa sauti ya AI-powered, ufuatiliaji wa cheo cha SERP katika injini zote, utafiti wa nenosiri na fursa ya kufunga, uchambuzi wa backlink na ufuatiliaji, taswira ya gridi ya ndani ya SEO, Google Business Profile sync (mapitio, posts, Q & A, picha, ufahamu), ripoti zilizopangwa (kila siku / kila wiki / kila mwezi) na nyeupe-label PDF uzalishaji kwa ajili ya viwanda.

AI na automatisering

Wateja AI chat (multi-mtoaji: Claude, GPT-4o) Gemini, Grok), admin AI msaidizi, AI ujuzi grounding, auto-handoff naconfigurable revert, kwa kila nafasi ya AI Configuration, kusimamiwa AI na BYOK modes, ishara bajeti na udhibiti wa gharama, AI historia ya ukaguzi uchaguzi, AI ufahamu uchambuzi, tiketi AI triage, tiketi auto-reply kwa kuchelewa, kuandika AI (kujitenga haraka), na admin inbox copilot.

Kuunganisha na Ushirikiano

25+ kabla ya kujengwa connectors (Shopify, WooCommerce, BigCommerce, Magento 2, PrestaShop, OpenCart, osCommerce, WordPress, WHMCS, Zendesk, Stripe, Amazon SES, Postmark, Resend, SendGrid, Mailgun, Gmail IMAP, Slack, Google Biashara Profile), Connector Builder (hakuna-code / AI-kusaidia / kamili-code), kawaida OAuth mtiririko na PKCE, kiunganishi sokoni na usambazaji kulipwa, kiunga saini na uthibitisho, SmartLookup fuzzy kulinganisha, orodha kubwa ya HTTP hatua ufafanuzi ambao upatikanaji hutegemea ufungaji connector, enablement, Configuration na usahihishaji, maarifa sync, na workflow mapishi.

Programu ya Developer

RadhaAPI(watembeleaji, matukio, tiketi, anwani, mipangilio, viunganisho), specifikationer ya OpenAPI,API Usimamizi muhimu, webhooks ya nje (async, saini, iliyosainiwa, iliyohifadhiwa, SSRF-kulindwa, isiyo na uharibifu), MatukioAPI Kwa ajili ya matumizi ya kawaida, widget SDKna azimio utambulisho, trigger cookbook, mikataba ya hatua, kontakt SDKufungaji wa soko, SDKs ya upande wa seva (PHP, Node.js), WordPress Plugin ya, na WHMCS ya moduli.

Mipangilio na Shughuli

Utambulisho wa biashara, usanidi wa AI kwa nafasi ya kazi, mipangilio ya kufuatilia, usalama (HSTS, Ruhusa za Polisi, IP kuzuia, ulinzi wa nguvu za brute), RBAC (Owner / Jumla Admin / Agent), usimamizi wa timu na mialiko, dashibodi ya utendaji wa timu, ufuatiliaji wa uwepo wa timu , mfumo wa template ya barua pepe (registry-kuendeshwa, mhariri wa kuona, chips tofauti), mtengenezaji wa utafiti, ujuzi wa kikoa, usanidi ulioingizwa wa tiketi, sera za kuhifadhi data, uendeshaji wa hesabu, mzunguko wa malipo (kila mwezi kupitia mzunguko wa maisha), uingizaji wa kawaida, uingizaji wa fedha, na eneo la uchunguzi, udhibiti wa croport, hali ya uchunguzi, na hatari ya uchunguzi.

Usalama na ufuatiliaji

Biashara ya Enterprise Enterprise SSO (OIDC na uthibitisho wa JWKS, utoaji wa JIT), SAML Utekelezaji, GDPR/DSAR utunzaji (kuuza na kufuta katika mifumo yote), data erasure kwa kuwasiliana, usimamizi wa kibali, kutengwa workspace (strict swala-layer scoping), uchaguzi ukaguzi, kushindwa kuingia kufuatilia, IP kuzuia, outbound Webhook SSRF walinzi, na sera za uhifadhi wa data.

Huduma ya Bridge

Alifanikiwa kupitia kwa OpsIQ Mtoa huduma URL mtoa huduma wa tovuti ya akili wito, uthibitisho wa leseni, ripoti za afya, PDF utoaji, na mauzo ya nje ya data, yote yalielekezwa kupitia kituo cha mtoa huduma kilichoundwa, sio muuzaji wa moja kwa moja API Maombi kutoka kwa server yako.

Kila ukurasa wa admin

Dashibodi ya juu

Nguvu

Kituo cha amri ya kila siku: maelezo ya trafiki, hesabu ya mgeni wa kuishi, muhtasari wa mauzo, kina cha foleni ya msaada, tahadhari za shughuli za AI, na njia za mkato za haraka.

Chakula cha kuishi

Uchambuzi

Wakati halisi mgeni mtiririko: maoni ukurasa, kuanza chat, fomu ya maombi, na nia ishara kuboresha kila sekunde chache na nchi, kifaa, na referrer filters.

Ziara ya logi

Uchambuzi

Rekodi kamili ya ziara: kifaa, kivinjari, OS, nchi, mji, referrer, params UTM, ukurasa wa kutua, utambulisho, na historia kamili ya mtazamo wa ukurasa.

Mkutano wa

Uchambuzi

Mtazamo wa safari-kundi: mtiririko wa ukurasa, wakati kwenye ukurasa, kina cha kitabu, njia ya uongofu, na ukurasa wa kuondoka kwa kila kikao cha wageni.

Rekodi ya kikao

Uchambuzi

Kuchezesha muda wa matukio yaliyochukuliwa: harakati za panya, clicks, scrolls, mabadiliko ya ukurasa, na uingiliano wa fomu kwa utambuzi wa UX.

Orodha ya Juu

Uchambuzi

Ukurasa wa utendaji: ziara, wakati wa ushiriki, kiwango cha bounce, uongofu, ushirikiano wa msaada, na mwelekeo wa mwenendo.

Geo intelligence ya

Uchambuzi

Ripoti za kijiografia: kuvunjika kwa nchi / mji na ramani, usambazaji wa kifaa, sehemu ya kivinjari, vyanzo vya trafiki, na kupenya soko.

Intiv ya funnel

Uchambuzi

Ufuatiliaji wa nia ya tabia: ziara za bei, mzunguko wa kurudi, kuvinjari doc, ushirikiano wa msaada, na ishara za desturi na uwezekano wa uongofu.

Matukio ya

Uchambuzi

Historia ya tukio la kuvutia: maoni ya ukurasa, matukio ya desturi, mazungumzo, ununuzi, maoni ya fomu na metadata kamili na kuchuja.

Jaribio la B

Uchambuzi

Split kupima: kujenga variants, kutenga trafiki, kufafanua malengo, kipimo umuhimu, na kutangaza washindi, wote kutoka ndani ya OpsIQ.

Makosa ya JS

Uchambuzi

Kukamata kosa la mbele: ujumbe, dalili za stack, vivinjari vilivyoathirika, mzunguko, kurasa zilizoathiriwa, na ufuatiliaji wa mwenendo.

Mauzo ya bidhaa

Mauzo ya bidhaa

Dashibodi ya mapato: maagizo, upyaji, marejesho, mchango kwa chanzo, utendaji wa kampeni, kulinganisha kipindi, na uchambuzi wa mwenendo.

Viongozi wa

Mauzo ya bidhaa

Usimamizi wa kuongoza: kufunga, chanzo cha mapato, hali ya CRM, maelezo ya mawasiliano, ishara za tabia, na uendeshaji wa bomba.

CRM ya juu

CRM

Full CRM: kituo cha amri, mawasiliano, makampuni, mikataba, bodi ya bomba, kufundisha, utabiri, matarajio, mlolongo, lifecycle, wakili wa data, na afya.

Tiketi za tiketi

Msaada wa msaada

Msaada wa inbox: idara, vipaumbele, ufuatiliaji SLA, AI triage, auto-reply, maelezo ya ndani, vifungo vya faili, kuunganisha, na usimamizi wa hali.

Chat ya inbox

Msaada wa msaada

Mazungumzo ya kuishi: AI na mazungumzo ya kibinadamu, handoff, ushirikiano, historia ya mazungumzo, utambulisho wa wateja, na ukusanyaji wa CSAT.

Rasimu za barua pepe

Msaada wa msaada

Usimamizi wa barua pepe: barua ya inbound kwa tiketi, muundo wa majibu ya AI-uliosaidiwa, uteuzi wa template, na usanidi wa sanduku la barua.

Kuwa na uhakika

I

Mpangilio wa mtoa huduma: chagua Claude / GPT-4o/Gemini/Grok, ingiza ufunguo wa API au kuwezesha AI iliyosimamiwa, kuweka mfano, joto, na bajeti za ishara kwa kila nafasi ya kazi.

Mafunzo ya

I

Kuandika haraka: wateja-inakabiliwa na usimamizi wa prompts, sheria za kuongezeka, miongozo ya sauti, mada marufuku, na usanidi wa mipaka.

Historia ya

I

Ukaguzi wa mazungumzo: maombi kamili / majibu ya kumbukumbu, matumizi ya ishara, gharama kwa kila mazungumzo, mtoa huduma, toleo la mfano, na matokeo ya azimio.

Ufahamu wa

I

Uchambuzi wa mfano: maswali ya kawaida, viwango vya azimio, mzunguko wa handoff, kuridhika na mada, na kitambulisho cha pengo la mafunzo.

Msingi wa ujuzi

I

Maudhui ya mafunzo ya AI: makala, viingilio vya FAQ, docs za bidhaa, ujuzi wa kontakt, na maingilio ya desturi. Semantic na utafutaji wa neno la msingi wa AI.

Viunganishi

Ujumuishaji

kitovu cha ushirikiano: viunganisho vilivyowekwa, hali ya afya, hesabu ya hatua, usimamizi wa credential, kivinjari cha soko, na Mjenzi wa Kuunganisha.

Maeneo ya Kuunganisha

Mipangilio ya

Usimamizi wa tovuti: kufuatilia snippet, muhimu wa tovuti, usanidi wa widget, mipangilio ya kikoa, na kutengwa kwa kazi ya tovuti.

Timu ya Timu

Mipangilio ya

Usimamizi wa mtumiaji: kuwakaribisha wanachama, kugawa majukumu (Owner / Jumla Admin / Agent), kuweka upatikanaji wa idara, na kusimamia ruhusa.

Utendaji wa Timu

Mipangilio ya

Ops metrics: nyakati za azimio, mzigo wa kazi, kufuata SLA, CSAT na wakala, viwango vya kufungua tena, masaa ya shughuli nyingi, na uchambuzi wa mwenendo.

Mipangilio ya

Mipangilio ya

Usanidi: utambulisho wa biashara, usanidi wa AI, ufuatiliaji, usalama, alama, uhifadhi, templates za barua pepe, bili, kuagiza / kuuza, uchunguzi, na eneo la hatari.

Leseni ya leseni

Mipangilio ya

Mpango wa usimamizi: hali ya leseni, vipengele vya mpango, metrics matumizi, tarehe ya upya, na kuboresha / chini ya daraja chaguzi.

Kuanza hapa

Mwongozo wa Kusafiri

Safari ya kuingia inageuka ufungaji mpya katika kazi OpsIQ Kazi ya kazi inaweza kushoto na kurudiwa bila kupoteza maendeleo.

Bidhaa ya Screen
Juu yaboardingOnboarding inaonyesha kila eneo la kuanzisha, hali yake ya sasa na hatua inayofuata kukamilisha.Juu yaboardingNafasi ya KaziPROGRESS60%COMPLETED6ya baadayeWidget yaMaisha ya kazi ya VIEWLeseni ya leseniKuheshimu leseni ya bidhaaKufanya hivyoKuwa mtoa hudumaChagua mtoa huduma na ufunguo wa mtihaniKufanya hivyoKuonyeshaBiashara ya utambulisho na toneKufanya hivyoTovuti ya tovutiOngeza tovuti na kufunga widgetBaadaye1COMPLETE BASICSJina la kikoa, brand, nk.2CONNECT DATATovuti na kontakt3VERIFY LAUNCHTimu, barua pepe, hundi
Onboarding inaonyesha kila eneo la kuanzisha, hali yake ya sasa na hatua inayofuata kukamilisha.

Kupendekeza kwa ajili ya

  1. Leseni ya: kuthibitisha leseni na kuthibitisha nafasi ya kazi ni kazi.
  2. Mtumiaji: Chagua mtoa huduma / mfano, ingiza sifa na kukimbia mtihani wa uunganisho. AI inaweza kuachwa ikiwa nafasi ya kazi itatumia analytics na tiketi tu.
  3. Utambulisho wa Biashara: Weka jina, sekta, maelezo, sauti ya wateja na maelezo ya bidhaa inayotumiwa na widget na AI.
  4. Mawasiliano ya: kuwezesha angalau jukwaa moja la nje wakati OpsIQ inahitaji maagizo, wateja, tiketi, barua pepe au mazingira mengine ya jukwaa.
  5. Tovuti na widget: Unda tovuti / nafasi ya kazi, nakala muhimu ya tovuti na kuthibitisha ziara ya kibinafsi katika Chakula cha Live.
  6. Timu na Uendeshaji: Kualika admins / wazee, kuunda idara, kuweka barua pepe routing na kuthibitisha mapendekezo ya taarifa.
  7. Ufuatiliaji wa Maisha: mtihani chat, tiketi, kiunganishi sync, cron, outbound barua pepe, webhooks na headers usalama.

Safari huhifadhi kukamilika kwa kila nafasi ya kazi. Kurudi kwenye Onboarding inapaswa kuonyesha hatua zilizokamilishwa badala ya kulazimisha kuanza upya.

Kuanza hapa

Usimamizi wa Usafiri na Ruhusa

Kwa kuwa OpsIQ Ramani hii inaelezea ambapo kila eneo la kazi linaishi na kwa nini ukurasa hauwezi kuonekana kwa kila msimamizi.

Bidhaa ya Screen
OpsIQ Usafiri wa urambazajiVikundi vya sidebar OpsIQ kwa eneo la kazi; viungo vya mtu binafsi huonekana tu wakati jukumu la sasa linaweza kutumia.OpsIQ Usafiri wa urambazajiNafasi ya KaziGROUPS8PichaRuhusa ya msingiSEARCHInapatikana kwa AvailableMaisha ya kazi ya VIEWMsaada wa msaadaTiketi, barua pepe, CSAT, ujuziKufunguaCRMMawasiliano, bomba, mikataba, matarajioKufunguaAutomation ya AutomationKazi, kanuni, malengoKufunguaUsalama na faraghaMaelezo ya jumla, ukaguzi, idhini, vitaluUsimamizi wa1PICK A GROUPMchezo wa sidebar2CHECK ROLENjia za kuzuia mimba zimezuiliwa3USE PAGE HELPKufungua sehemu ya kulinganisha
Vikundi vya sidebar OpsIQ kwa eneo la kazi; viungo vya mtu binafsi huonekana tu wakati jukumu la sasa linaweza kutumia.
Msaada wa msaada

Tiketi, jukwaa la barua pepe ya timu, CSAT, Kituo cha Msaada na mtiririko wa chatbot.

CRM

Uso wa mauzo ya kila siku: CRM Home, Kituo cha Amri, mawasiliano, bomba, utabiri, lifecycle, prospecting, sehemu, leaderboard, kibali cha mpango, wakili wa data, zana za ukuaji na mkondo wa shughuli.

Automation ya Automation

Kazi za uendeshaji wa tukio, sheria za maisha na malengo ya uongofu.

Masoko ya masoko

Kufikia, ujumbe wa ufanisi, matangazo, Studio ya Promotion, Studio Studio ya Utafiti, kushinikiza kampeni na ziara za kuongozwa.

Uchambuzi

Ripoti nyuso kwanza - Analytics Hub, ufahamu AI, mauzo, wateja, inaongoza, funnels, majaribio ya A / B, replay kikao, dashibodi desturi na ripoti iliyopangwa - kwa mgeni mbichi, kikao, ukurasa, jiografia na kumbukumbu za tukio katika sehemu ndogo ya Data.

Ukurasa wa Standal

Utaalamu wa tovuti, Utendaji wa Timu na Maoni hukaa nje ya makundi kama maingilio ya moja kwa moja.

Ujumuishaji

Waunganishaji, vitendo na kuchochea, masanduku ya barua, rasimu, mipangilio ya barua pepe, vituo vya kufungwa, webhooks za nje naAPIya funguo.

Usalama na faragha

Maelezo ya jumla ya usalama, faragha na kufuata, ridhaa ya kuki, shughuli za ukaguzi, logins zilizoshindwa, kufungwa IPs Aidha, na JavaScript makosa.

Mipangilio ya

Msingi wa msingi wa kazi (kwa ujumla, timu, maeneo, lugha), kisha collapsible subsections: AI Brain (marekebisho, usanidi, tathmini, historia), CRM Setup (wajenzi, mashamba ya desturi, kuongoza bao, afya), Data & Afya (diagnostics, mauzo ya nje) na Kupata Kuanza (juu ya ubao, msaada).

Ukurasa wa jukumu hauwezi kufungua ni siri kutoka kwa ubao. Kurasa mpango wa sasa haujumuishi kukaa inayoonekana na Kuboresha kuboresha Weka na kufungua skrini ya kuboresha katika programu.

Njia za moja kwa moja bado zinachunguzwa upande wa seva. Kufunga kiungo cha sidebar sio mpaka wa usalama: kila hatua iliyolindwa lazima ipitie ruhusa yake na ukaguzi wa nafasi ya kazi.

Uchambuzi

Kituo cha Analytics

Kichupo cha Analytics huleta msaada, kuzungumza, AI, mgeni na wakala kuripoti katika nafasi moja ya kazi iliyopitiwa tarehe na matokeo ya kuuza nje.

Bidhaa ya Screen
Kituo cha AnalyticsHub Analytics inaonyesha aina ya tarehe, kadi za metric na tabs kwa ajili ya Msaada, Chat, AI, Visitor na Agent utendaji.Kituo cha AnalyticsNafasi ya Kazitiketi184AI RESOLVE63%CSAT ya CSAT4.7Maisha ya kazi ya VIEWMsaada wa msaadaKuundwa, kufungwa, kusubiri, SLATab ya TabKuzungumzaMatokeo ya AI / Binadamu na Kushughulikia WakatiTab ya TabIKujiamini, Maoni, Matumizi ya IsharaTab ya TabAgent waKiwango cha juu, kasi na kuridhikaTab ya Tab1CHOOSE DATESKutayarisha au desturi2CHANGE TABMsaada kwa Agent3EXPORTDownload mchezo Kupakua CSV
Hub Analytics inaonyesha aina ya tarehe, kadi za metric na tabs kwa ajili ya Msaada, Chat, AI, Visitor na Agent utendaji.

Filters na udhibiti wa

  • Tumia kabla au baada ya utaratibu kutoka/kwa Kisha, safisha upya kila kadi na chati kwa kipindi hicho.
  • Usafirishaji wa nje CSV Kuhamisha maoni ya uchambuzi badala ya screenshot.
  • Kusanya nafasi ya kazi ni moja kwa moja; kubadilisha maeneo hubadilisha dataset msingi.

Nini kila hatua ya tab

  • Msaada: tiketi kuundwa / kufungwa / kusubiri, jibu la kwanza, ufumbuzi, ufunguzi wa kwanza-wasiliana, SLA, na kipaumbele / idara / hali breakdowns.
  • Chat ya: Vikao vilianza, maazimio ya AI, kuongezeka, kuachwa, kushughulikia wakati, ujumbe kwa kikao, na AI / kibinadamu / CSAT yote.
  • AI: Wastani wa kujiamini, kiwango cha chini cha kujiamini, usahihi wa triage, maoni, uharibifu wa ujuzi, matumizi ya ishara / cache, na vitu ambavyo vinahitaji ukaguzi.
  • Ziara ya: Mwelekeo wa trafiki na ushiriki kwa kipindi cha kuchaguliwa.
  • Mtumiaji: Kazi ya haraka, kasi, kufunga na hatua za kuridhika.

Tumia Hub Analytics kwa mapitio ya timu ya msalaba; tumia Wageni waliojitolea, Tiketi, CSAT, Historia ya AI na kurasa za Utendaji wa Timu wakati unahitaji uchunguzi wa ngazi ya rekodi.

Uchambuzi

Dashibodi ya juu

Dashibodi ni kituo chako cha amri ya kila siku. Inaonyesha trafiki, mauzo, msaada wa mzigo, shughuli za AI, na viashiria vya uongofu kwa mtazamo mmoja. Fungua kila asubuhi kuelewa kilichotokea usiku kucha na kile kinachohitajika kuzingatia leo.

Dashibodi ya juu
Maelezo ya jumla ya dashibodiscreen ya jumla inayoongozwa na jopo la AI la akili ya OpsIQ (na tahadhari za kila siku, Smart, Utabiri), tiles za widget ya KPI na widget ya trafiki ya siku saba, pamoja na udhibiti wa mpangilio wa Reset.Muhtasari wa jumlaNafasi ya KaziOPSIQ Kwa bahati nzuriFanya uchambuzi wa kina na OpsIQ Andika juu yakeMuhtasari wa Kila sikuTahadhari ya SmartUtabiri wa utabiriKubadilishwa kwa mpangilioWaandishi wa habari leo2,481+12%Kugeuka$8.2k ya+5%Kufunguliwa kwa majaribio143 SLA yaUsafiri · Mwisho 7 Siku za siku1AI-FIRSTOpsIQ Jopo la wataalamu2WIDGETSVifaa vya KPI ambavyo unaweza kupanga3yakoKubadilishwa kwa wakati wowote
screen halisi ya muhtasari: jopo la akili la OpsIQ juu (chagua uchambuzi na inaandika) juu ya vilivyoandikwa vya KPI unavyopanga mwenyewe.

Kadi za Dashibodi zilizoelezea

Wageni wa Kuishi

Idadi ya watu kwenye tovuti yako hivi sasa. hii updates kila 15 Mgeni ni "mfanyakazi" ikiwa anaweka ukurasa ndani ya kizingiti cha kazi (default: 90 sekunde).

Wageni wa kipekee

Watu wangapi walitembelea tovuti yako katika aina ya tarehe iliyochaguliwa. OpsIQ hutambulisha wageni kwa mchanganyiko wa alama za vidole, kuki, na (ikiwa inapatikana) utambulisho uliothibitishwa.

Mpya vs Kurudi

Wageni wapya wanaona tovuti yako kwa mara ya kwanza. wageni wa kurudi wamekuwa kuonekana kabla. uwiano juu ya kurudi inamaanisha maudhui yako huleta watu nyuma.

Kiwango cha Bounce

Asilimia ya wageni ambao waliacha baada ya kutazama ukurasa mmoja tu. Kiwango cha bounce juu ya 70% kwenye kurasa za kutua kwa kawaida inamaanisha ukurasa haukutana na matarajio ya mgeni, maudhui yasiyofaa, mzigo mdogo, au uzoefu duni wa simu.

Muda wa wastani kwenye ukurasa

Wageni hutumia muda gani kwenye kila ukurasa kwa wastani. nyakati fupi sana (chini ya sekunde za 10) kwenye kurasa za maudhui zinaonyesha kuwa maudhui hayahusishi. Mara nyingi katika kurasa za checkout zinaweza kuonyesha mkanganyiko.

Vitisho vimefungwa

IPKwa mujibu wa OpsIQ kutambuliwa kama uwezekano wa nia mbaya kulingana na kufunga tishio, majaribio ya nguvu za brute, au vitalu vya mwongozo. IPs Orodha ya.

Habari za leo/wiki hii

Mapato kutoka vyanzo vya mauzo vilivyounganishwa (Shopify, WooCommerce, Stripe, nk) Ikiwa mauzo yanaonyesha sifuri, angalia kwamba uunganisho wako wa jukwaa umeshikamana na kuunganisha.

Mwelekeo wa chati

Mstari wa mstari unaonyesha hesabu ya mgeni juu ya aina ya tarehe iliyochaguliwa. Angalia kwa ruwaza: spikes za trafiki (maonyesho, maelezo ya vyombo vya habari), kina (mwisho, likizo), na mwenendo endelevu.

Vyanzo vya juu

Ambapo wageni wako wanatoka: moja kwa moja, Google, vyombo vya habari vya kijamii, kampeni za barua pepe, maeneo ya rufaa. Tumia hii kuelewa ni njia gani za masoko zinafanya kazi.

browsers ya juu

Chrome, Safari, Firefox, Edge, na wengine. Kama kivinjari ina kiwango cha juu ya kawaida bounce, unaweza kuwa na CSS au JavaScript suala utangamano.

Saa ya joto

gridi ya kuonyesha shughuli mgeni kwa saa ya siku na siku ya wiki. Tumia hii kuamua wakati wa ratiba msaada mabadiliko, wakati wa kutuma matangazo, na wakati wa kuendesha matangazo.

Wageni wa hivi karibuni

Wageni wachache wa mwisho na nchi, ukurasa, kifaa, na chanzo. Inafaa kwa ukaguzi wa haraka wakati wa kampeni.

Kutumia aina ya filter

Bonyeza tarehe picker juu ya kulia ya Dashboard. Presets: Leo, Jana, Mwisho 7 Siku za Mwisho 30 Siku, Mwezi huu, mwezi uliopita, Custom mbalimbali. kadi zote dashibodi na chati update wakati wewe mabadiliko ya aina mbalimbali.

Mifano ya kazi

Kiwango cha bounce cha uchunguzi

Kwa mfano:
Kiwango chako cha bounce kimeongezeka kutoka 45% Kwa ajili ya 78% Wiki hii, nini kilichotokea?
Nini cha kufanya:

Angalia kwa makini: (1) Je, ukurasa maalum wa kutua umebadilika? Nenda kwenye Kurasa za Juu na Aina kwa kiwango cha bounce.2Je, kampeni ilituma trafiki kwenye ukurasa usiofaa? Angalia Vyanzo vya Juu kwa Warejeleaji wapya.3) Je, tovuti kuvunja kwenye simu ya mkononi? Angalia kuvunjika kwa browser kwa kiwango cha bounce simu.4) Je, ni trafiki ya bot? Angalia vitisho vya kukabiliana na maelezo ya wageni kwa mwelekeo wa tuhuma.

Wageni wa Zero kwenye dashibodi

Kwa mfano:
Dashibodi inaonyesha 0 wageni wa moja kwa moja ingawa tovuti yako inapata trafiki.
Nini cha kufanya:

Angalia kwa makini: (1Je, widget ya kufuatilia imewekwa? Angalia msimbo wako wa chanzo cha tovuti na kutafuta OpsIQ (Sauti ya mwandishi).2) Je, tovuti muhimu ni sahihi? kulinganisha data-tovuti-key katika script na ufunguo katika maeneo Kuunganishwa.3Ni CDN au cache inayotumikia ukurasa wa stale bila script? Futa cache yako ya CDN.4) Je, msimamizi wa matangazo au kiongozi wa CSP anazuia script? Angalia console ya kivinjari kwa maombi yaliyozuiwa.

Kusoma kwa saa ya joto

Kwa mfano:
Joto la joto linaonyesha shughuli nzito kati ya 10am-2pm siku za wiki lakini hakuna kitu mwishoni mwa wiki.
Nini cha kufanya:

Hii ni muundo wa trafiki wa B2B. Wageni wako ni wataalamu wa kufanya kazi kuvinjari wakati wa masaa ya biashara. matokeo: (1(i) Kuajiri wafanyakazi kwa muda wa siku za kazi.2• Tuma kampeni za barua pepe Jumanne-Jumapili asubuhi.3(iii) Hifadhi ya Taifa ni salama.4• Fikiria kutoa mazungumzo ya kuishi tu wakati wa masaa ya kilele.

Trafiki ya trafiki kutoka chanzo kisichojulikana

Kwa mfano:
Utaona kwamba ghafla 500 Wageni katika saa moja kutoka kwa mtu asiyejulikana.
Nini cha kufanya:

Nenda kwa wageni na filter kwa wakati: (1) Je, ni wageni halisi au bots? Angalia muda wa kikao, kurasa zilizotazamwa, na utofauti wa kivinjari. (2) Ikiwa ni kweli, ukurasa gani unaoingia? (3) Angalia kwa makini maelezo URLMtu anaweza kuwa na uhusiano na wewe kutoka Reddit, Hacker News, au blog maarufu. (4) Ikiwa ni trafiki ya bot, angalia vitisho na fikiria kuzuia IP mbalimbali.

Kwa nini wageni wangu ni tofauti na Google Analytics?+

OpsIQ Inahesabu wageni tofauti.Inatumia alama za vidole vya kivinjari na kuki, wakati GA hutumia mfano tofauti wa kidakuzi.Kuchuja Bot, viwango vya kuzuia matangazo, na utaratibu wa upakiaji wa script unaweza pia kusababisha tofauti. 10-20% Tofauti ni ya kawaida.

Ninawezaje kuingiza Plugin kwenye chombo kingine?+

Dashibodi imetayarishwa kwa ajili ya OpsIQ Kwa taarifa za nje, tumia REST API Kuvuta data ya uchambuzi na kuionyesha kwenye dashibodi yako mwenyewe au chombo cha BI.

Nini maana ya "mauaji"?+

Ina maana kuwa IP Kwa mujibu wa OpsIQ Ime flagged au imefungwa kulingana na kufunga tishio, logins mara kwa mara kushindwa, au vitalu mwongozo. Bofya counter kuona maelezo na kusimamia vitalu.

Uchambuzi

Ziara ya logi

Ingia ya Mgeni inaonyesha kila ziara kwenye tovuti zako zilizofuatiliwa. Kila mstari ni mzigo wa ukurasa mmoja kutoka kwa mgeni mmoja. Tumia kuchunguza tabia ya wageni binafsi, kupata trafiki ya kampeni, na kutambua masuala ya kufuatilia.

Ziara ya logi
Ziara ya logiMeza ya mgeni na bar filter (tarehe, tafuta)IP/ email, chanzo, kifaa) na nguzo kwa ajili ya IP/ barua pepe, eneo, chanzo, kifaa na wakati, na safu ya tishio iliyo bendera.Ziara ya logiyoursite.com7 Siku za sikuUtafutaji wa Kutafuta IP Kwa mfano, barua pepe, mji ...Chanzo chanzo▾Kifaa ▾IP ya EMAILMkutano waVyanzo vya chanzoFuraha yaWakati wa[email protected]Marekani · New YorkgoogleDesktop2 m2 wa41.62.10.4Uingereza · LondondirectSimu ya Mkono Mobile6 m[email protected]Berlin ya KatiTag: yaSimu ya Mkono Mobile14 m203.0.113.9· Mji wa LagosreferralDesktopthreat1–25 Kwa upande wa 3,402Mkutano wa→1FILTERTarehe · Kutafuta · Chanzo · Kifaa2REAL COLUMNSIP· Eneo · Kifaa · Tishio3DRILL INKukamilisha Mkutano wa Jumla
Ingia halisi: filter kwa tarehe, utafutaji na kifaa, kisha kusoma kila ziara na IP/Email, eneo, chanzo, kifaa na wakati, vitisho bendera katika nyekundu.

Nini kila rangi inaonyesha

IP Anwani ya anwani

Ziara ya mgeni IP Jina la mtumiaji: Ikiwa IP anonymization ni kuwezeshwa katika Mipangilio. Click kuona ziara zote kutoka hii IP.

Nchi na Jiji

Kugunduliwa kutoka IP anwani kwa kutumia data GeoIP. Inahitaji MaxMind GeoLite2 database au Cloudflare geo vichwa. Inaonyesha "Haijulikani" kama GeoIP si configured.

Ukurasa wa ukurasa URL

Ukurasa wa mgeni aliyepakiwa. Bonyeza ili kuona kamili URLmrefu ya URLs Wao ni kutambuliwa katika mtazamo wa meza.

Uangalizi wa

Ambapo mgeni alikuja kutoka kabla ya kutua kwenye tovuti yako. "Mkurugenzi" inamaanisha hakuna referrer (alama za kitabu, aina ya URLs, viungo vingine vya programu).

Vifaa na browser

Aina ya kifaa cha mgeni (desktop, simu, kibao) na kivinjari (Chrome, Safari, Firefox, nk). kilichotolewa kutoka kwa kichwa cha mtumiaji-Agent.

Tarehe na wakati

Wakati ukurasa umepakiwa, katika eneo lako la wakati uliowekwa.

Utambulisho wa Wateja

Ikiwa mgeni ametambuliwa (kupitia ishara ya utambulisho au kuingia), jina lake au barua pepe inaonekana. Vinginevyo inaonyesha kama haijulikani.

Filters ya

Tarehe ya tarehe

Filter ziara ya kipindi maalum cha wakati. Default: siku za mwisho 7

Tafuta

Kutafuta kwa ajili ya IP Ukurasa wa Tovuti, ukurasa URL, referrer, nchi, au barua pepe ya mteja.

Chanzo

Filter na chanzo cha trafiki: moja kwa moja, kikaboni, kijamii, Referral, Paid, Barua pepe.

Vifaa vya

Filter kwa Desktop, Simu ya Mkono au Tablet.

Mpya ya pekee

Waonyeshe wageni wa mara ya kwanza ambao hawajawahi kuonekana hapo awali.

Mifano ya kazi

Kupata wageni kutoka kampeni maalum

Kwa mfano:
Umezindua kampeni ya Matangazo ya Google na parameter ya UTM utm_source = google &utm_medium = cpc&utm-campaign = mauzo ya majira ya joto.
Nini cha kufanya:

Katika Ingia ya Mgeni, tumia uwanja wa Utafutaji na aina "sale-summer". ukaguzi wa utafutaji unarejelea URLs Ukurasa wa URLs Kwa hivyo vigezo vya UTM vitalingana. Unaweza pia kuchuja kwa Chanzo = Paid kupunguza chini zaidi.

Tafuta mtu ambaye ana tatizo la

Kwa mfano:
Mteja aliniandikia barua pepe akisema "ukurasa wako wa checkout ulivunjwa jana karibu na 3pm."
Nini cha kufanya:

Tafuta kwa anwani yao ya barua pepe katika Ingia ya Mgeni. Ikiwa walikuwa watumiaji, utambulisho wao utaonekana. Weka tarehe hiyo hadi jana. Angalia ziara za kurasa za checkout karibu na 3pm. Bonyeza kikao chao ili kuona mtiririko kamili wa ukurasa na makosa yoyote ya JavaScript

Kuharibu loop hitter au scraper

Kwa mfano:
Unagundua kuwa IP Anwani yake ni 500+ ziara katika saa moja, wote kwa ukurasa mmoja.
Nini cha kufanya:

Hii ni uwezekano wa bot, scraper, au script kuvunjwa. Nenda kwenye Ingia ya Mgeni na kutafuta kwa hiyo IP Angalia kwa makini: (1(a) Je, ni lini barabara zote zitajengwa katika eneo moja?2Je, mtumiaji wa mtandao ni mtu mwenye ujuzi? (3(a) Je, ni lini Mkutano wa 0 Ikiwa umethibitishwa kama bot, nenda kwenye Usalama na ushikilie IP.

Home »Unlabelled » Mkutano wa Bunge vs Chakula cha Kuishi

Ziara ya logi

Mstari mmoja kwa mtazamo wa ukurasa. Bora kwa: kuchunguza kurasa maalum, kutafuta trafiki kutoka vyanzo maalum, kutambua masuala ya kufuatilia.

Mkutano wa

Vikundi vya ukurasa wa maoni katika safari. Mstari mmoja kwa kikao cha ziara. Bora kwa: kuelewa mtiririko wa mtumiaji, kupima muda wa kikao, kutambua njia za uongofu.

Chakula cha kuishi

Onyesha wageni sasa kwenye tovuti yako. bora kwa: kufuatilia kampeni katika maendeleo, kufanya wageni wa hali ya juu, kuangalia fursa za msaada.

Kwa nini ninaona ziara zangu katika UAE?+

OpsIQ Kutenga trafiki yako mwenyewe, kuongeza ziara zote kwa default.IPHotuba kwa walioondolewa IPs Orodha katika Mipangilio > Kufuatilia.

Kwa nini wageni wanatangaza nchi isiyojulikana?+

Pia, uchunguzi wa GeoIP unahitaji Cloudflare« Geo headers (moja kwa moja kama kutumia Cloudflare) au faili ya hifadhidata ya MaxMind GeoLite2. Angalia Mipangilio > Njia ya GeoIP ili kuhakikisha faili ya database ipo na inaweza kusomwa.

Data ya wageni imehifadhiwa kwa muda gani?+

Data ya wageni imehifadhiwa kwa kipindi cha uhifadhi kilichoundwa katika Mipangilio (default: 90 siku). Baada ya hapo, kumbukumbu za zamani zinasafishwa moja kwa moja na kazi ya kuhifadhi cron.

Uchambuzi

Mkutano wa

Sessions kundi maoni mengi ukurasa kutoka mtu mmoja katika safari moja. Wakati Visitor Log inaonyesha mizigo ya ukurasa wa mtu binafsi, Sessions kuonyesha jinsi watu hoja kupitia tovuti yako kutoka kutua kwa exit.

Mkutano wa
Mkutano waJedwali la Ingia la Session na IP, nchi, kifaa, chanzo, muda na safu za kurasa, na mstari wa tishio ulio bendera.Mkutano wayoursite.comNchi ya (NG)Mkutano wa LogIP(a) KuwaNchi yaFuraha yaVyanzo vya chanzoUendelezaji waPicha41.62.10.4UingerezaDesktopgoogle3 m3 wa 12s6102.89.6.2ya yaSimu ya Mkono Mobiledirect1 m 05s388.21.4.9DEDesktopTag: ya48s11203.0.113.9Marekani ya MarekaniSimu ya Mkono Mobilereferralya 0 m 42s21SESSION LOGSafari za pamoja2COLUMNSNchi · kifaa · chanzo · muda3THREATMkutano wa hatari wafunguliwa
Kuingia kwa Session halisi: kila safari ya mgeni kama mstari (IP, nchi, kifaa, chanzo, muda na kurasa) na vikao vya hatari vilivyoonyeshwa kwenye nyekundu.

Jinsi ya kufanya mikutano

Kipindi huanza wakati mgeni anapakia ukurasa wao wa kwanza. Inaendelea kama wanavyokwenda kwenye kurasa zaidi. Kifungu kinaisha wakati mgeni hana kazi kwa kipindi cha muda wa kikao (default: 30 dakika) au kufunga kivinjari chao. Mtu huyo anayerudi baada ya muda huunda kikao kipya.

Nini kila mkutano unaonyesha

Ukurasa wa Kwanza

Ukurasa wa kutua, ambapo mgeni aliingia kwenye tovuti yako. Hii inakuambia ni maudhui gani yanayovutia watu.

Ukurasa wa mwisho

Ukurasa wa kuondoka, ambapo mgeni aliondoka. Ikiwa ukurasa wa exit mara nyingi ni ukurasa wa bei, wageni wanaweza kuwa wanakulinganisha na washindani.

Ukurasa wa kuhesabu

Ukurasa zaidi kwa kawaida unamaanisha ushiriki zaidi, lakini pia inaweza kumaanisha mgeni anapotea.

Muda wa muda

Muda wa jumla kutoka kwa mzigo wa ukurasa wa kwanza hadi shughuli ya mwisho. Sessions na sekunde za 0 ni bounce (mtazamo wa ukurasa mmoja, hakuna mwingiliano zaidi).

Chanzo

Chanzo cha trafiki kwa kikao hiki (Mkurugenzi, Google, kijamii, rufaa, nk).

Nchi ya nchi

Nchi ya ajabu kutoka kwa wageni IP Anwani ya.

Bounce ya

Ikiwa mgeni aliondoka baada ya kutazama ukurasa mmoja tu. vikao vya Bounced vina kiashiria nyekundu.

Kubadilisha

Ikiwa mgeni alikamilisha tukio la uongofu lililofuatiliwa (kununua, kujisajili, kuwasilisha fomu) wakati wa kikao hiki.

Filters ya

Tafuta

Kutafuta kwa ajili ya IP Barua pepe, ukurasa URL au kuingia katika vikao vya Bunge.

Aina ya

Filter na wageni wapya (kifungu cha kwanza kabisa) au wageni wanaorudi.

Chanzo

Filter kutoka chanzo cha trafiki.

Nchi ya nchi

Filter kwa nchi ili kuona vikao kutoka eneo fulani.

Vitisho/vipozi

Filter kuonyesha vikao tu vilivyopigwa au vikao vinavyoonyeshwa kama vitisho.

Mifano ya kazi

Profile ya mteja wa thamani kubwa

Kwa mfano:
Wateja wengi wanataka kununua bidhaa zao, unahitaji kujua kuhusu safari kabla ya kununua.
Nini cha kufanya:

Tafuta barua pepe zao katika Sessions. Angalia vikao vyao vyote: (1(a) Je, ni mara ngapi umenunua kabla ya kununua?2(a) Je, ni vigezo gani ambavyo vimetumika?3(a) Je, ni lini Serikali itanunua au kununua mitambo ya kuzalishia umeme? (Makofi)4) Ni muda gani wa jumla kutoka ziara ya kwanza ya kununua? Hii inakuambia safari ya kawaida ya ununuzi kwa wateja wenye thamani kubwa.

Kuhamisha login kutoka eneo jipya

Kwa mfano:
Kwa kawaida, mteja huhamia kutoka Nigeria lakini unaweza kuona kikao kutoka Urusi.
Nini cha kufanya:

Tafuta barua pepe ya mteja katika Sessions. Linganisha nchi ya vikao vya hivi karibuni. Ikiwa kikao kinaonekana ghafla kutoka nchi isiyo ya kawaida, inaweza kuwa safari halali au akaunti iliyoathirika.1Je, kulikuwa na jaribio la kuingia lililoshindwa kabla ya kufanikiwa?2• Alifanya hivyo IP Mabadiliko ndani ya kikao hicho? bendera kwa ajili ya ukaguzi kama tuhuma.

Kuna tofauti gani kati ya mkutano na mgeni?+

Mgeni ni mtu (au kivinjari). kikao ni ziara moja kutoka kwa mtu huyo. mgeni huyo anaweza kuwa na vikao vingi baada ya muda.

Jinsi ya kufanya OpsIQ Kuwatambua wageni wanaorudi?+

OpsIQ hutumia mchanganyiko wa kuki, alama za vidole vya kivinjari, na ishara za utambulisho zilizothibitishwa. Ikiwa mgeni anafungua kuki zao na hakuingia, itaonekana kama mgeni mpya.

Uchambuzi

Chakula cha kuishi

Feed Live inaonyesha wageni sasa kwenye tovuti yako kwa wakati halisi. Inasasisha moja kwa moja kila sekunde ya 15 (inategemea). Tumia wakati wa kampeni, uzinduzi wa bidhaa, na vipindi vya msaada wa busy ili kuona kinachotokea hivi sasa.

Chakula cha kuishi
Chakula cha kuishiMto wa shughuli halisi ya wakati unaonyesha hesabu ya kutembelea mtandaoni na kulisha vitendo vya wageni wa hivi karibuni nchini.Chakula cha kuishiyoursite.com37Wageni wa mtandaoni sasaShughuli za MaishasasaMarekani · Kuangalia /pricing2sUingereza kuanza mazungumzo5s· Kuongeza kwa Cart9s· Kukamilisha usajili1RIGHT NOWAngalia nani ni mgeni kwenye tovuti2AUTO-REFRESHUpdates kila mmoja 15s3KAZIKuruka katika kuishi chat
Angalia ni nani kwenye tovuti yako hii ya pili na wanafanya nini, kuburudisha kila mmoja 15 Sekunde moja kwa ajili ya.

Jinsi ya kufanya kazi

Kila mstari unaonyesha mgeni sasa kwenye tovuti yako: ukurasa wao wa sasa, nchi, kifaa, chanzo, muda wa kikao, na hesabu ya ukurasa. Vipengele vya Green vinaonyesha shughuli mpya tangu kupumzika kwa mwisho.

Mipangilio ya

Kufufua interval

Ni mara ngapi chakula cha kuishi kinatolewa? Default: 15 Viwango vya chini (Low Value)5-10s Kutoa sasisho za haraka lakini tumia rasilimali zaidi za seva. maadili ya juu (30-60s Ni rahisi kwenye seva lakini chini ya muda halisi.

Kiwango cha chini

Ni muda gani mgeni anachukuliwa kuwa "mfanyakazi" baada ya mzigo wao wa mwisho wa ukurasa: 90 Ikiwa mgeni anapakia ukurasa na kisha kusoma kwa ajili yake 2 Dakika bila kubonyeza, hupotea kutoka kwa chakula cha kuishi baada ya kizingiti.

Bonyeza kifungo

Bonyeza Kupumzika kuacha auto-refresh. Muhimu wakati unataka kusoma maelezo bila orodha ya uboreshaji. Bonyeza kuendelea kuanza tena.

Mifano ya kazi

Kuongoza kwa risasi wakati wa kampeni

Kwa mfano:
Unaendesha uzinduzi wa bidhaa. mgeni tu aliyeangalia ukurasa wako wa nyumbani, kisha makala, kisha bei, na sasa yuko kwenye ukurasa wa checkout.
Nini cha kufanya:

Hii ni tabia ya hali ya juu katika chakula cha kuishi: (1(i) Mruhusu mgeni ahudhurie mkutano huo.2Kama wao kuanza kuzungumza, AI itakuwa na mazingira yao kamili ya safari.3) Kama wao kuondoka bila kununua, wao kuwa kuongoza katika ukurasa wa Leads.4• Fikiria kuunda utawala wa ufanisi ili kuonyesha ujumbe wa kuzungumza wakati wageni wanafikia checkout.

Wageni wengi kutoka Same IP

Kwa mfano:
Unaona kuwa 20 Wageni kutoka Same IP Picha zote na Wizara ya Mambo ya Ndani ya Nchi.
Nini cha kufanya:

Hii inaweza kuwa: (1Ofisi na mtandao wa pamoja. Angalia ikiwa ziara zinaonekana kama wanadamu halisi (kurasa tofauti, muda wa kikao cha busara).2) bot au scraper. Angalia ikiwa vikao ni fupi sana (0-1sekunde) au kupiga kurasa kwa utaratibu. (3• mtihani wa mzigo. Ikiwa unatumia majaribio ya automatiska, usiondoe IP kutoka kwa ufuatiliaji.

Kwa nini show ya chakula cha mchana 0 Je, ni lini tovuti yangu ina trafiki?+

Angalia ukaguzi: (1) Je, script ya widget imewekwa kwenye tovuti yako? (2) Je, tovuti yako ni sahihi? (3) Je, kiwango cha kazi kimepungua? (4) Je, wageni hutumia blockers ya matangazo yenye nguvu ambayo huzuia script ya kufuatilia?

Je, ninaweza kupakua chakula cha moja kwa moja kutoka nchi au kifaa?+

Chakula cha kuishi inaonyesha wageni wote wanaofanya kazi. Kwa maoni yaliyochujwa, tumia kurasa za Visitor Log au Sessions na chaguzi zao za kuchuja. kulisha moja kwa moja ni rahisi kwa ufuatiliaji wa wakati halisi.

Uchambuzi

Orodha ya Juu

Ukurasa wa juu unaonyesha ni kurasa gani kwenye tovuti yako kupata trafiki zaidi. Ina safu ya kurasa kwa ziara, ushiriki, uongofu, na shughuli za usaidizi. Itumie kutambua maudhui yako bora, pata kurasa zisizofanya kazi, na kugundua kurasa zinazozalisha maswali ya msaada.

Orodha ya Juu
Orodha ya JuuOrodha ya orodha iliyoorodheshwa ya kurasa zilizotembelewa zaidi na baa za ziara za macho na hesabu.Orodha ya Juuyoursite.comOrodha ya kurasa zilizotembelewa zaidi/pricing3,402/2,910/docs1,740/blog/seo-guide980/signup6401RANKEDOrodha ya kurasa zilizotembelewa zaidi2SIGNALSZiara na ubadilishaji3FINDUkurasa unaoongoza tiketi
Kurasa zako zilizowekwa na trafiki na ushiriki, ili uweze kuona maudhui ya juu na kurasa zinazozalisha msaada.

Kila ukurasa una nini cha kuonyesha

Ukurasa wa ukurasa URL

Njia kamili ya URL. Kurasa zinazofanana (kwa mfano, anuwai za bidhaa) zinajumuishwa ikiwa kikundi kinawezeshwa.

Maoni ya Mtazamo

Idadi ya mara ukurasa huu ulipakiwa katika safu ya tarehe iliyochaguliwa.

Wageni wa kipekee

Ni watu wangapi walitazama ukurasa huu (mtu anayeangalia ukurasa huo mara mbili) 1 wa pekee).

Kiwango cha Bounce

Asilimia ya wageni ambao waliondoka kwenye tovuti yako baada ya kutazama ukurasa huu tu. High bounce juu ya kurasa za kutua = shida.

Wastani wa muda

Ni wageni wangapi wanatumia kwenye ukurasa huu kwa wastani. mfupi sana = si kusoma. mrefu sana kwenye ukurasa wa fomu = mkanganyiko.

Mazungumzo yaanza

Jinsi mazungumzo mengi ya kuzungumza yalianzishwa kutoka ukurasa huu. High chat kuanza kwenye ukurasa wa bidhaa maana maelezo ya bidhaa inaweza kuwa wazi.

Msaada wa tiketi

Ni tiketi ngapi za usaidizi zilizoundwa na wageni ambao walikuwa kwenye ukurasa huu. kuhesabu Tiketi ya juu = uwezekano wa UX au shida ya maudhui.

Mifano ya kazi

Kupata kurasa ambazo zinaongoza maswali ya msaada

Kwa mfano:
Timu yako ya msaada inaendelea kupata maswali kuhusu usafirishaji. ukurasa gani unashindwa?
Nini cha kufanya:

Panga Kurasa za Juu kwa "Kusaidia tiketi" au "Chat huanza" kushuka. Angalia kurasa za bidhaa au usafirishaji na makosa makubwa. ukurasa wenye maswali mengi ya msaada labda una habari isiyo wazi.

Kupata kurasa kwa kiwango cha juu exit

Kwa mfano:
Unataka kujua wapi watu wengi wanaondoka kwenye tovuti yako mara nyingi.
Nini cha kufanya:

Weka kiwango cha bounce kushuka. Sahau kurasa ambazo ni pointi za asili za kuondoka (shukrani kwa kurasa, kurasa za uthibitisho). Kuzingatia kurasa ambazo zinapaswa kuweka wageni wanaohusika: kurasa za bidhaa, bei, vipengele. Hizi zinahitaji wito bora wa hatua au maudhui wazi.

Kwa nini ukurasa wa kuonyesha 0 Hata hivyo, ninafahamu kwamba kuna njia ya kupata trafiki?+

Angalia kwa makini: (1) Je, widget ya kufuatilia imewekwa kwenye ukurasa huo maalum? programu za ukurasa mmoja zinaweza zisiwe na maoni ya ukurasa wa moto juu ya mabadiliko ya njia.2(a) Je, ni lini barabara hiyo itajengwa katika maeneo ya Halmashauri?3Je, CDN inahudumia toleo la cached bila script ya kufuatilia?

Uchambuzi

Geo intelligence ya

Geo Intelligence inaonyesha ambapo wageni wako wanatoka kwa nchi, mji, kifaa, na chanzo. Tumia kuelewa masoko yako ya kijiografia, kuamua juu ya msaada wa lugha, mpango wa masoko ya kikanda, na kuchunguza mwelekeo wa trafiki unaoshukiwa.

Jiografia
Geo intelligence yaRamani ya maeneo ya wageni kando na bar ya kila nchi.Geo intelligence yayoursite.comWageni wa eneoMarekani ya MarekaniUingerezaDEKwa hiyoya ya1MARKETSNchi, Jiji, Kifaa2PLANLugha na Maeneo3WATCHUsafiri wa ajabu
Ambapo wageni wako wanatoka (kwa nchi, mji na kifaa) kwa masoko ya ukubwa na doa trafiki isiyo ya kawaida.

Nini cha kuona

Orodha ya nchi za juu za bar

Nchi za juu zilizowekwa na hesabu ya mgeni. Bonyeza nchi kuchimba chini kwa data ya ngazi ya jiji.

Nchi ya Pint

Uvunjaji wa Visual wa trafiki kwa nchi. Hover kwa asilimia.

Orodha ya nchi

Kila nchi na wageni katika kipindi cha kuchaguliwa, kuonyesha hesabu ya mgeni, kuhesabu kikao, kiwango cha bounce, na kiwango cha uongofu.

Mji wa drill-down

Bonyeza nchi ili uone ni miji gani ndani ya nchi hiyo ina wageni wengi.

Jinsi ya kutambua GeoIP inavyofanya kazi

OpsIQ detects mgeni eneo kwa njia mbili: (1) Cloudflare geo vichwa. Kama tovuti yako ni nyuma Cloudflare, nchi ugunduzi ni moja kwa moja na sahihi. (2) MaxMind GeoLite2 database. Pakua database bure na configure njia katika Mipangilio. City-kiwango cha ugunduzi inahitajika Geo Lite2-City database, si tu nchi database.

VPN na trafiki ya wakala

Wageni kutumia VPN itaonekana kuja kutoka eneo la seva ya VPN, sio mahali pao halisi. OpsIQ Haiwezi na haipaswi kujaribu kupitisha VPN. Ikiwa unaona mifumo ya nchi isiyo ya kawaida, fikiria kwamba 10-20% Watumiaji wanaweza kutumia VPN.

Mifano ya kazi

Usafiri wa nchi zisizo za kigeni

Kwa mfano:
Unaendesha biashara ya Marekani tu, lakini 30% Usafiri wa umma ni kutoka India.
Nini cha kufanya:

Angalia ukaguzi: (1) Je, wageni hawa halisi? Angalia muda wa kikao na kurasa zilizotazamwa. vikao vifupi sana na bounce ya juu = bots uwezekano. (2) Je, Google itawasiliana na wewe? - Angalia maelezo ya kina. (3) Wanaweza kuwa wateja wenye uwezo katika soko jipya? Ikiwa trafiki ni ya kweli na inayohusika, fikiria kuongeza bei maalum ya India au maudhui.

Kuchaguliwa kwa msaada wa lugha

Kwa mfano:
Unahitaji kujua ikiwa unataka kutafsiri tovuti yako kwa Kihispania.
Nini cha kufanya:

Ikiwa nchi zinazozungumza Kihispania (Hispania, Mexico, Colombia, Argentina, nk) kwa pamoja zinawakilisha zaidi ya hayo. 10% trafiki yako na viwango vya chini bounce, tafsiri ni thamani ya kuzingatia. Pia kuangalia: Je, wageni kutoka nchi hizi kubadilisha kwa viwango sawa na soko lako la msingi?

Mipango ya Msaada wa Mabadiliko ya Mkoa

Kwa mfano:
Unahitaji kuamua masaa ya timu ya msaada kwa maeneo mbalimbali ya wakati.
Nini cha kufanya:

Tumia saa ya joto (kwenye Dashibodi) pamoja na Geo Intelligence. 40% kutoka katika nchi za Ulaya, na 35% Kutoka Marekani, unahitaji chanjo kwa maeneo yote mawili ya wakati. Ramani ya joto inaonyesha hasa wakati kila eneo lina kazi zaidi.

Nchi inatembelewa na wageni lakini hakuna amri

Kwa mfano:
Ujerumani yaonyesha ishara 500 Kwa mwezi huu, wanauza bidhaa zao kwa Sh.
Nini cha kufanya:

Uwekezaji: (1) Je, wao bouncing juu ya bei ukurasa? Labda bei yako si ushindani kwa soko hilo. (2) Je, unasafiri kwenda Ujerumani? Angalia ikiwa ukurasa wako wa usafirishaji unataja Ujerumani. (3) Je, Checkout yako inapatikana katika EUR? fedha mismatch sababu kutelekezwa checkouts. (4) Je, hawa ni wageni kutoka chanzo kimoja ambacho kinaweza kuwa trafiki ya chini?

Kwa nini wageni wanatangaza nchi isiyojulikana?+

GeoIP haijaundwa. Au imewekwa Cloudflare (ambayo inaongeza vichwa vya geo moja kwa moja) au kupakua hifadhidata ya MaxMind GeoLite2 na kuweka njia ya faili katika Mipangilio > Njia ya GeoIP.

Je, ninaweza kuzuia trafiki kutoka nchi nyingine?+

OpsIQ Haizuiwi na nchi. Tumia seva yako ya wavuti au Cloudflare Sheria za firewall kwa kuzuia nchi.OpsIQ Inazingatia kuonekana, sio udhibiti wa upatikanaji katika ngazi ya mtandao.

Uchambuzi

Intiv ya funnel

Funnel ya Intent inaainisha vikao vya wageni kwa kile wanachoonekana kuwa wanajaribu kufanya: kuvinjari, utafiti, kulinganisha, kununua, kupata msaada, au kuondoka. Tumia kuelewa usawa wa nia kwenye tovuti yako na kutambua ambapo wageni wanaondoka.

Intiv ya funnel
Intiv ya funnelfunnel kutoka Vinjari kwa Utafiti kulinganisha na Kununua na hesabu, pamoja na msaada na kuacha chips.Intiv ya funnelyoursite.comwa wa · 8,200Utafiti wa · 4,100Kulinganisha · 1,650Kununua · 520Msaada wa msaada 6%Kuacha kuondoka 11%1CLASSIFYNini wageni wanataka2STAGESTazama kununua3KurekebishaKupata nje ya
Vikao vilivyoainishwa kwa nia (kuandika, utafiti, kulinganisha, kununua) ili uweze kuona hasa ambapo watu wanaacha.

Aina za ndani

Kukausha

Wageni kwa kawaida kuangalia karibu. vikao fupi, kurasa chache, hakuna lengo maalum lililoonekana.

Utafiti wa

Wageni kusoma kurasa za bidhaa / ushindani, docs, au maudhui ya blogu. muda mrefu kwenye ukurasa, kurasa nyingi za maudhui.

Kulinganisha

Wageni wanaangalia bei, kulinganisha mpango, au meza za kipengele. Mara nyingi wageni wanaorudi.

Kununua

Wageni kwenye checkout, gari, au kurasa za saini. nia ya juu. Hizi ni fursa zako za uongofu.

Msaada wa kutafuta

Wageni kwenye kurasa za usaidizi, kurasa za kuwasiliana, au kuanza kuzungumza. Wanahitaji msaada.

Kukataa

Wageni ambao waliacha baada ya ukurasa mmoja. ushiriki mdogo.

Jinsi ya kusoma funnel

Kuhamisha funnel yako

Kwa mfano:
1,000 Wageni waalikwa wakisikiliza kwa makini. 270 Bonyeza kitufe cha mazungumzo. 92 kuanza kufanya ukaguzi. 64 ya malipo. 18 Kutoa tiketi za msaada.
Nini cha kufanya:

Bei ukurasa ni nguvu ya kutosha kujenga nia. Chat ni muhimu katika njia ya kununua: 27% ya bei wageni kushiriki na kuzungumza kabla ya kununua. msaada tiketi baada ya checkout inaweza kuonyesha uanzishaji au kuchanganyikiwa malipo: (1Kuhakikisha AI chat majibu ya bei maswali vizuri.2(i) Kuchunguza kwa 18 Tiketi za msaada wa baada ya ukaguzi kwa masuala ya kawaida.

Muda wa filters

Tumia kichujio cha tarehe ili kulinganisha mwelekeo wa nia katika vipindi. Kwa mfano, linganisha wiki ya Ijumaa Nyeusi hadi wiki ya kawaida. Unapaswa kuona spike katika "kununua" dhamira na uwezekano wa "Kutafuta Msaada" ikiwa matangazo yako yameunda mkanganyiko.

Jinsi ya kufanya OpsIQ Je, una malengo ya kitaaluma?+

OpsIQ Angalia ukurasa URLs, tabia ya kikao, na mwelekeo wa wakati. Bei za kurasa zinaonyesha nia ya kulinganisha. Kurasa za Checkout zinaashiria nia ya kununua. Msaada / kurasa za mawasiliano zinaunga mkono dhamira. Uainishaji ni msingi wa heuristic, sio inayotokana na AI.

Ninawezaje kurekebisha mipangilio ya malengo?+

Sio sasa. makundi ni kujengwa katika msingi wa mifumo ya kawaida ya tabia ya mtandao. Custom dhamira uainishaji ni juu ya ramani ya barabara.

Uchambuzi

Furaha, uhifadhi na njia

Kujenga safari za desturi kutoka ukurasa au hatua za tukio, kupima uhifadhi wa kikundi na kugundua njia ambazo wageni mara nyingi huchukua kupitia tovuti.

Bidhaa ya Screen
Furaha yafunnel desturi maonyesho kila ukurasa / tukio hatua, wageni waliobaki na asilimia ya uongofu.Furaha yaNafasi ya KaziSTEPS4CONVERSION28.4%WINDOW72hMaisha ya kazi ya VIEWBei ya kuangalia1,420 Wageni wa wageni100%Mpango wa kuchaguliwa780 Wageni wa wageni54.9%Ukaguzi waanza530 Wageni wa wageni37.3%Utaratibu wa kukamilika403 Wageni wa wageni28.4%1DEFINEChagua kuchagua 2–8 Hatua za hatua2Rahisi yaKugeuza Windows3Uendelezaji waKupata nje ya mstari mkubwa
funnel desturi maonyesho kila ukurasa / tukio hatua, wageni waliobaki na asilimia ya uongofu.

Furaha ya

Kuzalisha kwa jina la VAR 2 Kwa ajili ya 8 Weka dirisha la uongofu kwa masaa; mgeni anahesabu tu wakati hatua zilizoamriwa zinatokea ndani ya dirisha hilo. Tumia kushuka kati ya hatua za kuchagua wapi pa kukagua replay, makosa, kasi ya ukurasa au ujumbe.

Ugani wa

Kuhifadhi makundi wageni katika cohorts kila wiki na inaonyesha jinsi wengi kurudi. 6, 8 au 12 wiki angani. Kuhifadhi ufafanuzi cohort imara wakati kulinganisha releases au kampeni.

Njia ya

Njia zinaorodhesha mlolongo wa ukurasa wa kawaida. Chagua urefu wa njia kutoka 2 Kwa ajili ya 5 kurasa ili kuweka matokeo readable. Tumia kupata detours zisizotarajiwa, exits kawaida na maudhui kwamba mara kwa mara kabla ya uongofu.

Vyombo vya kawaida ni ufafanuzi wa uchambuzi, sio automatiserings. Ili kukabiliana na hatua iliyokamilishwa, kuunda lengo la uongofu, sehemu, kuchochea au kazi ya kazi.

Uchambuzi

Rekodi ya kikao

Session Replay inakuwezesha kuangalia ratiba ya kile mgeni alifanya kwenye tovuti yako: mambo ambayo wao clicked, jinsi walivyopiga kura, ambapo wao hovered, na nini wao aina (pamoja na maeneo nyeti masked).

Rekodi ya kikao
Rekodi ya kikaoMchezaji wa replay kuonyesha ukurasa wa mtazamo na mshale, jopo la maelezo ya kikao, na scrubber ya wakati.Rekodi ya kikaoyoursite.comKununua sasaSehemuUrefu wa 3m 12s14 Clicks yaMarekani · DesktopChrome 1241WATCHBonyeza, scroll, aina2MASKEDMaeneo ya siri yaliyofichwa3DIAGNOSEKuthibitisha taarifa za BBA
Replay hasa kile mgeni alifanya: bonyeza, scrolls, kuchapa (maeneo nyeti masked), kwenye skrini ya wakati.

Kupata Mkutano wa Haki

Kutoka ukurasa wa Sessions, angalia vikao na masuala yaliyoripotiwa, makosa ya ukurasa wa juu bila uongofu wowote, au vikao kutoka kwa wateja ambao walifungua tiketi za usaidizi.

Nini cha kufanya replay

Muda wa Timeline

Bar ya usawa inayoonyesha matukio kwa wakati. Bonyeza mahali popote kwenye ratiba ya kuruka hadi wakati huo.

Ukurasa wa urambazaji

Kila ukurasa wa kupakia unaonekana kama sehemu kwenye ratiba. Unaweza kuona njia halisi ambayo mgeni alichukua.

Clicks ya

Matukio ya bonyeza yanaonyeshwa kama dots kwenye ratiba na kama mambo muhimu katika ujenzi wa ukurasa.

Kusonga

Kina cha kitabu kinafuatiliwa ili uweze kuona ni kiasi gani chini ya mgeni kusoma.

Namna ya Kuwasiliana

Mtazamo wa shamba na matukio ya kuandika ni kumbukumbu. pembejeo ya maandishi katika nywila na mashamba nyeti ni masked kwa default.

Ubinafsi na Ubinafsishaji

Kikao cha replay masks nyeti fomu mashamba kwa default. maeneo ya nywila, pembejeo kadi ya mkopo, na mashamba alama na data-opsiq-mask ni kamwe kumbukumbu. Unaweza configure sheria za ziada masking katika Mipangilio > Kufuatilia. Kama sera yako kufuata inahitaji, unaweza Disable replay kabisa.

Kuthibitisha Checkout iliyovunjika

Kwa mfano:
Kuna msemo wa Kiingereza unaosema, “Nilijaribu kununua lakini kifungo hakikufanya chochote.”
Nini cha kufanya:

Tafuta kikao chao katika ukurasa wa Sessions (tafuta kwa barua pepe). Fungua replay. Angalia sehemu ya ukurasa wa checkout.1Je, walikuwa wakivaa mavazi ya heshima?2(a) Je, kulikuwa na JavaScript Makosa hutokea? (Angalia ukurasa wa makosa ya JS kwa wakati huo).3(a) Je, ukurasa huu ulipakia au kuonyesha ujumbe wa hitilafu?4) Je, ni kweli kwamba mchezo wa soka ulikuwa mgumu?

Ni kiasi gani cha kuhifadhi wakati wa kutumia tena?+

Data ya Replay inakua na kiasi cha trafiki. Tumia mipangilio ya uhifadhi ili kusafisha data ya zamani ya replay moja kwa moja. Kwa maeneo ya juu, fikiria kipindi kifupi cha uhifadhi wa replay (kwa mfano, 30 siku) kusimamia hifadhi.

Je, wageni wanaweza kuchagua kutoka kwa kucheza?+

Ikiwa "Uchunguzi Usifuatilie" umewezeshwa katika Mipangilio, wageni na viongozi wa DNT hawarekodi. Unaweza pia kuwatenga kurasa maalum kutoka kwa kucheza tena kwenye mipangilio ya kufuatilia.

Uchambuzi

Matukio ya

Ingia Matukio inaonyesha kila tukio ambalo OpsIQ amerekodi: maoni ya ukurasa, bonyeza, mazungumzo huanza, uumbaji wa tiketi, mauzo, na matukio ya desturi. Tumia ili kufuta ushirikiano, kuthibitisha utoaji wa wavuti, na kuelewa mlolongo wa vitendo.

Matukio ya
Matukio yalogi ya tukio la chronological na badges za aina ya rangi-coded: pageview, chat, mauzo, webhook na desturi.Matukio yayoursite.compageviewya Marekani · /pricing12:04:01chat.start· Wiper yafunguliwa12:04:09Uuzaji wa$49.00 · Kuwa na #104212:05:22Mtandao wa Yahoopayment.succeeded12:05:23customdemo_booked12:06:101EVERYTHINGKila tukio la kumbukumbu2DEBUGKuthibitisha utoaji wa Webhook3ORDERAngalia kwa makini
Muda wa kila kitu OpsIQ Rekodi (maoni ya ukurasa, mazungumzo, mauzo, webhooks, matukio ya desturi) kwa ajili ya kufuta na ukaguzi.

Built-katika matukio (kiotomatiki)

⚠️
Hizi ni events-log Jina la mtumiaji – NiniOpsIQRekodi kwenye ratiba ya mgeni kwa uchambuzi, uchunguzi na ukaguzi. Wao ni msamiati tofauti kutoka Tovuti ya Nje Matukio unajiunga na mwisho wa. Kama wewe ni kujenga webhook mpokeaji, kutumia orodha katika sehemu ya Webhooks, au simu webhooks.events.list; kuingia kwa jina kutoka kwenye meza hii haitatoa chochote.

Kila rangi ina jina lake Tuma ujumbe Majina ya CantonOpsIQ Maduka ya maduka Wote ni kumbukumbu: jina mbichi wewe alimtuma, na moja ya kanuni ambayo ramani kwa, hivyo ripoti imeandikwa dhidi ya kodi kanoni inazidi kufanya kazi yoyote alias tracker kutumika.

pageview page.viewed

Kurasa zilizofuatiliwa ni pamoja na URL, kichwa, referrer na timestamp. page_view Na kwa kuwa view Wanakubaliwa kama kitu kimoja.

chat_open support.chat_opened

Mgeni anakuja na kufungua widget ya chat.

chat_send support.chat_message_sent

Mgeni anatuma ujumbe wa mazungumzo. upande wa jibu unahifadhiwa kama support.chat_message_received.

ticket_open support.ticket_created

Tiketi ya msaada imeundwa. ticket_create kuwa ni sawa na majibu, na kama ilivyo kwa support.ticket_replied Na kwa kuwa support.ticket_closed.

form_submit form.submitted

Fomu ya maombi imeambatanishwa. submit Inakubaliwa kama kitu kimoja.

purchase commerce.purchase_completed

Kununua kwa ajili ya bure. purchase_successna kwa milomo ya wajeni, order.completed, sale.completed, payment.completed Na kwa kuwa invoice.paidWote wanakubaliwa kutoka jukwaa linalounganishwa.

Ukaguzi wa commerce.checkout_started

Kujiandikisha kuanza. Related: cart_view, checkout_view, checkout_intent, checkout_abandon, add_to_cart.

login_success identity.signed_in

Ishara ya kushindwa ni ishara ya kushindwa login_failedkuhifadhiwa kama identity.login_failed-Kutokuwa na lock login_lockout_created.

Usajili conversion.signup

Mgeni anamalizia ishara, kiongozi ni leadkuhifadhiwa kama conversion.lead.

js_error error.js

A yaJavaScriptMakosa yanawekwa kwenye ukurasa uliofuatiliwa.

💡
Jina la tukio unalotuma ambalo sio moja ya haya aliases bado limerekodiwa kitenzi - hakuna kitu kilichopungua. Haina ramani ya canonical, kwa hivyo haitaingia kwenye ripoti za kodi.

Matukio ya kawaida

Unaweza kutuma matukio ya desturi kutoka tovuti yako au seva kwa OpsIQ. Matukio ya Forodha ni muhimu kwa kufuatilia vitendo maalum kwa biashara yako: bonyeza kitufe, matumizi ya kipengele, video ina, downloads, nk.

JavaScript • Matukio ya kawaida kutoka kwa browser
// Send a custom event from the browser
window.OpsIQ = window.OpsIQ || [];
window.OpsIQ.push(["track", "plan_selected", {
  plan: "pro",
  billing: "annual",
  value: 99
}]);
PHP · Rekodi shughuli za mawasiliano kutoka kwa seva yako
// Record a server-side activity for a contact (PHP)
$ch = curl_init("https://your-opsiq-domain.com/api/v1.php");
curl_setopt_array($ch, [
    CURLOPT_POST => true,
    CURLOPT_RETURNTRANSFER => true,
    CURLOPT_HTTPHEADER => [
        "Authorization: Bearer opq_your_key",
        "Content-Type: application/json",
    ],
    CURLOPT_POSTFIELDS => json_encode([
        "action" => "crm.activities.record",
        "site_key" => "site_abc123",
        "email" => "[email protected]",
        "event" => "subscription.upgraded",
        "value" => 50,
        "currency" => "USD",
    ]),
]);
$response = curl_exec($ch);
curl_close($ch);

Kuchuja Matukio

Aina ya Tukio

Filter na majina maalum ya tukio: pageview, chat. started, tiketi. kuundwa, nk

Tarehe ya tarehe

Onyesha matukio kutoka kipindi maalum cha wakati.

Tafuta

Data ya tukio la utafutaji kwa neno muhimu (URL, barua pepe, maadili ya mali ya tukio).

Matukio ya aina gani yanahifadhiwa kwa muda gani?+

Matukio hufuata sera ya uhifadhi iliyowekwa katika Mipangilio. Default: 90 Matukio ya thamani ya juu (ununuzi, matukio ya usalama) yanaweza kusanidiwa na uhifadhi wa muda mrefu.

Je, ninaweza kutumia majaribio ya A / B?+

Ndiyo, wakati wa kuunda jaribio, unachagua tukio la uongofu. Tukio lolote lililojengwa au desturi linaweza kutumika kama lengo la uongofu

Uchambuzi

Jaribio la B

Majaribio yatakupima matoleo mawili ya ukurasa au kipengele na kipimo ambacho mtu hufanya vizuri. OpsIQ nyimbo za hisia, uongofu, na umuhimu wa takwimu.

Jaribio la B
Jaribio la BKadi mbili tofauti kulinganisha viwango vya uongofu, na badge mshindi na umuhimu juu ya lahaja inayoongoza.Jaribio la Byoursite.comAina ya A4.2%Kubadilishana · 1,020 Maoni ya maoniAina ya BWinner ya6.8%Kubadilishana · 1,005 Maoni ya maoni+62% lift · 96% muhimu1ya2 kichwa cha kichwa2Rahisi yaMabadiliko na umuhimu wa3Uamuzi waAkifafanua mshindi wa
Tumia tofauti mbili, angalia uongofu na umuhimu wa takwimu, na utangaza mshindi.

Jinsi majaribio ya kazi

1
Kuundwa kwa majaribio

Ingiza jina la kikundi, na kisha bofya kifungo.

2
Kukimbia kwa

OpsIQ kwa nasibu huwapa wageni anuwai na kufuatilia tabia zao. Usibadilishe jaribio wakati unaendesha.

3
Soma matokeo ya

Baada ya kukusanya data za kutosha, angalia kiwango cha kujiamini.95% Kuwa na uhakika kwamba unaweza kuwa 95% Kwa kweli, tofauti ni ya kweli, sio uwezekano wa nasibu.

Nchi za majaribio

Rasimu ya

Imeundwa lakini bado haijaanza. unaweza kubadilisha anuwai na metrics.

Kuendesha

Kuwapa wageni kwa variants. don t hariri wakati kuendesha.

Imekamilishwa

Ilifikia umuhimu wa takwimu au ilisimamishwa kwa manually. matokeo ni ya mwisho.

Archived ya

Matokeo yamerekebishwa na majaribio hayahitajika tena katika orodha ya kazi.

Mbinu bora za

Kufafanua metrics yako kabla ya kuanza

Chagua kile unachopima kabla ya kuanza. kuchagua metric baada ya kuona matokeo yanaanzisha upendeleo.

Kuhamisha trafiki ya ndani

Ongeza anwani za timu yako ya IP kwenye orodha ya kutengwa ili ziara za wafanyakazi hazitoi matokeo.

Kupumua kwa muda mrefu

Usiacha kufanya jaribio baada ya 100 Unahitaji mamia au maelfu ya wageni kwa kila aina ya matokeo ya kuaminika.

Badilisha moja kwa wakati

Ikiwa utabadilisha kichwa cha habari na rangi ya kifungo, hutajua ni mabadiliko gani yaliyosababisha uboreshaji.

Kuthibitisha uamuzi wako

Baada ya majaribio kumalizika, kumbuka ni aina gani ya kushinda na kwa nini umechagua kutekeleza.

Ni wageni wangapi ninaohitaji kwa ajili ya utafiti wa kweli?+

Inategemea kiwango cha uongofu wa msingi na ukubwa wa athari unayotaka kuchunguza. Kama utawala wa kidole: angalau 500 Wageni kwa ajili ya tofauti 20% Kwa ajili ya athari ndogo, unahitaji maelfu.

Je, ninaweza kufanya majaribio mengi kwa wakati mmoja?+

Ndiyo, lakini kuwa makini. Kama majaribio mawili kuathiri ukurasa huo, matokeo yao inaweza kuingiliana. Ni salama zaidi kwa kukimbia majaribia kwenye kurasa tofauti au vipengele wakati mmoja.

Uchambuzi

JavaScript Makosa ya makosa

JavaScript Makosa hukusanya makosa ya upande wa mteja kutoka kwa wageni wako wa tovuti. kifungo kilichovunjika, kushindwa API Piga simu, au rasilimali iliyopo inaonyesha hapa. Tumia ili kupata na kurekebisha mende zinazoathiri wateja halisi.

Makosa ya JS
JavaScript Makosa ya makosaOrodha ya makosa yaliyochukuliwa mbele na dots kali, faili ya chanzo, vivinjari na matukio.JavaScript Makosa ya makosayoursite.comMakosa ya hivi karibuniAina ya: Haiwezi kusoma x isiyojulikanaPicha zote na Wizara ya Mambo ya Ndani ya Nchi:42 • Chrome ya kawaida×214404 Upakiaji wa upakiaji /assets/app.cssSafari ya safari×88Kukataliwa (katika ahadi)api ya ya :17 • Firefox ya kisasa×51Tahadhari ya Ununuzi: Tukio la UnloadBidhaa za Js · Edge×331CAPTUREMakosa ya Wateja2IMPACTIdadi ya browsers na browsers3KurekebishaSquash halisi ya mende
Wageni halisi kupiga uso wa msimbo uliovunjika hapa (ujumbe, chanzo, kivinjari na mara ngapi) ili uweze kurekebisha mambo.

Nini kila makosa inaonyesha

Ujumbe wa makosa

Nakala ya kosa la JavaScript (kwa mfano, "Mtendaji: Hawezi kusoma mali za isiyojulikana").

Ukurasa wa ukurasa URL

Ni makosa gani ambayo ukurasa huo uliyasababisha.

Browser na vifaa vya

Browser na kifaa aina aliona kosa. baadhi ya makosa ni browser-hasa.

Kukusanya

eneo la msimbo ambapo kosa lilitokea. Bonyeza kupanua kufuatilia kamili ya stack.

Kwanza kuona

Wakati makosa haya ya kwanza yalionekana.

Mara ya mwisho kuona

Wakati makosa haya ya hivi karibuni yalitokea.

Hesabu ya

Ni mara ngapi makosa haya yamerekodiwa?

Mikutano iliyoathiriwa

Ni wangapi watembeleaji walipitia makosa haya.

Kukiri makosa

Sio wote JavaScript Mahitaji ya haraka: (1makosa kwenye kurasa muhimu (checkout, signup, login),2(b) makosa ya hesabu za muda mrefu,3makosa ambayo yalionekana hivi karibuni (yawezekanayo kurejeshwa kutoka kwa mabadiliko ya kanuni),4Makosa kwenye msimbo wako mwenyewe (si maandiko ya tatu).

Kusafisha button ya Checkout iliyovunjika

Kwa mfano:
Ukurasa wa Makosa ya JS unaonyesha "TypeError: Haiwezi kusoma mali ya undefined (kusoma kuwasilisha)" kwenye /checkout, Kuathiri 45 mikutano ya wiki hii.
Nini cha kufanya:

Hii ina maana 45 wateja halisi hakuweza kukamilisha checkout. Hatua: (1) Kufungua ukurasa katika kivinjari / kifaa mchanganyiko huo. (2) Kufungua kivinjari console na kuzalisha kosa. (3) Angalia trace stack kupata mstari halisi ya kanuni. (4) Fix bug, kutumia, na kufuatilia makosa kuhesabu kwenda sifuri.

Kufanya hivyo OpsIQ Je, ni makosa ya waandishi wa tatu?+

Ndiyo, ni OpsIQ Kukamata kila kitu JavaScript Makosa kwenye ukurasa, ikiwa ni pamoja na makosa kutoka kwa scripts za analytics, vilivyoandikwa vya kuzungumza, na maandiko ya matangazo. Filter by URL Katika mstari wa stack ili kuzingatia kanuni yako mwenyewe.

Jinsi ya kuondoa makosa yasiyojulikana?+

Huwezi kuzuia makosa ya moja kwa moja OpsIQ Unaweza kufuta orodha kwa ukurasa URL au kusitisha mimba, ndivyo wanavyo jipongeza na kuzawadiwa na wale waliowatuma.

Mauzo ya bidhaa

Mauzo na ubadilishaji

Kufuatilia mauzo huunganisha duka lako au jukwaa la kulipa kwa OpsIQ ili uweze kuona mapato pamoja na tabia ya wageni. Kila ununuzi unahusishwa na safari ya mgeni ili ujue ni kurasa gani, kampeni, na njia za kuendesha mapato.

Mauzo ya bidhaa
Mauzo ya bidhaaScreen ya Mauzo: jumla ya mapato na udhibiti wa kipindi cha wakati wote, utafutaji, na meza ya Ununuzi wa hivi karibuni (tarehe, mteja, jukwaa, kiasi, chanzo).Mauzo ya bidhaayoursite.comKugeuka$42,180+18%Wakati wote▾Kutafuta barua pepe, IP Taarifa ya utambulisho wa ...Kununua bidhaa za hivi karibuniDhihirisho laSiku ya kuzaliwaMtandaoAa mojaVyanzo vya chanzoJuni 3[email protected]Shopify$49googleJuni 3[email protected]WooCommerce$129directJuni 2[email protected]Stripe$480Matangazo ya matangazo1KugeukaMapendekezo na marekebisho2RECENT PURCHASESTarehe · mteja · kiasi3ATTRIBUTEDKwa chanzo cha trafiki
screen halisi ya Mauzo, mapato juu, kisha Ununuzi wa hivi karibuni (tarehe, wateja, jukwaa, kiasi), kila moja kuhusishwa na chanzo chake trafiki.

Mauzo ya dashibodi

Bidhaa za leo

Mapato kutoka kwa maagizo yaliyokamilishwa leo. Refreshes na kila tukio jipya la utaratibu kutoka kwenye jukwaa lako lililounganishwa.

Wiki hii / mwezi huu / jumla

Mapato ya jumla kwa kipindi hicho, fedha za ziada zimepunguzwa kutoka kwenye jumla hizi.

Mwelekeo wa chati

Mstari wa mstari unaonyesha mapato ya kila siku juu ya aina ya tarehe iliyochaguliwa. Angalia spikes (promotions, kampeni) na dips (masuala, msimu).

Vyanzo vya juu vya kubadilisha

Vyanzo vya trafiki vinavyosababisha ununuzi zaidi. wanunuzi wa "Mkurugenzi" mara nyingi walisajili tovuti yako. "Google" wanunuzi walikupata kupitia utafutaji.

Ununuzi wa hivi karibuni

Amri za hivi karibuni na barua pepe ya wateja, kiasi, sarafu, na vitu vilivyonunuliwa.

Ununuzi usiothibitishwa (safari ya mteja)

Wakati tracker anaona mgeni kufikia uthibitisho wa ununuzi katika browser lakini hakuna jukwaa kushikamana ina taarifa kwamba mauzo bado, safari ya mteja inaonyesha mstari Ununuzi (unconfirmed) na amber badge. Ni kamwe makosa kama mapato.

Upatanisho wa

Mauzo ya viunganisho hayategemei wavuti moja. Kila ishara ya malipo ambayo jukwaa linatuma inaweza kufungua uuzaji, na Mkataba wa Uunganishaji 2.3 inasoma tena orodha ya jukwaa yenyewe ya mauzo yaliyokamilishwa kwenye ratiba (default hourly per workspace) kwa hivyo mtandao ambao haujawahi kutolewa hauwezi kupoteza uuzaji. Wafanyakazi wanaweza kukimbia kwa mahitaji kutoka mstari wa amri na zana / mauzo_reconcile. php.

Mwongozo wa Hosting

Shopify

Nenda kwa wawasiliani >>Shopify Unda App ya Desturi katika Neno lako Shopify admin (Settings > Apps na vituo vya mauzo > Kuendeleza programu).Maeneo ya ruzuku: read_orders, read_customers, read-products. Copy Admin API upatikanaji wa taarifa.Katika OpsIQ Kuingia kwenye akaunti yako (kwa mfano. your-store.myshopify.com) na ishara ya upatikanaji. Bonyeza Uunganisho wa Mtihani. Ikiwa imefanikiwa, kuwezesha webhook sync kwa arifa za utaratibu wa wakati halisi.

WooCommerce

Nenda kwa wawasiliani >>WooCommerce Ndani yako WordPress Mheshimiwa Mwenyekiti, niende kwenye WooCommerce« Mipangilio > Advanced > REST API Unda ufunguo na ruhusa ya kusoma / kuandika. nakala muhimu ya watumiaji na siri ya walaji. OpsIQ Kuingia kwenye tovuti yako URL, muhimu kwa watumiaji na siri ya mtumiaji. Click Test Connection

BigCommerce

Nenda kwa Waunganishaji > BigCommerce.Katika admin yako ya BigCommerce, nenda kwenye Mipangilio ya Juu API Jinsi ya kuunda V2 / V3 API Akaunti na upeo wa kusoma kwa Amri, Wateja, na Bidhaa. nakala ishara ya upatikanaji, kitambulisho cha mteja, na API Kuingia mwenyewe katika yao. OpsIQ ya uchunguzi.

Magento ya 2

Nenda kwa Connectors > Magento. Katika yako Magentoo admin, kwenda mfumo> Ushirikiano. Kujenga ushirikiano mpya na API Upatikanaji wa rasilimali kwa Mauzo, Wateja, na Catalog. Kuhamasisha ushirikiano na nakala ya kuingia ishara. OpsIQ Kuwa na msingi wako wa magento URL.

PrestaShop

Nenda kwa Connectors > PrestaShop.Katika admin yako Presta Shop, kwenda Advanced Parameters > Webservice.Wezesha huduma ya mtandao na kujenga ufunguo mpya. Grant upatikanaji wa amri, wateja, na bidhaa. nakala muhimu na kuingia katika OpsIQ Pamoja na duka yako URL.

OpenCart

Nenda kwenye Mipangilio ya OpenCart. Generate API Ingia kwenye akaunti yako ya iCloud.API URL Jina la mtumiaji, na ufunguo katika OpsIQ· Mtumiaji huyu anatumia mtandao wa OpenCart API kwa ajili ya mawasiliano na data za wateja.

osCommerce

Nenda kwa Waunganishaji > osCommerce. Configure upatikanaji wa database au API sifa kama kumbukumbu katika mazingira kontakt. osCommerce ushirikiano kawaida inahitaji upatikanaji wa database moja kwa moja au desturi API ya moduli.

Stripe

Nenda kwa Connectors > Stripe. nakala yako ya Stripe imefungwa API Mlango wa Dashibodi ya Stripe (Developers)API funguo). mahitaji muhimu kusoma upatikanaji wa wateja, mashtaka, mapendekezo, na usajili. kuingia katika OpsIQ Tumia Webhook endpoint kwa matukio ya wakati halisi.

Mipangilio ya kawaida / majukwaa mengine

Matumizi ya REST API au webhooks kutuma matukio ya mauzo kutoka jukwaa lolote. Tuma ili.kukamilisha matukio na barua pepe kwa wateja, kiasi, sarafu, na vitu. Angalia Matukio API Sehemu ya muundo wa payload.

Kuelewa mauzo yako ya funnel

Vyanzo vya juu vya kubadilisha

Onyesha njia ambazo zinaleta wateja kulipa. ikiwa Google inaleta 1000 Wageni na 50 Biashara, hii ni moja ya5% Kiwango cha ubadilishaji: Ikiwa barua pepe inaingiza 200 Wageni na 30 Biashara, ambayo ni 15% Barua pepe ni ufanisi zaidi kwa wageni.

Malipo ya

Wao kupunguza jumla yako ya mapato ya wavu. Kama viwango vya marejesho ni juu kutoka chanzo maalum, trafiki inaweza kuwa ubora wa chini.

Usimamizi wa Fedha

OpsIQ huhifadhi sarafu ya awali ya shughuli na kiasi. biashara nyingi za bima zinaona mapato katika kila sarafu. taarifa ya kawaida hutumia kiwango cha ubadilishaji kilichopangwa.

Mifano ya kazi

100 Mauzo ya nje, mauzo ya sifuri

Kwa mfano:
Ukurasa wako wa bei unapokea 100 Wageni kwa siku lakini mabadiliko ya sifuri.
Nini cha kufanya:

Uwekezaji: (1) Tumia Session Replay kwenye wageni wa ukurasa wa bei. Tazama jinsi wanavyoingiliana na meza ya bei. (2) Angalia Kurasa za Juu kwa kiwango cha bounce cha ukurasa wa bei na wakati-juu ya ukurasa. (3) Angalia mazungumzo ya kuzungumza kutoka kwa wageni wa ukurasa wa bei. maswali gani wanayouliza? (4) Linganisha ukurasa wako wa bei kwa washindani. (5) Jaribu jaribio la A / B na mipangilio tofauti ya bei.

Mchango kwa kampeni ya masoko

Kwa mfano:
Umetuma kampeni ya barua pepe na vitambulisho vya UTM. Unapimaje athari zake za mapato?
Nini cha kufanya:

Nenda kwa Mauzo na filter kwa chanzo. Tafuta parameter ya kampeni UTM. utaona: (1(a) Je, ni kiasi gani cha fedha kimetolewa kutoka kwenye akaunti hiyo?2(a) Je, ni kiasi gani cha fedha kimetumika katika manunuzi hayo?3(i) Mapato ya jumla yanayotokana na kampeni.4(i) Kulinganisha na kipindi hicho kabla ya kampeni.

Kwa nini bidhaa za kuuza nje zina thamani ya sifuri hata kama kampuni yangu ina viwango vya chini?+

Angalia kwa makini: (1) Je, mtandao wa jukwaa umeunganishwa na afya? kwenda kwa Connectors na kuangalia hali.2) Je, si webhook sync enabled? Kama kutumia kura ya maoni, ni kazi cron mbio?3· Je, Muungano una haki ya API Kwa ajili ya? Shopify Unahitaji kusoma / amri.

Jinsi ya kufanya OpsIQ Je, unauza bidhaa kwa mgeni?+

Wakati amri inakuja kupitia kiunganishi, OpsIQ inalingana na barua pepe ya mteja kwa mgeni anayejulikana. Ikiwa mgeni alifuatiliwa kabla ya ununuzi, uuzaji huo unahusishwa na safari yao ya wageni, ikiwa ni pamoja na chanzo cha trafiki, ukurasa wa kutua, na historia ya kikao.

Ninawezaje kuongeza mauzo ya manually?+

Unaweza kutuma matukio ya mauzo kupitia REST API au webhooks kutoka mfumo wowote. muundo wa tukio ni kumbukumbu katika matukio API Sehemu ya.

Biashara ya Biashara

Kujenga, kuzindua na kuendesha Hifadhi ya asili

Duka la duka ni duka la asili la_ OpsIQ kwa bidhaa, kurasa, vitabu vya kuangalia, paneli za uendelezaji, checkout, akaunti za wateja na uuzaji wa usaidizi wa AI katika Chat ya Mteja na vituo vya kijamii vinavyounga mkono.

Kuanza katika masoko→Ukumbi wa Storefront

1
Chagua eneo la kazi

Hakikisha tovuti unayosanidi. Bidhaa, mipangilio, kurasa, maagizo na uchambuzi ni pekee kwa nafasi hiyo ya kazi.

2
Kuwezesha Biashara ya eCommerce na Shopify

Mipangilio ya jumla → Ecommerce ni mamlaka mzazi. Uchapishaji wa Storefront, uundaji wa utaratibu na malipo hubakia tofauti ili uweze kutazama orodha salama.

3
Kuchapisha bidhaa kamili

Weka aina ya bidhaa, bei, sarafu, hesabu, anuwai / maoni, vyombo vya habari na utimilifu. Preview bidhaa na chaguo za checkout kabla ya kuchapisha.

4
Kuthibitisha malipo na utekelezaji

Kuunganisha lango au kuongeza uhamisho wa benki, fedha au malipo ya kukabiliana. bidhaa za kimwili zinahitaji maeneo ya utoaji au ukusanyaji; bidhaa za digital zinahitaji faili zilizohifadhiwa au codes.

5
Kuharakisha kusoma

Weka kila blocker na kukagua kila onyo, kisha kukamilisha utaratibu wa sandbox kutoka duka la umma.

Mwanzo wa Maudhui na Sera

Maduka mapya na yaliyoboreshwa hupokea maandishi ya mwanzo ya kuhariri Kuhusu sisi, Vigezo na Masharti, Faragha ya faraghaKwa hivyo, na Kurudisha na kurudisha Wakati wa kupanda mbegu, hakuna haja ya kumwagilia.

  • Kugeuka kila mmoja [Add …] Haraka na kwa haraka Mafunzo ya awali Kufahamu kabla ya kuanza.
  • Tumia jina halisi la kisheria, njia ya kuwasiliana, ahadi za kutimiza, sheria za kurudi, mazoea ya data, vipindi vya uhifadhi na masoko yaliyotumiwa.
  • Kupata ushauri unaofaa kwa bidhaa na nchi unazotumikia. Mwanza ni mwongozo wa uendeshaji, sio ushauri wa kisheria.

Design, kurasa na matangazo

Mandhari na Design ya ukurasa

Chagua mandhari ya rangi iliyohifadhiwa na muundo, kisha tune typography, fills /gradients, maumbo, upana, mwendo, hover na mwanga /dark tabia. Preview desktop na simu kabla ya kuokoa.

Kuhusu, Kuwasiliana, Showcase / Lookbook na Akaunti

Kujenga kila ukurasa kutoka vitalu vinavyoweza kurekebishwa. Kila block ina anuwai ya kubuni ya premium. Weka vizuizi vya kufanya madai kama vile takwimu, timu, tuzo au nukuu hadi maudhui yao ni kweli.

Ukurasa wa kawaida

Weka kichwa, slug, shujaa, SEO na kuamuru vitalu; preview wakati rasimu, kisha kuchapisha. njia za kuhifadhi zimehifadhiwa kama vile gari, checkout, akaunti na sera haziwezi kutumika tena.

popups na paneli za upande

Unda ukurasa wa modal na angalau block moja. Chagua muundo wa premium, katikati / kushoto / kulia / chini ya uwekaji, mzigo / delay / exit / bonyeza trigger, nyuma, mwendo, upana, coupon na tabia ya mara kwa mara ya mgeni. mtihani karibu, keyboard na mpangilio wa simu.

Mavazi ya juu na footer

Link kwa kurasa, bidhaa, makusanyo, sera, akaunti / msaada / vitendo vya gari, modals ya kuishi au salama nje URLs. vitu vya kichwa vinaunga mkono kiwango kimoja cha kushuka /mega-menu.

Wateja Chat na maagizo ya kijamii

Kuwezesha Mteja Chat kuuza, kisha kuchagua ambapo wateja wanaweza kununua. Msaidizi hutafuta orodha na anauliza server kwa quote mamlaka; seva-si mfano-huunda kadi saini ya utaratibu. uthibitisho hutokea tu kupitia kadi hiyo kwenye mtandao au mwingiliano kuthibitishwa kwenye kituo cha kijamii.

WhatsApp, Messenger, Instagram, Telegram, LINE, SMS na X matumizi ya mtoa-kuthibitishwa channel akaunti kama utambulisho channel. Barua pepe bado ni kukusanywa kwa ajili ya risiti. Connector ili inabakia yake kusainiwa mkataba wa kimataifa na mfanyabiashara mamlaka jumla; Storefront Configuration haina kubadili kwamba mkataban.

Uchambuzi wa akili

Mapitio ya wageni wa kipekee, maoni ya bidhaa, nyongeza za gari, checkout huanza / abandons / makutano, uongofu, maagizo yaliyothibitishwa, mapato kwa sarafu, ununuzi, vifaa, nchi / maeneo, bidhaa za juu, kupona na maonyo ya ubora wa data. Ubadilishaji hutumia wazi matukio ya umma-Store; jumla ya fedha kamwe haijumuishi kimya.

Jenerali MkuuOpsIQ API

Tumia kichwa cha habari kwa mkono commerce.read; analytics.read Pia hutoa snapshot ya uchambuzi. nafasi ya kazi muhimu ni mamlaka.

Aina ya Storefront
{ "action": "commerce.storefront.get" }
{ "action": "commerce.storefront.catalog.get" }
{ "action": "commerce.pages.list", "kind": "modal", "status": "live" }
{ "action": "commerce.analytics.snapshot", "range_days": 30 }
{ "action": "commerce.readiness.get" }
{ "action": "commerce.products.list", "filters": { "active": true } }

Storefront kupata kurudi umma salama Configuration, URL, menus na starter-mapitio ya hali. Storefront catalog kurudi kila mandhari, kubuni ukurasa, aina kuzuia, kuzuia muundo na premium kukuza shell hivyo remote wajenzi kamwe ngumu-code chaguzi. Ukurasa orodha kurudi kurasa desturi na modals premium. Analytics kurudi jumla bila utambulisho wa mteja. Postman kutumia mikataba hii hiyo.

Mwisho wa kuanza kwa gari

  1. Desktop na simu: nyumbani, utafutaji, bidhaa / gari, uthibitisho wa checkout, akaunti, kufuatilia, downloads, Kuhusu, Mawasiliano, sera, kitabu, kurasa, menus na kila uendelezaji wa kuishi.
  2. Jaza malipo moja ya sandbox na kuthibitisha hali ya utaratibu, risiti, hisa na utimilifu.
  3. Weka moja ya wateja Chat utaratibu na mmoja mtoa huduma-sandbox amri juu ya kila kuwezeshwa kijamii channel.
  4. kuthibitisha matukio hayo kuonekana chini ya uso sahihi na fedha katika Hifadhi Intelligence.
⚠️
Nakala ya sera ya Starter hufanya duka lisilo la kuuza, lakini haifanyi nakala ya kisheria upya. Uzinduzi wa Usomaji unaendelea kuonya hadi kila haraka itakapobadilishwa.
Mauzo ya bidhaa

Viongozi wa

Viongozi ni wageni au wateja ambao wanaonyesha kununua au kuunga mkono nia. OpsIQ hutambua moja kwa moja inaongoza kwa kuzingatia tabia: ziara za ukurasa wa bei, ziara za kurudi, mwingiliano wa mazungumzo, kuanza kwa checkout, na ushiriki mkubwa. Tumia ukurasa wa Leads ili kuweka kipaumbele kufuatilia na kulisha bomba lako la CRM.

Viongozi wa
Viongozi waScreen ya Kiongozi: meza inayotafuta na IP/email, eneo, kifaa, chanzo na safu za tovuti, na chanzo cha juu na nchi.Viongozi wayoursite.comUtafutaji wa Kutafuta IP Mji mkuu, nchi ...Chanzo: Google · Nchi ya Juu: MarekaniIP ya EMAILMkutano waFuraha yaVyanzo vya chanzoMuda wa muda41.62.10.4Uingereza · LondonSimu ya Mkono Mobilegoogle4 M4M 12s[email protected]Marekani · New YorkDesktopdirect7 m2 wa 02s[email protected]Berlin ya KatiSimu ya Mkono MobileTag: ya5 m 40s203.0.113.9• Kuwa TorontoDesktopgoogle3 m3 wa 28s1DETECTEDWageni wa juu2TOPVyanzo vya msingi na nchi3ENRICHEDIP Mahali, mahali, wakati
Screen halisi ya Kiongozi, wageni wa juu kama meza inayoonekana (IP/ barua pepe, eneo, kifaa, chanzo, wakati kwenye tovuti) na vyanzo vya juu na nchi.

Nini hufanya uongozi

Ziara za ukurasa wa malipo

Wageni ambao wanaona bei yako au ukurasa wa mipango wanazingatia kikamilifu ununuzi.

Ziara ya kurudi

Wageni ambao kuja nyuma mara nyingi ni kushiriki lakini bado waongofu.

Mazungumzo ya mazungumzo

Wageni ambao kuanza kuzungumza ni kikamilifu kutafuta msaada, ama kabla ya ununuzi au baada ya kununua.

Ukaguzi wa kuanza

Wageni ambao wanafikia ukurasa wa checkout lakini hawakamilishi ununuzi.

Fomu ya Maombi

Wageni ambao wanawasilisha fomu ya kuwasiliana, ombi la demo, au fomu ya usajili.

Ushirikiano wa ukurasa

Wageni ambao wanaona kurasa nyingi na muda wa kikao cha muda mrefu wanachunguza sana.

Mwongozo wa Paneli ya Maelezo

Bonyeza yoyote ya kuongoza kuona profile yao kamili:

Utambulisho wa utambulisho

Jina, barua pepe, kampuni ikiwa inajulikana. Anonymous inaongoza show IP na mahali.

Mkutano wa

Vikao vyote kutoka kwa kuongoza hii na mtiririko wa ukurasa, muda, na chanzo.

Ukurasa wa Kuangalia

Kila ukurasa ambao walitembelea, uliamriwa na recency.

Chanzo

Jinsi walivyokupata: kikaboni, kulipwa, kijamii, rufaa, moja kwa moja.

Matokeo ya alama

A ya0-100 alama kulingana na kiwango cha tabia, usahihi, na nia ya ukurasa.

CRM ya hali ya

Kama mwongozo huu umeongezwa kwa CRM kama mawasiliano au mpango.

Bidhaa za tip

Maoni yaliyotokana na AI juu ya nini cha kufanya baadaye (kwa mfano, "bei iliyoonyeshwa"3 ^ Au “msisitizo wa muda mfupi.”

Kiwango cha juu cha ubora wa badge

Inaongoza na alama juu ya 80 kupata "Thamani Kuu" bege. Hizi ni matarajio yako ya moto zaidi. Kuwapa kipaumbele kwa kufikia, kuzungumza kwa ufanisi, au kuingia kwa bomba la CRM.

Mifano ya kazi

Kufanya kazi kwa uongozi wa moto

Kwa mfano:
Angalia ukurasa wako wa bei 3 Nyakati za wakati 2 Siku, ilianza kuzungumza juu ya mipango ya biashara, lakini haijanunua.
Nini cha kufanya:

Hii ni hatua ya juu: (1) Angalia maelezo yao ya kuongoza kwa kampuni na taarifa za jukumu. (2) Angalia nakala ya mazungumzo kwa mahitaji maalum na pingamizi. (3) Kuanzisha biashara katika CRM kwa taarifa zilizokusanywa. (4) Fanya kazi ya kufuatilia kwa mwanachama wa timu ya mauzo. (5) Ikiwa watarudi kwenye ukurasa wa bei, utawala wa mazungumzo ya ufanisi unaweza kusababisha ujumbe wa kibinafsi.

Kubadilisha anonymous inaongoza kwa CRM mawasiliano

Kwa mfano:
Wewe kuwa na 50 anonymous inaongoza kwa alama ya juu lakini hakuna anwani za barua pepe.
Nini cha kufanya:

Uchaguzi wa: (1) Kujenga utawala wa ufanisi ambao hutoa punguzo au kupakua rasilimali kwa kubadilishana barua pepe kwenye kurasa za juu. (2Tumia widget ya kuzungumza kuuliza barua pepe wakati wageni wasiojulikana wanaanza mazungumzo.3Ongeza ishara ya utambulisho kwenye kurasa zako za kuingia / saini ili wageni wa kurudi wanatambuliwa moja kwa moja.

Jinsi ya kuhesabu alama ya msingi?+

Alama inaona: usahihi wa ziara (recent = juu), mzunguko wa ziara(zaidi = zaidi), kurasa zilizotazamwa (kuzingatia / kuangalia = juu) muda wa kikao (muda mrefu = juu, mwingiliano wa kuzungumza (ikiwa ni pamoja = juu); na kurudi ziara (madarasa mengi = juu).

Ninawezaje kuunda kanuni za usimamizi wa wingu?+

Ndio. katika CRM Configuration, unaweza kuongeza kanuni za kuongoza-kuongeza alama kulingana na maneno maalum, matukio, vyanzo, au mwelekeo wa ukurasa.

CRM

CRM yako · Kuanza hapa

OpsIQ meli kamili ya AI-kwanza CRM ambayo inachukua ukweli wa wateja, husafisha data, alama inaongoza, mikataba ya makocha, mapato ya utabiri, na vitendo, kwa akili ya tovuti, msaada, tiketi, bidhaa na malipo kama graph moja ya kuishi. Kila hatua ya AI ni chanzo, kuelezea, inayoweza kurekebishwa na kupitishwa.

CRM ya juu
Maoni ya CRMPiga simu ya Trust iliyowekwa kwa Copilot kando na kadi nne za wakala wa AI: Steward, Prospector, Retention na Mchambuzi.CRM ya juuNafasi ya KaziImani ya UinjilishajiMwongozo wa MwongozoCopilot yaAutopilot ya magariNi kiasi gani cha AI inafanya mwenyeweDMsimamiziya kukopesha, riba.Kuthibitisha dataSDR yaMatarajio yaKupata na alamaBiashara mpyaRT yaUgani waPicha ya Churn,Kuchochea upyaANWachambuzi waUtabiri wa &Kufafanua idadi ya1AI-FIRSTWafanyakazi wanne wa Wakala2YOU DECIDEHaki miliki ya picha Trust3TRUSTEDChanzo cha habari na re-kubadilishwa
CRM ya kwanza inayoendeshwa na mawakala wa wataalamu wanne, na Piga Trust ambayo huamua ni kiasi gani wanafanya peke yao.

CRM ukurasa wa maelezo

Kituo cha CRM (Command Center)

Kuanza hapa

Screen yako ya kila siku nyumbani: pulse ya mapato, kile AI iligundua, nini ilifanya, foleni ya idhini, hatua zinazofuata, afya ya wakala, na ROI.

Mawasiliano ya

Nguvu

Watu na makampuni katika CRM yako. Kutafuta, filter, alama, na kusimamia maelezo.

Bomba la mafuta

Nguvu

Bodi ya mpango wa Visual na hatua za kuvuta-na-tone, uwezekano wa kushinda, na kufundisha AI.

Utabiri na Ripoti

Nguvu

Utabiri wa daraja la bodi: uliofanywa, uwezekano, kesi bora, na vipindi vya ujasiri na ufuatiliaji wa usahihi.

Maisha ya rafu

Nguvu

Ambapo kila mteja anasimama: kazi, katika hatari, upanuzi tayari, upya kutokana, au churning.

Kujenga CRM yangu

Kujiamini

Eleza usanidi wako wa CRM kwa Kiingereza wazi. OpsIQ inazalisha mpango unaobadilika na inatumika kwa idhini.

CRM Afya ya afya

Ops ya

Ukurasa wa ukaguzi: schema, agents, njia, vitendo vya AI, na hesabu za data za kuishi.

Jinsi ya jinsi OpsIQ Kuhakikisha kuwa uko salama

Kuuliza kabla ya kutenda

Mapendekezo ya AI kwenda kwenye foleni ya idhini. Unakubali, hariri, au kukataa kila mmoja. Hakuna kinachotokea bila kusema kwako.

Kamwe usiandike zaidi ya kuandika

Wakati AI inapendekeza mabadiliko, inaonyesha thamani ya sasa na thamani iliyopendekezwa. data iliyoingia kwa binadamu ina ulinzi wa kuthibitisha.

Kila kitu kinabadilishwa

Kila hatua ya AI imerekodiwa katika jarida. Unaweza kufuta mabadiliko yoyote kwa bonyeza moja.

Kufafanua

Kila mapendekezo ya AI yanaonyesha hoja yake na vyanzo vya data vilivyotumia. Hakuna sanduku nyeusi.

Bonyeza hapa kuanza.

1
Kujiandaa kwa CRM

Bonyeza AI CRM katika urambazaji wa kushoto. Kituo cha Amri inaonyesha hali yako ya sasa.

2
Angalia afya ya CRM

Fungua CRM Afya kuthibitisha schema, mawakala na njia ni tayari.

3
Mawasiliano ya mawasiliano

Ikiwa unaunganisha kazi (Shopify, WHMCS, nk), mawasiliano yanaingizwa moja kwa moja. Vinginevyo, kuagiza kupitia CSV Kwa mfano, fanya manually.

4
Kujenga bomba

Nenda bomba na kujenga bomba yako ya kwanza na hatua (kwa mfano, Kiongozi, Qualified, Pendekezo, Majadiliano, Won, Lost).

5
Ongeza mkataba wako wa kwanza

Unda mpango kutoka kwa kuwasiliana, kuweka kiasi na hatua, na basi Kocha wa Deal kukuongoza.

Je, ninahitaji kutumia CRM?+

CRM ni hiari. OpsIQ inafanya kazi kikamilifu kama kufuatilia + msaada jukwaa AI bila CRM.

Je, CRM inaweza kufanya kazi bila ya kuwa na uhusiano?+

Ndiyo. unaweza kuunda mawasiliano na mikataba manually. Waunganishaji hutajirisha CRM na data ya jukwaa (mipangilio, usajili, tiketi) lakini hazihitajiki.

Ni nini maana ya uaminifu?+

Tabaka la Uaminifu ni mfumo wa usalama unaodhibiti kile AI inaweza kufanya. mode ya Copilot (default): AI inapendekeza, hali ya kibinadamu inakubali.

CRM

nyumbani screen CRM

Kituo cha Amri ni mkutano wako wa kila siku. Fungua kila asubuhi kuona kilichotokea, nini kinahitaji tahadhari, na nini cha kufanya baadaye.

Kituo cha Amri
Kituo cha CRMCRM nyumbani na utabiri / kiwango cha juu / pipeline toggles, KPI iliyopimwa-forecast, na foleni ya pendekezo la AI na Kuingiliana na Kukataliwa kwenye kila mstari.Kituo cha CRMNafasi ya KaziUtabiri wa utabiriKiwango cha kushindaBomba la mafutaKwa mfano, hii Q$74 ya87%Mapendekezo ya · Kupitisha foleniKujenga mpango · Acme $ 24kKutoka kwa mazungumzo na mnunuziKukubalianaKuondolewa kwaHatua ya Nimbus→Mapendekezo ya PendekezoMajibu mazuri yameonekanaKukubalianaKuondolewa kwaKazi ya Kujitegemea · Kufuatilia UpyaHakuna shughuli katika 7 Siku za sikuKukubalianaKuondolewa kwa1TOGGLEUtabiri · Kushinda kiwango · Mkondo2AI PROPOSESKazi, hatua, majukumu3YOU DECIDEKukubaliana au kutokubali
Kituo cha Amri halisi: kubadili kati ya Utabiri, Kiwango cha Kushinda na Bomba, na kufanya foleni ya pendekezo la AI, kupitisha au kufuta mikataba, hatua za hatua na kazi ambazo zinaonyesha.

Nini Kituo cha Treni kinaonyesha

Idadi ya leo

Thamani ya bomba, mikataba ilishinda / kupoteza, inaongoza mpya, mikataba ya kazi, na mwenendo wa mapato, picha ya hali yako ya sasa.

Nini maana ya nini OpsIQ Waliopatikana

Ufahamu uliofunikwa na AI: mikataba iliyokwama, akaunti za hatari, fursa mpya, masuala ya ubora wa data, na ishara za soko.

Nini maana ya nini OpsIQ kufanya

Hatua AI imechukua (katika Autopilot) au mapendekezo (katika Copilot): hatua ya maendeleo, alama updates, mawasiliano utajiri, na uumbaji kazi.

Inahitaji idhini

Kila moja inaonyesha hatua iliyopendekezwa, hoja, na ushahidi.

Hatua inayofuata

Orodha ya majina 10 Mambo muhimu zaidi ya kufanya leo: kufuata mpango wa moto, angalia akaunti ya hatari, utafiti risasi mpya, nk.

Hali ya Msaidizi

Afya ya mawakala wa AI: kukamata, Data Steward, Deal Intelligence, Kocha wa Deal, SDR, Retention. Green = kukimbia, amber = inahitaji tahadhari, nyekundu = makosa.

Matokeo ya matokeo

Ufuatiliaji wa ROI: mikataba inayoathiriwa na AI, wakati uliohifadhiwa, usahihi wa utabiri, na kulinganisha na kazi ya CRM mwongozo.

Asubuhi ya Pasaka Kazi ya Upishi

1
Soma taarifa ya leo

Angalia afya ya bomba na mapato mwenendo, Je, wewe ni juu ya kufuatilia mwezi huu?

2
Weka wazi ratiba ya maombi

Pitia kila pendekezo la AI. Kuchukua hatua salama, hariri ikiwa inahitajika, kukataa mapendekezo mabaya.

3
Angalia nini OpsIQ Waliopatikana

Je, kuna hatari yoyote? - Kuna fursa mpya?

4
Fanya orodha ya hatua inayofuata

Kuanza na kipaumbele cha juu. AI imeweka hizi kwa haraka na athari za uwezo.

Kuamka baada ya muda wa kuondoka

Kwa mfano:
Umekaa kwa wiki moja, nini kimekuingia mpaka ukaondoka?
Nini cha kufanya:

Angalia kituo cha amri na angalia: (1• “Kwa nini OpsIQ“Akaonyesha matendo yote asiyoyatenda wakati wa kutokuwepo kwako.2) "Kuomba kibali" inaonyesha mapendekezo kusubiri kwa tathmini yako.3• “Kwa nini OpsIQ"Angalia mambo ya dharura".4) Weka tarehe ya dashibodi kwa kipindi chako cha kutokuwepo ili kuona mwenendo.

CRM

Mawasiliano, makampuni na mikataba

CRM kuandaa mahusiano yako ya biashara katika vitu vinne: Mawasiliano (watu), Makampuni (mashirika), Mikataba (nafasi za faida), na Kazi (Matendo ya kufuatilia).

CRM vifaa vya
CRM vifaa vyaRekodi ya mawasiliano inayohusishwa na Kampuni, Deal na vitu vya Kazi katika graph iliyounganishwa.CRM vifaa vyaNafasi ya KaziMawasiliano ya mawasilianoMtu · Barua pepe · SimuKampuni ya KampuniaccountsMkataba waFursa ya mapatoKazi ya TaskHatua za ufuatiliaji1OBJECTSMawasiliano, makampuni, mikataba2LINKEDMoja ya graph3TASKSUfuatiliaji wa Pamoja
Vitu vinne vya msingi (mawasiliano, makampuni, mikataba na kazi) vinavyohusishwa katika graph moja ya wateja iliyounganishwa.

Mawasiliano ya

Nini maana ya mawasiliano

Mtu katika CRM yako. Wanaweza kuwa mteja, matarajio, mpenzi, au kuongoza. Mawasiliano na barua pepe, jina, kampuni, vitambulisho, hatua ya mzunguko wa maisha, na alama ya moto.

Kutafuta mawasiliano

Tumia bar ya utafutaji kupata kwa jina, barua pepe, kampuni, au vitambulisho. Kutumia filters: hatua ya mzunguko wa maisha, alama ya risasi, chanzo, nchi, tarehe ya shughuli ya mwisho, mmiliki aliyepewa.

Maelezo ya mawasiliano

Bonyeza kuwasiliana ili kuona wasifu wao kamili: maelezo ya kibinafsi, kampuni, mikataba, shughuli, tiketi, mazungumzo, ziara za tovuti, alama ya kuongoza, na ufahamu wa AI.

Kiwango cha juu

A ya0-100 alama mahesabu kutoka ishara tabia: ziara ya tovuti, ushirikiano wa barua pepe, mwingiliano chat, historia ya ununuzi, na recency. juu = moto.

Makampuni ya makampuni

Zaidi ya tiketi ...
Mawasiliano ya Kampuni

Mawasiliano yanahusishwa na makampuni kwa kikoa cha barua pepe au kazi ya mwongozo. Kampuni moja inaweza kuwa na anwani nyingi.

mikataba ya

Nini maana ya mkataba

Mikataba ina cheo, kiasi, bomba, hatua, kushinda uwezekano, tarehe ya karibu, mmiliki aliyepangiwa, na mawasiliano yanayohusiana / kampuni.

Kushinda uwezekano

Weka manually au mahesabu na AI kulingana na data yako ya kushinda kihistoria. Inaendesha utabiri wa uzito.

Mpango wa Afya

Green (afya), amber (kwa hatari), au nyekundu (kushikamana). Kulingana na mwendo wa shughuli, muda wa hatua, na ishara za ushiriki.

Majukumu ya

Nini wajibu wa

Hatua ya kufuatilia iliyopewa mtu. Kazi zina kichwa, tarehe inayofaa, kipaumbele, aina (wito, barua pepe, mkutano, mwingine), na mawasiliano / mpango uliohusishwa.

Kazi zilizozalishwa

AI inajenga kazi moja kwa moja wakati inagundua kitu inahitaji tahadhari: kufuata mpango uliokwama, kujibu akaunti ya hatari, utafiti wa kuongoza mpya.

Kutafuta Mwongozo wa Moto

Kwa mfano:
Unataka kuona mawasiliano yote ya juu nchini Uingereza ambayo hayajawasiliana hivi karibuni.
Nini cha kufanya:

Nenda kwa Mawasiliano. Filter kwa: alama ya kuongoza > 80^ Tnn., “nchi ya Uingereza, shughuli za mwisho.” 7 Siku zilizopita. Panga kwa alama ya risasi kushuka. Hizi ni njia zako za haraka zaidi zisizopuuzwa, kipaumbele ufikiaji wa kipaumbele.

Kujenga mpango kutoka kwa kuwasiliana

Kwa mfano:
Mawasiliano tu walionyesha nia katika mpango wako wa biashara wakati wa mazungumzo.
Nini cha kufanya:

Fungua wasifu wa kuwasiliana. Bonyeza "Unda mpango." Ingiza jina la mkataba (kwa mfano, "Acme Corp - Mpango wa Biashara"), kiasi, bomba, na hatua (kwa Mfano, "Ingiza"). Weka tarehe ya karibu na uipe mwenyewe.

CRM

Bodi ya Mikopo (Bodi yako ya Biashara)

Bomba ni bodi ya kuona ambapo mikataba inakwenda kwa hatua kutoka kushoto kwenda kulia. Drag na kadi za kushuka ili kuendeleza mikataba. Kila kadi inaonyesha kiasi cha mpango, kushinda uwezekano, na hali ya afya.

Bomba la mafuta
CRM ya mfumo waScreen ya bomba na mikataba ya wazi, thamani ya wazi , takwimu za makadirio ya uzito na sifa, kifungo cha biashara mpya, foleni ya AI Approve, na bodi ya Lead /Qualified / Won.Bomba la mafutaNafasi ya KaziMikataba ya wazi23Thamani ya wazi$128kUtabiri wa uzito$74 yamikataba iliyosainiwa12+ Mkataba mpyaKupitisha foleni2 Kwa ajili ya ukaguziMwongozo waUundaji wa Inc4 yaLume ya6 ya kya uboraNibu ya$ 30 kwa kiloMlima wa Mizeituni9 ya kya waau wa$ 48 ya k1LIVE STATSThamani ya wazi na utabiri wa uzito2AI QUEUEMapendekezo ya mikataba3BOARDKufukuzwa kwa hatua
Screen halisi ya bomba: stats za kuishi (thamani wazi, utabiri wa uzito), foleni ya AI ya Kupitisha kwa mikataba iliyopendekezwa, na bodi ya kuvuta-na-tone.

Kutumia Bodi ya Bomba

1
Angalia mikataba yako

Bomba la mafuta linaonyesha mikataba yote ya kazi kama kadi zilizopangwa katika nguzo (hatua). Kila kichwa cha safu inaonyesha thamani ya jumla ya mikataba katika hatua hiyo.

2
Kuharakisha kwa ajili ya

Drag kadi kwa hatua inayofuata. uwezekano wa kushinda na makosa update instantly. Kama hoja inashindwa (uhalifu wa kibali), kadi snaps nyuma nafasi yake ya awali.

3
Angalia kadi ya mkopo

Beji ya kijani = afya (shughuli za msingi, kwenye track). Amber = katika hatari (kupungua chini, inahitaji tahadhari). Red = imesimama (hakuna shughuli kwa muda mrefu sana).

4
Bonyeza kwa maelezo

Bonyeza kadi kufungua mpango wa kina jopo na mawasiliano, shughuli, Kocha wa Mpango mfupi, na vitendo vya haraka.

Mkutano wa kuidhinisha

Mapendekezo ya AI yanaonekana kwenye foleni ya idhini juu ya ukurasa wa bomba. Kila pendekezo linaonyesha kile AI inataka kufanya, kwa nini na ushahidi. Unaweza:

Kukubaliana

Kukubali pendekezo kama-ni kitendo anaendesha kupitia tabaka la Trust na ni kumbukumbu katika jarida.

Edith ya

Badilisha pendekezo kabla ya kuidhinisha. Kwa mfano, kubadilisha hatua iliyopendekezwa au kurekebisha kiasi.

Kukataa

Kukataa pendekezo hilo, AI inajifunza kutoka kwa kukataa kufanya mapendekezo bora katika siku zijazo.

Uwezekano wa kushinda

Uwezekano wa kushinda unaweza kuwekwa kwa manually au mahesabu na AI. Wakati AI inahesabu, inatumia mfano uliofundishwa kwenye mikataba yako ya kufungwa (iliyoshinda na kupotea). Ikiwa huna data ya kutosha ya kihistoria, AI hutumia uwezekano wa default hatua. $10,000 Makubaliano ya 30% Uwezekano wa kuchangia $3,000 kwa ajili ya "utabiri".

Kujiandaa kwa ajili ya kushinda

Kwa mfano:
Mteja alisaini mkataba na kulipwa.
Nini cha kufanya:

Weka kadi ya biashara kwenye hatua ya "Won". OpsIQ Itakuwa itakuwa: (1) Weka mkataba kama imefungwa. (2) Kusasisha utabiri. (3) Ongeza shughuli za "Won" kwenye ratiba. (4) Ikiwa umepangiliwa, tengeneza tukio la wavuti (crm^ Tnn., “kwa ajili ya.” (5) Inaboresha hatua ya mawasiliano kwa "mteja"

Kushughulikia mikataba ya kudumu

Kwa mfano:
Unahitaji kupata mikataba ambayo imekuwa katika hatua moja kwa muda mrefu.
Nini cha kufanya:

Angalia beji nyekundu (salama) kwenye bodi ya bomba. Mikataba hii haikuwa na shughuli kwa muda mrefu kuliko kizingiti cha kuoza kilichoundwa (iliyowekwa katika Configuration CRM > Bomba). Bonyeza kila mpango uliokwama kuona mapendekezo ya Kocha wa Deal kwa reactivation.

Je, ninaweza kupata idadi ya mayai?+

Ndiyo. kwenda CRM Configuration > Bomba kujenga mabomba ya ziada. kawaida matumizi kesi: mabomba tofauti kwa ajili ya biashara mpya vs upya, au kwa bidhaa / huduma mbalimbali.

Nini kinatokea wakati mimi kuvuta mpango wa "kupoteza"?+

Mpango huo umewekwa alama kama imefungwa-kufungwa. Utaulizwa kwa sababu ya kupoteza. mpango ni kuondolewa kutoka bodi kazi lakini inaweza kupatikana katika mikataba iliyofungwa filter. kuwasiliana bado katika CRM.

CRM

Kuajiri Mafunzo

Kocha wa Mpango anachambua kila mpango na inakupa muhtasari na hali ya afya, ishara za hatari, watu muhimu, orodha ya kufuzu, mkutano prep, na kupendekeza vitendo vya baadaye. Kila kitu kinatoka.

Kocha wa
Kocha waKadi ya mpango inaorodhesha ishara za hatari zilizosababishwa na AI na vyanzo vya ushahidi, kando na mapendekezo ya AI na kifungo cha barua pepe.Kocha waNafasi ya KaziMwili wa Acme Corp $24,000Hatua: Mswada · 60% kushindaIshara za hatariHakuna majibu katika 10 Siku za sikuWaziri Mkuu akaa kimyaKujiandikisha katika chatVyombo vya habari: tiketi #482 · kuzungumza 6/12 · thread barua pepeKwa hiyo, napendekezaKuunganishwa tena kwa uchumiKujiandaa kwa ajili ya mfalme recapAidha, a 7Mpango wa Siku ya Mwisho.Kuwasilisha barua pepe1SIGNALSKwa nini mpango unaweza kuondoka2SOURCEDKila mmoja atimize wajibu wake kwa mujibu wa ushahidi.3HatuaBonyeza moja kwa hatua inayofuata
Kocha anataja kwa nini mpango unaweza kuteleza (kila ishara inanukuu chanzo chake) na mikono yako hatua inayofuata kuchukua.

Nini mwalimu anasema kuhusu wewe

Maelezo ya Afya

Kwa nini mpango huo ni afya, katika hatari, au kukwama. ishara maalum: siku katika hatua, tarehe ya mwisho ya kuwasiliana, mzunguko wa shughuli, kutaja mshindani, mwelekeo wa pingamizi.

Ishara za

Imewekwa katika: pingamizi zilizoinuliwa, kutajwa kwa mshindani, majadiliano ya bei, viashiria vya hatari vya msaada, ishara za upya / kuongezeka. Kila kiungo cha ishara kwenye chanzo chake (kuzungumza nakala, tiketi, barua pepe, shughuli).

Ramani ya blocker

Nani anasaidia mpango (mchanganyiko) na nani anapinga (kuzuia). kulingana na uchambuzi wa mwingiliano na majukumu ya kuwasiliana.

Orodha ya sifa

MEDDICC au orodha ya BANT (inategemea) inayoonyesha vigezo vya kufuzu vinakutana na ambavyo havipo. Daraja: A, B, C, D, au F.

Mkutano wa Prep

Kabla ya mkutano uliopangwa, kocha hutoa muhtasari: ajenda, pointi muhimu za kufunika, maswali ya kuuliza, hatari za kushughulikia, na vifaa vya kujiandaa.

Kuwasilisha na kuwasilisha mipango ya

Alipendekeza ujumbe ujao au kupiga script kulingana na hali ya sasa ya mpango na mwingiliano wa hivi karibuni.

Ushahidi wa Timeline

Kila madai kocha hufanya viungo kwa chanzo: namba ya tiketi, kitambulisho cha maandishi ya mazungumzo, tarehe ya shughuli, au ziara ya tovuti.

Jinsi ya kutumia coach

1
Soma kwa ufupi

Fungua mpango wowote na ufungue sehemu ya Kocha wa Deal. soma hali ya afya na ishara muhimu.

2
Mipaka ya Ufuatiliaji wa Karibu

Ikiwa "Mnunuzi wa Uchumi" hayupo, mpango wa kutambua na kushiriki mmiliki wa bajeti.

3
Hatua ya mapendekezo

Kocha anapendekeza hatua za baadaye. Bonyeza kuunda kazi, rasimu ya barua pepe, au ratiba ya mkutano, wote ulioelekezwa kupitia foleni ya idhini.

Kujiandaa kwa mkutano mkuu

Kwa mfano:
Kesho utakuwa na mkutano wa aina yake $50,000 ya mkataba.
Nini cha kufanya:

Bonyeza hapa na kusoma sehemu ya kwanza ya kitabu cha Mwanzo. (i)1· Masuala muhimu ya mazungumzo yanayojikita katika mahusiano ya hivi karibuni. (2*Maombi ambayo yaliwasilishwa katika kikao cha dharura wiki iliyopita.3(i) Wajumbe waliotajwa katika ibara ya Rasimu ya Katiba.4Maswali ya kuuliza kuhusu wakati wao.)5) Sababu za hatari kushughulikia kwa ufanisi. Tumia kifupi hiki kuandaa ajenda iliyozingatia, ya msingi wa ushahidi.

Fahamu kwa nini biashara yako iko hatarini

Kwa mfano:
Bomba linaonyesha beji nyekundu kwenye mpango ambao unafikiri ulikuwa unaendelea vizuri.
Nini cha kufanya:

Click the deal and read the Deal Coach health explanation. It might say: "This deal has been in Proposal stage for 22 days (threshold: 14). Last contact was 11 days ago. The primary contact opened a support ticket about data migration concerns 5 days ago (ticket #T-892). Suggestion: address the migration concern and schedule a follow-up call." Now you know exactly what to fix.

CRM

Utabiri na taarifa

Utabiri wa daraja la bodi na maelezo ya mabadiliko ya kiwango cha chini, na ufuatiliaji wa usahihi ili uweze kuthibitisha na kuelezea idadi yako.

Utabiri wa utabiri
Utabiri wa utabiriNambari ya utabiri wa robo mwaka na bendi za ahadi, bora-kao na bomba na maelezo ya usahihi.Utabiri wa utabiriNafasi ya KaziTAARIFA YA UCHUMI · THIS QUARTER312 Mshtuko wa87% Kuwa na malengoAhadi yaKesi bora zaidiBomba la mafutaAI-kupimwa na afya ya mpango na historia · usahihi uliofuatiliwa baada ya muda1MakundiAhadi ya kuwa na bomba2AI-WEIGHTEDKwa upande wa afya3PROVABLEUfuatiliaji wa haraka
Kuahidi, kesi bora na bomba kwa mtazamo, AI-ukubwa na afya ya mpango, na usahihi uliofuatiliwa ili uweze kuilinda.

Aina za utabiri

Ahadi ya

Kushughulikia kwa 80% Au uwezekano mkubwa zaidi wa kushinda. Hizi ni ushindi wako unaowezekana zaidi. Hii inapaswa kuwa mapato yako ya chini yanayotarajiwa.

Inawezekana kuwa

Mikataba yote ya wazi iliyopimwa na uwezekano wao wa kushinda AI-kuzingatia. Hii ni utabiri halisi zaidi wa kile utakachofunga.

Kesi bora zaidi

Hii ni kiwango cha juu iwezekanavyo mapato kama kila kitu inakwenda kikamilifu (ni nadra haina).

Kujiamini kwa muda

Mwezi 80% uwezekano bendi kuonyesha mbalimbali halisi. Mfano: "Utakuwa na uwezekani wa kufunga kati ya $45,000 na $72,000 robo hii."

Nini kimebadilika na kwa nini

utabiri ni pamoja na wiki-juu mabadiliko ya attribution. Wakati utabiri wako matone kwa $15,000 Ripoti hiyo inaeleza ni nini hasa kinachohusika na mabadiliko hayo: "Deal A aliteleza hadi robo ijayo".$8,000(b) Kuondolewa kwa Mkataba wa B.$5,000(c) Kupunguzwa kwa thamani (C)$2,000)."

Ufuatiliaji wa Usahihi

Utabiri wa MAPE

Kosa la asilimia kabisa: ni mbali na utabiri wako wa kihistoria. Chini ni bora zaidi.15% Kwa ujumla, matarajio yako ni ya ndani 15% matokeo halisi.

Uwezekano wa kushinda calibration

Brier alama kupima jinsi vizuri kushinda uwezekano mechi matokeo halisi. kama mikataba katika 70% Uwezekano wa kushinda 70% Kwa wakati huu, calibration ni nzuri.

Picha za kila wiki

OpsIQ Hukamata picha ya utabiri wako kila wiki (kupitia cron). Baada ya muda, unaweza kuona jinsi usahihi wako wa utabiri unavyoboresha.

Kuhimiza na kutoa tahadhari

Kubadilisha kwa hatua

Je, ni kiasi gani cha fedha kinachotolewa kutoka kila hatua hadi hatua inayofuata? 80% Kujiandikisha kwa ajili ya maombi, lakini tu 20% Kutoka kwa Mapendekezo ya Majadiliano, mapendekezo yako yanaweza kuhitaji kazi.

Kiwango cha kushinda kwa chanzo

Vyanzo vya kuongoza vinazalisha mafanikio zaidi. kuwekeza zaidi katika vyanzo vya juu vya kushinda.

Utendaji wa Per- Owner

Jinsi kila mwanachama wa timu ya mauzo anafanya: mikataba alishinda, thamani ya bomba, ukubwa wa wastani wa mpango, kiwango cha kushinda.

Tahadhari ya

Sandbagging (uwezekano wa chini usio na ukweli), overcommitting (juu ya kweli), na hatari ya kujitolea (makubaliano ya juu ya uwezekano yanaonyesha ishara za kibanda).

Kuelewa utabiri wa kushuka

Kwa mfano:
Utabiri wako wa robo mwaka umeshuka kutoka kwa $180,000 hadi $155,000 tangu wiki iliyopita.
Nini cha kufanya:

Fungua ukurasa wa utabiri na angalia "Kilichobadilika" ripoti inaonyesha: "Mpango wa Acme Corp ($15,000· Imechaguliwa na mshindi wa Tuzo ya Beta Inc (Bonyeza hapa)$8,000) tarehe ya mwisho ilisukumwa kwa robo ijayo. mpango mpya na Gamma LLC ($3,000· “Mabadiliko ya tabia nchi ni haya:-$20,000 + $3,000 = -$17,000, kuelezea kushuka kutoka $ 180K hadi $163K (na iliyobaki $8K alielezea kwa marekebisho ya uwezekano juu ya mikataba mingine).

CRM

Kutafuta biashara mpya

Wakala wa Kutazamia husaidia kupata na watafiti wateja wanaoweza. Eleza mteja wako bora, kuongeza makampuni ya lengo, na kuruhusu utafiti wa AI, alama, na rasimu ya ufikiaji wa kwanza.

Matarajio
MatarajioOrodha ya makampuni ya matarajio ya AI na maelezo sahihi, alama na kifungo cha nje cha rasimu kila mmoja.MatarajioNafasi ya KaziWaliochaguliwa na wakala wa SDRKaskazini Pemba Ltd.Saa ya · 50 Wafanyakazi · Kuajiri msaada88Mradi wa KuwasilishaMfg ya CobaltUzalishaji · 200 Wafanyakazi wa74Mradi wa KuwasilishaBidhaa ya RetailBiashara ya eCommerce · 30 Wafanyakazi wa69Mradi wa KuwasilishaAfya ya VegaHuduma ya afya · 80 Wafanyakazi wa63Mradi wa Kuwasilisha1FINDAkaunti za Target2MatokeoFit & Nia ya Kuwekwa3DRAFTBarua ya kwanza iliyoandikwa kwa ajili yako
Wakala wa SDR hupata makampuni ya lengo, alama yao inafaa, na inaandaa ufikiaji wa kwanza kwa ukaguzi wako.

Kuundwa kwa wakati mmoja

1
Kuelezea wateja wako bora

Nenda kwa CRM Configuration > Prospecting. Eleza profile yako bora ya wateja (ICP): viwanda vya lengo, ukubwa wa kampuni, majina ya kazi, mwelekeo wa kijiografia, masharti ya mechi za bidhaa, na alama ya chini inayofaa.50-500 Wafanyakazi nchini Marekani / Uingereza, kuuza zana za msanidi programu, na VP ya Mauzo au Mkuu wa Ukuaji kama mawasiliano ya msingi.

2
Kuongeza makampuni ya Target

Ingiza vikoa vya kampuni au majina unayotaka utafiti. Unaweza pia kuruhusu AI kupendekeza makampuni kulingana na ICP yako.

3
Matokeo ya utafiti

AI inatajirisha kila kampuni na data inayopatikana: ukubwa, sekta, stack ya teknolojia, habari za hivi karibuni, na alama inayofaa kwa maelezo.

4
Kuwezesha upatikanaji wa

Kwa makampuni mazuri, AI inaandaa ujumbe wa kugusa wa kwanza wa kibinafsi. Mapitio na kuidhinisha katika foleni.

Kujiandaa kwa ajili ya

Kila matarajio ya kupata a0-100 Matokeo ya mtihani kwa kuzingatia mambo matano:

ICP yajiandaa kwa uchaguzi

Jinsi vizuri kampuni inalingana na wasifu wako wa mteja bora (kiwanda, ukubwa, eneo).

Ishara za dharura

Je, kuna ushahidi wanaohitaji bidhaa yako sasa? matangazo ya kazi, mabadiliko ya teknolojia, malalamiko kuhusu washindani.

Bajeti ya Protokali

Ukubwa wa kampuni, hatua ya fedha na viashiria vya mapato vinapendekeza upatikanaji wa bajeti.

Michezo ya Bidhaa

Ni muhimu jinsi bidhaa yako ni kwa biashara zao kulingana na sekta na teknolojia.

Msaada wa vifaa

Kama unaweza kutumika kwa ufanisi mteja huyu (timezone, lugha, utata).

Kuajiri kampuni ya Target

Kwa mfano:
Hivyo basi, unataka kujua kama acme.com Ni thamani ya kufuatilia.
Nini cha kufanya:

Kuongeza nyongeza acme.com Katika orodha ya kuangalia, AI inarudi: alama ya Fit 78/100 Kwa mfano: B2B SaaS. 120 Wafanyakazi, makao makuu ya Marekani, hivi karibuni waliajiri VP ya Mauzo (ishara ya dharura), hutumia mshindani X (mchezo wa bidhaa). Kununua ishara: alitembelea ukurasa wako wa bei mara mbili mwezi uliopita (kutoka kwa ufuatiliaji wa tovuti). [email protected] (VP ya Mauzo) Iliyoandikwa wazi inarejelea ziara zao za hivi karibuni za kukodisha na bei.

CRM

Ufuatiliaji wa moja kwa moja

Sequences automate hatua mbalimbali zifuatazo: mchanganyiko wa barua pepe, kusubiri, kazi, wito, na hatua webhook kwamba kukimbia moja kwa moja baada ya kupitisha kutuma awali.

Uingiliaji wa
kufuatilia-up mfululizomtiririko wa mlolongo wa usawa: Barua pepe, kusubiri siku tatu, barua pepe, kisha kazi, na kutambua jibu.kufuatilia-up mfululizoNafasi ya KaziBaada ya kupokea barua ya kwanza→Barua pepeNdani yaNgoja tusubiri3 Siku za sikuBarua pepeUfuatiliaji waKazi ya TaskWito wa witoHatua zinaweza kuwa barua pepe, kusubiri, kazi au webhook. Jibu auto-stops mlolongo.1AUTOMATEUfuatiliaji wa hatua nyingi2STEPSEmail · kusubiri · kazi · webhook3YOU APPROVEUjumbe wa kwanza ni kupitiwa
Ufuatiliaji wa hatua mbalimbali (Email, kusubiri, barua pepe, kazi) ambayo unaidhinisha kwanza na jibu linaacha moja kwa moja.

Jinsi ya kufanya kazi

1
Kujenga mlolongo

Fafanua hatua: barua pepe, kusubiri siku 3, baruapepe, kusubira siku _5, kazi (mwito kama hakuna jibu), barua. Kila hatua ya barua ina template unaweza kubinafsisha.

2
Kuunganisha mawasiliano

Ongeza anwani kwenye mlolongo. AI inaweza pia kupendekeza usajili kutoka kwa matokeo ya utafutaji.

3
Utekelezaji wa moja kwa moja

Hatua zinaendesha moja kwa moja kwenye ratiba. Ikiwa majibu ya mawasiliano wakati wowote, mlolongo hupumzika kiotomatiki.

4
Matokeo ya kufuatilia

Angalia viwango vya wazi, viwango vya majibu, viwango Vya uongofu, na unsubscribes kwa hatua. Tumia hii ili kuongeza mlolongo wako.

Majibu ya kuelewa

Wakati wa kuwasiliana, AI inaainisha jibu:

Mafanikio ya

Kuvutiwa, anataka kuzungumza. kupumzika kwa muda, kazi iliyoundwa kwa ajili ya kufuatilia.

Kukataa

Ina wasiwasi lakini sio kukataa. mapumziko ya kutosha, kazi iliyoundwa na maelezo ya pingamizi.

Ukusanyaji wa

Kukataa kupokea ujumbe, mawasiliano ni kusimamishwa kwa kudumu.

Sio sasa

Kuvutiwa lakini wakati ni makosa. mapumziko ya kutosha, kazi snooze kuundwa.

Mtu mbaya

Si kuwasiliana sahihi. Sequence kuacha, kuwasiliana flagged kwa ajili ya ukaguzi.

Msaada wa msaada

Swali la msaada, sio majibu ya mauzo. mapumziko ya muda mfupi, tiketi iliyoundwa.

Ulinzi wa Anti-spam

Usimamizi wa Opt

Maombi ya kujiunga yanaheshimiwa mara moja na mawasiliano huzimwa kutoka kwa mlolongo wote wa baadaye.

Kila siku ya cap

Kiwango cha kila siku cha kazi (default: 1,000 barua pepe) huzuia kutuma wingi ambao husababisha filters za spam.

Kiwango cha Mawasiliano

Upeo wa juu 1 Ujumbe kwa kila siku, kuzuia watu wengi.

Usimamizi wa juu

Hatua zinazozidi cap ya kila siku zinaahirishwa hadi siku inayofuata. hazipungui au zimeruka.

Nini kinatokea ikiwa mtu anafungua tiketi ya msaada wakati wa mlolongo?+

Utaratibu wa pause moja kwa moja. Msaada unachukua kipaumbele juu ya ufikiaji. mlolongo unaweza kurudiwa tena baada ya suala la msaada kutatuliwa.

Je, ninaweza kupata A / B mtihani wa mzunguko?+

Si moja kwa moja ndani ya mlolongo, lakini unaweza kuunda mlolongo mbili na ujumbe tofauti na kulinganisha matokeo yao.

CRM

Vifaa vya maendeleo

Ukurasa mmoja chini ya CRM ambayo inashikilia injini ya ukuaji: mapato ya mara kwa mara (MRR / ARR), orodha ya bidhaa, fomu za kuchukua uongozi, viungo vya uhifadhi na kuongoza routing. Kila kitu hapa kinaandika moja kwa moja kwenye CRM, hivyo uwasilishaji wa fomu au wito uliokatwa ni kuwasiliana na historia, sio mstari katika spreadsheet.

Nini cha kufanya kwenye ukurasa

Mapato ya mapato

Mapato ya mapato

MRR na ARR makadirio kutoka yako halisi bili ledger. usajili ni kundi kutoka malipo kwa kila jukwaa, mzunguko wa kulipa ni inferred kutoka mapungufu ya malipo, na lapses michango wakati malipo ni overdue iliyopita 1.5 Mara mzunguko wake. Wateja kuunganisha na CRM mawasiliano moja kwa moja wakati ledger hubeba barua pepe zao.

Bidhaa ya catalog

Orodha ya

Chanzo kimoja cha ukweli kwa kile unachouza. Quotes kuvuta jina na orodha ya bei kutoka catalog, na quotes kukubalika roll up katika mapato na bidhaa. Bidhaa nyaraka, wao kamwe kufuta.

Fomu za Captre

Kukamatwa kwa

Kila fomu inapata ukurasa wa mwenyeji pamoja na msimbo wa iframe embed kwa tovuti yako mwenyewe. Mawasilisho kuwa mawasiliano, mmiliki anapata taarifa, na sheria zako za uendeshaji zinawapa kuongoza.

Viungo vya Kitabu

Kujiandaa

Kushiriki kiungo, basi matarajio kuchagua yanayopangwa bure. Slots heshima ya masaa ya kazi mratibu, timezone na mikutano zilizopo. booking inajenga mkutano, barua pepe matarajio kuthibitisha na taarifa mratibu.

Mwongozo wa Routing

Routing ya

Sheria za wilaya zinaendesha kwanza, basi sheria za shamba (vinavyolingana na uwanja kama vile nchi au chanzo), kisha kuzunguka-robin katika bwawa lako la rep. Inaunganisha Mawasiliano na DEALS sawa, chochote hali ya mpango: mpango wa kushinda bado unahitaji mmiliki wa ugawaji wa tume, wajibu wa akaunti na ufuatiliaji, na kwa mmiliki au mode ya kuonekana kwa timu rekodi isiyomilikiwa haionekani kwa kila mtu lakini Meneja. Records iliyoundwa na automatisering (kuuza kiungo, kuzungumza, kuagiza) hubeba hakuna muumbaji anayeingiliana, hivyo wanachukuliwa na sheria hizo badala ya kuunda kitu ambacho tayari kimeachwa.

Kujenga fomu yako ya kwanza

1
Vyombo vya maendeleo ya wazi

Nenda CRM, kisha Tools Growth, kisha sehemu ya fomu ya kuongoza.

2
jina na kisha kuchukua nafasi ya

Andika jina na orodha ya uwanja iliyojitenga, kwa mfano jina, barua pepe, ujumbe. Barua pepe daima inahitajika.

3
Kugawana au kujumuishwa

Nakili kiungo kilichohifadhiwa ili kushiriki mahali popote, au nakala msimbo wa kuingizwa na kuiweka kwenye ukurasa wowote wa tovuti yako.

4
Tazama Mwongozo wa Kuwasili

Kila uwasilishaji ni mawasiliano ya CRM na fomu. shughuli zilizotumwa, taarifa ya mmiliki, na uendeshaji wa moja kwa moja.

💡
Kurasa za kukamata umma hutumia anwani yako ya workspace. nafasi za kazi za wingu hutumia subdomain yao (kampuni.opsiq. help), kwa hivyo kiungo daima hutatua data sahihi.

Ulinzi wa ndani

Mafanikio ya macho yako, huwezi kuona chochote

Eneo la asali lililofichwa huacha maoni ya bot.

Kiwango cha chini

10 kwa kila saa IP Kushughulikia fomu na bookings.

Kukubaliana kwa uaminifu

Kuwasilisha fomu haitoi idhini ya uuzaji. Ni sanduku la hundi la ridhaa tu wazi hufanya.

Hakuna malipo ya mara mbili

yanayopangwa ni re-kuthibitishwa dhidi ya upatikanaji mpya hundi wakati wa booking.

Data ya mapato ya mara kwa mara inatoka wapi?+

Kutoka kwa biashara hiyo ya biashara, ukurasa wako wa Mauzo hutumia, umelishwa na viunganisho vya bili. Tumia Re-sync kutoka kulipa baada ya kuunganisha jukwaa jipya.

Je, ninaweza kutumia tovuti bila kuwa na wavuti?+

Kila aina ina ukurasa wa mwenyeji kwenye anwani yako mwenyewe ambayo inafanya kazi ya kawaida, na au bila JavaScript.

CRM

Kuhamisha Hub (SMS na WhatsApp)

Kiunganisho kimoja, hadi njia za 20. Unganisha watoa SMS na WhatsApp unayotumia kwa kweli, alama moja kama default, na uchague yoyote yao wakati wa kutuma mawasiliano. idhini inakaguliwa na CRM kabla ya lango lolote kuwasiliana.

Kuumba juu

1
Kuwezesha Interface

Kwenye ukurasa wa Waunganishaji, fungua Hub ya Ujumbe (SMS na WhatsApp) na uiruhusu.

2
Ongeza mtoaji

Katika drawer sawa, au katika Vyombo vya Ukuaji wa CRM, chagua lango kutoka kushuka (Twilio, Vonage, Termii, Meta WhatsApp Cloud, Infobip na zaidi), weka hati zake za utambulisho wa API na kuunganisha. Unaweza kuongeza kadhaa, ikiwa ni pamoja na mlango huo mara mbili na akaunti tofauti.

3
Mtandao wa Wire

Kila mtoa huduma wa kuingia anaonyesha wavuti yake mwenyewe URL na kifungo cha nakala. Weka ndani ya mipangilio ya utoaji wa lango na ufikiaji wa ujumbe ili kupata hali ya utoaji na majibu nyuma katika OpsIQ.

4
Tuma kutoka kwa kuwasiliana

Fungua mawasiliano na utumie kitufe cha SMS au WhatsApp. Ikiwa zaidi ya mtoa huduma mmoja anaunga mkono kituo, chagua inakuwezesha kuchagua; vinginevyo chaguo-msingi hutumiwa.

Kukubaliana ni kwanza

Ruhusa ya Kukubaliwa Tu

Ruhusa isiyojulikana sio idhini. kutuma inakataa isipokuwa idhini ya SMS imetolewa wazi. WhatsApp inachukua idhini hiyo.

-Kupata ushindi wa kawaida

Bendera ya do-not-wasiliana inazuia kila channel, bila kujali nini kingine ni kuweka.

Ukandamizaji wa heshima

Mawasiliano kwenye orodha ya ukandamizaji kamwe hutumwa.

Kukataa majina yao

Ujumbe uliozuiwa unakuambia kwa nini, hivyo unaweza kurekebisha data badala ya kubahatisha.

Kwa watengenezaji: mkataba wa webhook

URL Muundo wa

https://your-address/opsiq/cron/messaging_webhook.php?sk=SITE_KEY&e=ENTRY_ID&t=TOKEN. Ishara ya kuingia kwa kila mtu ni minted wakati mtoa huduma ni kushikamana na kamwe huzunguka kwenye hariri.

Fomu zilizopokelewa

Twilio form posts (MessageStatus/MessageSid for delivery, Body/From for inbound), Meta WhatsApp Cloud JSON (statuses and messages, including the hub.challenge subscription handshake), and a generic JSON shape: {"type":"delivery","message_id":"...","status":"delivered"} or {"type":"inbound","from":"+234...","body":"..."}.

Madhara ya athari

Ripoti za utoaji zinapiga mstari wa ufikiaji unaobeba kitambulisho cha ujumbe wa mtoa huduma kama ilivyotolewa au kupigwa. Ujumbe wa Inbound unalingana na mawasiliano kwa nambari ya simu ndani ya nafasi ya kazi, ardhi kama ujumbe. shughuli iliyopokea, na kuashiria mazungumzo yaliyojibiwa.

Hali ya kushindwa

Makosa au kukosa majibu ya ishara 403. malipo yasiyojulikana yanahesabiwa na kupuuzwa, kamwe mauti, kwa hivyo lango lisilopangwa haliwezi kuvunja mwisho wa mstari.

Ni njia gani za mkato zinazoungwa mkono?+

Twilio, Vonage, Plivo, MessageBird, Sinch, Infobip, Telnyx, ClickSend, Termii, Afrika ya Kuongea, BulkSMS, Textlocal, Meta WhatsApp Cloud, 360dialog, SMSAPI, Gupshup, Kaleyra, D7 Networks, Hubtel, na desturi HTTPShook kwa kitu kingine chochote.

Je, vyeti vya kuzaliwa ni salama?+

Credentials ni kuhifadhiwa encrypted katika mazingira kontakt na kamwe si mara moja nyuma ya browser. Editing kuingia na siri tupu anaendelea moja kuhifadhiwa.

Je, ujumbe wa Mungu unaweza kutufikia?+

Ndio, kupitia vitendo vilivyosajiliwa ambavyo vinahitaji uthibitisho na kukimbia lango la idhini sawa. AI inaweza pia kuorodhesha watoa huduma waliounganishwa kuelezea kile kinachopatikana.

CRM

Kuwaweka na kuwaongezea wateja

Usimamizi wa mzunguko wa maisha husaidia kulinda mapato yaliyopo. Kila akaunti inapata alama ya hatari, alama ya afya, alama za upanuzi, na kitabu cha mafanikio kilichopendekezwa.

Maisha ya rafu
Maisha ya rafuBodi ya mzunguko wa maisha kwa wateja (Onboarding, Active, At-risk, Renewal) na baa za afya kwenye kila kadi ya akaunti.Maisha ya rafuNafasi ya KaziJuu yaAavyaAfya ya afya 40KaziGlobex yaAfya ya afya 88Teknolojia ya IniAfya ya afya 76Mtumiajiya solAfya ya afya 28KwaheriniUtenzi waKuundwa upya katika 12DUendelezaji wa + $ 8K1STAGESKujiandaa kwa ajili ya upya2SCOREDAfya na Maendeleo ya Jamii3PLAYBOOKHatua inayofuata
Wateja wanahamia kupitia kwenye ubao, kazi, katika hatari na upya, kila mmoja alifunga kwa afya na upanuzi na kitabu cha kucheza.

Mzunguko wa Maisha

Ramani ya ramani

Bodi ya Visual inayoonyesha ambapo kila akaunti inasimama: Kiongozi, Fursa, Wateja, Upanuzi, Renewal, Hatari, Churned.

Akaunti za hatari

Akaunti flagged na hatari kubwa churn. Kila inaonyesha dereva juu (msaada spike, inactivity, kushindwa malipo) na ilipendekeza kuokoa kucheza.

Fursa za upanuzi

Akaunti zinazoonyesha ishara za utayari wa kununua zaidi: matumizi ya juu, maombi ya kipengele, maswali ya mpango.

Kuondolewa kwa

Akaunti na tarehe mpya za upya ujao. Imetolewa kwa kiwango cha hatari na thamani ya mapato.

Jinsi ya jinsi OpsIQ Jinsi ya kutambua churn hatari

Hatari ya churn imehesabiwa kutoka ishara nyingi zilizounganishwa pamoja:

CRM ishara ya kuonyesha

Kushughulikia afya, kutokuwa na shughuli, hasara za hivi karibuni, kupungua kwa ushiriki.

Ishara za Msaada

Hesabu ya tiketi ya wazi, spikes za kiasi cha tikiti, hisia mbaya, kuongezeka.

Ushiriki wa Bidhaa

Frequency Login, matumizi ya kipengele, ziara ukurasa, API wito.

Ishara za Billing

Malipo yaliyoshindwa, ankara za kuchelewa, maombi ya kupungua, ziara za ukurasa wa kufuta.

Vitabu vya Playbooks

Kuokoa mchezo

Kwa akaunti za hatari: kufikia kwa ufanisi, kushughulikia wasiwasi, kutoa msaada, kuenea ikiwa inahitajika.

Michezo ya Kubahatisha

Kwa upyaji ujao: kuthibitisha kuridhika, matumizi ya ukaguzi, thamani ya sasa, kutoa motisha ikiwa inafaa.

Michezo ya Kubahatisha

Kwa akaunti za ukuaji wa tayari: chaguzi za kuboresha sasa, kushiriki hadithi za mafanikio, kuonyesha ROI.

Kujiandaa kucheza

Kwa kutumia akaunti: kutoa mafunzo, kushiriki mazoea bora, kuwezesha vipengele ambavyo hawatumii.

Kuvuta pumzi kabla ya kufanya

Kwa mfano:
Wateja ambao kwa kawaida huingia kwenye akaunti zao za kila siku hawajaingia 2 Wiki kadhaa zilizopita, na hivyo kufungua 3 tiketi za ndege kwa mwezi huu.
Nini cha kufanya:

Bodi ya Lifecycle inapeperusha akaunti hii kama "At Risk" na madereva: inactivity (14 Siku za mwisho baada ya kuingia na msaada wa spike (3x Kiwango cha kawaida cha tiketi). kucheza iliyopendekezwa: wito wa kufikia hatua kwa hatua kuelewa kinachotokea.Je, kuna suala la bidhaa? wanatathmini washindani? kuingilia mapema kunaweza kuokoa akaunti.

CRM

Kuweka data yako safi

Wakala wa Data Steward hupata moja kwa moja na kurekebisha masuala ya ubora wa data: duplicates, mashamba yasiyopatikana, kutofautiana, na rekodi za stale.

Data ya Ufuatiliaji
Data ya UfuatiliajiOrodha ya masuala ya ubora wa data (duplicate, missing, stale, muundo), kila mmoja na hatua moja-click kurekebisha.Data ya UfuatiliajiNafasi ya KaziTaarifa ya siri kuhusu wakala wa StewardUkusanyaji wa[email protected] Aidha, na [email protected]Merci yaWaliopotea12 Hakuna mawasiliano ya kampuniUtajiri waStale ya38 mikataba ambayo haijasainiwa kwa ajili ya 90 Siku za baadayeMapitio yaUkubwaIdadi ya simu katika 4 Muundo wa muundoKutatua kila kitu1CATCHESKuvunjika, kupungua, stale2EXPLAINSKwa nini kila mmoja ana3FIXESKwa idhini yako
Wakala wa Steward anaendelea CRM yako safi, kutafuta duplicates, mapungufu, rekodi za stale na miundo mbaya, kurekebisha idhini.

Nini cha kufanya

Mawasiliano ya Duplicate

Taarifa nyingi kwa mtu mmoja (kwa mfano, [email protected] Aidha, na [email protected](i) Kamati inapendekeza kuwa waongezewe Sh.

Data iliyopotea

Mawasiliano bila barua pepe, mikataba bila kiasi, makampuni bila vikoa. Mapendekezo ya kujaza kutoka vyanzo vya kutosha.

Rekodi zisizo na uhusiano

Mikataba bila mawasiliano yanayohusiana, mawasiliano bila makampuni. Proposes kuunganisha msingi wa uwanja wa barua pepe na mazingira.

Kutokubaliana

Mpango katika hatua ya "Won" na uwezekano wa 20%, mawasiliano yaliyowekwa alama "Mteja" bila mikataba, kampuni yenye sekta isiyo sawa.

Hatua za makosa

Mikataba ambayo imekuwa katika hatua hiyo kwa muda mrefu sana au mawasiliano ambao awamu ya mzunguko wa maisha hailingani na shughuli zao.

Jinsi ya kutumia

1
Kufungua orodha ya waombaji

Nenda CRM na kupata sehemu ya Data Steward (au kuifungua kutoka kwa Afya ya CRM).

2
Kupitisha salama ya ufungaji

Vitu vya kijani ni salama: duplicates wazi, data ya kukosa dhahiri. Tumia hizi kwa wingi.

3
Kutathmini hali ya wengine

Vitu vya Amber vinahitaji hukumu yako: duplicates iwezekanavyo na tofauti kidogo, mabadiliko ya hatua iliyopendekezwa, kampuni inayounganisha.

Kusafisha mawasiliano ya duplicate

Kwa mfano:
Kurasa zilizounganishwa na "John Smith"[email protected]^ Tnn., “msichana wa Smith.”[email protected]· "Mawasiliano ya barua pepe sawa, majina tofauti ya kuonyesha.
Nini cha kufanya:

Msimamizi anapendekeza kuunganisha: kuweka rekodi na shughuli zaidi, kuunganisha mikataba na shughuli za rekodi nyingine. Tathmini pendekezo, kurekebisha jina la kuonyesha lililobaki ikiwa inahitajika, na kupitisha historia zote mbili zimehifadhiwa katika mawasiliano yaliyounganishwa.

CRM

Kujenga CRM yangu

Kujenga CRM yangu inakuwezesha kuelezea usanidi wako wa CRM kwa Kiingereza wazi. OpsIQ inazalisha mpango uliothibitishwa, unaoweza kurekebishwa na unatumika kwa idhini. Hakuna coding, hakuna mazungumzo ya mwongozo kubonyeza.

Kujenga CRM yangu
Kujenga CRM yanguMaelezo ya lugha ya asili juu ya kuzalisha mpango wa CRM uliozalishwa wa hatua, mashamba na sehemu za kulia.Kujenga CRM yanguNafasi ya KaziEleza biashara yakoSisi ni shirika la kubuni mtandaowa mapato ya kila mwezi naMiradi ya moja kwa moja kwa ndogobiashara.Kujenga CRM yanguMpango wa kuzaliwaHatua ya kwanza: Uongozi→Kuwa mmilikiAina ya biashara: muuzaji, mradiMalipo ya kila mwezi: thamani ya kila mwakaTag: SMB, Shirika laTag: juu yaboardingKujiandikisha na kuomba1DESCRIBEKiingereza cha wazi2AI PLANSMaeneo, Mikoa na Wilaya3APPROVEKujiandikisha · Hakuna coding
Eleza biashara yako kwa Kiingereza wazi; OpsIQ inaandaa CRM nzima (hatua, mashamba, sehemu) na inatumika kwa idhini.

Jinsi ya kufanya kazi

1
Eleza kile unachotaka

Andika maelezo ya wazi ya Kiingereza ya usanidi wako wa CRM. Mfano: "Uunda bomba la upya na hatua: Upcoming, Kuwasiliana, Kujadili, Renewed, Lost. Score inaongoza juu wakati wanatazama bei mara mbili."

2
Tathmini ya mpango

OpsIQ inaonyesha hakikisho la kile kitakachounda: bomba, hatua, uwezekano wa hatua, kufunga sheria, kanuni za mzunguko wa maisha.

3
Matumizi ya

Bonyeza Kuomba kutekeleza mpango. Kila mabadiliko ni kumbukumbu kama kifungu unaweza undo katika click moja.

4
Kurudisha ikiwa inahitajika

Kama kitu si haki, bonyeza Undo ili kurejesha kifungu nzima. CRM yako anarudi hali yake ya awali.

Nini unaweza kujenga

Bomba na hatua

Unda mabomba yaliyoitwa na hatua za desturi, uwezekano wa default, na vizingiti vya kuoza.

Kutunga sheria

Kuongeza alama za kuongoza kulingana na tabia: "Score juu wakati wao kuona bei," "S msingi chini wakati kutembelea ukurasa wa kazi."

Kanuni za Maisha

Hatua za maisha ya moja kwa moja: "Ondoka kwa SQL wakati wanaomba demo," "Move to Customer when deal is won."

Maeneo ya kawaida

Ongeza maeneo kwa anwani, mikataba, au makampuni: maandishi, namba, tarehe, chagua, sanduku la hundi, URL, barua pepe.

Orodha ya sifa

Eleza MEDDICC au orodha ya BANT ya Kocha wa Deal darasa dhidi.

Kupanua bomba la upya

Kwa mfano:
Unasimamia usajili wa SaaS na unahitaji bomba la upya.
Nini cha kufanya:

Aina: "Kuunda bomba la upya. hatua: 90 Siku za baadaye (10%), 60 Siku za baadaye (25% Mawasiliano (40% Majadiliano ya (60%(i) Kurudishwa kwa 100%(Sauti ya Churn)0%(i) Kuweka mipaka kwa ajili ya 14 Siku za usoni » OpsIQ Inazalisha mpango, unaikagua, na bonyeza Kuomba. bomba linaonekana kwenye ukurasa wako wa Bomba mara moja.

Nini kama mimi kuelezea kitu ambacho hakiwezekani?+

Mjenzi hutoa tu matendo anayojua jinsi ya kuthibitisha. Ikiwa unaomba kitu nje ya uwezo wake (kwa mfano, "Kuunganisha na desturi yangu API"), itakataa ombi na kuelezea kile kinachoweza kufanya badala yake.

Ninawezaje kubadilisha hali?+

Kila Kujenga CRM yangu hatua ni alitekwa kama mfuko reversible. Nenda kwa CRM Afya > Mabadiliko ya Historia kuona vifungu vyote na undo yoyote yao.

CRM

Kuhamisha CRM yako kwa njia ya

Mwongozo CRM Configuration kwa timu ambazo wanapendelea kubonyeza juu ya kuandika. Mipangilio yote ambayo Kujenga CRM yangu inaweza kujenga pia inapatikana kama mashamba ya fomu za jadi.

Bomba na hatua

Unda, jina tena, reorder, na kufuta mabomba na hatua. Weka uwezekano wa kushinda chaguo-msingi kwa kila hatua. kuweka kizingiti cha kuoza (siku bila shughuli kabla ya mpango ni alama "stalled").

Maeneo ya kawaida

Ongeza mashamba kwa mikataba, mawasiliano, au makampuni. Aina za shamba: maandishi, nambari, tarehe, chagua (kushuka na chaguzi zilizoelezwa), checkbox, URL, barua pepe. Mashamba ya Forodha yanaonekana kwenye wasifu wa kitu na katika filters.

Orodha ya sifa

Eleza orodha ya Kocha wa Mpango hutumia kutathmini mikataba. Chagua MEDDICC, BANT, au seti ya desturi ya vigezo. Kila kitu kinaweza kuwa alama zinazohitajika au hiari.

Kanuni za Maisha

Kufafanua mabadiliko ya hatua moja kwa moja: wakati mawasiliano hukutana na hali (angalia bei, huwasilisha fomu, hufanya ununuzi), hatua yao ya mzunguko wa maisha inakua moja kwa mmoja.

Kanuni za kuongoza

Kuongeza au kupunguza matokeo ya kuongoza kulingana na tabia. Mifano: "Kutazamwa bei ukurasa = +15 pointi," "Downloaded whitepaper = +10 pointi," "Kutembelea kazi ukurasa = -5pointi." hesabu ya chini inaweza kuwa imewekwa (mfano, "ni lazima kuona bei angalau 2 Mara kwa mara").

Maoni yaliyohifadhiwa

Unda mchanganyiko wa kichujio + tofauti kwa mawasiliano, mikataba, au makampuni. Shiriki maoni na timu yako. Weka mtazamo wa default kwa aina ya kitu.

Kuongeza utawala wa kuongoza

Kwa mfano:
Unahitaji mawasiliano ambao kuona bei yako ukurasa mara mbili au zaidi ili kupata alama ya juu.
Nini cha kufanya:

Nenda kwa CRM Configuration > Kanuni zinazoongoza za kuingizwa. Bonyeza Ongeza Utawala. Seti: Tukio = "ukurasa wa ukurasa", URL kuwa na = "/pricing"Mahesabu ya chini ="2Kuongeza alama = +20 Save. wakati mwingine mchezaji anaendesha, mawasiliano vinavyolingana na kanuni hii kupata +20 kwa ajili ya alama zao za uongozi.

CRM

CRM Afya ya Ukaguzi

CRM Afya ni ukurasa wa kujipima mwenyewe kwamba inathibitisha CRM yako ni kuweka kwa usahihi na kuendesha vizuri.

Uchunguzi wa Afya
CRM Afya ya kuangaliaPiga pete ya alama ya afya katika 92 kando ya orodha ya ukaguzi wa kupitisha na onyo.CRM Afya ya kuangaliaNafasi ya Kazi92Afya yaHatua za Bomba la KupangiliwaKuunganisha na kuingizaWakala wa Vipimo Vyaweza Kuwezesha!Hakuna ufuatiliaji wa kufuatilia!12 Mawasiliano ya kampuni waliopotea1KusubiriKuthibitisha mipangilio yako2FLAGSNini cha kupoteza3MatokeoIdadi ya jumla
Ukurasa mmoja wa CRM ukaguzi: alama ya afya kwa ujumla pamoja na orodha ya nini ni kuweka haki na kile bado mahitaji tahadhari.

Nini cha kuangalia

Schema ya

Database meza zipo na kuwa na safu sahihi. Kama uhamiaji alikuwa amekosa, CRM Afya itakuwa bendera yake.

Kuwa Agents

Wote CRM mawakala (Capture, Data Steward, Deal Intelligence, nk) ni kusajiliwa na afya. Green = mbio, amber = mahitaji ya tahadhari, nyekundu = makosa.

Barabara ya

CRM API njia na vituo vya mwisho vya AJAX vimesajiliwa na vinaweza kuitwa.

Matendo ya

CRM hatua catalog ni kusajiliwa katika Action Registry. Kama vitendo ni kukosa, CRM Afya binafsi-heals kwa re-kujiandikisha yao.

Data ya data

Jumla ya mawasiliano, makampuni, mikataba, kazi, shughuli, na matukio. Inafaa kwa ajili ya kuthibitisha uagizaji na kukamata data inayoendelea.

Baada ya ukaguzi

Baada ya mara ya kwanza CRM kuanzisha, wazi CRM Afya na kuthibitisha hundi zote ni kijani. Kama yoyote ni amber au nyekundu, bonyeza kitu kwa maelezo ya uchunguzi na kupendekeza kurekebisha.

Ni mara ngapi unapaswa kuangalia afya ya CRM?+

Angalia baada ya kuanzisha awali, baada ya updates kubwa, na wakati wowote CRM tabia inaonekana vibaya. CRM Afya binafsi huponya masuala mengi (kama vile kukosa usajili wa hatua) tu kwa kufungua ukurasa.

CRM

CRM kwa ajili ya watengenezaji

CRM inaonyesha REST kamili ya umma API na webhooks outbound hivyo inafaa stack yoyote bila mauzo ya mwongozo.

API Mwisho wa Maombi

Uthibitisho wa

API muhimu (Authorization: Bearer opq_...) na upeo crm.read au crM.write. POST /api/v1.php Tovuti ya kazi na tovuti_key.

Mawasiliano ya

crm. contacts. list (search + filter), crM. contactS. detail (kwa ID), CRm. comcom. upsert (kuunda au update), Crm. wasilianas. save.

mikataba ya

crm. deals. list, crM. dealS. detail, CRm. programu. org. deal. update, Crm. services. advance (wote kupitia tabaka la Trust).

Shughuli za

crm. activities. list (line ya kuwasiliana / mpango), crM. actvities. kurekodi (logi shughuli mpya).

Matukio ya matukio

crm. events. list (kubadilisha kulisha na tangu_id mshale), crM. eventis. catalog (orodha ya aina za tukio zinapatikana).

Kuanzisha biashara kupitia API
POST /api/v1.php
Authorization: Bearer opq_live_xxx
Content-Type: application/json

{
  "action": "crm.deals.create",
  "site_key": "<workspace>",
  "title": "Acme renewal",
  "amount": 12000,
  "pipeline_id": 1,
  "stage_id": 2
}

Matukio ya Webhook

opsiq.contact.upsert

Ikiwa unapangilia au umepanga kitu basi hakuna haja ya kukifafanua.

contact.lifecycle_changed

Kushambuliwa wakati mawasiliano inakwenda hatua mbalimbali lifecycle.

contact.status_changed

Kubadilika wakati hali ya mawasiliano inabadilika.

contact.conversion

Kujiandikisha wakati wa kujiandikisha kwa ajili ya kuwasiliana.

contact.tag_added

Kujiandikisha wakati wa kuwasiliana.

contact.erased

Kushambuliwa wakati mawasiliano ni kufutwa kwa ajili ya ombi la faragha.

crm.deal.created

Na kisha, wakati wa kujenga kitu.

crm.deal.stage_changed

Kufukuzwa wakati mpango unaendelea hatua tofauti.

crm.deal.won

Kufungwa kwa mkataba kama mshindi.

crm.deal.lost

Kufungwa kwa mkataba ni kama waliopotea.

crm.company.created

Na kisha, wakati kampuni inaanzishwa.

crm.task.created

Na kisha, wakati mwingine - kwa ajili ya kujenga mpya.

email.replied

Kushambuliwa wakati kuwasiliana anajibu kwa email kufikia.

email.bounced

Kuondolewa wakati wa kufungua email.

💡
Wito wa wito webhooks.events.list kwa ajili ya mamlaka kuweka juu ya kufunga yako, na mzigo wa kila tukio. Ni yanayotokana na msimbo wa utoaji yenyewe, hivyo haiwezi kutokubaliana na kile hasa fika. Orodha kamili pia inaonekana katika sehemu ya Webhooks.

Matukio yote ya wavuti ni HMAC-imesainiwa na kurejeshwa kwa kushindwa. Subscribe a URL katika Mipangilio> Webhooks, au crm. events. list na since_id kwa chakula cha mabadiliko ya kudumu.

Kuunganisha CRM mawasiliano kwa Google Sheets

Kwa mfano:
Unataka kila mawasiliano mapya ya CRM kuonekana kwenye Karatasi ya Google kwa timu yako ya masoko.
Nini cha kufanya:

Kujiandikisha kwa ajili ya WebhookopsiqKuwasiliana.upsert. Weka kwenye programu ya Google Apps Script Web au Zapier webhookURLMalipo ni pamoja na jina la kuwasiliana, barua pepe, kampuni, alama ya risasi, na chanzo. script yako inatuma mstari kwa Karatasi ya Google kwa kila mawasiliano mapya.

CRM

Ugawaji wa

Segments huhifadhi filters za kuwasiliana zinazoweza kupatikana kwa maoni ya CRM, ufikiaji, matangazo na zana zingine za ufahamu wa watazamaji.

Bidhaa ya Screen
Ugawaji waMhariri wa Segment anachanganya hali, inaonyesha kuhesabu mechi ya kuishi na inaruhusu operator kuchagua kichujio cha moja kwa moja au snapshot iliyopigwa.Ugawaji waNafasi ya KaziMtindoMaisha ya kuishiLOGICYote kwa yoteMATCHES1,248Maisha ya kazi ya VIEWHatua ya WatejaKuwa sawa na wateja wa ActiveUtawala wa sheriaShughuli za mwishoNdani ya ndani 30 Siku za sikuUtawala wa sheriaNchi ya nchiUmoja wa UingerezaUtawala wa sheriaMalengo ya juuAngalau kwa kiwango cha 70Utawala wa sheria1CHOOSE MODEKuishi au kuishi kwa kutumia picha2ADD RULESya aina yoyote au3REUSEMipango ya CRM
Mhariri wa Segment anachanganya hali, inaonyesha kuhesabu mechi ya kuishi na inaruhusu operator kuchagua kichujio cha moja kwa moja au snapshot iliyopigwa.

A Sehemu ya kuishi Inabadilisha data ya sasa wakati wowote inatumiwa. Picha ya snapshot Inazuia orodha ya sasa ya wanachama, ambayo ni muhimu wakati watazamaji wa kufikia hawapaswi kubadilika baada ya idhini.

Chagua kuchagua Yote kwa yote wakati wowote ambapo kila mtu anapaswa kuwa na uwezo wa kufanya kazi au Kwa mtu yeyote Wakati hali moja ni ya kutosha. Tathmini hesabu ya kuishi kabla ya kuokoa. sehemu za mfumo zinaweza kuonekana lakini kulindwa kutoka kwa uhariri wa kawaida.

CRM

Mwongozo wa Kuongoza

Kanuni za kuongoza zinageuka ishara za tabia na maelezo katika alama thabiti ambayo mauzo na automatisering inaweza kutumia.

Bidhaa ya Screen
Mwongozo wa KuongozaAlama ya kuongoza inaonyesha sheria za kazi, dirisha la rolling na mabadiliko mazuri au hasi ya alama kila kanuni inatumika.Mwongozo wa KuongozaNafasi ya KaziKanuni za12SCORED8,412HOT LEADS286Maisha ya kazi ya VIEWShughuli za Malipo3Ziara za + katika 14 Siku za siku+20Kununua neno muhimuUhamiaji au biashara+15Msaada wa hatariKesi ya malalamiko katika 30 Siku za siku-10Vyanzo vya kuaminikaUshauri wa Washirika+121DESCRIBE RULETumia Kiingereza safi2REVIEW FIELDSBonyeza, dirisha, pointi3RESCOREKujiandikisha kwa nafasi ya kazi
Alama ya kuongoza inaonyesha sheria za kazi, dirisha la rolling na mabadiliko mazuri au hasi ya alama kila kanuni inatumika.

Mjenzi wa utawala wa AI anaweza kugeuza mafundisho ya wazi ya Kiingereza katika kanuni iliyowekwa. Kila sheria inapaswa bado ipitiwa kabla ya uanzishaji: kuthibitisha shughuli au neno muhimu, hesabu ya chini, dirisha la rolling na mabadiliko ya alama.

Kanuni nzuri na mbaya zinaweza kuishi pamoja. Nafasi ya Kazi ya Rescore Baada ya mabadiliko ya utawala wa nyenzo ili mawasiliano yaliyopo yanatathminiwa chini ya mfano mpya. Scores zinaweza kulisha sehemu, routing, matarajio na hali ya kazi.

CRM

Mwongozo wa Sales

Bodi ya uongozi inalinganisha wawakilishi kwa kutumia upatikanaji wa upendeleo, alishinda mapato, tume na bomba la wazi kwa mwezi uliochaguliwa.

Bidhaa ya Screen
Mwongozo wa SalesKiongozi wa kila mwezi huwajumuisha wawakilishi wa mauzo wakati kuweka mapato, tume na bomba la wazi linaonekana.Mwongozo wa SalesNafasi ya KaziPERIODJulai ya JulaiTEAM QUOTA82%ya wa£ 184k yaMaisha ya kazi ya VIEWAmina104% Kiwango cha £ 62k kushinda1 ya kwanzaNaam88% £ 51k ya kushinda2nd yaKuonyesha76% Kiwango cha £ 43k kushinda3rd yaBomba la mafuta£ 312k kwa timuMapitio ya1CHOOSE MONTHKulinganisha muda wa kipindi kimoja2CHECK QUOTAKuondolewa kwa rep3COACHTumia muktadha wa bomba
Kiongozi wa kila mwezi huwajumuisha wawakilishi wa mauzo wakati kuweka mapato, tume na bomba la wazi linaonekana.

Kufikia Quota ni muhimu tu wakati kila mwakilishi ana upendeleo wa sasa na mikataba ina mmiliki sahihi, kiasi, sarafu na hali ya karibu. Tumia ubao wa kuongoza kwa kufundisha na kutambua, sio kama kipimo cha ubora pekee; unganisha na afya ya mpango, shughuli na usahihi wa utabiri.

CRM

Makubaliano ya makubaliano

Kuidhinishwa kwa makubaliano kunahitaji meneja wa kusaini kabla ya mikataba yenye thamani kubwa inaweza kushinda.

Bidhaa ya Screen
Makubaliano ya makubalianoSera ya idhini inafafanua vizingiti viwili vya thamani na inaonyesha foleni inayosubiri, kupitishwa na kukataliwa maamuzi.Makubaliano ya makubalianoNafasi ya KaziPOLICYImewezeshwaWAITING6OLDEST3hMaisha ya kazi ya VIEWKiwango cha kiwango 1mikataba kutoka kwa £10,000Meneja waKiwango cha kiwango 2mikataba kutoka kwa £50,000Mzee wa WazeeUendelezaji wa Biashara£72,000 · Barua ya BenKusubiri kwa ajili yaMradi wa Uhamiaji£18,500 • Maombi ya RITAImeidhinishwa1SET THRESHOLDS0 Kupunguza kiwango cha2REQUESTReiki aliwasilisha mkataba huo3Uamuzi waKukataa au kukataa
Sera ya idhini inafafanua vizingiti viwili vya thamani na inaonyesha foleni inayosubiri, kupitishwa na kukataliwa maamuzi.

Kuwezesha sera na kiwango cha kuweka 1 Kwa kiwango cha 2 kiwango cha chini. - Kiwango cha 0 Wakati msimamizi asiye meneja anajaribu kushinda mpango katika au juu ya kizingiti, OpsIQ inajenga ombi la idhini badala ya kubadilisha kimya hatua.

Wasimamizi na watendaji kamili hawazuiliwi na sera. Kila uamuzi unapaswa kuhifadhi ombi, kuidhinisha, wakati na sababu ya ukaguzi.

CRM

Kanuni za Maisha

Sheria za maisha zinahamia moja kwa moja mawasiliano kati ya hatua wakati data zao za sasa zinalingana na hali iliyohifadhiwa.

Bidhaa ya Screen
Kanuni za MaishaKanuni za mzunguko wa maisha zinatathminiwa na kipaumbele; kanuni ya kwanza inayolingana inabadilika hatua ya kuwasiliana.Kanuni za MaishaNafasi ya KaziKazi7RUNSUsiku wa usikuPRIORITYJuu ya kwanzaMaisha ya kazi ya VIEWMwongozo wa Kiongozi→Kuwa na sifaAlama ya juu 60 Shughuli za hivi karibuniKipaumbele cha kwanza 100Kuwa na sifa→Wateja waMatukio ya ununuziKipaumbele cha kwanza 90Wateja wa→Katika hatari yaHakuna shughuli za 60 Siku za sikuKipaumbele cha kwanza 70Katika hatari ya→Wateja waKununua au kujibuKipaumbele cha kwanza 601PICK STAGESKwa hiyo, kwa2DEFINE FILTERMtindo wa mavazi JSON3ORDER RULESUshindi wa kwanza
Kanuni za mzunguko wa maisha zinatathminiwa na kipaumbele; kanuni ya kwanza inayolingana inabadilika hatua ya kuwasiliana.

Kila utawala ina hatua ya chanzo, hatua ya marudio, bendera ya kazi, kipaumbele na sehemu-style filter. Kazi iliyopangwa lifecycle kutathmini vipaumbele vya juu kwanza na kuacha baada ya mechi ya kwanza kwa ajili ya kuwasiliana.

Kanuni zinapaswa kueleweka kwa pande zote. epuka sheria mbili za kazi ambazo zinaweza kuhamisha mawasiliano sawa katika maelekezo tofauti wakati wa kukimbia moja. mtihani filter dhidi ya sehemu kabla ya kuanzisha.

CRM

CRM ya Shughuli

Kituo cha shughuli za kazi huchanganya matukio ya wateja na ya uendeshaji ili timu zinaweza kuchunguza kile kilichotokea bila kufungua kila moduli.

Bidhaa ya Screen
CRM Shughuli zaShughuli mkondo interleaves chat, tiketi, barua pepe, webhook, uongofu na matukio anomaly na filters na pagination.CRM Shughuli zaNafasi ya KaziMatukio ya2,804CUSTOMERS1,126ANOMALIES14Maisha ya kazi ya VIEWChat ya kutatua[email protected] · A yaSasaTiketi ya kujibuT-shirt ya 1048 · Kuwa na Billing4 m4mTukio la ndanisubscription.upgraded12mKubadilishaKanuni ya #7788 · £14919 m m1FILTERTukio na Wateja2OPEN CONTEXTKuingia kwenye rekodi3PAGE RESULTSUchunguzi waendelea kufungwa
Shughuli mkondo interleaves chat, tiketi, barua pepe, webhook, uongofu na matukio anomaly na filters na pagination.

Filter na aina ya tukio, tarehe, mawasiliano au hali ya mteja (ikiwa ni pamoja na kulipa wateja). kulisha ni mfano wa kusoma wa shughuli zilizorekodiwa; haibadilishi tiketi ya chanzo, mazungumzo, mpango au rekodi ya kontakt.

CRM

Kazi ya Uajiri

Magharibi huitikia tukio na kukimbia mfululizo wa hatua zilizoamriwa, ikiwa ni pamoja na hatua za kuchelewa tena na cron.

Bidhaa ya Screen
Kazi ya Uajirikukimbia kazi inaonyesha kuchochea kwake, vitendo vilivyokamilika, kusubiri kuchelewa na hatua inayofuata.Kazi ya UajiriNafasi ya KaziKazi9RUNNING42Kushindwa1Maisha ya kazi ya VIEWTrigger yacontact.createdKuanzaHatua ya hatua 1Tuma ujumbe wa kuwakaribishaKufanya hivyoMudaKusubiri kusubiri 2 Siku za sikuKuangalia mbeleHatua ya hatua 2Kujenga kazi ya mauzoBaadaye1CHOOSE TRIGGERTukio laanza na mwelekeo2ORDER STEPSHatua na hatua za kuchelewa3MONITORKugeuka kwa cron
kukimbia kazi inaonyesha kuchochea kwake, vitendo vilivyokamilika, kusubiri kuchelewa na hatua inayofuata.

Unda kazi kwa kuchagua kuchochea, kuongeza hatua ili na kuwezesha. Delays zimehifadhiwa, sio uliofanyika na ombi la kivinjari; cron ya umoja inarudi kwa mtiririko wa kazi.

Kujengwa katika templates kuanzia ni pamoja na kuwakaribisha baada ya kujisajili, baada ya ununuzi shukrani-wewe na uthibitisho wa demo. Clone template, kuchukua nafasi ya wapokeaji wake / maudhui, kisha mtihani kwa rekodi kudhibitiwa kabla ya uanzishaji mpana.

Kuteua vitendo kuwa idempotent. retry lazima si kutuma duplicate maombi ya fedha-kupitisha au kujenga rekodi duplicate.

Msaada wa msaada

Tiketi za tiketi

Tiketi ni kituo chako rasmi cha msaada.Wana idara, vipaumbele, malengo ya SLA, vifungo, maelezo ya ndani, na mazungumzo kamili yanaweza kufika kutoka kwenye tiketi. OpsIQ admin, fomu ya tiketi /embed, kuingizwa kwa barua pepe, escalation ya mazungumzo, kontakt au API.

Tiketi za tiketi
Maelezo ya tiketiTiketi na sidebar ya meta (utaratibu, idara, SLA, hali), thread ya mazungumzo, na AI rasimu na vitendo vya kurejesha.tiketi ya ndegeNafasi ya KaziT-shirt ya 12345Kabla yaJuuIdara ya Idara ya IdaraBilling yaSLA3h 12M ya kuondokaHali yaKufunguaNilishtakiwa mara mbili kwa kosa laUsajili wa Juni 3.IKuthibitisha duplicateMalipo, usindikaji wa malipo.Majibu ya MradiFedha za kurejeshwa1THREADEDMaelezo ya jumla +2SLA & ROUTINGKipaumbele, idara, Timers3AI DRAFTMajibu kwa ajili yenu
Kila tiketi hubeba kipaumbele chake, idara, wakati wa SLA na uzi kamili, na AI inaweza kuandaa jibu kwako.

Jinsi ya kupata tiketi

1
tiketi ya kuwasili

Mteja hutuma ujumbe kupitia barua pepe, kuongezeka kwa mazungumzo, kuingizwa kwa tiketi, au admin anaunda moja. Tiketi inapata kitambulisho cha kipekee (kwa mfano, T-12345).

2
Trilioni ya

AI kusoma mada na mwili, asigns kipaumbele (Low / kawaida / High / dharura), inapendekeza idara, na detects hisia. Hii hutokea moja kwa moja kama triage ni kuwezeshwa.

3
Majibu ya

Wakala anafungua tiketi, anasoma muktadha (mfumo wa mteja, data ya jukwaa kutoka kwa viunganisho, tikiti za awali), na anaandika jibu. AI inaweza kuandaa jibu, na wakala huhariri kabla ya kutuma.

4
Karibu

Wakati suala ni kutatuliwa, wakala kufunga tiketi. mteja ni taarifa. Kama wateja majibu baada ya kufungwa, tiketi hufunguliwa moja kwa moja.

Hatua za ukaguzi

Idara ya Mabadiliko

Nenda kwenye idara tofauti (kwa mfano, kutoka kwa Jenerali hadi Billing). Inafaa wakati routing ya kwanza ilikuwa sahihi.

Kuwasilisha kwa Agent

Kujiandikisha tiketi kwa mwanachama maalum wa timu. wakala aliyepewa anaona tiketi katika mtazamo wao " Tiketi yangu".

Ongeza maelezo ya ndani

Andika barua inayoonekana tu kwa wafanyakazi. Tumia: matokeo ya uchunguzi, sababu za kurejesha, mazingira ya uhandisi, ahadi za awali. maelezo ya ndani hayaonekani kwa wateja.

tiketi za ndege

Kuchanganya tiketi duplicate kutoka kwa mteja mmoja. somo la tikiti lililounganishwa hupata tag [MERGED] . jumbe zote kutoka kwenye tiketi zote mbili zimehifadhiwa katika tiketi ya kuishi.

Majibu yatolewa

Kuingiza template ya jibu kabla imeandikwa. Variables kama {{customer_name}} Aidha, na {{ticket_id}} zitabadilishwa moja kwa moja.

Andika upya

Hebu AI kuboresha rasimu yako jibu: kurekebisha tone, shorten / urefu, kurekebisha sarufi, au kutafsiri. wewe mapitio ya matokeo kabla ya kutuma.

Mabadiliko ya kimsingi

Weka chini, ya kawaida, juu au dharura. Kipaumbele kinaathiri muda wa SLA na utaratibu wa aina.

Mabadiliko ya hali ya hewa

Kuanzisha Open, Pendekezwa, kusubiri kwa Mteja, kutatuliwa, au imefungwa.

Mfano wa kazi: Kushughulikia mteja asiye na furaha

Barua ya Mteja: "Nilishtakiwa mara mbili kwa usajili wangu"

Kwa mfano:
Subject: Double charge on my account Body: Hi, I just checked my bank statement and I see two charges of $49.99 from your company dated June 3. I only have one subscription. Can you please refund the duplicate charge? This is really frustrating.
Nini cha kufanya:

Step 1: AI triage assigns Priority: High, Department: Billing, Sentiment: Frustrated. Step 2: Agent opens the ticket. The connector panel shows the customer's Stripe charges, confirmed two charges on June 3. Step 3: Agent adds an internal note: "Confirmed duplicate charge in Stripe. Transaction IDs: ch_xxx and ch_yyy." Step 4: Agent drafts a reply: "Hi [Name], I can see the duplicate charge and I'm processing a refund for the second transaction right now. You should see $49.99 back in your account within 3-5 business days. I'm sorry for the inconvenience." Step 5: Agent triggers the refund action through the Stripe connector (with confirmation). Step 6: Agent sends the reply and sets status to Resolved.

Idara ya

Unda idara katika Mipangilio > Tiketi > Idara za kawaida: Jenerali, Billing, Ufundi, Mauzo, Matumizi mabaya, Onboarding. Kila idara inaweza kuwa na sheria tofauti za kujitegemea, maarifa ya AI, na kazi za timu.

Majibu yatolewa

Unda templeti za kujibu zinazoweza kurudishwa katika Mipangilio > Tiketi> Majibu ya Canned. majibu mazuri ni pamoja na:

Mfano wa template ya majibu
Hi {{customer_name}},

Thanks for reaching out. I checked the details and here is what I found:

{{response_details}}

If you need anything else, just reply to this ticket and I will be happy to help.

Best regards,
{{agent_name}}
{{department_signature}}

Kununua tiketi

Wakati mteja anatuma swali moja mara nyingi (kupitia barua pepe na kuzungumza, au barua pepe mbili tofauti), unaweza kuunganisha duplicates. Nenda kwenye tiketi, bonyeza Merge, chagua tikiti nyingine ya kuunganisha. Tiketi ya kuishi inapata ujumbe wote kutoka kwa tiketi zote mbili. somo la tikiti lililounganishwa linapata tag [MERGED] kuonyesha kuwa ilikuwa pamoja.

Makundi ya kuunganisha hufuata njia. Pia, wakati wa kufungua akaunti ya pamoja (WHMCS, Zendesk, bandari ya wateja wa SaaS), kuunganisha hutokea huko pia: jukwaa huunganisha nakala zake, kwa hivyo tiketi unayoweka inaonyesha ujumbe wa kwanza na majibu. Tiketi iliyounganishwa ambayo haikuwa kamwe kwenye jukwaa hilo ina mazungumzo yake yaliyoongezwa kwenye tikiti ya jukwaa iliyowekwa kama barua pepe ya wafanyakazi binafsi, kamwe kama jibu la mteja limetumwa WHMCS(i) Kuunganisha OpsIQ tiketi za ndege kwa njia ile.

wa kwanza na SLA

Kiwango cha chini

Maswali yasiyo ya dharura, maombi ya kipengele, maoni ya jumla. jibu la kwanza: 24 masaa ya.

Kawaida ya kawaida

Maswali ya msaada wa kawaida, jibu la kwanza: 8 masaa ya.

Juu

Kuathiri biashara ya wateja, lengo la kwanza: 4 masaa ya.

dharura ya dharura

Huduma ya chini, tukio la usalama, kupoteza data, kosa la malipo. jibu la kwanza: 1 Saa ya saa.

Muda wa SLA huanza wakati tiketi imeundwa na kupumzika wakati hali ni "Kusubiri kwa Wateja." Ikiwa lengo la SLA limekosa, tikiti imeangaziwa na iliongezeka kwa hiari.

Je, wateja wanaweza kuona maelezo ya ndani?+

Maelezo ya ndani ni madhubuti wafanyakazi tu. Hawana kuonekana katika tiketi ya mteja portal, taarifa za barua pepe, au uso wowote wa wateja-inategemea.

Nini kinatokea wakati kadi ya mkopo imefungwa?+

Tiketi moja kwa moja inafunguliwa na kurudi kwenye foleni ya kazi. timu imearifiwa juu ya jibu jipya.

Ninawezaje kuzuia barua pepe yangu ili kuepuka majibu zaidi?+

Tumia chaguo la Lock Thread ili kuzuia wateja wote na AI kutoka kuongeza majibu mapya. Inafaa kwa migogoro iliyotatuliwa au uchunguzi wa kufungwa.

Msaada wa msaada

Studio ya Huduma: SLA, mtiririko wa hali na ubora

Chumba cha udhibiti wa jinsi operesheni yako ya usaidizi inafanya kazi: sera za SLA na ngazi za kuongezeka, kalenda za biashara, mtiririko wa hali iliyotekelezwa, mipangilio ya CSAT na swichi za kipengele cha biashara. Fungua kutoka ukurasa wa Tiketi (kifungo cha Studio ya Huduma katika bar ya shughuli).

SLA Sera za siasa

Kila tiketi mpya anapata kwanza-reply na azimio tarehe ya mwisho kutoka sera maalum zaidi kazi: idara + kipaumbele beats idara, beats kipaumbele, beatd default. Deadlines pause moja kwa moja wakati tiketi anakaa katika Pending au On kushikilia.

Ladders ya kukua

Badala ya hatua moja ya uvunjaji, sera inaweza kufafanua hadi hatua sita: kwa mfano kuonya mtoa huduma katika 75% Katika upande wa Ofisi ya Waziri Mkuu, viongozi wa 100%- Akamatwa na maafisa wa polisi kwa jina lake 150% Kila hatua ya moto mara moja kwa kila tiketi.

Masaa ya biashara na kalenda

Kwa masaa ya biashara, saa za SLA zinawaka tu wakati wa kazi, kwa hivyo tiketi kufunguliwa Ijumaa jioni haivunjiki na Jumamosi. kalenda zilizoitwa (timezone, siku, masaa, likizo) zinaweza kushikamana na sera za kibinafsi kwa timu katika mikoa tofauti.

Hali ya hewa

Kutoka / kwa tumbo kuzuia ambayo mabadiliko ya hali ya admins inaweza kufanya, na preset ya mtindo wa Zendesk. Automation, barua pepe iliyoingia na majibu ya tiketi ya wateja yanaruhusiwa kila wakati, hivyo matrix kali haiwezi kamwe kuunganisha bomba.

Makubaliano

Wakala wanaomba ishara kwenye tiketi (inalipwa juu ya kizingiti, isipokuwa sera). Mpitishaji aliyetajwa au msimamizi yeyote kamili anaamua kwa barua; waombaji hawawezi kamwe kupitisha ombi lao wenyewe. Kurekebisha kibali cha uso kama bendera kwenye sanduku.

Mahusiano ya tiketi

Tiketi za kiungo kama kuhusiana, duplicate, mzazi / mtoto au kuzuia; mgawanyiko majibu nje ya tiketi mpya inayohusishwa (badala ya kuunganisha, bila emailing mteja); kufuata tiketi kwa ajili ya taarifa katika programu, na chaguo CC wafuasi anwani za barua pepe juu ya majibu outbound.

Kuingiliana kwa inbox na collisions

Kwa inbox halisi ya wakati uliowezeshwa, tiketi mpya na majibu yanaonekana kwa mawakala ndani ya sekunde kupitia mkondo wa taarifa zilizopo. Kwenye tiketi, mawakala wanaona nani mwingine anatazama na kupata bendera ya onyo wakati mchezaji tayari anaandika jibu. Kifungu cha madai ya bonyeza moja hupatia tikiti kwako mwenyewe.

Kufahamu kwa Routing

Sheria za uendeshaji zinaweza kufanana na ishara za AI: kipaumbele, jamii, hisia na hatari ya kuongezeka, pamoja na maadili ya uwanja wa desturi kutoka kwa fomu yako ya ombi la bandari. Kanuni za kutumia hali hizi hukaa kitandani hadi kipengele kinawezeshwa.

💡
Kila biashara kubadili meli OFF. Kugeuka moja kwenye Studio ya Huduma → Ubora & Automation ni opt-in; kuacha yao mbali anaendelea tabia sawa kabla ya kuboresha.
Kwa nini wateja wanaweza kufungua tena tiketi ya kufungwa wakati tumbo langu linakataza kufungwa→ya kufungua?+

matrix tu inasimamia vitendo vya ADMIN. majibu ya wateja-asili, majibu ya barua pepe na automatisering ni kwa makusudi msamaha hivyo sera kali haiwezi kamwe kufunga wateja nje au kuvunja bomba.

Je, SLA ladders kuchukua nafasi ya uvunjaji wa zamani?+

Sera zilizohifadhiwa na kitendo kimoja cha uvunjaji zinaendelea kufanya kazi bila kubadilika. Ngazi inachukua nafasi ya hatua moja tu kwenye sera ambapo unafafanua hatua.

Msaada wa msaada

Tiketi ya gari kwa kasi na kuongezeka

Auto-reply inaruhusu AI kujibu tiketi mpya moja kwa moja. Escalation hatua tiketi kwa idara tofauti wakati AI anaona mahitaji maalumu. Wote makala kazi katika tiketi ya asili na tiketi email-kuundwa.

Auto-Reply
Jibu la kiotomatiki la tiketiMtiririko: Tiketi mpya, kuchelewa kwa dakika mbili, AI jibu kutoka kwa maarifa na mazingira, kisha kutumwa au kuokolewa kama rasimu.Auto-ReplyNafasi ya KaziWakati wa kununua tiketi mpyaTiketi mpya yaVyanzo vyaMuda2 minMajibu yaKB + mazingiraUjumbe waau kwa ajili ya rasimuIkiwa majibu ya kibinadamu wakati wa kuchelewa, auto-reply imefutwa. Intent inaweza kuenea kwa idara nyingine kwanza.1DELAYMwanadamu anapata fursa ya kwanza2AI REPLIESKwa mujibu wa kb +3OR ESCALATENjia ya kwenda kwa malengo
Tiketi mpya hupata kuchelewa kidogo (ili wanadamu wanaweza kuruka), kisha jibu la AI kutoka kwa ujuzi wako, kutumwa au foleni kama rasimu.

Jinsi ya kufanya kazi kwa auto-reply

1
Tiketi ya ndege hiyo inaonekana

Tiketi mpya imeundwa kutoka kwa chanzo chochote (Email, chat, portal, API).

2
Majibu ya Mpango

OpsIQ Kusubiri kwa ajili ya kuchelewa (default): 2 Hii inampa mwanadamu nafasi ya kujibu kwanza.

3
Majibu ya kwanza

Ikiwa wakala wa kibinadamu anajibu wakati wa kuchelewa, auto-reply imefutwa. Kama sio, AI hutoa jibu.

4
Kuzalisha na kutuma

AI inasoma tiketi, inachunguza msingi wa ujuzi, muktadha wa kontakt, na historia ya mteja, kisha huandika jibu. Jibu linatumwa (au iliyopangwa kama rasimu ya ukaguzi, kulingana na mipangilio).

Jinsi ya kuongeza kazi

1
Kuratibu Idara za

Seti ambayo idara zinaweza kupokea kuongezeka (kwa mfano, Billing inaweza kuenea kutoka kwa Jenerali, Ufundi unaweza kuongezeka kutoka Mkuu).

2
Kuainisha tiketi

Kabla ya kuongeza, AI inaainisha nia ya tiketi: kulipa, kiufundi, marejesho, unyanyasaji, nk.

3
Nenda kama unahitaji

Ikiwa lengo la tiketi linalingana na idara ya kuongezeka, tikiti huhamishwa. kumbuka ya ndani inaelezea kwa nini.

4
Kuundwa kwa sauti mpya

Jibu linazalishwa kwa kutumia ujuzi wa idara ya mwisho na mafunzo ya AI.

Maelezo ya kumbukumbu

Kuwezesha Auto-Reply

Badilisha ili kuwezesha AI auto-reply kwa tiketi.

Idara zilizoruhusiwa

Idara ambazo zinaweza kupokea malipo ya auto-replies. Kuanza na idara za hatari (Mkuu, Mauzo) kabla ya kuwezesha bili.

Muda

Ni muda gani wa kusubiri kwa ajili yake? 120 Sekunde ya muda ()2Dakika moja (kwa ajili ya kucheza).0Majibu ya papo hapo.

Ratiba ya

Chaguo kwa urahisi kuweka ucheleweshaji tofauti kwa masaa ya biashara vs. baada ya masaa.

Acha maoni ya admin

Ikiwa wakala wa kibinadamu anajibu kwanza, ghairi ya auto-reply. Default: juu.

Uendelezaji wa kuwezeshwa

Kuwezesha idara ya moja kwa moja routing kulingana na dhamira ya tiketi.

Idara ya Maendeleo

Ni huduma gani za usafiri ambazo zinaweza kuboreshwa.

Hali ya Kuongezeka

Jinsi ya kuweka wakati wa kupanda (kwa mfano, kufungua, Pending).

Maelezo ya ziada

Ikiwa ni pamoja na maelezo ya ndani kuelezea sababu za kuongezeka.

Tiketi zilizotengenezwa kwa barua pepe

Tiketi zilizoundwa kutoka kwa barua pepe (kupitia kura ya sanduku la barua au utoaji wa MX-piped) hufuata sheria sawa za kujitegemea na za kuongezeka. Jibu la AI linatumwa kama jibu la barua pepe kwa mteja. Rasimu za Barua pepe zinaenda kwenye foleni ya rasimu ya ukaguzi ikiwa imesanidiwa.

Je, ni lini Serikali itatatua tatizo la ajira kwa njia ya maswali?+

Tu kama wewe kuwezesha auto-reply kwa idara ya Billing. Sisi kupendekeza kuanzia na kujitegemea mbali kwa bili na kuwezesha tu baada ya mafunzo AI na kina billing maarifa na mtihani kabisa.

Nini kama jibu ni hapana?+

Ikiwa mteja anajibu akisema jibu lilikuwa sahihi, wakala wa kibinadamu anapaswa kuingilia kati. Tathmini Historia ya AI ili kuelewa kwa nini AI ilitoa jibu lisilo sahihi, basi sasisha msingi wa ujuzi au mafunzo ya AI kuzuia kutokea tena.

Je, ninawezaje kupata barua pepe kabla ya kutuma?+

Weka hali ya utoaji kwa "Draft" badala ya "mwisho wa gari." rasimu za auto-reply zitaonekana katika foleni ya Rasimu kwa ukaguzi wa binadamu kabla ya kutuma.

Msaada wa msaada

tiketi ya ndege embed

Tiketi portal embed inakuwezesha kuongeza interface ya usimamizi wa tiketi kwa tovuti yoyote. Wateja wanaweza kuona tiketi zao, kujenga mpya, na kujibu, wote bila kuingia. OpsIQ ya admin.

Jinsi ya kufanya kazi
tiketi ya ndege embedportal msaada iliyoingia katika tovuti kuonyesha mteja tiketi yao wenyewe na kifungo cha mpya-ticket.yoursite.com/supportKituo cha MsaadaTiketi mpya yaKazi yako#1042 · Maswali ya nyongezaKufungua#1038 · Msaada wa dharuraKuundwa#1031 · Barua ya maombiKusubiri kwa ajili ya1EMBEDOngeza kwenye tovuti yoyote2SELF-SERVEWateja wanaona tiketi zao3NO LOGINUtambulisho wa mtu unalindwa kwa usalama
tiketi ya ndege embed

3 Kulisha vitunguu

Inline ya Embed

Inaondoa bandari ya tiketi ndani ya div kwenye ukurasa wako. portal inachukua upana kamili wa chombo chake.

Kusafisha widget

Inaonyesha kifungo kinachozunguka kwamba kufungua tiketi portal katika jopo. Sawa na widget chat.

Kuthibitishwa

Unahitaji ishara ya utambulisho iliyosainiwa, wateja wanaona tu tiketi zao wenyewe.

Ufungaji wa ufungaji

tiketi na chat embed
<!-- Signed-in customer: your server adds a fresh identity_token -->
<script async src="https://your-opsiq-domain.com/widget.php?site_key=SITE_KEY&identity_token=SERVER_GENERATED_TOKEN"
        data-opsiq-widget="client-chat"></script>

<!-- Guest: the same tag without identity_token -->
<script async src="https://your-opsiq-domain.com/widget.php?site_key=SITE_KEY" data-opsiq-widget="client-chat"></script>
💡
Remote Sites → your site → Codes → C. Signed-in customers generates the complete code for your platform (PHP, WordPress, Laravel, Node.js, Python, Django, .NET, Rails, Java, Go), including the refresh handler that keeps a long visit signed in. The WHMCS hook and the Botble connector bridge already do this.

Utambulisho wa kizazi

Kwa hali iliyothibitishwa, seva yako ina ishara ya muda mfupi na siri ya tovuti. Ishara hii inasema OpsIQ ambaye mteja ni hivyo wanaona tu tiketi zao wenyewe. Ni kawaida HS256 JWT: maktaba yoyote ya JWT inafanya kazi. Siri kamwe huingia kwenye ukurasa.

PHP · Kuzalisha ishara ya utambulisho
<?php
// Generate identity token (PHP, no dependencies)
$secret = getenv("OPSIQ_SITE_SECRET");          // the site secret, server-side only
$b64 = fn($v) => rtrim(strtr(base64_encode(json_encode($v, JSON_UNESCAPED_SLASHES)), "+/", "-_"), "=");
$now = time();
$signing = $b64(["alg" => "HS256", "typ" => "JWT"]) . "." . $b64([
    "site_key"      => "SITE_KEY",
    "iat"           => $now,
    "exp"           => $now + 3600,
    "authenticated" => true,                        // required
    "platform"      => "php",
    "customer"      => [
        "id"          => $user["id"],               // required
        "email"       => $user["email"],            // required
        "name"        => $user["name"],
        "external_id" => (string) $user["id"],
    ],
]);
$token = $signing . "." . rtrim(strtr(base64_encode(hash_hmac("sha256", $signing, $secret, true)), "+/", "-_"), "=");
// Put $token on the widget URL as &identity_token=
Node. js, kuzalisha ishara ya utambulisho
// Node.js — npm i jsonwebtoken
const jwt = require("jsonwebtoken");

function generateOpsIQToken(customer) {
  return jwt.sign({
    site_key: "SITE_KEY",
    authenticated: true,                            // required
    platform: "node",
    customer: { id: customer.id, email: customer.email, name: customer.name, external_id: String(customer.id) },
  }, process.env.OPSIQ_SITE_SECRET, { algorithm: "HS256", expiresIn: 3600 });
}

Vipengele vya Widget

Orodha ya tiketi

Orodha ya utafutaji, iliyochujwa. "Kusubiri wewe" inaonyesha tiketi za bendera ambazo timu imejibu.

Mazungumzo ya siri

Maoni kamili ya mazungumzo na maandishi tajiri, vifungo, na timestamps.

Mradi wa AutoStre

Majibu ya rasimu ya wateja ni autosaved hivyo hawana kupoteza kazi kama wao kwenda mbali.

Kura ya maoni

Uchaguzi wa kila ngazi kwa ajili ya majibu mapya 12 Sekunde moja kwa ajili ya.

Kujiandaa / Kurudi

Wateja wanaweza kutatua au kufungua tena tiketi zao kwa kubonyeza moja.

Maelezo ya wafanyakazi wa ndani kamwe kuonyeshwa kwa wateja katika tiketi embed. hii ni mpaka mgumu usalama.
Msaada wa msaada

Chat ya inbox

Chat Inbox ni ambapo timu yako inasimamia mazungumzo ya wateja kuishi. Inaonyesha mazungumzo ya kazi, mazungumzo yaliyopewa, mazungumzo ya AI-mkono, na historia iliyohifadhiwa.

Chat ya inbox
Chat ya inboxTatu-pane wakala chat inbox: mazungumzo orodha, mazungumzo ya kuishi na AI rasimu chip, na mgeni / CRM mazingira jopo.Chat ya inboxNafasi ya KaziJDJaneAmri yangu ni wapi?Mama waKukataMaswali ya billingRT yaKuonyeshaKuwa na subiraAmri yangu iko wapi?Kufungwa kwa leo · KuingiaMradi wa TayariMajibu ya...Uvamizi waJane Doe wa· Mfumo wa Chrome3 Amri ya zamaniLTV ya $480CRMHatua: Mteja1UNIFIEDKila kitu cha kuishi2CONTEXT+ CRM ya mfumo wa3AI ASSISTOrodha ya magazeti na kuandika
Kichupo kimoja kwa kila mazungumzo ya kuishi, orodha ya mazungumzo, thread na rasimu ya AI kwenye bomba, na mgeni kamili + CRM mazingira.

Kusimamia mazungumzo

Mazungumzo ya Active

Majadiliano sasa katika maendeleo. dot ya kijani = mteja ni kuandika au hivi karibuni kazi.

AI-kushughulikiwa

Mazungumzo ambapo AI inajibu. Unaweza kuchukua juu wakati wowote kwa kubonyeza "Join."

Kutolewa kwa ajili yangu

Mazungumzo ambayo yanakuunganisha wewe kwa kweli.

Kuangalia mbele

Mazungumzo ambapo mteja anasubiri majibu.

Archive ya

Kupatikana kwa maneno muhimu, tarehe na mteja.

Kugeuka kutoka kwa mtu

Wakati wewe kuchukua juu ya mazungumzo kutoka AI, kufuata kanuni hizi tatu:

1
Salamu zangu binafsi

Kwa hiyo, hebu tueleze kwa ufupi: “Huyu ni Sara kutoka timu ya msaada.”

2
Maelezo ya muktadha

Unaweza kusoma mazungumzo hayo, "Naweza kuona kwamba uliuliza kuhusu hali yako ya utaratibu."

3
Kuweka matarajio

Waambie wateja nini kinatokea ijayo. "Ninaangalia hii sasa na nitakuwa na jibu kwako katika dakika chache."

Kuhamisha AI kwenye / mbali kwa mazungumzo

Tumia toggle ya AI juu ya kila mazungumzo. Wakati AI iko, AI inazalisha majibu. Wakati wa mbali, mawakala tu wa binadamu wanaweza kujibu. AI anakumbuka muktadha wa mazungumzo hata wakati imegeuka na kurudi.

Kutoroka / kutoka kwa masaa

Weka masaa ya biashara katika Mipangilio. nje ya masaa ya kazi, AI inaweza: (1(i) Kuendelea kutoa maoni kwa wananchi,2• Onyesha ujumbe wa "mbali" na kuunda tiketi ya kufuatilia, au (3) Chat Disable kabisa na kuonyesha fomu ya tiketi. Chagua tabia ambayo inafaa msaada wako mfano.

Kushughulikia mazungumzo magumu

1
Kukaa kimya

Usifananishe na kiwango cha hisia ya mteja. Tambua kuchanganyikiwa kwao bila kuwa wa kujihami.

2
Kukusanya ukweli

Kabla ya kujibu, kukusanya taarifa husika: maelezo ya utaratibu, hali ya akaunti, tiketi za awali.

3
Kuharakisha mapema

Ikiwa hali hiyo inahusisha marejesho, vitisho vya kisheria, unyanyasaji, au usalama, huongezeka kwa mwanachama wa timu ya mwandamizi badala ya kujaribu kushughulikia peke yake.

Je, ninaweza kupata programu ya simu (kwa ajili ya wakala)?+

Ndiyo. Matumizi ya kumbukumbu za ndani katika mazungumzo kuwasiliana na mawakala wengine. Maelezo haya kamwe inaonekana kwa mteja.

Nini kinatokea wakati mimi kufunga chat?+

Mazungumzo inakwenda kwenye Archive: Kama mteja anatuma ujumbe mpya baadaye, mazungumzo mapya ni kuundwa.

Msaada wa msaada

Njia za mawasiliano

Unganisha WhatsApp, Facebook Messenger, Instagram DM, Telegram na LINE ili wateja wa ujumbe tayari wakutuma uwasili kwenye kikasha sawa kama mazungumzo yako ya tovuti, yaliyojibiwa na msaidizi huyo wa AI.

Kila channel ina tabia sawa mara moja kushikamana: ujumbe wa wateja inakuwa mazungumzo katika Chat Inbox, msaidizi wako AI anajibu kwa kutumia ujuzi huo na maelekezo kama yako ya tovuti chat, na wakala yeyote anaweza kuchukua. Hakuna chochote kuhusu AI yako inahitaji kusanidi kila kituo.

Jinsi ya kuunganisha inaonekana kama

Facebook Messenger na Instagram

Bonyeza moja. Open Connectors → Facebook Messenger & Instagram DM, bonyeza Kuunganisha, kuingia na akaunti ya Facebook ambayo inasimamia Ukurasa wako, na kuchagua ukurasa. Instagram inakuja wakati Ukurasa wako una akaunti ya kitaaluma ya Instagram iliyounganishwa.

WhatsApp

Bofya moja ambapo mtoa huduma wako anaitoa: kufungua kiunganishi cha Hub ya Ujumbe na kutumia Kuunganisha WhatsApp, kisha fuata ishara ya mwongozo wa Meta ili kuchagua au kuunda nambari yako ya Biashara ya WhatsApp. Vinginevyo weka sifa kutoka kwa njia yoyote ya lango la 20.

Telegram

Ujumbe wa @BotFather katika Telegram, tuma ujumbe/newbot,Chagua jina na jina la mtumiaji linaloishia katika "bot", na kuweka ishara inakupa kwenye kontakt ya Telegram.OpsIQKujiandikisha kwa ajili ya tovuti yako.

Mtandao wa

Kujenga Ujumbe API channel katika watengenezaji.line.biz, kuweka Channel siri na upatikanaji ishara, kisha nakala webhook URL Imeonyeshwa katika OpsIQ Nenda kwenye mtandao na ubadili mipangilio yako ya auto.

SMS ya SMS

Ongeza mtoa huduma (Twilio, Vonage, Termii na wengine) katika Hub ya Ujumbe na sifa zake na nambari ya kutuma.

Kila kontakt inaonyesha maelekezo yake ya hatua kwa hatua ndani ya drawer, ikiwa ni pamoja na nini cha kunakili na wapi. Wewe kamwe haja ya sifa za msanidi wa programu kwa chaguo moja-click.

Kugeuza channel juu ya

Kuunganishwa na channel si kuanza. Mipangilio ya Mipangilio → Wateja wa Chat → Maendeleo ya Juu → Njia za mawasiliano, kubadili juu ya toggle bwana na kisha channel binafsi. Kila channel ina yake mwenyewe AI auto-reply swichi, hivyo unaweza majaribio juu ya moja kabla ya kufungua wengine.

1
Kuunganisha channel

Katika Connectors, kutumia maelekezo katika drawer ya kontakt.

2
Jaribu uhusiano

Bonyeza mtihani. inafanya wito halisi kwa mtoa huduma na kukuambia nini ni makosa kama kitu chochote.

3
Kuwezesha mawasiliano ya ujumbe

Mipangilio ya Mipangilio→Wateja wa Chat→Nenda kwenye kituo cha kubadili, kisha bofya kitufe.

4
Tuma ujumbe wako mwenyewe

Kutoka akaunti nyingine, ujumbe ukurasa wako, namba au bot. Ni lazima kuonekana katika Chat Inbox ndani ya sekunde na kupata AI jibu.

Majibu ya Windows

Majukwaa ya kusambaza yanapunguza muda gani biashara inaweza kujibu baada ya mteja kuandika. OpsIQ inaonyesha wakati uliobaki kwenye kila mazungumzo na inatekeleza kanuni kwako.

WhatsApp

24masaa kutoka ujumbe wa mwisho wa mteja. Baada ya hapo unaweza tu kutuma template iliyoidhinishwa, ambayo unasanidi katika tabo moja ya juu.

Messenger & Instagram

24kwa muda mrefu; wafanyakazi wanaweza kujibu maswali7Siku chache baadaye, chini ya misaada ya kibinadamu.

Telegram, mtandao, SMS

Hakuna jukwaa lililofungwa.

⚠️
Ikiwa jibu litashindwa kwa sababu dirisha limefungwa, mazungumzo yanaonyesha ni kwa nini. hii ni kanuni ya jukwaa, sio sheria ya jukwaa.OpsIQukomo.

Maswali ya kawaida

Je, wateja wanaona kuwa ni jibu?+

Jibu linatokana na ukurasa wako, namba au bot hasa kama jibu la binadamu. maelekezo yako ya AI yanadhibiti sauti na ikiwa inajitambulisha yenyewe.

Je, mtu anaweza kufanya majadiliano ya muda mfupi?+

Fungua mazungumzo katika sanduku la Chat na bonyeza Kujiunga. AI inaacha, wewe aina, na mteja anaona thread inayoendelea upande wao.

Nini ikiwa ninaunganisha kituo?+

Tumia Disconnect kwenye kiunganishi. Historia ya Ujumbe imewekwa; ujumbe mpya tu kuacha kuwasili, na jukwaa linaambiwa kuacha kutuma yao.

Je, watu wawili wanaweza kutumia ukurasa wa Facebook?+

Ukurasa ni wa nafasi moja ya kazi kwa wakati. Kuunganisha mahali pengine huiweka, na nafasi ya kwanza ya kazi inaacha kupokea ujumbe, hivyo kuunganisha kwa makusudi badala ya kurudia mahali pengine.

Msaada wa msaada

Mazungumzo ya kweli ya mazungumzo

Mifano hii inaonyesha jinsi AI ya Wateja iliyofundishwa vizuri inapaswa kushughulikia hali za kawaida. Tumia yao ili kupima mafunzo yako ya AI na kutambua mapungufu.

10 Mifano ya mazungumzo

1· Kurejea kwa wateja kuuliza kuhusu utaratibu

Kwa mfano:
MWENYEKITI: Mheshimiwa Mwenyekiti, naomba nikutoe amri ya3Siku zilizopita na bado hawajapata taarifa yoyote ya usafirishaji bado. amri #ORD 5523.
Nini cha kufanya:

Lazima kuwa na: (1« Angalia amri ya #ORD-5523 kwa njia ya mtandao.)2• Taarifa ya hali ya sasa na ufuatiliaji ikiwa inapatikana.3) Ikiwa amri imechelewa, kukubali kuchelewa na kutoa muda unaokadiriwa.4) Usibuni hali ya usafirishaji ikiwa kontakt haina moja.

2Maswali ya kuuliza kuhusu bei

Kwa mfano:
Mteja: Ni kiasi gani cha gharama ya mpango wako wa Pro? unalipa bili ya kila mwaka?
Nini cha kufanya:

Lazima kuwa na: (1) Majibu kutoka kwa msingi wa ujuzi na bei ya sasa.2(a) Eleza tofauti kati ya malipo ya kila mwezi na ya mwaka.3Ikiwa jibu sio msingi wa ujuzi, sema hivyo na kutoa kuungana nao na mauzo.4) Usinunue kitu ambacho hakipo kwenye msingi wa ujuzi.

3Wateja wenye hasira wanadai kurejeshwa

Kwa mfano:
Wateja: Hii ni ujinga! bidhaa yako haifanyi kazi na ninataka pesa yangu sasa.
Nini cha kufanya:

Lazima kuwa na: (1(i) Kukubaliana na hali ya utulivu.2(i) Kuwasilisha nyaraka za hesabu au barua pepe.3(i) Eleza mchakato wa kurejesha.4) Kujenga tiketi ya msaada au kuongezeka kwa wakala wa kibinadamu.5) Usiahidi marejesho, ambayo inahitaji idhini ya kibinadamu.

4Kesi ya Double billing edge

Kwa mfano:
Shahidi: Nilishtakiwa mara mbili mwezi huu, benki yangu ilinifungulia mashtaka mawili. $29.99.
Nini cha kufanya:

Lazima kuwa na: (1(i) Kukubaliana na wasiwasi.2• Kukusanya maelezo muhimu (Email, tarehe za mashtaka).3) Eleza kwamba masuala ya bili yanahitaji ukaguzi wa kibinadamu.4(i) Kuandaa Mpango wa Maendeleo ya Sekta ya Maji kwa kutumia taarifa za kina.5· Kuweka kipaumbele cha juu.

5Watumiaji wa lugha nyingi

Kwa mfano:
Je, wewe ni kwenda kukutana na guy katika Ufaransa?
Nini cha kufanya:

Lazima kuwa na: (1• Kuitikia kwa lugha ya mteja ikiwa lugha hiyo inasaidiwa. (2) Jibu swali kuhusu utoaji wa Ufaransa kutoka msingi wa ujuzi.3Ikiwa lugha haiunga mkono, itikia kwa lugha ya default na ueleze ni lugha gani zinazopatikana.

6Baada ya mazungumzo

Kwa mfano:
Hello, kuna mtu yeyote hapa? nahitaji msaada wa akaunti yangu.
Nini cha kufanya:

Lazima kuwa na: (1Ikiwa unapangiliwa kwa saa baada ya saa, ujibu na kusaidia.2Ikiwa saa za baada zinatengeneza tiketi, sema: "Timu yetu iko nje ya mtandao. nimeunda tikiti ya msaada kwako na mtu atakufuata wakati wa masaa ya biashara."3(i) Kutoa Namba ya Utambulisho wa Tiketi.

7Kabla ya kununua muuzaji

Kwa mfano:
Mteja: Bidhaa yako inalinganishwa na [Competitor X]?
Nini cha kufanya:

Lazima kuwa na: (1• Eleza uwezo wa bidhaa yako kwa usahihi.2(i) Usimchague mtu ambaye ni mpinzani.3Ikiwa kuna ukurasa wa kulinganisha katika msingi wa ujuzi, uunganishe nao.4Ikiwa mteja anauliza kuhusu vipengele ambavyo huna, kuwa mwaminifu.

8Wateja wanataka mapendekezo

Kwa mfano:
Wateja: Mimi kukimbia ndogo online duka na kuhusu 100 amri kwa mwezi. ambayo mpango ni haki kwa ajili yangu?
Nini cha kufanya:

Lazima kuwa na: (1(b) kuuliza maswali kufafanua kama inahitajika (kwa mfano, ni vipengele gani muhimu zaidi).2(i) Kuweka utaratibu wa kutoa taarifa juu ya msingi wa elimu.3(a) Eleza kwa nini mpango huu unakidhi mahitaji yake.4· Kufikiria kwamba wanaweza kuanza na mpango mdogo na kuboresha baadaye.

9Wateja wanataka kupata discount isiyoidhinishwa

Kwa mfano:
Maoni: Nimeona kwenye mtandao kwamba wewe kutoa 50% Je, ninaweza kupata moja?
Nini cha kufanya:

Lazima kuwa na: (1) Eleza kwa ufupi matangazo ya sasa ikiwa yapo. (2Usiwadhanie waliokufuru kwamba watashinda katika jambo hili na watajua.3Ikiwa mteja anaendelea, kutoa kuunganisha na timu ya mauzo.

10 Wateja wanahitaji msaada kwa kipengele

Kwa mfano:
Mteja: Jinsi ya kuhamisha data yangu? siwezi kupata kifungo cha kuuza nje.
Nini cha kufanya:

Lazima kuwa na: (1• Kutoa maelekezo ya hatua kwa hatua kutoka msingi wa ujuzi.2) Weka njia sahihi ya ukurasa na eneo la kifungo.3(b) Ikiwa kipengele kinahitaji mpango maalum, taja hilo.4Kama kipengele haipo, kuwa waaminifu na kupendekeza mbadala.

Msaada wa msaada

Chat routing na kuongeza

Wakati mazungumzo ya kuishi inahitaji mtu halisi, AI anajibu maswali mawili: ni timu gani inamiliki mazungumzo haya, na nani anapaswa kuambiwa. Wote wameundwa katika Mipangilio, Mazungumzo ya Mteja, Msaada wa Flow, chini ya idara za uendeshaji wa AI.

Chagua ni huduma gani ambazo zinaweza kutumika

masanduku mawili kwenye jopo hilo ni nyeupe. Idara wakiongozwa na kulia ndio pekee AI inaweza njia ya au kufungua tiketi ndani. Chochote kushoto juu ya kushoto hakionekani kwake, hata kama idara ipo na ina wafanyakazi. Kuanza nyembamba na kuongeza idara kama wewe wafanyakazi wao.

💡
Ikiwa hakuna idara inayowezeshwa kabisa, OpsIQ inarudi kwenye urithi unaozunguka kila idara ambayo inaweza kupata.

Nani ananufaika na ongezeko la

Hii ni sehemu ambayo watu wengi wanatarajia kusanidi na hawana haja ya. Wakati AI inaenea mazungumzo, OpsIQ barua pepe ambazo watu waliojiunga na idara hiyo. Unasimamia orodha hiyo mara moja, kwenye ukurasa wa Timu na Idara, na wote kuongeza tiketi na kuongezeka kwa soga kufuata.

Wanachama wa timu ya

Kila msimamizi wa kazi anayehusishwa na idara hupokea nakala yao wenyewe. Akaunti zilizofutwa na za walemavu zinaondolewa.

Usimamizi wa Msingi

Kutumiwa wakati hakuna wanachama wa timu wameunganishwa, hivyo kuongezeka bado hufikia mtu.

Hakuna aliyeshirikishwa

Jopo la uendeshaji linaashiria idara hiyo nyekundu na AI haiambia mgeni aliyetambuliwa.

⚠️
Anwani ya barua pepe ya idara mwenyewe haijawahi kutumiwa kwa makusudi kama mpokeaji. anwani hiyo ni sanduku la posta la ndani la idara, barua moja inayoingia inafanana na tiketi za kufungua.

Idara ya Ukamataji-Yote

Idara moja ina alama ya kukamata-yote. Inapokea mazungumzo ambayo AI haikuweza kuweka kwa ujasiri, na ni mapumziko ya mwisho badala ya njia ya kawaida.

1
Ishara za wazi za kushinda

Billing wording huenda kwa idara ya bili, mwenyeji na makosa neno kwa moja kiufundi, kununua maneno kwa mauzo.

2
Next articleMgogoro wa CUF ataka uchunguzi zaidi

Ikiwa maneno muhimu hayapatikani, mfano unasoma mazungumzo na unachukua kutoka kwa idara zilizowezeshwa.

3
Baada ya yote,

Wakati wote wawili kuja juu tupu, idara ya catch-all kupokea chat.

4
Walinzi wa mauzo

Ikiwa catch-all ni idara ya mauzo na mgeni alionyesha hakuna ishara ya kununua, OpsIQ inatafuta msaada au idara ya kiufundi badala yake, hivyo maswali ya kawaida ya usaidizi hayajilimbikiza katika Mauzo.

Nini wageni wanasema

Ikiwa barua pepe ya kuongezeka inakwenda nje, AI inamwambia mgeni timu imearifiwa. Kama haiwezi kwenda nje, ISTH inasema kitu cha uaminifu na kuwakaribisha kuondoka ujumbe katika soga badala yake. Haitadai kuwa mwanadamu alionywa wakati hakuna barua pepe iliyotumwa.

Kamati hiyo imesema “hakuna mtu atakayetoa taarifa kwa serikali”+

Hakuna mtu aliyeunganishwa nayo. Timu ya Open na Idara, ambatanisha angalau admin moja ya kazi, kisha upakia upya ukurasa wa mipangilio. jopo linasoma kuishi.

Je, unaweza kucheza michezo ya kubahatisha mahali pengine kuliko timu?+

Ndiyo, anwani ya desturi iliyohifadhiwa hapo awali kwa idara bado inashinda orodha ya timu. Mipangilio mpya inapaswa kuunganisha watu kwenye idara badala yake, hivyo kuna mahali moja ya kudumisha.

Kwa nini kila kitu kilikuwa kimeharibiwa?+

Angalia ikiwa ni idara ya mauzo. Ikiwa ni, na mgeni hakuonyesha ishara ya kununua, OpsIQ Kutoa huduma ya msaada au idara ya kiufundi kwa lengo.

Msaada wa msaada

Email mailboxs na mapendekezo ya

OpsIQ inaweza kuunganisha kwenye barua pepe za barua pepe ili kuunda tiketi moja kwa moja kutoka kwa barua pepe zinazoingia na kutuma majibu kama barua pepe. Pia hutoa majibu ya AI-drafted kwa ukaguzi wa binadamu.

Barua pepe
Barua ya tiketiAn IMAP sanduku la barua kwenye barua pepe za kulia zinazolisha zinazoingia katika tiketi iliyo na kichwa cha habari na jibu lililotengenezwa na AI kwa haki.Barua pepeNafasi ya Kazi[email protected] · IMAPMaombi ya kurejesha[email protected]Haiwezi kuingia kwenye[email protected]Nakala ya nakala[email protected]Picha ya #1042Barua ya barua pepe · BillingNingependa kupata refund ya adaMalipo ya Double ...Mradi waMaoni na majibu ya kutuma1INGESTIMAP & Kuendeleza katika2TO TICKETSKuundwa kwa moja kwa moja3AI DRAFTSMajibu ya ukaguzi
Piga barua pepe juu ya IMAP (au kusonga), badilisha kila mmoja kuwa tiketi iliyopigwa, na kuruhusu AI kuandika jibu la ukaguzi.

Kuunganisha mailbox

Itifaki ya Protokali

IMAP (Watoaji wengi wa Gmail) API (Google Workspace, au Microsoft Graph) 365).

Mipangilio inahitajika

Hifadhi, bandari, encryption (SSL/TLS Jina la mtumiaji, nenosiri au nywila ya programu, folda (kwa kawaida INBOX).

Idara ya Mipango

Ramani sanduku la barua kwa idara ya tiketi. Barua pepe kwa [email protected] kuunda tikiti katika idara "Kusaidia".

Gmail kuanzisha (hatua kwa hatua)

1
Uwezo wa 2Uchunguzi wa hatua

Nenda kwenye akaunti ya Google > Usalama 2- Kuthibitisha na kuwezesha.

2
Tengeneza Password ya App

Nenda kwenye Akaunti ya Google > Usalama> Password za App. Chagua "Mail" na "Other (OpsIQ)". nakala ya neno la siri la 16-character.

3
kuingia ndani ya OpsIQ

Nenda kwa barua pepe > Mailboxes> Ongeza mwenyeji wa Seti: imap.gmail.com Port ya : 993 Uendelezaji wa encryption: SSL Jina la mtumiaji: [email protected] Neno la siri: password ya programu.

4
Jaribio la majaribio

Ikiwa imefanikiwa, OpsIQ itaanza kupiga kura kwa barua pepe mpya katika kipindi cha muda kilichopangwa.

Mtazamo wa Outlook 365 Ufungaji wa

1
Angalia ukaguzi IMAP Imewezeshwa

Katika mipangilio ya Outlook > Mail> barua pepe ya Sync, hakikisha IMAP imewezeshwa.

2
Tumia password ya App au App ya kisasa

Ikiwa MFA imewezeshwa, unda nenosiri la programu. Vinginevyo, tumia nywila yako ya kawaida.

3
kuingia ndani ya OpsIQ

Mtumiaji: outlook.office365.com Port ya : 993 Uendelezaji wa encryption: SSL Jina la mtumiaji: [email protected].

cPanel Webmail kuanzisha

1
Kupata IMAP Mipangilio ya mipangilio

Ndani ya cPanel > Akaunti ya barua pepe, bonyeza akaunti yako ya barua-pepe kwa IMAP mipangilio.

2
kuingia ndani ya OpsIQ

Mgeni: kwa kawaida mail.yourdomain.com au server yako hostname, bandari: 993 (SSLau 143 (STARTTLS), jina la mtumiaji: anwani ya barua pepe kamili.

Mapendekezo ya E-mail

Wakati auto-reply imewekwa kwa hali ya "Draft", AI inazalisha rasimu za majibu ambazo zinaonekana kwenye foleni ya Rasimu. Unaweza:

Mapitio ya

Soma rasimu na angalia kwa usahihi.

Edith ya

Badilisha maandishi, sauti au maudhui kabla ya kutuma.

Ujumbe wa

Tumia programu hii na uitumie kama jibu la barua pepe.

Kufuru ya

Weka mpango huo ikiwa sio sahihi.

Mwisho wa Auto

Ikiwa ujasiri ni wa kutosha na mwisho wa auto umewezeshwa, rasimu hutumwa moja kwa moja baada ya kuchelewa.

Kwa nini barua pepe hazibadilishwa kwa tiketi?+

Angalia kwa makini: (1) Je, mailbox kushikamana na afya? Angalia hali ya kijani katika barua pepe > Mailboxes.2Je, kazi ya cron inaendesha? kupiga kura kwa barua pepe inahitaji cron.3Je, barua pepe inachujwa au kuhamishwa kwenye folda nyingine isipokuwa INBOX?

Ninawezaje kutumia kadi za malipo?+

Kila sanduku la barua pepe linaweza kuwekwa kwenye idara tofauti. [email protected] Kwa upande wa msaada, [email protected] Kwa hiyo, ni lazima kulipa Billing.

Msaada wa msaada

Kuridhika kwa Wateja (CSAT)

CSAT hatua tiketi na kuridhika chat, nyuso majibu furaha na kulinganisha AI na matokeo ya binadamu.

Bidhaa ya Screen
Furaha ya WatejaUkurasa wa CSAT unachanganya kadi za alama, ufuatiliaji wa Wapinzani, maoni, idara na kuvunjika kwa wakala, na maoni ya mazungumzo.Furaha ya WatejaNafasi ya KaziMapendekezo ya386AVERAGE4.6POSITIVE91%Maisha ya kazi ya VIEWUfuatiliaji wa Detractor12 Majibu yaliyopendekezwa1–2Mapitio yaUchunguzi wa tiketiSentensi ya 24h Baada ya kumalizaMoja kwa moja autoMaoni ya Chatya ya 4.5 · Binadamu 4.7LinganishaMtazamo wa AgentHesabu ya majibu na hesabuKocha wa1WATCH AVERAGETumia mwelekeo, sio alama moja2FOLLOW DETRACTORSSoma maoni3COMPARE FAIRLYya binadamu na
Ukurasa wa CSAT unachanganya kadi za alama, ufuatiliaji wa Wapinzani, maoni, idara na kuvunjika kwa wakala, na maoni ya mazungumzo.

tiketi utafiti ni ratiba baada ya kufunga (kwa kawaida 24 masaa baadaye). majibu chanya ni matokeo ya 4 au 5. Matumizi detractor foleni kwa matokeo ya 1 au 2 na kusoma tiketi / mazungumzo kabla ya kuwasiliana na mteja.

Maoni ya mazungumzo yanaripotiwa tofauti kwa mazungumzo yaliyosimamiwa na AI na ya kibinadamu. Ukubwa wa sampuli za chini haipaswi kutumiwa kuwa mawakala au mifano ya cheo.

Msaada wa msaada

Matangazo ya timu

Ukurasa wa Jukwaa la Barua pepe unamruhusu mwendeshaji aliyeidhinishwa kutuma ujumbe wa wakati mmoja kwa mawakala wote wanaofanya kazi, wakala waliochaguliwa au idara na ukaguzi hutuma historia.

Bidhaa ya Screen
Barua ya maombiMwandishi wa barua pepe ya timu inaonyesha watazamaji, somo, ujumbe na historia ya utoaji uliopita.Barua ya maombiNafasi ya KaziWapokeaji12DELIVERED11Kushindwa1Maisha ya kazi ya VIEWUkaguziWafanyakazi wote waWaliochaguliwaMada yaMsaada wa JulaiKamiliUjumbe wa UjumbeOrodha ya Mipango na UtekelezajiKamiliHistoria ya historiaMatangazo ya awali na matokeoMtazamo wa mtazamo1CHOOSE PEOPLEWote waliochaguliwa au timu2WRITE CLEARLYUjumbe na ujumbe3REVIEW HISTORYMatokeo ya kuthibitisha
Mwandishi wa barua pepe ya timu inaonyesha watazamaji, somo, ujumbe na historia ya utoaji uliopita.

Ukurasa huu ni kwa ujumbe wa ndani wa uendeshaji, sio masoko ya wateja. Chagua watazamaji wadogo sahihi, majina ya hakikisho na anwani, kisha tuma. Uwasilishaji hutumia njia ya barua pepe iliyowekwa na kurekodi matokeo.

Msaada wa msaada

Mailboxs, utoaji na Inbound email

Angalia jinsi OpsIQ inavyotuma barua pepe, kugeuza ujumbe unaoingia kwenye tiketi na kuthibitisha uwanja wa kutuma uko tayari.

Bidhaa ya Screen
Mipangilio ya barua pepeMipangilio ya barua pepe huchanganya routing nje, Kutoka utambulisho, kuingizwa kwa sanduku la barua, hundi za utoaji na barua pepe ya mtihani.Mipangilio ya barua pepeNafasi ya KaziKutokaSMTPMAILBOXES3Do yaNjia ya kupitaMaisha ya kazi ya VIEWSimu ya Mkono-ConventionSMTP Msaada wa InterfaceImeandaliwa kwaKutoka kwa utambulishoSupport <[email protected]>KamiliIMAP mailbox ya posta[email protected] • Ndani ya boksiUchaguzi waKutoaSPF · DKIM · DMARCNjia ya kupita1CHOOSE OUTBOUNDKuunganisha au SMTP2CONNECT INBOXIMAP au bomba ya3yaKuwasilisha na kuthibitisha
Mipangilio ya barua pepe huchanganya routing nje, Kutoka utambulisho, kuingizwa kwa sanduku la barua, hundi za utoaji na barua pepe ya mtihani.

Email ya Nje

Wasimamizi kamili wanaweza kuchagua kontakt ya barua pepe iliyopendekezwa; OpsIQ Kugeuka nyuma kwa configured SMTP Utoaji wa barua pepe wakati unaofaa. Weka kutambuliwa kutoka kwa jina / anwani, tuma mtihani na uangalie 24 Mafanikio ya saa / kushindwa metrics.

Mailboxes ya

A IMAP sanduku la barua linahitaji jina, anwani ya barua pepe, idara ya lengo, mwenyeji, bandari, hali ya usalama, mtumiaji, nenosiri, folda, uchaguzi wa hali na kibali cha hati. Kura ya maoni sasa Kusubiri kabla ya kufanya cron.

Kupumua kwa haraka

Katika server hiyo, bomba barua pepe inaweza kupita ujumbe RFC822 kavu moja kwa moja. server ya mbali barua unaweza POST ujumbe kavu na kuhifadhiwa inbound mwisho pointi kutumia token yake. Njia zote mbili kuingia deduplication sawa, threading na tiketi-routing mkondoni.

Kutoa

SPF / DKIM / DMARC ni ushahidi wa ushauri kwa ajili ya kusanidi kutoka kwenye kikoa. hundi ya kijani haihakikishi uwekaji wa kikasha, lakini kushindwa lazima fasta kabla ya kutuma ujumbe wa uzalishaji.

Msaada wa msaada

Msaada wa Portal Studio

Msaada wa Portal Studio miundo na kuchapisha uzoefu wa msaada unaoendana na wateja bila kuhitaji mali za picha za nje.

Bidhaa ya Screen
Msaada wa Portal StudioPortal Studio inaonyesha hakikisho la msikivu pamoja na mandhari, urambazaji, maarifa, tiketi, msaidizi, fomu, footer na CSS udhibiti.Msaada wa Portal StudioNafasi ya KaziTEMPLATEKisasaPrecipital yaDesktopHali ya dharuraRasimu yaMaisha ya kazi ya VIEWMandhari ya ThemeRangi ya Brand na typographyEdith yaUsafiri wa usafiriUjuzi, tiketi, msaidiziEdith yaFomu ya tiketiMashamba, routing na nakalaEdith yaMwandishi waKujali na kufanya maishaMapitio ya1CHOOSE TEMPLATEKuanzia muundo2PREVIEW SIZESDesktop kwa ajili ya simu3PUBLISH SAFELYBaada ya hapo, rejesta
Portal Studio inaonyesha hakikisho la msikivu pamoja na mandhari, urambazaji, maarifa, tiketi, msaidizi, fomu, footer na CSS udhibiti.

Tumia template kama hatua ya kuanzia, kisha usanidi mandhari, mpangilio, urambazaji, utafutaji wa maarifa, fomu ya tiketi, msaidizi, footer, brand, tabia ya tiketi; desturi CSS na mipangilio ya jumla. desktop, kibao na simu kabla ya kuchapisha.

Msaada wa msaada

Ujuzi wa nje

foleni ya ujuzi-gap inakusanya maswali kwa wateja AI haikuweza kujibu kwa ujasiri ili timu iweze kuboresha chanjo.

Bidhaa ya Screen
Ujuzi wa njeMstari wa mstari wa pengo ulikosa maswali au maswali ya kujiamini na nyimbo ikiwa timu imetatua.Ujuzi wa njeNafasi ya KaziOPEN GAPS28REPEATED9RESOLVED116Maisha ya kazi ya VIEWmipaka ya uhamiajiAlipoulizwa aliuliza 14 Mara kwa maraJuuMsaada wa mwisho wa wikiAlipoulizwa aliuliza 8 Mara kwa maraWastani wa katiMuda wa kurejeshaAlipoulizwa aliuliza 6 Mara kwa maraWastani wa katiAPI Mkoa waAlipoulizwa aliuliza 3 Mara kwa maraKiwango cha chini1REVIEW QUESTIONAngalia muktadha wa mazungumzo2CHOOSE FIXKuwasili au Haraka3RESOLVEAngalia jibu lako la pili
Mstari wa mstari wa pengo ulikosa maswali au maswali ya kujiamini na nyimbo ikiwa timu imetatua.

Fungua pengo la kusoma swali la awali na mazungumzo ya karibu, kisha chagua kurekebisha sahihi: sasisha makala iliyopo, uunda nakala mpya ya ujuzi, ongeza ukweli wa biashara, data sahihi ya uunganisho au mabadiliko ya maagizo.

Msaada wa msaada

Utawala wa ukurasa

Ukurasa wa utawala wa hali unawasiliana afya ya huduma na matukio kwa kutumia vipengele, hali za sasa na sasisho.

Bidhaa ya Screen
Utawala wa StatusUtawala wa hali orodha vipengele na matukio ili waendeshaji wanaweza kuchapisha habari ya huduma iliyo wazi, ya muda.Utawala wa StatusNafasi ya KaziOVERALLOperesheni yaMkutano wa7INCIDENTS1Maisha ya kazi ya VIEWTovuti ya tovutiOperesheni yaKijaniAPIUtendaji ulioharibikaTazamaEmail ya IntifentOperesheni yaKijaniTukio la sasaAPI Uchunguzi wa latencyKufungua1UPDATE COMPONENTChagua nchi ya wazi2POST INCIDENTTaarifa za muda mfupi3RESOLVEKaribu kwa muhtasari
Utawala wa hali orodha vipengele na matukio ili waendeshaji wanaweza kuchapisha habari ya huduma iliyo wazi, ya muda.

Tumia hali za sehemu mara kwa mara. Wakati tukio linaathiri wateja, kuchapisha taarifa ya awali, kuongeza sasisho zilizosasishwa wakati mabadiliko kama ukweli unavyobadilika, na karibu na muhtasari wa azimio la ufupi. Usitumie ukurasa wa hadhi kama logi ya ndani; uchunguzi nyeti ni katika OpsIQ na kumbukumbu za seva.

I

Kukamilisha AI yako

Configuration ya AI ni wapi unapochagua mtoa huduma wako wa AI, mfano, na udhibiti wa gharama. OpsIQ mashabiki wanachagua: Claude (Anthropic· GPT-4o (kwa Kiingereza:OpenAI), Gemini (Google), na Grok (xAI) unaweza kutumia mwenyewe. API Msingi wa (BYOK• Kusimamiwa na AI ikiwa inapatikana kwenye mpango wako.

Kuundwa kwa AI
Muundo wa ConfigurationJopo la mipangilio ya AI: mtoa huduma aliyesimamiwa / BYOK anayeingiza, chagua wa mfano, na mita ya kila mwezi ya bajeti ya ishara.Muundo wa ConfigurationNafasi ya KaziMuundo wa ConfigurationMtoa hudumaAI Iliyosimamiwa(Sauti yako ya mkononi)BYOK)Model ya Mfano· KulinganishaBajeti ya mwezi62%1TWO MODESKuundwa kwa AI au BYOK2PICK A MODELKiwango cha juu3BUDGETSKugeuza kofia na udhibiti wa gharama
Chagua AI iliyosimamiwa au ufunguo wako mwenyewe, chagua mfano wa kasi na kina, na uweke matumizi ya kila mwezi kwa bajeti ya ishara.

Kuchagua mtoa huduma

Claude (Anthropic)

Nguvu hoja, makini na ukweli, nzuri katika kufuata maelekezo tata. Mifano: claude-sonnet-4-20250514 Licha ya...3.5 Bora kwa: mazungumzo ya msaada, maswali ya kiufundi, uchambuzi wa kina.

GPT-4 (kwa Kiingereza:OpenAI)

Haraka, ubunifu, nzuri kwa ujumla maarifa. Mifano: gpt-4o, gpt-mini. bora kwa: majibu ya haraka, kuandika ubunifu, maswali pana ya ujuzi.

Gemini (Google ya Google)

Bora katika maswali ya ukweli, msaada lugha nyingi. Models:gemini-2.0-flash,gemini-1.5-pro. Bora kwa ajili ya: msaada lugha nyingi, lookups halisi.

Kikoa cha kiwango (xAI)

Haraka, majibu mfupi. Models: grok-3-mini-haraka. Bora kwa ajili ya: majibu haraka, tone casual.

BYOK Kuundwa kwa AI

BYOK (Kuweka mkono wako wa kulia)

Unatoa ufunguo wako mwenyewe wa API kutoka kwa mtoa huduma. Unalipa mtoaji moja kwa moja. udhibiti kamili juu ya uteuzi na matumizi ya mfano.

AI Iliyosimamiwa

Ni sehemu yako kama ilivyo kwa wengine. OpsIQ Mpango wa. API Muhimu inahitajika. Matumizi yanapimwa dhidi ya usawa wa mkopo wa AI.

Hatua kwa hatua ya ufungaji

1
Kujiandaa kwa ajili ya Configuration

Katika kipindi cha OpsIQ Nenda kwenye Mipangilio > Configuration ya AI.

2
Chagua mtoa huduma

Chagua mtoa huduma wako wa AI kutoka kwenye kushuka.

3
Kuingia kwa kuingia API Key key muhimu

Ikiwa unatumia BYOK Kuingia mwenyewe API Kwa AI iliyosimamiwa, hii inashughulikiwa moja kwa moja.

4
Chagua Model

Chagua mfano maalum wa kutumia. mifano midogo ni ya haraka na nafuu. Mifano kubwa hutoa majibu bora ya ubora.

5
Uchunguzi wa uhusiano

Bonyeza "Uunganisho wa Test" ili kuthibitisha API Kazi ya msingi na mfano ni kazi. alama ya kijani inamaanisha mafanikio.

6
Kuokoa

Bonyeza Save ili kuamsha usanidi wako wa AI.

Udhibiti wa gharama

Bajeti ya mwezi

Weka matumizi ya kila mwezi ya juu kwenye ishara za AI. Wakati bajeti imefikia, AI ina upungufu wa neema (majibu mafupi, hakuna auto-reply) badala ya kuacha kabisa.

Kiwango cha ubadilishaji wa kiwango

Ishara za juu kwa mazungumzo moja. huzuia mazungumzo ya kukimbia kutoka kuteketeza mikopo mingi.

Tahadhari ya chini

Na kama malipo yako ni chini ya kiwango cha riba, 50,000 Katika kesi hii, tahadhari ni juu ya kudhibiti wadudu.

Mipangilio ya nafasi ya kazi

Ikiwa unasimamia tovuti nyingi, kila nafasi ya kazi inaweza kutumia mtoa huduma tofauti, mfano, na bajeti. Nafasi ya kazi inarithi defaults za kimataifa isipokuwa kuzidiwa. Ili kusanidi kwa nafasi ya kufanya kazi: kubadili kwenye nafasi ya ajira, kisha nenda kwenye usanidi wa AI na uhifadhi mipangilio huko.

Kupata kupata API funguo za

Anthropic (Sauti ya Claude)

kwenda kuwa console.anthropic.com > API Keys > Kujenga ufunguo. nakala muhimu kuanzia na "sk-ant-".

OpenAI (Sauti ya G)

kwenda kuwa platform.openai.com > API Keys > Unda ufunguo mpya wa siri. nakala muhimu kuanzia na "sk-".

Google (kwa Kiingereza)Gemini)

kwenda kuwa aistudio.google.com “Kwa kuwa API Chagua moja kwa ajili ya mradi wako, na kisha bofya kitufe cha kuingia.

XI (Grok)

kwenda kuwa console.x.ai > API Tumia na ujenge hoja yako.

Kuthibitisha yako ya kubuni

Kwa mfano:
Baada ya kuingia ufunguo wako wa API, bonyeza "Uunganisho wa Test." Unapaswa kuona alama ya kijani na jibu la sampuli kutoka kwa AI.
Nini cha kufanya:

Ikiwa jaribio hilo litashindwa: (1) Angalia kwamba API Ni sahihi (hakuna nafasi ya ziada). (2) Angalia kwamba akaunti yako ina bili iliyowekwa na mtoa huduma. (3) Angalia kwamba jina la kikoa ni halali. (4) Ikiwa unatumia AI iliyosimamiwa, hakikisha leseni yako inafanya kazi.

Ni nani mtoa huduma bora?+

Claude ni bora kwa mazungumzo ya msaada. GPT-4o ni haraka na rahisi. Gemini inashughulikia lugha nyingi vizuri. jaribu kila mmoja na uone ambayo hutoa matokeo mazuri kwa kesi yako maalum ya matumizi.

Je, ninaweza kubadilisha mwenyeji baadaye?+

mabadiliko ya mtoa huduma na API Muhimu wakati wowote, historia ya mazungumzo ya sasa imehifadhiwa. AI itatumia mtoa huduma mpya kwa mazungumzo yote ya baadaye.

Nini kinatokea wakati mimi kuondoka kutoka mikopo?+

AI inaharibika kwa neema: majibu yanakuwa mafupi, ya kujitegemea, na admin inaonyesha onyo la usawa wa chini. kufuatilia msingi, tiketi, na CRM kuendelea kufanya kazi bila AI.

I

Smart & cheap zaidi wateja chat

Seti ya udhibiti wa kuchagua ambao hufanya mazungumzo yako ya wateja iwe nadhifu (hii ni sababu katika akaunti ya mteja kama wakala wa kibinadamu) au nafuu (inatuma AI chini, au majibu katika hatua chache). Kila udhibiti umeondolewa kwa default na kujitegemea, kugeuka moja juu ya kamwe mabadiliko yoyote ya tabia nyingine. Wengi wanaishi chini ya Mipangilio > Chat Mteja> Behaviour; wachache ni Kuweka AI yako na Treni AI yako.

Njia ya haraka (Agent Mode)

Chatbot ya kawaida hujibu swali moja kutoka kwa kuangalia moja. Mtindo wa Agent juu, msaidizi anaweza kufanya hundi kadhaa za akaunti ya kusoma tu kwa upande mmoja na kuzitaja msalaba, kwa mfano "Je, nina tiketi za wazi, na ni usawa wangu wa kutosha kwa upya wangu ujao?" inajibiwa katika jibu moja na hesabu zilizofanywa. Inahusisha tu wateja waliothibitishwa kwenye akaunti au maswali ya kurejesha; kila kitu kingine kinaendesha njia ya kawaida ya malipo ya moja.

Mtindo wa Agent

Hadi kwa kuangalia wachache tu kwa upande, msalaba-upendeleo kabla ya kujibu. Turn juu wakati una jukwaa kushikamana (WHMCS, Shopify, Stripe, Zendesk, nk). Off = tabia moja-kuangalia, unchanged.

Kufikiria kwa kina majibu ya wakala

Jinsi ngumu mfano sababu juu ya zamu ngumu (chini / kati / juu) Kuanza chini; maswali mengi ya msaada yanashughulikiwa vizuri huko.

Mfano wa Agent

Pins mfano nguvu tu kwa ajili ya tata wakala zamu, hivyo kila siku chat anakaa juu ya mwanga, bei nafuu mfano na vigumu anarudi kulipa kwa kina. Blank = yako ya kawaida wateja-chat mfano.

Mpango wa Mbele · Majibu ya moja kwa moja (beta)

Hatua ndogo ya kupanga huamua ni kuangalia kwa kuvuta na ikiwa msingi wa ujuzi unahitajika, basi anajibu katika wito mmoja kuu badala ya hatua kadhaa. Kikundi cha kuingiza chini ya hali ya wakala. Haiwezi kuwezeshwa isipokuwa mode ya Wakala iko kwenye ubora wa jibu sawa, simu chache juu ya maswali mbalimbali ya sehemu.

Majadiliano na uelewa

Kumbukumbu ya mazungumzo (beta)

Huhifadhi muhtasari mfupi wa ujumbe wa zamani (jina, tiketi / idadi ankara, kiasi, maamuzi) hivyo msaidizi anabakia sambamba katika mijadala ndefu sana bila resending transcript nzima. Best kwa msaada-zito, threads muda mrefu; jozi na Agent mode.

Uvumilivu wa Typo

Anasoma typos ndogo ("tickets yangu wazi", "invocies kutozwa") kama maneno lengo hivyo habari sahihi ni kupatikana badala ya missed. Kazi na kila jukwaa kushikamana. Off kwa default; muhimu kwa ajili ya simu-zito mazungumzo.

Maelezo ya akaunti

Tu anaunganisha snapshot ya akaunti ya mteja wakati swali ni kweli kuhusu akaunti yao (sawa, ankara, tiketi, huduma), kuruka juu ya maswali ya jumla. Kata gharama bila kupoteza ubora. Msaidizi bado anaweza kupata akaunti kuishi wakati kugeuka inahitaji.

Gharama ya kuokoa

Tafuta kwa ajili ya kutafuta (beta)

"Hi", "shukrani" na "ok" hazisababisha utafutaji wa msingi wa maarifa, majibu hayo hayatumii. Ujumbe wowote wenye maudhui halisi bado hutafuta kama kawaida.

Majibu ya muda mrefu (tokens)

Jibu urefu ni sehemu ya gharama kubwa zaidi ya wito, hivyo cap busara (karibu 500 kwa msaada) ni moja ya ufanisi zaidi chat gharama udhibiti. Tu hupunguza kikomo yako ya kimataifa, kamwe kuinua yake.

Kujiandaa kwa ajili ya AI

Kufikiri kina (Customer & admin chat)

Ni kiasi gani mfano anadhani kabla ya kujibu (chini kwa juu). Weka wateja kuzungumza juu kidogo / chini kwa kasi; hifadhi mazingira ya juu kwa ajili ya uchambuzi na copilot admin.

Mfano wa kazi (kwa mfano, kwa kila kazi)

Kila uso wa AI (mazungumzo ya moja kwa moja, rasimu za tiketi, muhtasari, uchambuzi, copilot admin, matangazo, Site Intelligence na zaidi) inaweza kukimbia juu ya mfano wake mwenyewe. Mwanga ambapo masuala ya kasi, nguvu ambapo mambo ya ubora. Blank juu ya uso = mtoa huduma default kwa kazi hiyo.

Usimamizi wa gharama za mazungumzo

Copilot admin inaweza kuweka kumbukumbu ya kazi imefungwa na kupakia tu zana mahitaji ya swali (vifaa vya kila) badala ya kila chombo.

Treni ya AI

Maelekezo ya Compress

Maagizo yako yanatumwa kila upande, kwa hivyo urefu wao ni gharama ya mara kwa mara. kifungo cha Compress kinaandika upya nafasi ya kusema kitu sawa kwa maneno machache. Inakataa kuandika tena ikiwa itaacha chochote {variable} au kuadhimisha na kuvuka kutoka utoto kuingia utu uzima.

"Ni nini tayari katika ubongo" (ℹ️)

Kuonyesha nini OpsIQ Tayari unajua kuhusu biashara yako kwa kila yanayopangwa, hivyo unaweza kufuta chochote ambacho ulikuwa unarudia katika maelekezo yako mwenyewe.

💡
Kwa msaada mfupi wa kuzungumza pembejeo (mafundisho + data ya akaunti + historia, kutuma kila zamu) kwa kawaida gharama zaidi kuliko jibu fupi, caching na mazingira konda kusaidia wengi huko. Kwa maudhui yaliyozalishwa kwa muda mrefu pato linatawala. Kipindi cha urefu wa majibu na kina cha kufikiri cha chini kulipa huko. Angalia Weka AI yako ili kuweka caching haraka juu, ambayo inafanya sehemu kubwa ya mara kwa mara ya kila upande kuwa nafuu.
Je, mabadiliko haya yanabadilisha jinsi ya kujibu maswali?+

Kila udhibiti ni mbali na default na huru. kugeuka moja juu tu anaongeza tabia yake; kugeuka ni mbali anarudi chat kwa jinsi hasa kazi kabla.

Ni amri gani ninapaswa kuzitimiza?+

Kukimbia kila siku chat juu ya mwanga mfano na pin nguvu Agent mfano. Kisha, kama una jukwaa kushikamana, kuwezesha wakala mode, kisha Mpango mbele, kisha Long-kubadilishana kumbukumbu. kisha konda mazingira, skip-KB kwa-greetings, na jibu cap. Hatimaye compress maelekezo yako. Watch chache halisi mazungumzo baada ya mabadiliko kila mmoja.

Admin Agent kit: utafutaji wa wavuti, vitabu vya kukimbia, ujumbe, uhamisho wa faili

Admin AI chat ni mhandisi wa kazi, si tu sanduku la swali. Inaweza kufanya utafiti fixes kwenye mtandao, kuweka maktaba ya taratibu zako za uendeshaji, doria server yako juu ya ratiba, na hoja faili. Wengi wa hii inaendeshwa kwa kuuliza kwa ajili yake katika kuzungumza; jambo moja wewe configure up mbele ni ambayo mtandao kutafuta mtoa huduma anatumia, juu ya Seti up ukurasa wako wa AI.

Mtandao wa kutafuta

Kujengwa katika

Wakala hutafuta wavuti kwa docs, ujumbe wa makosa na habari ya sasa wakati inafanya kazi. Kutoka kwenye sanduku hili hutumia DuckDuckGo, ambayo inahitaji hakuna ufunguo na hakuna usanidi.

Vitabu vya Runbooks

Katika chat

A maktaba kuokolewa ya taratibu zako ("jinsi sisi kufanya X hapa"). wakala anaandika moja chini baada ya nailing kazi gumu na ifuatavyo wakati ujao, hivyo kujua-jinsi kuishi mwisho wa chat.

Misheni ya

Mipango ya

Kila asubuhi, angalia nafasi ya disk na kumbukumbu za makosa na uniambie." Matokeo yanafika kwenye bell yako ya admin.

Uhamisho wa File

Katika chat

Kuomba faili ya logi na kupata kiungo cha kupakua binafsi, au kuwa na faili moja iliyonakiliwa kutoka kwa seva moja iliyounganishwa hadi nyingine. Wote wamefungwa katika 5 MB.

Usimamizi wa Mtandao wa Wakala (kusanidi AI yako)

Mtafutaji wa Huduma

Nini wakala wa mtandao search anatumia. default ni DuckDuckGo: keyless, bure, kazi juu ya kila kufunga. Brave Search, Tavily na Serper.dev (Google matokeo) mara nyingi hurudi matokeo bora lakini kila moja inahitaji. API Kama mtoa huduma muhimu inashindwa kwa sababu yoyote (muhimu mbaya, upendeleo kutumika juu, mtandao shida), kwamba utafutaji ni nyuma ya DuckDuckGo moja kwa moja, hivyo kutafuta kamwe huenda giza.

Utafutaji wa Kutafuta API Key key muhimu

Muhimu kwa mtoa huduma wako aliyechaguliwa, tu inahitajika kwa ujasiri, Tavily au Serper. Mara baada ya kuokolewa ni masked na kamwe kuonyeshwa kwenye ukurasa tena; kuweka mpya kuchukua nafasi yake. Mtoa muhimu inakuwa kazi tu wakati mtoaji wote na ufunguo wake ni kuokolewa.

Vitabu vya Runbooks

Wakati wakala amefanya kazi kupitia kazi unataka kufanya njia hiyo tena, sema "okoa kwamba kama kitabu cha kukimbia kinachoitwa kusafisha usiku". Kutoka wakati huo juu yake anaona kitabu kwa jina katika kila kikao, na unapoomba kazi kwa jina (au kuielezea) inavuta hatua na kufuata yao. Unaweza kuuliza orodha, update au kufuta vitabu vya runbooks wakati wowote.

💡
Kitabu cha kukimbia ni mwongozo, sio kupita bure. Wakati wakala anafuata moja, kila hatua ambayo itabadilika seva bado inakwenda kupitia hali yako ya sasa ya ruhusa na inaonyesha kadi za idhini za kawaida.

Misheni ya

Ujumbe ni kazi ya mara kwa mara ambayo wakala anaendesha peke yake: kila siku katika saa iliyowekwa, au kila wiki kwenye siku iliyowekwa. Misheni ni kusoma tu na kubuni. Wanaweza kusoma seva, data na wavuti, lakini hawawezi kubadilisha kitu chochote; wao kuchunguza na kuripoti. Wakati ujumbe unamalizika, matokeo ya ardhi kama taarifa juu ya kengele yako admin.

⚠️
Misheni kukimbia mbali OpsIQ cron, hivyo inahitaji kuanzisha (angalia Cron na automatisering). moja-off "kukimbia sasa" kutoka kazi chat hata kati ya cron anaendesha juu ya server wengi.

Kuhamisha files

Uliza faili ("nipatie logi ya makosa ya leo kutoka kwenye seva ya wavuti") na wakala anaifungua na kujibu kwa kiungo cha kupakua binafsi. Kiunga hiki kinafanya kazi tu kwa wasimamizi waliosainiwa na hupungua baada ya siku moja. Faili zimefungwa katika 5 MB; kwa chochote kikubwa, uliza wakala wa kuikandamiza au kuipunguza kwenye seva kwanza.

Wakala anaweza pia nakala ya faili moja kati ya seva mbili zilizounganishwa, tena hadi 5 MB. Kuandika kwenye marudio hutendewa kama mabadiliko mengine yoyote hufanya: katika hali ya kuuliza unapata kadi ya idhini kwanza, faili iliyopo inaungwa mkono, na nakala hiyo inaweza kurekebishwa. Kwa usalama, maudhui ya faili yanasomwa upya kutoka kwa chanzo wakati nakala inatumiwa, sio kuchukuliwa kutoka kwa soga.

I

Treni yako ya AI

Mafunzo ni pale ambapo wewe kujifunza OpsIQ Jinsi ya kutenda. Unaandika hushawishi kwamba kufafanua utu, mipaka, lengo la ujuzi, na sheria za kuongeza. Fikiria kama kuandika mwongozo wa mafunzo kwa wakala mpya wa msaada.

Treni ya AI
Treni yako ya AIMhariri wa maelekezo ya AI na tabo za Wateja / Admin na sauti wazi ya Kiingereza, daima na kamwe sheria.Treni yako ya AINafasi ya KaziWateja wa AUsimamizi wa AIToni yaKuwa na furaha, kamwe kuwa na wasiwasi.DaimaKuwasilisha hati ya mashtaka kwa ajili ya kesi za jinai.HapanaKurejesha fedha bila ya kuangalia akaunti.1TWO MANUALSMtumiaji: admin2PLAIN ENGLISHKwa mfano, wakati mwingine, kamwe3GROUNDEDZaidi ya ujuzi wako msingi
Treni AI kama kuajiri mpya, Wateja na Admin miongozo iliyoandikwa kwa Kiingereza wazi (tone, daima, kamwe), msingi katika KB yako.

Maeneo mawili ya mafunzo

Wateja wa haraka

Inadhibiti jinsi AI inazungumza na wateja wako katika widget ya mazungumzo. Hii ni muhimu zaidi haraka kupata haki.

Usimamizi wa haraka

Inadhibiti jinsi AI inasaidia timu yako ya admin katika dashibodi ya mwendeshaji. Hii inashughulikia maswali ya ndani na utekelezaji wa hatua.

Kuajiri kampuni kubwa ya mwenyeji wa wavuti haraka

Wateja wako wa AI haraka wanapaswa kufunika maeneo haya:

1
Utambulisho wa utambulisho

Kwa mfano: "Wewe ni Luna, msaidizi wa msaada wa wateja wa kirafiki na mwenye ujuzi kwa Duka la Acme."

2
Aina ya Tone na Mtindo

Kwa mfano: "Kuwa mtaalamu lakini joto. Tumia lugha rahisi. epuka jargon.2-3 Kwa mfano, " max.

3
Mipaka ya ujuzi

Mfano: "Unajua kuhusu bidhaa zetu, bei, usafirishaji na sera ya kurudi. hujui kuhusu bidhaa za mshindani au maamuzi ya kampuni ya ndani."

4
Kanuni za kuongeza

Mfano: "Mteja kwa wakala wa kibinadamu wakati: mteja anaomba marejesho, ataja hatua za kisheria, anaripoti suala la usalama, au anauliza swali hilo mara tatu."

5
Mambo ambayo kamwe kufanya

"Kamwe usiahidi marejesho. Usishiriki kamwe fomu za bei ya ndani. Ufanye vipengele vya bidhaa ambavyo havipo. Usitoe ushauri wa matibabu, kisheria au kifedha."

Mfano wa haraka

Mfano wa Wateja AI haraka · Online Store
You are Aria, a friendly customer support assistant for TechGear.

PERSONALITY:
- Warm and professional
- Concise (2-3 paragraphs max per response)
- Use simple language, no jargon
- If unsure, say so honestly

KNOWLEDGE:
- Our products: laptops, accessories, software subscriptions
- Pricing: as listed in the knowledge base
- Shipping: free over $50, 3-5 business days standard, 1-2 days express ($12)
- Returns: 30-day money-back guarantee, must be in original condition

ESCALATION (hand off to human):
- Refund requests over $100
- Account security concerns
- Legal threats or complaints
- Customer explicitly asks for a human

NEVER DO:
- Promise specific delivery dates (say "estimated")
- Share discount codes not in the knowledge base
- Make up product specifications
- Give financial or legal advice
Mfano wa Wateja AI haraka · Kampuni ya mwenyeji
You are Atlas, an AI assistant for CloudHost web hosting.

TONE: Technical but accessible. Assume the customer has basic web knowledge.

KNOWLEDGE:
- Shared hosting, VPS, dedicated servers
- cPanel, DNS, SSL, email configuration
- WordPress, Joomla, Drupal installation
- Common error codes and troubleshooting

ESCALATION:
- Server outages affecting multiple customers
- Data loss or security breach reports
- Billing disputes over $50
- Complex migration requests

BOUNDARIES:
- Do NOT access customer servers or databases
- Do NOT change DNS records or passwords
- Always recommend the customer makes changes themselves
- For code issues, suggest steps but clarify you cannot debug their application

Kurejesha haraka yako kwa muda

1
Kuanza na misingi

Anza na utambulisho, sauti, na mipaka muhimu. Usijaribu kufunika kila kitu kwa siku moja.

2
Mapitio ya kila wiki

Soma mazungumzo ambapo AI ilitoa majibu mabaya au ya chini.

3
Kuharakisha kwa haraka

Kwa mfano: ikiwa AI inaendelea kuahidi malipo, ongeza "Kamwe usiahidi marejesho. Sema utaenea kwa timu ya kulipa."

4
Kuongeza ujuzi

Ikiwa AI haiwezi kujibu swali, ongeza jibu kwa Msingi wa Maarifa badala ya kujaribu kutosheleza kila kitu haraka.

⚠️
Weka haraka yako chini ya maneno ya 2,000. Mapendekezo ya muda mrefu yanaweza kuchanganya AI na kuongeza gharama za ishara.
Kuna tofauti gani kati ya msingi wa ujuzi na maarifa?+

Msingi wa ujuzi hutoa habari sahihi (maelezo ya bidhaa, bei, sera). AI inasoma wote wawili, lakini tabia ya haraka huunda wakati KB inatoa majibu.

Je, ninaweza kupata huduma tofauti kwa wateja?+

Haraka ni kwa nafasi ya kazi. Ikiwa unahitaji tabia tofauti ya AI kwa idara mbalimbali, tumia msingi wa ujuzi kutoa taarifa maalum za idara na kutaja muktadha wa idara katika haraka yako.

I

Historia ya

Historia ya AI inaonyesha kila mazungumzo ambayo AI imekuwa nayo na wateja na wasimamizi. Tumia ili kukagua utendaji wa AI, kupata majibu yasiyofaa, na kutambua mapungufu ya mafunzo.

Historia ya
Historia yalogi ya AI inageuka na beji za aina, swali na jibu, wakati wa majibu na matokeo.Historia yaNafasi ya KaziKila kitu kinakwenda kwa kasi, na kila kitu ni sawa.mazungumzoQ: Je, ni wapi amri yangu?A: Kuwasili leo, na kufuatiwa na ...0.9sMajibu yajibutiketi ya ndegeMajibu ya maswali kwa T-12345Malipo ya fidia yaliyoidhinishwa1.4sdraftedUsimamizi wa adminKukagua tiketi za ndege wiki hii12 Maelezo ya jumla yaliyorudishwa2.1sKufanyamazungumzoQ: Kukamilisha mpango wanguKutolewa kwa mtu0.7sescalated1EVERY TURNKuuliza, jibu, hatua2SEARCHABLEFilter & Export ya nje3OWNER-ONLYUfuatiliaji wa Ufuatiliaji wa Ufuatiliaji
Kila AI kugeuka (chat, rasimu ya tiketi, hatua admin) watumiaji na haraka halisi, jibu, muda na matokeo.

Nini kila mazungumzo inaonyesha

Tarehe na wakati

Wakati wa mazungumzo hayo Mhe.

Utambulisho wa Wateja

Jina na barua pepe ikiwa unajua, vinginevyo IP ya nchi.

Kipindi

widget Chat, tiketi ya auto-reply, rasimu ya barua pepe, au admin AI.

Ujumbe

Nakala kamili ya mazungumzo: ujumbe wa wateja na majibu ya AI.

Matumizi ya

Ni ishara ngapi mazungumzo zinazotumiwa. Matumizi ya ishara ya juu yanaweza kuonyesha AI inatoa majibu zaidi ya verbose au mazungumzo yalikwenda katika duru.

Hatua zilizochukuliwa

Vitendo vyovyote ambavyo AI alitekeleza wakati wa mazungumzo (angalia utaratibu, iliyoundwa tiketi, nk).

Kiwango cha juu

Ikiwa CSAT imewezeshwa, kiwango cha kuridhika kwa mteja kwa mazungumzo haya.

Kutafuta matatizo

Kutafuta neno la msingi

Tafuta mada maalum ili kuona jinsi AI inavyoshughulikia. mfano: kutafuta "kurejesha" kuangalia ikiwa AI inafuata sera yako ya marejesho.

Filter ya rating

Onyesha mazungumzo ya chini ili kuzingatia wateja wasioridhika.

Filter ya channel

Onyesha tu tiketi ya gari-replies kwa ukaguzi majibu automatiska tofauti kutoka chat.

Kutumika kwa ajili ya matumizi

Mazungumzo yaliyotokana na juu yanaweza kuonyesha matatizo: kukimbia kwa AI, kwenda katika duru, au kushindwa kujibu swali.

Ukaguzi wa kila wiki

1
Angalia Majadiliano ya Chini

Je, ni nini kilichoenda vibaya? ilikuwa pengo la maarifa, suala la sauti, au jibu lisilo sahihi?

2
Angalia Majadiliano ya Juu

Hii inaweza kuonyesha mkanganyiko. Je, AI ilirudia yenyewe? Je, imeshindwa kuelewa swali hili?

3
Mafunzo ya update

Kwa mapungufu ya ujuzi, ongeza makala kwenye Msingi wa Maarifa. Kwa masuala ya tabia, sasisha AI haraka. Kwa majibu ya mara kwa mara yasiyo sahihi, ongeza sheria za marekebisho wazi.

Kutafuta ujuzi wa mapungufu

Kwa mfano:
Unatafuta historia ya "kuanzisha" na kupata 15 Mazungumzo ambapo AI alisema "Sina maelekezo maalum ya ufungaji wa bidhaa hii."
Nini cha kufanya:

Hii inamaanisha Msingi wako wa Maarifa ni kukosa miongozo ya ufungaji. Unda makala za msingi za ujuzi kwa hatua za ufungaji wa kila bidhaa. Baada ya kuziongeza, mtihani kwa kuuliza maswali ya ufungaji wa AI.

I

Ufahamu wa

AI Insights moja kwa moja huchambua mifumo ya mazungumzo na matokeo yanayoweza kutekelezwa: maswali ya kawaida, mwenendo wa kuridhika, mapungufu ya ujuzi, na mwelekeo wa kuongezeka.

Ufahamu wa
Ufahamu wa akili (Intelligence Hub)Hub ya Akili: AI Leo Fupi, Tahadhari za Smart, Score-a-Lead / Analyse-aPage chombo, na 14- Siku ya trafiki chati.Ufahamu waNafasi ya KaziUtajiri wa leoTrafiki ya Juu 12%; 3 Mwongozo wa kina;2Mipango inahitaji ufuatiliaji.Tahadhari ya SmartMakosa ya CheckoutBonyeza juu ya /pricingMwongozo Mpya wa Kuongoza Kutoka kwetuMapato ya kabla wiki iliyopitaKuongoza / Kuonyesha ukurasaIP au URL…Kuendesha14 Siku ya Usafiri wa Reli1Utajiri wa leoAkisoma taarifa ya asubuhi2SMART ALERTSAnomaes yaongezeka3ON DEMANDKuweka alama ya kuongoza · Kuchunguza ukurasa
Hub ya Akili halisi: AI-iliyoandikwa Leo Brief, Tahadhari za Smart kwa makosa, juu ya mahitaji ya kuongoza bao na uchambuzi wa ukurasa, na 14 Siku ya Usafiri wa Umma.

Nini maoni ya kuonyesha

Maswali ya Juu

Ikiwa "Ninawezaje kuweka upya nenosiri langu?" ni #1, msingi wako wa ujuzi unahitaji mwongozo maarufu wa makazi ya nywila.

Mwelekeo wa kuridhika

CSAT alama baada ya muda. ni AI kuridhika kuboresha au kupungua? matone Sudden inaweza kuonyesha mabadiliko ya msingi wa maarifa ambayo kuvunja kitu.

Kiwango cha

Ni asilimia gani ya mazungumzo ambayo AI hutatua bila kuingilia kati kwa binadamu? kiwango cha juu 70% Nzuri sana hapa chini. 50% Hii ina maana kwamba inahitaji mafunzo zaidi.

Sababu za kuongezeka

Kwa nini mazungumzo yanatolewa kwa wanadamu. Sababu za kawaida: mteja aliomba binadamu, AI haikuweza kujibu, mada nyeti, suala la bili.

Ujuzi wa nje

Mada ambazo AI mara nyingi husema "Sijui" au hutoa majibu ya kujiamini.

Urefu wa mazungumzo

Mazungumzo ya muda mrefu sana (10+ ujumbe) yanaweza kuonyesha AI sio kuelewa swali.

Kutumia mawazo ya kuboresha

Kwa mfano:
Akili inaonyesha kwamba 23%"Wateja wanauliza juu ya udhamini" na AI haikuweza kujibu.
Nini cha kufanya:

Huu ni uelewa wa wazi.1) Andika makala ya udhamini kamili katika Msingi wa Maarifa kufunika masharti yote ya udhamini, mchakato wa madai, na kutengwa.2• Kusasisha AI haraka kwa taarifa ya udhamini wa kumbukumbu. (3• Fuatilia ufahamu wa AI wiki ijayo ili kuona ikiwa ongezeko la udhamini linapungua.

I

Mwongozo wa kucheza

Mkurugenzi Mtendaji wa Halmashauri ya OpsIQ Kusaidia timu yako kuongoza OpsIQ Kutoka ndani ya dashibodi ya admin. Unaweza kuuliza kuangalia data, kuelezea vipengele, muhtasari tiketi, na kutekeleza vitendo vya jukwaa.

Usimamizi wa AI
Mwongozo wa kuchezaSanduku la amri ya Ask-OpsIQ na kadi ya hatua ya jukwaa iliyoonyeshwa na AI inayoonyesha vigezo na kuthibitisha / cel.Kuuliza maswali OpsIQNafasi ya KaziKuuliza maswali OpsIQWeka huduma kwa akaunti ya muda mrefu #4821IHatua ya kusitisha: kusimamisha_ hudumaAkaunti: #4821 (overdue $120)Jukwaa la: WHMCS · Kubadilishwa · UkaguziUthibitisho wa kuthibitishaKuondolewa kwa1ASK ANYTHINGAmri za Kiingereza2PROPOSE FIRSTHatua zilizochukuliwa kabla ya kuanza3YOU CONFIRMKuchapishwa na ukaguzi
Mwambie admin AI nini unataka katika wazi Kiingereza; inapendekeza hatua halisi (iliyopitiwa, kurekebishwa, kukaguliwa) na kusubiri kwa kuthibitisha yako.

Nini ambacho Mkurugenzi anaweza kufanya

Angalia data

Swali: "Nionyeshe tiketi zote kutoka kwa [email protected]" au "Hali ya utaratibu #ORD-5523?"

Muhtasari

Swali: "Je! 10"Maswali ya juu" au "Nini ni muhimu zaidi katika wiki hii?"

Eleza maelezo ya

Swali: "Je, ni nini kinachosababisha mimi kuwa mjamzito?" au "jinsi ya kuzuia mimba?

Vitendo vya kutosha

Swali: "Je, unaweza kununua tiketi kwa ajili ya bure?"[email protected] Kuhusu malipo au "Close tiketi T-12345"

Maswali ya Jukwaa

Swali: "Ni wangapi ambao tumewahi kukutana nao?" au "Je, ni nini tunachojua kuhusu mwezi huu?

Mfano wa mazungumzo

Kuangalia kwa ajili ya wateja

Kwa mfano:
Meneja anauliza: "Kupata wateja [email protected]"Natumai utaonyesha shughuli zako za hivi karibuni"
Nini cha kufanya:

AI inaonekana juu ya mteja katika vyanzo vyote vya data vilivyounganishwa: vikao vya wageni, tiketi, mazungumzo ya kuzungumza, maagizo, na mawasiliano ya CRM. Inarudi muhtasari wa shughuli za hivi karibuni na viungo kwa kila kitu.

Kupata muhtasari wa kila siku

Kwa mfano:
Swali: "Ni nini kilichotokea leo?"
Nini cha kufanya:

Kwa maneno mengine: “Leo umekuwa 245 Wageni (up) 12%), 8tiketi ya ndege (3 Kuundwa kwa AI,2Amri mpya ya jumla $198 Kwa hivyo, na1"Uchunguzi wa mazungumzo juu ya ucheleweshaji wa usafirishaji."

Kupitisha hatua

Kwa mfano:
Admin anauliza: "Kubadilisha tiketi T-5523 kipaumbele cha dharura"
Nini cha kufanya:

AI inathibitisha: "Mimi kubadilisha tiketi T-5523 kipaumbele kutoka kawaida kwa dharura. Hii itaathiri SLA timer. Kuhakikisha?" Unaweza kuthibitisha, na hatua ni kutekelezwa.

💡
Admin AI hufanya tu vitendo ambavyo vimesajiliwa katika Msajili wa Hatua. Haiwezi kuunda vitendo au mifumo ya upatikanaji nje OpsIQ.
I

Wateja wa AI

Sehemu hii inashughulikia matukio ya kawaida ya AI yanayoambatana na wateja na vidokezo vya tabia vinavyotarajiwa na mafunzo.

Wateja wa A
Wateja wa AIMaktaba ya maswali ya wateja iliunganishwa na tabia inayotarajiwa ya AI na tag ya matokeo kwa kila mmoja.Wateja wa AINafasi ya KaziScenario Library · Kutarajia tabia ya AI“Nipo wapi amri yangu?”Angalia kwa makini simu ya mkononi, fuatiliaSuluhisho la ufumbuzi“Tunahitaji ukombozi wa kweli”Kukiri, kamwe ahadi · mkono kwa binadamuHandy ya“Je, huduma hiyo inapungua?”Angalia hali ya sasa, ripotiHali ya“Anza akaunti yangu”Kuthibitisha nia, kisha njia ya mwanadamuUthibitisho wa kuthibitisha1SCENARIOSMaswali ya kawaida2EXPECTEDJinsi ya kujibu3yaKupata mapungufu ya mafunzo
Maktaba ya maswali halisi ya wateja na jinsi AI inapaswa kushughulikia kila mmoja, kupima mafunzo yako na kupata mapungufu.

Maktaba ya Scenario

Hali ya Uchunguzi

Kwa mfano:
Mteja: "Kipindi changu cha agizo langu #12345?"
Nini cha kufanya:

Kutarajia tabia ya: (1• Angalia utaratibu kupitia kiunganishi cha jukwaa. (2• Taarifa ya hali ya sasa (kushughulikia, kusafirishwa, kutolewa).3(i) Kuongeza idadi ya watumishi ikiwa ni pamoja na;4) Ikiwa amri imechelewa, kukubali na kutoa muda unaokadiriwa. (5• Kamwe usiruhusu taarifa za uchunguzi.

Password ya maombi

Kwa mfano:
Mteja: "Nimesahau nenosiri langu na siwezi kuingia"
Nini cha kufanya:

Kutarajia tabia ya: (1(i) Kutoa maelezo ya hatua kwa hatua kutoka kwenye msingi wa ujuzi.2) Kujumuisha kiungo cha upya au njia ya ukurasa. (3(i) Kumbuka kwamba anwani ya barua pepe inaweza kuchukua dakika chache.4(i) Kupendekeza kuangalia spamfolder.5Ikiwa mteja bado hawezi kurudi, zidi kwa mwanadamu.

Maombi ya maombi

Kwa mfano:
Mteja: "Unawezaje kuongeza mode ya giza kwenye programu ya simu?"
Nini cha kufanya:

Kutarajia tabia ya: (1• Tunakushukuru kwa maoni yako.)2• Eleza jinsi maombi ya kipengele yanashughulikiwa (iliyopitiwa, upya, iliyowekwa kipaumbele).3Usiahidi kuwa utajenga ukuta.4Kama kuna kitu kama hicho, eleza.

Majadiliano ya Billing

Kwa mfano:
Mteja: "Nilishtakiwa lakini huduma yangu haifanyi kazi"
Nini cha kufanya:

Kutarajia tabia ya: (1(a) Kukubaliana na hali ya kuvunjika moyo.2• Angalia hali ya huduma ikiwa inawezekana.3(i) Kuwasilisha nyaraka zote za Wizara kwa mujibu wa masharti ya kifungu cha (1).4Usiahidi kurudi nyuma.5) Kuweka kipaumbele cha tiketi kwa ngazi ya juu.

Maswali ya nje

Kwa mfano:
Swali: "Hali ya hewa ni nini katika London leo?"
Nini cha kufanya:

Kutarajia tabia ya: (1“Mimi ni msaidizi wako wa msaada na ninaweza kusaidia kwa maswali kuhusu bidhaa zetu na huduma. Kwa habari za hali ya hewa, jaribu huduma ya hali ya anga.”2• Waulize kama una swali la bidhaa.

Jinsi ya kufanya jaribio la mteja?+

Fungua tovuti yako katika kivinjari cha kibinafsi / kisichojulikana na kuzungumza na AI kama mteja. Jaribu maswali ya kawaida, kesi za makali, na hali za adversarial. Angalia kwamba AI inafuata sheria zako za haraka na hutumia maudhui ya msingi wa maarifa kwa usahihi.

I

Msingi wa ujuzi

Msingi wa Maarifa ni maktaba ya makala ambayo AI hutumia kujibu maswali. Wakati mteja anauliza kitu, AI inatafuta msingi wa ujuzi kwa nakala husika na kuitumia kuzalisha majibu sahihi, yaliyotokana na msingi.

Msingi wa ujuzi
Msingi wa ujuziNa kwa upande wa elimu, ni lazima kuwa na ujuzi wa kutosha.Msingi wa ujuziNafasi ya KaziVyanzo vyaTovuti ya kutambaaMsaada wa makalaMaswali yaBidhaa za DocsMaarifa ya ujuziNeno la siri + keywordIMajibu ya msingiChanzo cha habari kilichotajwa.“Fedha zinatolewa kwa 3–5Siku za biashara »1INGESTCrawl, maswali ya mara kwa mara, kuagiza2RETRIEVENeno la siri + keyword3GROUNDEDMajibu ya Maudhui Yako
Weka tovuti yako na kuagiza docs katika msingi wa ujuzi; AI inarejesha vipande vya kulia na majibu, msingi na uliotajwa.

Jinsi ya kufanya kazi

1
Wateja wakiuliza swali

“Kwani sera yako ya kurudi ni nini?”

2
Kutafuta msingi wa ujuzi

OpsIQ hupata makala ya "Sera ya Kurudi" kwa kulinganisha maneno na maana ya semantic.

3
A. Inaleta majibu

AI inasoma makala na kuandika jibu la lugha ya asili kulingana na maudhui ya makala.

4
Wateja wana jibu sahihi

Majibu ni msingi katika sera yako halisi, sio data ya jumla ya mafunzo ya AI.

Kujenga makala nzuri

Moja ya mada kwa makala

Andika makala tofauti kwa kila mada: sera ya kurudi, viwango vya usafirishaji, usanidi wa akaunti, upya nenosiri.

Andika kama FAQ

Anza na swali wateja kuuliza, kisha kutoa jibu. Hii husaidia AI mechi maswali kwa makala.

Kuwa specific

“Mageuzi lazima yaanze ndani ya 30 Siku za utoaji ni bora kuliko "Tuna sera ya kurudi."

Kuhusisha kesi za makali

Nini kuhusu bidhaa za digital? nini kuhusu vitu kununuliwa kwenye mauzo?

Endelea kuwa sasa

Futa habari za zamani. sasisha bei, sera, na taratibu wakati zinabadilika.

Makala ya awaliUchaguzi unapaswa kuandika

Usafiri na utoaji

Gharama za usafirishaji, nyakati za utoaji, kufuatilia, usafirishaji wa kimataifa, na ucheleweshaji wa utunzaji.

Kurejea na Kurudi

Kurudi dirisha, hali, mchakato, tarehe ya kurejeshwa, na isipokuwa.

Usimamizi wa Akaunti

Hifadhi ya nenosiri, mabadiliko ya barua pepe, ufutaji wa akaunti, na usafirishaji wa data.

Malipo na bili

Maelezo ya mpango, mzunguko wa bili, njia za malipo, ankara, na sarafu.

Mwongozo wa Bidhaa

Jinsi ya kutumia kila bidhaa au kipengele. maelekezo hatua kwa hatua na viwambo vya skrini.

Matatizo ya Kutatua

Matatizo ya kawaida na ufumbuzi. ujumbe wa makosa na fixes yao.

Mawasiliano ya mawasiliano

Masaa ya biashara, njia za usaidizi, nyakati za majibu, na njia za kuongeza.

Sheria na utekelezaji wa

Muhtasari wa sera ya faragha, masharti ya muhtasari wa huduma, GDPR maombi ya data.

Mawasiliano ya Maarifa

Kila kontakt inaweza kuchangia maarifa kwa AI. Wakati kiunganishi kinawezeshwa, makala zake za ujuzi zilizojengwa (bidhaa ya bidhaa, maswali ya kawaida, jukwaa maalum la kutatua tatizo) zinapatikana moja kwa moja kwa AI, unaweza kuingiza ujuzi wa kontrakta kwenye au mbali kwa kila konferensi katika mipangilio ya Connector.

Bajeti ya Token

Msingi wa ujuzi una dari ya ishara inayoweza kusanidiwa (default: 32,000 | ishara) ambayo inadhibiti muktadha wa maarifa kiasi gani unaotumwa kwa AI kwa mazungumzo. Ikiwa msingi wako wa ufahamu ni mkubwa sana, AI huchagua makala husika zaidi ndani ya bajeti hii. Kuongeza dari ikiwa AI haipatikani makala zinazofaa; kupungua ikiwa unataka kupunguza gharama za ishara.

Ni makala ngapi ninapaswa kuwa nayo?+

Kuanza na5-10 Makala zinazofunika maswali yako ya kawaida. Ongeza zaidi unapotambua mapungufu kupitia Historia ya AI na Maarifa ya AI. biashara nyingi zinahitaji 20-50 Makala kwa ajili ya taarifa kamili.

Je, ninaweza kupata makala kutoka kwa mfumo mwingine?+

Kwa sasa, makala zinaundwa kwa manually katika OpsIQ. Unaweza kunakili maudhui kutoka FAQs zilizopo, vituo vya msaada, au nyaraka.

Ni aina gani ya makala inapaswa kuwa katika?+

Nakala ya wazi inafanya kazi vizuri zaidi. AI inaelewa lugha ya asili bora kuliko muundo HTML Andika kama ungependa kuelezea kwa mteja.

I

Tathmini ya kina na Mnara wa Mlinzi

Tathmini inaweka maswali muhimu kwa wateja katika vipimo vinavyorudiwa kwa ubora wa majibu, citations, kuongezeka na usalama wa hatua.

Bidhaa ya Screen
Uchunguzi waTathmini ya AI inaorodhesha kesi za mtihani wa dhahabu, tabia zinazohitajika, matokeo ya hivi karibuni na inaendesha iliyopangwa Watchtower.Uchunguzi waNafasi ya KaziSETS6CASES84PASS RATE96%Maisha ya kazi ya VIEWSera ya Usafiri wa UsafirishajiVigezo vinavyohitajikaNjia ya kupitaMaombi ya kurejeshaUthibitisho wa kibinadamu unahitajikaNjia ya kupitaMadai yasiyo ya lazimaHatua zilizochukuliwaNjia ya kupitaUhamiaji swaliChanzo cha ajali kimeonekanaFaili1CREATE CASESMapato ya dhahabu na sheria2RUN SAFELYKuogelea au kuishi eval3WATCHRatiba ya kila siku au kila wiki
Tathmini ya AI inaorodhesha kesi za mtihani wa dhahabu, tabia zinazohitajika, matokeo ya hivi karibuni na inaendesha iliyopangwa Watchtower.

Watendaji kamili wanaweza kuunda seti za tathmini na lebo za chanzo cha haraka, zinazotarajiwa, citations zinazohitajika, sheria za kuthibitisha binadamu, matarajio ya kuongezeka na vitendo vilivyokatazwa. kuendesha seti moja kwa moja, kuiendesha kavu, au kucheza historia iliyochaguliwa tena.

Mnara wa Mlinzi ratiba ya kila siku au kila wiki hundi kupitia cron na anaendesha idadi iliyofungwa ya kesi (hadi nane kwa kila kupita iliyopangwa). Mapitio kushindwa pamoja mtoa / mfano, toleo la haraka, toleo maarifa, vitendo vinavyopendekezwa na gharama kabla ya kubadilisha tabia ya uzalishaji.

I

Lugha na tafsiri

Lugha zinasimamia maandishi yanayotafsiriwa kwa wateja na tabia inayotumiwa wakati OpsIQ inafuata lugha ya mteja.

Bidhaa ya Screen
Lugha za lughaUkurasa wa lugha unaonyesha lugha ya chanzo, lugha zilizotafsiriwa, rasimu / hali ya maisha na tabia ya lugha ya wateja.Lugha za lughaNafasi ya KaziVyanzo vya chanzoKiingerezaLANGUAGES4Maisha ya kuishi3Maisha ya kazi ya VIEWKifaransaInterface na maudhuiMaisha ya kuishiKijerumaniInterface na maudhuiMaisha ya kuishiKihispaniaTafsiri ya maandishiRasimu yaKufuatilia WatejaMajibu ya lugha iliyogunduliwaJuu ya1SET SOURCELugha ya operator2ADD LANGUAGETafsiri katika background3PUBLISHKuumba au Kuishi
Ukurasa wa lugha unaonyesha lugha ya chanzo, lugha zilizotafsiriwa, rasimu / hali ya maisha na tabia ya lugha ya wateja.

OpsIQ Weka lugha ya chanzo kwa usahihi kabla ya kuunda tafsiri, kuongeza lugha za lengo, kisha kukagua rasimu kabla ya kuchapisha. "Fuata lugha ya wateja" inadhibiti lugha ya majibu; kutafsiri interface widget udhibiti vifungo vyake, lebo na maandishi ya mfumo.

Tafsiri ya eneo inaweza kuwa rasimu tu au kuishi. Usitegemee tafsiri ya mashine kwa maandishi ya kisheria, marejesho, usalama au usalama bila ukaguzi wa binadamu.

Kila mahali ambayo ina neno lako mwenyewe ni waliotajwa na ujumbe wake kuhesabu: mteja chat ujumbe, matangazo, ujumbe proactive, mazungumzo mtiririko, tours kuongozwa, matangazo ya, Bubbles teaser na Utafiti na fomuUso wa utafiti inashughulikia kila uchunguzi uliochapishwa kabisa: kichwa, kila swali, kila chaguo la jibu, vifungo, kuwakaribisha na kushukuru nakala, ukurasa chrome na kurasa za matokeo. Keys zimefungwa kwa kitambulisho cha swali na thamani ya chaguo, hivyo kurekebisha maswali au chaguzi kamwe kupoteza tafsiri, na kutafsiri ujumbe mmoja tu. kuchapishwa tafiti za kuishi hutolewa kwa default; rasimu zinajiunga wakati unapopanua wigo.

Uchunguzi wa barua pepe baada ya mazungumzo unafuatia lugha ambayo mgeni huyo aliwasiliana, ikiwa ni lugha hiyo unayotoa hapa; vinginevyo inatumia lugha yako ya mfumo. Mashamba yake sita yenye uhariri yanatafsiriwa kwenye ukurasa huu pia, na tabia ina kubadili kwake katika mipangilio ya Mazungumzo ya Mteja.

Tiketi na ujumbe wa bandari Inashughulikia waendeshaji wa maandishi ya kudumu mara moja na kila mteja kisha hupokea katika lugha hiyo moja: kukubali tiketi, uthibitisho uliofunguliwa, kufungwa na maoni, kwa sehemu za ishara na mstari wa kuwakaribisha. (Initia inahitaji bila shaka yoyote hii, tayari hujibu kwa lugha ya mteja.) Watumiaji wa barua pepe katika lugha yao wenyewe Imewezeshwa kwa OpsIQ Kuandika, barua pepe ya tiketi inatatua lugha ya mpokeaji kwa utaratibu huu: lugha waliyochagua kwenye bandari au Kituo cha Msaada (iliyowekwa kwenye tikiti), eneo la ndani kwenye rekodi yao ya kuwasiliana, kisha lugha waliyoandika, imegunduliwa ndani na maandishi na maneno ya alama, bila simu ya nje. Lugha tu zilizochaguliwa kwenye ukurasa wa Lugha hutumiwa, hivyo kipengele hicho kinaingia hadi lugha zinaongezwa. HTML wrapper barua pepe ni kwa makusudi si kutafsiriwa: ni markup, si prose. Staff-inatumia barua pepe (taarifa, idara ya tahadhari, muhtasari wa mchambuzi, ripoti iliyopangwa, digest kila wiki) daima hutumia lugha ya mfumo.

PeopleOS HR

PeopleOS: Mfumo wa uendeshaji wa kazi unaosimamiwa

Tumia maisha ya mfanyakazi kutoka kwa mahitaji hadi kuondokana na huduma ya kibinafsi ya simu, kazi za mkono wa ushahidi, ushirikiano wa aina na udhibiti wa binadamu juu ya maamuzi nyeti.

Ramani ya mfumo wa
PeopleOS maisha mzunguko amri kituoA tatu-dimensional PeopleOS dashboard kuunganishwa recruiting, wafanyakazi, mishahara, kujifunza na serikali AI.PeopleOS kituo cha amriUshahidi wa kuishiWatu wa watu248Juu ya miguu12Udhibiti wa GATES15 / 15Maisha ya uwaziKurudishwa kwaHi yaKukua kwa kukuaMalipo ya zawadiMabadiliko ya mpitoMmoja wa wanufaikaUshahidi wa ajira +Usimamizi waKubadilika, kurekebisha, kuchukuaKuthibitisha hiloMatokeo na kutoa ushahidi wa
PeopleOS inaendelea mzunguko wa maisha, udhibiti na uthibitisho kwenye rekodi moja ya utawala.

Wasimamizi wa

Kazi ya Opera

Kusimamia watu, shirika, kuajiri, kuingia ndani, nyaraka, kuondoka, upatanisho wa malipo, faida, utendaji, kujifunza, mahusiano ya wafanyakazi, uchambuzi na utawala.

Wafanyakazi na mameneja

Huduma ya kujitegemea

Tumia bandari ya kwanza ya simu kwa kumbukumbu za kibinafsi, maombi, nyaraka, ubao, wakati, maelezo ya kulipa, kujifunza, habari za kampuni na haki.

Waendelezaji

Kupanua

Tumia kwa ajili ya kulisha hr.* Hatua na ukaguzi platform.hr.* Shughuli kupitia mkataba mmoja, pamoja na madarasa ya kontakt. index yanayotokana katika PeopleOS API sehemu orodha kila moja na upeo wake.

⚠️
PeopleOS sio mwongozaji wa malipo, mshauri wa kisheria, ofisi ya ukaguzi wa nyuma au mtoa huduma wa utambulisho. mifumo ya nje ya kuthibitishwa inashikilia majukumu hayo. hundi ya kiufundi ya kijani kamwe haitoi idhini ya kisheria au ushahidi wa mtoa huduma.

Kupata PeopleOS HR

PeopleOS HR ni pamoja na katika mpango Enterprise. On kila mpango mwingine kulipwa ni kuongeza-on: mwenye akaunti inafungua Akaunti → Addons & Links, inachukua kitengo cha PeopleOS HR na ama huanza jaribio la bure au linaongeza kwa moja kwa moja. tiers hutofautiana katika watu wangapi na ni kiasi gani kuajiri, mahojiano na shughuli za AI wanazochukua. Bei na mipaka imewekwa kwenye akaunti, sio imeandikwa ndani ya bidhaa, hivyo angalia viwango vya sasa kwenye akaunti. Ukurasa wa Bei. Ni nini moduli inafanya, uso kwa uso, ni juu ya PeopleOS ukurasa wa bidhaa ya HR.

Nani anaweza kuongeza

Mpango wa kulipwa ambao unafanya kazi. mpango wa bure hauwezi kuongeza, na mpango uliolipwa ambao bado uko ndani ya jaribio la mpango wake mwenyewe unapaswa kusubiri hadi kesi hiyo itakapomalizika.

Jaribio la bure

Jaribio linaendesha kwenye kiwango unachochagua. Wakati unaishia bila kununua haki hiyo inaondolewa na hakuna kitu kilichofunguliwa. Hakuna chochote kinachofutwa: kumbukumbu zipo tena wakati nyongeza inapoongezwa.

Wakati ambapo hakuna mtu

HR ya PeopleOS haionekani kwenye ubao wa upande, palette ya amri, Mipangilio au msaada wa programu. Kiungo cha moja kwa moja kwenye ukurasa wa HR hutoa kuongeza-juu badala ya ukurasa.

Kupata Cap ya Pet

Wakati kikomo cha tier kinafikia ukurasa hutoa kiwango kinachofuata. Kuhariri au kuondoa kile ambacho tayari kipo hakijazuiwa kamwe.

Vifaa vya Kujitegemea

Haki ya kusafiri katika leseni. Ongeza kwenye akaunti yako ya OpsIQ na kufunga huchukua kwa hundi yake ijayo ya leseni.

Wiki ya kwanza ya maandalizi

Kila kitu hapa chini ni skrini halisi; hakuna chochote hapa kinahitaji msanidi programu.

1
Badilisha moduli kwenye

Kufungua PeopleOS → Usimamizi wa rasilimali watu· Kamati ya Bunge yaanza kwa kutoa mapendekezo, PeopleOS HR: na ni mbali hakuna HR ukurasa au mfanyakazi uso ni reachable. Kugeuza kubadili juu ni mbili-click uthibitisho; kugeuka moja off ni click moja. AI swichi chini yake (drafting msaada, uchunguzi wa maombi, wasaidizi uhuru, mahojiano ya AI, kutoa moja kwa moja kutuma, kuthibitisha utambulisho) kukaa mbali mpaka kuamua.

2
Weka Copilot ya Setup kufanya Configuration

Kufungua PeopleOS → Kuanzisha Copilot na kusema nini unataka katika lugha wazi: sera ya kuondoka na siku zake na taarifa, likizo ya umma kwa nchi, jamii kesi na yake SLA, cap gharama, template onboarding, pulse kila mwezi. Unapata mpango nyuma na kile ilichoelewa na kudhani. Hakuna chochote anaendesha mpaka kuthibitisha; hatua ya hatari ya kati inahitaji mtu wa pili; kila kukimbia majani risiti.

3
Jina la portal ya kazi

Kufungua PeopleOS → Mstari wa mbele → Kujiandikisha katika kubuniKwa kutumia mfumo wa kujitegemea, portal ya kuishi /hr/<address>; Anwani ya Portal Inataja tena mara moja na viungo vya zamani vya kuingia vinaendelea kufanya kazi kwa sababu anwani ya zamani inasonga mbele. kwenye wingu bandari ni /hr kwenye tovuti yako na hauhitaji anwani.

4
Chapisha tovuti yako ya kazi

Kufungua PeopleOS → KuajiriKila chapisho unalochapisha kutoka kwa marekebisho yaliyoidhinishwa linaonekana kwenye ukurasa wa kazi za umma; kiungo Fungua ukurasa wa kazi za umma Katika hatua ya juu, inaonyesha kile ambacho mgombea anaona.

5
Kujiandikisha kiosk kwa ajili ya vifaa vya pamoja

Kufungua PeopleOS → Mstari wa mbele → Vibanda Chagua Kujiandikisha kwa KioskIshara ya kifaa imeonyeshwa mara moja; kufungua ukurasa wa kiosk kwenye kibao au PC (ni /kiosk kwenye mwenyeji wa bandari) na kuiweka. Watu hufunga saa na barua pepe yao ya kazi na PIN, au kwa msimbo wa muda mfupi wa beji kutoka kwenye bandari yao.

6
kuamua nini wafanyakazi wanaweza kufanya kwa wenyewe

Kufungua Mipangilio ya Mipangilio→HR wa HRKila nguvu ya huduma binafsi (rekodi, maombi, nyaraka, kuondoka, kutoa maelezo na kadhalika) imewekwa kwa kila mfanyakazi, mameneja tu, au timu moja na timu chini yake.

7
Kuwapa watu na kuwapa fursa ya

Juu ya PeopleOS → Watu Unda mtu, ajira yao na meneja wao. Utoaji wa bandari upatikanaji mara tu mtu ana barua pepe halali na uhusiano wa ajira uliokusudiwa; mwaliko unatoka kwenye skrini hiyo na kuingia huanza kutoka safari uliyoanzisha.

Maisha yacycle

Mpango na Kuajiri

Unda mahitaji yaliyoidhinishwa, kuchapisha kazi, kupokea maombi kupitia webhooks salama za kufuatilia, ukaguzi wa muundo, mahojiano ya ratiba, maamuzi ya rekodi, utoaji wa suala na kuajiri.

Kujiunga na kutoa

Kujenga safari za kuingia ushahidi, kukusanya toleo sahihi la hati, vifaa vya ombi, templeti zilizoidhinishwa za upatikanaji na ufikiaji wa bandari usio na ukomo.

Kazi na kukua

Kuondoka kwa kazi, ratiba, maelezo ya kulipa, faida, gharama, malengo, maoni, mapitio, kujifunza, ujuzi, fursa za ndani, mfululizo na uchambuzi wa wafanyakazi.

Msaada na Ulinzi

Kutoa msaada wa kibinafsi wa HR, kesi za uhusiano wa wafanyakazi unaosimamiwa, maombi ya kisheria, marekebisho, maelezo, rufaa na ukaguzi wa kibinadamu wa kujitegemea.

Mabadiliko na kuondoka

Tumia mabadiliko ya ajira yenye ufanisi, upatikanaji wa kurudi, vifaa vya kupona, kupatanisha watoa nje, kutumia uhifadhi na kuhifadhi ushahidi unaohitajika.

Upatikanaji na utambulisho

Mtu wa kawaida anamiliki rekodi za ajira na kuthibitishwa nje ya utambulisho. Barua pepe ni data ya mawasiliano yenye nguvu, kamwe ufunguo wa kitambulisho cha kudumu. Portal inasoma ni binafsi-scoped; maoni ya meneja na msimamizi zinahitaji ruhusa wazi. API mawanda safu juu ya vibali vya njia na kamwe kuyapita.

Kuongeza mfanyakazi mpya

Kwa mfano:
Unda mtu, pangia ajira na meneja, upatikanaji wa bandari ya utoaji, kisha ufungue safari ya kuingia.
Nini cha kufanya:

Tumia mzunguko wa kavu na upungufu kwa API anaandika. kuthibitisha mtu ana barua pepe halali na uhusiano wa ajira uliokusudiwa kabla ya kutuma upatikanaji.

Kutatua utambulisho wa duplicate

Kwa mfano:
Mfumo wa nje unatambulisha wafanyakazi wawili tofauti.
Nini cha kufanya:

Unganisha pande zote mbili zilizothibitishwa kwa mtu wa kisheria na kutatua mgogoro waziwazi. Usiunganishe kumbukumbu tu kwa sababu thamani mbili za barua pepe zinalingana.

PeopleOS HR

Kazi ya HR na Portal ya Wafanyakazi

Jinsi kila eneo la PeopleOS linaendeshwa na kile wafanyakazi wanaona baada ya kuingia.

Watu na Shirika

Kudumisha mtu wa kisheria, ajira, aina ya mfanyakazi, meneja, timu, eneo, ujuzi, nyaraka na muundo wa shirika la ufanisi.

Kukubaliana na kutoa

Nenda kutoka kwa mahitaji yaliyoidhinishwa ya kutuma, maombi, ushahidi wa muundo, mahojiano, uamuzi, kutoa na kuajiri na malazi na njia za rufaa.

Kuingia na nyaraka

Assign aliamuru hatua maalum za mmiliki; kukusanya, kukagua, ishara, muda wake, kushikilia na kufuta nyaraka kwa toleo na ushahidi wa upatikanaji.

Muda, kuondoka na ratiba

Kufafanua aina za kuondoka zinazoungwa mkono na sera, mizani, maombi, idhini, likizo, upatikanaji, matukio ya kalenda na upatanisho.

Malipo, faida na gharama

Eleza malipo, matukio ya wafanyakazi yaliyoidhinishwa mkono kulipa, kupatanisha isipokuwa, kusimamia ustahiki wa faida na udhibiti wa ulipaji.

Utendaji na Ukuaji

Malengo ya kazi, hundi-ins, maoni, ukaguzi, calibration, kujifunza, ujuzi, ushauri, fursa za ndani na mfululizo.

Huduma ya HR na Uhusiano

Kutoa wafanyakazi binafsi msaada wakati kuweka malalamiko, nidhamu, whistleblower na muhuri kesi ushahidi katika mipaka ya kujitolea ruhusa.

Analytics na mipango ya

Tumia hatua za wafanyakazi, mipango ya hesabu ya kichwa, vigezo na metriki za uzoefu zilizopatikana kutoka kwa kumbukumbu; kamwe matokeo yasiyopotea kama mafanikio.

Ramani ya portaler

Muhtasari wa jumla

Wanahitaji tahadhari yako, mabadiliko tangu ziara ya mwisho, maombi ya wazi, matukio yajayo, kuingia maendeleo na matangazo.

Wasifu na kumbukumbu

Ajira, rekodi iliyothibitishwa, nyaraka, ruhusa, maombi ya faragha na maombi ya marekebisho.

Msaada wa HR na majukumu

Mazungumzo ya kibinafsi, maombi, vitendo ambavyo vinahitaji kazi za mfanyakazi na inayomilikiwa na kampuni kuonyeshwa tofauti.

Siku zako za kwanza

Ushahidi-backed onboarding ratiba na mmiliki, hali ya kutosha, kukamilika na kazi imefungwa.

Muda na kuondoka

Mizani, maombi ya kuondoka, upatikanaji, ratiba na matokeo ya kalenda.

Ujuzi na ukuaji

Kujifunza, ushahidi wa ujuzi, malengo, maoni, ushauri na fursa za ndani.

Kwa upande wangu, kwa ufafanuzi

Malipo ya lugha ya wazi na maelezo ya upatanisho wa malipo ambayo mfanyakazi anaruhusiwa kuona.

Kampuni ya Kampuni

Orodha ya orodha na chati ya shirika iliyo mdogo kwa wenzake wa habari wamechagua au sera inawaruhusu kushiriki.

Haki na maamuzi

Maelezo, rufaa, idhini, marekebisho, upatikanaji na maombi ya kufuta.

💡
Portal ni simu ya kwanza. kadi ya akaunti bado kupatikana, urambazaji na maudhui kitabu kwa kujitegemea kwenye skrini pana, na urambazaji wa simu badala ya kusukuma au kufunika ukurasa. nakala ndefu ya maelezo ni katika vipengele vya upatikanaji wa tooltip au ufunuo.

Salama ya uendeshaji

1
Kuchambua sera na ruhusa

Weka mamlaka, majukumu, njia za idhini, uhifadhi, kibali na udhibiti wa kipengele kabla ya kupakia kumbukumbu za kuishi.

2
Kuunganisha watoa huduma wa nje

Weka mfuko sahihi uliosainiwa, ingiza sifa za msingi za kibali na uunganishe uhusiano na vipimo vya kufanana.

3
Kukimbia kwenye sandbox au kivuli

Zoezi kamili la kazi na data ya kuamua na kulinganisha ushahidi uliotarajiwa kabla ya kuwezesha utekelezaji wa huduma halisi.

4
Kuwekwa chini ya udhibiti wa mbili

Mhakiki tofauti aliyeidhinishwa anachunguza mtoa huduma, usalama, faragha, kisheria, haki na upatikanaji wa ushahidi.

PeopleOS HR

AI, usawa, video na udhibiti wa kisheria

PeopleOS matibabu automatisering kama njia ya chombo kutawala: ruhusa sera, jaribio la utendaji, mtoa matokeo na ushahidi ni ukweli tofauti.

Udhibiti wa AI na Wakala

Kila wakala hutumia zana zilizosajiliwa kwa kusudi, mamlaka, darasa la hatari na uhuru wa kiwango cha juu. Uchukuaji wa binadamu, mzunguko wa mzunguko, matukio na mabadiliko ya mamlaka yanaweza kuacha utekelezaji. Marekebisho yanaweza kuunda seti iliyopendekezwa lakini kutoa mafunzo hadi mtu mwingine aliyeidhinishwa atakapokamilisha ukaguzi wa faragha.

Uadilifu wa

Kufafanua vikundi, sheria za chini za sampuli, metriki, utambulisho wa evaluator na tathmini iliyotolewa kisheria. Data iliyopotea haiishi; haijawahi kubadilishwa kuwa kupita.

Maelezo na Maombi

Kujenga maelezo kutoka kwa uamuzi uliofungwa na ushahidi wa sera. Tuma rufaa kwa binadamu huru na kuhifadhi ushahidi wa matokeo.

Mahakama za

Kuachilia pakiti za sera ya nchi tu na mmiliki wa kisheria anayewajibika, alitoa vyanzo vya kisheria na vipimo vya kupitisha. Mabadiliko makubwa ya sheria kusimamisha viathirio vilivyoathirika.

Sheria ya EU

Weka hesabu ya mfumo, darasa la hatari, tathmini ya athari za haki za msingi, matangazo, waangalizi, mita na ushahidi.

Video ya Ufuatiliaji wa Mipaka

Ushiriki sio wajibu

hr.interview.room.provision Kuumba eneo la mkutano. tu hr.interview.room.connect Inaweza kuthibitisha kuwa vyombo vya habari vinawafikia wafanyakazi.

Makubaliano ya makusudi

Kurekodi, nakala na uhai wa biometri ni uchaguzi tofauti. Kuondoa inatumika kwa madhumuni yaliyochaguliwa.

Hakuna uchambuzi wa

Mkataba wa video hauna uwanja au njia ya hisia, tahadhari, mvuto, rangi, ulemavu au inference kuonekana.

Njia za Binadamu na Maandishi

Mkaguaji anaweza kuchukua kwa muda mrefu kwa kikao, na njia ya malazi ya maandishi bado inapatikana.

Kuondolewa na kufutwa

Ujumbe wa kontakt unaripoti usafiri uliofichwa, sera ya uhifadhi na kumbukumbu za vyombo vya habari vya mtoa huduma, na lazima ziunga mkono ufutaji unaothibitishwa.

Nyumba ya sanaa, ambayo haikujengwa

Kwa mfano:
Chumba cha ZoomURLKuna, lakini daraja la vyombo vya habari halijatoa sauti / video kwa mfanyakazi wa mahojiano.
Nini cha kufanya:

Onyesha mkutano kama ilivyotolewa na ushiriki wa AI kama uongo. Weka mahojiano ya kibinadamu na njia za malazi ya maandishi zinapatikana.

Callback anasema kuwa uchunguzi wa

Kwa mfano:
Taarifa ya mwisho ya uchunguzi wa nyuma ya mtandao wa Yahook imekamilisha.
Nini cha kufanya:

Rekodi callback kama ladha, kisha swala mtoa huduma. Tu hali ya kuthibitisha majibu inaweza update hundi.

🚫
Tathmini ya upatikanaji wa kiufundi inaweza kurekodiwa na mvuvi wake, lakini uthibitisho wa WCAG unahitaji mtu tofauti. Uthibitisho wa Mtoa, kutolewa kwa kisheria na ushahidi wa haki pia inahitaji wamiliki wao wa kweli.
PeopleOS HR

PeopleOS API na connector maendeleo

Tumia General API kwa shughuli za HR zinazosimamiwa na mikataba ya kontakt ya mamlaka ya nje.

Jenerali MkuuAPIVyanzo vya ukweli

Ujumbe waJSONKwa ajili ya POST /api/v1.php- Kufahamu jinsi ya kutumia mbegu za kiume kupitia meta.actionsOpenAPI katika /api/v1/openapi.php, na Postman katika /api/v1/postman.phpindex ya chini inahesabu kuhesabu kamili ya curated hr.* Hatua na ukaguzi platform.hr.* Shughuli katika kujenga hii, hivyo hakuna kitu kwenye ukurasa huu ni aina kwa mkono.

Orodha ya watu
curl -sS https://your-opsiq.example/api/v1.php \
  -H 'Authorization: Bearer YOUR_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{"action":"hr.people.list","page":1,"per_page":50}'
Kujiandikisha kwa Kuandika
curl -sS https://your-opsiq.example/api/v1.php \
  -H 'Authorization: Bearer YOUR_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{"action":"hr.people.create","display_name":"Ada Reaudit","primary_email":"[email protected]","worker_type":"employee","idempotency_key":"hire-2026-0042","dry_run":true}'

Matumizi ya matumizi hr.read au hr.write Njia ya msimamizi wa lengo bado inakagua idhini yake mwenyewe. Inahitaji ufunguo thabiti wa idempotency; hatari kubwa anaandika inahitaji uthibitisho. Kujaribu kushindwa kwa muda mfupi na hali hiyo muhimu na swala la kupona baada ya muda usio uhakika.

Kila hatua ya kazi*

48 curated hr.* actions (22 reads, 26 writes) and 484 reviewed platform.hr.* operations, out of 2420 named actions in this build. Generated from the action registry, the same source as meta.actions, OpenAPI and Postman.

Watu, shirika na utambulisho (9)

hr.employee.provision

Write. Scope: hr.write. Provision seatless employee access and send the invitation. Required: person_uuid.

hr.employee.restore

Write. Scope: hr.write. Lift an employee access suspension (written reason required) and provision again. Required: person_uuid, reason.

hr.identity.facets

Read. Scope: hr.read. List a person's identity facets and open conflicts. Required: person_uuid.

hr.identity.link

Write. Scope: hr.write. Link an identity facet to a person. Required: person_uuid, facet_type, facet_key.

hr.org.tree

Read. Scope: hr.read. Read the organisation tree.

hr.people.create

Write. Scope: hr.write. Create an HR person. Required: display_name.

hr.people.get

Read. Scope: hr.read. Get one HR person. Required: person_uuid.

hr.people.list

Read. Scope: hr.read. List HR people.

hr.people.update

Write. Scope: hr.write. Update an HR person. Required: person_uuid, display_name, primary_email.

Mahitaji na Matangazo (3)

hr.postings.list

Read. Scope: hr.read. List job postings.

hr.requisitions.create

Write. Scope: hr.write. Create a requisition. Required: title, openings, justification.

hr.requisitions.list

Read. Scope: hr.read. List requisitions.

Kuacha, kujifunza na soko la kontakt (3)

hr.learning.overview

Read. Scope: hr.read. Read courses, paths and enrolments.

hr.leave.overview

Read. Scope: hr.read. Read leave types and requests.

hr.marketplace.overview

Read. Scope: hr.read. Read HR connector accounts, conflicts and deliveries.

Kuunganisha vyeti na afya (2)

hr.connectors.certify

Write. Scope: hr.write. Certify an HR connector (scope sandbox|production; production demands provider-side proof under dual control). Required: connector_class, connector_key, scope, evidence, submitted_by.

hr.connectors.health

Read. Scope: hr.read. One connector account's health: certification level and scope, last reconciliation verdict, failures and webhook backlog. Required: account_uuid.

Mahojiano ya mahojiano (7)

hr.booking.slots_reconcile

Write. Scope: hr.write. Release booking slots whose claim never became a booked meeting.

hr.interview.room.connect

Write. Scope: hr.write. Connect the AI to interview media; refuses unless media really reaches the worker. Required: media_uuid.

hr.interview.room.consent

Write. Scope: hr.write. Record or withdraw consent for ONE interview purpose (recording, biometric_liveness, transcription). Required: media_uuid, purpose, state.

hr.interview.room.pause

Write. Scope: hr.write. Pause a live interview. Required: media_uuid.

hr.interview.room.provision

Write. Scope: hr.write. Provision an interview room (a place to meet — NOT AI participation). Required: session_uuid, transport, accommodation_route.

hr.interview.room.state

Read. Scope: hr.read. Read an interview room, including whether the AI is actually participating. Required: media_uuid.

hr.interview.room.takeover

Write. Scope: hr.write. A human takes the interview; the AI cannot speak in it again. Required: media_uuid, reason.

Wafanyakazi na maabara ya lifecycle (7)

hr.agent.incident.close

Write. Scope: hr.write. Close an agent incident — the same act that lifts the suspension it caused. Required: incident_uuid, resolution.

hr.agent.step

Write. Scope: hr.write. Run one agent step: gate verdict, execution and outcome reported separately. Required: run_uuid, agent_key, tool_key, jurisdiction, purpose.

hr.agent.step.status

Read. Scope: hr.read. What actually happened at a step (permitted, executed, proven, failed, compensated). Required: run_uuid, seq.

hr.agent.takeover

Write. Scope: hr.write. A human takes an agent run; no further agent steps are accepted. Required: run_uuid.

hr.agent.tool.grant

Write. Scope: hr.write. Grant an agent a tool for one jurisdiction and purpose, up to a risk ceiling. Required: agent_key, tool_key, jurisdiction, max_risk, purpose.

hr.agent.tools

Read. Scope: hr.read. List the registered typed tools an agent may use, and open agent incidents.

hr.lifecycle.lanes

Read. Scope: hr.read. Every lifecycle lane with its mode, KPIs and whether a live tool path really exists behind it.

Uhalali wa kisheria (5)

hr.jurisdiction.capabilities

Read. Scope: hr.read. What this product may do in one country, per feature, with the law behind each answer. Required: code.

hr.jurisdiction.change.raise

Write. Scope: hr.write. Report a change in the law; a high or critical one suspends every lane in that jurisdiction at once. Required: pack_key, summary, severity.

hr.jurisdiction.coverage

Read. Scope: hr.read. Computed coverage for every market: released pack, named counsel owner, cited sources, passing tests.

hr.jurisdiction.explain

Read. Scope: hr.read. Why an action about one person is allowed, reduced or blocked, with the rule and citation. Required: person_uuid, feature.

hr.jurisdiction.pack.release

Write. Scope: hr.write. Put a drafted policy pack into effect; refused without a named counsel owner and a cited law. Required: release_uuid.

Uamuzi na maombi (2)

hr.decisions.appeals

Write. Scope: hr.write. File an appeal against an AI decision on a person's behalf; it must be heard by an independent human. Required: decision_uuid, subject_type, subject_id, grounds.

hr.decisions.explanation

Read. Scope: hr.read. Plain-language explanation of one AI decision: what was looked at, which policy, and how to appeal. Required: decision_uuid, audience.

Ubora wa (2)

hr.ai.corrections

Write. Scope: hr.write. Bundle recent reviewer corrections into a dataset; it is pending privacy review and trains nothing.

hr.ai.quality.overview

Read. Scope: hr.read. The AI quality board: sampled defect rate, override pressure per workflow, coaching reception.

Majadiliano ya kazi na uhifadhi (4)

hr.thread.delete

Write. Scope: hr.write. Delete a workforce conversation; refused while it is under legal hold. Required: thread_uuid, reason.

hr.thread.legal_hold

Write. Scope: hr.write. Place or lift a legal hold on a workforce conversation. Required: thread_uuid, on, reason.

hr.thread.retention

Write. Scope: hr.write. Set a conversation's retention class (standard|extended|permanent). Required: thread_uuid, retention_class.

hr.threads.retention_sweep

Write. Scope: hr.write. Run the conversation retention sweep; legal holds are never swept.

Kusoma na Kuachiliwa (4)

hr.experience.metrics

Read. Scope: hr.read. Measured persona experience metrics (self-service rate, decision cycle, coaching usefulness, quality) from live journeys.

hr.global.readiness

Read. Scope: hr.read. The whole launch picture: 15-gate leadership score, release readiness checks and jurisdiction coverage.

hr.readiness.read

Read. Scope: hr.read. Run the HR release readiness report.

hr.release.verify

Write. Scope: hr.write. Run the four HR release gates (schema, manifest, probe, readiness).

Mafunzo ya Kuunganisha

Kurudishwa

hr_job_board, hr_background_check, hr_identity_verification, hr_assessment Na kwa kuwa hr_tax_right_to_work.

Kuogelea na kuingia

hr_esignature, hr_calendar, hr_video Na kwa kuwa hr_equipment_it.

Operesheni za Kazi

hr_payroll, hr_benefits, hr_learning, hr_expense_payment, hr_directory Na kwa kuwa hr_data_warehouse.

Mawasiliano ya mawasiliano

hr_messaging Ni kutuma tu. mkataba haina mfanyakazi ujumbe kusoma mbinu.

Huduma ya Mwisho wa Gateway

PeopleOS HR Mtoa Gateway 1.0
GET    /v1/hr/health
POST   /v1/hr/job-postings
PATCH  /v1/hr/job-postings/{provider_ref}
POST   /v1/hr/job-postings/{provider_ref}/close
GET    /v1/hr/job-postings/{provider_ref}
POST   /v1/hr/background-checks
GET    /v1/hr/background-checks/{provider_ref}
POST   /v1/hr/identity-verifications
GET    /v1/hr/identity-verifications/{provider_ref}
DELETE /v1/hr/identity-subjects/{subject_ref}
POST   /v1/hr/payroll/worker-events
GET    /v1/hr/payroll/state?cursor=...
GET    /v1/hr/payroll/exceptions
POST   /v1/hr/equipment/requests
POST   /v1/hr/access/requests
GET    /v1/hr/provisioning/requests/{request_ref}
POST   /v1/hr/provisioning/requests/{request_ref}/revoke

Mlango wa lango unahitaji HTTPS, vitalu visivyo salama / malengo ya kibinafsi, pins zilizothibitishwa DNS Matokeo, hufuata hakuna kuelekeza tena, ukubwa wa majibu ya mipaka, inahitaji JSON, inasimamia upungufu wa kuamua, na inasaidia wakati HMAC Katika pande zote mbili, Webhooks ni daima hints ikifuatiwa na mtoa re-query.

Mlango wa ndani wa Webhook

3 milango ya umma kupokea callbacks: POST /opsiq/ajax_api.php?ajax=hr_connector_webhook (Maeneo ya connector_class, connector_key, topic), ?ajax=hr_esign_webhook (connector_key, offer_uuid, provider_ref(a) na ?ajax=hr_check_webhook (check_uuidKila inathibitisha mwili kupitia kontakt kuthibitishwa, huchoma utoaji hivyo replay kufa, na kumbukumbu tu ya kusubiri tena; jibu la mtoa huduma mwenyewe linabadilisha rekodi. kila kukataa ni jibu sawa la generic kwa madhumuni. PeopleOS hutoa hakuna matukio ya mtandao wa nje leo: webhooks.events.list Je, ni majina na si sifa ya mtu? hr familia, hivyo basi uchaguzi hr.* Kusoma au kutumia hr.connectors.health.

Maelezo ya kina

Orodha ya watu wa PeopleOS

Soma doc/contracts/PEOPLEOS_HR.md katika ufungaji wa kujitegemea kwa kila operator, API, kontakt, webhook na utawala wa kutolewa.

Mkataba wa developer

Soko la bidhaa lina README.md, DEVELOPER.md, connector_contract.json, hr_profile.json Ni wazi kuwa utachoka.

PeopleOS HR

Ukaguzi na utayarishaji wa uzalishaji

Madai ya uzinduzi yanahesabiwa kutoka kwa ushahidi. Utayarishaji wa pakiti, uthibitisho wa mtoa huduma, idhini ya kisheria, tathmini ya haki na uthibitisho wa ufikiaji ni tofauti kwa makusudi.

1
Sheria ya Kodi na Mikataba

Tumia syntax ya PHP, HR PHPUnit, njia / API usawa, OpenAPI / Postman hundi, mfuko wazi na JSON Schema uhalali.

2
Kufanya kazi kamili ya workflows

Mtihani kuajiri, AI mapitio, mahojiano / video, onboarding, saini, kuondoka, payroll, portal, taarifa, modals na njia kontakt kushindwa.

3
Mtihani wa UI na UI

Hifadhi desktop, kibao na mipangilio ya simu; keyboard, lengo, lebo, tofauti, reflow, tooltips, mazungumzo, kitabu cha taarifa na urambazaji wa kujitegemea.

4
Kukusanya ushahidi wa nje

Tumia mzunguko wa mtoa huduma halisi na ufutaji, utoaji wa sera za kisheria, data ya haki ya mwakilishi na uthibitisho wa kujitegemea wa WCAG.

5
Kuwekwa chini ya udhibiti wa mbili

Mkaguaji tofauti na mwasilishaji anakubali kontakt na kutoa ushahidi. Revoke au kuua-switch kiunganishi ikiwa uthibitisho wake unaisha.

Matokeo ya kila kitu

Mpango uliosainiwa

Faili hazijabadilika tangu saini ya mfuko wa idhini. Haithibitishi kazi za akaunti ya tatu.

Sandbox ya zamani

Tabia ya kuamua na mabadiliko ya hali yanakubaliana. Haithibitishi mtoa huduma halisi, muda wa makazi au ufutaji.

Uzalishaji wa kontrakta kuthibitishwa

Akaunti maalum ya nafasi ya kazi ilipitisha majukumu ya upande wa mtoa huduma chini ya udhibiti wa mbili.

Ripoti ya WCAG

Ushahidi unaoendeshwa na uvukizi upo kwa nyuso zilizoitwa; Sio ushahidi wa mtu wa pili.

Kujiandaa kwa ajili ya

Milango yote inayohitajika ni ya kijani wakati huo huo na hakuna ushahidi uliokwisha kamilika, kufutwa, kukosa au kukinzana na afya ya kuishi.

⚠️
Kamwe usijenge rekodi ya kupitishwa kisheria, haki, mtoa huduma au rekodi ya kuthibitisha uhuru tu ili kufuta lango. Rekodi blocker na mmiliki badala yake. mtazamo wa utayari ni muhimu hasa kwa sababu unakataa madai yasiyosaidiwa.
Kwa nini kuna simu ya mkononi lakini bado haijapatikana?+

Ufungaji inathibitisha uwepo wa mfuko. Wezesha, kuokoa sifa halisi za upendeleo, kupitisha mtihani wa uunganisho, kisha kutoa wigo wa uzalishaji wa akaunti ya PeopleOS kwa kutumia ushahidi wa mtoa huduma wa kweli na mhakiki tofauti.

Kwa nini tovuti haibadili rekodi?+

Callback inaweza kuwa halali lakini tu ladha. Angalia sanduku la webhook, mtoa huduma hali endpoint na maridhiano matokeo. PeopleOS mabadiliko mamlaka ya serikali tu baada ya re-query.

Ambapo ni kamili ya mashine kusoma HRAPI?+

Piga meta.actions na filter kwa hr na jukwaa.hr; au kutumia/api/v1/openapi.phpAidha, na/api/v1/postman.php.Wao ni zinazozalishwa kutoka rekodi sawa ya muda.

Msaada wa msaada

Msaada wa kituo cha msaada

Kituo chako cha Msaada ni tovuti ya usaidizi wa kibinafsi iliyojengwa kutoka kwa makala unayochapisha. Wateja wanaweza kusoma na kuichunguza kwenye ukurasa wake wa umma, na ndani ya widget ya mazungumzo, ili waweze kupata majibu yao wenyewe kabla ya kufungua mazungumzo. Kila kitu kinatoka kwa msingi wako wa ujuzi, hivyo maudhui sawa ambayo yanaelezea AI yako pia nguvu msaada wako wa umma.

Ambapo wateja wako wanaona

Ukurasa wa umma

Msaada wa haraka na rahisi katika tovuti /help.phpWateja kuvinjari kwa jamii, kutafuta, na kufungua makala yoyote. Unaweza kutoa jina lako mwenyewe na mtindo.

Ndani ya widget ya chat

Msaada kiungo katika widget chat hivyo wateja wanaweza kutafuta makala yako bila kuacha kuzungumza. Kama bado wanahitaji mtu, wao ni bomba moja mbali na kuanza mazungumzo.

Kugeuka juu ya

1
Fungua ukurasa wa Kituo cha Msaada

kwenda kuwa Config, then Help Center katika uongozi wake na kuwaelekeza Kutoa huduma ya kituo cha msaada wa umma.

2
Andika jina na uone

Weka jina la Kituo cha Msaada, ambayo inaonyesha katika kichwa na kichupo cha kivinjari, na uchague mtindo wa kuona. Unaweza kugeuza urambazaji juu mbali kwa ukurasa safi bila orodha.

3
Andika baadhi ya makala

Hakuna chochote kinachoonyesha mpaka kuchapisha makala hiyo. sehemu inayofuata inashughulikia jinsi.

Tuma makala kwenye kituo cha msaada

Makala moja inaonekana katika Kituo cha Msaada mara baada ya kuchapishwa na alama ya umma. Kuna njia chache za kufanya hivyo:

Andika makala moja

Fungua makala, alama iliyochapishwa, na ugeuke kwenye chaguo la kuionyesha katika Kituo cha Msaada.

Andika kila kitu kwa wakati mmoja

Matumizi ya Kuchapisha kila kitu kifungo kushinikiza yako yote kuchapishwa kuweka kwa Kituo cha Msaada katika click moja, badala ya kufanya yao moja wakati.

Badilisha FAQs katika makala

Je, una maswali yoyote? kutumia Andika kila kitu ili kusaidia Ili kuwasaidia katika makala, wao kukaa pamoja na kila kitu kingine.

Kuingiza msingi wa ujuzi uliopo

Kuhamisha kutoka kwenye mfuko mwingine? Uagizaji wa KB kifungo kwenye tabo ya makala huleta msingi wa ujuzi uliopo kwako. Una njia tatu za kuielezea katika maudhui yako:

Kufunga URL

Kutoa anwani ya kituo chako cha sasa cha msaada. Kama inatambua jukwaa (kwa mfano Zendesk) inasoma mti halisi wa jamii kutoka kwenye jukwaa hilo. Vinginevyo, inachukua tovuti na kujenga muundo kutoka kwa kurasa, kuagiza tu makala halisi na kuruka kuingia, bei, na kurasa za mawasiliano.

Chagua App ya Kuunganishwa

Ikiwa jukwaa tayari limeunganishwa na nafasi hii ya kazi na ina msingi wa ujuzi, inaonyesha chini ya kushuka Kuhamisha kutoka kwa App ya KuunganishwaChagua na kuagiza, hakuna URL au nenosiri linalohitajika. programu imeorodheshwa tu mara moja imeunganishwa na kuanzisha.

Ongeza kwenye A CSV

Hakuna tovuti ya kuishi kwa uhakika? upload asheet na title, categoryKwa hivyo, na body Picha zote na Wizara ya Mambo ya Ndani Parent / Child katika sekta ya ujenzi ili kujenga miundombinu isiyo na tija.

Chochote unachochagua, unapata Maoni ya kwanza: makala ni kupatikana, kundi kwa jamii, kila mmoja na hundi sanduku ili unaweza kuacha chochote huna unataka. Hakuna kitu ni kuokolewa mpaka click Import. Baada ya hapo unaweza Utenzi wa wote wa ndani ya chombo kimoja, au Kwa hivyo, a URL au programu iliyounganishwa itaingiza baadaye kwa kuvuta makala mpya na zilizobadilishwa.

💡
Waendelezaji: kontakt yoyote inaweza kutangaza msingi wake wa ujuzi kwa kushuka hii kwa kutangaza kb_capabilities Uunganisho katika seva settings.json (Tabia ya aina kb_sourceKwa kuwa adapter Aidha, a base_templateAngalia sehemu ya Waunganishaji na kumbukumbu ya kuunganisha jukwaa.

Kuungana na AI

Kituo cha msaada wa tidy ni rahisi kuvinjari na rahisi kutafuta. Kuungana na AI kifungo anafanya tidying kwa ajili yenu. Katika click moja kusoma makala yako kuchapishwa, aina yao katika makundi busara, na anaongeza tags. Inaunda jamii wakati inahitaji moja, reuses jamii kwamba tayari inafaa, na kuruka kitu chochote wewe tayari iliyoandaliwa, hivyo unaweza kukimbia tena wakati wowote kuongeza makala mpya. Kuwezesha shirika la kutoa misaada katika vikundi katika mazingira ya Kituo cha Msaada na inaweza pia faili makala chini ya nested Parent / Child Makundi, ambayo ni handy haki baada ya kuagiza msingi wa ujuzi kwamba alikuwa na sehemu ndogo.

💡
Jamii huwapa wateja njia ya kuvinjari, na vitambulisho vinavyoongeza utafutaji kwenye ukurasa wa umma na katika widget. Unaweza kurekebisha au kuhamisha mambo baadaye. AI inakupa hatua kali ya kuanzia, sio usanidi unaokwama nao.

Kituo cha Msaada ndani ya widget yako ya chat

Unaweza kuonyesha Kituo cha Msaada ndani ya widget chat hivyo watu kutafuta majibu kabla ya ujumbe wewe. Katika mazingira yako ya widget, kuchagua ambapo kiungo msaada inaonekana:

Katika kichwa

Icon ndogo ya msaada juu ya widget.

Juu ya Chini

Kiunga cha maandishi chini ya sanduku la ujumbe, kwa mfano "Kupiga kituo cha msaada". unaweza kubadilisha neno.

Maeneo mawili ya

Kuthibitisha hilo katika kichwa na chini kwa kuonekana zaidi.

Msaada kiungo ina yake mwenyewe rangi kudhibiti chini widget Kuonekana mipangilio. kuondoka ni juu ya Hakuna hata mmoja Ili kuchagua rangi ya ngozi yako, au chagua Kuwa imara Rangi ya rangi au a Gradient yaUzoefu wote wa msaada unafuata mandhari yako ya widget, kwa hivyo inaonekana kama sehemu ya brand yako.

Weka kituo chako cha msaada kwenye anwani yako ya mtandao

Kutoka kwenye sanduku kituo chako cha msaada tayari kina anwani safi, inayoweza kugawanywa ya yake mwenyewe (kwa mfano). /help/your-help-centerUnaweza kwenda hatua moja zaidi na kutumikia chini ya yako. Domain mwenyeweKwa hiyo, wateja na injini za utafutaji wanaona kama sehemu ya chapa yako, kwa mfano. yourdomain.com/help au help.yourdomain.comKila kitu kinaendelea kufanya kazi kwenye kikoa chako: viungo, picha, utafutaji na upimaji wa makala.

Chini ya tovuti yako kuu

Ndani ya Kujiamini, kisha Msaada Centerkufungua mlango wa Kujenga tab na kupata "Onyesha kituo chako cha msaada kwenye anwani yako ya wavuti". Chagua usanidi wako (Cloudflare, Nginx au Apache), nakala block iliyoandaliwa tayari, na kuiweka kwenye tovuti yako. Mwongozo wa ufungaji Bonyeza hapa kwa hatua sahihi.

Juu ya subdomain

Preferi ya help.yourdomain.comJopo hilo lina chaguo la subdomain. kwenye Cloudflare subdomain ndio njia ya kuaminika zaidi, na inakupa anwani safi bila chochote baada yake.

💡
Matumizi ya kutumia Cloudflare- Anaendesha tu mfanyakazi wake kwenye anwani ambayo inapendekezwa kupitia Cloudflare(wingu wa machungwa). Domain yako kuu mara nyingi inaonyesha moja kwa moja kwenye tovuti yako, hivyo utawala uliowekwa kwenye kikoa kikuu hauwezi kufanya chochote kimya. Njia ya kutegemea ni subdomain iliyoenea kama help.yourdomain.comMwongozo wa ufungaji unatembea kwako kupitia moja DNS rekodi na njia ya kwenda.
Nzuri kwa SEO. Mara kituo chako cha msaada kiko kwenye kikoa chako mwenyewe, injini za utafutaji zina index makala zako chini ya chapa yako. Kila ukurasa unatangaza anwani yake sahihi na orodha yao, hivyo nakala hiyo haijawahi kuorodheshwa mara mbili.
💡
Kutumia kiungo cha msaada wa in-widget pia? Katika widget ya 'Fungua katika kituo cha usaidizi', kuweka Ambapo kiungo ni kwenda Kwa kuwa Domain yako ya Msaada wa Kituo cha Msaada Kisha viungo hivi vinafunguliwa kwenye kikoa chako pia, sio kwenye anwani ya OpsIQ.

Angalia jinsi kila kitu cha msaada kinavyofanya kazi

Zaidi ya kura za maoni, Kituo cha Msaada kina yake mwenyewe Uchambuzi wa analyticsBadilisha kwenye mipangilio ya Kituo cha Msaada na inarekodi kimya jinsi watu hutumia msaada wako: makala zilizotazamwa zaidi, kile wanachotafuta, na utafutaji ambao ulikuja tupu (orodha iliyotengenezwa tayari kwa kuandika), kufanya kazi nje nchi ya mgeni na kifaa peke yake, hivyo hauitaji widget ya mazungumzo imewekwa kutoa ripoti. wawili hao wawili wawili Weka msaada wako, ukurasa wa umma na usaidizi wa ndani, pamoja na pamoja, ili uweze kuona ni kiasi gani kila mmoja anatumiwa.

💡
Analytics anakaa mbali mpaka kubadili juu yake, na unaweza kuwa na mgeni IP anwani anonymized. Hakuna kumbukumbu kabla ya kuchagua katika.

Chagua kile kinachoonekana kwenye kila ukurasa.

Kila sehemu ya Kituo cha Msaada (makundi kwenye ukurasa wa nyumbani, makala maarufu, orodha ya makala kwenye ukurasa na zaidi) ina kanuni yake rahisi. Kwa kila mtu unaweza kuonyesha au kujificha, na kuonyesha Yote yote kwa Kwa mujibu wa A, a Idadi yaKwa hiyo, Mwisho wa MwishoAu wale ambao bado wanakukumbuka Sifa ya kipengele Wakati utawala unapoweka orodha, wateja bado wanapata kiungo cha "Onyesha yote", kwa hivyo hakuna kitu kilicho nje ya kufikia.

Wewe pia kuamua jinsi kura muhimu kuangalia: siri, uwiano wa kirafiki kama "12 Kwa upande wa 14 kupatikana hii muhimu ", au makosa ya wazi Thumbs. kuweka chini-votes kuacha makala mpya kuonyesha awkward "0Kutoka nje ya0".

Angalia ni makala gani ya kazi

Kila makala inaonyesha a Je, hii ilikuwa na manufaa? Kila moja ndiyo au hapana inahesabiwa kwa kila makala, hivyo unaweza kuona katika mtazamo ambao makala hujibu maswali vizuri na ambayo ni lazima kuandika upya. kura zilizorudiwa kutoka kwa mgeni huyo zinapuuzwa, kwa hiyo makosa hukaa waaminifu.

Nakala na maandiko

Unaweza kubadilisha vichwa na maandiko kwenye Kituo cha Msaada ili kufanana na sauti yako. Acha shamba lolote tupu na linarudi kwa default ya busara, kwa hivyo unahariri tu maneno unayotaka kubadili.

Kituo cha Msaada kinashiriki maktaba moja na AI yako. Kila makala unayochapisha hapa ni maudhui sawa ambayo AI hutumia kujibu mazungumzo na tiketi, hivyo kuboresha moja inaboresha nyingine.

Maswali ya kawaida

Je, ninahitaji kuandika maudhui tofauti kwa Kituo cha Msaada?+

Inajengwa kutoka kwa makala sawa ya msingi wa maarifa ambayo AI hutumia tayari. chapisha nakala mara moja na inaweza kutumika wote wawili.

Ninawezaje kuhifadhi nakala za ndani?+

Ndio. makala tu wewe kuchapisha na alama ya umma kuonekana katika Kituo cha Msaada. chochote kisichochapishwa anakaa nje yake.

Je, wateja wanaweza kufikia mtu?+

Ndiyo, kiungo cha msaada wa widget kinakaa bomba mbali na kuanza mazungumzo, hivyo huduma ya kibinafsi kamwe haimtenganishi mtu yeyote.

Ukuaji wa SEO

Tovuti Intelligence (SEO suite)

Mtandao wa Intelligence niOpsIQKuwa mbunifu katika SEO Inatembea tovuti yako kama injini ya utafutaji, nyimbo ambapo una cheo, maneno muhimu ya utafiti, saa backlinks na washindani, pima uwepo wako wa ramani za mitaa, inaangalia kasi ya ukurasa, na kuibadilisha yote katika ripoti za kusomwa kwa wateja, na mchambuzi wa AI ambaye anaelezea nini cha kurekebisha na anaweza kuandaa fixes. Ni kipengele cha malipo; inapowezeshwa kuonekana kama Tovuti ya Akili katika ubao wa upande. Kila data ya kikoa inakaa tofauti, kutambaa, rankings na ripoti hazichanganya kati ya vikoa.

Tovuti ya Intelligence
Tovuti ya Dashibodi ya Usalama wa TovutiDashibodi ya SEO inayoonyesha alama ya afya ya tovuti, ufuatiliaji wa cheo cha neno muhimu na mwenendo wa trafiki.Tovuti ya Intelligenceyoursite.com86Afya ya Umma3 Masuala muhimuUfuatiliaji wa KeywordMsaada wa WhatsApp#3Kuishi chat saa#7crm kwa mashirika ya#12Clicks ya Organic1CrawlKutatua masuala ya kiufundi2TrackManeno muhimu, maneno ya msingi, backlinks3ya analytKueleza na kuandaa mipango ya
Mtazamo wa Akili wa Tovuti: alama ya afya ya tovuti kutoka kwa kutambaa hivi karibuni, kufuatilia cheo cha neno la msingi, mwenendo wa bonyeza kikaboni, na kitanzi cha hatua tatu: kutambaa, kufuatilia, hebu AI rasimu ya fixes.

Kupata tovuti ya akili

Ujasusi wa Tovuti ni sehemu ya mipango inayobeba. Kwenye mpango ambao haufanya kazi kama PeopleOS HR: mmiliki wa akaunti anafungua Akaunti → Addons & Links, inachukua kitengo cha Ujasusi wa Tovuti na kuanza jaribio la bure au linaongeza kabisa. Mpango wa bure, au mpango uliolipwa bado ndani ya majaribio yake mwenyewe ya mpango, hauwezi kuongeza. Mpaka inamiliki Suite imefichwa kutoka kwenye ubao na kiungo cha moja kwa moja hutoa nyongeza; wakati cap ya tier imefikia ukurasa inatoa tier ijayo; wakati kesi itakapomalizika bila kununua haki hiyo inaondolewa na hakuna kushtakiwa. Ukurasa wa Bei.

Bonyeza hapa kuanza ·

kutambaa ni OpsIQ kutembelea kurasa zako njia injini ya utafutaji ingekuwa, kupata masuala ya kiufundi: viungo vilivyovunjika, majina yaliyokosekana, maudhui nyembamba, kurasa za polepole, matatizo ya indexing.

1
Kuanza kwa kasi

Kwenye muhtasari, bonyeza kuanza kutambaa. OpsIQ mistari na inafanya kazi kupitia kurasa zako nyuma; kiashiria cha hali inaonyesha maendeleo.

2
Soma taarifa hizo

Wakati kumaliza, kufungua masuala na orodha ya ukurasa. Kila suala ni kundi kwa ukali hivyo wewe kukabiliana na kushinda kubwa kwanza.

3
Acha msaada wa AI

Mchambuzi wa AI hutoa muhtasari wa lugha wazi ya kile kilicho kibaya na kwa nini ni muhimu, na inaweza kuzalisha marekebisho yaliyopendekezwa unayopitia kabla ya kutumia.

Nini tovuti ya akili inafuatilia

Afya ya Tovuti & Afya ya tovuti

Scans kurasa zako kwa masuala ya kiufundi SEO na orodha kila ukurasa na matatizo yake. Re-run wakati wowote, au ratiba yake.

Ufuatiliaji wa

Ongeza maneno muhimu unayojali; OpsIQ hundi ambapo tovuti yako safu na nyimbo harakati kwa muda.

Utafiti wa Keyword

Kugundua mawazo mapya ya neno muhimu ili kulenga, na kocha wa nenosiri la AI kusaidia kipaumbele.

Viungo vya Backlink

Angalia kwa makini wale ambao wanataka kukutana na wewe, lakini si kuwa na uhusiano na wewe.

Washindani

Ongeza vikoa vya mshindani na kulinganisha mwonekano wako dhidi yao, na uchambuzi wa washindani wa AI.

Ramani ya (map) gridi ya taifa

Scan kuonekana kwa eneo la kujiandikisha kwenye gridi ya kijiografia ili kuona ambapo unajitokeza kwenye ramani, pamoja na zana za Wasifu wa Biashara ya Google.

Ukurasa wa Haraka

Tumia hundi za kasi ya ukurasa ili uweze kurekebisha kurasa za polepole ambazo zinaumiza rankings na uongofu.

Maudhui ya

Tengeneza muhtasari wa maudhui na rasimu zinazolenga maneno muhimu unayoyalenga.

Taarifa

Kujenga ripoti za kuchapishwa, tayari kwa wateja wa kila kitu hapo juu.

Kuunganisha Google kwa Data sahihi

Waunganishaji wawili wa Google wanabadilisha makadirio kuwa idadi halisi:

Google Search Console ya Utafutaji wa Google

Tafuta

Weka maswali halisi, bonyeza na hisia za Google kwa tovuti yako, ramani ya mali yako, na nafasi za cheo cha juu moja kwa moja kutoka data ya Google mwenyewe.

Google Analytics 4

Trafiki ya trafiki

Kuleta trafiki yako na data ya ushiriki pamoja na data yako ya SEO, kwa hivyo ripoti zinaonyesha kuonekana na tabia pamoja.

Taarifa za Kulipwa na White-label

Huna haja ya kuendesha kila kitu kwa mkono. Iliyopangwa huburudisha kutambaa tena, hundi za cheo, ukaguzi wa maneno, kurudi nyuma, scans za ndani na kizazi cha ripoti kwenye cadence (kila siku au kila wiki kulingana na mpango na kiasi). Hizi zinaendesha kupitia OpsIQ n, angalia Cron na sehemu ya automatisering. Ripoti zilizozalishwa kuuza nje kama nyaraka za kuchapishwa, zinazosoma wateja: wakala wanatuma kila mteja update ya SEO ya kawaida, na kwa sababu data ya kikoa ni mteja wao pekee, kila mmoja anaona tu.

Baadhi ya Huduma za Akili za Tovuti zinaita watoa data wa nje na AI kupitia OpsIQ's configured mtoa huduma. Wao kazi nje ya sanduku wakati suite ni kuwezeshwa kwa mpango wako. Kama refresh haina kukimbia, kuthibitisha OpsIQ Kwa mfano, unaweza kuona Cron na automatisering (angalia Cron).
Je, ninahitaji kuongeza kitu kwenye tovuti yangu kwa ufuatiliaji wa SEO?+

Crawls, ufuatiliaji wa cheo, utafiti wa maneno na backlink hufanya kazi bila kugusa tovuti yako. Kwa trafiki na data halisi ya utafutaji, kuunganisha Google Search Console na GA4.

Ninawezaje kupata zaidi ya moja?+

Ongeza kila uwanja tofauti; kutambaa kwao, nafasi na ripoti hukaa peke yake kutoka kwa kila mmoja.

Ni mara ngapi ninapaswa kuosha?+

Kila wiki ni mengi kwa tovuti nyingi; kutambaa juu ya mahitaji baada ya maudhui makubwa au mabadiliko ya muundo. Weka ratiba hivyo wewe kamwe kusahau.

Ukuaji wa SEO

Kuajiri (Mtendaji wa SEO)

Ukamilifu wa Auto ni sehemu ya Intelligence ya Site ambayo kwa kweli inatumika kurekebisha mpasuaji na mchambuzi wa AI kupendekeza, badala ya kushauri tu. Wakala anafanya kazi madhubuti kutoka kwa kile ambacho Tovuti ya Akili tayari imepatikana (haiwezi kamwe kuunda mabadiliko) na anatembea kila kurekebisha kupitia kitanzi kimoja salama: hakikisho la kukimbia kavu, idhini yako ya hatua kwa hatua, kuandika moja kwa moja, picha ya moja, na safu ya upya ambayo inathibitisha hesabu ya kutolewa wazi ilishuka. Ni kipengele kilichosimamiwa-AI-tu; inaonekana kama Sehemu ya Auto-Implement (sehemu ya ndani ya kuingilia)

Utekelezaji wa Auto
Kuwezesha SEO AgentMtiririko unaoonyesha marekebisho yaliyopendekezwa ya SEO kusonga kupitia hakikisho, idhini na kuandika moja kwa moja, na re-kukimbia tena.Utekelezaji wa Autoyoursite.comKupendekezwa fixesAdd missing <title>ImeidhinishwaKuhamisha robots. txtImeidhinishwaBonyeza sitemap.xmlUkaguzi waUchoraji wa DRY-RUN (DIFF)+ <title>AI Helpdesk - OpsIQ</title>+ <meta name=description ...>- <title>Home</title>KukubalianaRuvu ya kurukaKufufua - Re-CRAWLMasuala ya wazi 124Snapshot ya kuokolewa1Precipital yaKukausha kwa kila njia ya kusafisha2Barua ya maombi na baruaSSH au kuwa mwenyeji API3Uchoraji na RobKufufua + snapshot
Jinsi kikao kinavyoendesha: wakala anaorodhesha maelezo ya tovuti ya akili tayari iliyopendekezwa, inaonyesha usambazaji wa kila mmoja, hutumia zile unazoidhinisha zaidi. SSH au kuwa mwenyeji API Kabla ya kuandika kila kitu, hakikisha kuwa unakusanya maelezo ya kina.

Nini inaweza kubadilika

Wakala daima hutumia marekebisho ambayo Site Intelligence (au mchambuzi wa AI) tayari ilipendekeza kwa uwanja huo. Katika majukwaa yaliyosaidiwa ambayo inashughulikia:

Server ya config

sitemap.xml, robots. txt, na kuelekeza tena, kanuni za canonical na header katika . htaccess (Apache / LiteSpeed) au usanidi wa nginx.

Kurudisha kwa minyororo

Inapita mlolongo wa pop-hop unaoelekeza chini kwa hop moja kwa moja hadi mwisho URL, ndani ya kizuizi hicho kilichosimamiwa na . htaccess, hivyo kasi na thamani ya kuunganisha kuacha kuvuja kupitia hops za ziada.

Page <head>

Majina ya ukurasa wa missing au dhaifu, maelezo ya meta, vitambulisho vya canonical na vitalu vya data (schema).

WordPress SEO

Yoast, Rank Math na majina ya SEOPress & meta, na maandishi ya picha ya alt, yaliyotumiwa kupitia WP-CLI kwenye kichwa cha habari. SSH Njia ya kwenda au kurudi nyuma API kwenye barabara ya lami.

WordPress Data ya muundo

Kuongeza JSON-Kutoa taarifa kwa vyombo vya habari ambavyo havihusiki na tukio hilo SSH Njia ya msaidizi mdogo aliyesimamiwa (mtumiaji wa kutumia Plugin) huchapisha markup hivyo inafanya kazi na au bila programu-jalizi ya SEO; kwenye njia iliyohifadhiwa ambayo Plugin yako ya SEO inaibeba.

Viungo vya ndani

Inaongeza kiungo kimoja cha ndani kinachohusika ndani ya maudhui yaliyopo WordPress ili kuokoa kurasa za yatima na kuunganisha machapisho yanayohusiana. Kiungo kimoja kwa kila ukurasa, kamwe ndani ya kichwa, kiungo kilichopo au shortcode, na daima kupitishwa na wewe kwanza.

Maudhui ya ukurasa wa chini yanaandika

Rasimu kamili ya maudhui ya badala kwa kurasa nyembamba (zilizobadilishwa na chaguo la kutambaa, angalia chini). Kila rasimu inapitiwa na kupitishwa na wewe kabla ya kuchapisha chochote, na yaliyomo ya zamani yanahifadhiwa ili iweze kurejeshwa.

Ukurasa wa Akaunti (WordPress)

Inageuka kwenye caching ya ukurasa wa W3 Jumla ya Cache wakati kutambaa hupata matatizo ya kasi na Plugin hiyo imewekwa, kwa hivyo kurasa hutumikia haraka.

Shopify SEO

Bidhaa na ukusanyaji wa majina ya SEO & maelezo, ukurasa na blog-article SEO, pamoja 301 Kurejea, kwa njia ya Shopify Usimamizi wa API.

Webflow SEO

Kichwa cha SEO na maelezo ya meta kwa njia ya ukurasa Webflow Data ya data API v2 ya wa.

Kutayarisha vifaa vya moja kwa moja (chaguo mbili za kutambaa)

Jopo la Ushauri wa Site Intelligence lina jopo la kikoa (maeneo yake ya kutambaa) ina chaguzi mbili zinazoamua ni kiasi gani cha wakala kinachokuweka mbele ya muda. Zote zimeachwa kwa default na zote zinatumia mkopo wa AI, hivyo unazibadilisha tu wakati unataka kazi hiyo ifanyike kwako.

Auto-prepare AI hurekebisha baada ya kila kitambaa

Kila kutambaa pia anaandika maudhui ya kurekebisha halisi (vifaa, maelezo ya meta, maandishi ya alt, schema, redirects) kwa kile kilichopatikana, hivyo marekebisho yako tayari kuchunguza na kutumia wakati kitambaa kinamaliza badala ya kuzalishwa baadaye juu ya mahitaji.

Makala ya awaliMaandishi ya Maudhui (Tafsiri za ukurasa)

Wakala anaweza kuandaa maudhui kamili ya badala kwa kurasa nyembamba. Hakuna kitu kilichochapishwa peke yake: kila rasimu inaonekana kama mabadiliko unayopitia upande na kukubali au kukataa, yaliyomo ya awali yanahifadhiwa hivyo ni reversible, na ni mdogo kwa kurasa chache kwa kupitisha.

💡
Chaguzi zote mbili zinaandaa tu na kuandaa kazi ya rasimu. Kila mabadiliko bado yanaendelea kupitia idhini sawa kwa hatua, snapshot na rollback kama kurekebisha nyingine yoyote, hivyo kuwageuza kwenye kamwe huweka chochote kuishi peke yake.

Njia mbili za kuunganisha

SSH / SFTP Njia ya njia

Kujitegemea

Kwa tovuti kwenye seva yako mwenyewe, wakala huunganisha juu SSH/SFTP Kutumia sifa unazohifadhi, hariri faili za usanidi wa seva na ukurasa moja kwa moja, na inaendesha WP-CLI kwa ajili ya WordPress Bora wakati una upatikanaji wa shell na unataka udhibiti kamili wa faili.

Licha ...API Njia ya kwenda (hakuna njia) SSH)

Hakuna cha ziada

Kwa ajili ya majukwaa ambayo hayaruhusu SSH· Serikali inafanya kazi kwa njia ya afisa mmoja API Mawasiliano ya simu, WordPress (REST + Maombi ya Neno la siri), Webflow (Takwimu za data)API v.2 na ya Shopify (Sauti ya API Hakuna kitu kinachowekwa kwenye mwenyeji.

💡
Wix na Squarespace hawana waandishi wa umma wa SEO API Kwa hivyo kwenye majukwaa hayo Auto-Implement anaendesha katika hali ya ushauri: inaonyesha mabadiliko halisi ya kufanya (jina sahihi, meta au kuweka) kwako kuomba kwa mkono. Kila kitu kingine ni kusoma tu na salama.

Kugeuka kwenye kontakt

Kila jukwaa linafikia kila jukwaa kupitia kiunganishi:

Kujengwa katika

Shopify Aidha, na WordPress Meli ya abiria iliyo na OpsIQ, tu kuwawezesha chini ya Uunganisho na kuongeza sifa za duka / tovuti.

Kutoka kwenye soko la

Webflow, Wix na Squarespace kufunga kutoka kwa Connectors → Marketplace, kisha kuunganisha njia hiyo.

Jinsi Mkutano Unavyoendelea

1
Chagua mipangilio

Fungua Utekelezaji wa Auto (rocket) kutoka sehemu ya Ujasusi wa Tovuti. Inaorodhesha masuala ya Usalama wa Site tayari iligundua kuwa inaweza kurekebisha kwenye uwanja huu.

2
Kutathmini kila mabadiliko

Kwa kila kurekebisha wakala inaonyesha usambazaji wa kavu (hasa kile kitakachoandika) kabla ya kitu chochote kugusa tovuti ya kuishi.

3
Hatua kwa hatua

Unakubali (au kuruka) kila mabadiliko binafsi. Hakuna kitu kinachotumika bila kwenda-juu ya hatua hiyo.

4
Inaandika, kisha inapiga picha

Kwa mujibu wa taarifa hiyo, kampuni hiyo itafanya mabadiliko ya SSH au kwa ajili ya kuuzwa API Kwanza kabisa, ni muhimu kuokoa mmea, hivyo mabadiliko yoyote yanaweza kurudiwa.

5
Kuthibitisha, Kuishi

Kama inatumika kila mabadiliko wakala mara moja re-checks kwamba ukurasa halisi na inaonyesha kwa hatua "kupangiliwa kuishi" hukumu, hivyo wewe kuangalia kila ardhi fix kwenye ukurasa wa kuishi kama hutokea. Mwishoni ni upya tovuti nzima na kuthibitisha hesabu ya wazi iliyotolewa.

Usalama na bili

SEO ya pekee

Wakala anaweza tu kufanya kile ambacho Tovuti ya Akili ilipendekeza kwa kikoa hicho. Haiwezi kufanya mabadiliko ya kiholela kwenye tovuti yako au seva.

Ruhusa ya Hatua kwa hatua

Kila barua inaonyeshwa kama usambazaji na kutumika tu baada ya kupitisha hatua hiyo maalum.

Kuruka kwa kasi na rollback

Kila kitu kinahifadhiwa kabla ya kuandikwa, hivyo mabadiliko yoyote yanaweza kurejeshwa.

Ushahidi wa hatua kwa hatua

Kila ukurasa uliobadilishwa unakaguliwa tena mara moja imeandikwa na kupata uamuzi wa "uliorekebishwa kuishi", kwa hivyo kurekebisha imethibitishwa dhidi ya ukurasa wa kuishi mara moja, sio tu katika mzunguko wa kufungwa.

Maudhui ya kamwe si kuchapishwa auto

Viungo vya ndani na upyaji wa maudhui ya ukurasa mwembamba ni athari kubwa zaidi, kwa hivyo daima huonyeshwa kwako kwa idhini na kamwe haitumiki moja kwa moja, hali yoyote unayoendesha.

Kujiandaa kwa ajili ya

Utekelezaji wa Auto unaendesha AI iliyosimamiwa; imefungwa wakati nafasi ya kazi inatumia funguo zake (BYOK).

Billing ya

AI ishara muswada kawaida kama wewe kutumia yao, pamoja na gorofa kwa matumizi ya ada kwa Auto-Implement kikao, wote inayotolewa kutoka sawa kusimamiwa-AI mikopo.

Kuwezesha Auto-Implement ni mbali na default. Wezesha kwenye ukurasa wa usanidi wa AI (kadi ya Utekelezaji) na uhakikishe kontakt kwa jukwaa lako imeunganishwa kwanza.
Je, kuna mabadiliko yoyote bila ya kuuliza?+

Kila mabadiliko ni hakikisho kama kavu-kukimbia diff na kutumika tu baada ya wewe kupitisha kwamba hatua halisi. snapshot ni kuokolewa kabla kila kuandika ili uweze kurudi nyuma.

Ninahitaji SSH upatikanaji?+

Si juu ya WordPress, Shopify au Webflow. Wale kazi kupitia rasmi yao APIs bila shell kupata. SSH ni moja tu ya njia mbili, kutumika wakati unataka wakala wa hariri server config na faili moja kwa moja kwenye seva yako mwenyewe.

Jinsi gani tunajua kwamba kazi?+

Baada ya kutumia marekebisho yaliyoidhinishwa, wakala anafungua tena tovuti na inaonyesha hesabu ya suala la wazi kabla na baada, ili uweze kuthibitisha kurekebisha mapungufu yaliyopunguza masuala.

Je, ni lini itachapisha au kuchapisha maudhui ya ukurasa kwa njia yake mwenyewe?+

A. Maudhui ya AI yanarekebishwa hadi unapowageuza kwenye chaguzi za kutambaa, zinazuiwa kwa kurasa chache nyembamba kwa kupitisha, na kila rasimu inaonyeshwa kwako idhini ya upande kabla ya kuchapisha kitu chochote. maudhui ya awali imehifadhiwa, hivyo kuandika upya kunaweza kurudishwa kila wakati.

Ninawezaje kutumia funguo zangu za AI?+

Utekelezaji wa Auto unasimamiwa-AI tu na imefungwa chini ya BYOK. Inahesabu ishara za AI kawaida pamoja na ada moja ya gorofa kwa matumizi ya kila kikao, kutoka kwa mkopo huo uliosimamiwa-i.

Ukuaji na Ushiriki

Utafiti wa Studio

Studio ya Utafiti ni nafasi ya kazi kwa ajili ya kujenga tafiti zinazofaa ambazo zinaweza kutolewa kama ukurasa wa kawaida, widget ya tovuti au embed. Bidhaa ya sasa pia hutoa viungo vilivyokaribishwa, uhakiki wa rasimu iliyosainiwa, mialiko binafsi, kugawana QR, kuvinjari majibu na uchambuzi wa uchunguzi.

⚠️
Mipaka ya sasa ya malengo: Uzoefu wa ubunifu na uzoefu wa kwanza, Connector Builder survey uwezo, na mtoa huduma wa usajili / afya mipaka zinapatikana sasa. Studio ya Utafiti bado inahitaji usanifu huru wa kazi nyingi, Gateway ya utambulisho wa utafiti uliosainiwa, kulenga / kugusa wiring, CRM Outreach kutuma mtiririko na aina surveys.* API.

Kujenga uchunguzi

1
Chagua jinsi watu watakavyokuchagua

Mchawi wa sasa hutoa ukurasa wa Standalone & kiungo, widget ya tovuti na Inline embed. mtiririko ulioidhinishwa huanza na aina ya utafiti na baadaye huongeza barua pepe ya CRM, viungo vya kibinafsi na kupelekwa kwa QR kama uchaguzi wa darasa la kwanza.

2
Chagua lengo

Pick NPS, CSAT, CES, maoni ya bidhaa, baada ya ununuzi, kufuta, onboarding, tovuti, tukio, webinar, msaada, risasi /demo, jaribio, ushuhuda, utafiti, mfanyakazi, ulaji au maoni ya jumla.

3
Tumia template kamili au kuanza tupu

Orodha ya sasa ina watangulizi tayari wanaobadilishwa kwa kusudi. Kuchagua template inajenga rasimu iliyonakiliwa: kubadilisha utafiti wako haubadilishi starter au uchunguzi mwingine.

4
Ukaguzi wa haraka au wa haraka

Customize kufungua kila swali, kubuni, tabia na udhibiti wa utoaji. Mapitio ya haraka kufungua rasimu hiyo katika ukaguzi wa mwisho wa wateja-mtazamo. Hakuna kuchapisha au kutuma moja kwa moja.

Uchaguzi wa sasa na tabia ya

Ukurasa wa Standal & Link

Ukurasa uliochaguliwa na mwenyeji wa wavuti mwenyewe URL Tumia mialiko ya kibinafsi na expiry wakati kila mpokeaji anahitaji kiungo kinachodhibitiwa.

Tovuti ya widget

Ni inaweza kutumia ukurasa, jiografia, kifaa, mgeni, tarehe, sampuli, cooldown, ziara na kanuni za upendeleo. bado ni mkono na urithi haiwidget daraja wakati usanifu kupelekwa ni kujengwa.

Inline ya Embed

Utafiti wa msikivu uliowekwa ndani ya ukurasa, portal, bidhaa au kituo cha msaada. Haihitaji Studio ya Kukuza.

Barua pepe

Leo Studio inaweza kuzalisha mialiko HTML na viungo vya kibinafsi. Mwisho-kwa-mwisho kutuma kutoka kwa anwani za CRM / ushirikiano, kwa idhini, ukandamizaji, ratiba, retry na uwiano wa majibu, ni lengo la kupitishwa la ujumuishaji wa CRM.

Biashara ya kubuni na preview

Kurasa za utafiti zina mandhari inayomilikiwa na Utafiti na familia za ukurasa wa kufunga, udhibiti wa msikivu, nakala ya kukaribisha na kukamilika, na uhakiki wa rasimu iliyosainiwa. preview ya mtengenezaji ni kamili chini ya mhariri, sio reli nyembamba ya upande. Inatumia muda halisi wa kukimbia katika sura ya sandboxed na inasaidia desktop, kibao na upana wa simu; trafiki ya hakikisho haiandiki majibu au analytics.

💡
Studio ya Utafiti ni huru kutoka kwa Promotion Studio. Kulenga, utambulisho, mali, utoaji na uchambuzi lazima iwe inayomilikiwa na Utafiti. Maudhui ya kukuza yanaweza kutumiwa tu kupitia nakala ya wakati mmoja / muhimu ambayo inajenga data ya Utafiti; hariri za baadaye za Kukuza zinapaswa kuwa na athari yoyote.

Bidhaa ya fomu kamili

Shughuli za kujitegemea

Maisha ya kuishi

Utafiti mmoja unaweza kuwa na ukurasa uliochapishwa tofauti, widget, embed, CRM barua pepe, kiungo binafsi na QR kupelekwa, kila moja kwa hali yake mwenyewe, kubuni, watazamaji na analytics. Kila utafiti inaweza kusimamishwa, walemavu au kufutwa.

CRM na kampeni za

Maisha ya kuishi

Kujenga watazamaji kuthibitishwa kutoka kwa sehemu za CRM na viunganisho vya uchunguzi, kuifungia katika toleo lisilobadilika, kutoa mwaliko mmoja uliosainiwa kila mmoja, na tuma kupitia kontakt ya barua pepe iliyopigwa na uthibitisho wa utoaji wa kituo.

Vifaa vya Field na Uthibitisho

Maisha ya kuishi

Sliders, uchaguzi wa picha, kupakia faili, saini, anwani, simu, vichwa na maandishi tajiri, kwa urefu mdogo / upeo, barua pepe / URL/number presets, maandiko ya kosa la desturi na vigezo vya swali la kila URL.

Mantiki, formulas, matokeo

Maisha ya kuishi

Na / au makundi ya hali, sheria za tawi, injini salama ya fomu juu ya majibu, na bendi za alama ambazo zinashikilia ukurasa wao wa matokeo: ardhi ya mtihani uliopigwa kwenye uamuzi wake.

Lugha ya Kiosk, Prefill

Maisha ya kuishi

Lugha ya wageni inaorodhesha tu lugha zilizo na tafsiri halisi, hali ya kiosk kwa vidonge vya pamoja (malengo makubwa, kurekebisha gari, hakuna kuelekeza), wajenzi wa kiungo cha kabla, na maandishi salama na yenye ufanisi.

Jaribio la A / B

Maisha ya kuishi

Kuchapisha toleo la changamoto juu ya kupelekwa kwa yoyote na mgawanyiko wa trafiki. Wageni wanapewa fimbo, majibu yanapigwa muhuri na toleo lililotumiwa kweli, na meza ya kulinganisha inaonyesha majibu, kukamilika na alama ya maana kwa kila toleo. Kukuza mshindi katika bonyeza moja.

Wiki ya Kupumua

Maisha ya kuishi

Email ya kila wiki na mwisho wa 7 Siku za KPIs ya utafiti, tafiti nyingi zaidi, pigo la maoni na mkutano wa hivi karibuni wa AI, uliotumwa kupitia kiunganishi cha nje kilichopigwa.

Utawala wa utawala

Maisha ya kuishi

Orodha ya upatikanaji wa kila siku inayozuia nani anayeweza kuhariri, kuchapisha au kufuta utafiti. chapisha idhini (macho manne) inahitaji admin wa pili kutoa rasimu halisi; uhariri unarekebisha kibali. viungo vya kushiriki kwa Rasimu basi mhakiki aone rasimu halisi bila kuingia.

Programu ya Developer

Maisha ya kuishi

Mkataba wa Connector 2.2, utafiti wa aina. * na maoni.* Vitendo api/v1, utafiti wa kanoni. * matukio, webhooks za kudumu zilizosainiwa na Slack na Google Sheets relay miundo, na majibu moja PDF ya usafirishaji.

Ukuaji na Ushiriki

Utafiti wa Analytics na maoni ni bidhaa tofauti

Uchunguzi wa uchambuzi unaelezea jinsi utafiti wenyewe unavyowafikia watu na kufanya. Maoni yanafafanua kile wateja walisema katika vyanzo vyote vilivyoruhusiwa na biashara inapaswa kufanya kuhusu hilo. Bidhaa mbili zinaunganisha kila mmoja lakini hazishiriki au kuandika ukweli wa uchambuzi.

Uchunguzi wa Analytics

Iliingizwa kutoka kwa utafiti wa kibinafsi katika Studio ya Utafiti, sio kutoka kwa urambazaji wa upande wa kimataifa. Inapima ustahiki, mfiduo, kuchochea tabia, huanza, kukamilika, kuachwa, swali na msuguano wa tawi, muda, kupelekwa / matokeo ya kupotosha na kuegemea wakati wa kukimbia.

Maoni ya jumla & Inbox

Moja ruhusa-kufahamu chronological kulisha kwa majibu ya kukamilika Utafiti, kumbukumbu widget maoni, chat na tiketi CSAT, tiketi jibu maoni, wateja AI-answer ratings, maarifa-msingi kura muhimu na kupitishwa nje / vyanzo vya mteja.

Maoni ya Analytics

Analyzes maana ya mteja: asili metric mwenendo, mada / mandhari, hisia, mawazo, nia, dharura, maombi, malalamiko, sifa, safari / bidhaa / huduma / timu vipande, detractors na closed-mzunguko matokeo.

Umiliki wa Data

Majibu ya utafiti yanabakia mamlaka katika hifadhi ya Utafiti. Maoni huhifadhi kumbukumbu za chanzo zinazoweza kujengwa na ishara zilizotokana, kisha hubeba ushahidi unaoruhusiwa juu ya mahitaji. Jibu moja la kukamilika kwa uchunguzi inakuwa kwenye kipengee kimoja cha maoni.

⚠️
Ukurasa wa sasa wa maoni bado una kivinjari cha majibu ya Utafiti na kikasha tofauti cha kumbukumbu, na jumla zake za AI bado hawatumii mfano kamili wa chanzo. Muhtasari wa umoja / Inbox / Analytics / Vyanzo & muundo wa afya ni lengo la utekelezaji.

NPS, CSAT, CES, nyota, thumbs na kusaidia lazima daima kuhifadhi njia yao ya asili, kiwango, sampuli, dirisha la tarehe na denominator.

Ukuaji wa SEO

Studio ya Matangazo

Studio ya Kukuza inageuka tovuti yako katika injini ya uongofu. Kubuni pop-ups, mabango, slide-ins, baa za juu /bottom, kuchukua skrini kamili, vitalu vya inline na hata kuelekeza nchi makao, kisha kuonyesha ujumbe sahihi kwa mgeni kulia wakati wa kulia. Kila kitu ni mikononi kupitia widget ya OpsIQ tayari kwenye tovuti yako, hivyo hakuna chochote cha ziada cha kufunga. Wewe kubuni na kuokoa kampeni wakati wowote; wanaonyesha tu mara unapochapisha na studio imebadilishwa kwenye nafasi yako.

Studio ya Matangazo
Design ya StudioMuundaji wa kampeni ya kuona na palette ya vitalu, pop-up kwenye turubai, na jopo la kulenga.Msaada wa kiufundi - Designerya wankxKwa bahati nzuri, {first_name}!Kupata Kupata 15% Weka amri yako ya kwanzaSAVE15Kudai kadi yanguKutishaNchi ya nchiMarekani, CATrigger yaKutoka-kusudiA / B ya mgawanyiko50 / 50Mwandishi wa1Muundo waDrag vitalu kwenye turubai2MalengoNchi, ukurasa, watazamaji3Rahisi yaA / B ya kushinda na AI
designer Visual: palette ya vitalu upande wa kushoto, kampeni yako kwenye turubai (hapa pop-up ya kibinafsi kwa kutumia ishara ya {first_name}), na jopo la kuchapisha + linalolenga kulia.

Picha kubwa

Kampeni ya kampeni

Nini Maana ya Nini

Kukuza moja: pop-up, bendera, bar, slide-in, full-screen, inline block au geo-redirect. Kila mmoja ana lengo: mauzo, risasi, ishara ya juu, chat, utafiti, tangazo.

Design & Matoleo ya

Jinsi ya jinsi gani

Kila kuokoa inajenga toleo jipya, hivyo unaweza daima roll nyuma. hakuna kitu ni milele waliopotea.

Malengo ya

Nani ambaye ni nani ambaye

Ambao anaona ni: nchi, ukurasa, kifaa, chanzo trafiki, kurudi vs mpya, ratiba, na (na kontakt) wateja wako watumiaji-katika.

Vichochezi

Wakati ambapo wakati

Wakati inaonekana: mara moja, juu ya kuchelewa, kwenye kitabu, kwenye njia ya kutoka, wakati wa bure, kwenye bonyeza, baada ya kurasa za N, au kutoka kwa shughuli za mazungumzo / tiketi.

Uchambuzi

Matokeo ya matokeo

Hisia za kuishi, bonyeza-kupitia, uongofu, funnel ya kushuka, nchi / ukurasa / kifaa hupasuka, washindi wa A / B na ufahamu wa AI.

Kuanzisha yako ya kwanza kukuza katika 5 Hatua za hatua

1
Kuanza kutoka template au blank

Open Promotion Studio na bonyeza kampeni mpya, au kuchagua kubuni tayari-made kutoka nyumba ya sanaa templates. rasimu kufungua katika designer.

2
Kuumba kwa ajili ya

Drag katika vitalu, vichwa, maandishi, vifungo, picha, badges, stats, kuhesabu, fomu, kuponi, video, ratings, spin-wheels. Rangi ya mtindo, gradients na madhara 3D na sliders. Preview Desktop / Tablet / Simu, na kutumia bure hoja mahali popote.

3
Binafsi yake

Aina tokens kama {first_name}, {country} au {company} katika maandishi yoyote. Wakati wa kuonyesha-wao kuwa wageni's halisi maadili.

4
Malengo ya Target & trigger

Chagua ambaye anaona (nchi, ukurasa, kifaa, watazamaji) na wakati moto (kuotea, scroll, exit-intent).

5
Angalia, kisha kuchapisha

Bonyeza Angalia kwa skanning ya haraka kabla ya uzinduzi, kisha Chapisha. Inakwenda kuishi ndani ya sekunde na kuanza kukusanya analytics.

Vifaa ambavyo unaweza kujenga

Maudhui ya Maudhui

Nguvu

Kichwa, aya, orodha, quote, picha, icon, badge, stat, mgawanyiko na spacer, vitalu vya ujenzi wa ujumbe wowote.

Wito wa hatua

Nguvu

Buttons na vitendo halisi: kufungua kiungo, kuanza kuzungumza, kujenga tiketi, nakala coupon, au kuruka kwenye ukurasa.

Uasi wa haraka na kukamatwa

Premium ya kwanza

Muda wa kuhesabu, fomu (Email / simu / maandishi), coupon inaonyesha na video embeds.

Maoni & maoni

Premium ya kwanza

Spin-to-win magurudumu, kadi scratch, NPS / nyota ratings na funnels mbalimbali hatua.

Madhara ya Layout & Athari

Premium ya kwanza

Nguzo, baa za maendeleo, ushiriki wa kijamii, majibu ya ushahidi wa jamii, ndiyo / hakuna hatua mbili, maswali, na madhara ya 3D, tilt, angaza, parallax, glassmorphism.

Uwasilishaji wa kibinafsi

Aina yoyote ya haya katika vichwa, aya, vifungo, badges, stats, orodha au quotes. Wao ni kubadilishwa na maelezo ya kuishi ya mgeni wakati matangazo inaonyesha (kila mara kusafishwa kwa ajili ya usalama):

Vifaa vya Kutosha
From the visit:   {country} {city} {device} {page_path} {utm_source} {referrer}
From your CRM:    {first_name} {last_name} {email} {company} {segment} {lifecycle_stage}
From a connector: {balance_due} {unpaid_invoices}   (logged-in customers only)

Malengo ya kumbukumbu

Nchi na Eneo

Onyesha tu katika (au kujificha kutoka) nchi zilizochaguliwa, miji au maeneo ya wakati kupitia GeoIP. Kubwa kwa matoleo maalum ya mkoa au geo-kuelekeza.

Ukurasa wa & URLs

Mipaka ya kurasa fulani kwa kutumia usawa / kuanza na / ina / regex, na haijumuishi kurasa pia.

Vifaa vya

Desktop, kibao au simu ya mkononi, kwa mfano bar ndogo kwenye simu, modal kwenye desktop.

Aina ya wageni

Mpya, kurudi, inayojulikana (katika CRM yako) au bila kujulikana; sehemu za CRM, hatua ya maisha, alama ya kuongoza au lugha ya kivinjari.

Vyanzo vya trafiki

Kwa UTM (utm_source, utm_campaign) au kutaja tovuti, kwa mfano wageni tu kutoka tangazo maalum.

Ratiba ya mzunguko & frequency

Kuanza / tarehe ya mwisho, madirisha ya wakati wa siku, na mara ngapi mtu anaweza kuiona (kwa kikao, kwa siku, baada ya kufunga / bonyeza / kubadilisha).

A / B ya trafiki

Onyesha kwa asilimia ya wageni na kukimbia variants kichwa-kwa-kichwa; mtu huyo daima anaona lahaja sawa.

Ukaguzi (Logged-in)

Kwa kontakt kuwezeshwa, lengo na hali ya akaunti ya kuishi, kwa mfano wateja wenye ankara zisizolipwa, au wanachama wa kazi.

Vichochezi

Chagua jinsi kukuza inaonekana: Mara moja, baada ya kuchelewa, juu ya kina cha kitabu, kwenye hali ya nje, wakati wa bure, kwa kubonyeza kipengele, baada tu ya kurasa kadhaa kutazamwa, kwenye fomu-bandon, au kutoka kwa shughuli za mazungumzo / tiketi. Waendelezaji wanaweza moto mmoja kutoka msimbo wao wenyewe na window.OpsIQPromo.fire('event').

Wateja wa Target (Waunganishaji)

Hii ndio inafanya OpsIQ Matangazo maalum: kuunganisha jukwaa kama WHMCS (au kontakt yoyote inayounga mkono watazamaji) na studio inaweza kulenga wageni kwa hali yao ya akaunti ya kuishi.

1
Kuwezesha kontakt ya watazamaji

Chini ya Waunganishaji, kuwezesha moja ambayo inaonyesha ukweli wa watazamaji (WHMCS inafanya nje ya sanduku). Wateja wanatambuliwa salama wakati wa kuingia kwenye jukwaa hilo, OpsIQ kamwe hawaamini barua pepe iliyounganishwa.

2
Kuongeza utawala wa watazamaji

Katika lengo la kampeni > Ukaguzi, unahitaji kuingia na kuongeza sheria kama ankara zisizolipwa > 1, usajili ni uliopitadue, au akaunti ya mikopo > 0.

3
Binafsi na data zao

Matumizi ya alama kama vile {first_name} au {balance_due}. A "Una ankara iliyopita" kumbukumbu anaandika mwenyewe.

Kulenga kwa watazamaji ni kushindwa-usalama: ikiwa kontakt haiwezi kuthibitisha ukweli (au mgeni hakuingia), kukuza tu haionyeshi, hivyo kutoa inayolengwa haijawahi kufikia mtu mbaya. Kujenga kiunganishi chako mwenyewe?

Uwezo wa kufanya kazi (Company Supermarket)

Bidhaa kutoka kwa duka lako

Data ya kuishi

Kuzuia bidhaa huvuta vitu halisi (jina, bei, bei ya kuuza, picha, kiungo) moja kwa moja kutoka WHMCS, WooCommerce, Shopify au yako OpsIQ Tick "Kuweka safi" na kadi updates bei yake kutoka jukwaa kila saa wakati kuchapishwa.

Bidhaa zilizohifadhiwa

Kufuru za

Kuzuia coupon inaweza kuunda msimbo halisi wa discount katika duka lako wakati unapochapisha, kwa hivyo nambari ambayo mgeni hufunua daima hufanya kazi wakati wa Checkout.

Mapato ya kweli

Uchangiaji wa

Amri halisi kutoka kwenye majukwaa yako zinalingana na kampeni kila saa (kwa msimbo wa kuponi unaotumiwa au kwa barua pepe ya kuongoza) hivyo mapato unayoona ni kutoka kwa mauzo halisi, sio makadirio.

Ushahidi wa kweli wa kijamii

Kuamini

Kichupo cha uthibitisho wa kijamii kinaweza kuongoza na maagizo ya hivi karibuni ("Ada aliamuru Mpango wa Starter · 2h Kwanza, jina la kwanza na bidhaa tu, kamwe barua pepe au kiasi.

Majaribio na safari

A / B ya matumizi ya auto-winner

Split trafiki katika anuwai ya kubuni; basi studio kukuza mshindi wa takwimu moja kwa moja, au trafiki mkono kwa bandit optimiser ambayo inabadilisha wageni kuelekea kile kinachobadili kama ushahidi huja.

Kuinua juu

Hifadhi kipande cha wageni ambao hawaoni chochote, kwa hivyo unaweza kuthibitisha kampeni yenyewe husababisha kuinua.

Tofauti ya

Maudhui tofauti kwa watazamaji kwenye kampeni ya SAME (wageni wa simu, mikokoteni kubwa, wateja wanaorudi), kila sehemu inapata toleo lake mwenyewe.

Majaribio ya Trigger

Variants pia inaweza mtihani Wakati wa kuonekana: mara moja vs kuchelewa dhidi ya exit-intent, kipimo kichwa kwa kichwa.

Safari ya (chaining)

Lengo na kile mtu alifanya na kampeni nyingine ("saw kampeni A lakini hakuwa waongofu") kujenga mlolongo wa kukuza hatua mbalimbali.

Wachezaji

Wageni wa kidonge kidogo wanaweza kufungua tena baada ya kufunga kampeni, kwa hivyo pop-up imefungwa haijawahi kwenda kwa nzuri.

Kujua nini kilichotokea

Bonyeza kitufe cha "Strewing"

Msanii

Katika designer, toggle heatmap rangi halisi mgeni clicks juu ya kila block ya kubuni yako.

Hatua ya funnel

Furaha ya

Kampeni nyingi za hatua zinaonyesha hasa ambapo watu wanaacha, skrini kwa screen.

Kulinganisha kampeni

OpsIQ

Weka hadi kampeni nne kwa upande (maonyesho, bonyeza, uongofu), thamani bora iliyoonyeshwa.

Hadithi ya wiki na digest

I

Kila Jumatatu ardhi ya kuchimba katika taarifa zako; kifungo cha hadithi ya wiki ya 📖 kinaandika muhtasari wa lugha wazi na hatua zifuatazo wakati wowote unataka moja.

Kufanya kazi kwa utulivu

Kuwa Copilot & Mawazo

Kuzungumza na copilot ya kubuni ili kuhariri turuba ("fanya kichwa cha habari haraka, kuongeza kuhesabu"), kupata mawazo ya kampeni kutoka kwa data yako mwenyewe ya trafiki, kutafsiri kampeni kwa nchi, au auto-fix alama ya chini ya kubuni.

Bidhaa ya kuagiza

Amri moja inasoma tovuti yako na inapendekeza rangi zako za kweli za bidhaa na fonti; kuokoa na kila picker inaongoza pamoja nao.

Multi-screen mifereji

Hatua vitalu kupata kweli kwa ajili ya uhariri wa skrini: tabo kwa kila screen, kuongeza au reorder screens, na preview ifuatavyo.

Majina ya majina na uwepo

Jina matoleo muhimu ("Mgombea wa Launch"), rudisha yoyote yao, na uone onyo wakati mchezaji anahariri kampeni hiyo.

Vifaa vya Kusafirisha na Utawala

Angalia desktop, kibao na upande wa simu kwa upande mmoja; kuingiza watawala wa pixel kwa uwekaji sahihi.

Ukurasa wa Tovuti na Vituo

Kila kampeni inaweza pia kuwa ukurasa wa kawaida wa bios na nambari za QR, mlolongo wa drip ya barua pepe kwa inaongoza zilizokamatwa, au rasimu moja ya click mtandao.

Usalama wa Biashara

Chapisha kufungia madirisha (vizazi vya bure), mabadiliko ya dharura ya kuacha-wote, idhini, uchaguzi wa ukaguzi na rollback toleo.

Je, ninahitaji kuongeza msimbo kwenye tovuti yangu?+

Hapana. Maendeleo ni kutolewa na OpsIQ widget sawa tayari umewekwa. kubuni, kuchapisha, kufanya.

Je, watu wa aina hii watauonaje uongozi wa juu na wa juu?+

Weka kofia za mzunguko (kwa kikao / kwa siku, au kuacha baada ya mtu kufunga, bonyeza au kubadilisha). defaults mbaya hutumiwa.

Nani anaweza kuchapisha?+

Uchapishaji, kutengeneza, kupiga kumbukumbu na kurudi nyuma ni mdogo kwa wamiliki wa nafasi za kazi na watendaji kamili. mwanachama yeyote wa timu anaweza kuunda na kubuni rasimu.

Ukuaji wa SEO

Kukuza Designer

Kukuza Designer ni mhariri wa kizuizi cha msikivu kwa kujenga, kupitia, kutafsiri na kuchapisha uzoefu wa kampeni.

Bidhaa ya Screen
Kukuza Designerdesigner kuchanganya canvas kuishi, kifaa previews, vitalu, vigezo vya ubinafsishaji, maoni na historia ya toleo.Kukuza DesignerNafasi ya KaziVIEWPORTDesktopUhariri wav12Hali ya dharuraRasimu yaMaisha ya kazi ya VIEWMfumo wa blockKichwa cha habari, vyombo vya habari na CTAEdith yaKutoa blockPunguzo na tarehe ya mwishoEdith yaBinafsi yaMawasiliano na kampeni variablesKamiliKuangalia kwa ajili yaMaoni na uthibitishoMapitio ya1BUILD BLOCKSBadilisha mipangilio ya kuishi2Precipital yaDesktop, kibao, simu ya mkononi3PUBLISHToleo la Tafsiri
designer kuchanganya canvas kuishi, kifaa previews, vitalu, vigezo vya ubinafsishaji, maoni na historia ya toleo.

Tumia vitalu kuandika uzoefu, preview kila mtazamo mkono na kuingiza vigezo kupitishwa ubinafsishaji. Mapitio ya maoni na AI-media kuthibitishwa kabla ya uzinduzi. Kuokoa inajenga matoleo hivyo kubuni uliopita inaweza kukaguliwa au kurejeshwa.

Ukuaji wa SEO

Kukuza templates za kukuza

Templates kutoa searchable, jumuishwa kuanzia nyumba ya sanaa kwa ajili ya kampeni Promotion Studio.

Bidhaa ya Screen
Kukuza templates za kukuzaNyumba ya sanaa ya template inachagua mipangilio ya malipo na hutumia rangi za brand ya workspace wakati template inakuwa rasimu.Kukuza templates za kukuzaNafasi ya KaziKwa hisani ya RaiaMwemaKubadilishaRESULTS24ya BRANDKutumika kwaMaisha ya kazi ya VIEWKutoa kwaMabadiliko ya haraka na CTATazamaMgeni rasmi akikaribishwaBanner na orodha ya faidaTazamaBidhaa ya uzinduziUshahidi, Uthibitisho na HesabuTazamaMaombi ya maombiUtafiti wa harakaTazama1FILTERJamii na kutafuta2Precipital yaKuangalia kwa ajili ya Design kamili3USEKuunda mradi wa Branded
Nyumba ya sanaa ya template inachagua mipangilio ya malipo na hutumia rangi za brand ya workspace wakati template inakuwa rasimu.

Tafuta au kuchuja kwa kategoria, pakia matokeo ya ziada, uhakiki uzoefu kamili, kisha chagua Kutumia templateKampeni mpya bado ni rasimu na inaweza kubadilishwa katika Promo Designer kabla ya kuchapishwa.

Ukuaji wa SEO

Kukuza analytics

analytics kukuza huunganisha hisia na bonyeza kwa uongofu, mazingira ya watazamaji, matokeo ya utendaji wa kontakt na kujifunza kampeni.

Bidhaa ya Screen
Kukuza analyticsUchambuzi wa kukuza unaonyesha utendaji wa kichwa cha habari, watazamaji na kusababisha kuvunjika, inaongoza matokeo ya mauzo ya nje na kontakt.Kukuza analyticsNafasi ya KaziIMPRESSIONS42.8kCTR ya6.4%CONVERSIONS814Maisha ya kazi ya VIEWNchi ya nchiUingereza · 31%Kuvunjika kwaUkurasa wa ukurasa/pricing · 22%Kuvunjika kwaTrigger yaMalengo ya · 44%Kuvunjika kwaHatua ya KuunganishaBidhaa zilizotengenezwa · 97% Mafanikio ya mafanikioMatokeo ya1Rahisi yaHisia za kubadilika2SLICEUkurasa, Nchi, Mfumo3LEARNTumia ufahamu
Uchambuzi wa kukuza unaonyesha utendaji wa kichwa cha habari, watazamaji na kusababisha kuvunjika, inaongoza matokeo ya mauzo ya nje na kontakt.

Kusoma hisia, click-kwa njia ya kiwango na uongofu pamoja. Break matokeo chini kwa nchi, ukurasa, trigger na kifaa; mauzo ya nje alitekwa inaongoza wakati muhimu. Matokeo Connector hatua kuonyesha kama kukuza ahadi ufuatiliaji kweli mbio. AI ufahamu na muhtasari wa kujifunza lazima kutibiwa kama dhana kuthibitisha, si ushahidi moja kwa moja.

Ukuaji wa SEO

Matangazo ya

Matangazo huchapisha ujumbe katika eneo la arifa ya widget na kulenga kwa hiari, ratiba na wito wa hatua.

Bidhaa ya Screen
Matangazo yaMhariri wa Matangazo ni pamoja na maudhui, CTA, watazamaji, sehemu, utawala wa ukurasa, tarehe za kazi na mtindo wa kuona.Matangazo yaNafasi ya KaziKazi3AUDIENCEUgawaji waUtii waJuli ya 22–29Maisha ya kazi ya VIEWKichwa cha jinaMipango ya kuhifadhiKamiliMaudhui ya MaudhuiUjumbe wa MarkdownKamiliCTA ya CTASoma taarifa kwa kinaChaguo laUtawala wa sheriaKuajiri kurasa · Wateja wenye kaziMalengo ya Target1WRITEMarkdown2MalengoMaoni, Sehemu, Ukurasa3Utii waWindows ya Active
Mhariri wa Matangazo ni pamoja na maudhui, CTA, watazamaji, sehemu, utawala wa ukurasa, tarehe za kazi na mtindo wa kuona.

Chagua wageni wote, wageni waliosainiwa au wageni wapya; chaguo kwa urahisi hupunguza watazamaji na sehemu ya kuwasiliana na kanuni ya ukurasa. Weka tarehe za kazi-kutoka / zisizofanya kazi na bendera yenye nguvu. presets ya mtindo wa Premium na uwasilishaji wa rangi lakini usichukue nafasi ya maudhui wazi.

Ukuaji wa SEO

Kampeni za kushinikiza

Kampeni za kushinikiza hutuma arifa za kivinjari kwa wageni waliojiandikisha baada ya kuondoka kwenye tovuti.

Bidhaa ya Screen
Kampeni za kushinikizaMwandishi wa kushinikiza anaonyesha usajili kufikia, maudhui, vyombo vya habari, vitendo, sheria za lengo na hali ya ratiba.Kampeni za kushinikizaNafasi ya KaziSUBSCRIBERS8,214Siku ya31.6kCLICK RATE5.8%Maisha ya kazi ya VIEWKichwa cha jinaGari yako inasubiriKamiliMwili wa MwiliKurejea leo kwa ajili ya bureKamiliCTA ya CTAUfunguzi wa gariKamiliRatiba ya ratibaKuwasilisha sasa au kwa mpangoRasimu ya1PREPARE PUSHJina la kikundi, icon2MalengoMaoni, Sehemu, Ukurasa3SENDSasa, mpango au mpango
Mwandishi wa kushinikiza anaonyesha usajili kufikia, maudhui, vyombo vya habari, vitendo, sheria za lengo na hali ya ratiba.

Piga funguo za Mtandao wa Push kwanza chini ya mipangilio ya Mtandao. Kampeni inaweza kujumuisha kichwa, mwili, icon, picha ya shujaa, beji, CTA na hadi vifungo viwili vya hatua; arifa inayoendelea inabaki mpaka mgeni aingiliane.

Lengo na watazamaji, sehemu ya kuwasiliana kwa hiari na utawala wa ukurasa. Hifadhi rasimu, ratiba yake au kutuma mara moja. Tumia usajili na metrics bonyeza ili kuhukumu kufikia. HTTPS na mfanyakazi wa huduma mwenyeji sahihi anahitajika kwenye maeneo yaliyoingia ya tatu; angalia Web Push kwenye tovuti za watu wengine.

Ukuaji wa SEO

Ujumbe wa Proactive

Ujumbe wa ufanisi unafikia moja kwa moja wakati tabia ya mgeni inafanana na utawala, kabla ya kuuliza. Unajenga kila mmoja kama kanuni na sehemu tatu: nini kinapaswa kutokea, wakati unapaswa moto, na mara ngapi. Kila kitu kinawasilishwa kupitia widget ya OpsIQ tayari kwenye tovuti yako.

Proactive ya
Ujumbe wa ProactiveMwandishi wa utawala wa ufanisi katika sehemu tatu: chagua hatua (chat, bendera, ziara, kushinikiza, barua pepe), kuongeza hali, na kuweka baridi ya mzunguko.Ujumbe wa ProactiveNafasi ya Kazi1 · Hatua zaUjumbe wa ChatBendera ya Volta ya JuuMzungukoPush up yaBarua pepe2 · Masharti yapage = /pricingUkurasa wa wakati » 20sKurudi kwa kurudi3 · Kiwango cha FrequencyMara moja kwa mkutanoHali ya1HatuaChat, bendera, barua pepe, kushinikiza ...2CONDITIONSUkurasa, Muda, alama, kurudi3Mara kwa maraKujiandikisha kwa ajili ya wageni
Kila utawala wa ufanisi ni uchaguzi tatu: nini kinatokea (chat, bendera, ziara, kushinikiza, barua pepe, webhook), wakati (makubaliano), na mara ngapi (baridi).

Sehemu tatu za utawala

1
Nini cha kufanya (kwa vitendo)

Onyesha Bubble ya kuzungumza au bendera ya ukurasa, kuanza Ziara Iliyoongozwa, tuma kushinikiza mtandao au barua pepe, peana idara, au moto ishara za wavuti. {{visitor_name}} Aidha, na {{page_title}} Kuwa na maadili ya kweli.

2
Wakati wa kupanda, moto lazima uwe mkali.

Narrow ambaye husababisha: ukurasa /URL, wakati kwenye ukurasa, kina cha kitabu, alama ya kuongoza, kurudi dhidi mpya, bila masharti, moto wa utawala kwa kila mgeni. Ongeza angalau moja ili kuilenga. Masharti yanachanganya na NA.

3
Mara ngapi (mara nyingi)

Weka baridi ili mtu huyo asivurugwe, kwa mfano mara moja kwa kikao au mara moja kila siku.

⚠️
Kazi ya kubadilisha "Kukimbia wakati / sheria za muda kwa saa" inakuwezesha vitendo vya upande wa seva (Email, kushinikiza, webhook, pangia) moto kwenye ratiba ya mawasiliano inayojulikana ambao sio sasa kwenye ukurasa, hivyo unaweza "kutuma barua pepe za moto" moja kwa moja. Inahitaji kukimbia OpsIQ n.
Je, ni moto wa milele kwa kila mtu?+

Tu kama wewe kuongeza hakuna hali. Ongeza angalau moja ya masharti (ukurasa, risasi alama, kurudi ...) ili kulenga wageni haki.

Je, ni jinsi gani hizi zinahusiana na safari za ndege na ndege?+

Wao kazi pamoja: utawala wa ufanisi unaweza kuanza Ziara Guided, na Mtiririko Chatbot inaweza kuwa yalisababisha kwa sheria ya proactive. Kuanza na moja chat ujumbe utawala, kisha safu wengine juu ya.

Ukuaji wa SEO

Chatbot ya mtiririko

Chatbot Hutiririka script mazungumzo ya matawi ndani ya widget yako chat (utaratibu, majibu ya maneno muhimu, njia za kuongozwa) na hakuna kificho. mtiririko ni seti ya hatua kushikamana (nodes): kuuliza swali, mgeni huchukua chaguo, na mtiririko unawaweka chini ya tawi vinavyolingana.

Jinsi ya kufanya kazi
Chatbot ya mtiririkoTurutu ya mtiririko: matawi ya salamu katika vifungo vitatu vya chaguo, kila moja ikiongoza kwa hatua inayofuata, angalia utaratibu, au peana mkono kwa mwanadamu.Salamu kwa Mhe.Jinsi ya kusaidia?Fuata maagizo yanguMaswali ya BillingKuzungumza na mtuAngalia kwa amri→Wakala wa BinadamuTriggers: Salamu · Keyword · Mwongozo · Baada ya maelezo · On-chat-end
Chatbot ya mtiririko

Kuingiza kwenye · Wakati wa kutumia

Tumia njia ya mkato

Wakati njia ni kutabirika na unataka kuwa sawa kila wakati: hatua booking, anarudi mchawi, "mpango gani?" kuchagua, kukusanya barua pepe kabla handoff. Flows kamwe improvise.

Tumia AI

Wakati maswali ni wazi-kuliko, "je, hii kazi na kuanzisha yangu?". Wateja Chat AI majibu kutoka ujuzi wako mafunzo. mtiririko unaweza mkono mbali na AI (au binadamu) katika hatua yoyote.

Vichochezi

Salamu kwa Mhe.

Inaendesha kama ujumbe wa ufunguzi wakati mgeni kwanza kufungua chat.

Maneno muhimu

Inaendesha wakati mgeni anaunda neno uliloorodhesha (kwa mfano marejesho, bei, kufuta).

Baada ya muda wa ziada / baada ya kuchelewa

Kuanza mara moja maelezo ya mawasiliano ni pamoja, au muda uliowekwa katika mazungumzo.

Mwisho wa mazungumzo / Proactive

Inaendesha kama mazungumzo yanafunga (kwa mfano rating), au huanza na utawala wa Ujumbe wa Proactive.

Kujenga moja katika hatua nne

1
Kujenga mtiririko wa

Bonyeza Mto Mpya, jina lake, chagua aina ya kuchochea (na maneno muhimu ikiwa ni neno la msingi), kuokoa. Inaanza kuzima.

2
Kufungua milango ya

Bonyeza Edit Canvas. mjenzi wa kuona ambapo unaongeza hatua (ujumbe, maswali na vifungo, matawi) na kuunganisha.

3
Ongeza vidole na mkono mmoja

Kwa kila chaguo, vuta tawi kwenye hatua inayofuata. Njia za Mwisho kwa kutatua, kukabidhi AI, au kuhamisha binadamu.

4
kuwezesha

Bonyeza Enable. mtiririko inakwenda kuishi katika widget yako mara moja. Disable wakati wowote bila kupoteza kubuni.

Je, ni lini barabara hizo zitajengwa upya?+

Wanaendesha upande kwa upande. Tumia mtiririko wa njia za kutabirika na AI kwa maswali yaliyofunguliwa; mtiririko unaweza kila wakati kupeana ama.

Ukuaji wa SEO

Ziara ya Ziara

Guided Tours ni hatua kwa hatua walkthroughs kwamba pointi katika sehemu ya ukurasa wako na bubbles hotuba na mwanga, kuongoza mgeni kupitia onboarding au kipengele kipya. Wao ni themed kabisa na kujengwa katika mchoraji kuona na preview hai. ziara anaendesha tu wakati ni alama Active.

Jinsi ya kufanya kazi
Ziara ya ZiaraUkurasa uliofifia na pete ya uangalizi karibu na kifungo cha Ongeza-deal na hotuba ya maandishi ya Bubble kusoma Step 1 Kwa upande wa 4 Bonyeza kifungo cha pili.+ Ongeza MkatabaHatua ya hatua 1 Kwa upande wa 4Kujenga biashara yako ya kwanzaBonyeza hapa ili kuongeza mpango kwenye bomba lako.Baada ya→
Ziara ya Ziara

Jinsi ya kutengeneza ramani

Hatua za hatua

Kila hatua inalenga kipengele na inaonyesha bubbles na maandishi yako. Ongeza kama wengi kuacha kama walkthrough mahitaji na amri yao.

Mandhari ya kwanza na mandhari

Kuanza kutoka kabla au kubuni Bubble yako mwenyewe (colours, gradients, uangalizi) na hakikisho la kuishi juu ya haki.

Trigger ya

Chaguo la kuunganisha Utawala wa Proactive ili ziara ya auto-starts wakati huo utawala moto (kwa mfano kutembelea dashibodi ya mgeni wa kurudi).

Kazi ya Toggle

Ziara ni haki ya kukimbia tu wakati Active ni ticked. Untick kuchukua chini bila kufuta.

Kujenga moja katika hatua nne

1
Ziara mpya ya

Bonyeza New Guided Tour, jina lake, na kwa hiari kuunganisha Kanuni Proactive hivyo huanza moja kwa moja.

2
Kuongeza hatua

Ongeza kila kuacha: chagua kipengele kinachoonyesha na kuandika maandishi ya Bubble. rekebisha hadi njia itiririka.

3
Kuumba kwa ajili ya

Chagua preset au style Bubble mwenyewe. preview ya kuishi inaonyesha hasa nini wageni kuona.

4
Kufanya kazi

Ziara inaweza sasa kukimbia, kwa kuchochea yake mwenyewe, au kuanza na utawala wa Ujumbe wa Proactive.

Jinsi ya kuanza safari?+

Kwa kuchochea kwao wenyewe, au kupitia hatua ya "Safari ya Ujumbe wa Proactive", kwa hivyo unaamua ni wageni gani wanaoona ziara na wakati.

Ukuaji wa SEO

Malengo ya Kubadilisha

Malengo ya uongofu hugeuka shughuli unayojali (tukio la mtandao wa inbound, ujumbe wa mazungumzo, azimio la tiketi) katika uongofu uliorekodiwa na ugawaji kamili. Wakati shughuli zinawaka moto, OpsIQ inaingiza ubadilishaji dhidi ya kuwasiliana na kumfunga nyuma kwenye kampeni, sehemu na vyanzo ambavyo viliongoza huko.

Jinsi ya kufanya kazi
Malengo ya KubadilishaMtiririko wa lengo: tukio la malipo. succeed webhook linapata uongofu uliorekodiwa "kununua" thamani ya $49, unaohusishwa na chanzo chake na kampeni, na chips za mwanzo wa haraka hapo juu.Mwanzo wa harakaStripeKununua kununuaDemo ya bureJarida la Usajilipayment.succeededMtandao wa InboundKubadilisha“Uchawi” · $49KuwajibikaChanzo · Kampeni
Malengo ya Kubadilisha

Kufafanua malengo katika hatua tatu

1
Chagua shughuli za trigger

Chagua aina ya shughuli ambayo inahesabu kama uongofu, au kutumia preset ya haraka-kuanza, ununuzi wa Stripe, Demo iliyokatwa, usajili wa jarida au usajili ulianza.

2
jina lake na kuweka thamani ya

Kutoa uongofu jina (kununua, demo_booked, signup) na kwa hiari thamani ya kudumu na dirisha la ugawaji.

3
Kuokoa

Kuokoa na kuwezesha. Kuanzia wakati huo, wakati shughuli zote zina moto, OpsIQ inarekodi uongofu dhidi ya kuwasiliana na mchango kwa kugusa hapo awali.

Malengo tayari yameunganishwa kwenye mtandao wa ndani: lengo lolote ambalo husababisha mechi za moto wa aina ya tukio linaloingia moja kwa moja wakati eneo la tukio. Tumia ukurasa wa Inbound Webhooks kuunganisha Stripe, Calendly au mfumo wowote ambao unaweza POST JSON.
Ni nini kinachoweza kuwa mabadiliko?+

Shughuli yoyote iliyorekodiwa: tukio la mtandao wa inbound (kulipa. succeed), kukamata barua pepe ya mazungumzo, azimio la tiketi, chochote kwenye ratiba ya kuwasiliana.

Uchambuzi

Dashibodi za kawaida

Dashibodi za kawaida zinakuwezesha kujenga maoni yako mwenyewe ya metrics ambayo ni muhimu, badala ya kutegemea tu kwenye muhtasari wa kiwango. Ongeza vilivyoandikwa unayotaka, kokota na uziweke katika mpangilio unaopenda, uhifadhi, na uishiriki na timu yako.

Dashibodi za kawaida
Dashibodi za kawaidaMjenzi wa dashibodi na KPI na vigae vya widget ya chati, eneo la kushuka kwa dashed, na kifungo cha Ongeza-widget.Dashibodi za kawaidaNafasi ya KaziDashibodi yangu ya dashibodiOngeza widgetWaandishi wa2,481Kugeuka$8.2k yaUsafiri wa UmmaBonyeza hapa kupata widgetViwango vya juu/pricing/docs/signup1ADD WIDGETSPick metrics & chati za2ARRANGEDrag & Resume ya3KuwaKuwa na timu yako
Kujenga bodi yako mwenyewe: kuongeza KPI, chati na vilivyoandikwa orodha, Drag na resize yao katika mpangilio unataka, kisha kushiriki na timu.

Kujenga moja katika hatua tatu

1
Ongeza widgets

Bonyeza Ongeza Widget na uchague metric au chati unayotaka kufuatilia. Kurudia kwa kila kitu unachotaka kwenye ubao.

2
Kutayarisha mpangilio

Drag widgets reposition na kuvuta makali yao kwa resize. KPIs katika juu, chati chini. Chochote kinachosoma bora.

3
Hifadhi na Kushiriki

Hifadhi dashibodi na ushiriki na timu yako ili kila mtu aangalie nambari sawa.

Weka bodi tofauti kwa kazi tofauti (bodi ya "kwa mtazamo wa kila siku" na hesabu za kuishi, na bodi ya "uchunguzi wa mwezi" na chati za mwenendo) hivyo kila mmoja anakaa kuzingatia.
Ukuaji wa SEO

Kampeni za

Uhamiaji ni OpsIQ ya ya1:1na injini ya barua pepe wingi: kuandika ujumbe binafsi au kuendesha kampeni kwa sehemu CRM, na kutambua jibu, udhibiti wa wakati wa kutuma, kufuatilia wazi / bonyeza, pixel ya kufuatilia na unsubscribe moja-click. Ni kibali-gated na CAN-SPAM / CASL kulingana.

Uendelezaji wa
Kampeni zaScreen Outreach na Composer / Campaigns / Vituo vya tabo na meza ya kampeni inayoonyesha kutumwa, kiwango cha wazi na majibu.Uendelezaji waNafasi ya KaziKampeni zaKulinganishaTemplates zaMajibu ya majibuKwa hisani ya RaiaMwemaSiku yaFUNGWANIKwa mara yaJarida la mwezi Juni1,20048%7%Kesi ya ufuatiliaji34062%14%Ushindi wa nyuma82039%5%Kugundua autostops kufuatilia · bonyeza moja unsubscribe juu ya kila kutuma11:1 & BULKKulinganisha au kampeni2TRACKEDFungua, clicks, majibu3COMPLIANTUendelezaji wa Muungano uliojengwa katika
Engine Make: Send1:1Au kukimbia kampeni kwa sehemu, kufuatilia kufungua na majibu, na kukaa kulingana na kujengwa katika unsubscribe na kutambua jibu.

4 Vitabu vya

Kulinganisha

Andika barua ya kibinafsi1:1email kwa ajili ya {tokens} Kwa mawasiliano na CRM.

Kampeni za

Tuma kwenye sehemu ya CRM, iliyopangwa au sasa, na kofia na udhibiti wa wakati.

Templates za

Templates za ujumbe wa kurudia kwa ufikiaji wa mara kwa mara.

Majibu ya majibu

Jibu kutambua rekodi majibu na autostops kufuatilia kwa mtu yeyote ambaye alijibu.

Jinsi kampeni inavyoendeshwa

1
Chagua wasikilizaji

Chagua sehemu ya CRM (au kupakia orodha). Ukandamizaji na idhini hutumiwa moja kwa moja.

2
Kukubaliana

Andika ujumbe na ishara za ubinafsishaji; preview dhidi ya mawasiliano halisi.

3
Orodha ya barua pepe na kutuma

Tuma sasa au wakati bora. rekodi ya kufuatilia pixel inafungua; bonyeza na majibu yanahusishwa.

Kufikia ni idhini- na ukandamizaji-kusimamiwa, inajumuisha kujiandikisha moja kwa kila kutuma, na ifuatavyo majibu ya CAN-SPAM / CASL. moja kwa moja kuacha ufuatiliaji zaidi.
Uchambuzi

Taarifa zilizoandaliwa

Imeandaliwa Ripoti barua pepe meta iliyochaguliwa kwa wapokeaji waliochaguliwa kwenye ratiba (kila siku, kila wiki au kila mwezi) kama printable, nyeupe-label PDF Weka mara moja na ripoti inaenea kwenye kikasha moja kwa moja kupitia OpsIQ ya cron.

Taarifa zilizoandaliwa
Taarifa zilizoandaliwaScreen iliyopangwa-ripoti: meza ya ripoti na ratiba yao, wapokeaji na wakati wa mwisho wa kutuma, pamoja na kifungo cha taarifa ya Save.Taarifa zilizoandaliwaNafasi ya KaziTaarifa zilizoandaliwaRipoti ya SaveripotiUtii waWapokeajiMwisho wa sikuUsafiri wa kila wikiJumapili 9:00[email protected]2 iliyopitaRipoti ya Wateja wa SEOMwezi wa Mwezi[email protected]Juni 1Muhtasari wa MauzoKila siku[email protected]todayKuchukuliwa kama White-label PDF Kwa njia ya OpsIQ ya wa1AUTOMATEDKila siku · kila wiki · kila mwezi2Nyeupe-labelPDF Kwa wateja3WapokeajiKujiandikisha kwenye ratiba
Weka ripoti mara moja (iliyopangwa, safu, ratiba, wapokeaji) OpsIQ Barua ya White-label PDF moja kwa moja kwenye akaunti yako.

Kuanzisha Ripoti

1
Chagua nini cha kutuma

Chagua seti ya metric (traffic, SEO, mauzo, msaada ...) na safu ya tarehe.

2
Ratiba ya programu na wapokeaji

Kila siku, kila wiki au kila mwezi, wakati unapochagua, kwa wapokeaji mmoja au zaidi wa barua pepe.

3
Kuokoa

Ripoti hiyo inazalisha na barua pepe yenyewe kwenye ratiba, hakuna hatua ya mwongozo.

💡
Ripoti zilizopangwa kupitia kwa | OpsIQ cron, ikiwa ripoti haipatikani, kuthibitisha cron inaendesha (angalia Cron na automatisering).
Faragha ya faragha

Usajili na ufuatiliaji

Ukurasa wa faragha na ufuatiliaji ni mahali moja ya kuonyesha mkaguzi unayeshughulikia data binafsi kwa uwajibikaji: idhini ya msimamizi, logi ya ufikiaji wa admin, makazi yako ya data na sera ya uhifadhi, na tayari-kwa-print DPA, katika mtazamo mmoja wa tabbed.

Usajili na ufuatiliaji
Usajili na ufuatiliajiScreen ya faragha na ufuatiliaji: tabo kwa ajili ya idhini ledger, kuingia logi, makazi na DPA, pamoja na meza ya kibali cha misaada na kufutwa kwa channel.Uingiliaji wa faragha na ufuatiliajiNafasi ya KaziRuhusa ya KukubaliwaUpatikanaji wa logiUwakilishi waDPAMawasiliano ya simuCharles KitwangaHatuaDhihirisho la[email protected]barua pepeKutolewa kwaJuni 12[email protected]pushKurudishwa kwaJuni 10[email protected]marketingKutolewa kwaJuni 9Uthibitisho wa kutafuta kila ruzuku ya idhini na kurejeshwa, kwa njia ya channel1Mwongozo wa LEDUshahidi wa kila tuzo2ACCESS LOGNani aliyetumia data3DPATemplate ya bure
Screen moja ya ukaguzi: kiambatanisho cha idhini kinachotafutwa ( Wahamiaji / wanaopokea kwa njia ya kituo), logi ya upatikanaji wa nani aliyegusa data, makazi / mipangilio ya kurejesha, na inayoweza kuchapishwa DPA.

4 Vitabu vya

Ruhusa ya Kukubaliwa

Rekodi ya kupatikana kwa kila ruzuku ya idhini na kufuta, kwa kuwasiliana, channel (Email, kushinikiza, SMS, katika-widget), hatua, chanzo na tarehe. Uthibitisho wako wa mawasiliano walikubaliana (au kujiondoa).

Upatikanaji wa logi

Ambao kwenye timu yako kutazamwa, kuhaririwa, nje, kufutwa au ujumbe wa data ya mawasiliano, na admin, kuwasiliana, hatua, sababu alisema na IP hasa nini mdhibiti anauliza.

Uhifadhi na uhifadhi

Kutangaza ambapo data ya workspace hii anaishi, kuweka ni siku ngapi shughuli za safu zimehifadhiwa (0 = milele), na kurekodi mtawala wako wa data na DPO.

DPA Template ya template

Kuongeza kwa Usindikaji wa Data inayoweza kuchapishwa ambayo inajaza mtawala wako, anwani, DPO, makazi na uhifadhi. Print au kuhifadhi kama PDF.

Faragha & Utekelezaji jozi na Cookie idhini studio (ambayo hukusanya kibali) na ukurasa wa nje (ambayo hutoa nakala ya data kwa ajili ya DSAR). Angalia pia Cron na automatisering kwa ajili nightly kuhifadhi kusafisha.
Viunganishi

Kuunganisha majukwaa yako

Kuunganisha Link OpsIQ kwa majukwaa ya nje: maduka ya e-biashara, mifumo ya bili, wasindikaji wa malipo, watoa barua pepe, na desturi APIs Mara baada ya kushikamana, AI inaweza kuangalia amri, data ya wateja, usajili, na zaidi, na kuchukua hatua kwa idhini yako.

Jinsi ya kufanya kazi
Kuunganisha HubOpsIQ msingi kushikamana na WHMCS, Shopify, Stripe, WooCommerce, SendGrid na Google Biashara Profile, kila moja kuonyesha hali iliyounganishwa.WHMCSShopifyStripeWooCommerceSendGridGoogle ya BPOpsIQMsingi1PLUG IN25+ kabla ya kujengwa connectors2AI CONTEXTData ya kweli3ACTIONSFanya hivyo kwa idhini yako
Viunganishi

Meli hizo kwa pamojaOpsIQ

Hizi ni sasa wakati wewe kufunga na haja tu ya sifa zao.

WHMCS

Billing ya

Malipo ya mwenyeji wa wavuti: wateja, huduma, tiketi, ankara, vikoa, seva.

Shopify

Biashara ya E-commerce

E-biashara: maagizo, wateja, bidhaa, hesabu, malipo, webhooks.

WooCommerce

Biashara ya E-commerce

WordPress e-biashara: maagizo, wateja, bidhaa, kuponi, usafirishaji.

WordPress

CMS CMS

Maudhui na watumiaji kwenye AWordPressTovuti ya.

Square ya mraba

Malipo ya

Malipo na hatua ya kuuza: maagizo, wateja, orodha.

osCommerce

Biashara ya E-commerce

Biashara ya E-biashara: maagizo, wateja, bidhaa.

Botble Hoteli

Bridge Bridge ya Bridge Bridge

Tovuti ya hoteli ya Botble CMS kupitia sainiOpsIQ-Kusimamia utekelezaji wa kumbukumbu kwa jukwaa bila yaAPI.

Zendesk

Msaada wa msaada

Helpdesk: tiketi, watumiaji, mashirika, maoni.

Maelezo ya Biashara ya Google

Masoko ya masoko

Biashara ya ndani: kitaalam, machapisho, Q & A, ufahamu. Tumia OAuth

Kalenda ya Google

Uzalishaji wa Bidhaa

Matukio na matukio. matumizi yaOAuth.

GmailAidha, naIMAP

Barua pepe

Barua pepe: barua ya inbound na outbound, anwani-kitabu sync.

SendGrid

Barua pepe

Utoaji wa barua pepe: tuma barua pepe na kusimamia templates.

Mailgungun

Barua pepe

Utoaji wa barua pepe: tuma barua pepe kupitia Mailgun.

SlackTelegram, LINE, X DM

Ujumbe wa

Njia za kusambaza kwa mazungumzo ya ndani na nje.

Njia za Meta

Ujumbe wa

Facebook Messenger, Instagram DM na WhatsApp.

Mtandao wa Intelligence (GA4 Utafutaji wa Console)

Uchambuzi

Analytics na data ya utafutaji kwa ajili ya SEO Suite ya.

Uendelezaji wa tovuti na CRM Uwekezaji wa nje

CRM

Uendelezaji wa kampuni na uingizaji wa wateja wengi.

Inapatikana kutoka kwenye soko

Hizi ni vifurushi zilizochapishwa, sio sehemu ya kufunga. Weka moja kutoka kwa Waunganishaji, Soko la soko na imenakiliwa kwenye folda ya waunganisho wa kuishi, baada ya hapo inafanya kazi sawa na zile zilizo juu.

Stripe

Soko la

Malipo: mashtaka, wateja, ankara, usajili, malipo, migogoro.

BigCommerce

Soko la

E-biashara: maagizo, wateja, bidhaa, makundi, chapa.

Magento ya 2

Soko la

E-biashara: maagizo, wateja, bidhaa, makundi, hesabu.

PrestaShop

Soko la

E-biashara: maagizo, wateja, bidhaa, sheria za gari, flygbolag.

OpenCart

Soko la

Biashara ya E-biashara: maagizo, wateja, bidhaa, makundi.

Amazon SES, Postmark, Resend, Orodha ya bidhaa

Soko la

Uwasilishaji wa barua pepe ya biashara.

Jiraya la linear

Soko la

ya uchunguzi na ufuatiliaji wa mradi.

Zoom, Microsoft Kalenda, Outlook Barua

Soko la

Mikutano, kalenda na barua.

DocuSign, Apollo, SerpApi, Google Analytics

Soko la

Ishara, matarajio, data ya utafutaji na uchambuzi.

WebflowWix, Squarespace

Soko la

majukwaa ya tovuti.

💡
Orodha ya kontakt inakwenda kama vifurushi vimechapishwa. orodha ya mamlaka kwa ajili ya kufunga yako ni ukurasa wa Waunganishaji: kilichoorodheshwa kuna kile ambacho wakati wa kukimbia uligundua, na tabo la Soko linaonyesha nini unaweza kuongeza.

Kuunganisha kontakt

1
Nenda kwa waunganishaji

Kuhimiza kuunganisha kwenye ubao wa admin.

2
Kupata kontakt

Vinjari orodha au search. Waunganishaji ni kundi na jamii.

3
kuwezesha

Bonyeza kiunganishi na toggle Enable.

4
Kuingia kwa sifa

Weka katika maeneo yaliyohitajika: API Kwa maneno mengine, URL Kila kontakt ina mahitaji maalum yaliyowekwa katika jopo lake la mipangilio.

5
Uchunguzi wa uhusiano

Bonyeza "Uunganisho wa haraka." Matokeo ya kijani inamaanisha kontakt inaweza kufikia jukwaa la nje. matokeo nyekundu yanaonyesha kosa.

6
Maelezo ya mchezo

Chagua ambayo makala ili kuwezesha: ujuzi sync, webhook sync , vitendo vya AI. Sio wote waunganisho wanaunga mkono vipengele vyote.

Nini cha kufanya na interface yako

Kwa muktadha

AI inaweza kuangalia data ya wateja, maagizo, usajili, na zaidi kupitia kiunganishi. Wakati mteja anaongea, AI ina data halisi ya jukwaa la kumbukumbu.

(i) Mazingira ya Muungano (Conventioners

Munganisho wako wa ContextProvider feeds tiketi-AI muhtasari wa akaunti ya kusoma tu ya mmiliki wa tikiti. customer_id Kama ni hivyo, basi, kwa kutumia tiketi ya ndege, ambapo bendera ya ctx customer_trust_email Ni kweli, angalia maelezo ya ziada customer_email (Mtumiaji wa tiketi kuthibitishwa) majukwaa ya mbali yanaonyesha /context/customer-by-email Mwisho wa mwisho na kontakt inaita. Hii ndiyo inafanya AI quote usawa halisi / sauti badala ya kusema "tafadhali ingia." heshima toggles data-class operator (customer_sections, customer_allow_credit) na kuendelea kusoma kwa makini, kamwe kutoa siri.

Mwongozo wa Wateja (Waandishi wa Kuunganisha)

Kampuni ya IdentityProvider inafungua milango mitatu ya tiketi za kimataifa: lookupCustomerById() (Picha ya pamoja), lookupCustomerServices() (Makala ya Bidhaa na Huduma) listCustomers($query,$limit): "Mteja wa utafutaji au aina ya barua pepe" picker kwenye fomu ya asili ya Compose-NewTicket. kurudi safu za {id, external_id, name, email, company, phone, platform, platform_label}. Kanuni ya mbali: Ikiwa wateja wako wanaishi kwenye database nyingine au huduma, walete juu ya jukwaa lako API Ndani ya mbinu hizi, kamwe kusoma meza nyingine moja kwa moja (katika mfumo wa) OpsIQ DB wao ni placeholders tupu, ambayo ni kwa nini kusoma ndani anarudi picker tupu). Lango njia ya kijijini juu yako configured API URL; endelea kusoma hapa kama vile kuanguka kwaDB sawa.

Tiketi za barua pepe, kugundua & routing (waandishi wa kuunganishwa)

Wakati barua pepe inbound inakuwa tiketi ya asili, OpsIQ anagundua mtumaji kwa kupiga simu lookupCustomerById(0, ['email'=>$sender]) katika kila kontakt; mechi ya kwanza "mwenyewe" mteja na yake platform Slugs hupigwa kwenye uso ticket.created Tukio kama hilo _pipe_owner_platform (Sauti ya Mgeni).WHMCS Email ya mteja kufungua tiketi katika WHMCS (WHMCS Kwa mfano, mtu mwenye akili timamu ni kama mtu asiye na akili. Ikiwa kontakt yako inaangalia tiketi za asili kwenye jukwaa lake mwenyeweyako ticket.created Mhudumu lazima afungue mlango kwa hili: if (array_key_exists('_pipe_owner_platform',$payload) && $payload['_pipe_owner_platform'] !== '<your-slug>') return;Ufunguo huo haupo kwenye tiketi zisizo za kawaida (chat/manual /AI), hivyo kioo kama hapo awali. udhibiti wa kila sehemu huishi chini ya Timu na Idara → Tiketi za wazi kupitia barua pepe (Mtu yeyote / Wateja tu / Off).

Hatua za

AI inaweza kufanya vitendo kupitia kiunganishi: kuunda tiketi, maagizo ya sasisho, kufuta usajili, wote kwa idhini yako kupitia tabaka la Trust.

Maarifa ya ujuzi

Waunganishaji wanachangia vipengele vya ujuzi maalum wa jukwaa kwa AI. Shopify · Kuongeza matatizo ya e-biashara; WHMCS Mtumiaji anaongeza ujuzi wa mwenyeji.

Uagizaji wa msingi wa ujuzi (waandishi wa kuunganishwa)

Ikiwa jukwaa lako linashikilia msingi wa ujuzi, tangaza kb_capabilities block katika settings.json (Tabia ya aina kb_source) na kiunganishi chako kinaonekana katika mhariri wa Kituo cha Msaada Kuagiza KB → Import kutoka programu zilizounganishwa kushuka wakati wowote ni kuwezeshwa na configured katika nafasi ya kazi. Ni declarative, hakuna njia ya kutekeleza: jina kujengwa-katika adapter (zendesk Kituo cha Msaada wa Barabara API Kwa hivyo, au crawl Kwa ajili ya tovuti yoyote ya kb (au base_template Kama vile https://{subdomain}.zendesk.com, ambayo OpsIQ inajaza kutoka kwa mipangilio ya kuhifadhiwa ya kontakt yako. Credentials kamwe kuondoka seva; kivinjari tu hutuma mzigo wa kiunganishi. Ili kusaidia jukwaa jipya, ongeza opsiq_kb_<platform>_manifest() Kuiandika na kuitaja kwa jina kamili. connectors/PLATFORM_CONNECTORS.md §5.

Webhooks

Baadhi ya waunganisho hujiandikisha webhooks na jukwaa la nje kwa arifa za tukio halisi (amri mpya, sasisho za tiketi, nk).

Ufuatiliaji wa Mauzo

Waunganishaji wa biashara ya E-biashara hulisha data ya mapato katika dashibodi ya Mauzo kwa ajili ya ugawaji na analytics.

💡
Waunganishaji ni workspace-scoped. Kila nafasi ya kazi inaweza kuwa na viunganisho tofauti kuwezeshwa na sifa tofauti.WHMCS Eneo la kazi linatumia WHMCS Mawasiliano; a Shopify Eneo la kazi linatumia Shopify ya mawasiliano.
Je, ninaweza kutumia njia nyingi za mawasiliano kwa wakati mmoja?+

Ndiyo, unaweza kuwa na Shopify kwa amri na Stripe kwa malipo katika nafasi moja ya kazi. AI huunganisha data kutoka kwa viunganisho vyote vilivyowezeshwa.

Nini ikiwa ukurasa wangu haukuandikwa?+

Tumia Mjenzi wa Kuunganisha ili kuunda kiunganishi cha desturi kwa jukwaa lolote na REST API. Au angalia Soko la viunganisho vya kujengwa kwa jamii.

Wafanyakazi wa kampuni ya kufanya kazi kwa kujitegemea OpsIQ?+

Ndio, Waunganishaji hufanya kazi sawa katika matoleo ya wingu na ya kujitegemea.

Viunganishi

Mauzo na mkataba wa bili

Kila kontakt ya biashara hutumia mkataba wa tukio la jukwaa-neutral. WHMCS ni utekelezaji wa kumbukumbu, lakini Daraja la SaaS, maduka, watoa malipo, viunganisho vya soko na vifurushi vya Wajenzi wa Connector lazima kutii sheria sawa.

Nini kila mfanyabiashara wa biashara anapaswa kuchapisha

Moja ya viongozi wa

Publish realised economic events to opsiq_sales_events through CommerceEventRegistry::normalize(). Do not build a connector-specific Sales table or make core analytics query a remote platform directly.

Utambulisho wa chanzo

Jukwaa ni kontakt ya usajili wa slug, kama vile whmcs, shopify Au opsiq_saas. trafiki_source ina uthibitisho wa upatikanaji wakati hutolewa; vinginevyo tumia slug sawa kama kurudi nyuma. vitambulisho vya Hifadhi, sio lebo za kuonyesha. OpsIQ Inabadilisha jina la kontakt katika UI.

Ukadiriaji wa

event_id lazima deterministic. Map angalau moja immutable order_ref, invoice_ref au subscription_ref hivyo webhook retries na backfills update tukio hilo badala ya kujenga mauzo duplicate. service_ref inatambua bidhaa walioathirika au mfano huduma wakati mmoja ipo.

Chanzo cha Timestamp

Tukio la tukio ni malipo au wakati wa kiuchumi ulioripotiwa na jukwaa la chanzo. Kamwe kuchukua nafasi ya tarehe za malipo ya kihistoria na wakati wa kuagiza.

Fedha na FX

Tuma kiasi cha chanzo na sarafu ya ISO ya tatu. Ikiwa mpangilio wa kontakt unawezesha uongofu wa OpsIQ FX, taarifa zinabadilisha fedha ya kuripoti nafasi; vinginevyo ripoti huhifadhi kuhifadhi au sarafu ya jukwaa la malipo. Msimbo wa Connector lazima usihifadhi sarafu ya taarifa au kiwango cha ubadilishaji.

Maisha ya msingi ya ushahidi

Tumia mpya, upya, kuboresha, marejesho, mikopo au haijulikani. Kuainisha kutoka kwa sababu ya ankara, usajili au uhusiano wa huduma, aina ya simu, au shamba lingine la chanzo cha mamlaka. Ununuzi wa kurudia na mteja huyo sio upya moja kwa moja.

Mipaka ya Mauzo

Tu chanya kulipwa mpya, upya, kuboresha, au halali haijulikani risiti biashara ni katika mauzo & conversions. Refunds ni taarifa kwa refund na uchambuzi wa wavu-revenue. akaunti mikopo, mkoba juu-ups, ishara ya juu-up na Add Funds kubaki billing-ledger matukio na kamwe kuhesabu kama mauzo, uongofu, kiasi cha utaratibu, au mapato ya mauzo.

CRM ni tofauti kwa ajili ya

Mikataba ya CRM inawakilisha bomba na shughuli za mpango. Wao si mauzo ya jukwaa la biashara isipokuwa kama bili iliyounganishwa au jukwaa la kuhifadhi hutoa utaratibu uliolipwa au ankara kupitia mkataba huu.

Kila ishara ya malipo kufungua mstari

Wakati jukwaa linatuma uthibitisho kadhaa wa malipo moja (yanayolipwa, ili kulipwa, shughuli iliyoongezwa, malipo kukamilika) yoyote kati yao inaweza kufungua mstari wa gurudumu mara tu jukwaa linathibitisha uuzaji unalipwa; alama ya kuuza inaanguka kwa ndugu katika mstari mmoja.

Utaratibu wa Usajili (Contract) 2.3)

A connector whose platform can list completed sales declares sales_reconciliation and implements SalesReconciliationInterface::reconcileSales(). Core re-reads the platform list on a schedule (once per workspace interval, bounded, cursored) through the same idempotent writer, so a dropped webhook cannot lose revenue. Conformance fails a package that can list history but does not reconcile. The Connector Builder derives the capability from the sales backfill action.

Matarajio ya

Opsiq_conversions na muhtasari wa dashibodi ni makadirio ya utangamano yaliyojengwa kutoka kwa mwongozaji. Waunganishaji hawapaswi kutibu mradi kama chanzo cha kifedha cha ukweli. Marekebisho ya Mkataba yanaweza kutathmini tena safu zilizopatikana bila kufuta historia ya msingi ya kulipa.

Mlango wa mbali

Munganisho wa mbali anasoma jukwaa lake kupitia usanidi uliothibitishwa API. Haipaswi kutegemea meza za database ya seva moja. Tovuti halisi ya kikoa iliyohakikishiwa hutolewa na Uunganishaji na lazima itumiwe kwa kila mwandishi kuandika na backfill. Kazi au upeo wa kikundi ni usomaji wa wakati tu; haipaswi kupanua umiliki wa tukio lililohifadhiwa.

Mfano wa malipo ya Canonical

Matukio ya kawaida ya biashara
{
  "event_id": "acme_store:invoice:INV-1042",
  "event_name": "invoice.paid",
  "platform": "acme_store",
  "order_ref": "ORDER-884",
  "invoice_ref": "INV-1042",
  "subscription_ref": "SUB-28",
  "service_ref": "SERVICE-91",
  "status": "paid",
  "lifecycle_type": "renewal",
  "amount": 129.00,
  "currency": "USD",
  "traffic_source": "acme_store",
  "occurred_at": "2026-07-23 08:30:27"
}

Kuunganisha Builder

Wakati Mauzo na bili zinawezeshwa katika Connector Builder, kiasi cha ramani, sarafu, hali ya chanzo na tarehe ya chanzo, pamoja na angalau amri moja, ankara au kumbukumbu ya usajili. Ramani lifecycle_type wakati API inaonyesha ushahidi wa mamlaka wa mzunguko wa maisha. SalesIngest zinazozalishwa hupita kila mstari kupitia normalizer sawa ya Biashara ya kawaida inayotumiwa na viunganisho vya kujengwa na soko.

⚠️
Mikopo na Ongeza Fedha ni kwa makusudi kuhifadhiwa kwa ajili ya historia bili, mazingira ya usawa wa wateja na uchambuzi wa ledger. Kuwafukuza kutoka Mauzo haina kufuta yao; inawazuia tu kutoka inflating utendaji wa biashara.

Lifecycle_type huamua nini inakuwa mpango wa CRM

lifecycle_type Sio lebo ya uchambuzi. OpsIQ inasoma kuamua ikiwa uuzaji huingia bomba la CRM, kwa hivyo kila kontakt wa mauzo inafanya uamuzi wa bomba ikiwa inakusudia au la.

mpya

Kukamilisha mkataba wa biashara (New Deal).

Uboreshaji, uboreshaji

Hakuna mpango mpya wa biashara - upyaji hubadilisha kwenye kasi tofauti ya uwezekano na kuchanganya yao hupotosha utabiri wote.

Malipo ya dhamana

Kamwe kufungua mpango, katika hali yoyote, fedha kurudi kwa mteja si kushinda.

Kufukuzwa / haijulikani

Mapato tu, uuzaji umeandikwa lakini kamwe hufikia bomba.

Moja ya mauzo, mstari mmoja wa ger: utambulisho ni uuzaji, sio tukio

Usifanye mchezo kwa event_id Na wewe mwenyewe utajiongeza. event_id is platform:eventName:externalId, ambayo hujibu "je, tayari tumepitia utoaji huu" na hatuwezi kujibu "tumeandika uuzaji huu" jukwaa ambalo linatangaza malipo moja mara mbili - kama vile invoice.paid Kwa mara nyingine tena kama payment.completed - Kuingiza id mbili na ardhi fedha sawa mara mbili, bila kitu kugongana na hakuna kuonya.

💡
Iliyopatikana kwenye ufungaji wa kumbukumbu: ankara sita na safu tatu za kichwa kila mmoja, kutoka kwa njia tatu za msimbo kutumia miradi mitatu tofauti ya tukio_id. Wote walibeba 0.00 hivyo hakuna jumla iliyoonekana vibaya, na mchakato wowote wa kurejesha kiasi halisi ungehesabu malipo moja mara tatu.

Piga simu kwa maandishi ya pamoja badala yake. Core inahesabu utambulisho wa biashara ya uuzaji (sale_fingerprint(i) Kulinganisha na hali ya sasa, kuhifadhi asili event_id Juu ya update, na filters kwa safu halisi:

Njia pekee ya kusaidia kuandika mwongozo wa mauzo
\OpsIQ\Commerce\CommerceEventContract::upsertSaleRow('opsiq_sales_events', $row);
Ukusanyaji wa Mapato, Matukio mengi

ankara. kulipwa, malipo. kukamilika na kuuza. kamili kwa ankara moja kushiriki alama ya vidole moja na update mstari mmoja.

Fedha za kigeni zinabaki kuwa tofauti

Fedha kwenda nje ni ukweli tofauti kutoka kwa fedha kuja. marejesho ya ankara inaweka utambulisho wake mwenyewe, hivyo haiwezi kamwe kuandika malipo ambayo inabadilisha.

Hakuna kumbukumbu, hakuna fingerprint

Mstari usio na amri, ankara, usajili au kumbukumbu ya huduma haupata alama za vidole wakati wote, kwa hivyo safu mbili zisizohusiana hazigongana kamwe kwa sababu zote zinakosa kitambulisho.

Utangulizi wa awali

ankara_ref, kisha utaratibu_ref , kisha usajili_ref (baada ya hapo) na huduma_ref – nguvu kwanza, hivyo uuzaji mmoja unaweka utambulisho thabiti.

kitabu ni append-pekee: kamwe kuandika upya mauzo

Kurejesha, kufuta au kurekebisha ni Tarehe ya kuingiaKamwe kubadilisha mstari ni kurekebisha. kuandika malipo katika refund inaonekana tidy na mapumziko mambo matatu mara moja:

Inaharibu mapato ya jumla

Jumla ya mauzo na kiwango cha marejesho kuacha kuwa separable - na kiwango ya marejesho ni metric reversal iliyopo ili kuwajulisha.

Kitabu hiki kinahusu mabadiliko katika kipindi cha makosa

Kurudi kwa Machi ya uuzaji wa Januari lazima kupunguza Machi. kuandika tena mstari wa Januari kimya hupumzika kipindi cha kufungwa.

Inaondoa njia ya ukaguzi

Kuingia kwa gofu kunarekodi kile kilichotokea wakati fulani. Marekebisho ni kinyume cha sheria, ambayo ni jinsi usomaji wa vitabu vya kuingia mara mbili umefanya kazi kwa karne tano.

Kwa hiyo, mwasiliani anaripoti mabadiliko badala ya kutumia: kurudi refunded_at Na kwa kuwa refund_amount Pamoja na mzunguko wa maisha ya uuzaji mwenyewe, na basi mpiga simu aandike marejesho kama mstari wake mwenyewe wakati malipo yalitokea. Wawili hawawezi kugongana, kwa sababu alama za vidole vya kuuza hutenganisha kurudi kutoka mauzo.

💡
Kanuni hiyo inatumika kwa kiasi. Usi "kurejesha" kiasi kilichohifadhiwa kwa thamani ya sasa ya jukwaa: ankara iliyolipwa kutoka kwa mkopo wa akaunti iliyoandikwa kihalali 0 wakati wa malipo, na pesa tayari ilirekodiwa wakati mteja alipoweka juu. Kurudisha thamani ya uso inahesabu mara mbili.

Mkataba wa uainishaji

OpsIQ Chagua mtindo wa maisha Mara moja kwa mara, in \OpsIQ\Commerce\SaleLifecycleClassifier-Mkurugenzi wa mawasiliano anataja tu ni nani Jukwaa la wake Maneno yana maana gani, kwa kutumia \OpsIQ\Connectors\SalesLifecycleConnectorInterface::salesLifecycleVocabulary()Kisha kuomba kwa bidii, usiingie kwenye mtego huu.

Kuwasilisha maombi, kutoa uamuzi
public static function salesLifecycleVocabulary(): array
{
    return [
        'credit'             => ['addfunds'],                  // adds balance, sells nothing
        'upgrade'            => ['upgrade'],                   // resizes an existing commitment
        'recurring'          => ['hosting', 'domainrenew'],    // continues something owned
        'acquisition'        => ['domainregister'],            // obtains something new
        'recurring_prefixes' => ['domainaddon'],               // families that grow over releases
    ];
}

$lifecycle = \OpsIQ\Commerce\SaleLifecycleClassifier::classify([
    'explicit'    => $platformSaidSo,     // wins outright when present
    'line_types'  => $types,              // your platform's own line/item types
    'vocabulary'  => self::salesLifecycleVocabulary(),
    'is_order'    => $cameFromANewOrder,
    'is_refunded' => $moneyWentBack,
]);
💡
Precedence imewekwa na kushiriki: wazi, kisha kurejeshwa / kukatwa, basi mikopo, kisha kuboresha, kisha ni_order, kisha kurudia tena, kisha upatikanaji usiojulikana. Upgrade anakaa juu ya ukaguzi wa utaratibu kwa sababu majukwaa huongeza amri ya upgrades pia; mara kwa mara hukaa chini yake kwa sababu ankara ya kwanza ya usajili mpya hubeba aina ya mstari wa kurudiwa.

Kuthibitisha msamiati wote wa jukwaa

Hii ni kushindwa ambayo gharama zaidi na inaonekana kuwa mbaya zaidi. kontakt ya WHMCS ililingana ['hosting','addon','domain'] - Orodha ambayo inasoma kama kamili.WHMCS Je, si kutoa nje ya Domain Aina ya mistari halisi ya uwanja; hutoa DomainRegister, DomainRenew, DomainTransfer, PromoHosting, PromoDomain, DomainAddon* Na kwa kuwa UpgradeWote walianguka kwenye orodha ya unknown: 1,288 Malipo, miaka mitatu, hakuna makosa na mstari wa logi.

Kila mteja mpya anaingiza historia yake kupitia backfill ya kontakt, hivyo mdudu uainishaji haina kuathiri nafasi moja ya kazi - huathiri kila nafasi ya kazi ambayo milele onboards kupitia kiunganishi kwamba, wakati wao kwanza kuangalia bomba yao. kuchukua msamiati kutoka nyaraka jukwaa au sensa ya data kuishi, na mechi kukua familia kwa njia ya bomba zao. Prefix ya Kwa hiyo, hakuna mtu ambaye ameona bado analinganisha na ndugu zake badala ya kupotea.

💡
Kuangalia vitendo: kuhesabu ni wangapi wa safu yako mwenyewe ardhi juu ya haijulikani. kontakt ya mauzo yenye afya classifies karibu kila kitu. mkondo thabiti wa isiyojulikana ni karibu kamwe data huna - ni msamiati kiunganishi kamwe kujifunza kusoma.

Kurejesha historia iliyoingizwa

Kila mmoja waoOpsIQKampuni ya mawasiliano ya simu inatekeleza hatua hii — WHMCS, Shopify, WooCommerce, osCommerce, SaaS Bridge, Stripe, BigCommerce and Magento 2. Treat it as expected, not optional: a customer imports their old records on day one, so a classification fix that cannot reach that history only helps people who signed up afterwards. Implement \OpsIQ\Connectors\SalesLifecycleRepairInterface::reclassifySale() Kwa kutumia kila kumbukumbu ya kifaa chako tayari ina. tools/crm_backfill_sales_lifecycle.php Kisha kurekebisha historia ya kontakt yako nje na hakuna msimbo wa kuunganishwa: kavu kukimbia kwa default, inarudi yenyewe juu na kuthibitisha hesabu ya mstari kabla ya kuandika, inayoweza kurekebishwa kupitia undo ledger, na kamwe anaandika kusoma kushindwa kama jibu.

💡
Ikiwa kontakt yako haiwezi kusoma rekodi za zamani - kiunganishi cha wavuti tu hakiwezi - usiingie njia. Kurudi kwa stub haijulikani ni mbaya zaidi kuliko utekelezaji: backfill itaandika safu nzuri kama haijaorodheshwa na kuripoti mafanikio.
💡
Marejeo ya kina ya mfuko bado inapatikana katika viunganisho / CONNECTOR_EVENTS. md na waunganishaji / PLATFORM_CONNECtorS. Md katika usambazaji wa chanzo cha kujitegemea.
Viunganishi

Mkataba wa Safari

Safari Intelligence inakubali moja ya jukwaa-neutral tukio bahasha kutoka widget browser, kujengwa katika viunganisho, SaaS Bridge, vifurushi vya soko na pato la Connector Builder. majina maalum ya Jukwaa yanatafsiriwa kwa makali; funnel, attribution na Site Intelligence code hutumia tu matukio ya canonical.

Uunganisho na uaminifu wa mpaka

Maelezo ya mchezo Key-domain

Kila tukio linahusishwa na tovuti ya uwanja wa kuthibitishwa_key. Mkononi lazima achukue ufunguo huo kutoka kwa ConnectorRegistry au mwisho wake uliothibitishwa, kamwe kutoka kwa mwili usioaminika wa ombi. Domains huweka kumbukumbu tofauti; kikundi cha kikoa ni mkusanyiko wa wakati wa kusoma tu.

Utambulisho wa kipekee

Tukio_id inahitajika kwa viunganisho na lazima iwe ya kuamua kwa tukio moja la asili. Marekebisho, webhooks na backfills husasisha tukio moja badala ya duplicate safari au uuzaji.

Jina la asili ya Kanada

Hifadhi chanzo_event_name kwa ushahidi na matatizo ya kufungua, kisha ramani kwa tukio_name_canonical. uchambuzi wa msingi lazima kamwe tawi kwenye slug s-kontakt.

Ushahidi wa Server

Uchunguzi wa kivinjari unaweza kuanza au kupata safari. Matukio ya kontakt yaliyothibitishwa yanathibitisha usajili, kuingia, malipo, ununuzi, upyaji, marejesho na matokeo mengine ya mwisho. Ishara halali ya uwiano wa tovuti ni kujiunga kwa nguvu; ishara batili inakataliwa na vitambulisho vyake vilivyoingia haviaminiwi.

Faragha ya faragha

Tuma vitambulisho tu na mashamba zinazohitajika kwa safari iliyotangazwa. Kuheshimu idhini, masking na mipangilio ya uhifadhi. Kamwe usiweke sifa za utambulisho, data ya kadi, siri za uthibitishaji au miili ya ujumbe wa kibinafsi katika mali.

Canonical karatasi ya kupamba

Safari ya Matukio ya Tukio la
{
  "contract_version": 1,
  "event_id": "myshop:order:884:paid",
  "source": "myshop",
  "source_event_name": "order.paid",
  "event_name_canonical": "commerce.purchase.completed",
  "site_key": "exact_domain_site_key",
  "occurred_at": "2026-07-23T08:30:27Z",
  "visitor_id": "optional-browser-visitor",
  "session_id": "optional-browser-session",
  "journey_id": "optional-journey",
  "attempt_id": "optional-attempt",
  "correlation_token": "optional-signed-token",
  "customer_ref": "C-42",
  "user_email": "[email protected]",
  "object_type": "order",
  "object_ref": "884",
  "order_ref": "884",
  "outcome": "succeeded",
  "evidence_level": "server_confirmed",
  "confidence": 1,
  "properties": {"amount": 129, "currency": "USD"}
}

Kodi ya Canon

Tumia jina la kweli nyembamba. Familia zilizosaidiwa ni pamoja na matukio ya ushiriki wa ukurasa / CTA; usajili wa akaunti, kuingia, MFA na nenosiri; kuongoza na hatua za fomu; bidhaa, gari, checkout, malipo, ununuzi, usajili, upya na marejesho; hisia za kukuza na uongofu; kusaidia-centre, mazungumzo na hafla za tiketi; matukio ya usalama; na majina ya kawaida ya mwisho majina ya terminal ni account.signup.succeeded, account.login.succeeded, lead.form.succeeded, commerce.payment.succeeded, commerce.purchase.completed, commerce.subscription.renewed Na kwa kuwa commerce.refund.completed.

Uingiliaji wa kivinjari, uthibitisho na kuacha

widget inaweza kufanya kazi bila kontakt kwa kuchunguza muundo wa ukurasa, vitendo fomu, matokeo DOM na kumbukumbu ya safari ya mgeni. Ushahidi huo bado wazi graded kama aliona au inferred. Munganisho anaongeza uthibitisho mamlaka server na anaweza kuunganisha ni sawa jaribio browser. Abandonment ni kwanza kuhifadhiwa kama mgombea; inakuwa kutelekezwa tu baada ya dirisha utendaji kuweka katika UI na wakati hakuna kupona baadaye au mafanikio kuwepo.

Mapato na Matumizi

Attribution inapendelea ishara ya uwiano iliyosainiwa, basi safari halisi, jaribio, kikao au kumbukumbu ya biashara, kisha graph ya utambulisho uliokubaliwa, na hatimaye mechi ya tabia iliyofungwa. mauzo yasiyolinganishwa yanabaki bilatributed. uzito wa gofu nyingi lazima jumla 1Tovuti Intelligence inayohusishwa na mapato inasoma hii; mikopo, mkoba juu-ups, ishara za juu na Ongeza Fedha hazinunui kamwe kununua uongofu.

⚠️
Mfano wa mchango, madirisha ya kuangalia, utunzaji wa moja kwa moja wa trafiki, ujasiri wa chini, muda wa kuachwa na ufafanuzi wa funnel ni sera ya UI. Msimbo wa Kuunganisha haipaswi kuwa ngumu kuzibadilisha.

Kuunganishwa na Muumba

Taarifa ya Safari
{
  "capabilities": ["sales", "journey_events"],
  "journey_capabilities": {
    "journey_events": true,
    "payments": true,
    "subscriptions": false,
    "correlation_token": false,
    "backfill": true
  },
  "journey_event_mappings": [{
    "source_event_name": "order.paid",
    "event_name_canonical": "commerce.purchase.completed",
    "field_map": {
      "order_ref": "order.id",
      "customer_ref": "order.customer_id",
      "amount": "order.total",
      "currency": "order.currency",
      "occurred_at": "order.paid_at"
    }
  }]
}

Kutangaza tu uwezo mfuko kweli hutoa. Connector Builder inathibitisha ramani na inazalisha adapta moja ya jukwaa-neutral inayotumiwa na vifurushi vya kwanza. ingestion Safari anapokea tukio moja au kundi lililofungwa la 100 kupitia sehemu iliyozalishwa ya ushirikiano wa kuaminika.

💡
Biashara ya kiongozaji inabaki chanzo cha kifedha cha ukweli. Daraja la biashara-kwa-journey linachapisha matokeo yaliyothibitishwa na seva na kupatanisha malipo baada ya upsert iliyopo, kwa hivyo malipo moja kamwe inakuwa mauzo mawili.
Viunganishi

Jinsi ya kufanya kazi

Kila kontakt inatangaza seti ya vitendo: mambo ambayo AI inaweza kufanya kupitia jukwaa la nje. Hatua ni daraja kati ya "Aina inasema" na "AI inafanya."

Matendo ya
Jinsi ya kufanya kaziOmbi la mteja limewekwa kwenye kadi ya hatua ya kufuta, kisha orodha: ruhusa iliyokaguliwa, unathibitisha, API inayoitwa.Jinsi ya kufanya kaziNafasi ya Kazi“Unawezaje kunipigia simu yangu”Wateja wa watejaIcancel_subscriptiondeleteUthibitisho unahitajikaViungo: usajili_id (kutoka kwa muktadha)Hatua za kuchukuareadKuandika kuandikadeleteRuhusa na jukumu la ukaguziUnathibitisha kuwa hatuaAPI · Matokeo yaliyotangazwa1DECLAREDKila mtumiaji ana orodha ya vitendo2GATED+ Uthibitisho wa kuthibitisha3THEN RUNAPI Kurejea, matokeo ya
Ombi inakuwa hatua iliyotangazwa (iliyoandikwa kama kusoma / kuandika / kufuta) ambayo ni ruhusa ya ukaguzi, kuthibitishwa, kisha kutekelezwa na kuripotiwa.

Maisha ya Actioncycle

1
Wateja wanataka kitu

"Inaweza kujiandikisha." AI inatambua hii inahitaji hatua ya "mawasiliano_ usajili".

2
A. Kukagua vibali vya

Je, ni kweli kwamba mtumiaji wa sasa ana nafasi sahihi?

3
A. Kufufua vigezo

Hatua inahitaji kitambulisho cha usajili. AI inaonekana kutoka kwa muktadha wa mteja au anauliza mteja.

4
Uthibitisho wa

Kwa vitendo vya uharibifu au vya juu, AI inahitaji uthibitisho kabla ya kutekeleza.

5
Utendaji

Hatua hiyo inaita jukwaa la nje API.

6
Matokeo ya matokeo

A. Inaelezea matokeo ya wateja.

Aina za vitendo

Soma kwa vitendo

Angalia data bila kubadilisha chochote. Mifano: orodha_ taratibu, kupata_customer. salama, hakuna uthibitisho unaohitajika.

Andika matendo

Kujenga au kurekebisha data. Mifano: kuunda_ticket, update_order. inaweza kuhitaji uthibitisho.

Kupuuza vitendo

Ondoa data. Mifano: kufuta_subscription. daima zinahitaji uthibitisho.

Hatua za HTTP

Ilitangazwa kwa vitendo.json, generic API wito uliofafanuliwa kwa ufafanuzi.

Uwezo wa Kuweka

Uwezo wa kuchagua "uwezo" katika vitendo.json, kiunganishi-neutral darasa tag (kwa mfano "tickets" kwa ajili ya tiketi kusoma /lookup, "ticket_ kuunda" kwa kufungua tiketi).OpsIQ malango ya darasa nzima sare katika kila kontakt: tiketi kusoma kushuka nje ya AI wakati operator zamu mbali AI Tiketi Uelewa, na uundaji wa tiketi ni kuhifadhiwa kwa ajili ya OpsIQ mtunzi mwenyewe (kwa hivyo kontakt kujenga chombo haiwezi duplicate ni). kutangaza na kiunganishi chako kinakubaliana.OpsIQ Haupaswi kamwe kujua majina yako ya vitendo. Mjenzi wa Kuunganisha huiweka kama kushuka kwa uwezo kwa hatua.

Kanuni za vitendo

Utekelezaji katika PHP katika darasani ya kontakt. udhibiti kamili juu ya mantiki.

Mfano wa ufafanuzi wa vitendo
{
  "lookup_order": {
    "label": "Look up an order",
    "description": "Find an order by ID or email",
    "method": "GET",
    "endpoint": "/admin/api/2024-01/orders.json",
    "params": {
      "order_id": { "type": "string", "label": "Order ID" },
      "email":    { "type": "email",  "label": "Customer email" }
    }
  }
}
Viunganishi

Kujenga uhusiano wa kontakt

Mjenzi wa Kuunganisha hukuruhusu kuunda uunganisho kamili kwa jukwaa lolote na REST API. Hakuna coding inahitajika kwa viunganisho vya msingi.

Kujenga uhusiano wa kontakt
Mjenzi wa KiunganishiFomu ya kontakt-code: jina, aina ya auth, msingi URL, ramani ya hatua, mtihani wa kupitisha na kifungo cha kuchapisha.Mjenzi wa KiunganishiNafasi ya KaziMjenzi wa KiunganishiJina la jinaJukwaa la jukwaaAuthani waOAuth 2.0 (Sauti ya)Msingi wa msingi URLhttps://api.example.com/v2Hatua ya hatuaGET/customers →Orodha ya WatejaUchunguzi waonyeshaUwasilishaji wa kontakt1NO-CODEJina, auth, msingi URL2ANY APIKipaumbele, Bearer, msingi, HMAC, _OAuth3PUBLISHInto /connectors/<slug>/
Kuhimiza ujenzi katika ngazi yoyote API· Kuweka akiba, msingi wa URL na vitendo, mtihani ni, na kuchapisha kontakt kazi. Hakuna msimbo inahitajika.

Huduma kamili ya mwenyeji API Taarifa ya Habari

Kila kuzalisha API connector inaweza kuonyesha tofauti Native API Soma na asili API Kuandika matendo. Curated matendo kubaki preferred; asili matendo cover mtoa endpoints aliongeza baadaye. Runtime inasaidia REST, GraphQL, JSON, aina, XML, miili raw na sehemu nyingi, bounded pagination,API-version headers na idempotency wakati kuhifadhi vitambulisho ndani ya mipangilio workspace connector.

⚠️
Masoko ya fedha za kigeni ni chanzo cha /marketplace_connectors Aidha, pamoja na kuwa /connectors. Kuongeza toleo la mfuko, regenerate mkataba na nyaraka, kukimbia vipimo vya kufanana, kisha saini tena na kuchapisha toleo jipya la Marketplace.

Mhandisi wa Ujenzi

Mchawi ana hatua sita, kuonyeshwa kama tabs juu. Unaweza kuruka kati yao kwa uhuru, na Mradi wa kuokoa Katika ngazi ya chini, kazi yako inaendelea wakati wowote.

1
Utambulisho na wasifu

Jina, slug, maelezo na icon, kisha chagua wasifu wa mkataba: Standard API, Biashara, Helpdesk, Mailbox, Site Intelligence, SaaS Bridge, Jukwaa la PHP la Mitaa, au Jukwaa la bila yaAPI Wakati jukwaa mtumishi kitu wito na OpsIQ ina kufunga daraja. profile kuchagua uwezo kamili kuanzia hatua; unaweza bado kurekebisha uwezo wa mtu binafsi.

2
Authani wa

Chagua muundo wa uthibitishaji ambao jukwaa hutumia na kujaza katika mashamba yake. Ingiza sifa halisi za mtihani hapa pia: hutumiwa kwa mtihani wa uunganisho kwenye hatua inayofuata, na hazihifadhiwa baada ya kuchapisha.

3
Jaribio la majaribio

Kuingia mwenyewe API Msingi wa msingi URL na kuthibitisha mwisho, kisha kuendesha mtihani wa uunganisho wa moja kwa moja kutumia sifa kutoka hatua 2Fanya hivyo kabla ya kufafanua vitendo vyovyote, ikiwa ni auth au msingi.URL Ni makosa, kila hatua unayoandika baadaye itashindwa kwa sababu hiyo na utakuwa unarekebisha kitu kibaya.

4
Hatua za

Eleza kila operesheni: jina, mbinu ya HTTP, njia ya mwisho, vigezo, ramani ya uwanja wa majibu, na mipangilio ya kuaminika iliyoelezwa hapa chini. Unaweza kukimbia kila hatua moja kwa moja dhidi ya kuishi API kutoka hatua hii.

5
Vichochezi

Ramani matukio ya webhook jukwaa yako hutuma kwenye OpsIQ matukio, hivyo mambo yanayotokea kwenye jukwaa yako yanaweza kuanza kufanya kazi katika OpsIQ.

6
Mapitio, Mkataba wa Biashara na kuchapisha

Review every action, trigger and capability. Enterprise profiles expose the generated queue, worker, hook, migration, ticket-mirror, attachment and conflict contract before publishing. Publishing writes the package into /connectors/<slug>/.

⚠️
Uchapishaji hauendesha Suite ya kufanana. Publish tu inathibitisha fomu ya mchawi na hutoa maonyo ambayo hayazuiliki. suite kamili - wazi, faili za uwezo, mkataba wa utambulisho-uliotengenezwa na daraja-snippet hundi - inaendesha wakati unafungua Dry-run, na tena wakati wa kufunga.

Jinsi ya kufanya kazi na jinsi ya kuandika barua pepe hii si kuonyesha wewe

Tabia tano za watu wa jenereta mshangao. Hakuna mtu ni mdudu; wote itakuwa gharama wewe mchana kama kukutana nao kwa ajali.

Swali moja linaamua kupita: Je, jukwaa linafanya kaziAPI?

Jibu kwa hatua1kwa kuchukua hali ya upatikanaji wa data (au "Platform bilaAPI(a) maelezo ya ziada).APImode ya kutangaza native_api and emits the <slug>_api_call passthrough. Bridge mode declares platform_bridge Badala yake, barua native_api Hata kama spec mzee kubeba ni, hivyo wazi, tabaka yanayotokana na na docs utaalamu hawezi kutokubaliana. ai_brain_aware Aliongeza kwa njia yoyote.

^ Tnn., “alikuwa naAPI"

Mjenzi hufuata jibu lako; haifanyi kazi ukweli kwa yenyewe, na default wakati hakuna kitu kinachosemwa niAPIKwa mfano, hakuna-APIJukwaa linapaswa kusema hivyo - chagua "Platform bila ya"API"Maarifa, kuweka upatikanaji wa data kwa daraja, au tick platform_bridge; any one of the three is enough and they cannot contradict each other. Skip the question on a platform with no API and you are back to the old failure: a dead <slug>_api_call the model keeps reaching for. This used to be stamped unconditionally, so the trap is now escapable rather than gone.

Makosa ya mtihani wa uhusiano ili kupata/ping

Ikiwa unaacha njia ya kuthibitisha tupu, Mjenzi anaandika /ping katika mfumo wa kompyuta na kuingia kwenye profile.jsonKaribu hakuna jukwaa la kweli linalotumika njia hiyo, kwa hivyo Connection ya Mtihani inashindwa na HTTP404juu ya kila kufunga na kusoma kama mteja misconfiguration badala ya mfuko kasoro. Weka njia ya kuthibitisha kwamba jukwaa yako kweli majibu. Kwa daraja kiunganishi, kumweka katika uchunguzi wako mwenyewe mwisho pointi - inathibitisha mnyororo mzima katika wito mmoja: daraja ni kutumika, mechi muhimu, na daraja inaweza kufikia database.

Kuchapisha tena kunaandika nakala zako za mkono

Uwezo sasa hufuata jibu la upatikanaji wa data, kwa hivyo wale wasio na drift tena. Kila kitu kingine kilichozalishwa bado kinafanya: hariri ContextProvider. php au faili nyingine yoyote iliyotolewa na kuchapisha ijayo inabadilisha. ubaguzi mmoja uliohifadhiwa ni faili ya daraja - mchawi tu huandika daraja linalobeba alama yake mwenyewe, kwa hiyo moja iliyoandikwa mkono imeachwa peke yake.

Kuchapisha upya faili

Un-tick uwezo na ijayo kuchapisha kuondosha yake mtoa faili. Hand-edits kwa faili yoyote yanayotokana — ContextProvider.php juu ya yote - ni overwritten bila onyo. Nakala customisations nje kwanza, au kuchukua umiliki wa mfuko kwa kufuta .opsiqKuwa developer.jsonMchawi hayupo hivyo.

Kutolewa kwa #Status daima ni hakikisho

Mchawi hana udhibiti wa hilo. kifurushi kinachomaanisha kusafirisha kama uzalishaji lazima iwe na toleo la_status lililobadilishwa kwa mkono katika mipangilio.json - na kwamba hariri huvunja saini, hivyo saini tena baadaye.

Kuthibitisha uaminifu, sio asili

Vifurushi vya wajenzi vinasainiwa na ufunguo wa usanidi huu. Hiyo hutambua uharibifu. Haithibitishi ni nani aliyeandika mfuko, na ufungaji wowote unaoshikilia ufunguo huo unaweza kuzalisha saini sawa.

Kuvunjika kwa miti ya miwa ni tu checked katika mti mmoja

Serikali yakanusha tuhuma zinazomkabili ambazo tayari/connectors/.Hata hivyo, yeye si kuangalia/marketplace_connectors/,Kwa hivyo mfuko wa chama cha kwanza kilichoidhinishwa na mkono na slug sawa inaweza kuishia kivuli.

💡
Mchawi hana hatua ya kuandika maarifa. faili ya ujuzi inayoelezea jukwaa lako linazalishwa kwako kutoka kwa jina, maelezo, aina ya auth na vitendo unavyofafanua, na imejaa AI wakati kontakt inawezeshwa.

Hatua ya kuchukua (hatua) 4)

Kila hatua ina mipangilio ifuatayo: Ni nne tu zinazohitajika; udhibiti wa wengine ambao wanaweza kukimbia na jinsi kwa makini.

Hatua ya msingi na label

Ufunguo ni kile AI wito; studio ni nini binadamu kusoma. Keys ni majinapaced na kontakt yako slug moja kwa moja, hivyo viunganisho viwili wanaweza wote kuwa "orodha_orders" bila colliding.

Njia ya HTTP

Kupata, post, PUT, Patki au DELETE.

URL Njia ya njia

Imependekezwa kwa msingi URL Matumizi ya {name} Kwa mfano, kwa wakulima /opportunities/{id}/stage

Parameters ya

Kwa kila kipimo, unaweza kuchagua wapi kwenda: Mwili wa Mwili, Njia ya njia, Mahitaji ya au kichwa cha kichwaNjia ya mkato ya kufikia A {placeholder};Maombi ya parameter yanazingatiwa kwa URL.

Majibu ya ramani

Sema ni uwanja gani katika majibu ya JSON inamaanisha nini, ambayo ni jina la mteja, ambalo ni barua pepe, ambayo ndio jumla ya agizo. Hii ndiyo inaruhusu AI kusoma data ya jukwaa lako badala ya kuifikiria.

Nani anaweza kutumia

Timu yako (admin AI), wateja waliosainiwa (mazungumzo ya mteja), wote, au msaidizi wa kuandika. vitendo vya Wateja vinaendeshwa tu kwa mteja aliyesajiliwa, na mashamba ya utambulisho imefungwa kwao moja kwa moja ili mteja mmoja hawezi kuuliza kuhusu mwingine.

Inahitaji uthibitisho

Mtu lazima akubali kabla ya hatua.

Kuwa na uhakika

Kuonya hatua kama kufuta au kubadilisha hali. kutumika kuonya kabla ya anaendesha.

Ruhusa zinazohitajika

admin lazima kushikilia ruhusa hii kwa AI kuendesha hatua kwa niaba yao; watendaji kamili daima kupita manage_integrations, manage_general, manage_billing, manage_sales_bridge, manage_knowledge, manage_appearance, manage_behavior, manage_permissions, manage_dangerzone, reply_to_chats, escalate_to_ticket, send_agent_emailHakuna, au hakuna mtu yeyote aliye na uwezo wa kufanya hivyo.

Maelezo ya mchezo A-A

Chaguo, lakini inafaa kuandika. Inaelezea AI wakati wa kufikia hatua hii, kwa mfano "Utumia hili wakati admin anauliza kubadilisha hatua ya mpango".

Uwezo wa uwezo

Kitambulisho cha darasa la hiari, ama tiketi (tembe ya kusoma au kuangalia) au tiketi_ kuunda (inafungua tiketi). Tagging lets OpsIQ lango lote kwa mara moja, kwa mfano, kujificha tiketi inasoma wakati mwendeshaji anapogeuza ufahamu wa tikiti ya AI.

Orodha ya njia

Chaguo. Kwa mwisho ambao hurudisha orodha, njia iliyopigwa kwa safu, kwa mfano data au data. items

Njia ya makosa

Eneo la mwili ambalo uwepo wake unamaanisha wito ulishindwa, kwa mfano kosa. ujumbe, muhimu kwa APIs Kurudi kwa HTTP 200 juu ya kushindwa.

Kukimbia kwa

Kila hatua inaweza kuchukuliwa dhidi ya maisha API Kutoka hatua hii, ili uweze kurekebisha njia mbaya au jina la shamba kabla ya mtu mwingine yeyote kuitumia.

⚠️
Andika vitendo vinalindwa na chaguo-msingi. Hatua yoyote kwa kutumia POST, PUT, PATCH au DELETE huanza kuhitaji idhini ya kusimamia_kujumuisha Na kwa kuwa Hatua mpya ya kuandika inashindwa kufungwa badala ya kuruhusu AI kubadilisha data yako bila kusimamiwa. Unaweza kubadili wote juu ya hatua, lakini kuibadilisha kwa kujua.
💡
Ili kuwa wito kutoka kwa mazungumzo ya wateja, hatua lazima iwe kusoma-tu: kuondoka wote wawili Requires uthibitisho na Destructive unticked. Hatua mteja anaweza kusababisha kwamba pia mabadiliko hali si kitu mchawi basi meli kwa ajali.

Kuhamisha tovuti (hatua) 5)

Hatua ya Wachimbaji inakupa webhook URL kujiandikisha na jukwaa lako, na kuthibitisha kila ombi linalowasili.

Ishara ya kichwa

Kichwa cha jukwaa ishara yako na, kwa mfano X-Hub-Signature-256.

Algorithm ya

HMAC-SHA1, HMA C-SHA256 au HMAc-SHA512.

Mpango wa Ishara

Rahisi, hex wazi au msingi 64 digest. Au Stripe-style, t = ...,v1 =... muundo uliotumiwa na Stripe na majukwaa kadhaa ambayo ilinakili.

Utangulizi wa Prefix

Baadhi ya majukwaa huandaa mapema digest, kwa mfano sha256 =. Acha tupu ikiwa yako haina.

Matukio ya ramani

Ramani kila tukio jukwaa yako kutuma kwenye OpsIQ tukio ambalo linapaswa kuendelezwa.

Auto-kujiandikisha kwa ajili ya tovuti

Ikiwa jukwaa lako lina API Kwa ajili ya kusimamia tovuti yako mwenyewe, huna haja ya kujiandikisha. URL Kwa njia ya mikono, wazi Jisajili kwa tovuti hii ya bure kwenye kuwezesha Na katika hatua ya pili, eleza mambo mawili ambayo unayafanya kwa usahihi. 4:

Hatua ya Webhook

Unatoa jina la parameter ambalo linabeba URL, kwa hiari yule anayeshikilia orodha ya tukio, na njia katika majibu ambayo ina ID mpya ya wavuti.

Hatua ya kufuta-webhook

Kuitwa wakati kontakt ni walemavu, kwa kutumia id alitekwa juu, hivyo mlemavu kiunganishi pia kuacha jukwaa yako kutuma kwa mwisho wa wafu.

Uwezo wa kubadili unaweza kubadilika

Wasifu na uwezo hufafanuliwa na Mkataba wa Uunganishaji 2.2. Uwezo uliozalishwa na wa kuamua hutolewa moja kwa moja; uwezo wa biashara huzalisha EnterpriseExtension.php Kuunganishwa na waya wa runtime lifecycle.

Hatua za

Operesheni AI inaweza kukimbia kwenye jukwaa lako: maagizo ya orodha, kupata mteja, kutoa marejesho.

Vichochezi

Kupata webhoot kutoka jukwaa yako na kugeuka yao katika OpsIQ matukio.

Tiketi ya

AI Triage na jibu Copilot kwenye tiketi ambazo zinakaa kwenye jukwaa lako. Chagua mwisho ambao unarudi tikiti moja na majibu yake na ramani ya mashamba; OpsIQ inasoma thread kupitia hiyo.

Mailbox na mawasiliano

Onyesha barua ya mteja kwenye ratiba yao, tuma kutoka kwa mpango, na ulinganishe kitabu chako cha anwani katika OpsIQ CRM.

Wateja wa kigeni

Ukurasa kupitia orodha yako ya wateja na kuagiza kila mmoja kama kuwasiliana kwa OpsIQ. hii ndio kifungo cha Uagizaji kinaendesha.

Mazingira ya

Kusukuma data ya kuishi kutoka kwenye jukwaa lako katika kila mazungumzo ya AI.

Utambulisho wa utambulisho

Fanya kazi ambayo mteja wako ni mgeni, na uonyeshe wasifu wao na ununuzi kwenye tiketi.

Bidhaa na bili

Matukio ya mapato ya chakula na takwimu za MRR OpsIQ ya Dashibodi.

Tiketi za ndani

Kugeuza tiketi na barua pepe jukwaa yako inatoa kwa webhook OpsIQ Msaada wa threads.

Majibu ya nje

Post OpsIQ wafanyakazi walijibu nyuma kwenye jukwaa ambalo thread ilianzia.

Watumiaji wa Sync

Kuingiza akaunti yako ya wafanyakazi katika OpsIQ Watumiaji wa admin.

Idara ya Sync

Kuhamisha huduma yako katika OpsIQ.

Kuhamasisha na kukuza bidhaa za chakula

Hebu Kukuza Studio lengo juu ya ukweli unajua kuhusu mtu, na kutoa bidhaa yako halisi ndani ya kukuza.

Msaidizi wa Studio

Expose ukweli wa uchunguzi uliothibitishwa na seva, waliepuka vigezo na kurasa za wapokeaji wa CRM zilizofungwa kupitia SurveyProvider. php iliyojitolea.

Asili ya Native IP Kuzuia kuzuia

Wakati ambapo wakati OpsIQ Kwa upande mwingine, IP Piga simu kwa block ya jukwaa yako mwenyewe API Kwa hiyo, mfumo huo pia unatekelezwa.

Matukio ya Usalama

Kuwa imefungwa-IP Ishara za hatari kutoka kwa OpsIQ.

Ujuzi wa jukwaa kwa AI

Kila kontakt wewe kujenga meli kumbukumbu fupi kuelezea jukwaa yako ni nini na matendo yake kufanya. OpsIQ admin AI inasoma kila wakati kontakt yako imewezeshwa, kwa hivyo inaeleweka jukwaa lako badala ya kuona orodha ya majina ya hatua.

API Njia ya kupita

Kiunganisho chako daima hupata simu ya kusudi la jumla ili AI inaweza kufikia mwisho haukufafanua hatua iliyopangwa kwa. Tumia vitendo vilivyoandikwa ambapo unaweza; hii ni hatch ya kutoroka.

Mkataba wa Kuunganisha Canon 2.2 Kumbukumbu ya kumbukumbu

Mkataba wa: 2.4 · 57 capabilities · 8 profiles.

Maelezo ya Connector

standard_api · Standard REST or GraphQL API

Actions, triggers, OAuth/API-key authentication and optional context/identity mappings. Capabilities: actions, triggers, native_api, ai_brain_aware.

commerce · Commerce and billing platform

Customers, orders, sales, subscriptions, billing, promotions and journey events. Capabilities: actions, triggers, journey_events, sales, sales_reconciliation, billing, sync_orders, customer_import, survey, promo_audience, promo_feed, context, identity.

helpdesk · Helpdesk and ticket platform

Inbound tickets, outbound replies/notes, customer roster, AI triage and bidirectional ticket mirroring. Capabilities: actions, triggers, inbound_ticket, outbound_reply, outbound_note, ai_tickets, customer_import, survey, context, identity, ticket_mirror, ticket_merge, attachment_bridge, conflict_resolution.

mailbox · Mailbox and email provider

Inbound/outbound mail, address-book sync, multi-account OAuth and CRM timeline integration. Capabilities: inbound_email, outbound_email, mailbox, email_mailbox, oauth, actions, customer_import, ai_reply.

site_intelligence · Site Intelligence data provider

SEO, analytics, search-console, local-search or monitoring provider with scheduled sync. Capabilities: actions, triggers, site_intelligence, seo, scheduled_workers, durable_queue.

saas_bridge · SaaS bridge

Deep two-way SaaS integration with customers, billing, identity, tickets, webhooks, queues, attachments and workers. Capabilities: actions, triggers, webhook, context, identity, customer_import, survey, journey_events, sales, sales_reconciliation, billing, inbound_ticket, outbound_reply, ticket_mirror, ticket_merge, attachment_bridge, durable_queue, scheduled_workers, database_migrations, conflict_resolution, enterprise_hooks, admin_assets.

no_api_bridge · Platform with no API (OpsIQ installs a bridge)

For a self-hosted PHP application that serves no callable API. The wizard generates a signed bridge file the operator drops into their own site, plus the typed actions that read and write through it. Capabilities: actions, platform_bridge, ai_brain_aware.

local_php_platform · Local PHP platform bridge

WHMCS-style local hooks, database access, two-way tickets, billing/customer sync, queues and migrations. Capabilities: actions, native_data, context, identity, customer_import, survey, journey_events, sales, sales_reconciliation, billing, inbound_ticket, outbound_reply, ticket_mirror, ticket_merge, attachment_bridge, durable_queue, scheduled_workers, database_migrations, conflict_resolution, enterprise_hooks, admin_assets.

Uwezo wa Canon

Matendo ya vitendo

Universal actions. Capability version: 1.0. Mode: generated. Runtime methods: registerActions. Package files: actions.json.

Watangulizi wa

Inbound event triggers. Capability version: 1.0. Mode: generated. Runtime methods: handleWebhook. Package files: actions.json.

Mtandao wa Yahoo

Inbound webhook endpoint. Capability version: 1.0. Mode: generated. Runtime methods: handleWebhook.

journey_events

Universal Journey Event Contract mapping. Capability version: 1.1. Mode: generated. Interfaces: OpsIQ\Connectors\JourneyEventConnectorInterface. Package files: settings.json.

muktadha wa

AI context providers. Capability version: 1.0. Mode: generated. Runtime methods: contextProviders. Interfaces: OpsIQ\Connectors\ContextConnectorInterface. Package files: ContextProvider.php.

guest_lookup

Guest record lookup without login (reference + proof match). Capability version: 1.0. Mode: generated. Runtime methods: contextProviders. Interfaces: OpsIQ\Connectors\ContextConnectorInterface. Package files: GuestLookupProvider.php.

Utambulisho wa utambulisho

Admin/customer identity providers. Capability version: 1.0. Mode: generated. Runtime methods: identityProviders, detectAdmin, detectCustomer. Interfaces: OpsIQ\Connectors\IdentityConnectorInterface. Package files: IdentityProvider.php.

sales

Sales and revenue ingestion. Capability version: 1.2. Mode: generated. Interfaces: OpsIQ\Connectors\CommerceConnectorInterface. Package files: SalesIngest.php.

sales_reconciliation

Scheduled sales-ledger reconciliation against the platform. Capability version: 1.0. Mode: generated. Runtime methods: reconcileSales. Interfaces: OpsIQ\Connectors\SalesReconciliationInterface.

Billing ya

Cross-platform billing snapshot. Capability version: 1.0. Mode: generated. Runtime methods: billingProviders. Interfaces: OpsIQ\Connectors\BillingConnectorInterface. Package files: BillingProvider.php.

payments

Payment-provider capability bus. Capability version: 1.0. Mode: generated. Runtime methods: paymentsCapabilities.

Biashara ya biashara

Sell through chat: canonical commerce role map. Capability version: 1.0. Mode: declarative. Package files: commerce_roles.json.

inbound_ticket

External ticket/email to OpsIQ ticket ingestion. Capability version: 1.0. Mode: generated. Runtime methods: handleWebhook. Interfaces: OpsIQ\Connectors\TicketMirrorConnectorInterface.

outbound_reply

Reply mirroring to the external platform. Capability version: 1.0. Mode: generated. Runtime methods: pushReply. Interfaces: OpsIQ\Connectors\TicketMirrorConnectorInterface.

ticket_merge

Ticket merges applied on the platform (native merge or private transcript note). Capability version: 1.0. Mode: generated. Runtime methods: mergeTickets. Interfaces: OpsIQ\Connectors\TicketMergeConnectorInterface.

sync_users

Staff/customer synchronisation. Capability version: 2.0. Mode: generated. Runtime methods: listCustomers. Interfaces: OpsIQ\Connectors\CustomerImportConnectorInterface. Package files: SyncImport.php.

sync_departments

Department/team synchronisation. Capability version: 1.0. Mode: generated. Package files: SyncImport.php.

sync_orders

Order roster and order-event synchronisation. Capability version: 1.0. Mode: declarative. Interfaces: OpsIQ\Connectors\CommerceConnectorInterface.

sync_products

Product, catalog and inventory synchronisation. Capability version: 1.0. Mode: declarative. Runtime methods: registerActions.

sync_projects

Project, issue and workspace synchronisation. Capability version: 1.0. Mode: declarative. Runtime methods: registerActions.

customer_import

CRM customer roster import. Capability version: 2.0. Mode: generated. Runtime methods: listCustomers, backfillChunk. Interfaces: OpsIQ\Connectors\CustomerImportConnectorInterface.

security_events

Receive and emit security events. Capability version: 1.1. Mode: generated. Runtime methods: securityCapabilities, syncBlockedIp, removeBlockedIp. Interfaces: OpsIQ\Connectors\SecuritySyncConnectorInterface.

security_native_block

Native remote IP/CIDR blocking. Capability version: 1.0. Mode: generated. Runtime methods: syncBlockedIp, removeBlockedIp. Interfaces: OpsIQ\Connectors\SecuritySyncConnectorInterface.

survey

Survey identity, audiences, recipients and variables. Capability version: 1.0. Mode: generated. Runtime methods: surveyAudienceCatalog, surveyAudienceFacts, surveyVariableCatalog, surveyVariables, surveyRecipientPage. Interfaces: OpsIQ\Connectors\SurveyConnectorInterface. Package files: SurveyProvider.php.

reply_feedback

Ticket reply feedback mirror (platform reply ratings land via the portal write method). Capability version: 1.0. Mode: generated. Runtime methods: replyFeedbackCatalog, pullReplyFeedback. Interfaces: OpsIQ\Connectors\ReplyFeedbackConnectorInterface.

promo_audience

Promotion targeting facts. Capability version: 1.0. Mode: generated. Runtime methods: subscribers. Interfaces: OpsIQ\Connectors\PromotionConnectorInterface.

promo_feed

Promotion product/content feed. Capability version: 1.0. Mode: generated. Interfaces: OpsIQ\Connectors\PromotionConnectorInterface.

email_mailbox

Mailbox bus, outbound mail and address-book sync. Capability version: 1.0. Mode: generated. Runtime methods: emailAccounts. Interfaces: OpsIQ\Connectors\MailboxConnectorInterface.

inbound_email

Receive inbound email. Capability version: 1.0. Mode: declarative. Runtime methods: poll, handleWebhook. Interfaces: OpsIQ\Connectors\MailboxConnectorInterface.

outbound_email

Send outbound email. Capability version: 1.0. Mode: declarative. Runtime methods: registerActions. Interfaces: OpsIQ\Connectors\MailboxConnectorInterface.

mailbox

Mailbox connector. Capability version: 1.0. Mode: declarative. Runtime methods: emailAccounts. Interfaces: OpsIQ\Connectors\MailboxConnectorInterface.

ai_tickets

AI triage and Inbox Copilot for remote tickets. Capability version: 1.0. Mode: generated. Runtime methods: loadTriageContext. Package files: AiOperations.php.

ai_reply

AI-assisted reply drafting. Capability version: 1.0. Mode: declarative. Runtime methods: registerActions.

ai_brain_aware

Connector expertise supplied to Admin AI. Capability version: 1.0. Mode: generated. Package files: ai_expertise_admin.md, ai_api_reference.md.

native_api

Native API passthrough. Capability version: 1.0. Mode: generated. Runtime methods: registerActions.

platform_bridge

Signed platform bridge (for platforms with no API). Capability version: 1.0. Mode: generated. Runtime methods: registerActions. Package files: bridge/.

native_data

Local database/platform data adapter. Capability version: 1.0. Mode: declarative. Runtime methods: nativeDataProviders. Interfaces: OpsIQ\Connectors\NativeDataConnectorInterface.

ya crm

CRM capability provider (calendar, enrichment, telephony or customer data). Capability version: 1.0. Mode: declarative. Runtime methods: crmCapabilities. Interfaces: OpsIQ\Connectors\CrmCapabilityConnectorInterface.

block_registry

Remote sender block-registry synchronisation. Capability version: 1.0. Mode: declarative. Runtime methods: blockSender, unblockSender, isSenderBlocked. Interfaces: OpsIQ\Platform\BlockRegistryInterface.

inbound_comment

Inbound comment ingestion. Capability version: 1.0. Mode: declarative. Runtime methods: handleWebhook.

outbound_note

Outbound private note. Capability version: 1.0. Mode: declarative. Runtime methods: registerActions.

outbound_notification

Outbound notification delivery. Capability version: 1.0. Mode: declarative. Runtime methods: registerActions.

oauth

OAuth 2.0 authorisation. Capability version: 1.0. Mode: generated.

reviews

Review ingestion and response. Capability version: 1.0. Mode: declarative. Runtime methods: registerActions.

ya ndani

Local search/location data. Capability version: 1.0. Mode: declarative. Runtime methods: registerActions.

ya seo

SEO data and actions. Capability version: 1.0. Mode: declarative. Runtime methods: registerActions.

site_intelligence

Site Intelligence provider. Capability version: 1.0. Mode: declarative. Runtime methods: siteIntelligenceProviders. Interfaces: OpsIQ\Connectors\SiteIntelligenceConnectorInterface.

Uchambuzi wa analytics

Analytics data provider. Capability version: 1.0. Mode: declarative. Runtime methods: analyticsCapabilities.

comms

Communications/video-meeting provider. Capability version: 1.0. Mode: declarative. Runtime methods: commsCapabilities.

admin_assets

Connector-provided admin/account/public browser assets. Capability version: 1.0. Mode: generated. Runtime methods: adminAssets. Interfaces: OpsIQ\Connectors\AdminAssetConnectorInterface.

enterprise_hooks

Platform-native hooks and lifecycle callbacks. Capability version: 1.0. Mode: extension. Package files: EnterpriseExtension.php.

durable_queue

Durable outbox/inbox queue and retry policy. Capability version: 2.0. Mode: extension. Package files: EnterpriseExtension.php.

ticket_mirror

Bidirectional ticket mirror with conflict handling. Capability version: 2.0. Mode: extension. Interfaces: OpsIQ\Connectors\TicketMirrorConnectorInterface. Package files: EnterpriseExtension.php.

attachment_bridge

Attachment upload/download transfer. Capability version: 2.0. Mode: extension. Package files: EnterpriseExtension.php.

database_migrations

Connector-owned schema migrations. Capability version: 1.0. Mode: extension. Package files: EnterpriseExtension.php.

scheduled_workers

Connector-owned scheduled/background workers. Capability version: 1.0. Mode: extension. Package files: EnterpriseExtension.php.

conflict_resolution

Two-way sync conflict strategy. Capability version: 1.0. Mode: extension. Package files: EnterpriseExtension.php.

⚠️
Ufafanuzi wa wajenzi unabaki chanzo cha mamlaka. Weka sheria za biashara maalum ya jukwaa katika pointi za upanuzi zilizozalishwa; mfuko wa maisha, foleni, wafanyakazi, uhamiaji na vipimo vya kufanana vinabaki kusimamiwa na Wajenzi.

Kutathmini hali ya kila hatua

Ustaadhi wa

Ni mara ngapi kwa retry wito kushindwa, na backoff kwamba mara mbili kila jaribio. Tu timeouts, 429s na 5xx makosa ni retried; 4xx ni ombi lako kosa na kurudia itakuwa tu kuchoma kiwango chako kikomo.

Kiwango cha ukomo

dari kwa dakika kwa hatua hii, hivyo trigger busy hawezi nyundo jukwaa yako. kuondoka ni katika 0 kwa hakuna kikomo.

Muda wa

Ni muda gani wa kusubiri kwa ajili ya tovuti yako kabla ya kuacha.

Uthibitisho wa

Unahitaji mtu kukubali kabla ya hatua anaendesha. kuitumia kwa chochote uharibifu.

Aina za Uthibitishaji

Hatua ya hatua 2 Chagua moja ambayo inafanana na jukwaa lako API Nyaraka, jenereta hutoa mteja sahihi wa HTTP kwa hiyo.

API Kichwa cha kichwa

Kibodi ya tuli iliyotumwa kama kichwa cha kudumu, kwa mfano X-API-Key. Unapeana jina la kichwa na lebo fomu ya admin inapaswa kuonyesha. Hii inatuma ufunguo kama kichwa tu; ikiwa API inatarajia ufunguo kama parameter ya swala badala yake, tumia vichwa vya Custom au kiunganishi kamili cha msimbo.

Bearer alama

Token sent as Authorization: Bearer <token>. Common for modern APIs.

Msingi wa Auth

Jina la mtumiaji na nenosiri, msingi wa 64-encoded katika kichwa cha idhini. Unachagua lebo zote mbili za maeneo zinaonyesha kwenye fomu ya admin.

HMAC- aliyopewa

Ufunguo wa umma pamoja na siri, na mwili wa ombi uliosainiwa. Unampa kichwa cha saini, kichwa muhimu na kichwa cha wakati unaotarajia jukwaa lako.

OAuth 2.0 (Taasisi za Kielektroniki)

Server-to-server, bila mwingiliano wa mtumiaji na hakuna kuelekeza. Unatoa ishara URL na wigo wa hiari; admin hutoa kitambulisho cha mteja na siri. Tumia hii wakati jukwaa lako linashughulikia hati za maombi badala ya mtu.

OAuth 2.0 (Sauti ya button)

Kodi ya simu kwa kutumia PKCE, kwa Stripe. Shopify, Slack na QuickBooks-style programu. wewe kutoa idhini URL Kwa hiyo, hoja URL na upeo. Baada ya kuchapisha, admin clicks Connect juu ya kontakt, kuidhinisha kwenye jukwaa lako, na OpsIQ Hifadhi ishara ya kuburudisha na mints kupata ishara juu ya mahitaji. redirect URI Jisajili kwenye akaunti yako OAuth Programu inaonyeshwa kwenye ukurasa wa mipangilio ya kontakt.

Viongozi wa kawaida

A bure-umbo JSON header ramani kwa kitu chochote mifumo hapo juu si cover, kwa mfano {"X-API-Key":"{api_key}","X-Tenant":"{tenant_id}"}. Kila placeholder inakuwa uwanja juu ya fomu admin.

💡
PKCE inatumika kwa mtiririko wa Connect-button tu. Mtiririko wa wateja hauna mwelekeo na hakuna hatua ya mtumiaji, hivyo PKCE haitumiki kwake.

Mavazi ya kichwa

Ofset

Matumizi offset na kikomo vigezo. Mfano:? Offset =100 Kiwango 50.

Ukurasa wa ukurasa

Tumia nambari ya ukurasa. mfano: ?page =3Ukurasa wa wavuti = ukurasa 50.

Kionyesha

Tumia ishara ya mshale kutoka kwa majibu ya awali.

Link ya kichwa

Tumia kichwa cha majibu ya Link na rel "next".

Msimbo wa PHP

kontakt. php ReTURNS mfano. Haitangaza darasa lililoitwa kwamba OpsIQ kuwinda kwa. majina ya njia hapa chini ni yale ConnectorInterface inahitaji; kupata moja mbaya ni mauti katika mzigo, sio onyo.

php - mkataba wa kweli, mdogo na unaoweza kutekelezwa
<?php
/* connectors/myplatform/connector.php */
declare(strict_types=1);

use OpsIQ\Connectors\AbstractConnector;

require_once __DIR__ . '/Client.php';

return new class extends AbstractConnector {

    /* ── the three identity methods. NOT identifier()/label(). ── */
    public function slug(): string        { return 'myplatform'; }
    public function name(): string        { return 'My Platform'; }
    public function description(): string { return 'Orders and customers from My Platform.'; }

    public function capabilities(): array { return ['actions', 'context']; }

    public function settingsSchema(): array
    {
        $f = __DIR__ . '/settings.json';
        if (!is_file($f)) return [];
        $j = json_decode((string)file_get_contents($f), true);
        return is_array($j['settings'] ?? null) ? $j['settings'] : [];
    }

    /* ── NOTE THE ARGUMENT. testConnection() with no parameter is a fatal. ── */
    public function testConnection(array $settings): array
    {
        try {
            $resp = \OpsIQ\Connectors\MyPlatform\Client::callWithSettings($settings, 'GET', '/me', [], []);
            $code = (int)($resp['http_code'] ?? 0);
            return ($code >= 200 && $code < 300)
                ? ['success' => true,  'info'  => ['message' => 'Connection OK', 'http_code' => $code]]
                : ['success' => false, 'error' => "Verify endpoint returned HTTP $code"];
        } catch (\Throwable $e) {
            return ['success' => false, 'error' => 'Test failed: ' . $e->getMessage()];
        }
    }

    public function onEnable(array $settings): array  { return ['success' => true]; }
    public function onDisable(array $settings): array { return ['success' => true]; }

    public function handleWebhook(array $payload, array $headers, array $settings): array
    {
        return ['success' => true, 'note' => 'No triggers declared.'];
    }

    /* Inherited from AbstractConnector: reads actions.json for you.
     * Override only to ADD actions the manifest cannot express. */
    public function registerActions(array $settings): array
    {
        return parent::registerActions($settings);
    }
};
⚠️
Three things that fatal at class load rather than failing gracefully. The identity methods are slug(), name() and description() — not identifier() and label(). testConnection() TAKES an array of settings; a no-argument version is an incompatible signature. And there is no $this->http() or runAction() on AbstractConnector — HTTP goes through your own Client.php or through an action declared in actions.json.

tiketi za ndege katika mfumo wa tiketi ya asili

Wakati jukwaa lako linamiliki tiketi, kioo ndani ya OpsIQ kutoka kwa kontakt yako kutumia kiunganisho chako cha tikiti (kuunda kwa tiketi mpya, kuongeza-reply kwa ufuatiliaji). subscribers() Kwa njia ya mbinu, ticket.created, ticket.replied, ticket.updated, ticket.deletedKwa kujitegemea, kuongezeka, SLA na CSAT zote zinakubaliana na matukio sawa, kwa hivyo unawarithi bila msimbo wa ziada.

Kama wewe ni kufanya ticket.deletedPia, unashughulikia vipengele vya kuunganisha. Tiketi ya bure ya tiketi ya kuondoka merged_into na wala hakutumwa kwa mtu anayewasiliana naye ticket_merge- Kuwasili kwa ndege hiyo ni mara moja ticket.merged Badala yake, ili uweze kuunganisha kwenye jukwaa lako badala ya kufunga tiketi iliyounganishwa huko. Uwezo wa kuunganisha tiketi (Contract 2.4).

Nani aliandika ujumbe wa ufunguzi

Tiketi ni ya aina Kwa ajili ya ya wananchi, lakini ujumbe wa maandishi unaweza Wafanyakazi wa: wakala kufungua tiketi kwa niaba ya mteja, au kufikia hatua za mbele. Kila msaada wa kusaidia hii, hivyo ni sehemu ya ulimwengu wote ticket.created Mkataba badala ya kitu ambacho kila kontakt hutatua binafsi.

author_type

Mdhamini au mpokeaji; na mteja atachukuliwa.

author_id

Kitambulisho cha wafanyakazi wakati mwandishi_type =admin. Kamwe kitambulisho cha mteja.

author_name

Jina la ofisi au jina la kampuni linaanza na "kurudi".

author_email

Kamwe mteja mmoja. ujumbe wa wafanyakazi chini ya barua pepe ya wateja ni taarifa na ukaguzi kosa.

Hii sio ya kawaida ya vipodozi. Watumiaji wa kusoma author_type kuamua nani atakayembadilisha, barua ya wazi iliyoandikwa na mfanyakazi client Inaacha auto-reply haki ya kujibu ujumbe wakala wako mwenyewe aliandika, na inafanya echo jukwaa yako ya ufunguzi huo kuonekana kama ujumbe mpya wa wateja, ambayo kisha ardhi kama duplicate na flips tiketi kwa ajili ya kufungua. Majibu yajibuWeka ishara ya jukwaa lako kwenye hiyo katika kontakt yako Matukio ya kawaidaKamwe sio kwa watumiaji.

Kuzuia kwa msingi

Wakati wakala anazuia mtumaji, hii inatumika kwa Kila mmoja kila channel mara moja (barua pepe, chat, portal, widget na kila kontakt twin) kwa sababu block ni kutekelezwa katily, kabla ya kiunganishi yoyote anaona ujumbe. kontrakta wako kurithi ni kwa kufanya kitu. Hakuna kazi inbound kutekeleza na hakuna njia ya kupata hiyo vibaya.

Nusu ya uchaguzi ni KuondolewaKuambia jukwaa lako mteja alizuiwa hapa. Itumie tu ikiwa jukwaa lako linaweza kuonyesha kitu sawa.

Uwezo wa ()

Lazima ni pamoja na block_registry Na darasa lazima kutekeleza BlockRegistryInterface. bendera ni madai; interface ni dhamana. Usajili inahitaji wote wawili.

blockSender($b)

Inapokea aina (email | uwanja| ip), thamani, sababu, admin_id, expires_at, site_key. Rejea [matokeo, maelezo?, remote_ref?].

unblockSender($b)

Malipo sawa, kurejeshwa. lazima iwe ya malipo. Kuzuia kitu ambacho kamwe hakizuiwi ni noop, sio kosa.

isSenderBlocked($b)

Kwa ajili ya upatanisho, basi drift inaripotiwa badala ya kugunduliwa na mteja.

Matokeo ya Thamani

sawa

Tumia kwenye jukwaa lako. Jumuisha remote_ref wakati una rekodi ya thamani ya kumbukumbu.

noop

tayari katika nchi zilizoomba.

unsupported

Tovuti yako haina dhana sawa, sio makosa.

kushindwa

Unaweza kuwa alifanya hivyo na akaenda vibaya. pamoja maelezo; ni ardhi katika uchaguzi wa ukaguzi.

Kukataa ni jibu sahihi. majukwaa mengi hawana dhana "kuzuia hii ya kutuma" na kutoa tu kusimamishwa kwa ACCOUNT, ambayo inaacha bili, logins na huduma badala ya barua ya msaada. Kupiga " wakala alizuia anwani ya spam" kwenye "kufunga akaunti ya mteja huyu" ingeruhusu kizuizi cha mtu kilichopigwa marufuku kusitisha huduma za wateja wa kulipa. Ikiwa hiyo ndio lever pekee unayo, kurudi unsupported Acha tu hii iondoke.

Pia, suala la ukusanyaji wa mapato linahusisha maeneo ambayo Inaweza kuwa Fanya hivyo lakini usiruhusu. - Angalia kwa makini API, si kipengele: lever ambayo ipo tu katika admin jukwaa UI ni lever yako kontakt haina.

Mfano wa kazi · Zendesk (utekelezaji wa kumbukumbu)

Soma connectors/zendesk/connector.php alongside this. It is short, and every branch below is a decision you will face too.

email ya barua pepe→ya ok ok

ya wa /api/v2/users/{id} Maombi mapya ya mtumiaji wa mwisho yanaelekezwa kwenye Tiketi zilizosimamishwa badala ya kufungua moja, kwa kweli wazo sawa na kuzuia mtumaji, na haikatai bili kwa sababu watumiaji wa mwisho wa Zendesk hawana.

uwanja → unsupported

Zendesk inaweza kusimamisha kikoa kizima, lakini tu kwa njia ya kusimamisha: neno la msingi katika maandishi ya blocklist ya Kituo cha Admin, na hakuna API anaandika uwanja huo. Kipengele hicho kipo; lever haipo.

ip →bila ya kuungwa mkono

Hakuna kiwango cha tiketi IP Kuna block moja kwa moja.

Anwani isiyojulikana→ya noop

Zendesk haiwezi kutumia anwani ambayo haijawahi kuona. Hakuna cha kufanya sio kushindwa, na kizuizi cha ndani bado kinaacha tiketi.

Mkurugenzi au msimamizi→bila ya kuungwa mkono

Wafanyakazi wa kuacha kazi watafunga mfanyakazi mwenzake nje ya Helpdesk. Anwani ya wafanyakazi kufikia orodha ya block ni zaidi uwezekano wa kuwa makosa kuliko maelekezo, angalia jukumu kabla ya kutenda juu yake.

Mstari huo wa mwisho ni moja ya thamani kuiga. Mkataba hauwezi kukuzuia kupanga kizuizi kwenye kitu cha uharibifu, kwa hivyo kila kontakt ina kuamua yenyewe nini itakataa. Kukataa kwa sauti kubwa, na detail Mtu anaweza kusoma, anakataa kutii.

Taarifa kwa uhakika. Angalia jinsi baadhi ya vipengele hivi ni okHiyo ndiyo matokeo sahihi, sio pengo: kizuizi cha kikoa bado kinafanya kazi (inatekelezwa kwa msingi wakati imeandikwa); haiwezi kuonekana nje. ok Kwa kitu ambacho haukufanya ungemwambia mwendeshaji kizuizi hicho kilifikia jukwaa lako wakati haujawahi kushoto OpsIQ.

Kanuni za

Timu ya taifa daima inashinda

Ni imeandikwa kabla ya kuitwa na anasimama chochote wewe kurudi. Huwezi kuzuia operator kuzuia mtu.

Kamwe usiwahi kuwa na

Kutupa ni kutibiwa kama unsupported na kumbukumbu. Kurudi kushindwa kwa undani badala yake hivyo sababu haiishi.

Kuwa na uwezo wa kulipa

Orodha hiyo inaweza kupitiwa zaidi ya mara moja.

Kurejea haraka

Fan-out ni synchronous na operator click. Queue polepole kazi badala ya kufanya ombi wazi.

Usirudi nyuma kwenye

Kamwe usiingie tena kwenye OpsIQ kutoka kwa msimamizi wako. Usajili unaruka kontakt ya asili, lakini hop ya pili itafunga.

Kila barua pepe inatumwa kwa opsiq_block_registry_log (utendaji, aina, thamani, sababu, admin, asili, slug ya kiunganishi, matokeo, maelezo na timestamp) ili operator anaweza kuona block aliwasili kutoka jukwaa lako badala ya kutoka kwa wakala, na kile kila kontakt alifanya kuhusu hilo.

Kuwasilisha nyaraka kwa usahihi

Mkono wa attachments safu ya kuunda ()/addReply(). kila kitu hubeba faili katika moja ya maumbo matatu:

content_b64

Msingi wa 64 ya faili ya RAW, matumizi kwa faili nyuma auth (visa vingi vya inbound). OpsIQ inaipa na re-hosts faili kwako. sura inayozunguka zaidi.

url Chanzo cha URL

Umma https URL (kwa mfano maudhui ya Zendesk_url) lazima iwe https; hupita SSRF / ruhusu ya ukaguzi kabla ya kuhifadhiwa.

stored_path

Kumbuka faili iliyohifadhiwa tayari uliyoandika (kile ambacho mtunzi wa asili hutoa).

Items also accept filename, mime_type and size_bytes. Caps: 12 MB/file, ~24 MB total, 10 files per call. Most platform read APIs return attachment Majina ya pekee (si kwa vidole), hivyo muundo wa kuaminika ni: soma vitabu ambapo msimbo wako tayari unaendesha (ndani ya jukwaa, au kutoka kwenye mzigo wa malipo ya mtandao), uwaweke 64, na uwachukue kama content_b64 juu ya tukio hilo.

Kuwa nje (OpsIQ →jukwaa yako). Wakati mtu anafungua akaunti, ticket.replied Mgawanyo wa fedha unakupa majibu kama stored_path Mambo yaliyo chini ya OpsIQ Hifadhi ya faili.soma na kushinikiza katika muundo wa jukwaa lako mwenyewe, na angalia docs za jukwaa, mambo ya encoding: WHMCS Mahitaji ya base64_encode(json_encode([[name,data]])) (JSON, si serialize; Zendesk uploads ghafi bytes kwa /uploads.json Kwa ajili ya kupanda mbegu, comment.uploadsGmail yatuma RFC yenye mchanganyiko wa sehemu nyingi 822 Ujumbe wa msingi wa 64url-encode katika raw; Amazon SES inbound attachments need the S3 receive action (the SNS path caps at 150 KB).

majukwaa ya mbali: API + webhook, kamwe meza nyingine app

Kama una jukwaa la Programu ya bure au database (Sauti ya SaaS, kijijini WHMCS, DB tofauti kwenye seva moja), Kamwe kuandika barua ya moja kwa moja: msingi wa data ya msalaba kuandika ardhi juu ya uhusiano wowote ni kazi na kimya miss safu halisi. Kuondolewa *Kuwasilisha fomu ya maombi iliyosainiwa API (Masaa, hali, idara, kufuta); Ndani ya *Asema kuwa mtandao wa intaneti umesajiliwa, kampuni yake handleWebhook() Kuthibitisha na kuzima moto ticket.* tukio. Ili kuacha kitanzi kioo, tag nini kushinikiza na alama ya asili (kwa mfano). mirror_origin:'opsiq'); jukwaa linairudia kwenye wavuti na msimamizi wako wa ndani anaruka echoes zake mwenyewe. OpsIQEvents::isMirroredEvent() Juu ya kila mchezaji.

Picha ya Mirror, priority & idara

Majibu ya moja kwa moja yanabadilisha hali, na Wakala wa Agent Majibu ya majibu→ answered, a Wateja wa wateja Majibu ya majibu→ customer_reply-Kuona kwamba kwa njia hiyo, mabadiliko ya wazi yanajiunga na ticket.updated Kuwa kusoma payload['changes'] (Kwa mfano, {status:'closed'}).

Hali ya: OpsIQ Mpango wa Kanal Istanbul ni open, customer_reply, answered, in_progress, pending, closedWeka ramani ndogo ya njia mbili kwenye msamiati wa jukwaa lako, na hakikisha safu yako inakubali maadili unayoandika (anwani ya barua pepe). ENUM Kukosekana kwa thamani kunapungua kimya na databases baadhi). Idara ya: Kwa kuwa OpsIQ Kwa upande mwingine, hakuna maana kwa upande wako. Kamwe usiruhusu(a) Kuwasilisha nyaraka za uwongoname, email Na kwa kuwa slug(i) Kutatua tatizo hilo kwa kutumia barua pepe→Jina la jina→ya fedha, na hivyo “kuwekeza” katika sekta yako ya wa Serikali badala ya kuwa na Jenerali Mkuu• Kuingiliana kwa pande zote mbili ticket.escalated Aidha, a department_id Mabadiliko katika ticket.updated.

💡
Hadhi / kipaumbele / mada / idara / kufuta mirroring ni gated na toggles kwa kila-connector (mirror_status_changes, mirror_priority_changamoto, Mirror_Subject_Changes, Mirror _Department_Change, Mirror # delete) kusoma kupitia pamoja OpsIQ\ Connectors \ MirrorOptions msaidizi. Embed kwamba kuzuia katika mipangilio yako.json na kila tiketi-mirija connector anasoma toggles identically.

Kuunganishwa na tiketi kwa bidhaa / huduma

Ikiwa mteja alichagua bidhaa maalum wakati wa kufungua tiketi, stamp ladha hivyo wakala anaona kadi ya huduma iliyozingatia (kwa kubonyeza moja "angalia bidhaa nyingine" kwa wengine).

related_service_id

Preferred: the service id exactly as it appears in your IdentityProvider::lookupCustomerServices() list (each service's id). Unambiguous match.

related_service_label

Mfumo wa huduma ya jukwaa, kwa mfano. WHMCS 396 (Huduma ya Huduma)396) / D11 (domain)11). OpsIQ Decomposes aina ya hiari-letter + id na mechi orodha yako ya huduma, na ulinzi wa aina hiyo msimbo wa kikoa kamwe mechi bidhaa ya ID moja. Expose ref inayolingana kwenye kila huduma kwa ajili ya mechi halisi.

related_domain

Jina la kikoa; linalolingana na kama kizuizi dhidi ya maelezo ya kila huduma / uwanja.

💡
Kujenga orodha ya kiungo mara moja, katika sura hapo juu, na OpsIQ anashughulikia mapumziko: mwenyeji URLs ni kupita kupitia na maudhui base64 ni kuhifadhiwa na tena-hosted kwa ajili yenu. Huwezi kamwe haja ya kuandika kila jukwaa faili usimamizi.
⚠️
Funguo za hatua ni barua za chini, tarakimu na inasisitiza. Mjenzi anapokea3Kwa ajili ya80wahusika na pia inaruhusu dots; duka la hatua linakubali2Kwa ajili ya100wahusika bila dots, hivyo kuweka kwa barua, tarakimu na inasisitiza na wewe kukidhi wote. Kuongeza hatua inajenga hakuna AJAX njia, hivyo hakuna kitu cha regenerate - re-save kiunganishi na ni synced.

Kuumba kwa ajili yako

Huna haja ya kujaza hatua sita kwa mkono. Eleza kiunganishi katika maneno yako mwenyewe naOpsIQAI inaandika maelezo yote, huendesha kwa njia ya halali sawa ambayo mchawi hutumia, na hukuonyesha mpango kabla ya kitu chochote kilichoandikwa diski. Kuna maeneo mawili ya kufanya hivyo, na huzalisha mfuko huo.

Mchawi wa ajira tunaye wenyewe

Kufungua Kuunganisha→Kuongeza kontakt→Kujenga Link ya KuunganishaJuu ya hatua1utaona kuwa ✨Kujenga kwa ajili yangu· Jinsi ya kutumia simu za mkononi, ni nini OpsIQ Lazima kusoma na nini cha kuandika, na nani anayetumia - kuongeza API mizizi kama unajua, na vyombo vya habari ni. mchawi kujaza kila hatua kutoka rasimu, na wewe mapitio na hariri hasa kama alikuwa ameunda 6 Kamati hiyo inaonekana kama ✨Kufikiria juu ya AIKwa hivyo unaweza kuomba mabadiliko (pia soma ankara) badala ya maeneo ya uhariri.

Kwa kuulizaOpsIQ

Kufungua Kuuliza maswali OpsIQ copilot mahali popote katika admin na kusema nini unataka. Wewe kamwe haja ya jina hatua au kujua mchawi ipo.

1
Kuuliza yake

Kwa mfano: "Nijenga kontakt kwa Trello. Ni lazima orodha ya bodi yangu na orodha, kusoma kadi, na kujenga kadi kwenye ubao. Trello anatumia ufunguo wa API." Kuundwa kwa Link hii Kadi. Ujumbe wako ni mfupi, hivyo kuweka jukwaa, kusoma na kuandika ndani yake.

2
kuthibitisha rasimu ya

Hakuna kitu kilichoandikwa bado. copilot rasimu ya maelezo, kuhalalisha ni, na majibu kwa mpango: nini kontakt inafanya, vitendo itakuwa wazi (inaandika alama), mawazo alifanya, na maswali bado una kujibu - kawaida ambayo sifa za kutoa. rasimu ni imesimama chini ya kitambulisho na anakaa inapatikana kwa ajili ya24masaa ya.

3
Sema “Kuwatengeneza”.

Kamati ya Utendaji inaonyesha kuwa Kujenga card naming the connector and its slug. This one writes: it publishes the package into /connectors/<slug>/. Confirm it and you get the path back, together with the setting you still have to fill.

4
Kuingia katika sifa na kuwezesha

Kiunganisho kipya kinachapishwa lakini hakiwezeshwa, na haina siri. Fungua mipangilio yake, ingiza ufunguo wa_ API au ishara, vyombo vya habari Jaribio la majaribioKwa hiyo, kwa kuwezesha“Ukiendelea kufanya hivyo, hakuna chochote.

💡
Kadi zote mbili zinahitaji click yako. rasimu hatua anaandika chochote wakati wote; kujenga hatua ni alama uharibifu na daima anauliza. AI haiwezi kuchapisha kontakt, kuwezesha moja, au kuingia credential juu yake mwenyewe.

Nini na nini cha kufanya na si kuruhusiwa

Mwenyeji ni The Wall

Ufafanuzi ulioandikwa unapitisha uthibitisho sawa () kifungo cha kuchapisha cha mchawi hutumia. Ikiwa hakitapita, AI imepewa makosa na inajaribu tena, hadi mara tatu, na kisha hukataa katika maneno ya validator mwenyewe. rasimu ambayo inashindwa kuwa mfuko.

Hakuna hati ya utambulisho

Rasimu ya majina muundo wa uthibitishaji na mashamba ya mipangilio; kamwe hubuni ufunguo, ishara au siri. Unajaza wale baadaye kwenye ukurasa wa mipangilio ya kontakt.

Majibu ya maswali, si kwa hoja

Kitu chochote ambacho hakikuweza kujua – utambulisho wako wa akaunti, eneo ambalo kati ya maeneo mawili huainisha mpango wako unafichua—hurudi kama swali juu ya mpango badala ya dhana ya kimya.

Kuvunjika kwa moyo kunashindwa kabisa

AI inaambiwa kamwe sio kuunda njia, lakini hakuna mfano ni kamili. Njia isiyo sahihi huchapisha kama hatua ambayo inashindwa mtihani wake wa kuishi kwenye Hatua au mara ya kwanza inaendesha - sio mafanikio ya kimya.

Mfumo huu ni wa kawaida

Nini hutoa ni mfuko wa kawaida wa Mjenzi: faili sawa zinazozalishwa, mkataba huo, saini hiyo, inayoweza kuhaririwa katika mchawi, iliyosababishwa na ukurasa wa Waunganishaji. Hakuna aina tofauti ya "Ikontakt".

Mfumo wako wa kuandika

Ubora hufuata mfano uliosanidiwa chini ya Mipangilio → AI. Rasimu ndogo, za mtindo wa bei nafuu kontakt sahihi lakini wazi na huuliza maswali zaidi; mfano wenye nguvu hupata zaidi ya vituo vya mwisho mara ya kwanza.

⚠️
Copilot inaweza tu kuendesha vitendo hivi kufunga hii kweli imesajiliwa. Kama Connector Builder vitendo ni kukosa - mpango ambao haujumuishi yao, au jukumu bila ya kuwa na. manage_connectors - copilot inasema hivyo badala ya kutoa kadi ambayo itashindwa wakati clicked.
Viunganishi

Kuuza kupitia chat: Biashara jukumu ramani

kontakt ambayo inaweza kuuza - jukwaa la kuhifadhi, mfumo wa uhifadhi, lango la malipo - linatangaza ni nani wa shughuli zake za Own kujibu OpsIQmajukumu ya biashara ya canonical. kutangaza na kontakt inaonekana chini ya Mipangilio → Wateja wa Chat → Kuuza kupitia chat moja kwa moja; kuacha kutangaza na kutoweka. Hakuna orodha ya kujiandikisha juu.

Faili ya faili: commerce_roles.json

Taarifa hiyo inaishi katika faili yake mwenyewe kwenye mizizi ya mfuko - Uwepo wa faili ni madaiHaiwezi kuishi katika connector_contract.jsonFaili hiyo inazalishwa tena na zana za ufungaji na schema yake inakataa funguo zisizojulikana, kwa hivyo kizuizi cha kuongeza mkono kitashindwa kuthibitisha na kisha kuandikwa zaidi.

commerce_roles.json
{
  "commerce": {
    "roles": {
      "catalog_search": { "operation": "acme_search_products", "transport": "http" },
      "customer_lookup": { "operation": "acme_customer_lookup", "transport": "http" },
      "quote":          { "operation": "acme_quote_order",     "transport": "http" },
      "payment_methods": { "operation": "acme_payment_methods", "transport": "http" },
      "order_get":      { "operation": "acme_get_order",       "transport": "http" },
      "order_create":   { "operation": "acme_create_order",    "transport": "http",
                          "recovery": "acme_get_order" }
    },
    "customer_ordering": {
      "enabled": true,
      "version": 1,
      "mode": "direct_order",
      "audience": "clients_only",
      "account_flow": "existing_client",
      "payment_flow": "connector_methods",
      "identity_parameter": "external_customer_id",
      "quantity_parameter": "quantity",
      "label": "Acme Store",
      "checkout_hosts": [],

      "transaction_kind": "purchase",
      "decision_mode": "immediate",
      "payment_timing": "on_confirmation",
      "reversibility": "reversible",
      "cancellation_flow": "platform_only",
      "fulfilment_presence": "remote_delivery",
      "notify_flow": "platform_automatic",
      "customer_fields": {"name": "required", "email": "required", "address": "required", "phone": "optional"},
      "client_tools": ["catalog_search", "catalog_get", "quote"],
      "account_timing": "before_quote"
    }
  }
}

Sheria na kwa nini kila mmoja

Kazi ni msamiati wa karibu

OpsIQKamwe usiruhusu jukumu kutoka kwa jina la kitendo. Jukumu ambalo halijatangazwa halipo - kutangaza ni mkataba wote.

Kazi yako lazima iwe moja ya kazi zako

Kila kazi ya mikono lazima iwe katika mikono yako actions.json. typo anatangaza uwezo kwamba haiwezi kukimbia, na ni uso kwa mteja kama "Ninaweza kuangalia kwamba kwa ajili yenu" kufuatiwa na kitu chochote.

Kazi ya kusoma kamwe haileti maana katika operesheni ya uharibifu

Soma majukumu (upatikanaji, quote, utaratibu wa kuangalia) lazima ramani ya shughuli ambazo hazibadili chochote kwenye jukwaa lako.

Jukumu la kuandika kamwe ramani kwa operesheni ya rekodi ya kawaida

Mapping ya order_create Kwa upande wake, Mbunge wa Jimbo la Ludewa Mhe. record.create, db.insert, recordCreate, spelling yoyote, separator yoyote - ni kukataliwa kimuundo. mstari imeandikwa moja kwa moja bypasses jukwaa yako ya bei, kufunga hisa na uthibitisho barua, kuzalisha utaratibu mfumo wako mwenyewe haamini kabisa katika.

Kazi ya kuandika inatangaza operesheni ya kupona

Kuangalia kwa heshima ambayo hujibu "je, kuandika ardhi yangu?". wakati hatari zaidi ni moja baada ya jukwaa lako tayari limeunda utaratibu; bila kuangalia upya chaguzi pekee ni kujaribu kipofu au kupoteza.

Malipo ya malipo ya mtoa huduma yana majukumu matatu ya ziada

Mfuko ambao unazungumza moja kwa moja na mtoa huduma wa malipo lazima pia kutangaza payment_profile (Masaa, nchi, mbinu na Mazingira ya mazingira - mazingira yasiyo na hali ni jinsi ushirikiano wa mtihani unachukua malipo ya moja kwa moja), webhook_verify (Mpango wa saini halisi ya mtoa huduma; ushindani wa siri wa kawaida unakataliwa) na event_map (matukio ya kutoa kwenye wale wa Canonical). kontakt ya mfanyabiashara ambayo inatumika tu record_payment Inapokea ushahidi wa malipo ya kisheria tayari; haipaswi kujifanya kuwa mlango.

Kueleza jinsi wateja wanaweza kuagiza kutoka kwa duka linalounganishwa

Munganisho wa biashara na kontakt ya njia ya malipo ni mikataba tofauti. Kuunganishwa kwa Huduma ya Wateja wa KampuniChagua hali ya kina zaidi ambayo jukwaa linaweza kuthibitisha. chaguo limewekwa ndani ya saini commerce_roles.jsonHifadhi na Mteja Chat upya kusoma wakati wa utekelezaji. Kuondoa jukumu au mlemavu / uninstalling kontakt hivyo invalidates pendekezo lililotolewa hapo awali badala ya kuacha mamlaka ya stale nyuma.

catalog_only

Ramani za ramani catalog_search au catalog_get. OpsIQ inaweza kutafuta na kuelezea bidhaa, lakini haiwezi kuonyesha utaratibu wa kupunguzwa au uthibitisho wa checkout. Kila kifurushi kinabaki kwenye default hii ya kweli mpaka quote yake mwenyewe iliyoorodheshwa na vitendo vya Checkout / kuagiza kupita mkataba zaidi na vyeti vya Soko; kamwe msaada wa shughuli kutoka kwa jina la jukwaa.

platform_checkout

Pia ramani quote Na kwa kuwa platform_checkoutBiashara ya biashara - sioOpsIQMsingi wa Kurejea checkout_url, checkout_reference Na kwa mujibu wa kanuni ya Canonical quote.URLLazima uwe na HTTPS, jina la mwenyeji lazima lifanane customer_ordering.checkout_hosts au mwenyeji wa HTTPS inayotokana na checkout_host_settingNa kwamba, unaweza kuishi kwa ajili ya si zaidi15Dakika. bidhaa permalink, gari la ndani lililokusanyikaURLau kurudi nyuma.URLSio uwezo wa ukaguzi wa biashara.

direct_order

Pia ramani quote, order_create Na kwa kuwa order_getKwa kuwa order_create.recoveryCore inaburudisha nukuu mara moja kabla ya utekelezaji, hutoa ufunguo wa idempotency, na anauliza operesheni ya kupona baada ya kila matokeo yasiyojulikana kabla ya jaribio lolote. payment_flow=opsiq_gatewayNi lazima kuongeza ramani record_payment Kwa ufanisi wa kufufua / kurudi nyuma. OpsIQ inathibitisha kikamilifu shughuli ya lango, kiasi cha mechi, sarafu, mfanyabiashara na kumbukumbu ya utaratibu, anaandika kumbukumbu ya mtoa huduma mara moja, kisha anasoma ankara ya biashara / agizo la nyuma. mark_invoice_paid Kuingiza hali ni kukataliwa kwa sababu haina ushahidi wa malipo. hatua ya kuunda lazima iombe bei ya jukwaa mwenyewe, hisa na mantiki ya biashara; database ghafi inakataa.

Kuthibitisha utambulisho, na nini operator inaweza kubadilisha

Wakati ambapo wakatiOpsIQKumiliki malipo, chat mteja lazima kufikia email_otp kabla ya kuanzishwa kwa Mfuko huo.OpsIQBarua pepe ya A6msimbo wa tarakimu na anauliza kwa hilo. Hii si kitu ambacho kontakt huchagua nje; ni sakafu ya uhakika mahitaji ya kernel ya utekelezaji order_create.

Ni nani aliye na mamlaka ya pekee, na ni nani anayetawala

operator inaweza kukubali anwani unverified tu ambapo kontakt yako alitangaza fulfilment_presence: customer_presentMgeni wa hoteli lazima awasili, kwa hivyo anwani isiyofaa huelekeza risiti na chumba bado kipo. remote_delivery - kusafirishwa, kutolewa, kupakuliwa-na uhakiki unahitajika chochote operator seti, kwa sababu thamani majani juu ya nguvu ya anwani hiyo peke yake. minimum_assurance au reversibility: irreversible Pia inaondoa uwezo wa mtumiaji wa kuacha.

Muda gani wa kutumia msimbo

Dakika ya 30 kwa default, operator-kusanidiwa kutoka5Dakika moja kwa24Kwa upande mwingine, mteja anaona kuwa kuna hesabu ya moja kwa moja iliyotolewa katika yao wenyewe Wakati wa eneo, si operator. msimbo wa muda mrefu unasema wazi sana na hutoa mpya badala ya kuripoti code batili - mteja kuandika sahihi lakini-mzee kificho imefanya makosa, na kuwaambia kuwa wamewatuma pande zote kitanzi sawa.

Nini wateja wanapaswa kutoa: Wateja_fields

Jina na barua pepe ni daima required na ni zilizokusanywa kwanza. address, phone Na kwa kuwa company as required au optional Ili kufaa biashara: duka ambalo meli vifurushi vinatangaza anwani inayohitajika; hoteli inatangaza simu inahitajika, kwa kuwa mgeni hawezi kuwasiliana na uhifadhi. Msaidizi anawauliza katika mazungumzo kabla ya kunukuu, na OpsIQ amekataa kuweka amri ambayo haina uwanja unaohitajika. mjenzi anaandika ramani iliyoboreshwa, msingi ni pamoja, hivyo mkataba kwenye diski ni wazi.

Wakati wa kujenga akaunti,

at_order (default) inaruhusu amri kuandika kuunda akaunti ya mnunuzi wa mara ya kwanza. before_quote Wakati wavuti yako iko tayari -WHMCSkodi na profile ya mteja mwenyewe na quotes katika sarafu ya mteja - naOpsIQUnda akaunti yako kwa kubonyeza hapa customer_create hatua mara tu mashamba required ni maalumu, kisha anauliza quote kwa akaunti hiyo, hivyo kadi ya uthibitisho hubeba jumla wewe kweli ankara. account_flow: connector_signup.

Msaidizi huchota, haisomi: wateja_tools

Kwa kuunda amri, msaidizi kamwe kusoma catalog pasted. wito zana tatu - commerce_catalog_search ( swala tupu ni maelezo ya jumla ya familia za bidhaa; matokeo zaidi ya kikomo yameorodheshwa kwa jina), commerce_catalog_get kwa ajili ya jambo moja tu, na commerce_quote, ambayo mints saini kadi ya uthibitisho server-kwa njia ya kuta huo njia kiunganishi daima alikuwa. chombo kimoja kwa kitenzi, komponenti yako kama parameter, hivyo duka na viunganisho sita anapata zana tatu badala ya kumi na nane. client_tools Kukataa kwa kila kitu, na kukataa kwa kila mmoja. catalog_only kontakt kamwe quotes. uthibitisho ni kamwe chombo: kadi ya kifungo kwenye mtandao, halisi CONFIRM Amri kwenye channel, na hakuna mfano anasema anatumia fedha.

Nini cha kufanya na orodha yako ya bidhaa

id, nameKuwa salama kwa wateja summary, a category au familia ya bidhaa (hii ni jinsi neno la mteja linapata kipengee ambacho jina lake ni msimbo), currency, unit_amount_minor, availableKwa hivyo, na input_schema Kutafuta alama ya maneno ya mteja dhidi ya jina, familia, mzunguko na muhtasari.

Kukataa kwa sababu ambayo mteja anaweza kufanya

Kurudi kwa kurudi {"success":false,"error":"…","missing":["domain"],"retryable":true} Kama kuna makosa au ni makosa, basi majina hayo missing au retryable kufikia wateja verbatim; kushindwa wazi anakaa generic hivyo hakuna uvujaji wa ndani.

Fedha za Geo na Kituo cha Dharura

Wakati operator zamu juu ya Geo Fedha (Client Chat)→Behaviour), mteja anasoma bei katika sarafu yao wenyewe juu ya kila uso - maandishi ya kuzungumza, kadi ya wavuti, kadi za maandishi ya kituo na sarafu ya ufunguzi wa duka - kwa kutumia duka la jukwaa lenyewe la FX. Bei yako haijawahi kubadilishwa: kadi inaonyesha takwimu ya mgeni kando ya jumla ya duka, na taratibu za lango zinaonyesha kiasi gani. Kununua bidhaa zote (Settings → Biashara) ni kubadili kuua: catalog, quotes na kuangalia-ups kukaa wazi; kupendekeza na kuthibitisha kuacha juu ya kila channel.

Wakati wa kuuza kupitia chat si kufanya

Mfanyabiashara hawezi kufika

muhuri wa mfuko ni kuvunjwa: faili ilihaririwa baada ya kusainiwa. Re-kuchapisha mfuko. nakala imewekwa soko si kuhaririwa katika mahali; update kutoka jopo la soko.

Kuagiza ni kusimamishwa kwa ajili ya duka hili sasa

Mabadiliko ya kuua ni kwenye Mipangilio → Biashara → Pause uuzaji wote.

Maombi bado hayajatolewa kwenye channel hii

Kituo hakipatikani chini ya Ambapo wateja wanaweza kununua. jina la kumbukumbu la seva linaingia channel.

Mhudumu anataja kitu lakini hakuna kadi inayoonekana

Simu ya mkononi imezimwa, kila simu inaita kama [opsiq][commerce][client_tool] Kwa sababu: kitambulisho cha bidhaa isiyofaa, shamba ambalo kitu hakitangaza, kikoa kilichochukuliwa, au kukataa kwa mfanyabiashara mwenyewe. soma logi kabla ya kuamini paraphrase msaidizi.

Waziri Mkuu alisema kuwa hawezi kuona bidhaa

Ukurasa ni wa nafasi nyingine ya kazi. Kila widget tovuti ni ya workspace moja, na kontakt kuhifadhi lazima kuwezeshwa huko.

Majibu ya maswali badala ya majibu

"Niambie zaidi kidogo kuhusu kile unachohitaji" inamaanisha mtoa huduma wa AI anajiita ameshindwa; Historia ya AI inaonyesha kosa halisi chini ya zamu hiyo, na zana hazikufikiwa.

Kiunganisho cha kontakt hakionyeshi katika mazungumzo

Mfanyakazi hurekebisha mabadiliko ya msimbo ndani ya dakika, lakini mazungumzo yanabadilisha kadi yake ya mwisho.

Mtazamaji wa Nigeria aona dola licha ya kuwa sarafu ya Geo

Angalia hii ya geo-IPDatabase imesanidiwa (Client Chat)→Geo) na kwamba sarafu ya mgeni ina kiwango cha FX; bila kiwangoOpsIQInaonyesha bei ya duka badala ya idadi mbaya.

Kwa ujumla, ni takwimu pekee ambayo inabadilisha fedha

Maelezo ya mchezo Kutoroka unit_amount_minor, quantity Na kwa kuwa total_amount_minor, na ni kujaribu kutibu tatu kama derivable kutoka mbili za kwanza. Sio, na kudhani tayari ina gharama ya mteja halisi fedha.

quantity ni nini MTUmiaji alichagua - chumba moja, leseni moja, sera moja. multiplier yako inaweza kuwa kitu OpsIQ kamwe anaona: usiku, viti, mizunguko bili, umbali, uzito, ngazi. Hoteli quotes chumba moja kwa ajili ya usiku tatu kama wingi 1, kitengo 105,000jumla 315,000. OpsIQ kuzidishwa kitengo kwa kiasi cha bei kadi ya uthibitisho, alionyesha mgeni 105,000, na kisha kulipa. 315,000 mfanyabiashara kweli kurudi. Kukubaliana na takwimu moja na kuwa kulipa mwingine ni jambo mbaya zaidi mkataba huu unaweza kufanya.

Kanuni ya

total_amount_minor Hii ndio takwimu pekeeOpsIQkuonyesha, kuonyesha, mashtaka na kupatanisha dhidi ya. unit_amount_minor Ikiwa jumla yako sio kile unachotaka kushtakiwa, nukuu yako ni sahihi - OpsIQ haitarekebisha, kwa sababu jumla ambayo imerekebishwa kwa msaada ni moja ambayo haujakubali kuheshimu.

Nini maana ya quote yako

Tumia usiku wako mwenyewe, tiers, punguzo, kodi na ada kabla ya kujibu. Kama mstari wako haina kupatanisha — mara kadhaa idadi nzima kamwe sawa yako jumla - OpsIQ hushughulikia kitu kizima kama mstari mmoja kwa bei yake halisi badala ya kuunda kuvunjika ambayo inakubaliana na chochote.

6 majibu ambayo hufanya mkataba huu kuwa na kampuni yoyote

Tangazo hapo juu lilianza kama tangazo la duka: kununua kitu, kulipa sasa, ni yako, unaweza kufuta. Kila moja ya hizo nne ni dhana biashara halisi haishiriki. Benki inayohamia haiwezi kuivunja. bima hawezi kusema "imethibitishwa" mpaka mwandishi ameangalia. ankara za mfanyabiashara baadaye. Kliniki inamdai mtu ambaye sio mgonjwa. Kwa njia yoyote ya kusema hivyo, biashara hizo zinaweza kuwakilisha mchakato wao wenyewe kwa wateja wao au haziwezi kuunganisha wote.

Kwa hiyo, kampuni ya mawasiliano ya simu inajibu maswali mengine sita. Kila mmoja anashindwa kusoma kwa makini Kusema hakuna kitu ni salama na kamwe si cha kupuuza, kwa sababu kusema chochote ni kile mwandishi anafanya wakati hawajafikiria swali.

transaction_kind

purchase, booking, subscription, bill_payment, transfer, application, top_up, renewalVocabulary badala ya tabia: huamua neno mteja wako anasoma. Kuita uhamisho wa waya "amri" hufanya sauti ya msaidizi kama haijui biashara inayozungumza, na hakuna kiasi cha mabomba sahihi kinapona kutoka hiyo. Defaults kwa hiyo. purchase.

decision_mode

immediate au deferredChagua deferred Kwa chochote kinachoenda chini ya kuandika, tathmini ya mikopo, marejeo, kuingia au kamati. OpsIQ Imewasilishwa kwa Badala yake badala ya imethibitishwaKumwambia mtu maombi yao ni kuthibitishwa wakati yeye anakaa na binadamu ni kitu kuharibu zaidi chat msaidizi anaweza kufanya kwa ajili ya biashara kudhibitiwa, na ni tabia default ya kila rejareja umbo mtiririko. immediate.

payment_timing

on_confirmation, deposit_then_balance, invoice_later au no_paymentUamuzi huu utaamua kamaOpsIQKufungua ukurasa wa malipo Kwa ujumlaKwa hiyo, haiwezi kuondolewa kutoka kwa payment_flow - Hii inasema kuwa ambaye ni nani ambaye fedha hizo, alisema kuwa Wakati na wakati ganiKazi wewe ankara baadaye, na maombi ambayo gharama kitu cha kuwasilisha, kumaliza katika uthibitisho badala ya kufikia orodha ya lango kwamba ni tupu au makosa.

reversibility

reversible au irreversibleKitu muhimu zaidi kontakt ya kifedha inasema. chumba kinaweza kutolewa na sehemu inaweza kurudi; uhamisho uliokamilishwa hauwezi - hakuna undo, pesa ni mwisho mwingine, na dawa pekee ni kuuliza mgeni kuirudisha. irreversible Moja kwa moja nguvu cancellation_flow Kwa kuwa none na kuzuia mtu yeyote kuingia katika akaunti ya mpokeaji. Chochote ambacho tamko hili linasema· Maeneo mawili kutokubaliana sio hali ya kutatua wakati wa kukimbia na kila kitu kinachosomwa kwanza. reversible.

cancellation_flow

none, platform_only au connector_cancelMajukumu ya kufuta tayari yamekuwepo na hakuna utawala kuhusu nani anaweza kuwafikia, na nadhani mbili makosa kushindwa kwa maelekezo tofauti: nadhani wazi na ujumbe wa mazungumzo hufuta uhifadhi kulipwa bila ada iliyonukuliwa; nadhani imefungwa na mteja ambaye anataka kufuta ni aliiambia simu. connector_cancel Aidha, inahitaji cancellation_quote Na kwa kuwa order_cancel kwa hisani ya RaiaMwemaOpsIQKamwe usitoe ahadi za uongo kabla hujazitekeleza. none.

fulfilment_presence

customer_present au remote_deliveryIkiwa anwani ya barua pepe isiyothibitishwa inaweza gharama yoyote. Mgeni wa hoteli lazima awasili, kwa hivyo anwani isiyofaa inapotosha risiti na chumba bado kiko hapo; sehemu iliyowekwa, seva iliyopewa au kiungo cha kupakua kinaacha nguvu ya anwani hiyo pekee. Hii ndio inafanya ukaguzi wa barua pepe ya "skip" ya operator inapatikana wakati wote., na ni alitangaza na wewe badala ya kuchaguliwa na wao - hivyo hoja hoteli hawezi kurithiwa na kontakt kwamba meli bidhaa. remote_delivery.

minimum_assurance Na kwa kuwa disclosure (Sauti ya)

minimum_assurance Acha kuomba Zaidi ya zaidi Uthibitisho wa utambulisho kuliko OpsIQ unahitaji, sio chini - benki inayohitaji hatua ya uhamisho ni kufanya kazi kwa mkataba. Kuweka pia huondoa uwezo wa mwendeshaji kuruka uhakiki kwa kontakt yako, kwa sababu uamuzi wa hatari wa mfanyabiashara mwenyewe unaondoa urahisi wa operator. disclosure Maneno yaliyoonyeshwa Kabla ya kabla ya kabla ya kifungo kuthibitisha, kwa kiwango, ada au haki ya baridi-off lazima sasa; bila hiyo, biashara zinazodhibitiwa zinahitaji maneno katika jina la bidhaa.

notify_flow

platform_automatic, platform_triggered au noneWakati OpsIQ inachukua malipo yako ya checkout mwenyewe kamwe inaendesha, hivyo chochote ambacho kawaida barua pepe haziwaka moto. Rekodi ya malipo alama ya agizo lililolipwa; haizuii jukwaa la kumwambia mtu yeyote. platform_triggered Mahitaji ya order_notify jukumu na ahueni, na OpsIQ anauliza tu baada ya malipo kusoma-nyuma inathibitisha fedha ni kumbukumbu. none Hufanya uthibitisho wa upande wa OpsIQ lazima, kwa sababu vinginevyo mteja anayelipa hasikii chochote kabisa. none.

Biashara ya 9 isiyo na uhusiano

Hakuna yoyote ya haya walikuwa iliyoundwa karibu. Kila mmoja ni mkataba kujibu kwa uaminifu kwa sekta tofauti, naOpsIQHakuna anayejua kuhusu kila mmoja wao.

Kampuni moja, makampuni tisa
Hotel        booking      immediate  deposit_then_balance  reversible    -> payment page, "confirmed", identity may be waived
Online shop  purchase     immediate  on_confirmation       reversible    -> payment page, "confirmed", identity always verified
Bank         transfer     immediate  on_confirmation       IRREVERSIBLE  -> payment page, no cancel route, never waived
Insurer      application  DEFERRED   no_payment            reversible    -> no payment page, "submitted", never "confirmed"
Utility      bill_payment immediate  on_confirmation       IRREVERSIBLE  -> payment page, nothing to give back
Clinic       booking      immediate  invoice_later         reversible    -> NO payment page, billed afterwards
Tradesman    booking      immediate  invoice_later         reversible    -> NO payment page, invoiced on completion
Telecom      top_up       immediate  on_confirmation       IRREVERSIBLE  -> payment page, final once sent
University   application  DEFERRED   no_payment            reversible    -> no payment page, decision follows
Tukio la kulipwa linalotolewa kwenye majukwaa

Baada ya malipo ya asili ya Hifadhi imethibitishwa kikamilifu na kufanywa, OpsIQ hutoa payment.completed Pamoja na kuwa pamoja order_id, payment_id/provider_ref, gatewayKwa kweli, kwa amount_minorya ISO currencywateja, vitu vya mstari, channel na paid_at· Mdhamini wa biashara lazima awasilishe ushahidi huo kupitia record_payment na kusoma nyuma; kontakt ya ukaguzi wa mwenyeji hutumia tukio lake la kulipwa mamlaka na haipaswi kupokea barua ya malipo ya duplicate.

Ni kiongozi wa chama, si mtu anayetoa maoni

Mfano unaweza kuchagua bidhaa na wingi uliotangazwa, lakini haiwezi kuchagua jina la operesheni, mint checkout URL au kuunda hali ya biashara kutoka kwa maandishi. mteja anapokea kadi halisi iliyosainiwa na lazima a press button yake ya kuthibitisha. uthibitisho huo ni amefungwa kwenye nafasi ya kazi, kontakt, bidhaa, wingi, quote, sarafu, thread na expiry.

Wateja wa kijamii wanashikilia mtiririko huo bila barua pepe haraka

WhatsApp, Messenger, Instagram, Telegram, LINE, SMS na X kutumia mtoa-kuthibitishwa channel akaunti kama utambulisho wa mteja. mapendekezo ni kusainiwa kwa hiyo channel hifadhidata na kuthibitisha bado anaendesha kupitia quote safi sawa, hisa, idempotency, malipo na kurejesha vidhibiti. mteja kijamii hutumia hasa moja-time hatua ya kuthibitishia iliyotolewa katika mazungumzo yao; prosa kawaida kama vile “ndiyo” kamwe amri mamlaka.

Historia ya amri hufuata kiungo halisi cha utambulisho, kamwe nadhani barua pepe

Amri za asili zina indexed na utambulisho wa kituo cha opaque, kwa hivyo AI inaweza kujibu "hali yangu iko wapi?" bila kuuliza nambari ya barua pepe au agizo. Kwa historia ya duka iliyounganishwa, kuunganisha kitambulisho cha channel kwenye nafasi ya kazi CRM/ rekodi ya kawaida na kutekeleza ufuatiliaji wa mamlaka kwa mteja / utaratibu katika kontakt.Watoaji wa mazingira ya Wateja hupokea kiungo kilichohifadhiwa; hawapaswi kuchagua akaunti kutoka jina la kuonyesha au barua pepe iliyoingizwa kwenye mazungumzo.Kwa amri moja inayolingana AI hujibu moja kwa moja; na kadhaa inafupisha mechi na kuuliza ambayo moja; bila kusema historia haihusiani.

Fanya malipo ya jumla: mashamba yaliyopangwa na utambulisho wa seva

Core haina WHMCS, hoteli, SaaS, duka, benki, bidhaa, njia au tawi la muuzaji. parameters ni fomu ya wateja na Mpangilio wa Hifadhi ya AI. Mkontakt wa uhifadhi anaweza kutangaza tarehe na wageni; kontakti ya bili inaweza kutangaza mzunguko; mwasiliani wa biashara wa baadaye anaweza kutangaza maeneo yake salama.OpsIQSanitizes udhibiti wa asili na hutuma maadili yaliyokusanywa tu kwa hatua ya kontakt iliyowekwa.

Maelezo ya mchezo quote
{
  "action_id": "acme_customer_quote",
  "scope": "client",
  "is_destructive": false,
  "parameters": [
    {"name":"external_customer_id","type":"string","required":true},
    {"name":"item_id","label":"Product","type":"string","required":true},
    {"name":"quantity","label":"Quantity","type":"integer","required":true,"minimum":1},
    {"name":"cycle","label":"Billing cycle","type":"select","required":false,
     "options":[{"value":"monthly","label":"Monthly"},{"value":"annual","label":"Annual"}]}
  ]
}

Kwa ajili ya clients_only, kuweka customer_ordering.identity_parameter Kwa parameter ya hatua ambayo inapata kitambulisho cha mteja wa nje. uwanja huu haujaonyeshwa kwa mteja na thamani yoyote ya simu inayotolewa imeondolewa; OpsIQ inaingiza tu id kutoka kiungo kilichothibitishwa cha kontakt.

Maeneo ya pamoja: Akaunti za wateja zilizosainiwa na usanidi wa kontakt ni sehemu ya kazi ya msingi ya kikundi. Hata hivyo, ishara ya utambulisho lazima isainiwe kwa tovuti halisi ya mwanachama ambayo inaiga widget, kwa kutumia siri ya wavuti ya mwanachama huyo. OpsIQ inathibitisha kwamba uso kwanza na kisha tu hutatua biashara na mteja anayeunganishwa kupitia msingi wa kikundi. Kamwe ubadili ufunguo wa tovuti ya mwanachama na ufunguo wa msingi na kamwe usinakili siri ya msingi kwa tovuti ya wanachama.

Canonical bahasha ya kontakt lazima kurudi

Orodha ya
{
  "success": true,
  "data": {"items":[{
    "id":"42", "name":"Example product", "summary":"Customer-safe summary",
    "currency":"USD", "unit_amount_minor":2500, "available":true,
    "selection":{"item_id":"42"}
  }]}
}
Nukuu ya
{
  "success": true,
  "data": {
    "quote_id":"opaque", "currency":"USD",
    "unit_amount_minor":2500, "total_amount_minor":5000,
    "selection":{"item_id":"42","quantity":2},
    "expires_at":"2026-08-31T14:05:00Z"
  }
}

Majibu ya ukaguzi wa jukwaa hurudia quote halali ya canonical na inaongeza HTTPS checkout_urlCore inaburudisha nukuu wakati wa uthibitisho na kulinganisha sarafu, uteuzi kamili na thabiti hasa. Munganisho hutafsiri majibu yake ya jukwaa katika bahasha hizi; msingi hautafsiri mashamba ya muuzaji au hujenga mfanyabiashara URL.

Kufanya operator-kujengwa lango inapatikana katika Hifadhi ya asili na chat

Uwezo wa malipo pekee hauweki lango mbele ya wateja. Mlango wa Malipo ya Hifadhi block katika Connector Builder. Inaongeza mkataba uliochapishwa wazi, uumbaji wa ramani ya checkout na ufuatiliaji wa malipo ya kazi, na kuruhusu vikoa vya mtoa huduma-vilivyohifadhiwa Checkout. Mara tu kontakt imewekwa, kuwezeshwa na kuchaguliwa chini ya mipangilio ya Biashara, lango hilo linaonekana kwenye Duka la umma, Hifadhi ya duka la kawaida, mteja-chat na checkout ya uhuru. Hakuna mtoaji anayeweka ni ngumucoded.

Mkataba wa lango la biashara ya
{
  "commerce": {
    "roles": {
      "checkout_create": { "operation": "acme_checkout_create", "transport": "http",
                           "recovery": "acme_payment_status" },
      "payment_status":  { "operation": "acme_payment_status", "transport": "http" },
      "payment_profile": { "operation": "acme_payment_profile", "transport": "http" },
      "webhook_verify":  { "operation": "acme_webhook_verify", "transport": "http" },
      "event_map":       { "operation": "acme_event_map", "transport": "http" },
      "payment_refund":  { "operation": "acme_refund", "transport": "http",
                           "recovery": "acme_refund_status" }
    },
    "storefront_gateway": {
      "enabled": true, "version": 1, "label": "Acme Pay",
      "checkout_hosts": ["checkout.acmepay.com", "*.acmepay.com"]
    }
  }
}
Uwezo wa Checkout

Ramani za hatua ya Checkout checkout_url Na wakati wa kujifungua, session_id· The yaURLLazima iwe HTTPS, haina sifa yoyote, na inafanana na mwenyeji aliyeruhusiwa.

Uwezo wa hali ya Canon

Hali ya huduma hufanya mtoa huduma mpyaAPIKuangalia na ramani paid Kama ilivyo kwa kweli, amount_minor Kama ilivyo kwa wapenda soka, currency kama kanuni ya tatu ya ISO, na provider_refKurudi kwa URL, kamba ya swala, mzigo wa mteja, au maagizo ya "kuthibitishwa" kamwe sio malipo ya ukweli.

Mkataba wa Malipo ya Ruhusa

Ikiwa njia ya malipo inaunga mkono kurejeshwa, ramani payment_refund na kazi yake ya ukombozi. accepted Na kwa kuwa completed Wajenzi wa pamoja provider_ref-Kutoa huduma kwa wateja na kurudi statusBila ya kufanya kazi zote mbili,OpsIQHakuna matangazo ya malipo ya kontakt.

Nani anathibitisha amri

Mwandishi kamwe hawezi kuandikaOpsIQhali ya utekelezaji.OpsIQInalinganisha kiasi kilichorejeshwa na sarafu hasa na kumbukumbu za mtoa huduma; tu basi hufanya msingi wa mpito uliothibitishwa na mtoa huduma. Uhamisho wa benki ya mwongozo bado mtiririko pekee ambao wakala aitwaye anaweza kupitisha.

Kwa upande wa Mhandisi wa Mawasiliano, Mhe. Biashara ya biashara, kuweka mipaka na pia kufanya ukaguzi wa Kuunganishwa kwa Huduma ya Wateja wa Kampuni, Mlango wa Malipo ya Hifadhi, au wote wawili wakati kiunganishi kweli hutoa mikataba yote miwili. mchawi kuhalalisha tamko na kuandika commerce_roles.jsonUchapishaji bado hutumia mapitio ya kawaida ya Soko na mchakato wa saini; mkataba huu haupitii ukaguzi wa mfuko au hufanya kontakt isiyo ya kufungwa. php tools/verify_commerce_contracts.php.
💡
Usafiri ni wa http kwa mbali API au bridge Kwa ajili ya operesheni jina katika daraja lililotumika (angalia NO-APIMuundo chini). Majukumu ni usafiri-agnostic; kukimbia tu inahitaji usafiri alisema hivyo inaweza kurekebisha daraja.
Viunganishi

Kuuza kupitia chat bila kontakt: Actions & Triggers

Mkataba wa biashara hapo juu hauhitaji kifurushi cha kontakt. Ikiwa jukwaa lako ni yako mwenyewe - ofisi ya nyuma ya desturi, mfumo wa ndani wa API, hakuna mtu anayetuma kiunganishi kwa — unaweza kufikia mashine sawa ya kuuza na zana mbili ambazo unatumia kuunganisha kitu kingine chochote: Hatua za kawaida (hatua zako za HTTP, zilizofafanuliwa kwenye ukurasa wa Actions) na Triggers (hata webhooks za wavuti). mkataba huo, kadi moja, uhakikisho wa utambulisho huo huo, kernel ya malipo sawa, risiti.

Jinsi ya kuunganisha

Unajenga hatua moja ya desturi kwa jukumu la biashara - kila mmoja ni mwisho wa HTTPS wazi upande wako, iliyofafanuliwa chini Mfumo wa Uendeshaji na Automation→Hatua za Pamoja na yakeURL, kichwa auth na vigezo. Kisha wewe kuokoa tamko moja kwamba ramani majukumu ya vitendo hivyo. Kutoka wakati huo duka yako inaonekana katika chat hasa kama kiunganishi-backed moja: AI quotes kutoka kwa yako ya quote hatua, kadi ya uthibitisho hutoa, mteja kuthibitisha barua pepe zao, ili kernel wito yako ya utaratibu hatua na ufunguo idempotency, OpsIQ inachukua malipo kupitia njia ya milango ya kazi, na yako ya Hakuna chochote kuhusu uzoefu wa mteja anasema "mteja".

Tamko la

Kuokoa hiiJSONKama sehemu ya kazi commerce_custom_integration (Mapendekezo ya→kwa ajili ya shughuli za maendeleo, au kwa njia ya utaratibu waAPIHii ni sawa na muundo wa mfuko commerce_roles.json Biashara ya hisa, pamoja na action Kutaja majina ya desturi yako IDs:

commerce_custom_integration
{
  "enabled": true,
  "roles": {
    "catalog_search":  { "action": "acme_catalog" },
    "quote":           { "action": "acme_quote" },
    "order_get":       { "action": "acme_order_get" },
    "customer_create": { "action": "acme_customer_create",
                         "recovery": "acme_customer_by_email" },
    "order_create":    { "action": "acme_order_create",
                         "recovery": "acme_order_by_key" },
    "record_payment":  { "action": "acme_record_payment",
                         "recovery": "acme_payment_by_key" }
  },
  "customer_ordering": {
    "enabled": true, "version": 1,
    "mode": "direct_order",
    "audience": "guests_and_clients",
    "account_flow": "connector_signup",
    "payment_flow": "opsiq_gateway",
    "label": "Acme Store",
    "identity_parameter": "client_identifier",
    "quantity_parameter": "quantity",
    "transaction_kind": "purchase",
    "fulfilment_presence": "remote_delivery",
    "notify_flow": "platform_automatic"
  }
}

Mwisho, kuongeza custom_commerce kwa ajili ya kuwawezesha wateja kununua bidhaa chini ya masharti→Wateja wa Chat→Kununua kwa njia ya chat. kuingia ni upya kuangalia juu Kila mmoja kila Ombi, na linakataa kwa sababu zilizotajwa badala ya kujificha kimya duka lako: jukumu la mode yako inahitaji ramani hiyo bila kitu, jukumu la kuandika bila hatua ya kupona (§15.7 - kuandika ambayo matokeo yake hayawezi kuulizwa tena ni kukataliwa), hatua ambayo imefutwa au walemavu tangu kuokolewa.

Nini kila hatua ya kazi lazima kufanya

Kurudi kwa Link ya Link

Majibu ya {"success": true, "data": { ... }} – au - au {"success": false, "error": "a sentence a customer may read"}Hatua yako Njia ya Mafanikio Inapaswa kuwa juu ya kifuniko.

Ku quote: yote-katika jumla, katika vitengo ndogo

Kurudi kwa kurudi quote_id, product_name, quantity, unit_amount_minor, total_amount_minor, currency, selection, selection_summary, expires_atKila kitu katika "jumla yako ni takwimu pekee kwamba hatua fedha" sehemu juu inatumika verbatim: kodi, ada na multipliers kwenda INTO jumla yako, kwa sababu jumla yako ni nini saini, kuonyeshwa na kushtakiwa.

Kuundwa kwa Sheria: Heshima ya Msingi wa Malipo

Wewe unapokea idempotency_keyMkataba uliosainiwa total_minor Na kwa kuwa currencyKuwa Certified customer_email, na vigezo vyako mwenyewe quote. Hifadhi ufunguo kwa utaratibu; kama wewe tayari umba amri kwa ajili yake, kurudi kwamba ili badala ya pili. kuthibitisha fedha - kama mfumo wako bei agizo tofauti na jumla saini, kukataa retryably badala ya under-charging. reference Jukwaa lako linatambua.

Jibu: Andika kuhusu moja ya barua

order_by_key Kupata ufunguo wa malipo na majibu {"found": true, "order": {...}} au {"found": false}. kupatikana: uongo ni ahadi - OpsIQ inaweza retry kuandika juu ya nguvu yake. hadhi kulisha au orodha ya amri za hivi karibuni si jibu kuhusu moja kuandika.

Malipo ya dhamana: Njia yako mwenyewe

Inapokea kitambulisho cha shughuli ya lango kama ufunguo wa malipo pamoja na kumbukumbu yako ya agizo, baada ya OpsIQ ina kiasi kilichothibitishwa kikamilifu na sarafu kwa njia ya lango. platform_notified: true Kama una akaunti ya biashara, mteja wako atatuma barua pepe.

Michango ya kadi huja kutoka vigezo vyako vya hatua

parameter yoyote wewe kutangaza juu ya hatua yako QUOTE (zaidi ya kigezo utambulisho) kwamba AI haijakusanya ni yaliyotolewa kwenye kadi ya uthibitisho kama pembejeo mteja kujaza wenyewe - uwanja, tarehe, kiti. Label yao vizuri; studio ni nini mteja kusoma.

Soma zaidi: Sikiliza mauzo yako mwenyewe

Matukio mawili moto kwenye basi ya tukio la pamoja, hivyo webhooks yako na automatiserings kusikia kila mauzo ya mazungumzo popote ilipotekelezwa:

commerce.order.created

Wakati amri nchi upande wa mfanyabiashara, kabla ya malipo - kumbukumbu, kontakt (au custom_commerce), kiasi, fedha, barua pepe ya mteja, ID thread.

commerce.payment.confirmed

Mara moja kwa utaratibu, wakati lango linathibitisha kikamilifu malipo. Inaendesha madai sawa ambayo yanazuia risiti za duplicate, hivyo haiwezi mara mbili moto wavuti yako.

Wakati wa kuhitimu kwa kontakt

Ushirikiano wa desturi ni usanidi wa nafasi ya kazi: hutumikia duka lako, kwenye nafasi yako ya kazi. Wakati unataka kusambaza ushirikiano - maeneo mengine ya kazi, soko, toleo, kusainiwa, kufunga vifurushi vilivyolipwa - hufunga vitendo sawa na tamko moja kama kiunganishi. Mkataba haubadilika; tu wrapper hufanya.

Viunganishi

Kuunganisha jukwaa ambayo hainaAPI(Elekezwa kutoka Mfumo wa Bridge)

Mengi ya majukwaa halisi meli hakuna RESTAPICMS ya hoteli, mfumo wa zamani wa bili, chombo cha ndani cha bespoke. bado unaweza kuandika kamiliOpsIQkontakt kwa moja: kiunganishi meli moja PHP faili kwamba operator matone katika webroot yao ya umma, na kwamba faili niAPIUkurasa huu ni muundo wote, na sheria ambazo zinafanya kuwa salama kuendesha na sababu ya kila utawala.

Sura ya hiyo

Kiunganisho cha kawaida huita mtu mwingine wa API. Kikontakt cha daraja huleta yake mwenyewe. Hakuna kitu kingine kinachobadilika: vitendo sawa, watoa mazingira sawa, mkataba huo wa utambulisho, mpangilio sawa wa mfuko.

1
Unaweza kuunda faili moja ya PHP

It lives in your package at bridge/opsiq-<platform>-bridge.php. It talks to the platform's database directly, or boots the platform's framework, or both. It answers JSON.

2
Mtumiaji anaiweka kwenye mtandao wake

Karibu na index ya jukwaa mwenyewe. php Hakuna msimbo wa jukwaa umebadilishwa, hakuna Plugin imewekwa, hakuna kitu cha kudumisha kwenye upgrades wa jukwaa.

3
Jopo la kuunganisha mikono yao faili

Mipangilio yako.json inatangaza webhook_help. snippet_template. ukurasa wa kontakt unaifanya kama faili inayoweza kupakuliwa na mipangilio yao ya kuishi tayari imebadilishwa, kwa hivyo hakuna kitu cha kuhariri mkono.

4
OpsIQInatumia server-kwa-server

Mteja wako.php anatuma maombi ya GET na ufunguo wa pamoja katika X-Opsiq-Bridge-Keyer, msingi waURLKuweka ni msingi wa tovuti ya jukwaa.

Muumba wa Connector anaweza kuzalisha hii kwa ajili yenu sasa. Chagua "Platform bila ya API"Ufafanuzi (au kuweka upatikanaji wa data kwa daraja) na hutoa faili la daraja, snippet ya jopo linalolingana na vitendo vilivyoandikwa ambavyo vinasoma na kuandika kupitia - kwa maombi ya Laravel kusoma yake.env, kwa WordPress kusoma wp-config.php, au na sifa unazoweka kwa kitu kingine chochote. mode ya Bridge inarekebisha uthibitishaji kwa OpsIQ Itifaki ya daraja: kontakt inazalisha salama api_key Kama inawezekana, basi ni kama X-Opsiq-Bridge-Keyna kuhakikisha kwamba thamani ya hifadhi hiyo inalipwa kwa OPSIQ_BRIDGE_KEY Katika faili inayoweza kunakiliwa. Mwandishi wa mkono tu wakati jukwaa lako sio mojawapo ya hizo, au unapohitaji tabia daraja linalozalishwa halifichi. Daraja la maandishi ya mkono ni salama kutoka kwa mchawi: linaandika tu faili la daraja lililobeba alama yake mwenyewe.
💡
Kila kitu kwenye ukurasa huu kinaonyeshwa katika PHP dhidi ya MySQL, kwa sababu hiyo ni utekelezaji wa kumbukumbu na mchanganyiko pekee wa bomba la ufungaji linaunga mkono kikamilifu. muundo yenyewe ni lugha-agnostic na injini ya utambuzi: angalia "Kilimo katika lugha nyingine na database zingine" kwa lango huko Node, Python, Go, Ruby, .NET na Java, swala la utangulizi kwa ajili ya PostgreSQL, SQL Kwa mfano, Server SQLite Kwa mfano, katika kesi ya Oracle na MongoDB sawa - pamoja na kizuizi cha ufungaji ambacho kinaamua jinsi daraja lisilo laPHP linafikia operator.

ya usalama na kwa nini kila mmoja ana

Faili hii inakaa kwenye mtandao wa umma nyuma ya ufunguo mmoja ulioshirikiwa. Ukweli huo unaongoza kila kanuni hapa chini. Usipuuzi yoyote yao ili kufanya daraja lako liwe rahisi.

Simu ya mkononi kamwe haiweziSQL

Sio kifungu cha Ambapo, sio ORDER BY kipande, si "hii mara moja" parameter ya swala la mbichi. mpiga simu anataja meza, safu na thamani; faili yako hujenga taarifa. Wakati mwasiliani anaweza kuchangia maandishi ya SQL, ufunguo mmoja wa pamoja unakuwa utekelezaji wa database kiholela.

Majina ya meza na safu ni halali dhidi ya habari_schema

Wakosoaji hawawezi kufungwa kama vigezo, hivyo wanapaswa kuchunguzwa badala yake. soma meza halisi na orodha ya safu kwa database hii na kukataa chochote kisicho juu yake. Kitambulisho ambacho sio kitu halisi cha schema hii basi hakiwezi kufikia swala kabisa - ambayo ndiyo inafanya kuwa salama kuweka wazi kila meza.

Kila kitu ni parameter ya msingi

Bila ubaguzi, ikiwa ni pamoja na maadili ndani ya utafutaji. vitambulisho vya heshima pamoja na thamani iliyofungwa ni jozi ambayo hufanya jumla ya uso na nil ya uso wa sindano.

Kusoma ni ya ulimwengu wote, kuandika ni kuruhusiwa

Angalia hii: Hii ni kanuni ambayo watu wengi wanataka kuruka.

Waandishi wa habari wakamatwa kwa kusoma na kukataa kuandika

Mechi juu ya safu NAME: password, kumbuka_token, siri, api_key, faragha_key. chumvi, ishara. Weka thamani na placeholder njiani. Kukataa kuandika kabisa kwenye njia - kuandika nenosiri ghafi hash si operesheni, ni footgun.

Kuondolewa ni moja ya row, kwa msingi

Kamwe kufuta wingi, kamwe kufuta na filter. kuondolewa kwa wingi ni jinsi database kufa. Kama mtu kweli anahitaji moja, wanaweza kufanya hivyo katika jukwaa.

Kusoma ni juu ya msalaba

Weka parameter ya kikomo na dari ngumu. swala la kukimbia lazima lisiweze kufuta database kupitia ujumbe wa mazungumzo.

Kushindwa kufunga mpaka mlango ufunguliwe

Daraja lisilo na mpangilio majibu 403 kwa kila kitu. daraja ambalo linasaidia kabla haijaundwa ni daraja ambalo lilikuwa la manufaa kwa mgeni.

Muda wa kawaida wa kulinganisha, ufunguo katika kichwa

Hash_equals, kamwe ==. ufunguo huenda katika X-Opsiq-Bridge-Key, sio kamba ya swala, kwa hivyo inakaa nje ya magogo ya upatikanaji, kumbukumbu za wakala na vichwa vya Refererer.

Kuwa tu

Njia moja, sura moja, hakuna kitu cha kuingiza katika mwili. Kila kitu daraja hufanya ni wazi kama GET na vigezo kuthibitishwa, na OpsIQ ndiye mpiga simu pekee.

Soma kwa ujumla, andika ruhusu-na kwa nini

Hii ni kanuni ambayo inapata hoja na, hivyo hapa kuna sababu kamili. Msaidizi lazima awe na uwezo wa kuona jukwaa zima: hiyo ndiyo inafanya kuwa muhimu, na kusoma haiwezi kuharibu chochote. Andika ni tofauti. faili hii anakaa katika mtandao wa umma nyuma ya ufunguo mmoja ulioshirikiwa. Ikiwa uvujaji huo muhimu, uso wa kuandika usiozuiliwa hufanya kuvuja sawa na udhibiti kamili wa database - mtumiaji mpya wa admin, meza ya uhifadhi iliyofunguliwa.

⚠️
Kwa kuwaOpsIQAmri ya amri inafungua AI, sio ufunguo. admin kubonyeza Kuruhusu hatua ya uharibifu ni udhibiti juu ya msaidizi.Sio udhibiti wa yeyote anayeshikilia ufunguo wa daraja. Hizi ni vitisho viwili tofauti, na orodha ya kuruhusu ni jibu la pili.
Ndege ya abiria, kutoka daraja la Botble
/* ── WRITE ALLOW-LIST — which tables the assistant may CHANGE here.
 *
 * READS are unrestricted: the assistant can see every table in the platform.
 * WRITES are limited to this list, because this file sits in a PUBLIC webroot
 * behind ONE shared key — an allow-list means that even a leaked key cannot
 * reach a table you never enabled (no new admin users, no emptied bookings).
 *
 * Comma-separated table names. Add tables as you need them — e.g. append
 * ',pages,posts' to let the assistant edit site content. Set it to '*' to
 * allow every table, deliberately. Empty falls back to the hotel defaults. ── */
const OPSIQ_WRITE_TABLES = 'ht_bookings,ht_booking_rooms,ht_booking_addresses,ht_rooms,ht_room_types,ht_customers,customers';

Maelezo mawili katika hundi hapa chini ni rahisi kupata makosa. jina la meza linawasili tayari RESOLVED, kubeba jedwali la ufungaji kabla yafix, wakati operator anaandika orodha ya kuruhusu bila kupangiliwa kwa sababu hiyo ndio wangeweza aina ya kawaida. Linganisha njia zote mbili au kufunga kabla inaruhusu kitu na kila kuandika mapumziko. Na kukataa lazima kuelezea yenyewe, kwa sababu mtu anayesoma ni admin katika dirisha la mazungumzo, sio msanidi programu aliye na kufuatilia stack.

Angalia orodha ya ruhusu, verbatim kutoka kwa wauzaji wa soko_connectors /botble/bridge/opsiq-botble-bridge. php
/** Tables a WRITE may touch. Empty = the built-in defaults. */
$writeAllowed = static function (string $table) use ($prefix): bool {
    $raw = trim((string)(defined('OPSIQ_WRITE_TABLES') ? OPSIQ_WRITE_TABLES : ''));
    if ($raw === '') $raw = 'ht_bookings,ht_booking_rooms,ht_rooms,ht_customers,customers';
    if (trim($raw) === '*') return true;                     // explicit opt-in to everything
    $bare = ($prefix !== '' && stripos($table, $prefix) === 0) ? substr($table, strlen($prefix)) : $table;
    foreach (explode(',', $raw) as $t) {
        $t = trim($t);
        if ($t === '') continue;
        if (strcasecmp($t, $table) === 0) return true;
        if (strcasecmp($t, $bare)  === 0) return true;
        if ($prefix !== '' && strcasecmp($prefix . $t, $table) === 0) return true;
    }
    return false;
};

/** One refusal, one explanation — used by every write op. */
$requireWritable = static function (string $table) use ($writeAllowed): void {
    if ($writeAllowed($table)) return;
    opsiq_bridge_out(['success' => false, 'error' =>
        'write_not_allowed: "' . $table . '" is not in this bridge\'s write allow-list. '
        . 'Reads are unrestricted. To permit writes here, add the table to OPSIQ_WRITE_TABLES '
        . 'in opsiq-botble-bridge.php (or set it to "*" to allow every table).'], 403);
};

Mlango wa mlango, kwa ukamilifu

Ukaguzi wa nne, katika utaratibu huu, kabla ya kitu chochote kugusa data. nakala ya utaratibu na hundi.

4 kwa ajili ya ukaguzi, ili
<?php
declare(strict_types=1);

/* ── EDIT THIS: a long random secret (40+ chars). Empty = bridge OFF. ── */
const OPSIQ_BRIDGE_KEY = '';

header('Content-Type: application/json; charset=utf-8');
header('Cache-Control: no-store');

function opsiq_bridge_out(array $payload, int $code = 200): void
{
    http_response_code($code);
    echo json_encode($payload, JSON_UNESCAPED_SLASHES);
    exit;
}

/* 1. Fail closed. An unconfigured bridge answers nothing to anyone. */
if (OPSIQ_BRIDGE_KEY === '' || strlen(OPSIQ_BRIDGE_KEY) < 24) {
    opsiq_bridge_out(['success' => false, 'error' => 'bridge_not_configured'], 403);
}
/* 2. One method. */
if (strtoupper((string)($_SERVER['REQUEST_METHOD'] ?? '')) !== 'GET') {
    opsiq_bridge_out(['success' => false, 'error' => 'method_not_allowed'], 405);
}
/* 3. Constant-time key comparison, key from a header (never the query string). */
$given = (string)($_SERVER['HTTP_X_OPSIQ_BRIDGE_KEY'] ?? '');
if ($given === '' || !hash_equals(OPSIQ_BRIDGE_KEY, $given)) {
    opsiq_bridge_out(['success' => false, 'error' => 'forbidden'], 403);
}
/* 4. Only now read credentials and connect. */

Kujiandikisha kwa vitambulisho dhidi ya taarifa_schema

Hii ni kipande ambacho kinageuka "Msaidizi anaweza kufikia meza yoyote" kutoka kwa reckless kuwa salama. Suluhisho la jina la meza ya simu dhidi ya schema halisi, kuvumilia prefix ya meza isiyo na au ya ziada, na kurudi null kwa kitu kingine chochote. Kila kitu chini kisha kazi na jina ambalo linaenea lipo.

Uthibitisho wa Identifier na redaction, verbatim kutoka daraja la Botble
/** Real tables in THIS database — the allow-list, straight from the DB. */
$allTables = static function () use ($pdo, $db): array {
    static $cache = null;
    if ($cache !== null) return $cache;
    $st = $pdo->prepare('SELECT TABLE_NAME FROM information_schema.TABLES WHERE TABLE_SCHEMA = ? ORDER BY TABLE_NAME');
    $st->execute([$db]);
    return $cache = array_map('strval', $st->fetchAll(PDO::FETCH_COLUMN));
};

/** Resolve a caller-supplied table name to a REAL one, or null. */
$resolveTable = static function (string $name) use ($allTables, $prefix): ?string {
    $name = trim($name);
    if ($name === '' || !preg_match('/^[A-Za-z0-9_]+$/', $name)) return null;
    $tables = $allTables();
    foreach ($tables as $t) if (strcasecmp($t, $name) === 0) return $t;
    /* Tolerate a missing or extra table prefix. */
    foreach ($tables as $t) {
        if (strcasecmp($t, $prefix . $name) === 0) return $t;
        if ($prefix !== '' && strcasecmp($prefix . $t, $name) === 0) return $t;
    }
    return null;
};

/** Column introspection: table => [column => true]. Cached per request. */
function opsiq_bridge_columns(PDO $pdo, string $db, string $table): array
{
    static $cache = [];
    if (isset($cache[$table])) return $cache[$table];
    $stmt = $pdo->prepare('SELECT COLUMN_NAME FROM information_schema.COLUMNS WHERE TABLE_SCHEMA = ? AND TABLE_NAME = ?');
    $stmt->execute([$db, $table]);
    $cols = [];
    foreach ($stmt->fetchAll(PDO::FETCH_COLUMN) as $c) $cols[strtolower((string)$c)] = true;
    return $cache[$table] = $cols;
}

/** Columns whose VALUES must never leave the platform. */
$secretCol = static function (string $c): bool {
    return (bool)preg_match('/(^|_)(password|remember_token|secret|api_key|private_key|salt|token)($|_)/i', $c);
};
/** Columns a write may never touch — auth material. */
$writeBanned = static function (string $c): bool {
    return (bool)preg_match('/(^|_)(password|remember_token)($|_)/i', $c);
};
/** Strip secret values from a row before it leaves the server. */
$redact = static function (array $row) use ($secretCol): array {
    foreach ($row as $k => $v) if ($secretCol((string)$k)) $row[$k] = '[redacted]';
    return $row;
};

Kusoma na kuandika, au kusoma

Angalia nini ni amefungwa na nini ni kuthibitishwa. safu filter ni checked dhidi ya orodha halisi ya nguzo na kisha interpolated kama kitambulisho; thamani yake ni imefungwa. kikomo ni clamped. Rows ni redacted juu ya njia nje. update anakataa muhimu msingi na yoyote safu auth, na stamps updated_at wakati meza ina moja.

Soma meza yoyote - vitambulisho vilivyothibitishwa, maadili yaliyofungwa, safu zilizofungwa
case 'query': {
    $t = $resolveTable((string)($_GET['table'] ?? ''));
    if ($t === null) opsiq_bridge_out(['success' => false, 'error' => 'unknown_table'], 404);
    $cols = opsiq_bridge_columns($pdo, $db, $t);
    if (!$cols) opsiq_bridge_out(['success' => false, 'error' => 'unknown_table'], 404);

    $sql = "SELECT * FROM `$t` WHERE 1=1";
    $args = [];

    /* Equality filter: column must be REAL, value is bound. */
    $wc = strtolower(trim((string)($_GET['where_column'] ?? '')));
    if ($wc !== '') {
        if (!isset($cols[$wc])) opsiq_bridge_out(['success' => false, 'error' => 'unknown_column: ' . $wc], 400);
        $sql .= " AND `$wc` = ?";
        $args[] = (string)($_GET['where_value'] ?? '');
    }
    /* Ordering: column validated, direction from a fixed pair. */
    $ob = strtolower(trim((string)($_GET['order_by'] ?? '')));
    if ($ob !== '' && isset($cols[$ob])) {
        $dir = strtoupper(trim((string)($_GET['order'] ?? 'DESC'))) === 'ASC' ? 'ASC' : 'DESC';
        $sql .= " ORDER BY `$ob` $dir";
    } elseif (isset($cols['id'])) {
        $sql .= " ORDER BY `id` DESC";
    }
    /* Hard row cap. */
    $lim = (int)($_GET['limit'] ?? 25);
    if ($lim < 1)   $lim = 25;
    if ($lim > 200) $lim = 200;
    $off = max(0, (int)($_GET['offset'] ?? 0));
    $sql .= " LIMIT $lim OFFSET $off";

    $st = $pdo->prepare($sql);
    $st->execute($args);
    $rows = array_map($redact, $st->fetchAll());
    opsiq_bridge_out(['success' => true, 'data' => [
        'table' => $t, 'returned' => count($rows), 'rows' => $rows,
    ]]);
}
Andika mstari mmoja - meza iliyokubaliwa, kukataa safu za auth, mstari mmoja kwa ufunguo wa msingi
case 'record.update': {
    $t = $resolveTable((string)($_GET['table'] ?? ''));
    if ($t === null) opsiq_bridge_out(['success' => false, 'error' => 'unknown_table'], 404);
    $requireWritable($t);                       // the allow-list, before anything else
    $cols = opsiq_bridge_columns($pdo, $db, $t);
    $pk   = $primaryKey($t);
    $id   = (string)($_GET['id'] ?? '');
    if ($id === '') opsiq_bridge_out(['success' => false, 'error' => 'id_required'], 400);

    $set = json_decode((string)($_GET['set'] ?? ''), true);
    if (!is_array($set) || !$set) opsiq_bridge_out(['success' => false, 'error' => 'set_json_required'], 400);

    $frag = []; $args = [];
    foreach ($set as $col => $val) {
        $col = strtolower(trim((string)$col));
        if (!isset($cols[$col]))  opsiq_bridge_out(['success' => false, 'error' => 'unknown_column: ' . $col], 400);
        if ($writeBanned($col))   opsiq_bridge_out(['success' => false, 'error' => 'refused: "' . $col . '" is auth material - change it through the platform own password flow, never by direct write.'], 400);
        if ($col === $pk)         opsiq_bridge_out(['success' => false, 'error' => 'refused: the primary key cannot be rewritten.'], 400);
        if (is_array($val) || is_object($val)) $val = json_encode($val, JSON_UNESCAPED_SLASHES);
        $frag[] = "`$col` = ?";
        $args[] = ($val === null) ? null : (string)$val;
    }
    if (isset($cols['updated_at']) && !isset($set['updated_at'])) $frag[] = '`updated_at` = NOW()';

    $before = $pdo->prepare("SELECT * FROM `$t` WHERE `$pk` = ? LIMIT 1");
    $before->execute([$id]);
    $prev = $before->fetch();
    if (!$prev) opsiq_bridge_out(['success' => false, 'error' => 'not_found'], 404);

    $args[] = $id;
    $up = $pdo->prepare("UPDATE `$t` SET " . implode(', ', $frag) . " WHERE `$pk` = ? LIMIT 1");
    $up->execute($args);
    opsiq_bridge_out(['success' => true, 'data' => [
        'table' => $t, 'id' => $id, 'changed' => $up->rowCount(),
        'before' => $redact(array_intersect_key($prev, $set)),
    ]]);
}

Kutatua tofauti za mfumo

Matoleo ya Jukwaa hutofautiana. Nguzo zinahamia, kupata jina, au haipo. Daraja ambalo linachukua schema moja inafanya kazi kwenye ufungaji mmoja. Introspect na kurekebisha badala yake: chagua tu nguzo ambazo zipo hapa, vumilia jedwali la prefix, na jaribu spellings dhahiri za kumbukumbu.

Ustahimilivu wa Schema, kutoka kwa Daraja la Botble
/* Only ever select columns that exist on THIS install. */
$pick = static function (array $cols, array $wanted, string $alias = 'b'): string {
    $out = [];
    foreach ($wanted as $c) if (isset($cols[$c])) $out[] = "`$alias`.`$c`";
    return $out ? implode(', ', $out) : "`$alias`.*";
};

/* References vary: stored with or without a leading "#", with or without an
 * operator-configured alpha prefix, or only as a numeric id. Try every
 * plausible form — the PROOF match is what actually gates disclosure, so
 * tolerant matching here is safe. */
$refCandidates = [$ref, '#' . $ref];
$digitsOnly = preg_replace('/\D+/', '', $ref);
if ($digitsOnly !== '' && $digitsOnly !== $ref) {
    $refCandidates[] = $digitsOnly;
    $refCandidates[] = '#' . $digitsOnly;
}
$refCandidates = array_values(array_unique($refCandidates));
💡
Kutoa daraja yako op = ray kwamba ripoti STRUCTURE tu - ambayo meza kutatuliwa, ambayo safu ya meza kuu ina, na SHAPE ya kumbukumbu mpya zaidi na kila digit masked. ni muhimu-gated kama kila kitu kingine, na anarudi "mtazamaji hana kupata chochote" kutoka tiketi msaada katika jibu la pili. Kamwe basi kurudi rekodi halisi.

makosa ya jinai na kwamba utaratibu wa

Moja ya njia kwa ajili ya kila kitu

Success is {"success":true,"data":{...}}. Failure is {"success":false,"error":"snake_case_reason"}. Your Client.php and every action then have exactly one response shape to handle.

Hakuna mechi na hakuna mechi lazima iwe sawa

Juu ya uso wa kuangalia, kumbukumbu ambayo haipo na kumbukumbu ambayo ushahidi wake haukufanana lazima uwasilishe majibu ya SAME. Majibu tofauti hugeuza daraja lako kuwa neno ambalo linathibitisha ni marejeo halisi, ambayo ni usafirishaji wa bure kwa mteja yeyote mgonjwa.

Kamwe usiruhusu mtu yeyote apoteze nafasi ya kutembelea

Mfumo huu unaweza kuwa sahihi kwaOpsIQKwa hiyo, ni jambo gani ambalo mgeni anapaswa kuamua kwaOpsIQkatika hatua moja ya kukataa.

Faili ya nakala katika jopo la kontakt

operator kamwe kufungua hazina yako. Wao kufungua jopo la kontakt katika OpsIQ na vyombo vya habari nakala. kwamba nakala huja kutoka mazingira.json, na ni lazima kuwa mpango sawa kama daraja / *. php.

Mipangilio.json - kuingia kwa jopo la kontakt ya daraja
{
  "settings": [
    { "key": "base_url", "label": "API base URL", "type": "text", "required": true },
    { "key": "api_key",  "label": "Bridge key",   "type": "password", "required": true,
      "autogenerate": true,
      "help": "Auto-generated the moment you enable the connector. It must match OPSIQ_BRIDGE_KEY inside the bridge file; the copyable file below already carries this value once saved." }
  ],
  "webhook_help": {
    "title": "One file, three surfaces",
    "body": "This platform has no public REST API, so this ONE file IS the API. Copy it into the site PUBLIC webroot, keeping the filename.",
    "snippet_filename": "opsiq-yourplatform-bridge.php   (drop next to the site index.php)",
    "snippet_template": "<?php\n/* ... the whole bridge file ... */\nconst OPSIQ_BRIDGE_KEY = \u0027{{setting:api_key}}\u0027;\n..."
  },
  "snippet_bindings": [
    { "assignment": "OPSIQ_BRIDGE_KEY", "setting": "api_key" }
  ]
}
{{setting:key}} carries live values

The connector panel substitutes {{setting:<key>}} in the snippet with that connector's saved value, so the copied file already contains the operator's generated bridge key and needs no hand-edit. An empty or unsaved setting leaves the token visible, so the operator can see exactly what is still missing.

snippet_bindings kuishi kuzaliwa upya

Kutangaza kila kazi ya siri yanayotokana wazi. chombo sync hujenga nakala ya jopo kutoka daraja lililosafirishwa na kisha kurejesha OPSIQ_BRIDGE_KEY = {{setting:api_key}} Kutoka kwa kumfunga hii. Bila hiyo, kuboresha kunaweza kunakili faili ya mfuko usio na ufunguo na kuondoa kimya kizuizi cha mwendeshaji muhimu kinachowekwa. Wajenzi wa Connector hutoa hii inayofunga moja kwa moja kwa pakiti za daraja zilizozalishwa.

Wafanyabiashara wengine wa nafasi wanabadilishwa kwa upande wa seva

Licha ya hayo,{webhook_url}, {webhook_path}, {webhook_secret}, {site_key}, {base_url}Aidha, na{slug}Kuwekwa katika chumba cha kulala kabla ya kuona snippet

Webhook_help inaweza kuwa kitu kimoja au orodha

Orodha inakupa snippets kadhaa katika jopo moja, kwa mfano faili ya daraja na ndoano tofauti ya kupeana.

🚫
Usihifadhi snippet kwa mkono. faili ya daraja na nakala ya jopo ni nakala mbili za programu moja, na wata drift - daraja liliboreshwa na nakala yake ya jopo haikuwa, hivyo mtu yeyote aliyerejesha na kunakiliwa kutoka kwenye jopo lililoweka daraja la zamani na kupoteza kimya kila uwezo mpya. Hakuna kitu kilichogundua: kukubaliana kupita, saini zilipitishwa, vipimo vilipita.
Weka nakala mbili zinazofanana
# Regenerate every package's panel snippet from its bridge file
php tools/sync_connector_bridge_snippets.php --apply

# Show what would change, without writing
php tools/sync_connector_bridge_snippets.php

Drift is now a failing conformance check, not a support ticket: the verifier compares the two line by line (ignoring the {{setting:...}} placeholders, which are supposed to differ) and names the first line that differs. Run the sync tool as the last step before every release, right before signing.

Nini ambacho chombo kinapaswa kuwa wazi

Shughuli zilizoundwa na uso wa data ya ulimwengu wote, pamoja. Wale walioumbwa wanarudi tidy, majibu yaliyojengwa kwa kusudi kwa maswali ambayo watu wanauliza; wale wa ulimwengu hufunika kila kitu kingine ili Msaidizi kamwe ashindwe kukwama.

Kusoma kwa sauti

stats, orodha kuu ya kitu na filters, kitu kimoja na safu zake kuhusiana, orodha ya kile ni kuuzwa, utafutaji wa wateja na historia. Hizi kutoa AI jibu nzuri katika wito mmoja badala ya tano.

Mwandishi wa maandishi

Mabadiliko mawili au matatu ya hali ambayo ni suala - kuweka hadhi, kufuta. Weka maadili yaliyokubaliwa yameorodheshwa.

Aina ya Biashara

Kwa jukwaa linalouzwa linafunua orodha ya kujengwa kwa kusudi, quote, checkout / utaratibu na shughuli za ushahidi wa malipo, kisha kuzipanga katika commerce_roles.json Pamoja na kuwa pamoja transport: bridgeKamwe ramani ya biashara kuandika jukumu la rekodi ya dunia nzima. kuunda / kuboresha uso.

Utambuzi wa Universal

meza (na makosa ya mstari) na kuelezea (madaraja, aina, ufunguo wa msingi, pamoja na bendera inayoweza kusomwa na kuandikwa kwa kila safu). Hii ndivyo msaidizi anajifunza jukwaa ambalo haukutarajia.

Kusoma na Kuandika

swali, record. get, record. kuunda, record, update, record kufuta. Kila mmoja wao kukubaliwa kama inavyoonyeshwa hapo juu.

Kabla ya lango kuu

Uchunguzi wa utambulisho huitwa na ADMIN's BROWSER, sawa-asili, hivyo hawawezi kutuma header desturi. Uthibitishaji wao ni jukwaa kikao yenyewe. Kuweka mbele ya lango muhimu, kuwaweka mbali na data zote rekodi, na kamwe basi yao kurudi siri.

Ugonjwa wa zinaa

op=diag, structure only, masked.

Ramani ya biashara ya Bridge
{
  "commerce": {
    "roles": {
      "catalog_search": {"operation":"hotel_catalog_search","transport":"bridge"},
      "quote":          {"operation":"hotel_quote","transport":"bridge"},
      "order_create":   {"operation":"hotel_order_create","transport":"bridge",
                           "recovery":"hotel_order_get"},
      "order_get":      {"operation":"hotel_order_get","transport":"bridge"},
      "record_payment": {"operation":"hotel_record_payment","transport":"bridge",
                           "recovery":"hotel_order_get"}
    },
    "customer_ordering": {
      "enabled":true, "version":1, "mode":"direct_order",
      "audience":"guests_and_clients", "account_flow":"guest_checkout",
      "payment_flow":"opsiq_gateway"
    }
  }
}
💡
The canonical jukumu udhibiti mlolongo na mamlaka; operesheni daraja anaendelea jukwaa mwenyewe mzigo wa malipo. hoteli inaweza kuhitaji kuwasili, kuondoka na wageni, WHMCS inaweza kuhitaji mteja zilizopo au kontakt-owned sainiup, na SaaS jukwaa inaweza kuhitaji bili mzunguko. Core kamwe hardcodes maeneo hayo. daraja lazima kuomba huduma za biashara ya jukwaa hivyo hisa, kodi, ankara, barua pepe ya uthibitisho na ndoa zote kukimbia.
⚠️
record_payment Sio njia ya mkato ya malipo ya alama. Kukubali tu ushahidi wa mtoa huduma aliyethibitishwa: agizo halisi, mfanyabiashara, kiasi, sarafu ya ISO, kumbukumbu ya mtoa huduma, mara mpya zilizohakikishiwa na ufunguo wa upungufu. Endelea kupitia malipo / nambari ya jukwaa API, kisha urejeshe utaratibu wa mamlaka au kurudi kwa ankara. matokeo yasiyojulikana lazima yaweze kupona kabla ya jaribio lolote.
💡
Kama jukwaa lako daima kujibu maswali, meli daraja na hakuna kuandika ops na darasa zima la hatari ya kuandika kutoweka.

Angalia kabla ya kupanda mbegu

Serikali yakanusha kila kitu bila kuweka msingi

Jaribu tena. jina mara kwa mara tupu na kuthibitisha kila majibu ya op 403.

Kukataa kwa wakati unaofaa ni kushindwa mara kwa mara

hash_equals, na muhimu kusoma kutoka kwa kichwa tu.

Jina la akaunti ya mpokeaji limekataliwa

Na jina la meza halisi na prefix mbaya bado hutatua.

Ukurasa wa siri kamwe hauonekani katika kusoma

Na mwandishi anakataa kutaja jina la mtu.

Barua ya barua kwa meza nje ya orodha ya ruhusa imekataliwa

Kwa ujumbe unaoelezea operator jinsi ya kupanua.

Jopo la snippet linacheza faili ya daraja

php zana /sync_connector_bridge_snippets. php ripoti yake katika hatua.

Kurejesha kontakt sio ya kutosha

Kama mfuko wako meli daraja faili, operator kuboresha kiunganishi lazima pia redeploy kwamba faili katika webroot yao. Sema hivyo katika mwili wa jopo na katika CHANGELOG yako, kila kutolewa.

Viunganishi

Kuhamisha mfumo wa jukwaa kutoka kwa daraja

Ni kitabu ambacho kinaweza kusomwa tu na SQLDaraja ambalo linaunganisha vitu kwenye jukwaa (ili, uhifadhi, ankara iliyolipwa) lazima ipitie safu ya maombi ya jukwaa mwenyewe, na booting safu hiyo bila kichwa ni mahali ambapo kila kushindwa kwa hila katika muundo huu huishi. Kila kitu chini kilijifunza njia ngumu juu ya ujumuishaji wa moja kwa moja, kila utawala dhidi ya kasoro halisi ambayo haikuzalisha kosa popote.

Kujiandikisha katika database sio amri

Raw INSERTs hufanya rekodi ya kivuli

Mstari unaonekana, admin anaorodhesha, na bado sio rekodi ya jukwaa inaamini iliunda: hakuna nambari ya kumbukumbu ya asili, hakuna ndoa za mfano, hakuna matukio, hakuna ankara, hakuna barua pepe ya mteja, hakuna kiungo cha huduma cha wateja. Mteja ananukuu kumbukumbu jukwaa ambalo halijawahi kutolewa kwa wafanyakazi ambao hawawezi kupata. Kujenga kupitia huduma ya jukwaa mwenyewe; ikiwa inaonyesha tu huduma ya malipo ya baada ya malipo, kuunda grafu inayotarajia na mkono kwenye seam inafafanua.

Kamwe usiongeze idadi ya jukwaa

Sampuli mbili za muundo wa kumbukumbu hufanya iwe rahisi kuzaa, na kuizalisha ni kivuli kimoja cha kuandika ngazi moja chini: siku jukwaa linabadilisha mpango wake, kila rekodi yako ni mbaya na hakuna kinachokuonya. Piga jenereta yake (kumbuka inafikia moja isiyo ya kawaida), na kusoma thamani iliyohifadhiwa nyuma badala ya kuamini kile ulichotuma.

Jukwaa la nguzo linaweka maana ya jukwaa

Kabla ya kuhifadhi chochote chako katika safu ya jukwaa, pata kila msomaji. Safu inayoitwa kama yanayopangwa bure inaweza kuwa na mzigo: kwenye ushirikiano wa kumbukumbu, transaction_id akageuka kuwa ishara ya mteja emailed "angalia booking yako" kiungo kutatua kwa njia: idempotency digest kuhifadhiwa huko kimya kuvunja kila kiungo mgeni. Weka uwekaji wako wa vitabu katika meza daraja inayomilikiwa: UNIQUE (ushirikiano), idempotency_key) ni mlinzi wa replay, kizuizi kinakataa mapacha ya wakati huo, na uchunguzi wa kupona unasoma meza hiyo ambayo uumbaji uliandika: MySQL DDL inafanya shughuli ya wazi bila kizuizi.

Matukio, wasikilizaji na mtego wa barua pepe mara mbili

Soma chanzo cha huduma kabla ya kutuma matukio yake

Ikiwa huduma ya jukwaa unayoita tayari inatuma tukio hilo, kuituma mwenyewe hutuma barua pepe za kuthibitisha kwa mteja na hutoa ankara mbili. Ikiwa hakuna kitu kinachosikiliza, kupeleka hutuma hakuna. Wala kushindwa kunaleta kosa. Kufikiria njia, kugawa mistari yake ya chanzo, na kusoma kile kinachofanya: nadhani ya jina na hata regex juu ya mwili wote walipata hii vibaya kabla ya chanzo kiliamua.

Wasikilizaji wa kweli hufunua ukweli na kuwaonya.

Laravel inawafunga wasikilizaji wa darasa katika kufungwa, hivyo kupata Wasikilizaji () ripoti za [email protected] kwa kila kitu. getRawListeners() majina ya madarasa halisi. Usituma tukio ambalo wasikilizaji wako hawawezi kutaja.

Kujiua hakumaanisha “kukimbia baadaye”

Kwa foleni =sync (kifungu cha default kwenye ufungaji mwingi wa uzalishaji) msikilizaji aliyepangwa anaendesha INLINE katika ombi lako la daraja. muktadha wako wa boot ni mazingira yake ya kutoa: kila usajili au URL defect katika nchi yako boot katika inbox ya mteja. Angalia config ('queue.default') kabla ya hoja kuhusu wapi kitu chochote anaendesha, na kuangalia kazi /failed_jobs Kabla ya kufanya kazi, mfanyakazi aliajiriwa.

Ulinzi wa usalama unaunganisha na nchi ya jukwaa yenyewe

Huduma ambayo inatuma bila masharti lazima iitwe mara moja tu. Alama ambayo haiwezi drift ni hali ya rekodi ya jukwaa (ita tu wakati rekodi bado inasubiri), sio bendera ya "sent" inayofanana na yako ambayo inaweza kutokubaliana nayo.

Kupakia si tu ni ya bure kwenye mtandao

Kujiandikisha nini tovuti boot kujiandikisha

Template variables, module settings, filter hooks: platform service providers often register them only on a web request. On the reference integration the email handler substitutes only REGISTERED variables: every value was set correctly and the customer's confirmation still rendered with empty name, phone and link, no error anywhere, because registration lives in a runtime registry the headless boot never filled. Find the platform's registration call (for Botble: EmailHandler::addTemplateSettings with the module's email config) and make it in your boot, exactly as the platform's own provider does.

Pin kila mmojaURLKwa upande mwingine, sio tu njia ya

Maombi yaliyochukuliwa yanaashiria kwenye script yako ya daraja, hivyo njia(), url(i) Kuzalisha na kuzalisha mali( site.comya umma/opsiq-bridge.php/checkout/TOKEN: kiungo cha wateja kupitia JSON Bonyeza kitufe cha "RootUrl" (config('app).url') Inarekebisha jenereta; diski ya STORAGE ina mizizi yake mwenyewe, kwa hivyo nembo ya barua pepe inakaa kuvunjwa hadi faili.disks. umma.url Imewekwa pia (inatatua lazily, kwa hivyo kuiweka kwenye kazi za boot, na tu wakati wa tupu au script- jamaa: CDN ya operator URL Je, si kuwa na wasiwasi juu yenu?

Fanya zoezi kabla ya kuweka mkono wako

Huduma za jukwaa zinasoma kupitia uunganisho wao wenyewe na haziwezi kuona shughuli yako ya wazi. Kuitwa kabla ya kufanya, huduma ya malipo baada ya kulipwa haipatikani malipo kamili, kimya huacha rekodi isiyolipwa, na bado huchoma matukio yake, kwa hivyo mteja ana barua pepe kuhusu rekodi ambayo jukwaa linafikiri haijalipwa.

Kanuni za uaminifu

Hakuna Matata Wall Stickers

Kama njia ya asili ni unreachable, kukataa na kosa retryable kabla ya hatua yoyote fedha. Kamwe mzulia kumbukumbu, kamwe mbichi-update hadhi ya kufanya nusu integrated rekodi kuangalia kumalizika. malipo kuthibitishwa ambayo usindikaji wa asili kushindwa kwenda maridhiano kama needs_attention: pesa ni kweli, hali ni kwa uaminifu "kulipwa, si kusindika".

Taarifa ya ukweli, si taarifa yako

"Huduma ilikimbia" na "mteja aliambiwa" ni ukweli tofauti: ushirikiano wa kumbukumbu uliosafirishwa barua pepe kamili ya kuangalia na kila uwanja tupu wakati moto wa mbio ulisema kweli.Warudi tofauti (kumaliza mchakato, jaribio la kuarifiwa), kuweka simu kwa wito platform_notified Hii inaimarisha OpsIQ Uthibitisho wa kurudi wakati wowote jukwaa halikuchukua, na kamwe kudai utoaji: kikasha hakionekani kutoka kwa seva.

Baada ya kuandika

Meli uwezo kusoma tu uchunguzi katika daraja: kuwepo kwa darasa, saini mbinu, vipande chanzo ya njia wewe nia ya kuwaita, wasikilizaji ghafi, dereva foleni, na (wakati swali inaweza kuwa jibu kwa wito kazi harmless) wito wa kuishi yenyewe. nadharia tano kuhusu barua pepe moja mashimo alikufa dhidi ya vipimo kabla ya chanzo makazi yake. Uchunguzi pande zote gharama nakala faili; kuandika vibaya kwenye jukwaa la kuishi gharama mteja.

Viunganishi

Daraja katika lugha nyingine na databases nyingine

Muundo wa daraja sio muundo wa PHP.OpsIQWito ni mwisho wa HTTP, kwa hivyo faili inaweza kuwa Node, Python, Go, Ruby, .NET au Java, na duka nyuma yake linaweza kuwa lolote.SQLEngine au engineMongoDBNini ni PHP-umbo ni bomba la ufungaji, na kwamba kikwazo huamua jinsi daraja lako linafikia operator.Soma sehemu ya utoaji kwanza: ni sehemu ambayo inawashangaza watu.

Nini hasa kontakt inahitaji

Hii ni lugha ya taifa, hakuna chochote katika lugha hiyo.

Usafiri wa Usafiri

HTTPS moja hupata ombi kwa simu. Hakuna mwili, hakuna njia nyingine.

Uthibitisho wa

Siri ya pamoja katika X-Opsiq-Bridge-Key Kuomba kichwa, ikilinganishwa kwa wakati wa mara kwa mara. Sio parameter ya swala, sio cookie, sio msingi auth.

Parameters ya

ya kiwango cha juu. op Majina ya kikoa. do Majina ya operesheni, wengine ni hoja za operesheni hiyo.

Majibu ya majibu

JSON. {"success":true,"data":{...}} au {"success":false,"error":"snake_case_reason"}Maombi ya Maudhui-Type /jsonHakuna cha kuficha.

Viwango vya Kodi

200 juu ya mafanikio. 403 ya msingi au isiyo sahihi 404 Haikupatikana, 405 Mbinu mbaya, 400 Hoja mbaya sana, 501 bila ya kuzingatia masharti ya Katiba hii.

Haya yote ni

Hakuna mfumo, hakuna kukimbia, hakunaOpsIQKwa upande mwingine, ikiwa unaweza kufanya hivyo, basi inaweza kuwa na nafasi.

Kusambaza: nini kinaweza kuishi kwenye daraja / kitu ambacho sio lazima

Kifurushi kilichosainiwa kinajumuisha orodha ya kudumu ya upanuzi wa faili, na faili nje ya orodha hiyo imeachwa nje ya ZIP. Daraja katika lugha orodha haina kufunika kwa hivyo haiwezi meli ndani ya mfuko - lakini haiwezi tena kutoweka kwako pia.26Agosti ya Agosti2026Faili ya ndani bridge/ kwamba mfuko ingekuwa kushuka ni vigumu kukubaliana kushindwa, hivyo mfuko anakataa kupita badala ya kufunga na hakuna daraja ndani yake.

Jinsi ya kutumia kadi / folda wakati wa kujenga
bridge/bridge.php     ->  SHIPPED, and drift-checked against the panel snippet
bridge/server.js      ->  SHIPPED, and drift-checked against the panel snippet
bridge/bridge.py      ->  REFUSED at conformance: "Bridge files are packaged" FAILS
bridge/bridge.rb      ->  REFUSED at conformance
bridge/main.go        ->  REFUSED at conformance
bridge/Bridge.cs      ->  REFUSED at conformance
bridge/Bridge.java    ->  REFUSED at conformance
PHP na yaJavaScriptMsaada kamili

Meli za faili katika ZIP iliyosainiwa, na snippet verifier ana nakala yako ya jopo kwa muda-identical kwake, popote kati ya mbili ni. ukaguzi wa drift unasoma kila faili katika daraja /, sio tu PHP ndio, hivyo daraja lililoboreshwa na nakala ya jopo la stale inashindwa kujenga katika lugha yoyote.

Kila kitu - tu kupitia kwa jopo

Jopo la snippet ni maandishi wazi bila kujua lugha gani inashikilia, kwa hivyo inafanya kazi kwa stack yoyote. Weka programu nzima katika webhook_help. snigget_template, jina faili katika snappet_filename, na usiacha nakala katika daraja / - ulinganifu utakataa kifurushi badala ya meli iko tupu.

Kama unahitaji lugha nyingine katika mfuko

Widen PackageSigner::EXTENSIONS deliberately, then re-sign and re-seed. That is a decision about what executable code Nabtech distributes, so make it on purpose — do not discover it from a missing file.

💡
Jina la faili katika webhook_help.snippet_filename wakati wowote mfuko wako meli daraja zaidi ya moja. Hiyo ni jinsi verifier anajua ambayo daraja nakala bodi inamilikiwa; bila yake, pairing ambiguous ni taarifa kama onyo conformance na kwamba snippet ni kushoto unchecked.
⚠️
Hatua ya kuangalia drift ni kwamba faili daraja na nakala yake jopo ni nakala mbili za mpango mmoja na itakuwa tofauti. php tools/sync_connector_bridge_snippets.php --applyKisha, rudisha tena pakiti.

Mlango wa mlango, katika lugha sita

Ukaguzi sawa wa nne katika utaratibu huo kila mahali: kushindwa kufungwa na hakuna ufunguo, njia moja, kulinganisha wakati wa mara kwa mara muhimu kutoka kwa kichwa, kisha kuunganisha. mtego pekee ni kulinganisha, na ni mtego tofauti katika kila lugha.

⚠️
Kulinganisha na SHA-256digests ya funguo mbili badala ya funguo wenyewe. Ni sahihi katika kila lugha, na ni sidesteps ukweli kwamba kadhaa mara kwa mara comparators ama kutupa au leak juu ya urefu mismatch — Muda wa Node SafeEqual inafufua Range Error wakati buffers tofauti kwa urefu, ambayo kugeuka ufunguo makosa katika muda mrefu500Badala ya kuwa na A403.
Node.js — Mlango wa mlango
// Node.js — no dependencies
const http = require("http"), crypto = require("crypto"), url = require("url");

const BRIDGE_KEY = process.env.OPSIQ_BRIDGE_KEY || "";   // empty = bridge OFF

const sameKey = (a, b) => {
  const ha = crypto.createHash("sha256").update(String(a)).digest();
  const hb = crypto.createHash("sha256").update(String(b)).digest();
  return crypto.timingSafeEqual(ha, hb);                 // equal lengths, always
};
const out = (res, payload, code = 200) => {
  res.writeHead(code, { "Content-Type": "application/json; charset=utf-8",
                        "Cache-Control": "no-store" });
  res.end(JSON.stringify(payload));
};

http.createServer(async (req, res) => {
  if (BRIDGE_KEY.length < 24)         return out(res, { success: false, error: "bridge_not_configured" }, 403);
  if (req.method !== "GET")           return out(res, { success: false, error: "method_not_allowed" }, 405);
  const given = req.headers["x-opsiq-bridge-key"] || "";
  if (!given || !sameKey(BRIDGE_KEY, given))
                                      return out(res, { success: false, error: "forbidden" }, 403);

  const q = url.parse(req.url, true).query;
  // ... dispatch on q.op / q.do exactly as the PHP bridge does
}).listen(process.env.PORT || 8787);
Python - mlango wa mbele
# Python — Flask
import hashlib, hmac, os
from flask import Flask, request, jsonify

app = Flask(__name__)
BRIDGE_KEY = os.environ.get("OPSIQ_BRIDGE_KEY", "")      # empty = bridge OFF

def same_key(a: str, b: str) -> bool:
    return hmac.compare_digest(
        hashlib.sha256(a.encode()).digest(),
        hashlib.sha256(b.encode()).digest(),
    )

def out(payload, code=200):
    resp = jsonify(payload)
    resp.status_code = code
    resp.headers["Cache-Control"] = "no-store"
    return resp

@app.before_request
def gate():
    if len(BRIDGE_KEY) < 24:
        return out({"success": False, "error": "bridge_not_configured"}, 403)
    if request.method != "GET":
        return out({"success": False, "error": "method_not_allowed"}, 405)
    given = request.headers.get("X-Opsiq-Bridge-Key", "")
    if not given or not same_key(BRIDGE_KEY, given):
        return out({"success": False, "error": "forbidden"}, 403)
Ruby, NET na Java - kulinganisha sawa
// Go
func sameKey(a, b string) bool {
    ha := sha256.Sum256([]byte(a))
    hb := sha256.Sum256([]byte(b))
    return subtle.ConstantTimeCompare(ha[:], hb[:]) == 1
}

func gate(next http.HandlerFunc) http.HandlerFunc {
    return func(w http.ResponseWriter, r *http.Request) {
        w.Header().Set("Content-Type", "application/json; charset=utf-8")
        w.Header().Set("Cache-Control", "no-store")
        key := os.Getenv("OPSIQ_BRIDGE_KEY")
        if len(key) < 24 { out(w, 403, "bridge_not_configured"); return }
        if r.Method != http.MethodGet { out(w, 405, "method_not_allowed"); return }
        given := r.Header.Get("X-Opsiq-Bridge-Key")
        if given == "" || !sameKey(key, given) { out(w, 403, "forbidden"); return }
        next(w, r)
    }
}

// Ruby
def same_key?(a, b)
  OpenSSL.secure_compare(Digest::SHA256.digest(a.to_s), Digest::SHA256.digest(b.to_s))
end

// C# / .NET
static bool SameKey(string a, string b) =>
    CryptographicOperations.FixedTimeEquals(
        SHA256.HashData(Encoding.UTF8.GetBytes(a)),
        SHA256.HashData(Encoding.UTF8.GetBytes(b)));

// Java
static boolean sameKey(String a, String b) throws Exception {
    MessageDigest d = MessageDigest.getInstance("SHA-256");
    return MessageDigest.isEqual(d.digest(a.getBytes(UTF_8)), d.digest(b.getBytes(UTF_8)));
}

Kujiandikisha kwa kila database ya injini

Mali ya usalama haibadiliki: meza au jina la safu ambalo mlinganiaji anayetolewa lazima achunguzwe dhidi ya schema halisi kabla haijaunganishwa, na kila thamani lazima iwe parameter iliyofungwa. Ni swala la utangulizi tu, tabia ya kunukuu na kifungu cha paging tofauti.

MySQLAidha, naMariaDB

Orodha ya: SELECT TABLE_NAME FROM information_schema.TABLES WHERE TABLE_SCHEMA = ?· Kusimama: sawa dhidi ya information_schema.COLUMNS Pamoja na kuwa pamoja AND TABLE_NAME = ?· Kutaja kwa backticks, mara mbili ya mgongo wowote ndani. LIMIT n OFFSET m.

PostgreSQL

Maoni ya habari_schema, majina ya chini ya kesi, WHERE table_schema = $1 (Kwa kawaida publicQuote na quotes mara mbili, kuongeza quote yoyote ndani. ukurasa na LIMIT n OFFSET mAngalia utawala wa kukunja: kitambulisho kisicho na maneno kimewekwa kwa kesi ya chini, kwa hivyo kulinganisha kesi-kwa makini wakati unapotatua jina.

SQL Mtoa Huduma

Maoni ya INFORMATION_SCHEMA. Quote na mabano ya mraba, mara mbili bracket yoyote ya kufungwa ndani. Uchoraji unahitaji ORDER BY: ORDER BY [id] DESC OFFSET @o ROWS FETCH NEXT @n ROWS ONLY.

SQLite

Orodha ya: SELECT name FROM sqlite_master WHERE type = 'table' AND name NOT LIKE 'sqlite_%'• Nyaraka za: SELECT name FROM pragma_table_info(?) - Tumia fomu hii ya thamani ya meza, kwa sababu ya wazi PRAGMA table_info(x) Taarifa haiwezi kuchukua parameter imefungwa na kuwakaribisha kamba interpolation kuna hasa shimo wewe ni kujaribu kufunga. Quote na quotes mara mbili. LIMIT n OFFSET m.

Oracle

Orodha ya: SELECT TABLE_NAME FROM ALL_TABLES WHERE OWNER = :owner- Kutoka kwa vifungu ALL_TAB_COLUMNS. Kutaja kwa nukuu mbili, na kukumbuka vitambulisho visivyojulikana vya kesi ya UPPER, kinyume cha Ukurasa wa PostgreSQL OFFSET :o ROWS FETCH NEXT :n ROWS ONLY 12c na ya baadaye.

MongoDB

Hapana SQL, kwa hivyo hakuna kitambulisho cha kuingilia kati na vigezo visivyofungwa - nidhamu tofauti ya lengo moja.

Mahitaji ya kuingia kwa injini
-- MySQL / MariaDB
SELECT TABLE_NAME  FROM information_schema.TABLES  WHERE TABLE_SCHEMA = ?;
SELECT COLUMN_NAME FROM information_schema.COLUMNS WHERE TABLE_SCHEMA = ? AND TABLE_NAME = ?;

-- PostgreSQL
SELECT table_name  FROM information_schema.tables  WHERE table_schema = $1;
SELECT column_name FROM information_schema.columns WHERE table_schema = $1 AND table_name = $2;

-- SQL Server
SELECT TABLE_NAME  FROM INFORMATION_SCHEMA.TABLES  WHERE TABLE_SCHEMA = @schema;
SELECT COLUMN_NAME FROM INFORMATION_SCHEMA.COLUMNS WHERE TABLE_SCHEMA = @schema AND TABLE_NAME = @table;

-- SQLite
SELECT name FROM sqlite_master WHERE type = 'table' AND name NOT LIKE 'sqlite_%';
SELECT name FROM pragma_table_info(?);

-- Oracle
SELECT TABLE_NAME  FROM ALL_TABLES      WHERE OWNER = :owner;
SELECT COLUMN_NAME FROM ALL_TAB_COLUMNS WHERE OWNER = :owner AND TABLE_NAME = :tbl;
💡
Kutatua, kisha kutumia jina la RESOLVED. Kamwe kupita spelling caller kupitia swala hata baada ya kuangalia ni - kuangalia jina halisi katika orodha kusoma kutoka schema na interpolate kwamba. Ni gharama chochote na inafunga pengo kati ya "jina hili linalingana kitu" na "hii ni jina mimi nina karibu kukimbia."

MongoDBSheria hizo, bila yaSQL

Hakuna kamba ya swala kuingiza, kwa hivyo watu hufikiri hakuna kitu cha kulinda. Kuna: hati ya chujio. Kupitia simu-supplied JSON moja kwa moja ndani find() Tuma ujumbe wa simu {"$ne": null} au {"$gt": ""} Ambapo ulitarajia thamani, na kimya kuchagua kila hati. Kujenga filter mwenyewe.

MongoDB- ukusanyaji wa ruhusu, scalar-forced filter, projection kama redaction
// Node + the official driver
const names = (await db.listCollections({}, { nameOnly: true }).toArray()).map(c => c.name);

function resolveCollection(given) {
  if (!/^[A-Za-z0-9_.-]+$/.test(given || "")) return null;
  return names.find(n => n.toLowerCase() === String(given).toLowerCase()) || null;
}

const coll = resolveCollection(q.collection);
if (!coll) return out(res, { success: false, error: "unknown_collection" }, 404);

// Build the filter from a validated field and a SCALAR value. Never spread
// caller JSON into it: {"$ne":null} would match every document.
const filter = {};
if (q.where_field) {
  if (!/^[A-Za-z0-9_.]+$/.test(q.where_field))
    return out(res, { success: false, error: "unknown_field: " + q.where_field }, 400);
  filter[q.where_field] = String(q.where_value ?? "");   // String() is the guard
}

// Projection is the redaction allow-list: drop secrets, never return them.
const projection = { password: 0, remember_token: 0, api_key: 0, secret: 0, token: 0 };

const limit = Math.min(Math.max(parseInt(q.limit ?? "25", 10) || 25, 1), 200);
const rows  = await db.collection(coll)
                      .find(filter, { projection })
                      .limit(limit)
                      .skip(Math.max(0, parseInt(q.offset ?? "0", 10) || 0))
                      .toArray();
Majina ya waliochaguliwa kutoka orodha

Hiyo ni maelezo yako_schema. kutatua spelling ya mwombaji dhidi yake na kutumia jina lililochaguliwa.

Kuwezesha kila filter thamani kwa scalar

Kamba () au Nambari () karibu ni ulinzi wote dhidi ya sindano ya operator. hati ambapo ulitarajia thamani ni sawa na NoSQL ya nukuu iliyopotea.

Kuundwa kwa mradi ni utawala wa hatua

Weka maeneo ya siri-umbo katika makadirio hivyo wao kamwe kuondoka server, badala ya kufuta yao kutoka matokeo baadaye.

Kusahau kwa ajili ya single-documents na / au

Futa moja na kutatuliwa _id. Kamwe kufuta Wengi, na kamwe filter wito kusukumwa.

Andika barua pepe zilizoruhusiwa

Sababu ya msingi kamaSQL: jina makusanyo ya kuandika inaweza kugusa, na kukataa wengine kwa maelezo.

Mwisho wa utambulisho katika lugha nyingine

Uchunguzi wa utambulisho ni nusu nyingine ya daraja, na ni HTTP pia. kizuizi cha kutia saini ni sawa katika kila lugha: msingi wa 64url malipo, HMAC-SHA256 ambayo kamba, kujiunga na dot.

Usiandike hii kutoka mwanzo. Mipangilio, Msaada Portal hubeba njia tayari kwa lugha ya bandari (moja-time, ishara ya dakika mbili). Maeneo ya mbali, tovuti yako, Kanuni, C. Recognise watumiaji-katika wateja moja kwa moja hubeba toleo la mazungumzo kwa kila lugha (ishara ya saa moja pamoja na kontrakta wa kuburudisha).
Nini cha kufanya wakati wa kubadili

Wale snippets mint ishara ya PORTAL, ambayo ni kali kwa makusudi: hubeba jti na matumizi moja: kweli na maisha kuhusu120Kwa sababu katika hatua ya pili, aURLDaraja au ishara ya utambulisho wa widget haina yoyote ya hizo na hutumia muda mrefu, dakika kwa masaa.

Nini kinaendelea kuwa sawa

Tovuti_key, iat, exp na ngazi ya juu kuthibitishwa: kweli, pamoja na admin au mteja somo na id na jina la mtumiaji au barua pepe. Same madai, saini moja, siri hiyo.

Vifungu viwili vya kuthibitisha

Sehemu tatu JWT ilisaini kazi za HS256, na hivyo hufanya malipo ya sehemu mbili ya msingi wa 64url pamoja na hex HMAC kwamba kumbukumbu ya PHP hutoa. Tumia maktaba yoyote ya lugha yako kufanya asili - maktaba ya JWT kawaida ni njia fupi nje ya PHP.

Kamwe usifungue kwenye browser

Kweli katika kila lugha. Kujiandikisha kwa mteja inamaanisha kusafirisha siri ya tovuti kwa kila mgeni.

Kuchagua, kwa uaminifu

Programu hii ni PHP

Andika daraja katika PHP. Ina meli katika mfuko, ni drift-checked, na inaweza boot jukwaa mwenyewe kusoma kikao cha kuishi kwa ajili ya uchunguzi wa utambulisho.

Jukwaa la Node

A. Js Bridge meli, ishara na ni drift-checked hasa kama PHP moja. Hakuna kitu ni kutolewa up.

Jukwaa ni Python, Ruby, Go, NET au Java.

Kutoa kupitia snippet ya jopo na kusema hivyo katika mwili wa jopo; usiachie faili katika daraja /, ambapo ulinganifu utakataa kifurushi. Munganisho ni kawaida kabisa: vitendo, watoa mazingira, utambulisho na wageni wote hufanya kazi sawa, kwa sababu hakuna mmoja wao anayeshughulikia kile kinachojibu wito wa HTTP.

Huwezi kuendesha mchakato kwenye mwenyeji wa jukwaa

Kisha muundo wa daraja sio chombo sahihi. Daraja lipo ili kufikia jukwaa kutoka ndani ya jeshi lake mwenyewe. Ikiwa unaweza tu kuifikia kutoka nje, unaandika kawaidaAPIKuingiliana na kitu chochote ambacho kinaonyeshwa.

⚠️
Moja zaidi ya kikwazo thamani ya kupanga karibu: uchunguzi wa utambulisho ina kusoma kikao cha kuingia jukwaa, ambayo kwa kawaida inamaanisha kukimbia ndani ya mchakato wa jukwaa mwenyewe au angalau juu ya mwenyeji wake na upatikanaji wa duka lake la kikao. Daraja lililoandikwa katika lugha tofauti kutoka jukwaa linaweza kuhudumia data kwa urahisi na bado linajitahidi kujibu op =admin_identity. Ikiwa hiyo ni kesi yako, meli daraja la data katika lugha yako na uchunguzi wa kitambulisho katika jukwaa.
Viunganishi

Kutoa Msaidizi wa Nusu: Vitendo na Mazingira

Hii ni jambo moja la kawaida kukosa kutoka kwa kontakt kwamba "kazi lakini haina maana". Hatua basi AI kufanya mambo. sehemu ya muktadha hebu kujua mambo. kontrakta mahitaji yote mawili, na maswali mengi admin anauliza ni akajibu kwa mazingira, kamwe kwa hatua. unganisho na vitendo kamili na hakuna mtoa huduma wa muktadha ataripoti ukweli kwamba haiwezi kuona chochote.

nusu ya

Jinsi ya kufanya hivyo - jinsi ya kufanya mambo

Imetangazwa katika vitendo.json au kurejeshwa kwa hatua za kujiandikisha (). Mfumo unachagua moja, unajaza vigezo vyake, na OpsIQ hutekeleza. Vitendo ni kwa vitenzi: kufuta uhifadhi huu, kufungua tiketi hiyo, kubadilisha hali hii.

Sehemu ya Mazingira - Jinsi AI Inavyojua Mambo

Imekusanywa na ContextProvider kabla ya mfano anaendesha. "Ni amri ngapi mwezi huu", "ni wateja wangu wapya zaidi," "tunauza nini" wote kutatua kupitia kuangalia mazingira, na kamwe kugusa hatua wakati wote.

⚠️
Symptom ya mtoa huduma aliyekosekana: Msaidizi anajibu "Hakuna kontakt kuwezeshwa zinazotolewa sehemu hii muktadha" wakati kiunganishi ni imewekwa, enabled na kupitisha uhusiano wake mtihani. Hakuna ni watumiaji, hakuna makosa. ujumbe huo maana hakuna mtoa huduma alidai sehemu hiyo.

Sehemu ya Universal ya msamiati

OpsIQKazi yako ni kuamua nini kila mmoja ina maana kwenye jukwaa lako na kujibu.Kununua hoteli ni amri ya hoteli; chumba ni kile ambacho hoteli huuza.

Amri / amri ya kusubiri

Chochote shughuli ni kwenye jukwaa yako: maagizo, uhifadhi, kutoridhishwa, kazi, usafirishaji. pending_orders ni orodha hiyo imechujwa kwa wale wasiomaliza.

Wateja wa wateja

Orodha ya wateja.

products

Nini jukwaa linauza: bidhaa, vyumba, mipango, huduma.

Billing ya

Mapato na jumla ya fedha, pamoja na hesabu za serikali.

tiketi, huduma, vikoa, server, shughuli

Tumia hizi wakati jukwaa lako linawashikilia kwa kweli. Usilazimishe ramani - sehemu isiyojibiwa ni bora kuliko ile mbaya.

Chochote kingine ambacho tovuti yako ina

Mtangazaji wako mwenyewe. mtoa huduma anayetangaza sehemu (): [' leseni’, 'ushirika’] ina wale waliojiunga katika orodha ya kuruhusu-orodha ya jukwaa maalum kuwa inapatikana bila mabadiliko ya msingi.

Makosa ambayo yanagharimu siku moja

Mtoa mazingira lazima kutekeleza interface. aina ya Usajili-checks ni, hivyo darasa kwamba tu kuangalia haki ni amekosa - bila kosa, popote.

ContextProvider. php - mkataba, kutoka mfuko wa kumbukumbu ya Botble
use OpsIQ\Platform\ContextProviderInterface;

/* MUST implement ContextProviderInterface: ContextRegistry::collectAll()
 * type-checks it, so a provider that merely LOOKS right is skipped and every
 * section answers "No enabled connector supplied this context section" — the
 * exact symptom, with no error anywhere. */
final class ContextProvider implements ContextProviderInterface
{
    public function slug(): string  { return 'yourplatform_context'; }
    public function label(): string { return 'Your Platform (orders, customers, products)'; }
    public function priority(): int { return 30; }   // lower renders earlier

    /** ADMIN only. The guest surface has its own provider and its own rules. */
    public function surfaces(): array { return ['admin']; }

    /** The universal section names this connector can answer. */
    public function sections(): array
    {
        return ['orders', 'pending_orders', 'clients', 'products', 'billing'];
    }

    public function isAvailable(): bool
    {
        try {
            $s = \OpsIQ\Connectors\ConnectorRegistry::getSettings('yourplatform') ?: [];
            return trim((string)($s['base_url'] ?? '')) !== '' && trim((string)($s['api_key'] ?? '')) !== '';
        } catch (\Throwable $e) {
            return false;
        }
    }

    public function build(array $ctx): string
    {
        $section = strtolower(trim((string)($ctx['section'] ?? '')));
        $limit   = max(3, min(50, (int)($ctx['limit'] ?? 20)));
        $query   = trim((string)($ctx['query'] ?? ''));
        try {
            switch ($section) {
                case 'orders':
                case 'pending_orders': return $this->orders($limit, $query, $section === 'pending_orders');
                case 'clients':        return $this->customers($limit, $query);
                case 'products':       return $this->products($limit);
                case 'billing':        return $this->billing();
            }
        } catch (\Throwable $e) {
            return '';   // a provider must NEVER break prompt assembly
        }
        return '';
    }
}
Kujiandikisha kutoka kwa Connector

Tumia ContextConnectorInterface na urudishe watoa huduma wako kutoka kwa muktadha waProviders (). darasa la kontakt linaweza pia kutekeleza MuktadhaProviderInter uso moja kwa moja na kusajiliwa kama yenyewe.

Rejea maandishi ya wazi, sio JSON

Kujenga () inarudi kizuizi cha maandishi ambacho kimeingizwa kwa haraka. Andika kwa msomaji: kichwa, kisha mstari mmoja kwa kila mstari.

“Kurejea” badala ya kukurupuka

Kupata isipokuwa yako mwenyewe. mtoa huduma kwamba kutupa ni watumiaji na imeruka, lakini kurudi ' ni mkataba.

Kwa mfano, huwezi kuandika sehemu () kwa ajili yako.

Sehemu ya meli iliyozalishwaProvider. php (): safu {rejea [; } na mchawi hana shamba kwa ajili yake. Jaza kwa mkono - na kumbuka kwamba republishing kutoka kwenye faili mchawi OVERWRITES faili. nakala hariri yako kwanza.

⚠️
Hali TOTAL kweli, si idadi ya safu wewe alimtuma. ukurasa si jumla. mtoa huduma kwamba orodha ya mistari ishirini bila kusema hivyo anapata msaidizi ujasiri kujibu "Wewe kuwa na uhakika"20"Malipo" wakati jukwaa linaingia669Akaunti moja ya bei nafuu na mstari mmoja wazi - "TAL juu ya faili:669(Picha hii inaonyesha kuwa ni mpya zaidi20Ni kweli kabisa, na kila kitu ni kibaya zaidi kuliko kile ambacho watu hawakijui.
Sehemu ya kifungu ambacho hakiwezi kuchanganywa
$lines = ['YOUR PLATFORM — ORDERS (live, newest first)'];
$lines[] = 'TOTAL orders on file: ' . (int)$total
         . ' (this list shows the newest ' . count($rows) . ' only — never count these rows to answer "how many")'
         . ' | by status: ' . $byStatus;
foreach ($rows as $r) {
    $lines[] = '#' . (int)$r['id'] . ' ' . $r['reference'] . ' | ' . $r['status']
             . ' | amount ' . $r['amount'] . ' | ' . substr((string)$r['created_at'], 0, 16);
}
$lines[] = 'Use yourplatform_get_order (order_id) for the full record.';
return implode("\n", $lines);

Andika matendo yako kama yalivyoOpsIQUnaweza kusoma kutoka kwa maandishi

OpsIQInaainisha hatua kwa maneno katika utendaji wake_id, na ni kihafidhina kwa makusudi: chochote haiwezi kutambua inachukuliwa kama kuandika na inahitaji kadi ya idhini. Kupata kitenzi haki na kusoma tu anaendesha.

1
Kuharibu au inahitaji ushindi wa kuthibitisha

Ikiwa imewekwa, hatua inahitaji idhini kila wakati. Kuwajulisha kwa uaminifu - hii ndio inayofunika kadi ya kibali cha admin.

2
Kuandika neno popote katika id hufanya kuwa kuandika

kuongeza, kuunda, kufungua, kurekebisha, kubadilisha, kurekebisha na kufuta, kuondoa, kuharibu, kufuta, kurejesha, kusitisha, kukomesha, kupitisha, kutuma, kuweka alama, upya, kukamata, utupu, kufunga, kufungua tena, kugawa, kutoa, kuweka, kuingiza, kuwezesha, kuzuia, kutoa , kuzalisha, malipo, kulipa, utoaji, upya , kuboresha, kuunganisha, kuhamisha, kuhamisha , kuenea, bendera, kujiandikisha, sync, kushinikiza, kuagiza, kushinikiza , kukimbia, kuanza, kuanzisha, kuacha, kusimamisha, kuanza na wachache zaidi.

3
Kisha kusoma neno hufanya kuwa kusoma

kupata, orodha, utafutaji, kutafuta, kuona, kuonyesha, kuchota, kuhesabu, lookup, kuelezea, kusoma, kuuza nje, preview, mtihani, ping, hali, muhtasari, maelezo, historia ya hivi karibuni, angalia, kumbukumbu, takwimu, metrics, jumla, mapato, kuvunjika, ripoti, analytics, usawa, matumizi, upendeleo, snapshot, ufahamu, kulisha, rasimu, triage, classify, zinaonyesha.

4
Kwa hiyo, mfumo wa HTTP huamua

Soma, pitia na utafakari kuhusu.

5
Kwa maneno mengine, ni barua

Bila kutambua maana ya idhini inahitajika, default hiyo ni makusudi.

⚠️
Andika maneno yamezingatiwa kabla ya kusoma maneno, hivyo jina lililochanganywa kama get_and_sync_orders limeainishwa kama WRITE. Chagua kitenzi kimoja, weka kwanza, na kuiweka safi: orodha_ taratibu, kupata_customer, search_bookings, kufuta_bookling, kuweka utaratibu_status.

Tu kutangaza asili_api kama jukwaa kweli ina moja

The native_api capability registers a generic <slug>_api_call passthrough so the model can reach endpoints your typed actions do not cover. On a platform with no API it is worse than useless: the model keeps reaching for a tool that cannot succeed, instead of using the tools that can.

Muumba anaamua kutoka kwa jibu lako la upatikanaji wa data

Say the platform has an API and it declares native_api and emits the passthrough. Say it has none (bridge mode, or the "Platform with no API" profile) and it declares platform_bridge instead and strips native_api, so the two can never both be true. You no longer hand-edit this.

Vifaa vya mkono vilivyoandikwa lazima vipate haki

Ikiwa unaandika wazi mwenyewe, utangaza moja ya asili_api au jukwaa_bridge. Ushirikiano unashughulikia jukwaa_ daraja kama kiunganishi cha kutoroka kinatarajiwa kuwa, na Mjenzi anakataa spec ambayo inadai jukwaa_daraja kwenye kontakt ya API.

Kuwa na ai_api_reference. md uaminifu kwa njia yoyote

On a connector that declares native_api the admin brain heads that file with a line naming <slug>_api_call. Without native_api it is headed neutrally instead, so a bridge connector no longer advertises a tool it does not have. Describe your real surface — for a bridge, that is your op and do vocabulary, not a REST endpoint table.

Jifunze jinsi ya kusimamia ubongo wako juu ya jukwaa

Declare ai_brain_aware and ship two Markdown files. They are read from the INSTALLED package directory (opsiq/connectors/<slug>/) for ENABLED connectors only, and injected into the admin agent's system prompt.

ai_expertise_admin.md

Nini jukwaa hili ni, jinsi data yake ni umbo, nini vitu vyake ni kuitwa, na quirks ambayo vinginevyo kufanya msaidizi nadhani. kuandika kwa mwenzake mwenye uwezo ambaye hajawahi kuona jukwaa.

ai_api_reference.md

Uso wa simu. Kwa kiunganishi cha daraja hili ni op yako na fanya msamiati na vigezo vyao, sio meza ya mwisho ya REST.

Bajeti ya Bajeti

Kwa kiasi6,000wa mawasiliano kwa njia ya simu, na kuhusu24,000Wahusika kwa block nzima katika kila kontakt kuwezeshwa. Juu ya cap per-connector faili yako ni truncated; kuwa mafupi kabla truncator ni.

Malipo ya moja kwa moja

Faili hizi ni tofauti kati ya msaidizi kutumia zana yako ya meza na kujibu kutoka sehemu isiyo sahihi kwa sababu hakuna kitu kilichoiambia kuwa zana hizo zilikuwepo.

💡
Faili zote mbili lazima ziwe katika mfuko wa INSTALLED, sio tu mti wako wa chanzo. Ni faili za kawaida za mfuko, kwa hivyo zinafunikwa na saini na kusafirishwa katika ZIP - ambayo pia inamaanisha kuhariri moja baada ya kusainiwa kuvunja muhuri.
Viunganishi

Utambulisho kupitia kiunganishi: admin, mteja, portal

Mkataba mmoja wa kusaini hutumikia nyuso tatu. kazi ya kontakt ni kugeuka "ambaye ameingia kwenye jukwaa" katika ishara iliyosainiwaOpsIQkuweza kuthibitisha na kisha kutoa taarifa kwa vyombo vya habari.OpsIQs sura. kontakt kamwe inathibitisha mtu yeyote - jukwaa hufanya, na saini hubeba madai hayo.

Tatu, moja ya alama

Mtawala – ndani ya moyo wako

Somo la admin. widget mizigo ndani ya jopo la admin jukwaa na kila mwanachama wa wafanyakazi ni sawa na yao wenyeweOpsIQBonyeza kwenye ukurasa wa admin widget.

Wateja - mteja aliyesainiwa, katika mazungumzo ya wateja

Hii ndiyo inayowezesha mtumiaji kuingia kwenye akaunti yao ya WHOLE badala ya kuangalia bila kujulikana: kila utaratibu, maelezo kamili, na hatua yoyote ya huduma unayoruhusu.

Portal - kiungo cha kina katika portal ya msaada

pamoja na madai ya Jti na single_use, pamoja na120maisha ya pili, kwa sababu ishara husafiri katika aURLNa lazima iweze kutumika mara moja.Usiweke mkono huu: Mipangilio, Msaada Portal hubeba snippet tayari kwa kila lugha, na jukwaa linakuhimiza wakati eneo la akaunti linaendesha kwenye seva hii.

Mkataba wa payload

Haya ni madai ya uhakiki kuangalia. Hakuna hapa ni hiari, chochote mfano sehemu nyingine inaweza kupendekeza.

site_key

Kiwango cha juu. lazima sawa na ufunguo wa tovuti ya ombi, au ishara inakataliwa.

iat na exp

Ngazi ya juu, sekunde za unix. exp lazima iwe katika siku zijazo na baada ya iat. Ishara zaidi ya dakika moja baadaye inakataliwa.

Inayofuata:Kweli

Ngazi ya juu, kando na exp. Jukwaa lako linadai kwamba binadamu halisi ni watumiaji katika.

Jukwaa la jukwaa

Kiwango cha juu. slug fupi ya jina la asili. Imependekezwa, na inaruhusu mtoa utambulisho wa kiunganishi kuwaambia ishara zake mwenyewe kutoka kwa jukwaa lingine.

Usimamizi au Wateja

Kitu kinachotaja mada hiyo. Lazima kibebe kitambulisho kisicho na hatia, na jina la mtumiaji au barua pepe - lango la ufikiaji wa kila-admin lina mechi hizo.

Kuchanganya, verbatim kutoka daraja la Botble
$payload = [
    'site_key'      => $cfgSiteKey,
    'iat'           => time(),
    'exp'           => time() + 6 * 3600,
    'authenticated' => true,
    'platform'      => 'yourplatform',
    /* 'admin' or 'customer' — OpsIQ stamps the matching session identity
     * from whichever key is present. */
    $opsiqSubject   => $subjectPayload,
];
$payload64     = rtrim(strtr(base64_encode(json_encode($payload, JSON_UNESCAPED_SLASHES)), '+/', '-_'), '=');
$identityToken = $payload64 . '.' . hash_hmac('sha256', $payload64, $cfgSecret);

mbili na kushindwa kwao.

OpsIQIna dalili mbili za kuthibitisha, na hawakuwa sawa. Kujua hii inakuokoa mchana, kwa sababu dalili haionekani kama sababu.

Mfumo wa uendeshaji una sifa zake mwenyewe

opsiq/embed/admin_ajax. php hubeba verifier ya ndani ambayo inakubali bendera iliyothibitishwa katika nafasi yoyote. Orodha ya mazungumzo, historia na haijasoma yote inakwenda kupitia hiyo, kwa hivyo wanathibitisha faini.

Kuingiliana kwa waya ni ngumu zaidi

opsiq/ inajumuisha / mteja_identity_token_verify.php inakaa nyuma ya mkondo wa mazungumzo na msingi wa AJAXAPI"Kihistoria ilikuwa ni lazima bendera ipepee katika ngazi ya juu.

Dalili ya

Kila mazungumzo hugeuka majibu "Admin login required". Inasoma kama mdudu kikao na si: ishara ni kukosa bendera ya ngazi ya juu.

Nini cha kufanya sasa msingi

Sasa inakubali bendera katika ngazi ya juu au ndani ya somo, hivyo mkataba ni sare. Wazee cores kusoma tu kiwango cha juu.

Hii ni mashine-checked sasa. faili yoyote katika mfuko wako kwamba ishara za utambulisho wa mints ni statically scanned dhidi ya mkataba, na payload jukwaa bila kukataa kukubaliana na faili halisi na mstari. Run mwenyewe: php zana / uthibitisho_identity_ contracts. php.

Wateja wa ndani katika mazungumzo ya mteja

Mambo mawili lazima yawe kweli. Core lazima stamp mteja kuthibitishwa, na kontakt yako lazima sasa.

1
Daraja lako au mwisho wa pointi unaashiria ishara ya mteja

Mtia saini sawa kama msimamizi, na somo la mteja. Soma mteja kutoka kikao cha jukwaa mwenyewe. Ikiwa jukwaa lako linaashiria wateja katika walinzi tofauti kutoka kwa admins, soma mlinzi unataka na usirudi nyuma kwenye masomo - ndivyo mteja atakabidhiwa ishara ya admin.

2
Msingi wa kuthibitisha na stamping ni

Kwa ishara halali, stamps msingi somo kuthibitishwa katika kikao. mtoa huduma wako anasoma utambulisho kuthibitika; kamwe inathibitisha.

3
Mwandishi wako wa habari anathibitisha

Mgunduaji () anarudi sura ya OpsIQ. Lazima kutekeleza OpsIQ \IdentityProviderInterface, au Usajili unaruka kimya - mtego huo kama mtoa huduma wa mazingira.

4
Wateja wako wanaovutiwa na wateja kukubali mteja_id

Na kwa kuwaOpsIQInafunga utambulisho uliothibitishwa kabla ya utekelezaji. mfano hauwezi kuisambaza.

IdentityProvider. php - soma utambulisho uliothibitishwa, uwasilishe katika sura ya OpsIQ
use OpsIQ\Platform\IdentityProviderInterface;

final class IdentityProvider implements IdentityProviderInterface
{
    public function slug(): string  { return 'yourplatform_identity'; }
    public function label(): string { return 'Your Platform identity (bridge-signed identity_token)'; }
    public function priority(): int { return 25; }   // ahead of the generic session provider

    public function isAvailable(): bool
    {
        try {
            $s = \OpsIQ\Connectors\ConnectorRegistry::getSettings('yourplatform') ?: [];
            return trim((string)($s['base_url'] ?? '')) !== '';
        } catch (\Throwable $e) { return false; }
    }

    public function detectAdmin(): ?array
    {
        $row = $this->sessionRowFor('_opsiq_admin_identity');
        if (!$row || !$this->isOurs($row)) return null;
        return [
            'id'       => (int)($row['id'] ?? 0),
            'name'     => $this->displayName($row, 'Admin'),
            'email'    => (string)($row['email'] ?? ''),
            'username' => (string)($row['username'] ?? ''),
            'role'     => (string)($row['role'] ?? ''),
            'platform' => 'yourplatform',
            'source'   => 'yourplatform_identity_token',
        ];
    }

    public function detectCustomer(): ?array
    {
        $row = $this->sessionRowFor('_opsiq_customer_identity');
        if (!$row || !$this->isOurs($row)) return null;
        return [
            'id'       => (int)($row['id'] ?? 0),
            'name'     => $this->displayName($row, 'Customer'),
            'email'    => (string)($row['email'] ?? ''),
            'phone'    => (string)($row['phone'] ?? ''),
            'platform' => 'yourplatform',
            'source'   => 'yourplatform_identity_token',
        ];
    }

    /* A session identity stamped by ANOTHER platform's token must not be
     * claimed here. An empty platform is accepted because older bridges did
     * not stamp one, and the site key already scoped the token. */
    private function isOurs(array $row): bool
    {
        $p = strtolower(trim((string)($row['platform'] ?? '')));
        return $p === '' || $p === 'yourplatform' || $p === 'remote';
    }

    private function sessionRowFor(string $key): ?array
    {
        if (session_status() !== PHP_SESSION_ACTIVE) return null;
        $row = $_SESSION[$key] ?? null;
        return (is_array($row) && (int)($row['id'] ?? 0) > 0) ? $row : null;
    }
}

Bidhaa za Kuingiliana: mbili, zote zinahitaji

Mfano lazima kamwe kuchagua data ambayo inasoma. OpsIQ inatekeleza kwamba upande wake, na jukwaa lako lazima litekeleze kwa upande mwingine pia. lock moja ni mdudu mbali na uvujaji; kufuli mbili ni mkataba.

Lock ya1 — OpsIQKufafanua vigezo vya utambulisho

Kabla ya hatua ya kuzungumza kwa wateja, OpsIQ inachukua nafasi ya kila parameter ya utambulisho wa mgeni aliyethibitishwa na kitambulisho cha VERIFIED: mteja_id, mteja_d, mtumiaji_id , mtumiaji-id, akaunti_id kuchukua ID iliyohakikishiwa; Mteja_identifier, mteja wa akaunti_idifier anaichukulia kama kamba; barua pepe, mteja / email, customer_email, user_Email, mtumiaji.

Lock ya2- Jukwaa lako linaelezea kila swala

Chukua kitambulisho ulichopewa na uongeze kwenye kifungu cha kila kusomwa kwa kila maandishi na kila kuandika juu ya uso huo. Usiamini kumbukumbu katika ombi peke yake. mteja aliyesainiwa akiuliza kuhusu amri ya mtu mwingine lazima arudi tupu, sio marufuku.

Jina lako la kikoa ni hivyo kufunga1Unaweza kupata yao

Piga simu kwa mteja_id, sio cust au ref. parameter OpsIQ haiitambui ni parameter ambayo haiwezi kufunga.

⚠️
Wape wateja waliotiwa saini kwenye shughuli zao za OWN, tofauti na admins, hata wakati SQL inaonekana sawa. nyuso mbili zilizo na sheria tofauti zinabaki kuwa waaminifu; uso mmoja na bendera inakuwa uvujaji siku ambayo mtu huhariri tawi lisilo sahihi.

Zero ukurasa wiring: kontakt-kutangazwa uchunguzi

You can spare the operator all page wiring. Add an admin_identity_probe_url setting (https only) pointing at your identity endpoint. The plain admin-widget loader from Remote Sites, Codes then works with no page attributes at all: the widget discovers the endpoint through the connector, calls it with the site key and widget token, and authenticates each admin individually. A page can still override with a data-identity-endpoint attribute or window.OpsIQAdminIdentityEndpoint.

mipangilio.json-Kufanya uchunguzi wa
{
  "key": "admin_identity_probe_url",
  "label": "Admin identity probe URL",
  "type": "text",
  "placeholder": "https://your-site.com/opsiq-yourplatform-bridge.php?op=admin_identity",
  "help": "Set this to your bridge admin_identity endpoint and the plain admin-widget loader works with NO page wiring: the widget probes this URL by itself, the bridge answers with the signed identity of the CURRENTLY logged-in admin, and every admin is matched to their own OpsIQ agent. Leave empty to keep the admin embed off."
}
Uchunguzi huo umeitwa na browser

Uthibitishaji wake ni kikao cha jukwaa. Weka AHEAD ya lango lako la ufunguo wa daraja, iweka mbali na data ya rekodi, na usirudie chochote kwa mgeni aliyeingia.

Inajibu kwa muundo wa kawaida

{"success":true,"authenticated":true,"admin":{...},"identity_token":"..."} — and {"success":false,"authenticated":false,"error":"..."} when nobody is signed in.

Hakuna siri ya muda mrefu katika chanzo cha ukurasa

Ni tu kwa ajili ya ishara, na ni bure.

ya mwisho kwa ajili ya kazi za sanaa,WordPress, WHMCS, Symfony na PHP wazi, pamoja na maalum ngumu-won Laravel na utaratibu wa matatizo, ni juu ya admin widget ukurasa. Wao ni msimbo huo kwa ajili ya mteja somo: mabadiliko walinzi wewe kusoma na ufunguo somo ishara.

Viunganishi

Kuchapisha: kuchapisha folda sio kuchapisha

Njia ya kawaida ya kupoteza mchana ni kuhariri kontakt chini ya soko_connectors /, usakinisha, na kupata kitu kilichobadilika. Installs hazisoma folda hiyo. Wanavuta ZIP iliyosainiwa kutoka kwenye orodha ya soko. Uchapishaji ni mlolongo unaoweka mabadiliko yako katika ZIP hiyo.

Kwa nini Bocco hakufanya chochote

marketplace_connectors/<slug>/ is the SOURCE

Ni mahali ambapo kazi, hakuna kitu kinachoingia.

Kamati ya Bunge yaidhinisha ZIP

Kupakuliwa kwa kufunga ambayo ZIP, inathibitisha saini, na kuifungua. Mpaka ujenge upya ZIP kila usanikishaji unaendelea kupata mfuko wa zamani.

Mwandishi wa habari atangaza mahali pengine

It writes into /connectors/<slug>/ on this install. That is a local connector, not a marketplace release. The two paths do not overlap.

Utaratibu wa Kufunguliwa

1
Weka faili katika faili mbili

mipangilio.jsonKwa upande wake Meneja wa Kampuni ya Konferensi_Company.jsonUunganisho unalinganisha nao na inashindwa ikiwa slug, toleo au uwezo uliowekwa haukubaliani. Ongeza kuingia kwa CHANGELOG.md wakati uko hapo - ni faili inayohitajika.

2
Kurudisha daraja la Snippet

php tools/sync_connector_bridge_snippets.php --apply — only relevant if your package ships bridge/*.php, and mandatory if it does. Skipping it means the panel hands operators the previous bridge.

3
Kurudisha kila pakiti

php zana / resign_all_connectors. php - saini inashughulikia faili hashes, hivyo hariri yoyote invalidates yake. Sign mwisho, baada ya kila faili ni ya mwisho.

4
Kuhamisha funguo za kuingia, kisha ubofye

Mtazamaji anaashiria kila mfuko kama hujenga ZIP, na inaendesha katika muktadha ambapo ufunguo hauwezi kusomwa kutoka kwa mipangilio - hivyo lazima uje kutoka kwa mazingira.

5
Download mchezo Kutoroka, kama wewe ni mmoja

Kurejesha kontakt updates mfuko. Haigusa nakala ameketi katika mtandao operator wa mtandao. Waambie, katika jopo na katika changelog.

Kwa ujumla, kwa utaratibu
# 2 — hold the panel copy identical to the shipped bridge
php tools/sync_connector_bridge_snippets.php --apply

# 3 — re-sign (do this last, after every file is final)
php tools/resign_all_connectors.php

# 4 — the seeder reads the signing key from the ENVIRONMENT only
export OPSIQ_CONNECTOR_SIGNING_KEY="$(php -r 'require "bootstrap/init.php"; echo opsiq_setting("connector_signing_key","");')"
php saas/scripts/maint/seed_marketplace_free.php --apply --only=<slug>

# verify before and after
php tools/verify_identity_contracts.php
php vendor/bin/phpunit tests/phpunit/Unit/Connectors
⚠️
Kwa nini mauzo ya nje sio hiari: msaini anaangalia ufunguo katika OPSIQ_CONNECTOR_SIGNING_KEY kwanza na kiunganishi_signing_key kuweka pili. seeder anaendesha kwenye bootstrap ya SaaS na zana / ishara_connector.php boots chochote wakati wote, hivyo katika msomaji wa mazingira yote mawili haipo - bila kutofautiana kwa mazingira hakuna ufunguo, na unapata "Hakuna kitufe cha kusaini kinapatikana" au kila kifurushi kilichoripotiwa kama saini_failed.OpsIQUnaweza kupata ufunguo mwenyewe.

Nini hasa ni meli

Tu faili saini inashughulikia

ZIP ni kujengwa kutoka orodha ya saini mwenyewe faili, hivyo kupotea faili ameketi katika folda yako mfuko si kusafirishwa. Hiyo ni makusudi: faili unsigned kutumika kwapanda pamoja na wateja.

Kuongezewa muda

ya php,jsonKwa upande wake, Dk.css^ Tnn., “mfumo wa nuru.”html, sh, svg, png, jpg, jpeg, gif, webp, ico, yml, yaml - recursively, ikiwa ni pamoja na daraja / na vipimo / saini.jsonyenyewe ni kutengwa na hashes na kisha aliongeza kwa ZIP hivyo kufunga unaweza kuthibitisha.

Kila kitu kinaelezwa kama kisichoandikwa

Mtazamaji hutaja kila faili iliyoachwa nyuma. soma orodha hiyo. Faili uliyotarajia kusafirisha kuonekana kuna maana ya ugani usiofaa au mahali pabaya - sio mafanikio ya kimya.

Kuhamisha faili yoyote iliyofunikwa kuvunja muhuri

Ikiwa ni pamoja na faili ya Markdown, rudisha upya mfuko huo.

Nyaraka zinazohitajika katika mfuko wa usambazaji

connector.php

Lazima urudishe mfano wa ConnectorInterface.

settings.json

Manifest: slug, jina, toleo, manifest_version, utangamano, uwezo, kiunganishi_mkataba_ugeuzi, mipangilio.

connector_contract.json

Mkataba wa kusoma mashine. slug yake, toleo na uwezo kuweka lazima kuwa sawa na mazingira.json

README. md, DEVELOPER. mD, ChangeLOG. mdi

Wote watatu wanakaguliwa kwa kuwepo na ukubwa mdogo. DEVELOPER. md inahitaji maudhui halisi, sio stub.

Taarifa kwa mujibu wa uwezo uliotangazwa

Kila uwezo wa jina faili anatarajia - ContextProvider. php kwa muktadha, IdentityProvider php kwa utambulisho, GuestLookupProvider, na kadhalika - isipokuwa kiunganishi anatekeleza uwezo wa inline.

Hakuna kitu kinachoonekana kama imani

Conformance scans tatu Markdown faili kwa ajili ya maadili siri umbo na funguo binafsi, na inashindwa juu ya hit.

Angalia kabla ya kupanda

Suite kamili ya usawa ni moja ambayo imewekwa. Inaangalia wazi dhidi ya mkataba wa canonical, kwamba uwezo wa kukimbia na wazi wanakubaliana, kwamba kila uwezo uliotangazwa una faili yake na mbinu zake, mkataba wa utambulisho-kuongezeka katika kila faili ndogo, mechi ya daraja-snippet, utazamaji wa mgeni huruhusu usafi, utendaji wa kipekee na usalama wa uthibitisho, na saini ya mfuko.

Kushikilia kila kitu kabla ya kila hatua
# conformance for every marketplace package
php tools/test_marketplace_connector_conformance.php

# the identity-token contract, statically, with file:line on failure
php tools/verify_identity_contracts.php

# the connector unit suite
php vendor/bin/phpunit tests/phpunit/Unit/Connectors

# the release gate
php tools/release_gate_connectors.php
💡
Kushindwa moja ni inatarajiwa na si tatizo: mfuko saini hundi ripoti onyo wakati wewe bado editing. Ni wazi wakati wewe re-sign. Kila nyingine kushindwa ni moja ya kweli.
Viunganishi

Kuunganisha mfuko na kumbukumbu ya lifecycle

Hii ni mkataba wa ngazi ya chanzo kwa ajili ya kujenga kiunganishi kwamba OpsIQ inaweza kugundua, kusanidi, kuthibitisha, kuwezesha, kutekeleza, mtihani, ishara na kusambaza.

Maelezo ya mtengenezaji
Kuunganisha mfukoMfuko wa kontakt una utekelezaji wa uunganisho unaohitajika na wazi, kwa vitendo vya hiari, mapishi, maarifa, mali na metadata ya saini.Kuunganisha mfukodeveloperMANIFESTv1Maisha ya uwaziKusimamiwaKazi ya kaziKuonekanaMaisha ya kazi ya VIEWconnector.phpUunganisho wa darasa / kiwandainapohitajikasettings.jsonMpangilio wa Mipangilio na Mipangilioinapohitajikaactions.jsonUfafanuzi wa vitendoChaguo lasignature.jsonKuunganisha metadataUhuru wa Kuachiliwa1DECLAREUwazi na uwezo wa2IMPLEMENTMaisha ya rafu na watoaji3Kuwa makiniMtihani, ishara, pakiti
Mfuko wa kontakt una utekelezaji wa uunganisho unaohitajika na wazi, kwa vitendo vya hiari, mapishi, maarifa, mali na metadata ya saini.

Kiwango cha chini cha mfuko

connectors/example_platform/
├── connector.php          # connector implementation / entry point
├── settings.json          # manifest + configuration schema
├── actions.json           # optional action catalogue
├── README.md              # setup, scopes, webhooks and limits
├── workflow_recipes.json  # optional reusable recipes
├── knowledge.json         # optional provider knowledge
├── profile.json           # optional connector profile
├── src/                   # optional client/provider classes
├── assets/                # optional admin assets
└── signature.json         # signed release metadata

Mkataba wa

settings.json Tumia tafsiri ya wazi 1Mthibitishaji anatarajia slug, jina, toleo, onyesho_version, utangamano, maelezo na uwezo. opsiq_min Na kwa kuwa opsiq_max· Kutolewa kwa leseni ni moja ya Uzalishaji wa uzalishaji, beta ya beta, Maoni ya preview au template ya templateUkomavu wa uwezo hutumia viwango vya L1-L6. vifurushi vya urithi vinaweza kuwa kawaida na maonyo, lakini mfuko mpya unapaswa kupita bila onyo.

Nguvu connector interface

  • Utambulisho na Uanzishaji: slug(), name(), description(), capabilities(), settingsSchema(), testConnection().
  • Maisha ya rafu: onEnable() Na kwa kuwa onDisable()Kuharibika lazima kuwa isiyo ya uharibifu; kusafisha data ni operesheni tofauti ya makusudi.
  • Kuingiza / kufuta: handleWebhook(), poll(), backfill(). Poll inashughulikia kazi ya kuongezeka; backfill inaingiza historia na lazima iwe salama kurudia.
  • Msaada: pushReply() ambapo kamati hiyo inakubali kutoa majibu.
  • Hatua za kuchukua: registerActions() mikataba ya utekelezaji wa shughuli za uzalishaji.
  • Usalama wa: securityCapabilities(), syncBlockedIp(), removeBlockedIp(), testSecuritySync().

Msingi wa abstract pia hutoa backfill ya hiari, orodha ya wateja, ugunduzi wa akaunti ya barua pepe / uundaji, wanachama, kutambua admin / mteja, watoa bili / maelezo / utambulisho, uchimbaji wa majibu, kutafuta tena wito wa HTTP, JSON-path upatikanaji, nafasi ya fuzzy na wasaidizi wa pagination.

Uwezo na Uthibitishaji

Majina ya uwezo yanayosaidiwa ni pamoja na vitendo, vichocheo, mazingira, utambulisho, mauzo, bili, inbound_ticket, outbound_reply, sync_users, maingiliano_departments, matukio ya usalama, wateja_import, usalama_native_block, promo_audience, Promo_feed, barua pepe_box, asili_api, ai_brain_kufahamu na ai-tickets. mjenzi hutoa wajenzi API Msingi, msingi, HMAC.OAuth 2sifa za wateja,OAuth 2Kanuni ya idhini na templates za uthibitishaji wa desturi.

Usajili wa Lifecycle

  1. Ugunduzi unabeba mfuko na kuthibitisha yake wazi.
  2. Configuration ni kuhifadhiwa kwa kila nafasi ya kazi; siri ni encrypted.
  3. Jaribio la kuunganisha linathibitisha sifa bila kuwezesha kontakt.
  4. Kuwezesha wito onEnable(), synchronises hatua ufafanuzi na inaweza kuanza backfill ya awali.
  5. Upigaji kura / mtandao wa wavuti / usajili daima hubeba mazingira ya kazi.
  6. Simu mbaya onDisable() na kuacha shughuli bila kufuta data iliyoingizwa.
  7. Uwindaji ni operesheni ya wazi.

Kanuni za Uadilifu

  • Tumia ufunguo wa workspace / tovuti katika kila kusoma, kuandika, muhimu ya cache, muhimu wa deduplication na kuangalia kwa wavuti.
  • Fanya backfill, ingestion ya mtandao na kuandika vitendo vinavyostahili. Rekodi ID ya nje / kitambulisho cha tukio popote jukwaa linapotoa moja.
  • Kwa kutumia mfumo wa mizizi, tumia yao API Kamwe usifikiri kwamba data yako ya kibinafsi iko kwenye meza OpsIQ uhusiano.
  • Kurejea makosa ya muundo, usalama wa wateja. Kamwe kufichua siri, kufuatilia mtoa huduma ghafi au kuwepo kwa kazi nyingine.
  • Kueleza tu uwezo mfuko kweli kutekeleza. actions.json Orodha haifanyi hatua inayoweza kutumika mpaka kontakt imewekwa, kuwezeshwa, kusanidi na uunganisho wake ni halali.

Kuthibitisha na Kuachiliwa

Run PHP lint, uthibitisho wa wazi, vipimo vya uunganisho, majaribio ya schema ya hatua, vipimo vilivyotengenezwa na wavuti / replay, majaribio-isolation ya workspace, vipimo vyake vya backfill-repeat, vipimo vinavyounganishwa na walemavu na kushindwa / jaribio. mfuko wa soko unapaswa kisha kutiwa saini na kuthibitishwa, ni pamoja na kuanzisha /permissions / barua pepe / nyaraka za mtandao, na hali yake ya kweli ya kutolewa.

Viunganishi

Maelekezo ya Kuunganisha

Maelekezo ya hatua kwa hatua kwa ajili ya Mipangilio ya kontakt ya kawaida.

Maelekezo
Kuunganisha mapishiA ya Shopify mapishi ya kuanzisha kama orodha: kuunda programu, mawanda ya ruzuku, ishara ya kuweka na mtihani, kuwezesha webhooks, mahali utaratibu wa jaribio.Kuunganisha mapishiShopifyMapishi · Shopify kwa webhooksTumia App ya Customization katika Shopify Usimamizi wa adminUfafanuzi wa Ruzuku: read_orders, read_customersHifadhi ya kuhifadhi domain + ishara, bonyeza mtihaniKuwezesha Webhook sync (Maoni ya Usajili wa Auto)Weka utaratibu wa mtihani → Inaonekana katika Mauzo katika 30s1STEP BY STEPCopy-paste maelekezo ya2REAL PLATFORMSShopify · WHMCS · Stripe· Fedha za GBP3ya waUchunguzi waonyesha kuwa katika 30s
Kila mapishi ni orodha ya orodha unayofuata juu hadi chini, hapa, Shopify na webhooks halisi ya wakati wa utaratibu, kuthibitishwa na agizo la mtihani.

Mapishi: Shopify Kuwa na Webhooks ya muda halisi

Kwa mfano:
Lengo: Kuunganisha Shopify kwa ajili ya utaratibu wa kawaida na GDPR utekelezaji.
Nini cha kufanya:

1. Create a custom app in Shopify admin (Settings > Apps > Develop apps). 2. Grant scopes: read_orders, read_customers, read_products, write_customers. 3. Copy the Admin API access token. 4. In OpsIQ Connectors > Shopify, enter store domain and token. 5. Click Test Connection. 6. Enable Webhook sync, OpsIQ registers order/customer webhooks automatically. 7. GDPR webhooks register automatically (data_request, customers/redact, shop/redact). 8. Verify: place a test order, check it appears in OpsIQ Sales within 30 seconds.

Mapishi: WHMCS Ushirikiano wa Ushirikiano

Kwa mfano:
Lengo: Kuunganisha WHMCS ili AI inaweza kuangalia wateja, huduma, tiketi, na ankara.
Nini cha kufanya:

1. In WHMCS admin, Setup > Staff Management > Manage API Credentials. Create a key. 2. In OpsIQ Connectors > WHMCS, enter URL, API identifier, and secret. 3. Click Test Connection. 4. Install the WHMCS module addon for ticket relay. 5. Verify: ask the admin AI "Find client [email protected]". WHMCS data should appear.

Malipo ya Stripe

Kwa mfano:
Lengo: Kufuatilia malipo ya Stripe na kuruhusu AI kuangalia shughuli.
Nini cha kufanya:

1. In Stripe Dashboard > Developers > API keys, create a restricted key (read: Customers, Charges, Invoices, Subscriptions). 2. In OpsIQ Connectors > Stripe, enter the restricted key. 3. Test Connection. 4. Add webhook endpoint in Stripe: copy the webhook URL shown on the connector's own settings page. It carries a per-connector token and looks like https://your-domain.com/api/connectors.php?slug=stripe&token=THE_TOKEN A URL without the token is rejected with "Missing slug or token". 5. Select events: charge.succeeded, invoice.paid, customer.subscription.updated. 6. Copy the webhook signing secret to OpsIQ. 7. Verify: make a test payment, check it in OpsIQ Sales.

Maelezo ya Biashara ya Google

Kwa mfano:
Lengo: Kuunganisha GBP kwa usimamizi wa ukaguzi, machapisho, na ufahamu.
Nini cha kufanya:

1. Create a Google Cloud project, enable Business Profile API. 2. Create OAuth 2.0 credentials (Web application). 3. Set redirect URI: copy it from the connector's own settings page. Google and Microsoft connectors share one slug-less callback: https://your-domain.com/connectors.php?oauth=callback Everything else uses https://your-domain.com/connectors.php?slug=<slug>&oauth=callback OAuth redirect URIs must match EXACTLY, and a URI missing oauth=callback is read as a webhook and answered with "Missing slug or token". 4. In OpsIQ, enter Client ID and Client Secret. 5. Click Authorize, sign in, grant access. 6. Select your business location. 7. Verify: reviews, posts, and insights should appear.

Viunganishi

Kupanua CRM & tovuti ya akili

OpsIQ subsystems ni wazi kwa ajili ya ugani. kontakt inaweza kuziba uwezo mpya katika CRM au Site Intelligence na hakuna mabadiliko ya OpsIQ Msingi, kupitia Usajili wa Uwezo wa Jukwaa (\)OpsIQ Kutangaza uwezo, kutekeleza njia yake ndogo kuweka, meli kontakt,OpsIQ Kuingiza ndani na kuweka katika UI, Wateja 360 Muda wa kufunga na ufungaji wa haraka.

Kupanua CRM na SI
Uwezo wa jukwaaMunganisho kwenye mabasi ya uwezo wa kulisha kushoto (CRM, Ujasusi wa Tovuti, Analytics) iliyogunduliwa na Uwezo wa Usajili.Uwezo wa jukwaaNafasi ya KaziLink yako yaKubainisha uwezoCRMkalenda · utajiri · esign · malipo · sanduku la baruaTovuti ya IntelligenceOrodha ya maeneo · rank_dataUchambuziMtandao wa Internet_analytics · Ripoti & ingestCapabilityRegistryInafungua na kufunga waya wa UI + Time1DECLAREUwezo wa kufanya kazi, sio msingi wa mauzo2PLUG INCRM · SI · Usafiri wa treni3AUTO-WIREDUI, wakati wa muda, haraka
Munganisho anatangaza uwezo (calendar, utajiri, data ya cheo, analytics ...) na OpsIQ auto-wires yao katika CRM na Usalama wa Tovuti, hakuna mabadiliko ya msingi.

Kuthibitisha uwezo

Maelezo ya kina (settings.json)

Kuongeza A <domain>_capabilities array, bora kwa ajili ya hakuna-code / soko la viunganisho. Domains: crm, site_intelligence.

Kwa kutumia msimbo (connector. php)

Kutekeleza crmCapabilities() / siCapabilities() Rejea barua ya kujiuzulu.

Kutangaza mtoa kalenda ya CRM (settings.json)

Kwa mfano:
Lengo: kufanya kontakt ya kalenda kuonekana katika jopo la mkutano wa ratiba ya CRM.
Nini cha kufanya:

"crm_capabilities": [ { "type": "calendar", "label": "Calendar (Acme)", "actions": ["createEvent","listEvents","freeBusy"], "requires_auth": true } ]

Kutangaza mtoa huduma wa akili (settings.json)

Kwa mfano:
Lengo: kulisha data ya ndani katika Intelligence ya Site.
Nini cha kufanya:

"site_intelligence_capabilities": [ { "type": "local_listing", "actions": ["listLocations","listReviews","getInsights"], "requires_auth": true } ]

Uwezo wa usafiri na njia zao za usafiri

crm / kalenda ya

createEvent($settings,$params) →{success,event_id,html_link,meet_link} listEvents; freeBusy• Kuongozwa naOpsIQ\CRM Kwa mfano, CalendarBridge.

crm / utajiri wa

enrich($settings,$params) →{Uwezo wa kufanya kazi}OpsIQ\CRM \EnrichmentBridge (pia anaendesha moja kwa moja kwenye kampuni kuunda wakati mtoa huduma ameunganishwa).

« C / Esign ya

sendForSignature($settings,$params) → {kufanikiwa, envelope_id, ishara url}. Driven na \OpsIQ\CRM\EsignBridge.

Tovuti ya ndani / local_listing

listLocations, listReviews, getInsights- Kuhamisha kwa kutumia Google Business Profile kontakt.

Tovuti ya Intelligence / cheo_data

keywordRanks($settings,$params) → {ufanikio, nafasi}. Driven na \OpsIQ\SiteIntelligence\RankDataBridge. meli: SerpApi kiunganishi.

Uchambuzi wa wavuti / uchambuzi

report($settings,$params) (Standard / Export) ingest($settings,$events) (Aina ya Kuongoza)OpsIQ\ Analytics \WebAnalyticsBridge. meli: Google Analytics (GA4) kontakt ya data API kwa ripoti, Itifaki ya Upimaji wa kuagiza. Analytics ni wazi kwa viunganisho kama CRM + Site Intelligence (domain) analytics / analytics_capabilities).

Malipo ya malipo / utoaji

listPayments, customerPayments, createPaymentLinkKuendeshwa na \OpsIQ\ Malipo ya malipo. Onyesha malipo ya mteja kwenye ratiba ya CRM + tuma kiungo cha malipo kwenye mpango. Ships: Stripe Payments kiunganishi. Domain payments / payments_capabilities.

Barua pepe ya barua pepe / e-mail_sync

listMessages + sendMessage• Kuongozwa na OpsIQ\MailboxBridge. barua pepe za mteja kwenye Wateja 360 Muda wa + tuma barua pepe kutoka kwa mpango. Ships: Gmail + Outlook / Microsoft 365 Kikoa cha Domain mailbox / mailbox_capabilities.

Kushiriki kwa pamoja OAuth Programu ya 1 + moja kwa moja

Waunganishaji wote wa Google wanashiriki programu moja kupitia \OpsIQ\OAuth GoogleApp.com yaweka google_oauth_client_id/_secret Mara moja na kalenda, Analytics, Wasifu wa Biashara + Gmail kazi zote (kwa-uunganishaji "(kinyume)" mashamba ni overrides). Pia kushiriki moja redirect URI, <site>/connectors.php?oauth=callback (hakuna kiungo cha kuunganisha), kwa sababu Google haitoi maelezo yoyote. API Kuongeza URIs kwa programu; OpsIQ Kurejesha kontakt kutoka kwa saini OAuth state Tafadhali sajili moja ya URI mara moja na kila kontakt ya Google (inapopatikana + baadaye) inaruhusu bila usanidi wa Console zaidi. SharedGoogleApp::resolve(...)ya redirect_uri Kutoka kwa yako oauthParams(); kamwe ngumu-code redirect. viunganisho vya Microsoft hufanya vivyo hivyo kupitia \OpsIQ\OAuth MicrosoftApp (kwa ajili ya Microsoft)microsoft_oauth_*).

Vifaa vya Kuagiza ni Uwezo wa Kushughulikia

Kwa kuwa Uagizaji wa bidhaa (Elekezwa kutoka Historia) na Wateja wa vifungo kuonyesha tu kwa ajili ya viunganisho kwamba kweli kutekeleza yao, wanaona kwa kutafakari, hivyo hakuna bendera kutangaza. backfill() au backfillChunk() Kuingiza bidhaa kutoka kwa muuzaji; override listCustomers() (kurudisha {Email, kwanza_name, ...} kurasa) kupata wateja wa Import. urithi AbstractConnector Hakuna-op na kifungo anakaa siri, hivyo UI kamwe inatoa uingizaji kontakt haiwezi kufanya.

Usafiri wa mabasi

Wakala wa CRM inapendekeza na mikutano ya vitabu mbali ishara za mpango (\OpsIQ\CRM\MeetingProposer → CalendarBridge), na akaunti mpya za auto-kuongeza, "AI inafanya kazi kitanzi cha CRM", kutekelezwa katika mabasi ya kiunganishi.

Tiketi ya Mteja (Teknolojia)fetchTicket())

2 - Hakuna mabadiliko ya msingi

Wakati mgeni anataja nambari ya tiketi katika mazungumzo ya mteja ("hali ya T-000123?"), OpsIQ inatatua kwa tiers mbili. Kuwa 1 Kusoma kwa pamoja OpsIQ Simu ya mkononi, kila simu inayounganishwa na inbound_ticket Inaangalia tiketi zake huko, hivyo tiketi za synced zinafanya kazi tu kwa viunganisho vyote na msimbo wa kuunganishwa. Kuwa 2 Ni kurudi kwa moja kwa tiketi za zamani ambazo hazijawahi kuonekana: wito wa msingi fetchTicket() kwa kila mtumiaji ambaye ana uwezo wa kutumia. duck-typed (Elekezwa kutoka Kwa method_exists()Kama vile contextProviders()/audienceCatalog()(i) Kwa hiyo, Kamati ConnectorInterface Haipatiwi na viunganisho ambavyo hazihitaji ( Vyanzo vya barua pepe / mazungumzo ambayo huunda tiketi za asili) tu kufuta.

⚠️
Umiliki ni wajibu na wako wa kutekeleza. fetchTicket() kupata utambulisho wa mgeni aliyealikwa katika $ctx (client_id + client_email, utambulisho huo kuthibitishwa mteja chat AI anatumia). kutatua wateja jukwaa kutoka utambulisho huo na swala tu kwamba tiketi ya mteja, kisha re-check umiliki juu ya rekodi ya kina. null kwenye kosa lolote, makosa, au hitilafu, kamwe data ya mteja mwingine. null Kwa bahati mbaya, "hawezi kupata tiketi hiyo."
kontakt. php, mkataba wa kuchotaTicket (mapendekezo: viunganisho /whmcs na viunganisho/zendesk)
<?php
// connector.php — OPTIONAL universal client-chat ticket resolver (Tier 2).
// Only add it if your platform keeps its OWN ticket store that may hold tickets
// not yet mirrored into OpsIQ. Return the normalised array below, or null.
//
// $ref      = ['mode' => 'id'|'tid', 'value' => string]  (from extract_ticket_ref)
// $ctx      = ['client_id' => int, 'client_email' => string]  (VERIFIED visitor)
// $settings = your connector settings
public function fetchTicket(array $ref, array $ctx, array $settings): ?array
{
    try {
        $email = trim((string)($ctx['client_email'] ?? ''));
        $cid   = (int)($ctx['client_id'] ?? 0);
        if ($cid <= 0 && $email === '') return null;            // no verified identity → refuse

        // 1) Resolve THIS visitor on your platform (by verified email/id).
        // 2) List ONLY their tickets and match $ref against the ticket number/id.
        // 3) Re-confirm ownership on the detail record before returning.
        //    On any miss/mismatch/error → return null (never leak).

        return [
            'tid'        => 'T-000123',     // the customer-facing reference
            'id'         => 123,            // your internal id
            'status'     => 'open',
            'subject'    => '…',
            'department' => 'Billing',     // '' if your platform has none
            'priority'   => 'high',
            'opened_at'  => '2026-06-29 10:00:00',
            'last_reply' => '2026-06-29 12:00:00',
            'message'    => 'opening message text',
            'replies'    => [               // oldest → newest; opening message may be first
                ['who' => 'You',   'date' => '…', 'message' => '…'],
                ['who' => 'Staff', 'date' => '…', 'message' => '…'],
            ],
        ];
    } catch (\Throwable $e) {
        error_log('[yourslug][fetchTicket] ' . $e->getMessage());
        return null;                                             // graceful degrade
    }
}

Jinsi ya kutumia jukwaa hili

Utambuzi wa uvumbuzi

CapabilityRegistry::providers($domain,$type) Orodha ya watoa huduma na hali iliyowekwa / iliyowezeshwa / tayari (mfumo wa faili-msingi; DB tu kwa bendera iliyowezeshwa).

Uchaguzi wa kuchagua

CapabilityRegistry::active($domain,$type) Inarudi mtoa huduma wa kwanza aliye tayari na kontakt yake iliyopakiwa na mipangilio. Bridges huita hii badala ya slugs ngumu.

Kuthibitisha-ku-install

Ambapo kipengele kinahitaji uwezo ambao haujaunganishwa bado, UI inaonyesha kuunganisha moja-click Connect / Install haraka, kamwe udhibiti wa kifo.

Mwongozo kamili

See ya connectors/PLATFORM_CONNECTORS.md (CRM + tovuti ya akili) connectors/CRM_CONNECTORS.md kwenye mfuko huo.

Viunganishi

Wateja binafsi huduma ya kuangalia & refunds (kujenga kontakt yako kwa ajili ya wateja chat)

Wateja waliojiandikisha wanaweza kuuliza mteja kuzungumza AI kuhusu akaunti yao ya OWN ("mtihani wangu", "amri zangu", 'zinazounga mkono jibu la tiketi yangu') na, ikiwa biashara inawezesha, ombi marejesho. Yote ni powered kwa tangazo la kontakt yako: hakuna OpsIQ Mabadiliko ya msingi, hakuna jukwaa ngumu. AI inaita kuangalia kwako kama zana za asili (haiwezi kuunda moja), utambulisho umefungiwa upande wa seva kwa mteja aliyethibitishwa, na matokeo hukatwa moja kwa moja kwa AI.

Kuthibitisha Wateja wa Kuangalia

Katika yako actions.jsonHatua ya kusoma tu inakuwa wito kwa wateja na wote watatu: "scope":"client", "requires_confirmation":false, "is_destructive":falseMatumizi ya "scope":"both" Wakati kuangalia sawa lazima pia ijulikane na timu yako katika Admin AI. msamiati kamili ni admin, client, both Na kwa kuwa system (system Hafikii AI - API na njia za wavuti tu). Kitu kingine chochote kinakataliwa kabisa: uthibitisho wa mfuko unashindwa na hatua haifungi. writing Msaada - Msaidizi wa Kuandika Anatumiwa admin Hatua ya kuchukua.

Kanuni ya utambulisho (mandatory)

Jina parameter yako ya utambulisho kutoka seti standard. imefungwa kwa ID kuthibitishwa namba: client_id, clientid, customer_id, user_id, userid, account_idKushikilia kitambulisho hicho kama kamba: client_identifier, customer_identifier, account_identifierKuondolewa kwa barua pepe iliyohakikishiwa: email, client_email, customer_email, user_email. OpsIQ Inafunga na auto-fills kutoka kwa mteja aliyethibitishwa na jukwaa; AI kamwe huona au huchagua utambulisho. Jina lisilo la kawaida linashindwa kufungwa (limefungwa, haijawahi kufichuliwa).

Nini cha kufanya admin

Chochote kisicho na upeo wa utambulisho huo: ku-by-bare-id (order_id/ticket_id pekee), orodha za duka, utafutaji wa maandishi ya bure. Wale ni uvujaji wa wateja kwenye jukwaa lolote. "scope":"admin".

Kuumba matokeo (kubeba funguo)

Matokeo ya kuangalia ni miundo trimmed kabla ya kufikia AI: funguo siri-umbo ni imeshuka, masharti mrefu na orodha ni capped, mashamba tupu ni kupogolewa, na ramani gorofa pana kuliko cap muhimu anaendelea yake Majibu ya Maswali ya KwanzaFedha (credit, balance, amount, total, due, paidUtambulisho (email, *name, phone, companyNchi ya (status, active, expir*, renew*), tarehe, mpango / bidhaa/domain/service/subscription/order/invoice/ticket fields, sarafu, hesabu na stats/summary/totals, kabla ya viti vyovyote vilivyosalia kwenda kwenye funguo zingine za thamani ndogo zaidi. Mwongozo wa vitendo: jina la mashamba yako na msamiati huo wa kawaida na kurudi mashamba ambayo yanajibu swali la mteja badala ya dump ya jukwaa la 100-key; shamba lililoitwa nje ya msamiati hushindana kwa viti vya kushoto na linaweza kupunguzwa kutoka kwa mzigo mkubwa sana wa malipo.

Refunds · Nini kiambatanisho chako kinatoa

Shughuli mbili za ghafi, zisizo na sera: (1) usomaji wa malipo unaoweza kuchujwa kwa utambulisho na kumbukumbu ya shughuli (yako API lazima NA filters), kwa mfano. whmcs_get_transactions; (2(i) Kurudisha hatua za utekelezaji (scope:"admin", requires_confirmation:true, is_destructive:trueHakuna haja ya kuwa na wateja, kwa mfano. whmcs_refund_orderBiashara inachukua funguo zote katika Mipangilio → Mteja Chat; OpsIQ inabadilisha tena seva ya malipo, inatumika sanduku la sera ya biashara (kipengele cha kiwango, dirisha la umri, kikomo cha kila mwezi), masuala ndani ya sanduku, na faili tiketi ya ukaguzi kwa kila kitu kingine.

Hakuna wajenzi wa code

Mhariri wa hatua ya Connector ina udhibiti sawa: kuweka "Nani anaweza kuitumia" kwa wateja waliojiandikisha, kuacha wote kuandika hundi mbali, na kutumia jina la kawaida la kitambulisho.

Utekelezaji wa Kumbukumbu

"Huduma ya Wateja" katika connectors/whmcs/actions.json, woocommerce/actions.json, oscommerce/actions.jsonMkataba kamili katika connectors/README.md §8.1–8.2 Aidha, na ConnectorInterface::registerActions().

Viunganishi

Watazamaji wa wageni - kuruhusu wageni kufuatilia uhifadhi, usafirishaji au utaratibu bila kusaini (guest_lookup)

Hoteli, couriers na majukwaa mengi ya biashara hutumikia wateja ambao wana kumbukumbu lakini hakuna kuingia: mgeni aliye na uthibitisho wa uhifadhi, mpokeaji mwenye nambari ya kufuatilia. guest_lookup Uwezo (Mkataba wa Washirika, mode: yanayotokana) inakuwezesha kontakt yako kutumikia wageni hao katika mazungumzo ya mteja AI - hakunaOpsIQMabadiliko ya msingi, hakuna jukwaa ngumu. kontakt yako inasema nini inathibitisha haki na mashamba ya WHICH yanaonekana;OpsIQKukataa kwa ajili ya dhambi, kumkufuru Roho Mtakatifu na kukataliwa.

Mfumo wa uaminifu

Ushahidi + ushahidi, kamwe utambulisho

Mgeni anatoa kumbukumbu ya rekodi (ikilinganishwa na regex unayotangaza) pamoja na ushahidi unaochagua - kwa kawaida barua pepe kwenye rekodi. Hatua yako ya kuchota inarudisha rekodi SERVER-SIDE kwa kumbukumbu;OpsIQMtoa huduma aliyezalishwa analinganisha ushahidi dhidi ya rekodi ya FETCHED. pembejeo ya mgeni haijawahi kuaminiwa, na hakuna utambulisho uliothibitishwa umeundwa: mechi hiyo inampa mgeni kwenye uwanja wa kumbukumbu moja, hakuna kitu kingine.

Kukataa (hakuna neno la kuunganisha)

Sio-msingi na ushahidi-mismatch huzalisha jibu moja sawa. AI ni wazi maelekezo kamwe kuthibitisha kama kumbukumbu ipo na kamwe invent maelezo ya rekodi. majaribio ni kiwango cha ukomo kwa mazungumzo + IP kwa msingi kabla ya kontakt yako ni milele ushauri.

Double-in, chaguo zote mbili za default

Hakuna chochote kinachohudumia wageni hadi biashara inapowezesha swichi za BOTH: udhibiti wa eneo la kazi katika Mipangilio→Usalama wa usalama→"Guest rekodi lookups katika mteja chat" (permission-gated NA daima password-confirmed, hata wakati hiari hatua-up ni mbali), na kontakt yako mwenyewe guest_lookup_enabled Mipangilio ya kuingiza. Kuweka au kuwezesha kontakt peke yake kamwe kufungua uso wa mgeni.

Mgeni rasmi wa kikao hicho

Waandishi wa habari wakiwa kwenye uzinduzi huo guest Mazingira ya asili - tofauti na admin Na kwa kuwa customerWatoaji wa mazingira ya zamani hawashauriwi kamwe kwa wageni wasiojulikana, na mtoa huduma wa mgeni hashauriwa kamwe kwa wale waliosainiwa. ctx inapata hubeba ujumbe wa mazungumzo, kitambulisho cha thread na barua pepe ya mgeni iliyothibitishwa (bila kuthibitishwa) kabla ya kuzungumza kama mgombea wa uthibitisho - hakuna uwanja wa utambulisho.

Kufafanua hayo katika kikao cha Bunge

1
Kufafanua hatua ya kuchukua

Katika hatua za hatua, ongeza hatua ya kusoma tu ambayo inarudi rekodi moja kwa kumbukumbu yake (kwa mfano. GET /bookings/{booking_number}) na ramani ya mashamba yake ya majibu na aliases: hali, kuwasili, kuondoka, chumba_type, mteja_email ...

2
^ Tnn., “machungu ya macho.”

Katika hatua ya kwanza, uwezo wa guest_lookupJopo la kujitolea linaonekana: chagua hatua ya kuchota, jina la parameter ya kumbukumbu, kutoa muundo wa kumbukumbu (mwili wa regex kama vile \bBK-[0-9]{4,10}\b(a) jina la rekodi ("kitabu"), na kuchukua ushahidi - barua pepe kwenye kumbukumbu (kurudishwa) au hakuna (kumbukumbu ya pekee, kwa ufuatiliaji wa hali tu).

3
Kuruhusu maeneo ya wazi

Tick hasa mashamba mgeni anaweza kuona. Kila kitu kingine ni DROPPED - kamwe redacted. Mjenzi anakataa mashamba PII-umbo (Email, simu, anwani, malipo ...) katika ruhusu, na toleo la kutolewa suti ya kibali re-checks utawala huo kabla ya kuchapisha, hivyo spec iliyopangwa mkono haiwezi sneak moja katika. Kumbuka kwamba ufungaji wa wakati uthibitisho inashughulikia wazi na saini tu, hivyo kuendesha suti ya kufanana mwenyewe kabla ya meli. uwanja wa ushahidi yenyewe unaweza kuonyeshwa.

4
Kuchapisha na kuwezesha

Muumba wa Bidhaa GuestLookupProvider.php - utekelezaji ngumu wa canonical, sawa kwa kila mfuko unaozalishwa - na inaongeza guest_lookup_enabled toggle kwa mazingira ya kontakt yako. biashara silaha swichi mbili na chat AI huanza kutoa lookup wakati mgeni anauliza kuhusu aina yako rekodi.

Sheria ya mikataba

Maeneo ya Kuingiliana tu

Fikiria "nini itakuwa courier kuchapisha kwenye ukurasa wa kufuatilia umma": hadhi, tarehe, chumba au huduma jamii, makosa. Majina, maelezo ya mawasiliano, anwani za mitaani, data ya malipo na maelezo ya maandishi ya bure hawana nafasi katika mazungumzo bila kujulikana - Mjenzi na kukubaliana wote wanakataa yao.

Majibu ya AI ni kutoka kwa block

Mtoa kuzalisha kumaliza pato lake na maelekezo ya kujibu tu kutoka mashamba waliotajwa na kutoa tiketi kwa kitu kingine chochote. undani si katika orodha ya ruhusu ni "si inapatikana katika chat" - kwa kubuni.

Ufuatiliaji wa kazi unaendelea

Mtoa huduma anaelekeza kumbukumbu kutoka kwa ujumbe wa hivi karibuni wa mgeni katika mazungumzo hayo, hivyo "na wakati ni kuangalia nje?" inafanya kazi bila ya kurudia kumbukumbu. kumbukumbu iliyolingana na barua pepe ya ushahidi zinakumbukwa kwenye thread ya gumzo kama CANDIDATES, hivyo ufuatiliaji hauulizi tena. Wao ni wagombea tu: kila zamu bado inashikilia rekodi ya seva-pamoja na upya uthibitisho kabla ya kutoa uwanja mmoja.

Vifaa vya mikono vilivyoandikwa

Soko la bidhaa linaweza kuwa na faida zake GuestLookupProvider.php implementing ContextProviderInterface Pamoja na kuwa pamoja surfaces(): ['guest']Fuata mkataba wa template uliozalishwa hasa - kuchota kwa kumbukumbu, upande wa seva ya mechi ya ushahidi, sare kukataa, pato la pekee-na kutangaza guest_lookup in capabilities. Marekebisho yanathibitisha uso wa mgeni na scans orodha ya ruhusa kwa PII.

💡
Watazamaji wa wageni ni mazingira ya kusoma tu kwa AI. Hawana kutekeleza vitendo, kamwe kuunda utambulisho, na kamwe kufungua njia ya huduma ya mteja hapo juu - kwamba njia bado inahitaji jukwaa-kuthibitishwa saini wateja.
Viunganishi

Matangazo ya matangazo (promo_audience)

Hebu Promotion Studio lengo kampeni na mteja LIVE na bili hali kutoka jukwaa yako: "ina ankara unpaid", "ili inasubiri", 'subscription kufutwa'. kontakt yoyote (kabla ya imewekwa, soko, au moja kujenga mwenyewe) anajiunga kwa kutekeleza mbinu mbili ndogo. No OpsIQ mabadiliko ya msingi, hakuna jukwaa hardcoding: kontaktoni yako inaonekana kama jukwaa katika Targeting tab na kuacha yake mwenyewe ya ukweli, na viunganisho kadhaa inaweza kuwezeshwa upande wa studio.

Kukuza watazamaji
Watangazaji wa promosheni yaUtambulisho uliothibitishwa ulipitishwa kwa watazamaji wa kontakt wito kuzalisha ukweli ambao unaendesha utawala unaolenga, na noti iliyofungwa.Watangazaji wa promosheni yaNafasi ya KaziNdani yaUtambulisho wa kuthibitishwaIdadi ya watazamaji()Link yako yaUkweli waunpaid_invoices = 2Kanuni yaMalipo yasiyo ya lazima | 1Maonyesho ya KampeniKushindwa kufungwa: mteja asiyejulikana au kosa lolote → kampeni inakaa siri.1TWO METHODSBendera ya Volta ya Juu2LIVE STATEKulipwa, Kusubiri, Kulipwa3FAIL-SAFEKamwe usiruhusu mtu aonekane vibaya
Munganisho wako anajibu ukweli wa bili ya kuishi kwa mgeni aliyeingia; malengo ya studio juu yao, na inashindwa kufungwa hivyo kutoa kulipa kamwe hufikia mtu mbaya.

Jinsi ya kufanya kazi

1
Kuwasilisha taarifa yako

Tumia watazamajiCatalog () kwenye darasa lako la kontakt. Inarudi lebo na orodha ya funguo ambazo jukwaa lako linaweza kujibu. Kila ufunguo inaonyesha katika kushuka kwa studio chini ya jina la jukwaa lako.

2
Majibu kwa mteja mmoja

Implement audienceFlags(array $identity). OpsIQ calls it at delivery time with the VERIFIED logged-in visitor identity (from the widget identity token, the same identity the client chat AI uses). Return a flat key => value map.

3
Kufanya hivyo

Wezesha kiunganishi.Kifungu cha Kukuza Studio Targeting kinakua sehemu ya "Kulipa na kulipa" orodha ya jukwaa lako; admins hujenga sheria kama "unpaid_invoices > 1“Kila kitu kinabadilika na kuwa tofauti kama vile {unpaid_invoices}.

« php, mkataba kamili wa promo_audience
public function audienceCatalog(): array
{
    return ['label' => 'My Billing Platform', 'keys' => [
        ['key' => 'unpaid_invoices', 'label' => 'Unpaid invoices (count)', 'type' => 'number'],
        ['key' => 'pending_orders',  'label' => 'Pending orders (count)',  'type' => 'number'],
        ['key' => 'client_status',   'label' => 'Client status',           'type' => 'text'],
    ]];
}

public function audienceFlags(array $identity): array
{
    // $identity = verified token payload: ['email' => ..., 'id' => ..., 'name' => ...]
    $email = strtolower(trim((string)($identity['email'] ?? '')));
    if ($email === '') return [];
    $client = $this->api('GetClient', ['email' => $email]); // your platform call
    if (!$client) return []; // unknown client -> return [] (fails CLOSED)
    return [
        'unpaid_invoices' => (int)$client['unpaid_count'],
        'pending_orders'  => (int)$client['pending_orders'],
        'client_status'   => (string)$client['status'],
    ];
}

Sheria ya mikataba

Kueleza uwezo

Ongeza 'promo_audience' Kwa ajili ya interface yako capabilities() Panga hivyo jukwaa na orodha ya soko kama watazamaji-uwezo (ugunduzi pia hufanya kazi kutoka kwa uwepo wa njia, lakini kutangaza ni ishara safi). connectors/whmcs Uunganisho ni utekelezaji kamili wa kumbukumbu.

Jina la msingi

Chini nyoka_case, 2-60 chars, vinavyolingana na ^[a-z0-9_] + $. Aina: nambari, maandishi, bool. funguo zisizotangazwa zilizorejeshwa na watazamaji Flags () bado zinaweza kutumika katika sheria, lakini kutangaza kila kitu unachounga mkono ili admins iweze kuona.

Utambulisho wa kuthibitishwa

The $identity array comes from the signed widget identity token issued by the customer site at login, never from client-supplied fields. If your platform cannot resolve the identity, return an empty array.

Kufungwa · Mara zote

Kwa kosa lolote (API chini, mteja ambaye hakupatikana, muda) kurudi [] utawala ambao ukweli wake unakosekana hufanya kampeni isionyeshe. popup iliyopangwa haipaswi kumfikia mtu mbaya; OpsIQ inatekeleza hili katika mchezaji wa sheria pia.

Utendaji wa utendaji

audienceFlags () huitwa mara moja kwa kila kontakt kwa mtazamo wa ukurasa, na tu wakati kampeni iliyochapishwa kweli inatumia sheria za jukwaa lako. wageni wasiojulikana wanakugharimu wito sifuri. 1-2 API maombi ya; OpsIQ Ubinafsi ndani ya maombi.

Wafanyakazi wa kujitolea kwa bure

Wasimamizi huchanganya funguo zako na =, !=, >,>=, <=,<==, ina, imewekwa, ni tupu, wewe tu ugavi maadili.

Maelezo ya kibinafsi

Kila ukweli mara mbili kama variable katika nakala ya kampeni: {unpaid_invoices}, {client_status} Pamoja na ujenzi wa {first_name} Aidha, na {client_email}· Malipo ya ada hulipwa kabla ya kulipa.

Hakuna-code ya soko la kontakt

Ukweli wa moja kwa moja

Declarative (JSON-tu) masoko ya soko wanatangaza promo_audience kwa FREE: ikiwa kontakt yako inatangaza wateja / watumiaji, ankara, maagizo au rasilimali za usajili, OpsIQ hupata mteja_status, bila malipo_invoices, kiasi_due, inasubiri_orders, maandishi na usajili_stus kutoka kwa vitendo vyako vya utafutaji vilivyopo. Hakuna msimbo wowote.

Orodha ya desturi (settings.json)

Ongeza kitu cha watazamaji_capability · {"label": " Jukwaa langu", "keys": ["key": 'open_carts', "labels"; "magari ya wazi", aina "aina":") ), kudhibiti hasa ambayo ukweli (na maandiko) yanaonekana katika studio.

Kuthibitisha mtoa huduma wako

1
Kuwezesha Interface

Waunganishaji > kontakt yako > Kuwawezesha. Kisha kufungua tabo ya kampeni yoyote ya Targeting. jukwaa lako lazima lionekana chini ya "Client & bili (waunganisho)".

2
Kujenga utawala

Ongeza: jukwaa yako · muhimu · >= · 1 na kuweka "Logged-katika wateja tu". Kuokoa na kuchapisha.

3
Kuthibitisha pande zote mbili

Ingia kwenye jukwaa lako kama mteja ambaye analingana na utawala (popup lazima aonyeshe) na kama mtu ambaye hana (pop up lazima kukaa siri). wageni wa nje wanaovutiwa kamwe hawalingani na sheria zilizowekwa.

Piga kampeni kutoka kwa msimbo wako mwenyewe (kuchochea mteja)

Kwa nini kwa sababu

Zaidi ya kuchochea kujengwa katika (kuchelewa, kitabu, exit-intent, wavivu, click, kurasa-viewed, chat / tiketi shughuli), unaweza moto kampeni kutoka popote kwenye tovuti yako au kontakt mbele-mwisho, baada ya mafanikio checkout hatua, wakati gari ni kutelekezwa, wakati SPA mabadiliko njia yako, nk.

Jinsi ya jinsi gani

kuanzisha kampeni ya kutaka Desturi ya Jina la tukio (kwa mfano, checkout_failedKisha, piga simu ya kimataifa kutoka kwenye ukurasa wako:

Tovuti yako / kontakt mbele ya JS
// Any campaign whose Custom trigger event matches will be evaluated
// (it still respects targeting, frequency caps and audience rules).
window.OpsIQPromo && window.OpsIQPromo.fire('checkout_failed');
💡
Firing tukio kamwe bypasses kulenga au frequency. Ni tu releases "wakati" kampeni bado ina kupita kila utawala (geo, watazamaji, ridhaa, kofia) kabla ya inaonyesha.
Mwongozo kamili wa jinsi ya kutumia (kubuni, vitalu, analytics, A / B, kuchapisha) unaishi katika Kituo cha Msaada wa Programu chini ya Kushiriki katika→Mafunzo ya StudioUwezo hapa ni aligundua moja kwa moja kutoka yoyote ENABLED kontakt katika viunganisho / au soko_connectors/. Hakuna kitu cha kujiandikisha. meli mbinu mbili, na studio inafanya wengine.
Viunganishi

Uwezo wa kontakt ya utafiti (Contract 2.2)

Kwa kuwa survey Uwezo unawezesha usambazaji wowote wa jukwaa kuthibitishwa kwa watumiaji wanaobadilisha utambulisho, ukweli wa watazamaji, vigezo salama na wagombea wa mpokeaji kwenye Studio ya Utafiti. promo_audience na haitoi umiliki wa kontakt wa tafiti, majibu, analytics au utoaji wa barua pepe.

💡
Utekelezaji wa hali. Kuandika ni kamili na inayoweza kutumika leo: Mkataba wa Uunganishaji 2.2, SurveyConnectorInterface-Kujenga jengo la kisasa, linalojengwa SurveyProvider.phppakiti metadata na usawa kutengwa meli zote. Matumizi bado wired: SurveyConnectorRegistry Inatekelezwa na kupimwa, lakini hakuna wakati wa utafiti wito bado, hivyo afya ya mtoa huduma haipatikani katika admin UI na mfuko wa kontakt iliyochapishwa inasema uwezo. Kujiandikisha-kutokana na Utoaji wa Njia ya Utambulisho wa Utafiti, kulenga na ujumuishaji wa kutofautiana, CRM Outreach materialization na ramani za kwanza za mtoa huduma zinazosafirishwa zinabaki awamu tofauti. Kujenga dhidi ya mkataba huu sasa; kutarajia kukimbia kuanza kuteketeza katika kutolewa baadaye.

Wajibu wa mtoa huduma

Orodha ya maoni na ukweli

Kutangazwa kwa ukweli wa kisheria na kutatua maadili tu kwa somo la kuthibitishwa seva, workspace-bound. ukweli wa kawaida ni pamoja na order_count, last_order_status, cancelled_order_count, customer_created_at, active_subscription_count, past_due_invoice_count Aidha, na open_ticket_count.

Orodha ya tofauti na viwango

Kutangaza wateja, akaunti, utaratibu, usajili na msaada vigezo na aina, unyeti na kuruhusiwa mazingira. nakala ya utafiti inahitaji kuanguka na matokeo-kifaa kukimbia.

Haki miliki ya picha Recipied pat

Chaguo la kuhesabu wagombea kwa CRM Outreach na ID imara za nje, kurasa zilizofungwa, mishale ya kuamua na metadata inayohusiana na idhini. Utafiti hufunga watazamaji waliochaguliwa kabla ya kutuma yoyote.

Utambulisho wa utambulisho

Kukubali utambulisho tu kutoka kwa Gateway ya Utambulisho wa Utafiti baada ya saini ya ishara, expiry, kusudi, kontakt na uthibitisho wa nafasi ya kazi. barua pepe iliyosambazwa na kivinjari, ID, vitambulisho au ukweli unaodaiwa sio mamlaka kamwe.

Afya ya Runtime

SurveyConnectorRegistry imeundwa kutoa taarifa za watoaji wanaoshirikiana, waliozuiwa na wasiopatikana bila kuweka mipangilio, njia, utambulisho wa asili au ujumbe wa ubaguzi, na mtoa huduma aliyezuiliwa hawezi kamwe kutakiwa. Uso wa ripoti bado haujafunuliwa katika admin UI: leo mtoaji aliyezuiwa ni tu inert.

Kanuni zilizofungwa

funguo zisizotangazwa, aina mbaya, maadili ya juu, chini ya mismatches, kontakt timeouts na utambulisho usiojulikana ni kukataliwa. utawala wa kulenga ambao unahitaji ukweli usiopatikana haulingani. kurasa za Recipient zimefungwa na ukaguzi. maadili nyeti kamwe kuonekana katika preview umma au kumbukumbu.

Ujenzi wa lango la

Mkataba wa 2.2 meli uwezo wa Usajili kuingia, interface, jopo la ramani ya utafiti, yanayotokana SurveyProvider.php, toleo la uwezo, kumbukumbu ya README / watengenezaji na marekebisho ya usawa. Biashara, Helpdesk, Daraja la SaaS na maelezo ya PHP ya ndani ni pamoja na; Standard API waunganisho huchagua. lango la tuli linakataa mtoa huduma wa Utafiti anayeita jina la Kukuza, meza au uwezo.

💡
Nakala kutoka Kukuza ni kuagiza tu: Mjenzi anaweza kutafsiri ramani za kukuza zinazofaa mara moja, isipokuwa nakala kamili ya utafiti na uthibitisho wa rekodi. Kuteua au kubadilisha ramani ya uendelezaji lazima isibadilishe tabia ya Utafiti.
Viunganishi

Uwezo wa kujibu maoni (Contract 2.2)

Kwa kuwa reply_feedback Uwezo wa kuona ratings ya jukwaa mwenyewe kwa mara nyingine katika OpsIQ- Nyota ambayo mteja anatoa jibu la wafanyakazi ndani ya WHMCS wa Wilaya ya Mkuranga katika majibu yake kwa OpsIQ admin thread, na chip hiyo, wakala mikopo, maoni ukurasa kuingia na Team & Performance computation kama rating aliyopewa juu ya OpsIQ Hifadhi moja, chip moja, bomba moja; kontakt tu hutafsiri.

Njia moja ya kuandika

Kuna njia mbili za kuingia na ukweli mmoja. OpsIQ tiketi za bandari zinaandika asili. Tiketi za Jukwaa hutiririka kupitia kiunganishi, na ardhi ya msingi kila tukio kupitia ReplyFeedback::recordMirrored(): safu sawa, utawala wa wafanyakazi tu, moja-rating-per-reply hivi karibuni-kushinda semantics, stamp workspace na Sauti ya Wateja indexing portal kuandika matumizi.

Kujiandikisha (barua pepe nne, kisha ujisajili)

1
connector_contract.json

Ongeza uwezo. reply_feedback kuingia: toleo la 1.0, ReplyFeedbackConnectorInterface, mbinu za kujibuFeedBackCatalog na pullReplyFeed back, inamaanisha inbound_ticket.

2
settings.json

Ongeza jibu_feedback kwenye orodha ya uwezo. Hii ndio ugunduzi wa kontakt unasoma.

3
spec.json

Kutangaza jibu_feedback. modes (poll na / au webhook) na kiwango cha rating ya jukwaa. Hii ndio lango la usawa linasoma.

4
Mafunzo ya Runtime

Tumia interface, orodha ya jibu_feedback katika uwezo (), kisha usaini tena mfuko.

Wajibu wa mtoa huduma

Orodha ya

Kutangaza modes, jukwaa mwenyewe rating kiwango (msingi normalises kwa asili ya 1-5), na dalili yoyote ya majibu, orodha lazima kukubaliana na spec.json.

Tafsiri ya

pullReplyFeedback anarudi matukio ya canonical: jukwaa tiketi id, jukwaa jibu ID, rating, hiari majibu / maoni, wakati kuwasilishwa na tukio imara_id. Inasoma na kutafsiri.

Ukadiriaji wa

event_id ni imara kwa maoni, hivyo tukio lililorudiwa ni no-op na mabadiliko ya rating (shinda za mtihani, kama bandari).

Mafunzo ya nidhamu

Kurasa zimefungwa na kuamua; mshale ambao hauendelei mwisho wa kukimbia. backfill ya kihistoria kama dirisha la rolling, kamwe kuvuta moja kubwa.

Usalama wa Pro

Bila usanidi wowote, rejea ukurasa kamili tupu badala ya kutupa. Mkimbiaji wa usawa anachunguza kwa hoja tupu.

Uamuzi wa kushindwa

Core inatatua kila tukio kwa jibu la ndani na kioo alama ya kioo cha tiketi tayari stamps (<slug>:<ticket>:reply:<reply>Tukio ambalo haliwezi kutatuliwa limepunguzwa, kamwe kuamuliwa; maoni tu yanaunganisha majibu ya wafanyakazi; na mkopo wa wakala daima hutoka kwa mwandishi aliyepo. inbound_ticket au ticket_mirror.

Mfano wa kazi: WHMCS

WHMCS -Kuweka alama za nyakati katika viwango vya nyota tblticketreplies.ratingNa Mwenyezi Mungu ni Mjuzi wa yote. WHMCS kiunganishi anatangaza hali ya kura na 1-5 vipimo, meli a ticket_reply_ratings Amri ya relay katika faili yake ya daraja, na hutafsiri kila mstari katika tukio ambalo ids zinalingana na whmcs:<ticket>:reply:<reply> Alama ya kioo chake cha tiketi tayari stamps. Baada ya kuboresha kiunganishi, re-copy faili daraja kwa server WHMCS hivyo amri mpya ipo hapo.

💡
Full developer mkataba na interface, maumbo tukio, sheria za kuhalalisha na orodha ya usawa: doc/contracts/TICKET_REPLY_FEEDBACK_CAPABILITY.md Katika kipindi cha OpsIQ Kukubalika: kiwango cha jibu ndani ya jukwaa, kusubiri kwa uchaguzi wa saa, na majibu sawa katika OpsIQ Inaonyesha chip, ukurasa wa maoni unaorodhesha, na tukio lililorudiwa halijabadilisha chochote.
Viunganishi

Uwezo wa kuunganisha tiketi (Contract 2.4)

Kwa kuwa ticket_merge Uwezo hufanya tiketi kuunganisha katika OpsIQ kuunganisha kwenye kila jukwaa la tikiti lililounganishwa. Tiketi ya jukwaa iliyohifadhiwa inapata ujumbe wa tiketi zilizounganishwa, kuanzia na ujumbe wa ufunguzi wa tiketi ya kila moja, badala ya tiketi ya jukwaa lililounganishwa imefungwa tu.

Kwa nini kuwepo

Kuingia kwa ndani OpsIQ Inahamisha kila ujumbe wa tiketi zilizounganishwa katika tiketi iliyohifadhiwa na huondoa tiketi zilizounganishwa. Kabla ya Mkataba 2.4 Simu ya mkononi ilisikika tu ticket.deleted kwa kila tiketi ya ndege. WHMCS Alipoteza tiketi hiyo na kuifungia WHMCS Tiketi kamwe kupokea kile mteja kwanza aliandika: somo alionyesha [MERGED] na maudhui alikuwa missing.

Nini cha kufanya

Tiketi. merged (mara moja kwa kuunganisha)

ticket_id, tiketi_idadi, mada na external_ref ya tiketi KEPT; native_table (opsiq_tickets); site_key; vyanzo, tiketa kuunganishwa zamani kwanza, kila mmoja na ticket_ID, tikete_number, mada, external_Ref, client_name, client _email, created_at na ujumbe [{reply_id, mwandishi_aina, mwendeshaji_jina, created _at, mwili}]; merged_by; merted_at. Ujumbe ni mteja-kuonekana mazungumzo, waliotekwa kabla ya hoja. kumbukumbu za ndani kamwe ni pamoja na.

Tiketi. deleted (kwa ajili ya tiketi zilizounganishwa)

Pamoja na moto huo, kwa sasa merged_into {ticket_id, ticket_number, external_ref· Waziri Mkuu hakutoa taarifa kwa mwasiliani ambaye alisema ticket_mergeWatumiaji wengine wanaweza kusema kuunganisha kutoka kwa kufuta.

Mtandao wa Nje

Tiketi.merged ni tukio la kutoa. A SaaS webhook endpoint imesajiliwa kwa tiketi.deleted pia inapata tiketi.mergied, hivyo ushirikiano kujengwa kabla ya 2.4 Kusikiliza kwa kuunganisha.

Nini cha kufanya na interface yako

Kutangaza

List ticket_merge in capabilities() and settings.json, and implement TicketMergeConnectorInterface::mergeTickets(array $merge, array $settings). Required on Contract 2.4 for any package that declares ticket_mirror or handles ticket.deleted; conformance fails it otherwise.

Kuhamasisha asili wakati unaweza

When the kept ticket and a merged ticket both have a copy on your platform (TicketMergeContract::twins() resolves them from external_ref), call the platform's own merge.

Ongeza maelezo ya kibinafsi

A merged ticket with no copy on your platform: add TicketMergeContract::transcript() to the kept platform ticket as a PRIVATE note. Never a public reply, which would email the customer their own old messages.

Kueleza kile ambacho hakijaingia

Kila nakala iliyounganishwa ambayo huwezi kuunganisha inakwenda bila kuchanganywa, na msingi hutumia utunzaji wako wa kawaida wa kufuta (karibu, au kufuta kwa mirror_deletes) kwa wale hasa. Njia ya Kurudi haijasaidiwa tu wakati jukwaa halina kuunganisha na hakuna maelezo binafsi. usafiri au kushindwa ni sawa = uongo kwa sababu; imeandikwa katika Diagnostics.

Heshima kwa wateja wako

Mafungu hayo ya kioo ambayo lango la tiketi yako nyingine inayotazama lango huunganisha.

Bonyeza hapa kuanza kwenye jukwaa lako

Resolve the platform ids and call TicketMergeContract::applyInbound(['<prefix>'], $keptId, $mergedIds). OpsIQ merges its copies with _origin=mirror, so nothing is pushed back to you.

Utekelezaji wa

WHMCS

MergeTicket (ticketid = kuweka tiketi, kuunganisha zilizounganishwa = tikiti zilizounganishwa) wakati wote wawili wako katika WHMCS; OngezaTicketNote na nakala vinginevyo. ndoano ya Tiketi ya relay inaunganisha OpsIQ Picha wakati wafanyakazi wakiwa katika WHMCS.

Zendesk

Barua ya posta /api/v2/tickets/{id}/merge.json pamoja na maoni ya kuunganisha binafsi (hadi tiketi tano kwa simu), pamoja na nakala kama maoni ya kibinafsi kwenye tikiti iliyohifadhiwa, kwa sababu Zendesk Tiketi ziliunganishwa bila kuhamisha maoni yao.

OpsIQ Daraja la Saas

Barua ya posta /v1/tickets/{id}/merge Pamoja na source_ids, ambayo hatua portal majibu na vifungo; jibu ndani hubeba nakala ya tiketi kwamba walikuwa kamwe kwenye bandari /manage Kuunganisha OpsIQ Nakala ya nakala.

Mjenzi wa Kiunganishi

ticket_merge imechukuliwa, kamwe haijatelekezwa: mfuko unaozalishwa unatangaza wakati unaunganisha tiketi ya jukwaa inayounda (msajili aliyeundwa na tikiti ya kiungo kwenye), hushughulikia tiketi.deleted, au inatangaza ticket_mirrorKwa upande wa mapato, chini ya Merges yaChagua hatua ya kuunganisha jukwaa (map kuunganisha).target_remote_idya kuingia na kutoka.source_remote_ids au ya Muungano.source_remote_id) na hatua ya kibinafsi (maelezo ya ramani).remote_id na note.body). Vifurushi vinavyozalishwa () hutumia zote mbili.Kwa hakuna, Mjenzi anaonya kwamba ujumbe wa tiketi uliounganishwa hautafikia jukwaa.

💡
Mkataba wa jumla: doc/contracts/CONNECTOR_CONTRACT.md, sehemu ya Tiketi huunganisha. Kukubali: kuunganisha tiketi mbili katika OpsIQ kwamba zote zipo kwenye jukwaa, kisha kufungua tiketi iliyowekwa kwenye jukwaa.
Viunganishi

Biashara ya Masoko

Soko la inakuwezesha kugundua, kufunga, na kuchapisha viunganisho vilivyojengwa na jamii.

Soko la
Biashara ya Masokogridi ya kutafutwa ya kadi za kontakt jamii na makundi, kufunga vifungo na ratings nyota.Biashara ya MasokoNafasi ya KaziMawasiliano ya kutafuta...CalendlyKujiandaaUfungaji wa★ 4.8HubSpotCRMUfungaji wa★ 4.6MailchimpionBarua pepeUfungaji wa★ 4.7QuickBooksAkaunti ya UhasibuUfungaji wa★ 4.5TwilioSMS ya SMSUfungaji wa★ 4.9MaelezoDocs yaUfungaji wa★ 4.41DISCOVERJumuiya ya unganisho2ya ndaniMoja ya click moja3PUBLISHIngia na uwasilishe yako
Vivinjari vya jamii, kufunga katika click moja, au ishara na kuchapisha yako mwenyewe, kabla ya imewekwa na soko tiers wote searchable.

Kutafuta na kufunga kontakt

1
Tazama

Nenda kwa Connectors > Marketplace. Tafuta kwa jina, jamii, au jukwaa.

2
Mapitio ya

Angalia maelezo, vitendo vinavyoungwa mkono, na ratings.

3
Ufungaji wa

Bonyeza Install. kiunganisho cha kupakua na kufunga kwenye soko_connectors /.

4
Kuundwa kwa Takwimu

Kuwezesha mawasiliano, kuingia API ushahidi na uchunguzi wa madai hayo.

Kuchapisha kontakt

1
Kujenga na kufanya majaribio

Tumia wajenzi wa Connector. kuthibitisha vitendo vyote.

2
Package ya Package

Maelezo ya jumla.json vitendo.json ya maarifa.json Faili za PHP.

3
Ishara ya ishara

Run php tools/sign_connector.php <slug> to sign ONE package (it also accepts a path). It does not boot OpsIQ, so give it the key: either --key=<secret> or the OPSIQ_CONNECTOR_SIGNING_KEY environment variable, otherwise it stops with "No signing key available". tools/resign_all_connectors.php re-signs EVERY package on the install and reads the key from settings by itself, but it can also mint a NEW install-wide signing key, so reach for it only when that is what you want.

4
Kuwasilisha

Pakia kupitia mtiririko wa uwasilishaji wa soko kwa ukaguzi.

2 Mawasiliano ya simu

connectors / — nini kweli anaendesha

Kila kitu hapa ni kuishi: viunganisho vinavyosafirisha na OpsIQ, chochote kilichowekwa kutoka sokoni, na chochote ambacho Mjenzi wa Kuunganisha huchapisha kwenye ufungaji huu.

Home / Biashara / Uchumi/Makampuni ya simu yatakiwa kutoa taarifa

Chanzo cha kuchapisha kwa vifurushi vya soko la kwanza. Sio mzizi wa ugunduzi: hakuna kitu hapa ni kuishi mpaka imeingizwa, saini, mbegu kwenye orodha na imewekwa, ambapo ardhi ya nakala katika viunganisho /.

💡
Angalia katika maeneo yote mawili. mfuko wewe authored chini marketplace_connectors / si nakala kwamba mbio — kufunga nakala yake ndani ya connectors /, na tu kwamba nakala ni kugunduliwa katika runtime. Stripe, BigCommerce, Magento 2, PrestaShop, OpenCart, Amazon SES, Postmark na Resend ni packages soko wote: kufunga moja kabla ya kutarajia kupata katika Connectors.
Developer ya developer

API Mhandisi wa Webhook

Kwa kuwa API Webhook Builder inakuwezesha kuunda desturi API Wasikilizaji na wasikilizaji wa wavuti ndani OpsIQ bila ya kuwa na PHP.

API Ujenzi wa jengo
API Mhandisi wa WebhookMjenzi anayechagua aina ya kuchochea (ndani ya mtandao, ratiba, tukio, mwongozo) ambayo hulisha katika hatua inayoweza kusanidiwa.API Mtumiaji wa Webhook BuilderNafasi ya KaziKuanzaMtandao wa InboundMpango wa (Cron)OpsIQ Tukio la tukioMwongozo wa MwongozoHatua ya hatuaRamani za maeneo ya kuingia→Kutoa tiketi / taarifa/ piga simu APIHifadhi ya Mwisho1MtunziWebhook · ratiba · tukio · mwongozo2NO RAW PHPAlizaliwa katika3HatuaRamani ya maeneo, kisha kukimbia
Kujenga vituo vya mwisho bila PHP mbichi: chagua kuchochea (ndani ya webhook, ratiba, tukio au mwongozo), kisha maeneo ya ramani kwa hatua.

Vichochezi

Tukio la tukio

wakati kitu kinapokuwa ndani ya OpsIQ Au wakati mfumo wa nje unachapisha tukio linalolingana na wavuti yako URL Jina la tukio, kwa mfano tiketi. kuundwa.

Ratiba ya ratiba

Tumia moja ya matukio ya muda mrefu kama jina la tukio: cron. dakika, cron au cron kila siku.

Phra ya

Kukimbia wakati admin anauliza AI kwa ajili yake katika lugha wazi. Ongeza maneno ambayo lazima mechi, kwa mfano kupata mteja.

Mtandao wa Inbound

Mfumo wa nje hutuma HTTP Post kwa yako OpsIQ Mtandao wa Yahoo URL Kwa jina la tukio lolote, kuchochea kusikia kwa moto wa tukio hilo.

Wakati mwingine, ni muhimu tu: hali

Tukio trigger inaweza kubeba hali, hivyo tu anaendesha wakati incoming data mechi. Bila ya masharti ni anaendesha kila wakati tukio moto.

Field ya Field

Njia katika data ya tukio. Tumia dot kwa maadili yaliyohifadhiwa, kwa mfano mteja. Email.

Kuingiliana na kila kitu au

Chagua kama kila sheria lazima icheze, au tu moja ya kanuni hizo.

Majaribio ya

sawa, si sawa, ina, haina, huanza na, ni moja ya, si moja ya. Matching kupuuza miji mikuu.

Idadi ya majaribio

Idadi kubwa zaidi kuliko, angalau, chini ya idadi nyingi. Hesabu zilizoandikwa kama maandishi bado kulinganisha kwa usahihi.

Uchunguzi wa

Iko hapa, haipo, iko tupu, haijaachwa.

Ukurasa pekee wa injini ya utafutaji kwa ajili ya tiketi za dharura

Kwa mfano:
Tiketi ya Tukio. kuundwa, na kanuni moja: kipaumbele sawa na dharura.
Nini cha kufanya:

Hatua hiyo inasimamia tiketi za dharura na imeruka kwa kila kitu kingine. Hakuna kuchuja inahitajika mwisho wako.

💡
Ikiwa unaacha sheria tupu trigger anaendesha kila tukio linalolingana, ambayo ni tabia sawa na kabla ya hali kuwepo.

Hatua za

Kuhamisha Webhook

Tuma HTTP kwa Ujumbe wa Nje URL kwa malipo ya kawaida.

Kujenga tiketi

Unda tiketi ya msaada na idara maalum, somo, na ujumbe.

Tuma ujumbe wa email

Tuma barua pepe kwa template ya desturi.

Rekodi ya rekodi

Kusasisha mteja, tiketi au rekodi ya CRM.

Utekelezaji wa kontakt

Kupitisha hatua iliyosajiliwa kutoka kwa kontakt iliyowezeshwa na idhini ya kontrakta wake na sheria za uthibitisho.

Kuendesha gari OpsIQ Jenerali Mkuu API Hatua ya hatua

Tafuta orodha kamili inayoitwa General API catalog. Fields, mawanda, ruhusa, uthibitisho, idempotency na msaada wa kukimbia kavu hutoka kwa mkataba wa utekelezaji wa kuishi; kazi ya kufanya kazi hufanya ndani ya nafasi yake ya kazi iliyohifadhiwa na mazingira ya msimamizi.

Kutoa huduma ya ushauri API Maombi ya maombi

Tumia interface ya asili API Kusoma au kuthibitisha asili API Andika hatua wakati mtoa huduma endpoint haina hatua curated. Credentials kubaki ndani ya kontakt na tu jamaa njia za mtoa huduma ni kukubalika.

Wafanyakazi wa Actions & Triggers wajenzi, /api/v1.php, OpenAPI na Postman hutumia hatua moja ya utekelezaji, hivyo hatua iliyochaguliwa haiwezi kuelea kutoka kwa nyaraka za muda.
Developer ya developer

Waigizaji wa filamu za Kibongo

Tayari kutumia maelekezo ya hatua kwa ajili ya automatisering kawaida.

Jinsi ya kufanya kazi
Waigizaji wa filamu za KibongoMtiririko wa mapishi: Webhook ya uptime hupita chujio cha uzalishaji, kisha mashabiki nje ili kuunda tiketi ya haraka na kuwajulisha Slack.uptime.downUfuatiliaji wa WebhookIkiwa una niafilterTiketi ya dharuraKuthibitisha Slack #ops
Waigizaji wa filamu za Kibongo

Auto-kuunda tiketi kutoka kwa ufuatiliaji

Kwa mfano:
Mfumo wa ufuatiliaji hutuma post wakati seva inapungua.
Nini cha kufanya:

Trigger: Inbound webhook Condition: payload.status = "down" Action: Create ticket · Dept: Technical, Subject: "Server {{payload.hostname}} down", Priority: Urgent

SlackTaarifa juu ya amri kubwa

Kwa mfano:
Ujumbe wa Slack kila wakati mteja anaweka amri juu ya $100.
Nini cha kufanya:

Trigger: Event (order.completed) Condition: order.amount > 100 Action: Send webhook to Slack incoming webhook URL with order details

Wiki ya Kuhamisha Email

Kwa mfano:
Barua pepe ya muhtasari kwa usimamizi kila Jumatatu saa 9 asubuhi.
Nini cha kufanya:

Trigger: Schedule (Monday 09:00) Action: Send email with last week's stats pulled from the REST API

tiketi za ndege kwa stale

Kwa mfano:
Kama huna tiketi ya kujibu 24 Muda wa kazi, teua uongozi wa timu.
Nini cha kufanya:

Trigger: Schedule (every hour) Condition: ticket.status = "Open" AND ticket.last_reply_age > 86400 Action: Assign to team-lead, add internal note

Developer ya developer

Kujenga hatua yako ya kwanza

Hii walkthrough inajenga hatua connector rahisi kutoka mwanzo.

Ujenzi wa vitendo
Kujenga hatuaFomu ya ufafanuzi wa hatua: jina la kuangaliaup_order, ombi la GET /orders/{id}, parameter ya kitambulisho cha aina, na kupitisha 200 ya uchunguzi.Hatua mpyaNafasi ya KaziHatua mpyaJina la jinalookup_orderMaombi ya maombiGET/orders/{id}Paradizi ya· Kusimama imara200 · Utaratibu wa kupata1DEFINEJina, Njia ya Mwisho2PARAMSAina ya pembejeo3yaMaisha ya kuishi 200 Matokeo ya matokeo
Kujenga hatua moja kutoka mwanzo. jina, kuweka njia na mwisho, kutangaza vimelea typed, na mtihani kwa kuishi 200.

2 Hatua ya

Kabla ya kuanza, kuamua ni nani unahitaji. wote ni configured katika screen moja.

Wito wa nje API

Hatua hutuma ombi la HTTP kwenye jukwaa lako. Chagua hii wakati ambapo OpsIQ inahitaji kufikia na kufanya kitu upande wako.

Kuunganishwa kwa hatua ya kontakt

Hatua anaendesha kitu ambacho kiunganisho kilichowekwa tayari hutoa. Chagua hii wakati kazi iko tayari inapatikana na unataka tu kuisababisha. Unachukua hatua ya kontakt kutoka kwenye orodha, kwa hivyo hakuna chochote cha waya.

Chaguo la pili ni jinsi unavyotumia kila kitu ambacho waunganishaji wako wanaweza tayari kufanya bila kujenga yoyote tena: kusoma thread ya tiketi, kuangalia mteja, kuagiza mawasiliano, na kadhalika. Chagua hatua ya kontakt kutoka kushuka na umefanya.
1
Mpango wa Hatua

Mfano: "lookup_product". Angalia bidhaa kwa jina, bei ya kurudi, hisa, na maelezo.

2
Kufafanua katika vitendo.json

Ongeza ufafanuzi wa hatua:

vitendo.json- Muundo halisi wa wazi
{
  "actions": [
    {
      "action_id": "lookup_product",
      "label": "Look up a product",
      "category": "Catalogue",
      "description": "Find a product by name and return price, stock and description.",
      "scope": "admin",
      "requires_confirmation": false,
      "is_destructive": false,
      "delivery_type": "http",
      "http_method": "GET",
      "http_url": "/api/products/search",
      "parameters": [
        { "name": "name", "type": "string", "required": true, "in": "query",
          "description": "Product name to search for" }
      ],
      "returns": [
        { "alias": "id",          "path": "data.id",             "type": "string" },
        { "alias": "name",        "path": "data.name",           "type": "string" },
        { "alias": "price",       "path": "data.price",          "type": "number" },
        { "alias": "stock",       "path": "data.stock_quantity", "type": "number" }
      ]
    }
  ]
}
⚠️
Mambo matatu ambayo hufanya hatua kushindwa kujiandikisha kabisa. action_id ni REQUIRED na lazima kuwa2Kwa ajili ya100Wahusika wa barua za chini, tarakimu na inasisitiza - kuingia bila moja kukataliwa kabisa. wazi ni kitu kilicho na "hatua" LIST, sio ramani iliyochorwa kwa jina la hatua. Na ramani ya majibu ni "kurejea" na njia za DOTTED (data.id), si JSONPath ($. data.id) - hakuna "jibu_mapping", "method", 'mwisho' au "sehemu" mahali popote katika Usajili.
3
Uchunguzi wa Kukausha kwa Dry-run

Katika hatua ya Mapitio ya Wajenzi wa Connector, bonyeza Dry run. Inaendesha orodha kamili ya kulinganisha dhidi ya mfuko wako na, wakati umewapa sifa, hufanya mtihani halisi wa uunganisho. Haitumii data ya sampuli.

4
Kuthibitisha matumizi ya

Uliza admin AI: "Angalia bidhaa Widget Pro." AI inapaswa kupata na kutekeleza hatua.

⚠️
Kuongeza hatua kwa vitendo.json haiumbi njia ya AJAX, hivyo hakuna kitu cha kuzaliwa tena. vitendo vya Kuunganisha vinaunganishwa katika OpsIQ wakati kontakt imewezeshwa au mipangilio yake imehifadhiwa: kuokoa upya kiunganishi na hatua mpya inaonekana. zana /gen_route_registry. php inashughulikia usafirishaji wa AJAx wa admin na haina kuzaa kwenye matendo ya uunganisho.
Developer ya developer

Matukio ya mwisho

Mwisho wa Maombi ya Kukubaliwa JSON kutoka kwa mfumo mwingine na kuigeuza kuwa shughuli za kuwasiliana zilizoingizwa ambazo zinaweza kulisha ratiba, kufunga na kazi.

Bidhaa ya Screen
Mwisho wa MaombiKila chanzo cha ndani kina wenyewe. URL, siri, ramani na matokeo ya shughuli za hivi karibuni.Mwisho wa MaombiNafasi ya KaziVyanzo vya5ACCEPTED12.4kREJECTED18Maisha ya kazi ya VIEWJukwaa la BillingMatukio ya usajiliAfya ya afyaBidhaa ya AppMatukio ya ishara na matumiziAfya ya afyaTukio la IDprovider_event_idDevi yaIshara yaX-OpsIQ-Inbound-SignatureHMAC ya1CREATE SOURCEURL Kuwa siri2MAP PAYLOADBarua pepe, tukio na ID3ya waHMAC Baada ya kuingia
Kila chanzo cha ndani kina wenyewe. URL, siri, ramani na matokeo ya shughuli za hivi karibuni.

Kujenga chanzo moja kwa kutuma mfumo. OpsIQ huzalisha URL/ Token na siri. Kutuma JSON na Content-Type: application/json Tumia mwili wa kawaida kwa kutumia HMAC-SHA256:

X-OpsIQ-Inbound-Signature: sha256=<hex hmac>

Ramani ya ramani JSON Njia za barua pepe ya kuwasiliana, jina la tukio na ID ya tukio la hiari. Kitambulisho cha tukio ni ufunguo wa deduplication iliyopendekezwa. Shughuli iliyokubaliwa huingia wakati wa mawasiliano na inaweza kuathiri bao la kuongoza, sehemu, sheria za mzunguko wa maisha na kazi.

Kukataa saini halali kabla ya kugawanya data biashara. Kuzunguka siri kwa update pande zote mbili ndani ya dirisha kudhibitiwa; si logi siri.

Developer ya developer

Shughuli za Webhook

Utawala wa mtandao unaoingia huunda usajili uliosainiwa, vituo vya majaribio na wachunguzi wa utoaji wa asynchronous na afya ya retry.

Bidhaa ya Screen
Mtandao wa NjeUkurasa wa wavuti unaoingia unaorodhesha vituo vya mwisho vya HTTPS, usajili wa tukio, afya ya utoaji na mtihani uliosainiwa moja.Mtandao wa NjeNafasi ya KaziENDPOINTS7SUCCESS99.2%Kurudishwa4Maisha ya kazi ya VIEWCRM ya kiooMawasiliano* na mawasiliano.Afya ya afyaMsaada wa BusPicha zote na Wizara ya Mambo ya Ndani ya Nchi. *Afya ya afyaData ya kuhifadhi*KufufuaUwasilishaji wa mtihaniSampuli ya MalipoKamili1SUBSCRIBEya HTTPS URL Matukio ya2AUTHENTICATETaarifa ya HMAC3OBSERVEUsafiri wa Reli na Retries
Ukurasa wa wavuti unaoingia unaorodhesha vituo vya mwisho vya HTTPS, usajili wa tukio, afya ya utoaji na mtihani uliosainiwa moja.

Wasimamizi kamili huunda mwisho wa HTTPS, chagua matukio maalum au kadi ya mwitu, tunza siri kwa usalama na utuma mtihani. OpsIQ ishara ya mzigo wa malipo ghafi na HMAC-SHA256:

X-OpsIQ-Signature: sha256=<hex hmac>

Thibitisha saini kabla ya kufuta au kaimu. utoaji ni asynchronous na moja kwa moja retried baada ya takriban 1Kwa dakika moja, 5 Kwa dakika moja, 30 Kwa dakika moja,2Muda wa saa na 12 Masaa ya masaaTumia reli ya hivi karibuni ili kukagua hali, msimbo wa majibu na kuhesabu jaribio.

Mpokeaji wako lazima awe na uwezo kwa sababu mfumo wowote wa asynchronous unaweza kutoa upya. Kurudi majibu ya 2xx tu baada ya kukubalika kwa muda mrefu.

Developer ya developer

Webhooks

Webhooks kuruhusu mifumo ya nje kuwajulisha OpsIQ Kama kuna jambo (yaliyopita) na kama OpsIQ Kujulisha mifumo ya nje wakati kitu kinachotokea ndani (nje).

Webhooks
Mtandao wa NjeSkrini ya wavuti iliyo nje: meza ya mwisho na jina, matukio yaliyosajiliwa, dots za hali ya utoaji wa hivi karibuni, na kifungo cha mtihani wa Send.Mtandao wa NjeNafasi ya KaziMwisho wa Maombi+ Mwisho wa MaombiJina laMatukio yaMaisha yaSlack ya #sales-alertshttps://hooks.slack.com/…crm. deal. won, iliJaribio la majaribioCRM ya kioohttps://api.acme.com/hook*Kupata tiketi*,kupatikanaJaribio la majaribioZapierhttps://hooks.zapier.com/…chat.startedJaribio la majaribio1ENDPOINTSJina, Matukio ya URL2SIGNEDHMAC + Auto-Retried3SEND TESTKuthibitisha utoaji
Screen halisi ya mtandao wa wavuti: kila mwisho na matukio yake, afya ya utoaji wa hivi karibuni, na mtihani wa kutuma moja kwa moja, uliosainiwa na kurejeshwa.

Mtandao wa Nje

Kujiunga

Nenda kwenye Mipangilio > Webhooks. Ongeza mwisho wa pointi URL na uchague matukio ya kupokea.

Matukio ya matukio

Kujihusisha na matukio maalum, au ["*"] Kila kitu ni katika orodha yako. webhooks.events.list Kurejea kamaJSON.

Rehani ya

Kuondolewa kwa vifaa vya umeme, baada ya 15 Kushindwa kwa mfululizo, mwisho ni auto-disabled.

Kusaini

Kila utoaji unasainiwa. X-OpsIQ-Signature carries v2=<hex>Na kwa upande wa TAMISEMI, version.timestamp.delivery_id.body - si mwili peke yake. Daima kuthibitisha, na daima kujenga kamba hasa.

Ulinzi wa SSRF

OpsIQ si kutuma kwa binafsi / ndani IPs (127x, 10x, 172.16x, 192.168x, 169.254.169.254).

Uwasilishaji wa Async

Webhooks hutolewa kupitia foleni ya kazi, sio kuzuia OpsIQ shughuli za.

Kitambulisho cha Tukio

Kila tukio lina tukio la kipekee_id ambalo linabaki sawa katika retries kwa kupungua.

Nini cha kufanya na kila bidhaa

X-OpsIQ-Event

Kwa mfano, jina la ticket.created.

X-OpsIQ-Delivery

Kitambulisho cha utoaji. Inakaa sawa katika retries - kuitumia kupuuza duplicate.

X-OpsIQ-Timestamp

Kukataa kitu chochote cha zamani kuliko dakika tano.

X-OpsIQ-Signature

Taarifa hiyo kama v2=<hex>Kugawanya kwenye =Upande wa kushoto ni toleo, upande wa kulia ni thamani unayolinganisha.

X-OpsIQ-Signature-Version

Mpango huo ambao kwa sasa unatumika v2Soma kutoka kichwa badala ya ngumu-kukifunga, na msimbo wako anaendelea kufanya kazi kama v3 ni milele aliongeza.

⚠️
Hati ya usajili ni version.timestamp.delivery_id.body, si mwili mbichi peke yake. Kufunga tu mwili ni moja ya sababu ya kawaida ya uhakiki inashindwa - kila utoaji wa kweli unakataliwa na mwisho unaonekana kuvunjwa.

Kuthibitisha utoaji

PHP · KuthibitishaOpsIQMtandao wa Yahoo
<?php
// Read the raw body BEFORE any framework parses it — the signature covers
// the exact bytes we sent, so a re-encoded array will not match.
$raw      = file_get_contents("php://input");
$sigHeader= $_SERVER["HTTP_X_OPSIQ_SIGNATURE"] ?? "";   // "v2=<hex>"
$ts       = (string)($_SERVER["HTTP_X_OPSIQ_TIMESTAMP"] ?? "");
$delivery = (string)($_SERVER["HTTP_X_OPSIQ_DELIVERY"] ?? "");
$secret   = "your endpoint signing secret";   // shown once when you add the endpoint

// 1. Refuse a stale delivery. This is what stops a captured request being replayed.
if ($ts === "" || abs(time() - (int)$ts) > 300) {
    http_response_code(401);
    exit(json_encode(["error" => "Stale delivery"]));
}

// 2. The header names its own version: "v2=<hex>".
[$version, $received] = array_pad(explode("=", $sigHeader, 2), 2, "");

// 3. Rebuild exactly what OpsIQ signed.
$canonical = $version . "." . $ts . "." . $delivery . "." . $raw;
$expected  = hash_hmac("sha256", $canonical, $secret);

// 4. Constant-time compare, so a timing attack cannot reveal the secret.
if ($received === "" || !hash_equals($expected, $received)) {
    http_response_code(401);
    exit(json_encode(["error" => "Invalid signature"]));
}

// 5. Accept. Deliveries retry, so treat a delivery id you have already
//    processed as a success and do the work only once.
$event = json_decode($raw, true);
// ... your handling ...

http_response_code(200);
echo json_encode(["received" => true]);
Node.js · Ukaguzi waOpsIQMtandao wa Yahoo
const crypto = require("crypto");

// express.raw gives you the exact bytes OpsIQ signed. express.json() does not.
app.post("/opsiq-webhook", express.raw({ type: "application/json" }), (req, res) => {
  const raw      = req.body;                                  // Buffer
  const sig      = req.headers["x-opsiq-signature"]  || "";   // "v2=<hex>"
  const ts       = req.headers["x-opsiq-timestamp"]  || "";
  const delivery = req.headers["x-opsiq-delivery"]   || "";
  const secret   = process.env.OPSIQ_WEBHOOK_SECRET;

  // 1. Reject stale deliveries (replay protection).
  if (!ts || Math.abs(Date.now() / 1000 - Number(ts)) > 300) {
    return res.status(401).json({ error: "Stale delivery" });
  }

  // 2. Split "v2=<hex>" into its version and its value.
  const [version, received] = sig.split("=", 2);

  // 3. Rebuild what OpsIQ signed: version.timestamp.delivery_id.body
  const canonical = Buffer.concat([
    Buffer.from(`${version}.${ts}.${delivery}.`),
    raw,
  ]);
  const expected = crypto.createHmac("sha256", secret).update(canonical).digest("hex");

  // 4. Constant-time compare. Lengths must match first or timingSafeEqual throws.
  const a = Buffer.from(expected), b = Buffer.from(received || "");
  if (a.length !== b.length || !crypto.timingSafeEqual(a, b)) {
    return res.status(401).json({ error: "Invalid signature" });
  }

  // 5. Accept, and make the work idempotent on the delivery id.
  const event = JSON.parse(raw.toString("utf8"));
  res.json({ received: true });
});

Kila tukio ambalo linaweza kutokea

Imeundwa kutoka kwa ujenzi wa mbio, hivyo daima inafanana na toleo ulilokuwa nalo.

52 events can be delivered to a webhook endpoint on this install. Subscribe with ["*"] for all of them, or name the ones you want. The General API action webhooks.events.list Rejea orodha hii kama ifuatavyoJSONKwa hiyo, kanuni yako kamwe haina kuwa na ngumu-code ni.

Uchambuzi wa analytics (1)

analytics.anomaly

Fired by PHASE_ANOMALY_ALERTS when a daily KPI (sessions, pageviews, conversions, revenue) deviates from its same-weekday 4-week baseline beyond the configured threshold. Payload: day (required), title, site_key, anomalies.

Biashara ya biashara (2)

commerce.order.created

Fired the moment a chat-confirmed order lands on the merchant platform (connector or custom-actions integration) - before payment. Subscribe to sync carts, reserve stock, or notify fulfilment systems. Payload: reference (required), connector, amount_minor, currency, customer_email, thread_id, occurred_at.

commerce.payment.confirmed

Fired exactly once per order when the gateway actively verifies the payment (amount and currency exact). This is the settlement signal - it rides the same claim that prevents duplicate receipts, so it can never double-fire. Payload: reference (required), connector, occurred_at.

Mawasiliano ya mawasiliano (6)

contact.conversion

Fired by OpsIQ.

contact.erased

Fired by OpsIQ.

contact.lifecycle_changed

Fired by OpsIQ.

contact.status_changed

Fired by OpsIQ.

contact.tag_added

Fired by OpsIQ.

opsiq.contact.upsert

Fired by OpsIQ.

conversation (5)

conversation.assigned

Fired when a conversation is assigned to an agent or unassigned. Payload: thread_id (required), site_key, assigned_admin_id, by_admin_id, occurred_at.

conversation.created

Fired when a new Client Chat conversation (thread) is opened. Payload: thread_id (required), site_key, channel, client_email, client_name, visitor_id, created_at.

conversation.message.created

Fired when a visible message is written to a conversation by the visitor, an agent, the AI or the system. Internal notes do not fire. Payload: thread_id (required), message_id (required), site_key, sender_type, admin_id, message, has_attachment, created_at.

conversation.rated

Fired when the visitor rates a conversation (1-5 stars). Payload: thread_id (required), site_key, stars, comment, trigger, admin_id, occurred_at.

conversation.resolved

Fired when an agent resolves a conversation and hands it back to the AI. Payload: thread_id (required), site_key, by_admin_id, occurred_at.

ya crm (6)

crm.company.created

Fired when a CRM company/account is created. Payload: company_id (required), name.

crm.deal.created

Fired when a CRM deal/opportunity is created (by an order, the capture agent, or a human). Payload: deal_id (required), title, amount, currency, scope.

crm.deal.lost

Fired when a deal is moved to a Lost stage (closed-lost). Payload: deal_id (required), stage, amount.

crm.deal.stage_changed

Fired when a deal moves to a different pipeline stage. Payload: deal_id (required), stage, amount.

crm.deal.won

Fired when a deal is moved to a Won stage (closed-won). Payload: deal_id (required), stage, amount.

crm.task.created

Fired when a CRM task is created (incl. AI-suggested next-step / renewal tasks). Payload: task_id (required), title.

barua pepe (2)

email.bounced

Fired by OpsIQ.

email.replied

Fired by OpsIQ.

feedback (13)

feedback.analysis.completed

Fired when a Voice-of-Customer analysis run completes. Payload: analysis_run_id (required), workspace_key, sample_count, model_version.

feedback.detractor.detected

Fired when a newly indexed response meets its metric-specific detractor rule. Payload: feedback_item_id (required), workspace_key, source_kind, metric_kind, classification.

feedback.follow_up.completed

Fired when a Feedback follow-up is completed. Payload: feedback_item_id (required), workspace_key, actor_admin_id, outcome_code.

feedback.item.assigned

Fired when Feedback ownership changes. Payload: feedback_item_id (required), workspace_key, assignee_admin_id, team_id, actor_admin_id.

feedback.item.indexed

Fired when a source record is added to or refreshed in the canonical Feedback index. Payload: feedback_item_id (required), source_kind, source_id, workspace_key, metric_kind, classification.

feedback.item.redacted

Fired when source deletion or redaction removes Feedback content from the index. Payload: feedback_item_id (required), workspace_key, source_kind.

feedback.item.status_changed

Fired when the Feedback workflow state changes. Payload: feedback_item_id (required), workspace_key, state, actor_admin_id.

feedback.item.tagged

Fired when a tag is added to or removed from Feedback. Payload: feedback_item_id (required), workspace_key, tag, operation.

feedback.item.updated

Fired when a canonical Feedback item changes. Payload: feedback_item_id (required), workspace_key, change.

feedback.source.failed

Fired when a Feedback source replay or incremental index operation fails. Payload: workspace_key, source_kind (required), error_code, checkpoint.

feedback.source.lagging

Fired when a Feedback source checkpoint is behind its expected freshness window. Payload: workspace_key, source_kind (required), lag_seconds, last_success_at.

feedback.theme.detected

Fired when a canonical topic or theme signal is attached to Feedback. Payload: feedback_item_id (required), workspace_key, theme_key, confidence.

feedback.urgent.detected

Fired when an urgent Feedback signal is detected. Payload: feedback_item_id (required), workspace_key, source_kind, signal_key.

invoice (3)

invoice.created

Fired when an invoice is generated. Payload: invoice_id (required), customer_id, customer_email, amount, currency, due_date, items.

invoice.overdue

Fired when an invoice passes its due date unpaid. Payload: invoice_id (required), customer_id, customer_email, amount, currency, days_overdue.

invoice.paid

Fired when an invoice is paid in full. Payload: invoice_id (required), customer_id, customer_email, amount, currency, paid_at.

order (1)

order.created

Fired when a new order is placed. Payload: order_id (required), customer_id, customer_email, amount, currency, items, status, source.

Malipo ya malipo (3)

payment.completed

Fired when a payment succeeds. Payload: order_id (required), payment_id, provider_ref, customer_id, customer_email, amount, amount_minor, currency, gateway, invoice_id, items, paid_at.

payment.failed

Fired when a payment attempt fails. Payload: order_id, customer_id, customer_email, amount, currency, gateway, reason.

payment.refunded

Fired when a refund is issued. Payload: order_id, refund_id, customer_id, customer_email, amount, currency, reason.

Usalama wa usalama (1)

security.alert

Fired by PHASE_SECURITY_ALERTS when a security rule trips: failed-login wave, new automatic IP blocks, or a tamper-evidence (audit/consent hash chain) verification failure. Payload: rule (required), title, site_key, count, blocks, errors.

subscription (3)

subscription.cancelled

Fired when a subscription is cancelled. Payload: subscription_id (required), plan_name, customer_id, customer_email, cancel_reason, cancelled_at, ends_at.

subscription.created

Fired when a subscription is started. Payload: subscription_id (required), plan_id, plan_name, customer_id, customer_email, amount, currency, interval, trial_ends_at, next_billing_at.

subscription.renewed

Fired when a subscription renews successfully. Payload: subscription_id (required), plan_name, customer_id, customer_email, amount, currency, next_billing_at.

tiketi ya ndege (5)

ticket.closed

Fired when a ticket is closed or resolved. Payload: ticket_id (required), resolution, closed_by_type, closed_by_id.

ticket.created

Fired when a new support ticket is opened. Payload: ticket_id (required), ticket_number, subject, department_id, department_name, customer_id, customer_email, priority, message, author_type, author_id, author_name.

ticket.merged

Fired when one or more tickets are merged into another ticket. Payload: ticket_id (required), ticket_number, subject, external_ref, native_table, site_key, sources, merged_by, merged_at.

ticket.renumbered

Fired when a connector mirror adopts the remote platform's ticket number for an OpsIQ ticket. Payload: ticket_id (required), old_number (required), ticket_number (required), connector, external_ref.

ticket.replied

Fired when a reply is posted to a ticket. Payload: ticket_id (required), reply_id, author_type, author_id, author_name, message.

user (1)

user.registered

Fired when a new user/customer account is created. Payload: user_id (required), email, firstname, lastname, company, country, source.

Jinsi ya kufanya utafiti wa WebHub ndani?+

Tumia ngrok ili kufichua seva yako ya ndani. Weka mwisho wa wavuti kwenye ngrok yako URL.

Nini ikiwa mwisho wangu ni wa muda mfupi?+

OpsIQ Retries na backoff ya maonyesho. Ikiwa mwisho wako unapona ndani ya dirisha la retry, hakuna matukio yanapotea.

Developer ya developer

Funguo za API

API Maombi ya kweli kwa ajili ya OpsIQ Radha API Kila moja ya vipengele vya msingi vimepewa ruhusa.

Funguo za API
Funguo za APIKwa kuwa API skrini funguo: jopo la suala na kiwango cha upatikanaji na chips upeo, kando ya orodha ya funguo zilizopo masked na vifungo vya kufuta.Funguo za APINafasi ya KaziKuwasilisha hoja muhimuUpatikanaji wa upatikanajiSoma tuKikomoMipakacontacts.readtickets.readevents.writeMasuala ya msingiVifungu vyakoUshirikiano wa Zapieropq_••••4f2aKurejea kwaApp ya simuopq_••••91c7Kurejea kwaAnalytics ya njeopq_••••2db0Kurejea kwa1SCOPEDKujiandikisha au kupunguzwa2PER-ACTIONChagua maeneo sahihi3REVOCABLEKujiandikisha wakati wowote
Kuwa halisi API Screen funguo: kutoa ufunguo wa upeo, kusoma tu au vikwazo kwa kuchagua mawanda halisi, na kufuta ufunguo wowote wakati wowote.

Kujenga Kuwa API Key key muhimu

1
Nenda kwenye Mipangilio > API Mambo ya msingi

Navigate kuwa na API Usimamizi wa msingi.

2
Bonyeza kitufe cha Kujenga

Andika jina la kikoa.

3
Chagua maeneo

Kutoa ufunguo tu kile kinachohitajika. Scopes huja katika kusoma na kuandika jozi kwa kila eneo, hivyo ushirikiano wa taarifa unaweza kupewa kusoma na hakuna kitu kingine.

Maeneo ya Inapatikana

Chagua seti nyembamba zaidi ambayo inafanya kazi. admin Kutimiza kila upeo chini, hivyo kutumia tu wakati unahitaji upatikanaji mpana.

crm. read/cm. write zaidi ya mwaka mmoja uliopita

Mawasiliano, makampuni, mikataba, shughuli, sehemu, kufikia, uongofu, lifecycle na CRM webhooks.

tiketi ya kuingia. read/ tickets. write

Orodha na kusoma tiketi na ujumbe wao; jibu, update, wazi na kukimbia shughuli wingi foleni.

Majadiliano ya mazungumzo. kusoma / majadiliano.

Soma mazungumzo ya kuishi na historia ya ujumbe; tuma ujumbe, teua na kubadilisha hali.

kb. read/b. write zaidi ya mwaka mmoja uliopita

Msingi wa ujuzi.

Chat. read / chat. write

Kuokolewa kwa templates za kujibu.

connectors.read

Angalia ni nini wateja wako wananunua, na kisha unaweza kununua.

automations.read

Angalia matendo yako, kuchochea na historia yao ya kukimbia.

departments.read

Huduma zinazopatikana kwa ajili ya uendeshaji.

notifications.read

Kutambuliwa kwa operator aitwaye.

analytics.read

Sehemu ya Taarifa, CSV wa mapato na matumizi ya taarifa zilizoandaliwa.

site_intelligence.read

Tovuti zilizofuatiliwa na ripoti zao za SEO.

files.read

Bonyeza kiungo cha kupakua kwa ajili ya attachments.

status.write

Ukurasa wa ukurasa na matukio.

Kuandika kuandika

Waandishi wa AI: rasimu, muhtasari, kutafsiri, kuandika upya, kuandika, kuchambua.

Usimamizi wa admin

Kila kitu, ikiwa ni pamoja na idadi ndogo ya vitendo nyeti ambayo kwa makusudi hayawezi kufikiwa na upeo wowote mdogo: kufuta mawasiliano, kubadilisha mipangilio ya faragha, na kusoma logi ya upatikanaji.

💡
Piga hatua za meta. hatua na ufunguo wako ili kuona ni vitendo gani vinavyoweza kukimbia kwenye ufungaji wako. Hiyo daima ni ya kuaminika zaidi kuliko kufanya kazi kutoka orodha.

Viwango vya Upatikanaji wa

Wote

Kitu muhimu kinaweza kuitwa chochote ambacho mipaka yake inaruhusu.

Soma tu

Kila kuandika ni kukataliwa, chochote mawanda kusema. chaguo salama zaidi kwa taarifa, dashibodi na kitu chochote kwamba lazima kamwe mabadiliko data.

Kikomo

Unaorodhesha vitendo halisi ambavyo ufunguo unaweza kupiga simu. Kitu kingine chochote kinakataliwa, hata ndani ya wigo unaoruhusiwa.

4
Kusanya ufunguo

Bonyeza "Ingia". kisha bofya "Ongeza".

🚫
Kamwe kushiriki API nywila katika kanuni ya umma, mteja upande JavaScript, au toleo kudhibiti. Matumizi mazingira vigezo.
Developer ya developer

Kuunganisha tovuti yako

Kwa kuwa OpsIQ Widget ni moja ya JavaScript snippet wewe kuongeza kwenye tovuti yako kwa ajili ya kufuatilia, AI chat, uumbaji tiketi, na kitambulisho cha wateja.

Jinsi ya kufanya kazi
Kuunganisha tovuti yakoNakala ya mstari mmoja juu ya kulia na, upande wa kulia, ukurasa wa wavuti na OpsIQ Bonyeza Bubbles kuonekana kwenye kona.<!-- paste before </body> --><script src="https://cdn.opsiq.io/w.js" data-site="ws_8a2f" async></script>
Kuunganisha tovuti yako

Ufungaji wa msingi

Msingi wa widget
<script src="https://your-opsiq-domain.com/widget.php"
  data-site-key="site_abc123"
  async></script>

Paste before the closing </body> tag. The script loads asynchronously and does not block page rendering.

Sifa za Configuration

data-site-key

Unahitaji tovuti yako muhimu kutoka kwa maeneo yaliyounganishwa.

data-mode

Chaguo. "chat" (default), "tickets", au "zote mbili".

data-position

Bofya "Kuondoa" au "kuondoa".

data-color

Chaguo la kwanza - Kanuni ya rangi ya hex.

data-greeting

Ujumbe wa salamu za mwanzo.

data-language

Lugha ya hiari: "en", "es", 'fr', "de", “pt”, "ar", nk.

data-identity-token

Chaguo. Server-inazalishwa saini kitambulisho ishara.

Msaada wa Spam

Mwongozo wa Ufuatiliaji wa Spa
// Manually notify OpsIQ of a route change (for custom routers)
window.OpsIQ = window.OpsIQ || [];
window.OpsIQ.push(["pageview", {
  url: window.location.href,
  title: document.title,
}]);

Kanuni za CSP

Sheria za CSP kwa widget
script-src 'self' https://your-opsiq-domain.com;
connect-src 'self' https://your-opsiq-domain.com;
frame-src https://your-opsiq-domain.com;
Je, tovuti yangu inapungua?+

Chini ya 15 KB gzipped, mizigo async baada ya maudhui ya ukurasa.

Ninawezaje kubadilisha muonekano?+

Tumia rangi ya data kwa rangi ya msingi. msaada wa mawasiliano CSS Chaguzi za juu.

Developer ya developer

Ukarabati wa vifaa vya ujenzi

Mwongozo wa ufungaji maalum.

Jinsi ya kufanya kazi
Ukarabati wa vifaa vya ujenziJukwaa la kuweka kadi kwa ajili ya WordPress, Shopify Aidha, na Google Tag Manager Kila mtu anasema ambapo kuongeza widget.WP ya WPWordPressKuingiza Plugin, kuingiaTovuti yako ya msingi, salama.Maduka ya ShopShopifyWeka sufuria ya kupikia katikatheme. liquid kabla ya /body.GMT yaTag: Meneja waForodha ya desturi HTML Picha zote na Wizara ya Mambo ya Ndani.
Kuweka maelekezo

WordPress

Kwa mfano:
Ongeza kwenye kurasa zote za A WordPress Tovuti ya.
Nini cha kufanya:

Option 1: Edit theme footer.php, paste snippet before </body>. Option 2: Use "Insert Headers and Footers" plugin > Scripts in Footer. Option 3: Use a child theme footer.php to survive theme updates.

Shopify

Kwa mfano:
Ongeza kwenye yako Shopify ya biashara.
Nini cha kufanya:

Online Store > Themes > Edit Code > Layout > theme.liquid. Paste before </body>. Save.

Kujiandaa / Next. js

Kwa mfano:
Ongeza kwenye programu ya React au Next. js.
Nini cha kufanya:

In Next.js, use next/script in app/layout.tsx: import Script from "next/script"; <Script src="https://your-opsiq.com/widget.php" data-site-key="site_abc" strategy="lazyOnload" />

WHMCS

Kwa mfano:
Ongeza kwenye yako WHMCS eneo la wateja.
Nini cha kufanya:

Setiup > Mipangilio ya Jumla > Maudhui mengine ya Global Footer. Weka snippet. au hariri mguu wako wa template. tpl.

Google Tag Manager

Kwa mfano:
Ongeza kwa GTM.
Nini cha kufanya:

Unda Custom HTML tag, kuweka snippet. Trigger: Kurasa zote.

Developer ya developer

Admin widget katika backend yako (mkataba mmoja, jukwaa lolote)

Kuingilia ya OpsIQ Msaidizi wa admin - mazungumzo ya admin, kikasha cha tiketi na AI Kuandika — ndani ya jopo la admin la jukwaa lako mwenyewe, kwa hivyo timu yako kamwe haitoi zana zao. Kama utambulisho wa mgeni na bandari SSO Hii ni moja ya mikataba ya kawaida ambayo imewekwa katika15 Mstari wa msimbo wa seva ya jukwaa lako - muundo sawa Zendesk, Intercom na matumizi ya lugha kwa ajili ya SSO Hakuna Plugin ya perplatform kusubiri: stack yoyote ambayo inaweza kuhesabu HMAC Unaweza kufanya hivyo leo.

Hatua ya hatua1Mstari wa embed

Kutoka kwa Maeneo ya mbali→Tovuti yako→Kanuni za, nakala ya mstari wa kupakia na uiongeze kwenye kurasa za jopo lako la admin (mguu ni pamoja na, template ya mpangilio, au sanduku la desturi tu la JS):

Mtandao wa 1 unaunganisha
<script async src="https://YOUR-OPSIQ/opsiq/embed/admin_widget.php?site_key=SITE_KEY&identity_token=TOKEN_FROM_STEP_2"></script>

Hatua ya hatua2Kwa hiyo, kwaOpsIQambaye amewekwa katika hali ya utulivu.

Programu yako tu inajua ni admin gani iliyosainiwa - hiyo sio shortcoming, ni mfano wa usalama. seva yako inazalisha ishara ya muda mfupi iliyosainiwa kutoka kikao chako mwenyewe, kama ishara ya utambulisho wa mgeni, iliyosainiwa na siri ya wavuti hiyo:

PHP · Ingia utambulisho wa admin kutoka kikao chako
<?php
$secret  = "opsiq_whsec_your_site_secret";   // Remote Sites → Codes
$payload = json_encode([
    "site_key"      => "SITE_KEY",
    "iat"           => time(),
    "exp"           => time() + 6 * 3600,
    "authenticated" => true,          // REQUIRED, top level — see note below
    "platform"      => "your-platform",
    "admin"    => [
        "id"            => (string)$admin->id,      // from YOUR session
        "name"          => $admin->name,
        "username"      => $admin->username,
        "email"         => $admin->email,
        "role"          => $admin->role,
        "authenticated" => true,
    ],
]);
$payload64 = rtrim(strtr(base64_encode($payload), "+/", "-_"), "=");
$identityToken = $payload64 . "." . hash_hmac("sha256", $payload64, $secret);
// Put $identityToken into the embed line (identity_token=…), or expose it as
// window.OpsIQAdminIdentityToken before the loader script.
Upatikanaji wa admin, moja kwa moja

Kila admin ambaye kuingia kwenye jukwaa yako ni sawa kila mmoja:OpsIQ's per-admin upatikanaji lango kutatua jina la mtumiaji ishara + barua pepe dhidi ya mojaOpsIQWakala (ukurasa wa timu; tumia orodha ya "barua pepe za mechi" za wakala wakati barua pepe za jukwaa zinatofautiana) na hutumia nafasi ya kazi ya wakala huyo, idara na ruhusa za inbox. mwanachama mpya wa wafanyakazi = kuongeza wakala katikaOpsIQHakuna mabadiliko ya lazima.

Shughuli za usafiri wa pamoja

Chochote jukumu kamba ya jukwaa yako inaonyeshwa kwenyeOpsIQkwa ajili ya utekelezaji wa ahadi; mara zote mamlaka hiyo inatokana naOpsIQMheshimiwa Mwenyekiti, kamwe si kwa mujibu wa majukumu ya Tume.

Kwa nini usiulize kuhusu cookies zetu za login?

Browsers kamwe kutuma cookie yako admin kwa asili nyingine - hakuna muuzaji anaweza "kutambua" yako login-domain. Kila bidhaa kubwa kutatua hii kwa njia hiyo: server yako vouches, saini. Hiyo ni mkataba wote.

Hakuna njia ya kushiriki katika tovuti yako mwenyewe

Off ya OpsIQ mwenyeji hakuna hali isiyosainiwa au iliyoshirikiwa: loader anakaa siri mpaka ishara ya admin saini iwasili. Alama = ... thamani katika mzigo wa Codes ni ufunguo wa widget ambao hutambulisha tu tovuti; haiwezi kusaini mtu yeyote ndani.

Kwa kuwa authenticated Bendera - kuweka juu ya ngazi

Bendera hii ni madai ya seva yako kwamba binadamu ameingia, na OpsIQ anakataa ishara yoyote bila hiyo. "authenticated" => true beside site_key/iat/expSio tu ndani ya admin Sasa OpsIQ inakubali katika nafasi yoyote, lakini releases za zamani zinasoma tu kiwango cha juu - na kushindwa ni udanganyifu: orodha ya mazungumzo, historia na haijasoma yote halali wakati kila gumzo linageuka majibu. "Aina ya kuingia inahitajika", ambayo inaonekana kama mdudu kikao na si. Kama unaweza kuona hasa mgawanyiko huo, angalia bendera hii kwanza.

Toni ya usafi

Kuingia kwenye server tu, kamwe katika browserJavaScript- Weka muda mfupi (dakika hadi masaa);OpsIQInakataa ishara zilizokwisha muda mrefu na za baadaye, na saini inafunga ishara kwenye ufunguo wako wa tovuti.

Utekelezaji wa Kumbukumbu

Kwa kuwaWHMCSMfumo huu unafanya kazi moja kwa moja kutoka kwenyeWHMCSadmin kikao; Botble Hotel kiunganishi daraja faili inafanya hivyo kutoka Laravel kikao (op =admin_identity). Wote ni tu mkataba huu katika jukwaa yao dialect - nakala yoyote kusoma karibu na stack yako.

Zero Ukurasa wiring (uchunguzi uliounganishwa na kuunganishwa)

Wakati OpsIQ yako connector maduka utambulisho wako mwisho pointi katika yake admin_identity_probe_url Kuweka, mstari wa mzigo wa PLAIN ni kurasa zako zote za admin zinahitaji: widget inagundua uchunguzi kutoka kwa kontakt, inaita na ishara yako ya msingi ya tovuti + widget, na inathibitisha kila admin moja kwa moja. ukurasa unaweza bado kuzidi na msimbo wako wa eneo la kiungo cha wavuti. data-identity-endpoint Kuwajibika au window.OpsIQAdminIdentityEndpoint.

💡
Siri ya siri ni kwa ajili yako. Katika maeneo ya mbali, tovuti yako, Kanuni, Chaguo 3, Ingia katika wafanyakazi wako, kila mfano tayari una siri ya tovuti hii mwenyewe, hivyo msimbo hufanya kazi kama ilivyozoeleka: hakuna kitu cha kuiga au kusanidi. Mifano kwenye ukurasa huu inaonyesha opsiq_whsec_YOUR_SITE_SECRET Katika kila mfano, kila mmoja ana mtazamo wake. OPSIQ_SITE_SECRET (au mfumo wako mwenyewe kuweka, jina katika maelezo yake) juu ya server kwanza na matumizi kwamba wakati ni kuweka, hivyo unaweza kusonga siri nje ya faili wakati wowote unataka, kwa mfano kwa kuzunguka bila kurekebisha kanuni. njia yoyote file anaendesha kwenye server yako tu: kamwe paste ndani ya ukurasa wa web au kivinjari JavaScript, na kamwe kujitoa kwa repository umma, kwa sababu mtu yeyote mwenye siri unaweza saini katika kama yoyote ya wateja wako au wafanyakazi. WHMCS na Botble haja yoyote ya hii: WHMCS hook inafika na siri kujazwa katika, na Botble kiunganishi jopo hujaza ndani ya daraja.

Mfumo wa jumla, jukwaa kwa jukwaa

Kila mfano huchapisha tag ya Admin Chat tu kwa mwanachama aliyesainiwa katika wafanyakazi, na ishara iliyosainiwa aliongeza, na hujibu urejesho wa widget (?opsiq_identity_refresh=1&role=admin(i) Kwa kuwa {"success":true,"identity_token":"…"} au 401. Remote Tovuti, tovuti yako, Kanuni, Chaguo 3, Kuingia katika wafanyakazi wako prints kanuni hiyo na tovuti yako muhimu na siri kujazwa ndani.

⚠️
Na kwa upande wa pili, ni juu ya safu mbili za safu, na safu ya safu HMAC-SHA256 ya maandishi hayo ya msingi wa 64url. Sio JWT, na JWT imekataliwa. Kitu cha admin kinahitaji id na barua pepe, na exp lazima iwe ndani yake 24 masaa ya.

WHMCS

Nothing to add: the WHMCS hook in Option 1 already signs your logged-in staff into Admin Chat and refreshes the token. Do not paste the Option 3 loader as well.
1

Install the Option 1 hook as includes/hooks/opsiq_tracker.php.

2

Each staff member needs an OpsIQ agent account with the same email (or username): that is how their own permissions apply.

includes/hooks/opsiq_tracker.php
/* WHMCS: no extra code. Option 1 (the All-in-One WHMCS Hook) signs the logged-in
 * admin into Admin Chat on every admin page and answers ?opsiq_identity_refresh=1&role=admin. */

Botble (connector bridge)

Nothing to add: the Botble bridge signs your logged-in admins. Copy the bridge from the Botble connector panel (it arrives with OPSIQ_HOST, OPSIQ_SITE_KEY and OPSIQ_SITE_SECRET filled in), then put its one admin_embed line in Botble's admin Custom JS.
1

In Botble admin → Custom JS, add: <script async src="https://YOUR-BOTBLE-SITE/opsiq-botble-bridge.php?op=admin_embed"></script>

2

Each staff member needs an OpsIQ agent account with the same email (or username): that is how their own permissions apply.

public/opsiq-botble-bridge.php
<!-- Botble admin → Custom JS. The bridge signs the logged-in admin; nothing secret is in the page. -->
<script async src="https://YOUR-BOTBLE-SITE/opsiq-botble-bridge.php?op=admin_embed"></script>

PHP (no dependencies)

1

Save as opsiq-admin-chat.php. This site's signing secret is already filled in, so the code works as pasted. To keep it out of the file, set OPSIQ_SITE_SECRET in the environment on the server instead: that value is used first. Keep this file on the server and never commit it to a public repository.

2

At the very top of every ADMIN page, before any output: require 'opsiq-admin-chat.php'; opsiq_admin_chat_refresh(); and before </body>: <?= opsiq_admin_chat_tag() ?> (it replaces the Option 3 loader).

3

Replace opsiq_admin_chat_user() with your signed-in staff member. Each staff member needs an OpsIQ agent account with the same email (or username): that is how their own permissions apply.

opsiq-admin-chat.php
<?php
/* opsiq-admin-chat.php — sign your logged-in staff into OpsIQ Admin Chat. */

// WHO IS SIGNED IN AS STAFF — replace the body. Return null for anyone who is not staff.
function opsiq_admin_chat_user(): ?array
{
    $u = $_SESSION['admin'] ?? null;    // e.g. ['id' => 3, 'email' => '…', 'username' => '…', 'name' => '…', 'role' => 'Owner']
    return is_array($u) && !empty($u['id']) && !empty($u['email']) ? $u : null;
}

// The admin token is base64url(payload) . '.' . hex HMAC — NOT a JWT.
function opsiq_admin_chat_token(array $u): string
{
    $secret = (string) (getenv('OPSIQ_SITE_SECRET') ?: 'opsiq_whsec_YOUR_SITE_SECRET');   // this site's secret; the environment wins when set
    if ($secret === '') return '';                           // fail closed: no Admin Chat
    $now = time();
    $payload = rtrim(strtr(base64_encode(json_encode([
        'site_key'      => 'YOUR_SITE_KEY',
        'iat'           => $now,
        'exp'           => $now + 3600,                      // at most 24 hours
        'authenticated' => true,
        'platform'      => 'php',
        'admin'         => [
            'id'       => (string) $u['id'],                 // REQUIRED
            'email'    => (string) $u['email'],              // REQUIRED
            'username' => (string) ($u['username'] ?? ''),
            'name'     => (string) ($u['name'] ?? ''),
            'role'     => (string) ($u['role'] ?? ''),
        ],
    ], JSON_UNESCAPED_SLASHES)), '+/', '-_'), '=');
    return $payload . '.' . hash_hmac('sha256', $payload, $secret);
}

// Call at the top of every admin page, before any output.
function opsiq_admin_chat_refresh(): void
{
    if (empty($_GET['opsiq_identity_refresh'])) return;
    header('Content-Type: application/json; charset=utf-8');
    header('Cache-Control: no-store');
    $u = opsiq_admin_chat_user();
    $t = $u ? opsiq_admin_chat_token($u) : '';
    if ($t === '') { http_response_code(401); echo json_encode(['success' => false, 'login_required' => true]); exit; }
    echo json_encode(['success' => true, 'role' => 'admin', 'identity_token' => $t]);
    exit;
}

// Print before </body> on admin pages. Prints nothing for anyone who is not staff.
function opsiq_admin_chat_tag(): string
{
    $u = opsiq_admin_chat_user();
    $t = $u ? opsiq_admin_chat_token($u) : '';
    if ($t === '') return '';
    $src = 'https://YOUR-OPSIQ/opsiq/embed/admin_widget.php?site_key=YOUR_SITE_KEY&identity_token=' . rawurlencode($t);
    return '<script async src="' . htmlspecialchars($src, ENT_QUOTES) . '" data-opsiq-widget="admin-chat"></script>';
}

Laravel

1

This site's signing secret is already filled in, so the code works as pasted. To keep it out of the file, set OPSIQ_SITE_SECRET=… in .env with 'opsiq' => ['site_secret' => env('OPSIQ_SITE_SECRET')] in config/services.php on the server instead: that value is used first. Keep this file on the server and never commit it to a public repository.

2

Save the class as app/Support/OpsiqAdminChat.php; adjust isStaff() to your admin guard or role. Add the refresh middleware from the bottom of the code to your admin routes.

3

In your admin Blade layout before </body>: {!! \App\Support\OpsiqAdminChat::tag() !!}. Each staff member needs an OpsIQ agent account with the same email (or username): that is how their own permissions apply.

app/Support/OpsiqAdminChat.php
<?php
// app/Support/OpsiqAdminChat.php — no packages needed.
namespace App\Support;

final class OpsiqAdminChat
{
    /** WHO IS STAFF — adjust to your admin guard, role or gate. */
    private static function staff()
    {
        $user = auth('web')->user();                    // or auth('admin')->user()
        return ($user && $user->can('access-admin')) ? $user : null;
    }

    /** The admin token is base64url(payload) . '.' . hex HMAC — NOT a JWT. */
    public static function token(): string
    {
        $user = self::staff();
        $secret = (string) (config('services.opsiq.site_secret') ?: 'opsiq_whsec_YOUR_SITE_SECRET');   // this site's secret; config wins when set
        if (!$user || $secret === '') return '';
        $now = time();
        $payload = rtrim(strtr(base64_encode(json_encode([
            'site_key'      => 'YOUR_SITE_KEY',
            'iat'           => $now,
            'exp'           => $now + 3600,
            'authenticated' => true,
            'platform'      => 'laravel',
            'admin'         => [
                'id'       => (string) $user->id,           // REQUIRED
                'email'    => (string) $user->email,        // REQUIRED
                'username' => (string) ($user->username ?? $user->email),
                'name'     => (string) $user->name,
                'role'     => 'Admin',
            ],
        ], JSON_UNESCAPED_SLASHES)), '+/', '-_'), '=');
        return $payload . '.' . hash_hmac('sha256', $payload, $secret);
    }

    /** For the admin Blade layout, before </body>. Prints nothing for non-staff. */
    public static function tag(): string
    {
        $t = self::token();
        if ($t === '') return '';
        return '<script async src="' . e('https://YOUR-OPSIQ/opsiq/embed/admin_widget.php?site_key=YOUR_SITE_KEY&identity_token=' . rawurlencode($t)) . '" data-opsiq-widget="admin-chat"></script>';
    }
}

/* Refresh — Admin Chat asks ?opsiq_identity_refresh=1&role=admin on the admin page it is on.
 * app/Http/Middleware/OpsiqAdminChatRefresh.php, added to your admin route group:
 *
 *   public function handle($request, \Closure $next) {
 *       if (!$request->query('opsiq_identity_refresh')) return $next($request);
 *       $t = \App\Support\OpsiqAdminChat::token();
 *       return $t === ''
 *           ? response()->json(['success' => false, 'login_required' => true], 401)->header('Cache-Control', 'no-store')
 *           : response()->json(['success' => true, 'role' => 'admin', 'identity_token' => $t])->header('Cache-Control', 'no-store');
 *   }
 */

WordPress / WooCommerce

1

This site's signing secret is already filled in, so the code works as pasted. To keep it out of the file, add define('OPSIQ_SITE_SECRET', '…'); to wp-config.php instead: that value is used first. Keep this file on the server and never commit it to a public repository.

2

Paste into your theme's functions.php or a small plugin. It shows Admin Chat inside wp-admin to users who can manage_options; change the capability to suit your team.

3

Each staff member needs an OpsIQ agent account with the same email (or username): that is how their own permissions apply.

functions.php
/* functions.php or a small plugin — OpsIQ Admin Chat inside wp-admin. */

if (!defined('OPSIQ_SITE_SECRET')) define('OPSIQ_SITE_SECRET', 'opsiq_whsec_YOUR_SITE_SECRET');   // this site's secret; wp-config.php wins when set

function opsiq_admin_chat_token(): string {
    if (!is_user_logged_in() || !current_user_can('manage_options')) return '';     // who counts as staff
    if (!defined('OPSIQ_SITE_SECRET') || OPSIQ_SITE_SECRET === '') return '';
    $u   = wp_get_current_user();
    $now = time();
    // The admin token is base64url(payload) . '.' . hex HMAC — NOT a JWT.
    $payload = rtrim(strtr(base64_encode(wp_json_encode([
        'site_key'      => 'YOUR_SITE_KEY',
        'iat'           => $now,
        'exp'           => $now + 3600,
        'authenticated' => true,
        'platform'      => 'wordpress',
        'admin'         => [
            'id'       => (string) $u->ID,                   // REQUIRED
            'email'    => (string) $u->user_email,           // REQUIRED
            'username' => (string) $u->user_login,
            'name'     => (string) $u->display_name,
            'role'     => (string) (reset($u->roles) ?: 'administrator'),
        ],
    ])), '+/', '-_'), '=');
    return $payload . '.' . hash_hmac('sha256', $payload, OPSIQ_SITE_SECRET);
}

// Refresh: Admin Chat asks ?opsiq_identity_refresh=1&role=admin on the admin page it is on.
add_action('admin_init', function () {
    if (empty($_GET['opsiq_identity_refresh'])) return;
    nocache_headers();
    $t = opsiq_admin_chat_token();
    if ($t === '') wp_send_json(['success' => false, 'login_required' => true], 401);
    wp_send_json(['success' => true, 'role' => 'admin', 'identity_token' => $t]);
});

// The loader, on every wp-admin page, for staff only.
add_action('admin_footer', function () {
    $t = opsiq_admin_chat_token();
    if ($t === '') return;
    echo '<script async src="' . esc_url('https://YOUR-OPSIQ/opsiq/embed/admin_widget.php?site_key=YOUR_SITE_KEY&identity_token=' . rawurlencode($t)) . '" data-opsiq-widget="admin-chat"></script>';
});

Node.js / Express

1

No packages needed. This site's signing secret is already filled in, so the code works as pasted. To keep it out of the file, set OPSIQ_SITE_SECRET in the environment on the server instead: that value is used first. Keep this file on the server and never commit it to a public repository.

2

adminRouter.use(opsiqAdminChat) on your ADMIN routes, after your session middleware; adjust isStaff(). It answers the refresh and sets res.locals.opsiqAdminChatTag.

3

Print res.locals.opsiqAdminChatTag (unescaped) before </body> in your admin layout. Each staff member needs an OpsIQ agent account with the same email (or username): that is how their own permissions apply.

opsiq-admin-chat.js
// opsiq-admin-chat.js — no packages needed.
const crypto = require("crypto");

const isStaff = (user) => !!(user && user.isAdmin);        // WHO IS STAFF — adjust

// The admin token is base64url(payload) + "." + hex HMAC — NOT a JWT.
function opsiqAdminChatToken(user) {
  const secret = process.env.OPSIQ_SITE_SECRET || "opsiq_whsec_YOUR_SITE_SECRET";   // this site's secret; the environment wins when set
  if (!isStaff(user) || !secret) return "";
  const now = Math.floor(Date.now() / 1000);
  const payload = Buffer.from(JSON.stringify({
    site_key: "YOUR_SITE_KEY",
    iat: now,
    exp: now + 3600,                                        // at most 24 hours
    authenticated: true,
    platform: "node",
    admin: { id: String(user.id), email: user.email, username: user.username || user.email, name: user.name || "", role: user.role || "Admin" },  // id + email REQUIRED
  })).toString("base64url");
  return payload + "." + crypto.createHmac("sha256", secret).update(payload).digest("hex");
}

// adminRouter.use(opsiqAdminChat)
function opsiqAdminChat(req, res, next) {
  const token = opsiqAdminChatToken(req.user);
  if (req.query.opsiq_identity_refresh) {
    res.set("Cache-Control", "no-store");
    return token
      ? res.json({ success: true, role: "admin", identity_token: token })
      : res.status(401).json({ success: false, login_required: true });
  }
  res.locals.opsiqAdminChatTag = token
    ? '<script async src="' + ("https://YOUR-OPSIQ/opsiq/embed/admin_widget.php?site_key=YOUR_SITE_KEY&identity_token=" + encodeURIComponent(token)).replace(/"/g, """) + '" data-opsiq-widget="admin-chat"></script>'
    : "";
  next();
}

module.exports = { opsiqAdminChat };

Python (Flask)

1

No packages beyond Flask and flask-login. This site's signing secret is already filled in, so the code works as pasted. To keep it out of the file, set OPSIQ_SITE_SECRET in the environment on the server instead: that value is used first. Keep this file on the server and never commit it to a public repository.

2

Call init_opsiq_admin_chat(app) where you create the app, and adjust is_staff().

3

In your admin base template before </body>: {{ opsiq_admin_chat_tag }}. Each staff member needs an OpsIQ agent account with the same email (or username): that is how their own permissions apply.

opsiq_admin_chat.py
# opsiq_admin_chat.py — Flask + flask-login, no other packages.
import base64, hashlib, hmac, json, os, time, urllib.parse
from flask import request, jsonify
from flask_login import current_user
from markupsafe import Markup, escape

def is_staff(user):                                           # WHO IS STAFF — adjust
    return user.is_authenticated and getattr(user, "is_admin", False)

def opsiq_admin_chat_token():
    secret = os.environ.get("OPSIQ_SITE_SECRET") or "opsiq_whsec_YOUR_SITE_SECRET"   # this site's secret; the environment wins when set
    if not secret or not is_staff(current_user):
        return ""
    now = int(time.time())
    # The admin token is base64url(payload) + "." + hex HMAC — NOT a JWT.
    payload = base64.urlsafe_b64encode(json.dumps({
        "site_key": "YOUR_SITE_KEY", "iat": now, "exp": now + 3600,
        "authenticated": True, "platform": "python",
        "admin": {"id": str(current_user.id), "email": current_user.email,           # REQUIRED
                  "username": getattr(current_user, "username", current_user.email),
                  "name": getattr(current_user, "name", ""), "role": "Admin"},
    }, separators=(",", ":")).encode()).decode().rstrip("=")
    return payload + "." + hmac.new(secret.encode(), payload.encode(), hashlib.sha256).hexdigest()

def init_opsiq_admin_chat(app):
    @app.before_request
    def _opsiq_admin_refresh():
        if request.args.get("opsiq_identity_refresh"):
            t = opsiq_admin_chat_token()
            if t:
                resp = jsonify({"success": True, "role": "admin", "identity_token": t})
            else:
                resp = jsonify({"success": False, "login_required": True})
                resp.status_code = 401
            resp.headers["Cache-Control"] = "no-store"
            return resp

    @app.context_processor
    def _opsiq_admin_tag():
        t = opsiq_admin_chat_token()
        if not t:
            return {"opsiq_admin_chat_tag": ""}
        src = "https://YOUR-OPSIQ/opsiq/embed/admin_widget.php?site_key=YOUR_SITE_KEY&identity_token=" + urllib.parse.quote(t, safe="")
        return {"opsiq_admin_chat_tag": Markup('<script async src="%s" data-opsiq-widget="admin-chat"></script>' % escape(src))}

Django

1

No packages needed. This site's signing secret is already filled in, so the code works as pasted. To keep it out of the file, set OPSIQ_SITE_SECRET in settings.py (for example os.environ["OPSIQ_SITE_SECRET"]) on the server instead: that value is used first. Keep this file on the server and never commit it to a public repository.

2

Add "yourapp.opsiq_admin_chat.OpsiqAdminChatMiddleware" to MIDDLEWARE (after AuthenticationMiddleware) and "yourapp.opsiq_admin_chat.opsiq_admin_chat" to TEMPLATES context_processors. Staff = user.is_staff.

3

In your admin base template before </body>: {{ opsiq_admin_chat_tag }}. Each staff member needs an OpsIQ agent account with the same email (or username): that is how their own permissions apply.

opsiq_admin_chat.py
# yourapp/opsiq_admin_chat.py — no packages needed.
import base64, hashlib, hmac, json, time, urllib.parse
from django.conf import settings
from django.http import JsonResponse
from django.utils.html import format_html

def opsiq_admin_chat_token(user):
    secret = getattr(settings, "OPSIQ_SITE_SECRET", "") or "opsiq_whsec_YOUR_SITE_SECRET"   # this site's secret; settings win when set
    if not secret or not user.is_authenticated or not user.is_staff:
        return ""
    now = int(time.time())
    # The admin token is base64url(payload) + "." + hex HMAC — NOT a JWT.
    payload = base64.urlsafe_b64encode(json.dumps({
        "site_key": "YOUR_SITE_KEY", "iat": now, "exp": now + 3600,
        "authenticated": True, "platform": "django",
        "admin": {"id": str(user.pk), "email": user.email, "username": user.get_username(),   # id + email REQUIRED
                  "name": user.get_full_name(), "role": "Superuser" if user.is_superuser else "Staff"},
    }, separators=(",", ":")).encode()).decode().rstrip("=")
    return payload + "." + hmac.new(secret.encode(), payload.encode(), hashlib.sha256).hexdigest()

class OpsiqAdminChatMiddleware:
    def __init__(self, get_response):
        self.get_response = get_response
    def __call__(self, request):
        if request.GET.get("opsiq_identity_refresh"):
            t = opsiq_admin_chat_token(request.user)
            resp = (JsonResponse({"success": True, "role": "admin", "identity_token": t}) if t
                    else JsonResponse({"success": False, "login_required": True}, status=401))
            resp["Cache-Control"] = "no-store"
            return resp
        return self.get_response(request)

def opsiq_admin_chat(request):
    t = opsiq_admin_chat_token(request.user)
    if not t:
        return {"opsiq_admin_chat_tag": ""}
    src = "https://YOUR-OPSIQ/opsiq/embed/admin_widget.php?site_key=YOUR_SITE_KEY&identity_token=" + urllib.parse.quote(t, safe="")
    return {"opsiq_admin_chat_tag": format_html('<script async src="{}" data-opsiq-widget="admin-chat"></script>', src)}

.NET / C#

1

No packages needed. This site's signing secret is already filled in, so the code works as pasted. To keep it out of the file, set OpsIQ:SiteSecret (user-secrets, the OpsIQ__SiteSecret environment variable or Key Vault) on the server instead: that value is used first. Keep this file on the server and never commit it to a public repository.

2

In Program.cs after app.UseAuthentication(): app.Use(OpsiqAdminChat.Refresh); staff = users in the "Admin" role (adjust).

3

In your admin layout before </body>: @Html.Raw(OpsiqAdminChat.Tag(Context)). Each staff member needs an OpsIQ agent account with the same email (or username): that is how their own permissions apply.

OpsiqAdminChat.cs
// OpsiqAdminChat.cs — no packages needed.
using System.Net;
using System.Security.Claims;
using System.Security.Cryptography;
using System.Text;
using System.Text.Json;

public static class OpsiqAdminChat
{
    // The admin token is base64url(payload) + "." + hex HMAC — NOT a JWT.
    public static string Token(HttpContext ctx)
    {
        var secret = ctx.RequestServices.GetRequiredService<IConfiguration>()["OpsIQ:SiteSecret"];
        if (string.IsNullOrEmpty(secret)) secret = "opsiq_whsec_YOUR_SITE_SECRET";   // this site's secret; configuration wins when set
        if (string.IsNullOrEmpty(secret) || !ctx.User.IsInRole("Admin")) return "";      // WHO IS STAFF — adjust
        var now = DateTimeOffset.UtcNow.ToUnixTimeSeconds();
        var json = JsonSerializer.Serialize(new Dictionary<string, object> {
            ["site_key"] = "YOUR_SITE_KEY", ["iat"] = now, ["exp"] = now + 3600,
            ["authenticated"] = true, ["platform"] = "dotnet",
            ["admin"] = new Dictionary<string, string> {
                ["id"] = ctx.User.FindFirstValue(ClaimTypes.NameIdentifier) ?? "",      // REQUIRED
                ["email"] = ctx.User.FindFirstValue(ClaimTypes.Email) ?? "",            // REQUIRED
                ["username"] = ctx.User.Identity?.Name ?? "", ["name"] = ctx.User.Identity?.Name ?? "", ["role"] = "Admin" },
        });
        var payload = Convert.ToBase64String(Encoding.UTF8.GetBytes(json)).TrimEnd('=').Replace('+', '-').Replace('/', '_');
        using var h = new HMACSHA256(Encoding.UTF8.GetBytes(secret));
        return payload + "." + Convert.ToHexString(h.ComputeHash(Encoding.UTF8.GetBytes(payload))).ToLowerInvariant();
    }

    // app.Use(OpsiqAdminChat.Refresh)
    public static async Task Refresh(HttpContext ctx, Func<Task> next)
    {
        if (string.IsNullOrEmpty(ctx.Request.Query["opsiq_identity_refresh"])) { await next(); return; }
        ctx.Response.Headers["Cache-Control"] = "no-store";
        var t = Token(ctx);
        if (t == "") { ctx.Response.StatusCode = 401; await ctx.Response.WriteAsJsonAsync(new { success = false, login_required = true }); return; }
        await ctx.Response.WriteAsJsonAsync(new { success = true, role = "admin", identity_token = t });
    }

    public static string Tag(HttpContext ctx)
    {
        var t = Token(ctx);
        if (t == "") return "";
        return "<script async src=\"" + WebUtility.HtmlEncode("https://YOUR-OPSIQ/opsiq/embed/admin_widget.php?site_key=YOUR_SITE_KEY&identity_token=" + Uri.EscapeDataString(t)) + "\" data-opsiq-widget=\"admin-chat\"></script>";
    }
}

Ruby on Rails

1

No gems needed. This site's signing secret is already filled in, so the code works as pasted. To keep it out of the file, set OPSIQ_SITE_SECRET in the environment on the server instead: that value is used first. Keep this file on the server and never commit it to a public repository.

2

include OpsiqAdminChat in your admin base controller; adjust opsiq_staff.

3

In your admin layout before </body>: <%= opsiq_admin_chat_tag %>. Each staff member needs an OpsIQ agent account with the same email (or username): that is how their own permissions apply.

app/controllers/concerns/opsiq_admin_chat.rb
# app/controllers/concerns/opsiq_admin_chat.rb — no gems needed.
require "base64"
require "cgi"
require "json"
require "openssl"

module OpsiqAdminChat
  extend ActiveSupport::Concern

  included do
    before_action :opsiq_admin_identity_refresh
    helper_method :opsiq_admin_chat_tag
  end

  private

  def opsiq_staff                                        # WHO IS STAFF — adjust
    current_user if respond_to?(:current_user, true) && current_user&.try(:admin?)
  end

  # The admin token is base64url(payload) + "." + hex HMAC — NOT a JWT.
  def opsiq_admin_chat_token
    secret = ENV["OPSIQ_SITE_SECRET"].presence || "opsiq_whsec_YOUR_SITE_SECRET"   # this site's secret; the environment wins when set
    staff = opsiq_staff
    return "" if secret.blank? || staff.nil?
    now = Time.now.to_i
    payload = Base64.urlsafe_encode64({
      site_key: "YOUR_SITE_KEY", iat: now, exp: now + 3600,
      authenticated: true, platform: "rails",
      admin: { id: staff.id.to_s, email: staff.email,              # REQUIRED
               username: staff.try(:username).to_s, name: staff.try(:name).to_s, role: "Admin" }
    }.to_json, padding: false)
    payload + "." + OpenSSL::HMAC.hexdigest("SHA256", secret, payload)
  end

  def opsiq_admin_identity_refresh
    return unless params[:opsiq_identity_refresh].present?
    response.headers["Cache-Control"] = "no-store"
    t = opsiq_admin_chat_token
    return render(json: { success: false, login_required: true }, status: :unauthorized) if t.blank?
    render json: { success: true, role: "admin", identity_token: t }
  end

  def opsiq_admin_chat_tag
    t = opsiq_admin_chat_token
    return "" if t.blank?
    helpers.tag.script(nil, async: true, src: "https://YOUR-OPSIQ/opsiq/embed/admin_widget.php?site_key=YOUR_SITE_KEY&identity_token=#{CGI.escape(t)}", data: { opsiq_widget: "admin-chat" })
  end
end

Java (Spring Boot)

1

No libraries needed. This site's signing secret is already filled in, so the code works as pasted. To keep it out of the file, set opsiq.site.secret (for example from OPSIQ_SITE_SECRET) on the server instead: that value is used first. Keep this file on the server and never commit it to a public repository.

2

Replace staff() with your admin lookup. The filter answers the refresh; @ControllerAdvice exposes opsiqAdminChatTag to views.

3

Admin Thymeleaf layout before </body>: <th:block th:utext="${opsiqAdminChatTag}"/>. Each staff member needs an OpsIQ agent account with the same email (or username): that is how their own permissions apply.

OpsiqAdminChat.java
// OpsiqAdminChat.java — no libraries needed.
import jakarta.servlet.*;
import jakarta.servlet.http.*;
import java.io.IOException;
import java.net.URLEncoder;
import java.nio.charset.StandardCharsets;
import java.util.*;
import javax.crypto.Mac;
import javax.crypto.spec.SecretKeySpec;
import com.fasterxml.jackson.databind.ObjectMapper;
import org.springframework.beans.factory.annotation.Value;
import org.springframework.stereotype.Component;
import org.springframework.web.bind.annotation.ControllerAdvice;
import org.springframework.web.bind.annotation.ModelAttribute;
import org.springframework.web.util.HtmlUtils;

@Component
@ControllerAdvice
public class OpsiqAdminChat implements Filter {
    @Value("${opsiq.site.secret:opsiq_whsec_YOUR_SITE_SECRET}")   // this site's secret; opsiq.site.secret wins when set
    private String secret;

    /** WHO IS STAFF — replace: id, email, username, name, role. Null for anyone else. */
    private Map<String, String> staff(HttpServletRequest req) {
        if (req.getUserPrincipal() == null || !req.isUserInRole("ADMIN")) return null;
        String n = req.getUserPrincipal().getName();
        return Map.of("id", n, "email", n, "username", n, "name", n, "role", "Admin");
    }

    // The admin token is base64url(payload) + "." + hex HMAC — NOT a JWT.
    String token(HttpServletRequest req) {
        Map<String, String> u = staff(req);
        if (u == null || secret.isEmpty()) return "";
        try {
            long now = System.currentTimeMillis() / 1000;
            Map<String, Object> claims = new LinkedHashMap<>();
            claims.put("site_key", "YOUR_SITE_KEY"); claims.put("iat", now); claims.put("exp", now + 3600);
            claims.put("authenticated", true); claims.put("platform", "java"); claims.put("admin", u);   // id + email REQUIRED
            String payload = Base64.getUrlEncoder().withoutPadding().encodeToString(new ObjectMapper().writeValueAsBytes(claims));
            Mac mac = Mac.getInstance("HmacSHA256");
            mac.init(new SecretKeySpec(secret.getBytes(StandardCharsets.UTF_8), "HmacSHA256"));
            return payload + "." + HexFormat.of().formatHex(mac.doFinal(payload.getBytes(StandardCharsets.UTF_8)));
        } catch (Exception e) { return ""; }
    }

    @Override // Admin Chat refreshing on the admin page it is on
    public void doFilter(ServletRequest request, ServletResponse response, FilterChain chain) throws IOException, ServletException {
        HttpServletRequest req = (HttpServletRequest) request;
        if (req.getParameter("opsiq_identity_refresh") == null) { chain.doFilter(request, response); return; }
        HttpServletResponse res = (HttpServletResponse) response;
        res.setHeader("Cache-Control", "no-store");
        res.setContentType("application/json");
        String t = token(req);
        if (t.isEmpty()) { res.setStatus(401); res.getWriter().write("{\"success\":false,\"login_required\":true}"); return; }
        res.getWriter().write("{\"success\":true,\"role\":\"admin\",\"identity_token\":\"" + t + "\"}");
    }

    @ModelAttribute("opsiqAdminChatTag")
    public String tag(HttpServletRequest req) {
        String t = token(req);
        if (t.isEmpty()) return "";
        String src = "https://YOUR-OPSIQ/opsiq/embed/admin_widget.php?site_key=YOUR_SITE_KEY&identity_token=" + URLEncoder.encode(t, StandardCharsets.UTF_8);
        return "<script async src=\"" + HtmlUtils.htmlEscape(src) + "\" data-opsiq-widget=\"admin-chat\"></script>";
    }
}

Go

1

No modules needed. This site's signing secret is already filled in, so the code works as pasted. To keep it out of the file, set OPSIQ_SITE_SECRET in the environment on the server instead: that value is used first. Keep this file on the server and never commit it to a public repository.

2

Replace staff() with your session lookup and wrap your admin router: OpsiqAdminChatRefresh(adminMux).

3

Pass OpsiqAdminChatTag(r) to your admin layout and print it before </body>. Each staff member needs an OpsIQ agent account with the same email (or username): that is how their own permissions apply.

opsiq_admin_chat.go
// opsiq_admin_chat.go — standard library only.
package main

import (
    "crypto/hmac"
    "crypto/sha256"
    "encoding/base64"
    "encoding/hex"
    "encoding/json"
    "html"
    "html/template"
    "net/http"
    "net/url"
    "os"
    "time"
)

type OpsiqStaff struct{ ID, Email, Username, Name, Role string }

// WHO IS STAFF — replace with your session lookup. Return nil for anyone who is not staff.
func staff(r *http.Request) *OpsiqStaff { return nil }

// The admin token is base64url(payload) + "." + hex HMAC — NOT a JWT.
func opsiqAdminChatToken(r *http.Request) string {
    u, secret := staff(r), os.Getenv("OPSIQ_SITE_SECRET")
    if secret == "" {
        secret = "opsiq_whsec_YOUR_SITE_SECRET" // this site's secret; the environment wins when set
    }
    if u == nil || secret == "" {
        return ""
    }
    now := time.Now().Unix()
    body, _ := json.Marshal(map[string]any{
        "site_key": "YOUR_SITE_KEY", "iat": now, "exp": now + 3600,
        "authenticated": true, "platform": "go",
        "admin": map[string]string{"id": u.ID, "email": u.Email, "username": u.Username, "name": u.Name, "role": u.Role}, // id + email REQUIRED
    })
    payload := base64.RawURLEncoding.EncodeToString(body)
    mac := hmac.New(sha256.New, []byte(secret))
    mac.Write([]byte(payload))
    return payload + "." + hex.EncodeToString(mac.Sum(nil))
}

// OpsiqAdminChatRefresh answers Admin Chat's ?opsiq_identity_refresh=1&role=admin.
func OpsiqAdminChatRefresh(next http.Handler) http.Handler {
    return http.HandlerFunc(func(w http.ResponseWriter, r *http.Request) {
        if r.URL.Query().Get("opsiq_identity_refresh") == "" {
            next.ServeHTTP(w, r)
            return
        }
        w.Header().Set("Cache-Control", "no-store")
        w.Header().Set("Content-Type", "application/json")
        if t := opsiqAdminChatToken(r); t != "" {
            json.NewEncoder(w).Encode(map[string]any{"success": true, "role": "admin", "identity_token": t})
            return
        }
        w.WriteHeader(http.StatusUnauthorized)
        json.NewEncoder(w).Encode(map[string]any{"success": false, "login_required": true})
    })
}

// OpsiqAdminChatTag prints the loader for staff only.
func OpsiqAdminChatTag(r *http.Request) template.HTML {
    t := opsiqAdminChatToken(r)
    if t == "" {
        return ""
    }
    src := "https://YOUR-OPSIQ/opsiq/embed/admin_widget.php?site_key=YOUR_SITE_KEY&identity_token=" + url.QueryEscape(t)
    return template.HTML(`<script async src="` + html.EscapeString(src) + `" data-opsiq-widget="admin-chat"></script>`)
}

Utekelezaji wa mwisho wa utambulisho kwenye Laravel (maelezo yahard-won)

Ikiwa jukwaa lako ni Laravel (Botble, Bagisto, programu za desturi) na mwisho wako ni faili ya kawaida ambayo inasimamia mfumo wa kusoma admin-in, maalum tatu zitakuokoa masaa - kila moja ilizalisha kushindwa kwa uzalishaji halisi kabla ya kujifunza:

Kusubiri kabla ya bootstrap

Watoa huduma wako wanaweza kutatua request kutoka chombo wakati boot. lifecycle ya Laravel mwenyewe kumfunga ombi alitekwa kitu cha kwanza ndani Kernel::handle() Angalia amri hii: $app->instance('request', Request::capture()) Kabla ya kabla ya $kernel->bootstrap()Au unaweza kupata “Hakuna haja ya kuwa na nidhamu..

kikao-cookie kiambishi ni HMAC-keyed

Laravel ya kisasa inarekebisha maadili ya kidakuzi na HMAC iliyohesabiwa na KEY APP (CookieValuePrefix• Kuwa wazi sha1(name."v2") Kamwe hawezi kufanya hivyo, kwa sababu ya CookieValuePrefix::validate($name, $decrypted, $keys)^ Au “mfumo wa miundo” (40 hex chars + | katika nafasi 40). Waambie: id kikao mrefu kuliko 40 herufi (81 = prefix bado imeunganishwa) na kikao kwamba mizigo na tu _token ndani yake.

Ambapo ni muhimu kuishi

auth stamp ya kwamba login_<guard>_<sha1(guard class)> Kwa ajili ya default mtandao ulinzi: 'login_web_' . sha1(Illuminate\Auth\SessionGuard::class)Scan kwa yoyote login_* Ni muhimu kama kurudi kwa walinzi wa kawaida.

Kufukuzwa kama vile daraja

Meli ya A debug=1 mode kwamba majina ya kushindwa Hatua na ubaguzi - kukamata kipofu wote alifanya kupelekwa kuishi undiagnosable. daraja Botble (kutoka v1.0.7) ni kumbukumbu: alama za hatua katika kernel /bind/bootstrap / decrypt /session / auth / db.

Laravel · Mwisho wa utambulisho kamili (copy, kuweka mara mbili, kufanyika)
<?php
/* identity endpoint · LARAVEL (Botble, Bagisto, any Laravel admin)
 * Drop this in your PUBLIC web root, e.g. /opsiq-identity.php
 * Answers: {"success":true,"authenticated":true,"admin":{...},"identity_token":"..."} */
define("OPSIQ_SITE_KEY", "SITE_KEY");
define("OPSIQ_SITE_SECRET", "opsiq_whsec_your_site_secret");   // Remote Sites → Codes

header("Content-Type: application/json");
$step = "boot";
try {
    require __DIR__ . "/../vendor/autoload.php";
    $app = require_once __DIR__ . "/../bootstrap/app.php";

    $step = "bind";
    // ORDER MATTERS: bind the request BEFORE bootstrapping, or providers that
    // resolve "request" during boot throw "Target class [request] does not exist".
    $request = Illuminate\Http\Request::capture();
    $app->instance("request", $request);

    $step = "bootstrap";
    $kernel = $app->make(Illuminate\Contracts\Http\Kernel::class);
    $kernel->bootstrap();

    $step = "session";
    $app["session"]->driver()->setId($request->cookie(config("session.cookie")));
    $app["session"]->driver()->start();

    $step = "auth";
    $user = auth()->guard("web")->user();   // use YOUR admin guard name
    if (!$user) {
        echo json_encode(["success" => false, "authenticated" => false, "error" => "no admin session"]);
        exit;
    }

    $step = "sign";
    $admin = [
        "id"            => (string)$user->id,
        "name"          => (string)($user->name ?? $user->username),
        "username"      => (string)($user->username ?? $user->email),
        "email"         => (string)$user->email,
        "role"          => (string)optional($user->roles->first())->name,
        "authenticated" => true,
    ];
    $payload = json_encode([
        "site_key"      => OPSIQ_SITE_KEY,
        "iat"           => time(),
        "exp"           => time() + 6 * 3600,
        "authenticated" => true,          // TOP LEVEL — required
        "platform"      => "laravel",
        "admin"         => $admin,
    ], JSON_UNESCAPED_SLASHES);
    $p64   = rtrim(strtr(base64_encode($payload), "+/", "-_"), "=");
    $token = $p64 . "." . hash_hmac("sha256", $p64, OPSIQ_SITE_SECRET);

    echo json_encode(["success" => true, "authenticated" => true,
                      "admin" => $admin, "identity_token" => $token]);
} catch (\Throwable $e) {
    // debug=1 names the failing STEP — never ship a blind catch-all
    $err = ($_GET["debug"] ?? "") === "1"
        ? get_class($e) . " at [" . $step . "]: " . $e->getMessage()
        : "identity unavailable";
    echo json_encode(["success" => false, "authenticated" => false, "error" => $err]);
}

Mwisho wa mstari huo kwenye mistari mingine

Ni "nani aliyeingia?" mabadiliko ya mstari - kizuizi cha kutia saini ni sawa kila mahali. Ingia kwenye seva, kamwe katika JavaScript.

WordPress · WHMCS· Symfony · PHP wazi - kubadilisha kuangalia, kuweka saini
<?php
/* The ONE helper every platform shares. Keep it verbatim. */
function opsiq_identity_token(array $admin, string $siteKey, string $secret, string $platform): string {
    $payload = json_encode([
        "site_key"      => $siteKey,
        "iat"           => time(),
        "exp"           => time() + 6 * 3600,
        "authenticated" => true,          // TOP LEVEL — OpsIQ refuses the token without it
        "platform"      => $platform,
        "admin"         => $admin + ["authenticated" => true],
    ], JSON_UNESCAPED_SLASHES);
    $p64 = rtrim(strtr(base64_encode($payload), "+/", "-_"), "=");
    return $p64 . "." . hash_hmac("sha256", $p64, $secret);
}

/* ── WORDPRESS ─────────────────────────────────────────────────────────── */
require_once ABSPATH . "wp-load.php";
if (!current_user_can("manage_options")) { /* not an admin → refuse */ }
$u = wp_get_current_user();
$admin = ["id" => (string)$u->ID, "name" => $u->display_name,
          "username" => $u->user_login, "email" => $u->user_email,
          "role" => implode(",", $u->roles)];

/* ── WHMCS (inside an addon/hook, admin area) ──────────────────────────── */
$aid = (int)($_SESSION["adminid"] ?? 0);
if ($aid <= 0) { /* not an admin → refuse */ }
$row = Capsule::table("tbladmins")->where("id", $aid)->first();
$admin = ["id" => (string)$row->id, "name" => trim($row->firstname . " " . $row->lastname),
          "username" => $row->username, "email" => $row->email, "role" => "administrator"];

/* ── SYMFONY ───────────────────────────────────────────────────────────── */
$u = $security->getUser();                    // Symfony\Bundle\SecurityBundle\Security
if (!$u) { /* not an admin → refuse */ }
$admin = ["id" => (string)$u->getId(), "name" => $u->getName(),
          "username" => $u->getUserIdentifier(), "email" => $u->getEmail(),
          "role" => implode(",", $u->getRoles())];

/* ── PLAIN PHP / your own app ──────────────────────────────────────────── */
session_start();
if (empty($_SESSION["admin_id"])) { /* not an admin → refuse */ }
$admin = ["id" => (string)$_SESSION["admin_id"], "name" => $_SESSION["admin_name"] ?? "",
          "username" => $_SESSION["admin_username"] ?? "", "email" => $_SESSION["admin_email"] ?? "",
          "role" => $_SESSION["admin_role"] ?? ""];

/* ── then, on EVERY stack ──────────────────────────────────────────────── */
$token = opsiq_identity_token($admin, "SITE_KEY", "opsiq_whsec_your_site_secret", "wordpress");
echo json_encode(["success" => true, "authenticated" => true,
                  "admin" => $admin, "identity_token" => $token]);

Ikiwa haifanyi kazi - tambua katika utaratibu huu

Widget kamwe inaonekana, console anasema “Usajili wa leseni ya udereva unahitajika”

Mwisho wa siku wewe ni kurudi hakuna identity_tokenFungua mwisho wa pointi URL moja kwa moja kwenye kivinjari cha admin kilichoingia na &debug=1 - Utaona hatua ya kushindwa. On Laravel hii ni karibu daima ombi-kufunga au cookie-prefix bidhaa hapo juu.

Historia na mazungumzo hufanya kazi, lakini kila zamu ya kuzungumza inasema "Aina ya kuingia inahitajika"

Kuvunjika kwa kawaida, ishara yako ni kukosa TOP-LEVEL authenticated bendera - widget ya mwisho mwenyewe anapokea ishara, verifier pamoja nyuma ya mkondo chat anakataa. "authenticated" => true beside exp.

“Serikali haijaingia katikaOpsIQ" (HTTP)401)

Ishara imehakikishiwa, lakini jina la mtumiaji + mechi ya barua pepe hakuna OpsIQ Aliongeza kuwa Agent huyo katika OpsIQ → Timu, au kuongeza barua pepe ya jukwaa kwenye orodha ya mchezaji huyo wa mechi-Emails wakati inatofautiana na yao OpsIQ Barua ya email.

Kila kitu kila403sKutoka kwa kivinjari lakini inafanya kazi na curl

CORS preflight ni kukataa moja ya maombi yako kichwa. mwisho wako lazima kujibu OPTIONS na echo asili ya kuomba, au tu kuepuka viongozi wa desturi - widget inahitaji tu cookie.

Kazi leo, kazi ya jana, kushindwa

Angalia ukaguzi expIshara ni short-kuishi kwa kubuni. widget re-probes moja kwa moja, hivyo hii kawaida ina maana mwisho kusimamishwa kuona kikao - programu muhimu mzunguko, kikao-driver mabadiliko, au cookie-domain mabadiliko.

💡
widget admin hufanya siri mpaka utambulisho kutatua, na kila chat / inbox / data wito ni kutekelezwa server upande dhidi ya vinavyolinganaOpsIQwakala bila kujali chochote ukurasa anadai. ishara kufungua UI; ruhusa daima kuja kutokaOpsIQ.
Developer ya developer

Utambulisho wa Wageni

Utambulisho unaunganisha wageni wasiojulikana kwa wateja wanaojulikana. Wakati kutambuliwa, OpsIQ viungo vya historia ya kuvinjari, mazungumzo, na tiketi kwa maelezo ya mteja.

Jinsi ya kufanya kazi
Utambulisho wa WageniMtiririko: mtumiaji magogo katika tovuti yako, wewe kutoa ishara saini utambulisho, na OpsIQ unifies vikao vyao, mazungumzo na tiketi katika profile moja.Mtumiaji anaingiza katikakwenye tovuti yakoIshara ya KujiandikishaUtambulisho wa utambulisho_token (HMAC)Moja ya profilesessions+ chat ya+ tiketi za ndege
Utambulisho wa Wageni

mbili za utambulisho, na kila mmoja ana

Kiwango cha kiwango1- Ni ishara ya umoja usio na kifani

Unamwambia mtu ambaye ni mgeni aliye wazi JavaScript Inajaza barua pepe na kitambulisho cha mteja kwenye logi ya mgeni, kwa hivyo dashibodi yako inaonyesha trafiki iliyosainiwa na vikao vinajiunga. Ni HINT: mtu yeyote anaweza kuihariri katika kivinjari chao, hivyo OpsIQ Kamwe usitoe data ya akaunti juu ya nguvu yake.

Kiwango cha kiwango2- Ishara ya utambulisho iliyosainiwa

Seva yako ina ishara ya muda mfupi na siri ya wavuti. OpsIQ inathibitisha saini na kisha tu hushughulikia mtu kama mteja aliyethibitishwa. Hii ni kiwango ambacho kinafungua majibu ya akaunti katika mazungumzo ya wateja na kuangalia kwa kontakt.

⚠️
Kiwango cha kiwango1Ni njia ya kuonyesha ubora wa juu.2Ikiwa swali linaweza kujibiwa tu kwa mmiliki wa akaunti halisi, unahitaji kiwango2.
💡
Huna kuandika ngazi 2 kwa mkono: Remote Tovuti → tovuti yako → Kanuni → C. Kujiandikisha-katika wateja huzalisha saini code na refresh handler kwa PHP, WordPress, Laravel, Node.jsPython Django,.NET, Reli, Java na kwenda. WHMCS hook na Botble kiunganishi daraja tayari saini wateja. Utambulisho anasema nani mteja ni; amri zao au bookings kufikia mazungumzo kupitia connector (na faili daraja tu wakati jukwaa haina ) API).

Kiwango cha kiwango1- Uunganisho usio na ukomo

Weka kitu kabla ya script widget, au piga simu kutambua () baadaye mara moja programu yako anajua ni nani saini katika. Fomu zote mbili ni kusoma; matumizi yoyote inafaa ukurasa wako.

JavaScript· Njia mbili zinazokubaliwa
<!-- Form A: set the global before the loader -->
<script>
  window.OpsIQClient = {
    id:    "cust_1001",
    email: "[email protected]",
    name:  "Jane Smith",
    plan:  "pro"
  };
</script>
<script async src="https://YOUR-OPSIQ/widget.php?site_key=YOUR_SITE_KEY"></script>

<!-- Form B: identify later, e.g. after a client-side login -->
<script>
  window.opsiq.identify({
    id:    "cust_1001",
    email: "[email protected]",
    name:  "Jane Smith",
    plan:  "pro"
  });
</script>
⚠️
Only these forms are read: the window.OpsIQClient global, window.opsiqConfig.user, and window.opsiq.identify(). There is no OpsIQ.push(['identify', ...]) queue and no OpsIQClientSignature global — if you find either in an old note, it does nothing.

Kiwango cha kiwango2- Ishara ya utambulisho wa seva

Kwa mfano, katika kesi ya matumizi ya fedha kama vile admin widget, pamoja na customer Badala ya kuwa na admin Ingia kwenye seva yako na uipe kwa widget. maelezo mawili huamua ikiwa inathibitisha, na yote ni rahisi kupata makosa:

HMAC inajumuisha kamba BASE64URL, si JSON

Ishara ya ishara $payload64Hapana, si ya kwamba $payloadKujiandikisha kwa ghafi JSON hutoa ishara inayoonekana kuwa sahihi na kukataliwa kila wakati na mismatch saini.

base64url, unpadded

Tafsiri ya +/ Kwa kuwa -_ na kuwaondolea hatia = Plain base64 hutokea kuishi leo; msingi wa 64url ni mkataba na ni nini kila OpsIQ verifier na rejea kontakt hutoa.

Kuaminika kwenda katika ngazi ya juu

Kuwa na Beside site_key, iat Na kwa kuwa expNi madai yako kwamba binadamu halisi ni watumiaji katika, na OpsIQ anakataa ishara bila hiyo.

Mteja. id ni lazima

Ishara iliyobeba barua pepe tu inathibitisha kama saini na kisha imeondolewa kimya. Daima tuma kitambulisho.

Weka muda wa kutosha

Dakika kwa masaa. ishara ni kikao cha madai, si credential kuhifadhi.

PHP - ishara ya utambulisho wa mteja ( msimbo huu halisi unathibitisha)
<?php
/* Server-signed customer identity. Runnable as-is: set the two constants. */
$siteKey = "YOUR_SITE_KEY";                        // Remote Sites -> Codes
$secret  = "opsiq_whsec_your_site_secret";         // Remote Sites -> Codes

$payload = json_encode([
    "site_key"      => $siteKey,
    "iat"           => time(),
    "exp"           => time() + 3600,
    "authenticated" => true,                       // TOP LEVEL - required
    "platform"      => "your-platform",
    "customer"      => [
        "id"            => (string)$user->id,      // REQUIRED
        "email"         => (string)$user->email,   // REQUIRED
        "name"          => (string)$user->name,
        "plan"          => (string)($user->plan ?? ""),
        "authenticated" => true,
    ],
], JSON_UNESCAPED_SLASHES);

/* base64url(payload) . "." . hex HMAC-SHA256 OF THAT STRING. */
$payload64 = rtrim(strtr(base64_encode($payload), "+/", "-_"), "=");
$token     = $payload64 . "." . hash_hmac("sha256", $payload64, $secret);

/* Hand it to the widget either way: */
printf(
    '<script async src="https://YOUR-OPSIQ/widget.php?site_key=%s&identity_token=%s"></script>',
    rawurlencode($siteKey),
    rawurlencode($token)
);
// or, if the loader is already on the page:
// echo '<script>window.opsiqConfig = window.opsiqConfig || {}; '
//    . 'window.opsiqConfig.identityToken = ' . json_encode($token) . ';</script>';
🚫
Ishara kwenye seva tu. ishara iliyopunguzwa katika kivinjari JavaScript inamaanisha kusafirisha siri ya tovuti kwa kila mgeni, ambayo inapeana mtu yeyote uwezo wa kuiga mteja wowote.

Mkataba huo, pande tatu

Wateja chat juu ya tovuti yako

Somo la wateja, limepitishwa kama identity_token kwa widget. php. Imefunikwa hapo juu. Chaguo: na snippet A na kiunganishi cha mazungumzo tayari inathibitisha wateja wenyewe (idadi ya uhifadhi au agizo na uthibitisho, au msimbo wa barua pepe kabla ya utaratibu). Tovuti za mbali, Codes, C hutoa msimbo wa kutambua moja kwa moja kwa wateja ambao tayari wameingia kwenye tovuti yako.

Kuingiliana na sauti yako ya nyuma

admin somo, kupita kwa opsiq/embed /admin_widget. php Same signer, tofauti somo muhimu.

Msaada wa portal ya kina

Tofauti kali zaidi: madai sawa pamoja na jti na single_use: kweli, na120maisha ya pili, kwa sababu ishara husafiri katika aURLNa lazima iweze kutumika mara moja.Usiifunge mkono. Mipangilio, Msaada Portal ina snippet tayari kwa lugha yako, na jukwaa linakuhimiza wakati eneo lako la akaunti linaendesha kwenye seva hii.

Jinsi ya kufuta cookies?+

Wanajulikana mpaka watambuliwe tena. OpsIQ inaunganisha rekodi mpya ya isiyojulikana kwa wasifu wa mteja wakati ishara au ishara inapowasili.

Kwa nini ishara yangu kuthibitisha kwa logi ya mgeni lakini si kwa maswali ya akaunti?+

Hii ni kiwango cha1Kiwango cha2Mgawanyiko usiosainiwa unajaza logi ya mgeni na hakuna kitu kingine. Majibu ya Akaunti yanahitaji saini iliyothibitishwa.

Developer ya developer

Ingia ya Portal: Code kwa kila jukwaa

Tuma mteja ambaye tayari amesainiwa katika maombi yako moja kwa moja kwenye bandari yako ya msaada, iliyosainiwa ndani, bila nywila ya pili. ukurasa huu unaelezea jinsi simu inavyofanya kazi, kila madai katika ishara, kuanzisha, na njia kamili ya kila jukwaa. Mipangilio, Msaada Portal inachapisha msimbo huo na anwani yako ya portal na ufunguo wa nafasi ya kazi uliojazwa.

Jinsi ya kufanya kazi

1
Wateja wa mtandao wa simu za mkononi wanasaidia katika app yako

Kiungo kinaonyesha kwenye njia ndogo kwenye seva yako, kwa mfano /support-portal. Kamwe kwenye kiungo ambacho tayari kina ishara: ishara katika uvujaji wa ukurasa kupitia chanzo cha ukurasa, historia ya kivinjari na kichwa cha mtazamaji.

2
ya uchunguzi wa kina ambao umefanywa katika

Inasoma mteja kutoka kikao chako mwenyewe. mgeni ambaye hajasaini anatumwa kwa kuingia kwako kwanza na anarudi kwenye njia ya baadaye.

3
Njia ya kuhesabu ni moja kwa wakati.

HS256 JWT ya kawaida iliyosainiwa na siri hii ya kusaini kazi, ambayo seva yako tu inashikilia. Inamalizika baada ya sekunde za 120 na inaweza kutumika mara moja.

4
Njia ya kurudi kwenye portal

Kwa ukurasa wa bandari mteja alikuja kutoka wakati portal aliuliza kwa moja (opsiq_portal_return, kukubalika tu ndani ya anwani yako ya bandari), vinginevyo nyumba ya bandari. majibu hubeba Referrer-Policy: hakuna-referrer na Cache-Control: no-store.

5
Tovuti inathibitisha na kuonyesha wateja katika

Saini, ufunguo wa nafasi ya kazi, expiry na id ya wakati mmoja hukaguliwa. Mteja hupatikana au kuundwa kwa barua pepe na maombi yao yaliyopo yanalingana nao.

Kwa mujibu wa taarifa hiyo, madai ya

site_key

Ishara ya kazi yako. ishara iliyotengenezwa kwa nafasi nyingine ya kazi haikubaliwa hata wakati imesainiwa vizuri.

ya / exp

Imetolewa-katika na expiry, katika sekunde. ishara ya bandari maisha 120 sekunde: ni lazima tu kuishi moja redirect.

Inayofuata:Kweli

Taarifa ya programu yako kwamba ni kweli saini mtu huyu katika. zinazohitajika, katika ngazi ya juu.

jti + single_use: kweli

Alama ya kawaida na bendera ya wakati mmoja, kiungo hicho hakiwezi kutumika mara mbili.

Jukwaa la jukwaa

Lebo ya bure ambapo mteja alikuja kutoka (php, wordpress, whmcs) Onyesha katika wasifu wa mteja.

Wateja. id na wateja. email

id ni ID ya mteja wako mwenyewe; barua pepe ni jinsi portal hupata wateja na inafanana maombi yao.

Jina la mtumiaji / jina external_id

Chagua jina la kikoa, na anwani ya IP OpsIQ Nenda kwenye tovuti yako.

Kuundwa

1
Kujiandaa kwa njia ya

Mipangilio, Msaada Portal, Ingia bila kuingia kutoka kwenye programu yako. Chagua nini programu yako inaendesha; msimbo chini ya orodha una anwani yako ya bandari na ufunguo wa nafasi ya kazi kujazwa, na maelezo ya kuhesabiwa kwa jukwaa hilo.

2
Tayari mfumo huo upo katika

Njia iliyonakiliwa ina siri ya kutia saini kwa workspace, hivyo inafanya kazi kama ilivyopigwa. Ili kuiweka nje ya faili, kuweka OPSIQ_SITE_SECRET (au mazingira ya mfumo wako) kwenye seva badala yake: thamani hiyo hutumiwa kwanza. Usiweke njia katika ukurasa, JavaScript, programu ya simu au hifadhi ya umma: mtu yeyote mwenye siri anaweza kuingia kama mteja wowote.

3
Weka kiungo chako cha msaada kwenye njia

Kwa mfano, kwa https://your-app.com/support-portal.

4
Fanya ishara ya portal katika kifungo kutumia programu yako

Portal Studio, Ingia katika ukurasa, Tumia kuingia kwa tovuti yangu, Ukurasa wako wa kuingia URL: kuiweka kwenye njia hiyo. portal inaongeza “opsiq_portal_return” yenyewe na njia inarudisha mteja kwenye ukurasa huo, uliosainiwa.

5
Chaguo: Bonyeza kila mahali

Mipangilio, Msaada Portal, Ingia kila mahali: ishara ya programu yako URLKwa hiyo, kusaini nje ya bandari pia ishara mteja nje ya programu yako.

6
Jaribio la majaribio

Kuzalisha kiungo cha mtihani uliosainiwa kwenye ukurasa wa mipangilio hiyo ili kuangalia upande wa bandari peke yake, kisha kufungua njia yako wakati umesaini programu yako.

WHMCS Hakuna haja ya kuwa na kanuni: WHMCS ndoana kutoka maeneo ya mbali tayari ishara wateja katika bandari na kuwaleta nyuma kwenye ukurasa walikuwa juu.
💡
Siri ya siri ni kwa ajili yako. Katika Mipangilio, Msaada Portal, ishara isiyo na ukomo kutoka kwenye programu yako, kila mfano tayari ina siri ya tovuti hii mwenyewe, hivyo msimbo hufanya kazi kama ilivyozoeleka: hakuna kitu cha kuiga au kusanidi. Mifano katika ukurasa huu inaonyesha opsiq_whsec_YOUR_SITE_SECRET Katika kila mfano, kila mmoja ana mtazamo wake. OPSIQ_SITE_SECRET (au mfumo wako mwenyewe kuweka, jina katika maelezo yake) juu ya server kwanza na matumizi kwamba wakati ni kuweka, hivyo unaweza kusonga siri nje ya faili wakati wowote unataka, kwa mfano kwa kuzunguka bila kurekebisha kanuni. njia yoyote file anaendesha kwenye server yako tu: kamwe paste ndani ya ukurasa wa web au kivinjari JavaScript, na kamwe kujitoa kwa repository umma, kwa sababu mtu yeyote mwenye siri unaweza saini katika kama yoyote ya wateja wako au wafanyakazi. WHMCS na Botble haja yoyote ya hii: WHMCS hook inafika na siri kujazwa katika, na Botble kiunganishi jopo hujaza ndani ya daraja.

Njia kamili, jukwaa kwa jukwaa

OpsIQ server (self-hosted)

1

For a self-hosted OpsIQ: the route runs on your own OpsIQ server, so there is no secret to copy. OpsIQ reads this workspace's signing secret itself.

2

Save it as a page on that server, e.g. support-portal.php, and point your "Support" link at it.

3

Replace the body of $currentUser so it returns your signed-in customer (id, email, name), or null for a guest, and /login with your login page.

OpsIQ server (self-hosted)
/* OpsIQ server (self-hosted) — save as e.g. support-portal.php on your OpsIQ
 * server and link your "Support" button to it. OpsIQ reads the workspace's
 * signing secret itself, so there is nothing secret to copy. */

if (!function_exists('opsiq_portal_signed_url_for_site')) {
    require_once '/path/to/opsiq/opsiq/opsiq.portal_identity.php';
}

// 1. WHO IS SIGNED IN — replace the body. Return null for a guest.
$currentUser = static function (): ?array {
    $u = $_SESSION['user'] ?? null;
    return is_array($u) && !empty($u['id']) && !empty($u['email']) ? $u : null;
};
$user = $currentUser();
if (!$user) {
    header('Location: /login?return=' . urlencode($_SERVER['REQUEST_URI'] ?? '/'), true, 302);
    exit;
}

// 2. WHERE TO LAND — the portal page they came from, only if it is on the portal.
$portal = 'https://YOUR-OPSIQ/portal/your-workspace';
$back   = preg_replace('/#.*$/', '', (string)($_GET['opsiq_portal_return'] ?? ''));
$target = ($back === $portal || strpos($back, $portal . '/') === 0 || strpos($back, $portal . '?') === 0)
    ? $back : $portal;

// 3. MINT a one-time link (120 s) for this workspace.
$url = opsiq_portal_signed_url_for_site($target, 'YOUR_SITE_KEY', [
    'id'    => $user['id'],        // REQUIRED
    'email' => $user['email'],     // REQUIRED
    'name'  => $user['name'] ?? '',
], 120);
if (!$url) {
    http_response_code(503);       // fail closed: never send a customer to a guessed address
    exit('Support portal is not configured yet.');
}

header('Referrer-Policy: no-referrer');   // the token is in the URL
header('Cache-Control: no-store');
header('Location: ' . $url, true, 302);
exit;

PHP (no dependencies)

1

Save the snippet as a page in your app, e.g. support-portal.php.

2

This site's signing secret is already filled in, so the code works as pasted. To keep it out of the file, set OPSIQ_SITE_SECRET in the environment (hosting panel, .env or SetEnv) on the server instead: that value is used first. Keep this file on the server and never commit it to a public repository.

3

Replace the body of $currentUser with your app's signed-in customer, and /login with your login page.

PHP (no dependencies)
/* support-portal.php — a redirect route in your own app.
 * Mint at CLICK time: a token baked into an href leaks through page source,
 * browser history and the Referer header. */

// 1. WHO IS SIGNED IN — replace the body with your app's own session. Return null for a guest.
$currentUser = static function (): ?array {
    $u = $_SESSION['user'] ?? null;            // e.g. ['id' => 7, 'email' => '…', 'name' => '…']
    return is_array($u) && !empty($u['id']) && !empty($u['email']) ? $u : null;
};
$user = $currentUser();
if (!$user) {                                  // a guest: sign in first, then come back here
    header('Location: /login?return=' . urlencode($_SERVER['REQUEST_URI'] ?? '/'), true, 302);
    exit;
}

// 2. THE SECRET — server-side only. Fail closed without it.
$secret = (string) (getenv('OPSIQ_SITE_SECRET') ?: 'opsiq_whsec_YOUR_SITE_SECRET');   // this site's secret; the environment wins when set
if ($secret === '') { http_response_code(503); exit('Support portal is not configured.'); }

// 3. WHERE TO LAND — the portal page they came from, only if it is on the portal.
$portal = 'https://YOUR-OPSIQ/portal/your-workspace';
$back   = preg_replace('/#.*$/', '', (string)($_GET['opsiq_portal_return'] ?? ''));
$target = ($back === $portal || strpos($back, $portal . '/') === 0 || strpos($back, $portal . '?') === 0)
    ? $back : $portal;

// 4. MINT the token (standard HS256 JWT).
$b64 = static function ($v) {
    return rtrim(strtr(base64_encode(json_encode($v, JSON_UNESCAPED_SLASHES)), '+/', '-_'), '=');
};
$now = time();
$signing = $b64(['alg' => 'HS256', 'typ' => 'JWT']) . '.' . $b64([
    'site_key'      => 'YOUR_SITE_KEY',
    'iat'           => $now,
    'exp'           => $now + 120,                // URL-borne tokens live ~2 minutes
    'authenticated' => true,
    'jti'           => bin2hex(random_bytes(16)),
    'single_use'    => true,                      // one-time link; replay is refused
    'platform'      => 'php',
    'customer'      => [
        'id'          => $user['id'],             // REQUIRED
        'email'       => $user['email'],          // REQUIRED
        'name'        => $user['name'] ?? '',
        'external_id' => (string) $user['id'],
    ],
]);
$token = $signing . '.' . rtrim(strtr(base64_encode(hash_hmac('sha256', $signing, $secret, true)), '+/', '-_'), '=');

// 5. GO. The default is https://YOUR-OPSIQ/portal/your-workspace?site_key=YOUR_SITE_KEY&identity_token=…
$url = $target . (strpos($target, '?') === false ? '?' : '&')
     . 'site_key=' . rawurlencode('YOUR_SITE_KEY') . '&identity_token=' . rawurlencode($token);
header('Referrer-Policy: no-referrer');       // the token is in the URL
header('Cache-Control: no-store');
header('Location: ' . $url, true, 302);
exit;

Laravel

1

Run: composer require firebase/php-jwt

2

This site's signing secret is already filled in, so the code works as pasted. To keep it out of the file, set OPSIQ_SITE_SECRET=… in .env with 'opsiq' => ['site_secret' => env('OPSIQ_SITE_SECRET')] in config/services.php on the server instead: that value is used first. Keep this file on the server and never commit it to a public repository.

3

Paste the route into routes/web.php. The auth middleware sends guests to your login and back.

Laravel
/* routes/web.php — composer require firebase/php-jwt
 * Link customers to  route('support.portal') */

Route::get('/support-portal', function (\Illuminate\Http\Request $request) {
    $user   = $request->user();                                   // guaranteed by ->middleware('auth')
    $secret = (string) (config('services.opsiq.site_secret') ?: 'opsiq_whsec_YOUR_SITE_SECRET');   // this site's secret; config wins when set
    abort_if($secret === '', 503, 'Support portal is not configured.');   // fail closed

    // Where to land: the portal page they came from, only if it is on the portal.
    $portal = 'https://YOUR-OPSIQ/portal/your-workspace';
    $back   = preg_replace('/#.*$/', '', (string) $request->query('opsiq_portal_return', ''));
    $target = ($back === $portal || str_starts_with($back, $portal . '/') || str_starts_with($back, $portal . '?'))
        ? $back : $portal;

    $now   = time();
    $token = \Firebase\JWT\JWT::encode([
        'site_key'      => 'YOUR_SITE_KEY',
        'iat'           => $now,
        'exp'           => $now + 120,
        'authenticated' => true,
        'jti'           => bin2hex(random_bytes(16)),
        'single_use'    => true,
        'platform'      => 'laravel',
        'customer'      => [
            'id'          => $user->id,          // REQUIRED
            'email'       => $user->email,       // REQUIRED
            'name'        => $user->name,
            'external_id' => (string) $user->id,
        ],
    ], $secret, 'HS256');

    // Default target: https://YOUR-OPSIQ/portal/your-workspace?site_key=YOUR_SITE_KEY&identity_token=…
    $url = $target . (str_contains($target, '?') ? '&' : '?')
         . 'site_key=' . rawurlencode('YOUR_SITE_KEY') . '&identity_token=' . rawurlencode($token);

    return redirect()->away($url)
        ->header('Referrer-Policy', 'no-referrer')
        ->header('Cache-Control', 'no-store');
})->middleware('auth')->name('support.portal');

WordPress

1

This site's signing secret is already filled in, so the code works as pasted. To keep it out of the file, add define('OPSIQ_SITE_SECRET', '…'); to wp-config.php, above "That's all, stop editing", instead: that value is used first. Keep this file on the server and never commit it to a public repository.

2

Paste the snippet into your theme's functions.php, or a small plugin (Code Snippets works).

3

Create an empty page with the slug support-portal and link your "Support" menu item to it. Guests are sent to wp-login and back.

WordPress
/* functions.php, or a small plugin. Create an empty page with the slug
 * "support-portal" and link customers to it. */

add_action('template_redirect', function () {
    if (!is_page('support-portal')) return;
    if (!is_user_logged_in()) { auth_redirect(); }                 // login, then back here

    $secret = defined('OPSIQ_SITE_SECRET') ? OPSIQ_SITE_SECRET : 'opsiq_whsec_YOUR_SITE_SECRET';   // this site's secret; wp-config.php wins when set
    if ($secret === '') wp_die('Support portal is not configured.', '', ['response' => 503]);   // fail closed

    // Where to land: the portal page they came from, only if it is on the portal.
    $portal = 'https://YOUR-OPSIQ/portal/your-workspace';
    $back   = preg_replace('/#.*$/', '', isset($_GET['opsiq_portal_return']) ? wp_unslash((string) $_GET['opsiq_portal_return']) : '');
    $target = ($back === $portal || strpos($back, $portal . '/') === 0 || strpos($back, $portal . '?') === 0)
        ? $back : $portal;

    $user = wp_get_current_user();
    $b64  = static function ($v) {
        return rtrim(strtr(base64_encode(wp_json_encode($v)), '+/', '-_'), '=');
    };
    $now     = time();
    $signing = $b64(['alg' => 'HS256', 'typ' => 'JWT']) . '.' . $b64([
        'site_key'      => 'YOUR_SITE_KEY',
        'iat'           => $now,
        'exp'           => $now + 120,
        'authenticated' => true,
        'jti'           => bin2hex(random_bytes(16)),
        'single_use'    => true,
        'platform'      => 'wordpress',
        'customer'      => [
            'id'          => $user->ID,              // REQUIRED
            'email'       => $user->user_email,      // REQUIRED
            'name'        => $user->display_name,
            'external_id' => (string) $user->ID,
        ],
    ]);
    $token = $signing . '.' . rtrim(strtr(base64_encode(hash_hmac('sha256', $signing, $secret, true)), '+/', '-_'), '=');

    // Default target: https://YOUR-OPSIQ/portal/your-workspace?site_key=YOUR_SITE_KEY&identity_token=…
    $url = $target . (strpos($target, '?') === false ? '?' : '&')
         . 'site_key=' . rawurlencode('YOUR_SITE_KEY') . '&identity_token=' . rawurlencode($token);
    nocache_headers();
    header('Cache-Control: no-store');
    header('Referrer-Policy: no-referrer');
    wp_redirect($url, 302);                                       // wp_redirect, not wp_safe_redirect: the portal is another host
    exit;
});

WHMCS

Already using the OpsIQ WHMCS hook from Sites (includes/hooks/opsiq_tracker.php)? It already signs your customers into the portal and brings them back to the page they were on, so you do not need this snippet. Just set Portal Studio → Sign-in page → Your login page URL to your WHMCS client area login. Use the code below only if you are not installing that hook.
1

Save part 1 as opsiq_support.php in your WHMCS root (next to clientarea.php).

2

This site's signing secret is already filled in, so the code works as pasted. To keep it out of the hook, set $opsiq_site_secret = '…'; in configuration.php instead: that value is used first. Keep this file on the server and never commit it to a public repository.

3

Save part 2 as includes/hooks/opsiq_support_link.php to add Support to the client-area menu.

WHMCS
/* Two files you own — no OpsIQ module, nothing to keep updated.
 *
 * 1) Save this part as  opsiq_support.php  in your WHMCS root. */

require __DIR__ . '/init.php';

$ca = new WHMCS\ClientArea();
$ca->initPage();
$ca->requireLogin();                                         // login, then back here

$secret = '';
if (is_file(__DIR__ . '/configuration.php')) {
    include __DIR__ . '/configuration.php';                  // defines $opsiq_site_secret
    $secret = isset($opsiq_site_secret) ? (string) $opsiq_site_secret : 'opsiq_whsec_YOUR_SITE_SECRET';   // this site's secret; configuration.php wins when set
}
if ($secret === '') { http_response_code(503); exit('Support portal is not configured.'); }   // fail closed

// Where to land: the portal page they came from, only if it is on the portal.
$portal = 'https://YOUR-OPSIQ/portal/your-workspace';
$back   = preg_replace('/#.*$/', '', (string)($_GET['opsiq_portal_return'] ?? ''));
$target = ($back === $portal || strpos($back, $portal . '/') === 0 || strpos($back, $portal . '?') === 0)
    ? $back : $portal;

$uid    = (int) $ca->getUserID();
$client = localAPI('GetClientsDetails', ['clientid' => $uid]);

$b64 = static function ($v) {
    return rtrim(strtr(base64_encode(json_encode($v, JSON_UNESCAPED_SLASHES)), '+/', '-_'), '=');
};
$now     = time();
$signing = $b64(['alg' => 'HS256', 'typ' => 'JWT']) . '.' . $b64([
    'site_key'      => 'YOUR_SITE_KEY',
    'iat'           => $now,
    'exp'           => $now + 120,
    'authenticated' => true,
    'jti'           => bin2hex(random_bytes(16)),
    'single_use'    => true,
    'platform'      => 'whmcs',
    'customer'      => [
        'id'          => $uid,                       // REQUIRED
        'email'       => $client['email'] ?? '',     // REQUIRED
        'name'        => trim(($client['firstname'] ?? '') . ' ' . ($client['lastname'] ?? '')),
        'external_id' => (string) $uid,
    ],
]);
$token = $signing . '.' . rtrim(strtr(base64_encode(hash_hmac('sha256', $signing, $secret, true)), '+/', '-_'), '=');

// Default target: https://YOUR-OPSIQ/portal/your-workspace?site_key=YOUR_SITE_KEY&identity_token=…
$url = $target . (strpos($target, '?') === false ? '?' : '&')
     . 'site_key=' . rawurlencode('YOUR_SITE_KEY') . '&identity_token=' . rawurlencode($token);
header('Referrer-Policy: no-referrer');
header('Cache-Control: no-store');
header('Location: ' . $url, true, 302);
exit;

/* 2) And this part as  includes/hooks/opsiq_support_link.php  to put a
 *    Support entry in the client-area navbar:
 *
 *    add_hook('ClientAreaPrimaryNavbar', 1, function ($navbar) {
 *        $navbar->addChild('opsiqSupport', [
 *            'label' => 'Support',
 *            'uri'   => 'opsiq_support.php',
 *            'order' => 60,
 *        ]);
 *    });
 */

Node.js / Express

1

Run: npm i jsonwebtoken

2

This site's signing secret is already filled in, so the code works as pasted. To keep it out of the file, set OPSIQ_SITE_SECRET in the environment (.env with dotenv, or your host's settings) on the server instead: that value is used first. Keep this file on the server and never commit it to a public repository.

3

Paste the route after your session / passport setup. Change /login if your login page lives elsewhere.

Node.js / Express
// npm i jsonwebtoken
const jwt = require("jsonwebtoken");
const crypto = require("crypto");

const PORTAL = "https://YOUR-OPSIQ/portal/your-workspace";
const onPortal = (u) => u === PORTAL || u.startsWith(PORTAL + "/") || u.startsWith(PORTAL + "?");

app.get("/support-portal", (req, res) => {
  const user = req.user;                                  // set by your session / passport
  if (!user) return res.redirect("/login?next=" + encodeURIComponent(req.originalUrl));

  const secret = process.env.OPSIQ_SITE_SECRET || "opsiq_whsec_YOUR_SITE_SECRET";   // this site's secret; the environment wins when set
  if (!secret) return res.status(503).send("Support portal is not configured.");   // fail closed

  // Where to land: the portal page they came from, only if it is on the portal.
  const back = String(req.query.opsiq_portal_return || "").replace(/#.*$/, "");
  const target = onPortal(back) ? back : PORTAL;

  const token = jwt.sign({
    site_key: "YOUR_SITE_KEY",
    authenticated: true,
    jti: crypto.randomBytes(16).toString("hex"),
    single_use: true,                                     // one-time link
    platform: "node",
    customer: {
      id: user.id,                                        // REQUIRED
      email: user.email,                                  // REQUIRED
      name: user.name,
      external_id: String(user.id),
    },
  }, secret, { algorithm: "HS256", expiresIn: 120 });     // sets iat + exp

  // Default target: https://YOUR-OPSIQ/portal/your-workspace?site_key=YOUR_SITE_KEY&identity_token=…
  const url = target + (target.includes("?") ? "&" : "?")
    + "site_key=" + encodeURIComponent("YOUR_SITE_KEY") + "&identity_token=" + encodeURIComponent(token);
  res.set("Referrer-Policy", "no-referrer").set("Cache-Control", "no-store").redirect(302, url);
});

Node.js (no dependencies)

1

No packages needed. This site's signing secret is already filled in, so the code works as pasted. To keep it out of the file, set OPSIQ_SITE_SECRET in the environment on the server instead: that value is used first. Keep this file on the server and never commit it to a public repository.

2

Replace currentUser() with your app's signed-in customer, then call supportPortal(req, res) for GET /support-portal in your server.

Node.js (no dependencies)
// No packages needed — Node's own crypto is enough.
const crypto = require("crypto");

const PORTAL = "https://YOUR-OPSIQ/portal/your-workspace";
const b64 = (obj) => Buffer.from(JSON.stringify(obj)).toString("base64url");

// 1. WHO IS SIGNED IN — replace with your app's session lookup. Return null for a guest.
function currentUser(req) {
  return req.user || null;                                // { id, email, name }
}

// GET /support-portal
function supportPortal(req, res) {
  const here = new URL(req.url, "http://local");
  const user = currentUser(req);
  if (!user) {                                            // a guest: sign in first, then come back
    res.writeHead(302, { Location: "/login?next=" + encodeURIComponent(req.url) });
    return res.end();
  }
  const secret = process.env.OPSIQ_SITE_SECRET || "opsiq_whsec_YOUR_SITE_SECRET";   // this site's secret; the environment wins when set
  if (!secret) { res.writeHead(503); return res.end("Support portal is not configured."); }

  // Where to land: the portal page they came from, only if it is on the portal.
  const back = (here.searchParams.get("opsiq_portal_return") || "").replace(/#.*$/, "");
  const target = (back === PORTAL || back.startsWith(PORTAL + "/") || back.startsWith(PORTAL + "?")) ? back : PORTAL;

  const now = Math.floor(Date.now() / 1000);
  const signing = b64({ alg: "HS256", typ: "JWT" }) + "." + b64({
    site_key: "YOUR_SITE_KEY",
    iat: now,
    exp: now + 120,
    authenticated: true,
    jti: crypto.randomBytes(16).toString("hex"),
    single_use: true,
    platform: "node",
    customer: { id: user.id, email: user.email, name: user.name, external_id: String(user.id) },
  });
  const token = signing + "." + crypto.createHmac("sha256", secret).update(signing).digest("base64url");

  // Default target: https://YOUR-OPSIQ/portal/your-workspace?site_key=YOUR_SITE_KEY&identity_token=…
  const url = target + (target.includes("?") ? "&" : "?")
    + "site_key=" + encodeURIComponent("YOUR_SITE_KEY") + "&identity_token=" + encodeURIComponent(token);
  res.writeHead(302, { Location: url, "Referrer-Policy": "no-referrer", "Cache-Control": "no-store" });
  res.end();
}

Python (Flask / FastAPI)

1

Run: pip install pyjwt (the Flask example also uses flask-login).

2

This site's signing secret is already filled in, so the code works as pasted. To keep it out of the file, set OPSIQ_SITE_SECRET in the environment on the server instead: that value is used first. Keep this file on the server and never commit it to a public repository.

3

Paste into the module that creates your app. @login_required sends guests to your login view and back.

Python (Flask / FastAPI)
# pip install pyjwt flask-login
import os, secrets, time, urllib.parse
import jwt
from flask import request, redirect, abort
from flask_login import login_required, current_user

PORTAL = "https://YOUR-OPSIQ/portal/your-workspace"

def portal_link(user, back=""):
    secret = os.environ.get("OPSIQ_SITE_SECRET") or "opsiq_whsec_YOUR_SITE_SECRET"   # this site's secret; the environment wins when set
    if not secret:
        abort(503, "Support portal is not configured.")     # fail closed
    back = back.split("#", 1)[0]
    target = back if (back == PORTAL or back.startswith(PORTAL + "/") or back.startswith(PORTAL + "?")) else PORTAL
    now = int(time.time())
    token = jwt.encode({
        "site_key": "YOUR_SITE_KEY",
        "iat": now,
        "exp": now + 120,                                   # URL-borne: ~2 minutes
        "authenticated": True,
        "jti": secrets.token_hex(16),
        "single_use": True,                                 # one-time link
        "platform": "python",
        "customer": {
            "id": user.id,                                  # REQUIRED
            "email": user.email,                            # REQUIRED
            "name": getattr(user, "name", ""),
            "external_id": str(user.id),
        },
    }, secret, algorithm="HS256")
    # Default target: https://YOUR-OPSIQ/portal/your-workspace?site_key=YOUR_SITE_KEY&identity_token=…
    return (target + ("&" if "?" in target else "?")
            + "site_key=" + urllib.parse.quote("YOUR_SITE_KEY", safe="")
            + "&identity_token=" + urllib.parse.quote(token, safe=""))

@app.route("/support-portal")
@login_required
def support_portal():
    resp = redirect(portal_link(current_user, request.args.get("opsiq_portal_return", "")), code=302)
    resp.headers["Referrer-Policy"] = "no-referrer"
    resp.headers["Cache-Control"] = "no-store"
    return resp

Django

1

Run: pip install pyjwt

2

This site's signing secret is already filled in, so the code works as pasted. To keep it out of the file, set OPSIQ_SITE_SECRET in settings.py (for example os.environ["OPSIQ_SITE_SECRET"]) on the server instead: that value is used first. Keep this file on the server and never commit it to a public repository.

3

Paste the view into views.py and add path("support-portal/", views.support_portal) to urls.py. @login_required sends guests to LOGIN_URL and back.

Django
# pip install pyjwt   —   urls.py: path("support-portal/", views.support_portal)
import secrets, time, urllib.parse
import jwt
from django.conf import settings
from django.contrib.auth.decorators import login_required
from django.http import HttpResponse, HttpResponseRedirect

PORTAL = "https://YOUR-OPSIQ/portal/your-workspace"

@login_required
def support_portal(request):
    secret = getattr(settings, "OPSIQ_SITE_SECRET", "") or "opsiq_whsec_YOUR_SITE_SECRET"   # this site's secret; settings win when set
    if not secret:                                       # fail closed
        return HttpResponse("Support portal is not configured.", status=503)

    # Where to land: the portal page they came from, only if it is on the portal.
    back = request.GET.get("opsiq_portal_return", "").split("#", 1)[0]
    target = back if (back == PORTAL or back.startswith(PORTAL + "/") or back.startswith(PORTAL + "?")) else PORTAL

    now = int(time.time())
    token = jwt.encode({
        "site_key": "YOUR_SITE_KEY",
        "iat": now,
        "exp": now + 120,
        "authenticated": True,
        "jti": secrets.token_hex(16),
        "single_use": True,
        "platform": "django",
        "customer": {
            "id": request.user.pk,                        # REQUIRED
            "email": request.user.email,                  # REQUIRED
            "name": request.user.get_full_name(),
            "external_id": str(request.user.pk),
        },
    }, secret, algorithm="HS256")

    # Default target: https://YOUR-OPSIQ/portal/your-workspace?site_key=YOUR_SITE_KEY&identity_token=…
    url = (target + ("&" if "?" in target else "?")
           + "site_key=" + urllib.parse.quote("YOUR_SITE_KEY", safe="")
           + "&identity_token=" + urllib.parse.quote(token, safe=""))
    resp = HttpResponseRedirect(url)
    resp["Referrer-Policy"] = "no-referrer"
    resp["Cache-Control"] = "no-store"
    return resp

.NET / C#

1

Run: dotnet add package System.IdentityModel.Tokens.Jwt

2

This site's signing secret is already filled in, so the code works as pasted. To keep it out of the file, set OpsIQ:SiteSecret (user-secrets, the OpsIQ__SiteSecret environment variable or Key Vault) on the server instead: that value is used first. Keep this file on the server and never commit it to a public repository.

3

Paste into Program.cs after app.UseAuthentication(). RequireAuthorization() sends guests to your login and back.

.NET / C#
// dotnet add package System.IdentityModel.Tokens.Jwt   —   Program.cs
using System.IdentityModel.Tokens.Jwt;
using System.Security.Claims;
using System.Text;
using Microsoft.IdentityModel.Tokens;

const string Portal = "https://YOUR-OPSIQ/portal/your-workspace";

app.MapGet("/support-portal", (HttpContext ctx, IConfiguration cfg) =>
{
    var secret = cfg["OpsIQ:SiteSecret"];
    if (string.IsNullOrEmpty(secret)) secret = "opsiq_whsec_YOUR_SITE_SECRET";   // this site's secret; configuration wins when set
    if (string.IsNullOrEmpty(secret))                     // fail closed
        return Results.StatusCode(503);

    var id    = ctx.User.FindFirstValue(ClaimTypes.NameIdentifier) ?? "";   // REQUIRED
    var email = ctx.User.FindFirstValue(ClaimTypes.Email) ?? "";            // REQUIRED
    var name  = ctx.User.Identity?.Name ?? "";

    // Where to land: the portal page they came from, only if it is on the portal.
    var back = (ctx.Request.Query["opsiq_portal_return"].ToString()).Split('#')[0];
    var target = (back == Portal || back.StartsWith(Portal + "/") || back.StartsWith(Portal + "?")) ? back : Portal;

    var key   = new SymmetricSecurityKey(Encoding.UTF8.GetBytes(secret));
    var creds = new SigningCredentials(key, SecurityAlgorithms.HmacSha256);
    var now   = DateTimeOffset.UtcNow;
    var payload = new JwtPayload
    {
        { "site_key",      "YOUR_SITE_KEY" },
        { "iat",           now.ToUnixTimeSeconds() },
        { "exp",           now.AddSeconds(120).ToUnixTimeSeconds() },
        { "authenticated", true },
        { "jti",           Guid.NewGuid().ToString("N") },
        { "single_use",    true },
        { "platform",      "dotnet" },
        { "customer", new Dictionary<string, object>
            { { "id", id }, { "email", email }, { "name", name }, { "external_id", id } } },
    };
    var token = new JwtSecurityTokenHandler().WriteToken(new JwtSecurityToken(new JwtHeader(creds), payload));

    // Default target: https://YOUR-OPSIQ/portal/your-workspace?site_key=YOUR_SITE_KEY&identity_token=…
    var url = target + (target.Contains('?') ? "&" : "?")
        + "site_key=" + Uri.EscapeDataString("YOUR_SITE_KEY") + "&identity_token=" + Uri.EscapeDataString(token);
    ctx.Response.Headers["Referrer-Policy"] = "no-referrer";
    ctx.Response.Headers["Cache-Control"] = "no-store";
    return Results.Redirect(url);
}).RequireAuthorization();

Ruby on Rails

1

Add gem "jwt" to the Gemfile and run bundle install.

2

This site's signing secret is already filled in, so the code works as pasted. To keep it out of the file, set OPSIQ_SITE_SECRET in the environment (or Rails credentials) on the server instead: that value is used first. Keep this file on the server and never commit it to a public repository.

3

Save as app/controllers/support_controller.rb and add get "/support-portal", to: "support#portal" to routes.rb. Devise's authenticate_user! sends guests to login and back.

Ruby on Rails
# Gemfile: gem "jwt"   —   routes.rb: get "/support-portal", to: "support#portal"
require "jwt"
require "securerandom"
require "cgi"

class SupportController < ApplicationController
  before_action :authenticate_user!                      # login, then back here

  PORTAL = "https://YOUR-OPSIQ/portal/your-workspace"

  def portal
    secret = ENV["OPSIQ_SITE_SECRET"].presence || "opsiq_whsec_YOUR_SITE_SECRET"   # this site's secret; the environment wins when set
    return head :service_unavailable if secret.blank?    # fail closed

    # Where to land: the portal page they came from, only if it is on the portal.
    back = params[:opsiq_portal_return].to_s.split("#").first.to_s
    target = (back == PORTAL || back.start_with?(PORTAL + "/", PORTAL + "?")) ? back : PORTAL

    now = Time.now.to_i
    token = JWT.encode({
      site_key:      "YOUR_SITE_KEY",
      iat:           now,
      exp:           now + 120,
      authenticated: true,
      jti:           SecureRandom.hex(16),
      single_use:    true,
      platform:      "rails",
      customer: {
        id:          current_user.id,                    # REQUIRED
        email:       current_user.email,                 # REQUIRED
        name:        current_user.try(:name).to_s,
        external_id: current_user.id.to_s
      }
    }, secret, "HS256")

    # Default target: https://YOUR-OPSIQ/portal/your-workspace?site_key=YOUR_SITE_KEY&identity_token=…
    url = target + (target.include?("?") ? "&" : "?") +
          "site_key=#{CGI.escape("YOUR_SITE_KEY")}&identity_token=#{CGI.escape(token)}"
    response.headers["Referrer-Policy"] = "no-referrer"
    response.headers["Cache-Control"] = "no-store"
    redirect_to url, allow_other_host: true
  end
end

Java (Spring Boot)

1

Add io.jsonwebtoken:jjwt-api, jjwt-impl and jjwt-jackson (0.12+).

2

This site's signing secret is already filled in, so the code works as pasted. To keep it out of the file, set opsiq.site.secret in application.properties (for example from OPSIQ_SITE_SECRET) on the server instead: that value is used first. Keep this file on the server and never commit it to a public repository.

3

Replace currentUser() with your user lookup. With Spring Security the route must be authenticated so guests go to login and back.

Java (Spring Boot)
// io.jsonwebtoken:jjwt-api / jjwt-impl / jjwt-jackson (0.12+)
import io.jsonwebtoken.Jwts;
import io.jsonwebtoken.security.Keys;
import jakarta.servlet.http.HttpServletResponse;
import java.net.URLEncoder;
import java.nio.charset.StandardCharsets;
import java.security.Principal;
import java.time.Instant;
import java.util.*;
import org.springframework.beans.factory.annotation.Value;
import org.springframework.http.HttpStatus;
import org.springframework.stereotype.Controller;
import org.springframework.web.bind.annotation.*;
import org.springframework.web.server.ResponseStatusException;
import org.springframework.web.servlet.view.RedirectView;

@Controller
public class SupportPortalController {
    private static final String PORTAL = "https://YOUR-OPSIQ/portal/your-workspace";

    @Value("${opsiq.site.secret:opsiq_whsec_YOUR_SITE_SECRET}")   // this site's secret; opsiq.site.secret wins when set
    private String secret;

    /** WHO IS SIGNED IN — replace with your own lookup: id, email, name. */
    private Map<String, Object> currentUser(Principal principal) {
        return Map.of("id", principal.getName(), "email", principal.getName(), "name", principal.getName());
    }

    @GetMapping("/support-portal")
    public RedirectView supportPortal(Principal principal, HttpServletResponse response,
                                      @RequestParam(name = "opsiq_portal_return", defaultValue = "") String back) {
        if (principal == null) return new RedirectView("/login");               // login, then back here
        if (secret.isEmpty()) throw new ResponseStatusException(HttpStatus.SERVICE_UNAVAILABLE);   // fail closed

        // Where to land: the portal page they came from, only if it is on the portal.
        back = back.split("#", 2)[0];
        String target = (back.equals(PORTAL) || back.startsWith(PORTAL + "/") || back.startsWith(PORTAL + "?")) ? back : PORTAL;

        Map<String, Object> user = currentUser(principal);
        Map<String, Object> customer = Map.of(
            "id",          user.get("id"),                 // REQUIRED
            "email",       user.get("email"),              // REQUIRED
            "name",        user.get("name"),
            "external_id", String.valueOf(user.get("id")));

        Instant now = Instant.now();
        String token = Jwts.builder()
            .claim("site_key", "YOUR_SITE_KEY")
            .claim("authenticated", true)
            .claim("single_use", true)                     // one-time link
            .claim("platform", "java")
            .claim("customer", customer)
            .id(UUID.randomUUID().toString())              // jti
            .issuedAt(Date.from(now))
            .expiration(Date.from(now.plusSeconds(120)))
            .signWith(Keys.hmacShaKeyFor(secret.getBytes(StandardCharsets.UTF_8)), Jwts.SIG.HS256)
            .compact();

        // Default target: https://YOUR-OPSIQ/portal/your-workspace?site_key=YOUR_SITE_KEY&identity_token=…
        String url = target + (target.contains("?") ? "&" : "?")
            + "site_key=" + URLEncoder.encode("YOUR_SITE_KEY", StandardCharsets.UTF_8)
            + "&identity_token=" + URLEncoder.encode(token, StandardCharsets.UTF_8);
        response.setHeader("Referrer-Policy", "no-referrer");
        response.setHeader("Cache-Control", "no-store");
        return new RedirectView(url);
    }
}

Go

1

Run: go get github.com/golang-jwt/jwt/v5

2

This site's signing secret is already filled in, so the code works as pasted. To keep it out of the file, set OPSIQ_SITE_SECRET in the environment on the server instead: that value is used first. Keep this file on the server and never commit it to a public repository.

3

Replace currentUser() with your session lookup and register http.HandleFunc("/support-portal", supportPortal).

Go
// go get github.com/golang-jwt/jwt/v5
package main

import (
    "crypto/rand"
    "encoding/hex"
    "fmt"
    "net/http"
    "net/url"
    "os"
    "strings"
    "time"

    "github.com/golang-jwt/jwt/v5"
)

const portal = "https://YOUR-OPSIQ/portal/your-workspace"

type User struct{ ID, Email, Name string }

// WHO IS SIGNED IN — replace with your session lookup. Return nil for a guest.
func currentUser(r *http.Request) *User { return nil }

func supportPortal(w http.ResponseWriter, r *http.Request) {
    user := currentUser(r)
    if user == nil { // login, then back here
        http.Redirect(w, r, "/login?next="+url.QueryEscape(r.URL.RequestURI()), http.StatusFound)
        return
    }
    secret := os.Getenv("OPSIQ_SITE_SECRET")
    if secret == "" {
        secret = "opsiq_whsec_YOUR_SITE_SECRET" // this site's secret; the environment wins when set
    }
    if secret == "" { // fail closed
        http.Error(w, "Support portal is not configured.", http.StatusServiceUnavailable)
        return
    }

    // Where to land: the portal page they came from, only if it is on the portal.
    back := strings.SplitN(r.URL.Query().Get("opsiq_portal_return"), "#", 2)[0]
    target := portal
    if back == portal || strings.HasPrefix(back, portal+"/") || strings.HasPrefix(back, portal+"?") {
        target = back
    }

    jti := make([]byte, 16)
    rand.Read(jti)
    now := time.Now().Unix()
    token, err := jwt.NewWithClaims(jwt.SigningMethodHS256, jwt.MapClaims{
        "site_key":      "YOUR_SITE_KEY",
        "iat":           now,
        "exp":           now + 120,
        "authenticated": true,
        "jti":           hex.EncodeToString(jti),
        "single_use":    true,
        "platform":      "go",
        "customer": map[string]any{
            "id":          user.ID,    // REQUIRED
            "email":       user.Email, // REQUIRED
            "name":        user.Name,
            "external_id": fmt.Sprint(user.ID),
        },
    }).SignedString([]byte(secret))
    if err != nil {
        http.Error(w, "sign failed", http.StatusInternalServerError)
        return
    }

    // Default target: https://YOUR-OPSIQ/portal/your-workspace?site_key=YOUR_SITE_KEY&identity_token=…
    sep := "?"
    if strings.Contains(target, "?") {
        sep = "&"
    }
    w.Header().Set("Referrer-Policy", "no-referrer")
    w.Header().Set("Cache-Control", "no-store")
    http.Redirect(w, r, target+sep+"site_key="+url.QueryEscape("YOUR_SITE_KEY")+"&identity_token="+url.QueryEscape(token), http.StatusFound)
}

Wakati kuna kitu kibaya

Tovuti inafunguliwa, lakini imefunguliwa

Siri au kazi muhimu haina mechi nafasi hii ya kazi, ishara ni zaidi kuliko sekunde 120 (angalia saa ya seva), au kiungo hicho kilifunguliwa mara mbili. Kutengeneza kiungo cha mtihani kilichosainiwa: ikiwa hiyo inafanya kazi, kulinganisha madai ya ishara yako na mfano.

Daima kuweka katika portal ya nyumbani

Anwani ya kurudi haikuwa ndani ya anwani yako ya bandari, kwa hivyo ilipuuzwa kwa madhumuni. Linganisha na Portal URL iliyoonyeshwa katika Mipangilio.

Wageni wanapata makosa badala ya kuingia kwako

Badilisha /login katika njia na ukurasa wako wa kuingia halisi, na hakikisha kuingia kwako kunarudi kwenye anwani uliyopewa.

Hii inafanya kazi kwa baadhi ya wateja tu

Wateja. email au customer. id ni tupu kwao. Wote wawili wanahitajika.

Developer ya developer

Wateja chat: kutambua watumiaji katika wateja

Maeneo mengi hayahitaji hii: na snippet ya wazi ya mazungumzo na kontakt, chat inathibitisha wateja wenyewe, na uhifadhi au nambari ya utaratibu pamoja na ushahidi wa kuangalia na msimbo uliotumwa kabla ya agizo. Ongeza hii wakati unataka mteja ambaye tayari ameingia kwenye tovuti yako kutambuliwa moja kwa moja, na akaunti yao nzima. WHMCS tayari inaifanya kupitia ndoano yake. Tovuti za mbali, tovuti yako, Codes, C magazeti sawa na msimbo wako wa tovuti kujazwa katika mtandao wako.

Jinsi ya kufanya kazi

1
Ukurasa wako unachapisha tag ya chat

Kwa mteja aliyesajiliwa widget URL hubeba &identity_token = ... iliyosainiwa kwenye seva yako; kwa mgeni ni tag wazi. Hakuna siri katika ukurasa: ishara tu ambayo inaisha.

2
Chat inaonyesha ishara

Ishara, ufunguo wa nafasi ya kazi na expiry. mteja ni kisha inajulikana juu ya kila ombi la mazungumzo, na kontakt yako inaweza kujibu kuhusu amri zao wenyewe, bookings au ankara.

3
Kupumzika kwa muda kabla ya saa ni juu

Inaita ukurasa ni juu ya na? opsiq_identity_refresh =1& jukumu = mteja. Kanuni yako majibu {"kufanikiwa": kweli, "identity_token": "…"} wakati wateja ni alijiandikisha katika, au 401 na {"success":false,"login_required":true} wakati wao si. Hiyo ni kwa nini refresh handler lazima kukimbia kabla ya ukurasa wako prints kitu chochote.

Jinsi ya kutofautisha kutoka kwa ishara ya portal

Maisha ya

Saa moja (exp = iat + 3600Badala ya 120 Sekunde, kwa sababu inapanda kila ombi la mazungumzo badala ya moja kuelekeza.

Hakuna cha wala single_use

Na kila kitu ni sawa na wakati wa kupanda mbegu.

Kama ilivyo kwa kila kitu kingine

site_key, iat, exp, kuthibitishwa: kweli, jukwaa, na mteja aliye na kitambulisho kinachohitajika na barua pepe.

💡
Utambulisho anasema WHO mteja ni. amri zao, bookings au ankara kufikia chat kupitia kontakt: moja kwamba wito jukwaa yako APIAu, wakati tovuti yako haina API, kontakt pamoja na faili yake ya daraja (mtengenezaji wa kiunganishi hufanya moja).
💡
Siri ya siri ni kwa ajili yako. Katika maeneo ya mbali, tovuti yako, Kanuni, C, kila mfano tayari ina siri ya tovuti hii mwenyewe, hivyo msimbo kazi kama pasted: hakuna kitu cha kuiga au configure. opsiq_whsec_YOUR_SITE_SECRET Katika kila mfano, kila mmoja ana mtazamo wake. OPSIQ_SITE_SECRET (au mfumo wako mwenyewe kuweka, jina katika maelezo yake) juu ya server kwanza na matumizi kwamba wakati ni kuweka, hivyo unaweza kusonga siri nje ya faili wakati wowote unataka, kwa mfano kwa kuzunguka bila kurekebisha kanuni. njia yoyote file anaendesha kwenye server yako tu: kamwe paste ndani ya ukurasa wa web au kivinjari JavaScript, na kamwe kujitoa kwa repository umma, kwa sababu mtu yeyote mwenye siri unaweza saini katika kama yoyote ya wateja wako au wafanyakazi. WHMCS na Botble haja yoyote ya hii: WHMCS hook inafika na siri kujazwa katika, na Botble kiunganishi jopo hujaza ndani ya daraja.

Mfumo wa jumla, jukwaa kwa jukwaa

WHMCS

Nothing to add: the WHMCS hook in Option 1 already signs your signed-in clients into the chat, refreshes the token on long visits, and signs staff into Admin Chat. No connector is needed for this.
1

Install the Option 1 hook as includes/hooks/opsiq_tracker.php. Do not also paste the plain chat tag.

2

Optional: add the WHMCS connector under Connectors if you also want the chat to answer about invoices, services and tickets. Identity works without it.

includes/hooks/opsiq_tracker.php
/* WHMCS: no extra code. Option 1 (the All-in-One WHMCS Hook) signs the signed-in
 * client into Client Chat, answers ?opsiq_identity_refresh=1 and signs staff into
 * Admin Chat. No connector is needed for identity. */

Botble (connector bridge)

Nothing to add for bookings: the Botble connector takes bookings as a guest checkout and finds existing bookings by booking number and proof, so guests do not need to sign in. Admins are signed in through the bridge (op=admin_embed).
1

Install the Botble connector under Connectors, copy its bridge file from the connector panel and upload it to public/. The panel fills in OPSIQ_HOST, OPSIQ_SITE_KEY and OPSIQ_SITE_SECRET for you.

2

Botble has no API, so the bridge file is how the chat reads rooms and takes bookings. To also recognise a guest who is already signed in on the hotel site, use the Laravel option with your customer guard.

public/opsiq-botble-bridge.php
/* Botble: no extra code for bookings.
 * The connector books as a guest checkout and finds bookings by booking number + proof.
 * In public/opsiq-botble-bridge.php fill OPSIQ_HOST, OPSIQ_SITE_KEY and OPSIQ_SITE_SECRET.
 * Admins: op=admin_embed */

PHP (no dependencies)

1

Save as opsiq-chat.php. This site's signing secret is already filled in, so the code works as pasted. To keep it out of the file, set OPSIQ_SITE_SECRET in the environment on the server instead: that value is used first. Keep this file on the server and never commit it to a public repository.

2

At the very top of every page (or your front controller), before any output: require 'opsiq-chat.php'; opsiq_chat_refresh();

3

Just before </body> on every page: <?= opsiq_chat_tag() ?> — it replaces the plain chat tag. Replace opsiq_chat_user() with your signed-in customer.

opsiq-chat.php
<?php
/* opsiq-chat.php — signed-in customers for OpsIQ Client Chat. */

// WHO IS SIGNED IN — replace the body with your app's session. Return null for a guest.
function opsiq_chat_user(): ?array
{
    $u = $_SESSION['user'] ?? null;               // e.g. ['id' => 7, 'email' => '…', 'name' => '…']
    return is_array($u) && !empty($u['id']) && !empty($u['email']) ? $u : null;
}

function opsiq_chat_token(array $u): string
{
    $secret = (string) (getenv('OPSIQ_SITE_SECRET') ?: 'opsiq_whsec_YOUR_SITE_SECRET');   // this site's secret; the environment wins when set
    if ($secret === '') return '';                           // fail closed: plain chat, no identity
    $b64 = static fn($v) => rtrim(strtr(base64_encode(json_encode($v, JSON_UNESCAPED_SLASHES)), '+/', '-_'), '=');
    $now = time();
    $signing = $b64(['alg' => 'HS256', 'typ' => 'JWT']) . '.' . $b64([
        'site_key'      => 'YOUR_SITE_KEY',
        'iat'           => $now,
        'exp'           => $now + 3600,                      // the widget refreshes before this
        'authenticated' => true,
        'platform'      => 'php',
        'customer'      => [
            'id'          => $u['id'],                       // REQUIRED
            'email'       => $u['email'],                    // REQUIRED
            'name'        => $u['name'] ?? '',
            'external_id' => (string) $u['id'],
        ],
    ]);
    return $signing . '.' . rtrim(strtr(base64_encode(hash_hmac('sha256', $signing, $secret, true)), '+/', '-_'), '=');
}

// Call at the top of every page, before any output.
function opsiq_chat_refresh(): void
{
    if (empty($_GET['opsiq_identity_refresh'])) return;
    header('Content-Type: application/json; charset=utf-8');
    header('Cache-Control: no-store');
    $u = opsiq_chat_user();
    $t = $u ? opsiq_chat_token($u) : '';
    if ($t === '') { http_response_code(401); echo json_encode(['success' => false, 'login_required' => true]); exit; }
    echo json_encode(['success' => true, 'role' => 'customer', 'identity_token' => $t]);
    exit;
}

// Print before </body> on every page, instead of the plain chat tag.
function opsiq_chat_tag(): string
{
    $src = 'https://YOUR-OPSIQ/widget.php?site_key=YOUR_SITE_KEY';
    $u = opsiq_chat_user();
    $t = $u ? opsiq_chat_token($u) : '';
    if ($t !== '') $src .= '&identity_token=' . rawurlencode($t);
    return '<script async src="' . htmlspecialchars($src, ENT_QUOTES) . '" data-opsiq-widget="client-chat"></script>';
}

Laravel

1

Run: composer require firebase/php-jwt. This site's signing secret is already filled in, so the code works as pasted. To keep it out of the file, set OPSIQ_SITE_SECRET=… in .env with 'opsiq' => ['site_secret' => env('OPSIQ_SITE_SECRET')] in config/services.php on the server instead: that value is used first. Keep this file on the server and never commit it to a public repository.

2

Save the class as app/Support/OpsiqChat.php, and add the small OpsiqChatRefresh middleware from the bottom of the code to the web group, so the widget can refresh its token on any page.

3

In your main Blade layout, just before </body>: {!! \App\Support\OpsiqChat::tag() !!}

app/Support/OpsiqChat.php
<?php
// app/Support/OpsiqChat.php — composer require firebase/php-jwt
namespace App\Support;

use Firebase\JWT\JWT;

final class OpsiqChat
{
    public static function token(): string
    {
        $user = auth()->user();
        $secret = (string) (config('services.opsiq.site_secret') ?: 'opsiq_whsec_YOUR_SITE_SECRET');   // this site's secret; config wins when set
        if (!$user || $secret === '') return '';                 // guest, or not configured
        $now = time();
        return JWT::encode([
            'site_key'      => 'YOUR_SITE_KEY',
            'iat'           => $now,
            'exp'           => $now + 3600,
            'authenticated' => true,
            'platform'      => 'laravel',
            'customer'      => [
                'id'          => $user->id,                      // REQUIRED
                'email'       => $user->email,                   // REQUIRED
                'name'        => $user->name,
                'external_id' => (string) $user->id,
            ],
        ], $secret, 'HS256');
    }

    /** For Blade: {!! \App\Support\OpsiqChat::tag() !!} before </body>. */
    public static function tag(): string
    {
        $src = 'https://YOUR-OPSIQ/widget.php?site_key=YOUR_SITE_KEY';
        $t = self::token();
        if ($t !== '') $src .= '&identity_token=' . rawurlencode($t);
        return '<script async src="' . e($src) . '" data-opsiq-widget="client-chat"></script>';
    }
}

/* Refresh: the widget asks ?opsiq_identity_refresh=1 on the page it is on.
 * Laravel 11+ — bootstrap/app.php:
 *
 *   ->withMiddleware(function ($middleware) {
 *       $middleware->web(append: \App\Http\Middleware\OpsiqChatRefresh::class);
 *   })
 *
 * app/Http/Middleware/OpsiqChatRefresh.php:
 *
 *   public function handle($request, \Closure $next) {
 *       if (!$request->query('opsiq_identity_refresh')) return $next($request);
 *       $t = \App\Support\OpsiqChat::token();
 *       return $t === ''
 *           ? response()->json(['success' => false, 'login_required' => true], 401)->header('Cache-Control', 'no-store')
 *           : response()->json(['success' => true, 'role' => 'customer', 'identity_token' => $t])->header('Cache-Control', 'no-store');
 *   }
 */

WordPress / WooCommerce

1

This site's signing secret is already filled in, so the code works as pasted. To keep it out of the file, add define('OPSIQ_SITE_SECRET', '…'); to wp-config.php instead: that value is used first. Keep this file on the server and never commit it to a public repository.

2

Paste into your theme's functions.php or a small plugin. It prints the chat itself, so remove the plain chat tag if you added one.

3

For WooCommerce orders in the chat, add the WooCommerce connector under Connectors.

functions.php
/* functions.php or a small plugin — OpsIQ Client Chat with signed-in customers. */

if (!defined('OPSIQ_SITE_SECRET')) define('OPSIQ_SITE_SECRET', 'opsiq_whsec_YOUR_SITE_SECRET');   // this site's secret; wp-config.php wins when set

function opsiq_chat_token(): string {
    if (!is_user_logged_in() || !defined('OPSIQ_SITE_SECRET') || OPSIQ_SITE_SECRET === '') return '';
    $u   = wp_get_current_user();
    $b64 = static fn($v) => rtrim(strtr(base64_encode(wp_json_encode($v)), '+/', '-_'), '=');
    $now = time();
    $signing = $b64(['alg' => 'HS256', 'typ' => 'JWT']) . '.' . $b64([
        'site_key'      => 'YOUR_SITE_KEY',
        'iat'           => $now,
        'exp'           => $now + 3600,
        'authenticated' => true,
        'platform'      => 'wordpress',
        'customer'      => [
            'id'          => $u->ID,                     // REQUIRED
            'email'       => $u->user_email,             // REQUIRED
            'name'        => $u->display_name,
            'external_id' => (string) $u->ID,
        ],
    ]);
    return $signing . '.' . rtrim(strtr(base64_encode(hash_hmac('sha256', $signing, OPSIQ_SITE_SECRET, true)), '+/', '-_'), '=');
}

// Refresh: the widget asks ?opsiq_identity_refresh=1 on the page it is on.
add_action('init', function () {
    if (empty($_GET['opsiq_identity_refresh'])) return;
    nocache_headers();
    $t = opsiq_chat_token();
    if ($t === '') wp_send_json(['success' => false, 'login_required' => true], 401);
    wp_send_json(['success' => true, 'role' => 'customer', 'identity_token' => $t]);
});

// The chat tag, on every front-end page.
add_action('wp_footer', function () {
    $src = 'https://YOUR-OPSIQ/widget.php?site_key=YOUR_SITE_KEY';
    $t = opsiq_chat_token();
    if ($t !== '') $src .= '&identity_token=' . rawurlencode($t);
    echo '<script async src="' . esc_url($src) . '" data-opsiq-widget="client-chat"></script>';
});

Node.js / Express

1

Run: npm i jsonwebtoken. This site's signing secret is already filled in, so the code works as pasted. To keep it out of the file, set OPSIQ_SITE_SECRET in the environment on the server instead: that value is used first. Keep this file on the server and never commit it to a public repository.

2

app.use(opsiqChat) after your session / passport middleware. It answers the refresh and sets res.locals.opsiqChatTag.

3

Print res.locals.opsiqChatTag (unescaped) just before </body> in your layout, instead of the plain chat tag.

opsiq-chat.js
// opsiq-chat.js — npm i jsonwebtoken
const jwt = require("jsonwebtoken");

function opsiqChatToken(user) {
  const secret = process.env.OPSIQ_SITE_SECRET || "opsiq_whsec_YOUR_SITE_SECRET";   // this site's secret; the environment wins when set
  if (!user || !secret) return "";
  return jwt.sign({
    site_key: "YOUR_SITE_KEY",
    authenticated: true,
    platform: "node",
    customer: { id: user.id, email: user.email, name: user.name, external_id: String(user.id) },  // id + email REQUIRED
  }, secret, { algorithm: "HS256", expiresIn: 3600 });     // sets iat + exp
}

// app.use(opsiqChat) — after your session / passport middleware.
function opsiqChat(req, res, next) {
  const token = opsiqChatToken(req.user);
  if (req.query.opsiq_identity_refresh) {                  // the widget refreshing on this page
    res.set("Cache-Control", "no-store");
    return token
      ? res.json({ success: true, role: "customer", identity_token: token })
      : res.status(401).json({ success: false, login_required: true });
  }
  const src = "https://YOUR-OPSIQ/widget.php?site_key=YOUR_SITE_KEY" + (token ? "&identity_token=" + encodeURIComponent(token) : "");
  res.locals.opsiqChatTag = '<script async src="' + src.replace(/"/g, """) + '" data-opsiq-widget="client-chat"></script>';
  next();
}

module.exports = { opsiqChat };

Python (Flask)

1

Run: pip install pyjwt flask-login. This site's signing secret is already filled in, so the code works as pasted. To keep it out of the file, set OPSIQ_SITE_SECRET in the environment on the server instead: that value is used first. Keep this file on the server and never commit it to a public repository.

2

Call init_opsiq_chat(app) where you create the app. It answers the refresh and gives templates opsiq_chat_tag.

3

In your base template, just before </body>: {{ opsiq_chat_tag }}

opsiq_chat.py
# opsiq_chat.py — pip install pyjwt flask-login
import os, time, urllib.parse
import jwt
from flask import request, jsonify
from flask_login import current_user
from markupsafe import Markup, escape

def opsiq_chat_token():
    secret = os.environ.get("OPSIQ_SITE_SECRET") or "opsiq_whsec_YOUR_SITE_SECRET"   # this site's secret; the environment wins when set
    if not secret or not current_user.is_authenticated:
        return ""
    now = int(time.time())
    return jwt.encode({
        "site_key": "YOUR_SITE_KEY", "iat": now, "exp": now + 3600,
        "authenticated": True, "platform": "python",
        "customer": {"id": current_user.id, "email": current_user.email,       # REQUIRED
                     "name": getattr(current_user, "name", ""), "external_id": str(current_user.id)},
    }, secret, algorithm="HS256")

def init_opsiq_chat(app):
    @app.before_request
    def _opsiq_refresh():
        if request.args.get("opsiq_identity_refresh"):
            t = opsiq_chat_token()
            resp = jsonify({"success": True, "role": "customer", "identity_token": t}) if t \
                else (jsonify({"success": False, "login_required": True}), 401)
            if isinstance(resp, tuple):
                resp[0].headers["Cache-Control"] = "no-store"
            else:
                resp.headers["Cache-Control"] = "no-store"
            return resp

    @app.context_processor
    def _opsiq_tag():
        t = opsiq_chat_token()
        src = "https://YOUR-OPSIQ/widget.php?site_key=YOUR_SITE_KEY" + ("&identity_token=" + urllib.parse.quote(t, safe="") if t else "")
        return {"opsiq_chat_tag": Markup('<script async src="%s" data-opsiq-widget="client-chat"></script>' % escape(src))}

Django

1

Run: pip install pyjwt. This site's signing secret is already filled in, so the code works as pasted. To keep it out of the file, set OPSIQ_SITE_SECRET in settings.py (for example os.environ["OPSIQ_SITE_SECRET"]) on the server instead: that value is used first. Keep this file on the server and never commit it to a public repository.

2

Add "yourapp.opsiq_chat.OpsiqChatMiddleware" to MIDDLEWARE (after AuthenticationMiddleware) and "yourapp.opsiq_chat.opsiq_chat" to TEMPLATES context_processors.

3

In your base template, just before </body>: {{ opsiq_chat_tag }}

opsiq_chat.py
# yourapp/opsiq_chat.py — pip install pyjwt
import time, urllib.parse
import jwt
from django.conf import settings
from django.http import JsonResponse
from django.utils.html import format_html

def opsiq_chat_token(user):
    secret = getattr(settings, "OPSIQ_SITE_SECRET", "") or "opsiq_whsec_YOUR_SITE_SECRET"   # this site's secret; settings win when set
    if not secret or not user.is_authenticated:
        return ""
    now = int(time.time())
    return jwt.encode({
        "site_key": "YOUR_SITE_KEY", "iat": now, "exp": now + 3600,
        "authenticated": True, "platform": "django",
        "customer": {"id": user.pk, "email": user.email,             # REQUIRED
                     "name": user.get_full_name(), "external_id": str(user.pk)},
    }, secret, algorithm="HS256")

class OpsiqChatMiddleware:
    def __init__(self, get_response):
        self.get_response = get_response
    def __call__(self, request):
        if request.GET.get("opsiq_identity_refresh"):
            t = opsiq_chat_token(request.user)
            resp = (JsonResponse({"success": True, "role": "customer", "identity_token": t}) if t
                    else JsonResponse({"success": False, "login_required": True}, status=401))
            resp["Cache-Control"] = "no-store"
            return resp
        return self.get_response(request)

def opsiq_chat(request):
    t = opsiq_chat_token(request.user)
    src = "https://YOUR-OPSIQ/widget.php?site_key=YOUR_SITE_KEY" + ("&identity_token=" + urllib.parse.quote(t, safe="") if t else "")
    return {"opsiq_chat_tag": format_html('<script async src="{}" data-opsiq-widget="client-chat"></script>', src)}

.NET / C#

1

Run: dotnet add package System.IdentityModel.Tokens.Jwt. This site's signing secret is already filled in, so the code works as pasted. To keep it out of the file, set OpsIQ:SiteSecret (user-secrets, the OpsIQ__SiteSecret environment variable or Key Vault) on the server instead: that value is used first. Keep this file on the server and never commit it to a public repository.

2

In Program.cs, after app.UseAuthentication(): app.Use(OpsiqChat.Refresh);

3

In _Layout.cshtml before </body>: @Html.Raw(OpsiqChat.Tag(Context))

OpsiqChat.cs
// OpsiqChat.cs — dotnet add package System.IdentityModel.Tokens.Jwt
using System.IdentityModel.Tokens.Jwt;
using System.Net;
using System.Security.Claims;
using System.Text;
using Microsoft.IdentityModel.Tokens;

public static class OpsiqChat
{
    public static string Token(HttpContext ctx)
    {
        var secret = ctx.RequestServices.GetRequiredService<IConfiguration>()["OpsIQ:SiteSecret"];
        if (string.IsNullOrEmpty(secret)) secret = "opsiq_whsec_YOUR_SITE_SECRET";   // this site's secret; configuration wins when set
        if (string.IsNullOrEmpty(secret) || ctx.User.Identity?.IsAuthenticated != true) return "";
        var id = ctx.User.FindFirstValue(ClaimTypes.NameIdentifier) ?? "";      // REQUIRED
        var email = ctx.User.FindFirstValue(ClaimTypes.Email) ?? "";            // REQUIRED
        var creds = new SigningCredentials(new SymmetricSecurityKey(Encoding.UTF8.GetBytes(secret)), SecurityAlgorithms.HmacSha256);
        var now = DateTimeOffset.UtcNow;
        var payload = new JwtPayload {
            { "site_key", "YOUR_SITE_KEY" }, { "iat", now.ToUnixTimeSeconds() }, { "exp", now.AddSeconds(3600).ToUnixTimeSeconds() },
            { "authenticated", true }, { "platform", "dotnet" },
            { "customer", new Dictionary<string, object> { { "id", id }, { "email", email }, { "name", ctx.User.Identity?.Name ?? "" }, { "external_id", id } } },
        };
        return new JwtSecurityTokenHandler().WriteToken(new JwtSecurityToken(new JwtHeader(creds), payload));
    }

    // app.Use(OpsiqChat.Refresh) — the widget refreshing on the page it is on.
    public static async Task Refresh(HttpContext ctx, Func<Task> next)
    {
        if (string.IsNullOrEmpty(ctx.Request.Query["opsiq_identity_refresh"])) { await next(); return; }
        ctx.Response.Headers["Cache-Control"] = "no-store";
        var t = Token(ctx);
        if (t == "") { ctx.Response.StatusCode = 401; await ctx.Response.WriteAsJsonAsync(new { success = false, login_required = true }); return; }
        await ctx.Response.WriteAsJsonAsync(new { success = true, role = "customer", identity_token = t });
    }

    public static string Tag(HttpContext ctx)
    {
        var t = Token(ctx);
        var src = "https://YOUR-OPSIQ/widget.php?site_key=YOUR_SITE_KEY" + (t != "" ? "&identity_token=" + Uri.EscapeDataString(t) : "");
        return "<script async src=\"" + WebUtility.HtmlEncode(src) + "\" data-opsiq-widget=\"client-chat\"></script>";
    }
}

Ruby on Rails

1

Add gem "jwt" and run bundle install. This site's signing secret is already filled in, so the code works as pasted. To keep it out of the file, set OPSIQ_SITE_SECRET in the environment on the server instead: that value is used first. Keep this file on the server and never commit it to a public repository.

2

include OpsiqChat in ApplicationController.

3

In app/views/layouts/application.html.erb before </body>: <%= opsiq_chat_tag %>

app/controllers/concerns/opsiq_chat.rb
# app/controllers/concerns/opsiq_chat.rb — Gemfile: gem "jwt"
require "jwt"
require "cgi"

module OpsiqChat
  extend ActiveSupport::Concern

  included do
    before_action :opsiq_identity_refresh
    helper_method :opsiq_chat_tag
  end

  private

  def opsiq_chat_token
    secret = ENV["OPSIQ_SITE_SECRET"].presence || "opsiq_whsec_YOUR_SITE_SECRET"   # this site's secret; the environment wins when set
    return "" if secret.blank? || !respond_to?(:current_user, true) || current_user.nil?
    now = Time.now.to_i
    JWT.encode({
      site_key: "YOUR_SITE_KEY", iat: now, exp: now + 3600,
      authenticated: true, platform: "rails",
      customer: { id: current_user.id, email: current_user.email,          # REQUIRED
                  name: current_user.try(:name).to_s, external_id: current_user.id.to_s }
    }, secret, "HS256")
  end

  def opsiq_identity_refresh
    return unless params[:opsiq_identity_refresh].present?
    response.headers["Cache-Control"] = "no-store"
    t = opsiq_chat_token
    return render(json: { success: false, login_required: true }, status: :unauthorized) if t.blank?
    render json: { success: true, role: "customer", identity_token: t }
  end

  def opsiq_chat_tag
    t = opsiq_chat_token
    src = "https://YOUR-OPSIQ/widget.php?site_key=YOUR_SITE_KEY" + (t.present? ? "&identity_token=#{CGI.escape(t)}" : "")
    helpers.tag.script(nil, async: true, src: src, data: { opsiq_widget: "client-chat" })
  end
end

Java (Spring Boot)

1

Add io.jsonwebtoken:jjwt-api, jjwt-impl and jjwt-jackson (0.12+). This site's signing secret is already filled in, so the code works as pasted. To keep it out of the file, set opsiq.site.secret (for example from OPSIQ_SITE_SECRET) on the server instead: that value is used first. Keep this file on the server and never commit it to a public repository.

2

Replace currentUser() with your user lookup. The filter answers the refresh on every page; @ControllerAdvice exposes opsiqChatTag to views.

3

Thymeleaf layout before </body>: <th:block th:utext="${opsiqChatTag}"/>

OpsiqChat.java
// OpsiqChat.java — io.jsonwebtoken:jjwt-api / jjwt-impl / jjwt-jackson (0.12+)
import io.jsonwebtoken.Jwts;
import io.jsonwebtoken.security.Keys;
import jakarta.servlet.*;
import jakarta.servlet.http.*;
import java.io.IOException;
import java.net.URLEncoder;
import java.nio.charset.StandardCharsets;
import java.security.Principal;
import java.time.Instant;
import java.util.*;
import org.springframework.beans.factory.annotation.Value;
import org.springframework.stereotype.Component;
import org.springframework.web.bind.annotation.ControllerAdvice;
import org.springframework.web.bind.annotation.ModelAttribute;
import org.springframework.web.util.HtmlUtils;

@Component
@ControllerAdvice
public class OpsiqChat implements Filter {
    @Value("${opsiq.site.secret:opsiq_whsec_YOUR_SITE_SECRET}")   // this site's secret; opsiq.site.secret wins when set
    private String secret;

    /** WHO IS SIGNED IN — replace with your lookup: id, email, name. Null for a guest. */
    private Map<String, Object> currentUser(Principal p) {
        return p == null ? null : Map.of("id", p.getName(), "email", p.getName(), "name", p.getName());
    }

    String token(HttpServletRequest req) {
        Map<String, Object> u = currentUser(req.getUserPrincipal());
        if (u == null || secret.isEmpty()) return "";
        Instant now = Instant.now();
        return Jwts.builder()
            .claim("site_key", "YOUR_SITE_KEY").claim("authenticated", true).claim("platform", "java")
            .claim("customer", Map.of("id", u.get("id"), "email", u.get("email"), "name", u.get("name"),
                                      "external_id", String.valueOf(u.get("id"))))          // id + email REQUIRED
            .issuedAt(Date.from(now)).expiration(Date.from(now.plusSeconds(3600)))
            .signWith(Keys.hmacShaKeyFor(secret.getBytes(StandardCharsets.UTF_8)), Jwts.SIG.HS256)
            .compact();
    }

    @Override // the widget refreshing on the page it is on
    public void doFilter(ServletRequest request, ServletResponse response, FilterChain chain) throws IOException, ServletException {
        HttpServletRequest req = (HttpServletRequest) request;
        if (req.getParameter("opsiq_identity_refresh") == null) { chain.doFilter(request, response); return; }
        HttpServletResponse res = (HttpServletResponse) response;
        res.setHeader("Cache-Control", "no-store");
        res.setContentType("application/json");
        String t = token(req);
        if (t.isEmpty()) { res.setStatus(401); res.getWriter().write("{\"success\":false,\"login_required\":true}"); return; }
        res.getWriter().write("{\"success\":true,\"role\":\"customer\",\"identity_token\":\"" + t + "\"}");
    }

    @ModelAttribute("opsiqChatTag")
    public String tag(HttpServletRequest req) {
        String t = token(req);
        String src = "https://YOUR-OPSIQ/widget.php?site_key=YOUR_SITE_KEY" + (t.isEmpty() ? "" : "&identity_token=" + URLEncoder.encode(t, StandardCharsets.UTF_8));
        return "<script async src=\"" + HtmlUtils.htmlEscape(src) + "\" data-opsiq-widget=\"client-chat\"></script>";
    }
}

Go

1

Run: go get github.com/golang-jwt/jwt/v5. This site's signing secret is already filled in, so the code works as pasted. To keep it out of the file, set OPSIQ_SITE_SECRET in the environment on the server instead: that value is used first. Keep this file on the server and never commit it to a public repository.

2

Replace currentUser() with your session lookup, and wrap your router: http.ListenAndServe(addr, OpsiqChatRefresh(mux)).

3

Pass OpsiqChatTag(r) to your layout template and print it before </body>.

opsiq_chat.go
// opsiq_chat.go — go get github.com/golang-jwt/jwt/v5
package main

import (
    "encoding/json"
    "fmt"
    "html"
    "html/template"
    "net/http"
    "net/url"
    "os"
    "time"

    "github.com/golang-jwt/jwt/v5"
)

type OpsiqUser struct{ ID, Email, Name string }

// WHO IS SIGNED IN — replace with your session lookup. Return nil for a guest.
func currentUser(r *http.Request) *OpsiqUser { return nil }

func opsiqChatToken(r *http.Request) string {
    u, secret := currentUser(r), os.Getenv("OPSIQ_SITE_SECRET")
    if secret == "" {
        secret = "opsiq_whsec_YOUR_SITE_SECRET" // this site's secret; the environment wins when set
    }
    if u == nil || secret == "" {
        return ""
    }
    now := time.Now().Unix()
    t, err := jwt.NewWithClaims(jwt.SigningMethodHS256, jwt.MapClaims{
        "site_key": "YOUR_SITE_KEY", "iat": now, "exp": now + 3600,
        "authenticated": true, "platform": "go",
        "customer": map[string]any{"id": u.ID, "email": u.Email, "name": u.Name, "external_id": fmt.Sprint(u.ID)}, // id + email REQUIRED
    }).SignedString([]byte(secret))
    if err != nil {
        return ""
    }
    return t
}

// OpsiqChatRefresh answers the widget's ?opsiq_identity_refresh=1 on any page.
func OpsiqChatRefresh(next http.Handler) http.Handler {
    return http.HandlerFunc(func(w http.ResponseWriter, r *http.Request) {
        if r.URL.Query().Get("opsiq_identity_refresh") == "" {
            next.ServeHTTP(w, r)
            return
        }
        w.Header().Set("Cache-Control", "no-store")
        w.Header().Set("Content-Type", "application/json")
        if t := opsiqChatToken(r); t != "" {
            json.NewEncoder(w).Encode(map[string]any{"success": true, "role": "customer", "identity_token": t})
            return
        }
        w.WriteHeader(http.StatusUnauthorized)
        json.NewEncoder(w).Encode(map[string]any{"success": false, "login_required": true})
    })
}

// OpsiqChatTag is printed before </body> in your layout.
func OpsiqChatTag(r *http.Request) template.HTML {
    src := "https://YOUR-OPSIQ/widget.php?site_key=YOUR_SITE_KEY"
    if t := opsiqChatToken(r); t != "" {
        src += "&identity_token=" + url.QueryEscape(t)
    }
    return template.HTML(`<script async src="` + html.EscapeString(src) + `" data-opsiq-widget="client-chat"></script>`)
}

Wakati kuna kitu kibaya

Chat inachukua watumiaji katika mteja kama mgeni

tag ilikuwa kuchapishwa bila ya identity_token (siri ni kukosa kwenye server, hivyo msimbo inashindwa kufungwa), au ufunguo wa kazi ishara au siri haina mechi.

Baada ya hapo, mtu huyo aliamka baada ya saa moja hivi.

Kivinjari cha kuburudisha hakifikiwa: lazima iendeshe kabla ya matokeo yoyote, kwenye kila ukurasa gumzo linaonekana.

Video ya wimbo wa skanning inaonyesha mara mbili

Ondoa lebo ya wazi ya kuzungumza kutoka kwa template yako: msimbo huu unachapisha chat yenyewe.

Developer ya developer

Plugins na SDK

OpsIQ Kutoa SDK Plugins kwa ajili ya majukwaa ya kawaida.

Jinsi ya kufanya kazi
Plugins na SDKPakiti nne: PHP SDK, Node.js SDK, WordPress Plugin na WHMCS moduli, kila moja na amri yake kufunga.PHPPHP SDKWaandishi wa habari wanahitajika opsiq/sdkJSJJSDKNPM katika @opsiq/sdkWP ya WPWordPress Plugin ya pluginBonyeza install & connectya waWHMCS Moduli ya moduliOngeza kwenye billing + tiketi ya relay
Plugins & SDKs ya
PHP SDK

Kifurushi cha Composer: kizazi cha ishara ya utambulisho, hatua API wasaidizi, uhakiki wa saini ya wavuti.

JavaScript SDK

Upande wa kivinjari: kufuatilia, utambulisho, matukio ya desturi, udhibiti wa mazungumzo.

WordPress Plugin ya plugin

Widget sindano, utambulisho kutoka vikao vya mtumiaji wa WP, WooCommerce sync.

WHMCS Moduli ya moduli

Ushirikiano kamili: widget, tiketi ya relay, utambulisho, admin AI.

Shopify Mandhari ya ugani

App inaunganishwa na utambulisho wa wateja moja kwa moja.

PHP SDK kuanza haraka

PHP SDK mfano
composer require opsiq/sdk

use OpsIQ\SDK\Identity;
$token = Identity::createToken(
    siteKey: "site_abc123",
    secret:  "opsiq_whsec_your_secret",
    customer: ["id" => "cust_1001", "email" => "[email protected]", "name" => "Jane"]
);

// Call any catalog action over the action API
$ch = curl_init("https://your-opsiq.com/api/v1.php");
curl_setopt_array($ch, [
    CURLOPT_POST => true,
    CURLOPT_RETURNTRANSFER => true,
    CURLOPT_HTTPHEADER => [
        "Authorization: Bearer opq_your_key",
        "Content-Type: application/json",
    ],
    CURLOPT_POSTFIELDS => json_encode([
        "action" => "crm.contacts.list",
        "status" => "lead",
        "limit"  => 25,
    ]),
]);
$contacts = json_decode(curl_exec($ch), true);
Developer ya developer

Utafiti wa utafiti API Matukio na automatisering ya bure ya kontakt

Studio ya Utafiti imeundwa kutumia Mkuu wa Aina hiyo API, executor ya ndani, basi la tukio na shughuli za mtandao kama wengine wa OpsIQ Hii inaruhusu watengenezaji kuunganisha mwisho bila kujenga kontakt packaged.

⚠️
Hali ya utekelezaji: Orodha ya kuishi sasa inaonyesha tu platform.get.survey.config Na kwa kuwa platform.save.survey.configya The surveys.* Na kwa kuwa feedback.* Nchi zilizo chini ya mkataba wa makubaliano ni lazima zirudi unknown_action mpaka itakapothibitishwa.

Familia za hatua

Aina, templates na uzinduzi wa haraka

surveys.types.*, surveys.templates.* Na kwa kuwa surveys.quick_launch.* Orodha, preview, instantiate na kuthibitisha kamili ya kuanza.

Utafiti na tafsiri

surveys.create|get|list|update|archive|duplicate pamoja na toleo lisilobadilika, uthibitisho na kuchapisha vitendo.

Kuajiriwa na kupangiwa

surveys.deployments.*, surveys.links.*, surveys.audiences.*, surveys.triggers.* Na kwa kuwa surveys.variables.*.

Kuwasili na majibu

surveys.invitations.*, surveys.campaigns.*, surveys.recipients.*, surveys.responses.*- mauzo ya nje, redaction na analytics.

Webhooks, kuagiza na maoni

surveys.webhooks.*, surveys.imports.*, feedback.items.*, feedback.analytics.*, feedback.sources.* Na kwa kuwa feedback.analysis.*.

Kuunganisha Free

1
Kuandaa na kuwasilisha kwa ujumla API

Tumia tafiti zilizoandaliwa. * vitendo na ufunguo wa kazi-kufungwa. Andika ruhusa ya kutangaza, hatari, uthibitisho, upungufu na tabia ya kukimbia kavu.

2
Kupata Tukio la Biashara yako

Tuma tukio lililosainiwa kwenye wavuti iliyoingia, kwa mfano kufuta amri au kukamilika hatua ya kuingia. Ulinzi wa Replay unazuia kitambulisho cha tukio.

3
Kuiweka katika vitendo na waendelezaji

Chagua moja OpsIQ Jenerali Mkuu API Hatua kama vile kutoa mwaliko wa Utafiti au kuandaa kampeni, kisha ramani ya mashamba kutoka kwa mzigo wa malipo uliothibitishwa.

4
Kujiunga na matukio ya utafiti

Kutoa kumbukumbu ya utafiti salama wa biashara. * Lifecycle subset kwa mwisho wako na saini, filter, retry, log na replay mamlaka

Mradi wa Canon

Orodha ya pamoja itafikia Utafiti / Uhamisho wa kuchapisha hali, watazamaji na kusababisha maamuzi, mialiko, kutoa / kuanza / sehemu / kamili / ndoa, majibu ya hatua, hali ya kampeni na kushindwa kwa utoaji. High-volume lengo, kitabu na swali muda kukaa katika Hifadhi ya Analytics ya Survey isipokuwa wazi kumbukumbu kwa shabiki nje.

Munganisho ni wa hiari. Inaongeza ugunduzi wa jukwaa unaoweza kupatikana, utambulisho uliothibitishwa, ukweli, vigezo na uunganishaji wa mpokeaji. Jenerali API pamoja na Hatua & Triggers / wavuti bado njia kamili ya ushirikiano kwa watengenezaji ambao hawahitaji kontakt iliyowekwa.
Developer ya developer

ya ya API

Kwa kuwa OpsIQ Radha API Inakuwezesha kufikia vipengele vyote vya jukwaa.

Jinsi ya kufanya kazi
ya ya APIMwisho wa barua pepe kuonyesha ujumbe OpsIQ API Kwa ufunguo wa Bearer, orodha ya tiketi za wazi, na paged JSON majibu.$ curl -X POST https://your-domain.com/api/v1.php \-H "Authorization: Bearer opq_..."200 OK{ "data": [{ "id": 4192, "ticket_number": "T-4192","subject": "Card declined", "status": "open" },... more tickets ...], "page": 1, "per_page": 50, "has_more": true }
ya ya API

Fomu ya maombi

Tumia kichwa kama Authorization: Bearer opq_... au X-OpsIQ-Key: opq_...Tumia kichwa kimoja cha uthibitisho, sio vyote viwili.

API Fomu ya maombi
POST https://your-opsiq-domain.com/api/v1.php
Authorization: Bearer opq_your_api_key
# Alternative header: X-OpsIQ-Key: opq_your_api_key
Content-Type: application/json

{
  "action": "endpoint.name",
  "site_key": "site_abc123"
}

Vitendo vya kawaida

Kwa kuwa API Hatua kwa hatua: kutuma action Kila msimamizi aliyesajiliwa JSON operesheni ina jina imara. {"action":"meta.actions"} (Hakuna ufunguo unaohitajika) kwa orodha ya mamlaka, kwa kila-programu, ombi la mkataba, metadata hatari na upeo. platform.routes.* Daraja bado ni kwa ajili ya ushirikiano wa zamani.

crm.contacts.list

Orodha ya mawasiliano CRM (scope crm. read). Params: q, hadhi, chanzo, tag, alama ya kuongoza, kikomo.

crm.contacts.upsert

Suluhisho-au-kuunda mawasiliano (scope crm. write). Params: barua pepe pamoja na mashamba, vitambulisho, maelezo.

crm.deals.list

Orodha ya CRM mikataba (scope crm. read). Params: hali, hatua_id, kampuni_id , mmiliki_admin_id na bomba_id.

crm.activities.record

Rekodi shughuli ya mzunguko wa maisha / biashara kwa mawasiliano (scope crm. write). Params: barua pepe au contact_id, tukio, thamani, sarafu.

crm.conversions.record

Rekodi uongofu (scope crm. write). Params: contact_id au barua pepe, uongofu_aina, thamani, sarafu.

crm.events.list

Chagua mkondo wa tukio la CRM (scope crm. read). Params: kikomo.

tickets.list

Orodha ya tiketi (scope tickets. read). Params: ukurasa, per_page, aina, utaratibu, hali, kipaumbele, idara_id, assigned_admin_id , mteja_email, utafutaji.

tickets.get

Tiketi moja na ujumbe wake (scope tickets. read). Params: tiketi_id au tiketi_number, ni pamoja na ujumbe wa_limit, ujumbe_limiss.

tickets.reply

Tuma jibu kwa tiketi (scope tickets. write). Params: tiketi_id au tiketi_number, mwili, mwandishi_type, mwandishi-jina, ndani.

tickets.update

Sasisha tiketi (scope ticket. write). Params: tiketi_id au tiketi_number, hadhi, kipaumbele, somo, idara_id, assigned_admin_id.

tickets.open

Fungua tiketi ya usaidizi (scope tickets. write). Params: customer_email, customer_name, subject, body, priority.

tickets.bulk

Tumia operesheni ya foleni kubwa (scope tickets. write). Params: uendeshaji, ids.

conversations.list

Orodha ya mazungumzo ya kuishi (majadiliano ya macho. soma). Params: ukurasa, per_page, hadhi, aliyepewa_admin_id, mteja_email, utafutaji.

conversations.get

Mazungumzo moja na ujumbe wake (mazungumzo ya sauti. soma). Params: mazungumzo_id au thread_key, ni pamoja na ujumbe wa_.

conversations.messages

Ukurasa wa historia ya ujumbe (majadiliano ya macho. soma). Params: mazungumzo_id, ukurasa, per_page, ni pamoja na_internal.

conversations.send

Tuma ujumbe katika mazungumzo (majadiliano ya sauti. andika). Params: mazungumzo_id, ujumbe, kutuma_aina, ndani.

conversations.update

Assign, re-status au upya kichwa mazungumzo (majadiliano ya macho. write). Params: mazungumzo_id, hadhi, assigned_admin_id , somo.

connectors. list /. kupata /,mtihani

Angalia ni viunganisho gani vilivyowekwa, kila mtu anaweza kufanya nini, na ikiwa hati zake za utambulisho zinafanya kazi (viungo vya scope. read).

automations.actions.list

Hatua ambazo wajenzi wako wa vitendo wataendesha (scope automatiserings. read).

automations.triggers.list

Ni nini kinachowaka na juu ya hali gani (scope automatisering. read).

automations.runs.list

Utekelezaji wa historia kwa ajili ya kufuta ushirikiano (scope automatiserings. read). Params: hali, action_key.

departments.list

Idara unaweza njia ya tiketi kwa (scope idara. read).

notifications.list

Taarifa kwa operator mmoja (scope notifications. read). Params: admin_id (inahitajika), un-unlimited_only.

analytics.export

Sehemu ya ripoti kama CSV (scope analytics. read). Params: sehemu, kabla, kutoka, hadi. wito analytics. sections. list kwa maadili halali.

Tovuti_intelligence. sites. list/ . reports. list

Tovuti zilizofuatiliwa na ripoti zao za SEO (scope tovuti_intelligence. read).

Biashara. com/Business. com

Orodha yako ya Hifadhi, paged (biashara ya scope. read). Filters: kazi, jamii, utafutaji. .get Inarudi bidhaa moja na tofauti zake.

Biashara. com/. get

Amri za duka (scope biashara. read). Filters: hali, malipo_method, channel, mteja_email. order_id au kumbukumbu yake ya ORD, na vitu vya mstari. kushughulikia kwa njia ya lango la moja kwa moja hairudi kamwe.

commerce.refunds.list

Kurejesha maombi na hali yao (biashara ya eneo. read).

commerce.quotes.create

Bei ya bidhaa kwa mteja (scope trade. write). store Au bofya kifungo cha kuingia ili uone baadhi ya vipengele.

tiketi za ndege.csatOrodha ya / .get/metris

Majibu ya kuridhika kwa wateja kama data (scope tiketi. read). Filter na rating, tiketi, wakala au kipindi; .metrics Inarudi idadi sawa ya dashibodi inaonyesha.

conversations.ratings.list

Kuzungumza mazungumzo wageni wako lilipimwa, na maoni, nini ilisababisha rating na wakala sifa (scope mazungumzo. read).

knowledge.articles.list

Ukurasa kupitia makala yako ya Kituo cha Msaada (scope kb. read).

knowledge.articles.get

Makala moja ya Kituo cha Msaada kwa id (scope kb. read). Params: makala_id.

webhooks.events.list

Kila tukio unaweza kujiunga na mwisho wa wavuti, na mzigo wake wa malipo. Inapatikana kwenye kila mpango, ili uweze kujenga dhidi yake kabla ya kununua.

files.get

Kiungo cha kupakua kilichosainiwa kwa kiungo cha attachment (scope files. read). Params: kumbukumbu, ttl.

security.check

kuuliza kama kuna IP Au barua pepe imefungwa au tuhuma hapa (scope security.read).IP firewall, orodha ya spam ya tiketi na hukumu ya usalama wa cached. Params: ip Kwa njia ya email.

security.report

R ip oti unyanyasaji mfumo wako aliona (scope security.write). Rekodi kama tukio la usalama, classified na Usalama AI mara moja, na admins ni kuarifiwa juu ya hukumu high-hatari.ip Barua pepe, aina, sababu, chanzo.

Usalama. blocklist. add / . list

Kusimamia sheria za spam bomba la tiketi kutekeleza (usalama wa tovuti.write / usalama.read). duka moja kama ukurasa wa Tiketi "Block sender" udhibiti. Params: aina (Email, domain, nk)ip^ Tnn., “kwa sababu ya thamani, muda wa saa.”

💡
Meta. actions ni mamlaka kila wakati. Inarudi kila hatua inapatikana kwenye ufungaji wako na upeo wa mahitaji ya kila mmoja, hivyo huna kamwe nadhani au kwa bidii-code orodha hii.

Kupumua, kuchuja na kuchagua

Kila hatua ya orodha hutumia vigezo sawa, kwa hivyo unajifunza mara moja.

Ukurasa wa Tovuti / ukurasa

Ukurasa wa kuanza 1Ukubwa wa ukurasa. Default 50 Kiwango cha juu 200· Masharti na masharti pia yanakubaliwa kama unayapendelea.

Kujiandaa / Order

Kila hatua inakubali seti ya aina fulani; kitu kingine chochote kinapuuzwa badala ya kukosea.

filters

Tuma filters kama kitu, au kupitisha chujio kama parameter ya ngazi ya juu. Vichujio visivyojulikana hupuuzwa.

Nini cha kufanya nyuma

Vitu, ukurasa, per_page, kuhesabu, jumla na has_more. Endelea kuomba kurasa mpaka ina_ zaidi ni uongo.

Ukurasad, filtered, orodha ya maombi
POST /api/v1.php
Authorization: Bearer opq_your_api_key

{
  "action": "tickets.list",
  "status": "open",
  "priority": "urgent",
  "sort": "created_at",
  "order": "desc",
  "page": 1,
  "per_page": 50
}

Makosa ya

Kila kushindwa kurudi sura sawa, na imara code Unaweza kuwa na uhakika kwamba huwezi kupata juu ya mtu. error maandishi, ambayo yanaweza kutafsiriwa.

Majibu ya makosa
{
  "success": false,
  "code": "missing_scope",
  "error": "API key missing required scope. Needed one of: tickets.read, admin",
  "request_id": "req_8f2c1a9d4b7e"
}
Kukosekana kwa api_key/ invalid_api_

Hakuna ufunguo uliotumwa, au ufunguo ni sahihi au umemalizika. HTTP 401.

missing_scope

Muhimu ni halali lakini haina upeo wa hatua hii inahitaji. HTTP 403.

Soma_only_key / Hatua ya Kurudishwa

Funguo ni kusoma tu, au hatua hii haipo kwenye orodha yake ya kuruhusu. HTTP 403.

unknown_action

Hakuna hatua kama hiyo. piga meta.actions kwa orodha ya sasa. HTTP 400.

Upotoshwaji wa Picha/Stream/Tirms

parameter inahitajika haipo, au thamani haikubaliwa. HTTP 400.

not_found

Rekodi haipo, au haipo katika nafasi ya kazi ufunguo huu unaweza kuona. HTTP 404.

plan_feature_locked

Mpango wako haujumuishi kipengele hiki ni cha. mwili unataja jina la featureKwa hiyo, plan_name Kwa nguvu na kwa upgrade_urlKujaribu hakutasaidia; mpango lazima ubadilike. HTTP402.

license_required

Leseni ya ufungaji haifanyi kazi, kwa hivyo hakuna hatua itaendesha mpaka irudishwe. HTTP402.

selling_paused

maalum ya biashara: duka limeuza kuzima, kwa hivyo hakuna chochote kinachoweza kunukuliwa au kuamuru. HTTP400.

rate_limited

Kikomo cha saa kwa ufunguo huu kinatumiwa. HTTP 429.

server_error

Kitu kilichoshindwa upande wetu. ombi_id linabainisha jaribio ikiwa unahitaji kuripoti. HTTP 500.

Uhakikisho wa usalama

Kama una muda wa kuandika nje, huwezi kujua kama ni kuwasili. idempotency_key Na kurudia wito huo kunarudisha matokeo ya awali badala ya kufanya kazi mara mbili.

Kuandika kwa usahihi
{
  "action": "tickets.reply",
  "ticket_id": 4192,
  "body": "Thanks, that is now fixed.",
  "idempotency_key": "your-unique-id-for-this-attempt"
}
Inachukua muda gani

Jambo la muhimu kukumbuka ni kuwa 24 kwa muda mrefu dhidi ya vitendo hivyo na API ya muhimu.

Nini cha kufanya nyuma

Jibu la awali, pamoja na idempotent_replay: kweli ili uweze kusema ni replay.

Kushindwa kuendelea kuwa na uwezo

Kama wito ulishindwa, kutuma tena na ufunguo huo huendesha tena, ambayo ni nini unataka.

Kusoma kwa

Kusoma ni kupuuza muhimu, kurudia kusoma ni kinyume.

Jaribio la jaribio bila kubadilisha chochote

Ongeza dry_run: true Muhimu wako, mawanda na vigezo vyote vinaangaliwa kama kawaida, kisha simu huacha kabla ya chochote kilichoumbwa au kubadilishwa.

Kukausha kukimbia: kuthibitisha sifa na malipo salama
{
  "action": "tickets.update",
  "ticket_id": 4192,
  "status": "closed",
  "dry_run": true
}

{
  "success": true,
  "dry_run": true,
  "would_execute": true,
  "message": "Authorised and validated. No write was performed because dry_run was set."
}
Tumia kavu_run wakati unajenga. Ni njia ya haraka zaidi ya kuthibitisha ufunguo ina mawanda sahihi na mzigo wako wa malipo umeundwa kwa usahihi, bila kuunda data ya mtihani unayotakiwa kusafisha.

Kiwango cha ukomo

Kiwango cha chini cha

Kiwango cha chini kwa saa moja API Kuondolewa (Default) 1000 Tumia kwa muda wa saa moja.API ya Keys.

Wakati wa kukomaa

HTTP 429 na code rate_limited, plus Retry-Baada ya header kukuambia jinsi sekunde kadhaa kusubiri. kikomo resets juu ya saa kesho saa.

Kujua ambapo wewe ni

Kila jibu hubeba X-RateLimit, X-Remaining na X-LateLim-Reset (kiasi cha Unix) Kukaa na kupungua polepole kabla ya kukimbia badala ya kusubiri kukataliwa.

Kueleza 429 Kutoka kwa 401

A 429 inamaanisha kusubiri na kujaribu tena. A 401 ina maana ufunguo mwenyewe ni mbaya au umemalizika, kwa hivyo kujaribu hakutasaidia hadi utakaporekebisha ufunguo.

Ulinzi wa Jeshi la Polisi

Jaribio la mara kwa mara la kushindwa kutoka kwa mtu mmojaIPWao ni tofauti sana, na kamwe funguo za Valid hazisafiri hii.

Mazoezi bora ya mazoezi

Kurejea wakati Kukaa anapata chini, na heshima Retry-baada ya 429 badala ya kujaribu mara moja.

Tafsiri na utulivu

Toleo la sasa

(b) Kila jibu linatolewa na X-OpsIQ-API Kwa mfano, X-OpsIQ-API Jaribu kuwa na uhakika wa kile unachozungumza.

Jinsi ya Kukumbuka

Ikiwa toleo limewahi kustaafu, majibu hupata vichwa vya kawaida vya Deprecation na Sunset, na ripoti za meta. hatua zimepunguzwa na jua_at. Angalia wale katika ufuatiliaji wako na hautashangaa kamwe.

Nini cha kufanya si kubadilika

Majina ya vitendo, vigezo vyao na nambari zao za makosa. Vitendo vipya na mashamba mapya ya hiari yanaweza kuongezwa wakati wowote, kwa hivyo kupuuza maeneo ambayo hutambua badala ya kushindwa kwao.

Kukamilika kwa Muungano, kuanza

Hii ni kitanzi nzima: kupata kazi, kusoma, kutenda juu yake, na kuthibitisha nini ulifanya.

Full tiketi ya ndege juu ya API
# 1. Discover what this install offers and what each action needs.
POST /api/v1.php
{"action":"meta.actions"}

# 2. Find the urgent open tickets.
POST /api/v1.php
Authorization: Bearer opq_your_api_key
{"action":"tickets.list","status":"open","priority":"urgent","per_page":25}

# 3. Read one, including its conversation history.
{"action":"tickets.get","ticket_id":4192}

# 4. Reply, safely enough to retry if the network drops.
{"action":"tickets.reply","ticket_id":4192,
 "body":"We have issued the refund.","idempotency_key":"reply-4192-attempt-1"}

# 5. Close it.
{"action":"tickets.update","ticket_id":4192,"status":"closed"}

# 6. Page through anything larger: keep going until has_more is false.
{"action":"tickets.list","page":2,"per_page":50}
💡
Kila kitu juu kazi njia moja kwa mazungumzo: conversations. list, conversations. get, conversation. send na conversations, update kufuata mfano sawa, vigezo na sura ya majibu.

Mifano ya kazi zaidi

Kila moja ya haya ni kipande kamili, kinachozunguka cha ushirikiano halisi badala ya kipande.

Ukurasa kupitia kila rekodi, katika lugha tatu

Kanuni ni sawa kila mahali: Endelea kuomba ukurasa unaofuata hadi mwisho. has_more Ni uongo, kamwe usifikiri kuwa ni jambo la kawaida.

Python · Ukurasa kupitia kila tiketi ya wazi
import requests

API  = "https://your-opsiq-domain.com/api/v1.php"
HEAD = {"Authorization": "Bearer opq_your_api_key"}

def every(action, **params):
    """Yield every record for a list action, one page at a time."""
    page = 1
    while True:
        r = requests.post(API, headers=HEAD,
                          json={"action": action, "page": page, "per_page": 200, **params},
                          timeout=30)
        r.raise_for_status()
        body = r.json()
        if not body.get("success"):
            raise RuntimeError(f"{body.get('code')}: {body.get('error')}")
        yield from body.get("items", [])
        if not body.get("has_more"):
            return
        page += 1

for ticket in every("tickets.list", status="open"):
    print(ticket["ticket_number"], ticket["subject"])
Ukurasa wa · Kila ukurasa kupitia kila mwongozo
const API = "https://your-opsiq-domain.com/api/v1.php";
const HEAD = { Authorization: "Bearer opq_your_api_key", "Content-Type": "application/json" };

async function* every(action, params = {}) {
  for (let page = 1; ; page++) {
    const res  = await fetch(API, {
      method: "POST",
      headers: HEAD,
      body: JSON.stringify({ action, page, per_page: 200, ...params }),
    });
    const body = await res.json();
    if (!body.success) throw new Error(`${body.code}: ${body.error}`);
    yield* body.items ?? [];
    if (!body.has_more) return;
  }
}

for await (const contact of every("crm.contacts.list", { status: "lead" })) {
  console.log(contact.email);
}
PHP · Ukurasa kupitia kila tiketi ya wazi
<?php
$api = "https://your-opsiq-domain.com/api/v1.php";

function opsiq(string $action, array $params = []): array {
    global $api;
    $ch = curl_init($api);
    curl_setopt_array($ch, [
        CURLOPT_POST           => true,
        CURLOPT_RETURNTRANSFER => true,
        CURLOPT_HTTPHEADER     => [
            "Authorization: Bearer opq_your_api_key",
            "Content-Type: application/json",
        ],
        CURLOPT_POSTFIELDS => json_encode(["action" => $action] + $params),
        CURLOPT_TIMEOUT    => 30,
    ]);
    $body = json_decode((string)curl_exec($ch), true) ?: [];
    curl_close($ch);
    if (empty($body["success"])) {
        throw new RuntimeException(($body["code"] ?? "error") . ": " . ($body["error"] ?? "unknown"));
    }
    return $body;
}

$page = 1;
do {
    $res = opsiq("tickets.list", ["status" => "open", "page" => $page, "per_page" => 200]);
    foreach ($res["items"] as $t) {
        echo $t["ticket_number"], " ", $t["subject"], PHP_EOL;
    }
    $page++;
} while (!empty($res["has_more"]));

Kutatua kila kushindwaAPIUnaweza kurudi

Ofisi ya Tawi codeKamwe, kamwe, kwa maneno ya error“Mkataba huu ni wa mkataba wote katika kazi moja.

Python · Mteja ambaye anashughulikia kila msimbo wa makosa kwa usahihi
import time, requests

RETRYABLE = {"server_error", "handler_unavailable"}

def call(action, **params):
    for attempt in range(4):
        r = requests.post(API, headers=HEAD, json={"action": action, **params}, timeout=30)
        body = r.json()
        if body.get("success"):
            return body

        code = body.get("code")

        if code == "rate_limited":
            # Honour Retry-After rather than guessing.
            time.sleep(int(r.headers.get("Retry-After", 60)))
            continue

        if code in RETRYABLE:
            time.sleep(2 ** attempt)
            continue

        # Everything below is permanent: retrying cannot fix it.
        if code == "plan_feature_locked":
            raise RuntimeError(f"Plan {body['plan_name']} lacks {body['feature']}: {body['upgrade_url']}")
        if code in ("missing_scope", "read_only_key", "action_restricted"):
            raise RuntimeError(f"This API key cannot do that: {body['error']}")
        if code in ("invalid_api_key", "missing_api_key"):
            raise RuntimeError("The key is wrong or expired; retrying will not help.")
        raise RuntimeError(f"{code}: {body.get('error')} (request_id {body.get('request_id')})")

    raise RuntimeError("Gave up after repeated retries")

Kusubiri matokeo mabaya katika muda wa saa moja.

Soma alama za chini, fungua tiketi kwa kila mmoja, na usifanye hivyo mara mbili.

Kufungia kwa wateja wasio na furaha
# 1. Yesterday's detractors.
POST /api/v1.php
{"action":"tickets.csat.list","filters":{"max_rating":2},"days":1,"per_page":100}

# 2. For each one, open a follow-up ticket. The idempotency key is derived
#    from the response id, so re-running the job creates nothing twice.
POST /api/v1.php
{"action":"tickets.open",
 "customer_email":"[email protected]",
 "subject":"Following up on your feedback",
 "body":"We saw your rating and want to put it right.",
 "priority":"high",
 "idempotency_key":"csat-followup-8821"}

# 3. The same shape works for chat: conversations.ratings.list with
#    {"filters":{"max_stars":2},"days":1} returns the comment, what
#    prompted the rating and which agent it is credited to.

Andika swali na ufanyie kazi kwenye jibu la muuzaji

Kukataa kunakuambia nini cha kukusanya
POST /api/v1.php
{"action":"commerce.quotes.create","source":"whmcs","item_id":"47","quantity":1}

# The merchant needs more from the customer before it can price this:
{
  "success": false,
  "code": "quote_refused",
  "error": "We need the domain this hosting plan is for.",
  "actionable": true,
  "missing": ["domain"]
}

# Ask the customer for exactly what "missing" names, then quote again.
POST /api/v1.php
{"action":"commerce.quotes.create","source":"whmcs","item_id":"47",
 "fields":{"domain":"example.ng"}}

{
  "success": true,
  "source": "whmcs",
  "quote": {
    "quote_id": "…",
    "totals": { "total": { "amount_minor": 306027, "currency": "NGN" }, "currency": "NGN" },
    "expires_at": "2026-09-05T12:34:56+00:00"
  },
  "ordering": { "creates_order": false, "confirm_via_api": false }
}
⚠️
Onyesha wateja totals.total Idadi haizidi bei ya kitengo - hoteli inanukuu chumba kimoja kwa usiku tatu - hivyo takwimu unayohesabu inaweza kutofautiana na kile mfanyabiashara atachotoza.

Ni salama kwa mtumiaji wa mtandao ambao ni salama kuendesha katika uzalishaji

Kuthibitisha, de-duplicate, jibu haraka, kisha kufanya kazi. kutoa retry, hivyo tukio hilo linaweza kufika zaidi ya mara moja.

PHP · Msaidizi wa Webhook wa uzalishaji
<?php
// (verification exactly as in the Webhooks section, omitted here for brevity)

$event    = json_decode($raw, true);
$name     = $_SERVER["HTTP_X_OPSIQ_EVENT"] ?? ($event["event"] ?? "");
$delivery = $_SERVER["HTTP_X_OPSIQ_DELIVERY"] ?? "";

// 1. Already seen this delivery? Say OK and stop — do not redo the work.
if ($db->alreadyProcessed($delivery)) {
    http_response_code(200);
    exit(json_encode(["ok" => true, "duplicate" => true]));
}

// 2. Answer FAST. Anything slow belongs on your own queue: OpsIQ treats a
//    timeout as a failure and will retry the whole delivery.
$db->markProcessed($delivery);
$queue->push($name, $event);

http_response_code(200);
echo json_encode(["ok" => true]);

// 3. Your worker then routes on the event name.
//    conversation.rated        -> alert the team on a 1 or 2 star rating
//    ticket.created            -> mirror into your own helpdesk
//    crm.deal.won              -> post to #sales-alerts
//    commerce.payment.confirmed-> release the order in your fulfilment system

Mipango na Haki za

Kila hatua ni ya kipengele cha bidhaa, na mpango wako anaamua ambayo makala una. Kama mpango wako haina pamoja na kipengele, majibu ya vitendo 402 - baada ya ufunguo wako kuchunguzwa, hivyo mpiga simu asiye na uzoefu hajui chochote kuhusu mpango wako, na kabla ya kitu chochote kuundwa, kwa hiyo kuandika imefungwa kamwe nusu saa.

Hatua ya mpango
{
  "success": false,
  "code": "plan_feature_locked",
  "feature": "commerce",
  "plan_locked": true,
  "plan_name": "Growth",
  "upgrade_url": "https://…",
  "request_id": "req_8f2c1a9d4b7e"
}
Jinsi ya kufanya hivyo mbali na matatizo ya ruhusa

A ya403Ina maana KEY ni nyembamba sana - kuiweka kwa upana sahihi na inafanya kazi.402Ina maana ACCOUNT haina kipengele - hakuna ufunguo unaweza kufungua, mpango lazima ubadilike.

Usifanye kazi ya A402

Hakuna cha maana, ni juu ya ardhi upgrade_url Kwa yeyote atakaye nunua kitu kwa mkono wake, basi ni halali kwake kukitwaa.

Mfumo wa utawala hauruhusu

Scopes zinaonyesha nini mtoa muhimu aliyetumwa; mpango unaonyesha kile akaunti ilinunuliwa. ufunguo wa admin-kupatikana bado anapata 402 kwa kipengele mpango unakosa.

Kujua kabla ya meli

Kwa kuwa feature Kila hatua ya kazi itachapishwa katika saraka ya utendaji hapa chini na meta.actionKwa hiyo, unaweza kuangalia wakati wa kujenga badala ya kugundua katika uzalishaji.

Njia ya haraka zaidi ya kuona ambapo ufunguo ni meta.meInaripoti mpango wa nguvu, kila kipengele kinachobeba, na kila hatua muhimu hii haiwezi kuita kwa sababu ya kila mmoja.

meta. me — nini muhimu hii inaweza kweli kufanya
POST /api/v1.php
Authorization: Bearer opq_your_api_key

{"action":"meta.me"}

{
  "success": true,
  "key": { "name": "Reporting", "scopes": ["tickets.read"], "permissions_mode": "read_only" },
  "plan": { "name": "Growth", "features": { "ticket_system": true, "commerce": false } },
  "capabilities": {
    "available_action_count": 812,
    "blocked_actions": {
      "commerce.orders.list": "plan_locked:commerce",
      "tickets.reply":        "read_only"
    }
  }
}
Piga simu meta. me kwanza wakati ushirikiano unafanya tofauti kati ya mitambo miwili. Inajibu "kwa nini ufunguo huu hauwezi kufanya hivyo" katika ombi moja, bila mtu yeyote kufungua admin.

Kuhesabu gharama

commerce.quotes.create Inaunda kitu kimoja kwa mteja mmoja. Haifanyi chochote - hakuna amri, kikao cha malipo, hakuna hisa iliyoshikiliwa - hivyo ni salama kupiga simu wakati mteja bado anaamua.

Kusahau kitu kimoja
POST /api/v1.php
Authorization: Bearer opq_your_api_key

# Your own Store
{"action":"commerce.quotes.create","source":"store","item_id":"12","quantity":2}

# A connected merchant platform, priced for a known customer
{"action":"commerce.quotes.create","source":"whmcs","item_id":"47",
 "fields":{"domain":"example.ng"},
 "customer":{"connector_customer_id":"1042"}}
Jumla ya ushindi wa mfanyabiashara

Kwa jukwaa kushikamana, jumla huja kutoka kwa mfanyabiashara huyo na ni kamwe recalated hapa. Wingi haina daima kuzidisha bei ya kitengo - hoteli quotes chumba kimoja kwa usiku tatu — hivyo kuonyesha jumla wewe walikuwa iliyotolewa, si moja wewe kazi nje.

Watangazaji wa habari wanasema nini kuhusu kupotea

Kama biashara inahitaji zaidi kutoka kwa wateja, unaweza kupata quote_refused Kwa kuwa A missing Orodha ya majina ya mashamba kukusanya, na maneno ya mfanyabiashara mwenyewe kuonyesha.

Amri sio yaAPIWito wa wito

quote ni indicative. uthibitisho hutokea ambapo mteja ni - kadi saini katika chat, au mfanyabiashara mwenyewe checkout – kamwe kupitia hii API majibu anasema hivyo katika ordering.

Wakati wa kununua hisa

Kama kampuni imeacha kuuza, ikinukuu majibu selling_paused Badala ya kununua kitu ambacho hakuna mtu anayeweza kukinunua.

Mwisho wa pointi nyingine

Karibu kila kitu unachohitaji ni barua moja. /api/v1.phpHizi ni tofauti, na kila mmoja ni kwa ajili ya nini.

/api/v1/openapi.php · /api/v1/postman.php · /api/docs/

Hakuna muhimu inahitajika, hivyo unaweza kuchunguza kabla ya kuwa na moja.

/api/ai_stream.php

Matukio ya ujumbe wa seva kwa majibu ya mazungumzo ya kuishi kama yanazalishwa. Mto, sio hatua ya JSON.

/api/writing.php

ya mwisho wa kuandika, kila kitu ambacho kinapatikana pia writing.* Hatua juu ya/api/v1.php,Hii ndio ambapo kazi mpya inapaswa kwenda.

/api/inbox_copilot.php

Rasimu, kuandika upya na triage kwa sanduku la tiketi lililoingia katika admin yako mwenyewe.

/api/v1/si/…

Ujasusi wa Tovuti kama REST ndogo API - tovuti, kutambaa, masuala, maneno muhimu, mapato - kwa mabomba ya CI ambayo yanahitaji kuanza kutambaa baada ya kupeleka na kusoma matokeo.

/api/connectors.php?slug=&token=

Ambapo jukwaa kushikamana POSTs yake mwenyewe webhooks na wewe. ishara ni minted wakati kuwezesha kontakt.

/api/integrations/*.php

Injini ya ushirikiano: kukimbia na kuthibitisha vitendo, na mauzo ya ingest, utambulisho na matukio ya safari. Inatumia aina yake muhimu, iliyotolewa chini yaAPI& Webhook wajenzi wa wavuti.

💡
Hizi zote zinatii sheria za mpango sawa na vitendo. Kipengele cha mpango wako haujumuishi majibu ya 402 hapa pia, katika sura moja.

Kila hatua, kwa kadiri ya uwezo wake unahitaji

Orodha hii ni yanayotokana na orodha ya kukimbia, hivyo daima inafanana na toleo wewe ni juu. meta.actions Kurudisha taarifa kama hiyo JSON.

2420 named actions: 804 reads, 1616 writes and 69 scopes. Every registered administrator JSON operation has a stable named action. OpenAPI: /api/v1/openapi.php. Postman: /api/v1/postman.php. Contract quality: declared_dynamic: 606; explicit: 63; route_inferred: 1633; source_inferred: 118.

administration (25)

administration.2fa.disable

Write. Scope: administration.write, admin. Contract: route_inferred. Admin 2fa Disable

administration.2fa.enable

Write. Scope: administration.write, admin. Contract: route_inferred. Admin 2fa Enable

administration.2fa.recovery.regenerate

Write. Scope: administration.write, admin. Contract: route_inferred. Admin 2fa Recovery Regenerate

administration.2fa.setup

Read. Scope: administration.read, admin. Contract: route_inferred. Admin 2fa Setup

administration.2fa.status

Read. Scope: administration.read, admin. Contract: declared_dynamic. Admin 2fa Status

administration.ai.train.from.reply

Write. Scope: administration.write, admin. Contract: route_inferred. Admin Ai Train From Reply

administration.brain.cancel

Write. Scope: administration.write, admin. Contract: declared_dynamic. Admin Brain Cancel

administration.brain.view

Write. Scope: administration.write, admin. Contract: route_inferred. Admin Brain View

administration.chat.access.check

Write. Scope: administration.write, admin. Contract: route_inferred. Admin Chat Access Check

administration.chat.create.ticket.on.behalf

Write. Scope: administration.write, admin. Contract: route_inferred. Admin Chat Create Ticket On Behalf

administration.chat.draft.ticket.from.thread

Write. Scope: administration.write, admin. Contract: route_inferred. Admin Chat Draft Ticket From Thread

administration.conv.delete

Write. Scope: administration.write, admin. Contract: route_inferred. Admin Conv Delete

administration.conv.get

Write. Scope: administration.write, admin. Contract: route_inferred. Admin Conv Get

administration.conv.list

Write. Scope: administration.write, admin. Contract: route_inferred. Admin Conv List

administration.conv.new

Write. Scope: administration.write, admin. Contract: route_inferred. Admin Conv New

administration.conv.save

Write. Scope: administration.write, admin. Contract: route_inferred. Admin Conv Save

administration.notification.prefs.get

Read. Scope: administration.read, admin. Contract: declared_dynamic. Admin Notification Prefs Get

administration.notification.prefs.save

Write. Scope: administration.write, admin. Contract: declared_dynamic. Admin Notification Prefs Save

administration.notifications.list

Read. Scope: administration.read, admin. Contract: route_inferred. Admin Notifications List

administration.notifications.mark.all.read

Write. Scope: administration.write, admin. Contract: declared_dynamic. Admin Notifications Mark All Read

administration.notifications.mark.read

Write. Scope: administration.write, admin. Contract: route_inferred. Admin Notifications Mark Read

administration.notifications.pulse

Write. Scope: administration.write, admin. Contract: route_inferred. Admin Notifications Pulse

administration.online.list

Read. Scope: administration.read, admin. Contract: declared_dynamic. Admin Online List

administration.presence.ping

Write. Scope: administration.write, admin. Contract: declared_dynamic. Admin Presence Ping

administration.realtime.token

Write. Scope: administration.write, admin. Contract: route_inferred. Admin Realtime Token

Uchambuzi wa analytics (43)

analytics.add.widget

Write. Scope: analytics.write, admin. Contract: route_inferred. Dashboard Add Widget

analytics.analytics.connectors.catalog

Read. Scope: analytics.read, admin. Contract: declared_dynamic. Analytics Connectors Catalog

analytics.analytics.data

Read. Scope: analytics.read, admin. Contract: route_inferred. Analytics Data

analytics.analytics.export

Read. Scope: analytics.read, admin. Contract: route_inferred. Analytics Export

analytics.analytics.export.csv

Read. Scope: analytics.read, admin. Contract: route_inferred. Analytics Export Csv

analytics.analytics.import

Write. Scope: analytics.write, admin. Contract: route_inferred. Analytics Import

analytics.analytics.report

Write. Scope: analytics.write, admin. Contract: route_inferred. Analytics Report

analytics.analytics.segments.delete

Write. Scope: analytics.write, admin. Contract: route_inferred. Analytics Segments Delete

analytics.analytics.segments.list

Read. Scope: analytics.read, admin. Contract: declared_dynamic. Analytics Segments List

analytics.analytics.segments.save

Write. Scope: analytics.write, admin. Contract: route_inferred. Analytics Segments Save

analytics.analytics.status

Read. Scope: analytics.read, admin. Contract: declared_dynamic. Analytics Status

analytics.clear.all

Write. Scope: analytics.write, admin. Contract: declared_dynamic. Replay Clear All

analytics.compute

Read. Scope: analytics.read, admin. Contract: route_inferred. Funnels Compute

analytics.create

Write. Scope: analytics.write, admin. Contract: route_inferred. Ab Test Create

analytics.create.route.dashboard.create

Write. Scope: analytics.write, admin. Contract: route_inferred. Dashboard Create

analytics.create.route.report.create

Write. Scope: analytics.write, admin. Contract: route_inferred. Report Create

analytics.delete

Write. Scope: analytics.write, admin. Contract: route_inferred. Ab Test Delete

analytics.delete.route.dashboard.delete

Write. Scope: analytics.write, admin. Contract: route_inferred. Dashboard Delete

analytics.delete.route.funnels.delete

Write. Scope: analytics.write, admin. Contract: route_inferred. Funnels Delete

analytics.delete.route.report.delete

Write. Scope: analytics.write, admin. Contract: route_inferred. Report Delete

analytics.events

Read. Scope: analytics.read, admin. Contract: route_inferred. Replay Events

analytics.export

Read. Scope: analytics.read, admin. Contract: source_inferred. Analytics Export

analytics.get

Read. Scope: analytics.read, admin. Contract: route_inferred. Dashboard Get

analytics.layout.save

Write. Scope: analytics.write, admin. Contract: route_inferred. Dashboard Layout Save

analytics.list

Read. Scope: analytics.read, admin. Contract: declared_dynamic. Ab Test List

analytics.list.route.dashboard.list

Read. Scope: analytics.read, admin. Contract: declared_dynamic. Dashboard List

analytics.list.route.funnels.list

Read. Scope: analytics.read, admin. Contract: declared_dynamic. Funnels List

analytics.list.route.report.list

Read. Scope: analytics.read, admin. Contract: declared_dynamic. Report List

analytics.remove.widget

Write. Scope: analytics.write, admin. Contract: route_inferred. Dashboard Remove Widget

analytics.rename

Write. Scope: analytics.write, admin. Contract: route_inferred. Dashboard Rename

analytics.results

Read. Scope: analytics.read, admin. Contract: route_inferred. Ab Test Results

analytics.save

Write. Scope: analytics.write, admin. Contract: route_inferred. Funnels Save

analytics.save.widgets

Write. Scope: analytics.write, admin. Contract: route_inferred. Dashboard Save Widgets

analytics.scheduled.list

Read. Scope: analytics.read, admin. Contract: explicit. List scheduled analytics reports for an operator Required fields: admin_id.

analytics.sections.list

Read. Scope: analytics.read, admin. Contract: explicit. List analytics report sections and date presets

analytics.send.now

Write. Scope: analytics.write, admin. Contract: route_inferred. Report Send Now

analytics.sessions

Read. Scope: analytics.read, admin. Contract: route_inferred. Replay Sessions

analytics.step.visitors

Read. Scope: analytics.read, admin. Contract: route_inferred. Funnels Step Visitors

analytics.timeline

Read. Scope: analytics.read, admin. Contract: route_inferred. Replay Timeline

analytics.toggle.shared

Write. Scope: analytics.write, admin. Contract: route_inferred. Dashboard Toggle Shared

analytics.update

Write. Scope: analytics.write, admin. Contract: route_inferred. Ab Test Update

analytics.update.route.report.update

Write. Scope: analytics.write, admin. Contract: route_inferred. Report Update

analytics.widget.data

Read. Scope: analytics.read, admin. Contract: route_inferred. Dashboard Widget Data

automations (6)

automations.actions.list

Read. Scope: automations.read, admin. Contract: explicit. List integration actions

automations.delete

Write. Scope: automations.write, admin. Contract: route_inferred. Workflow Delete

automations.list

Read. Scope: automations.read, admin. Contract: route_inferred. Workflow List

automations.runs.list

Read. Scope: automations.read, admin. Contract: explicit. List automation execution history

automations.save

Write. Scope: automations.write, admin. Contract: route_inferred. Workflow Save

automations.triggers.list

Read. Scope: automations.read, admin. Contract: explicit. List integration triggers

mazungumzo (40)

chat.call.start

Write. Scope: chat.write, admin. Contract: route_inferred. Chat Call Start

chat.cobrowse.send

Write. Scope: chat.write, admin. Contract: route_inferred. Chat Cobrowse Send

chat.feedback

Read. Scope: chat.read, admin. Contract: route_inferred. Chat Feedback

chat.feedback.digest

Write. Scope: chat.write, admin. Contract: route_inferred. Chat Feedback Digest

chat.form.delete

Write. Scope: chat.write, admin. Contract: route_inferred. Chat Form Delete

chat.form.get

Read. Scope: chat.read, admin. Contract: route_inferred. Chat Form Get

chat.form.list

Read. Scope: chat.read, admin. Contract: declared_dynamic. Chat Form List

chat.form.save

Write. Scope: chat.write, admin. Contract: route_inferred. Chat Form Save

chat.form.set.default

Write. Scope: chat.write, admin. Contract: route_inferred. Chat Form Set Default

chat.meeting.decide

Write. Scope: chat.write, admin. Contract: route_inferred. Chat Meeting Decide

chat.meeting.outcome.set

Write. Scope: chat.write, admin. Contract: route_inferred. Chat Meeting Outcome Set

chat.meeting.type.delete

Write. Scope: chat.write, admin. Contract: route_inferred. Chat Meeting Type Delete

chat.meeting.type.save

Write. Scope: chat.write, admin. Contract: route_inferred. Chat Meeting Type Save

chat.meeting.types.list

Write. Scope: chat.write, admin. Contract: route_inferred. Chat Meeting Types List

chat.meetings.list

Write. Scope: chat.write, admin. Contract: route_inferred. Chat Meetings List

chat.online.admins

Write. Scope: chat.write, admin. Contract: route_inferred. Chat Online Admins

chat.permissions.list

Write. Scope: admin. Contract: route_inferred. Chat Permissions List

chat.permissions.revoke

Write. Scope: admin. Contract: route_inferred. Chat Permissions Revoke

chat.permissions.save

Write. Scope: admin. Contract: route_inferred. Chat Permissions Save

chat.permissions.upload.avatar

Write. Scope: admin. Contract: route_inferred. Chat Permissions Upload Avatar

chat.reaction.toggle

Write. Scope: chat.write, admin. Contract: route_inferred. Chat Reaction Toggle

chat.saved_replies.add

Write. Scope: chat.write, admin. Contract: source_inferred. Chat Saved Replies Add Retry-safe with idempotency_key.

chat.saved_replies.list

Read. Scope: chat.read, admin. Contract: explicit. List workspace and personal saved replies

chat.saved_replies.save

Write. Scope: chat.write, admin. Contract: source_inferred. Chat Saved Replies Save Retry-safe with idempotency_key.

chat.set.persona

Write. Scope: chat.write, admin. Contract: route_inferred. Chat Set Persona

chat.snooze.clear

Write. Scope: chat.write, admin. Contract: route_inferred. Chat Snooze Clear

chat.snooze.set

Write. Scope: chat.write, admin. Contract: route_inferred. Chat Snooze Set

chat.transfer.thread

Write. Scope: chat.write, admin. Contract: route_inferred. Chat Transfer Thread

chat.transfer.unread

Write. Scope: chat.write, admin. Contract: declared_dynamic. Chat Transfer Unread

chat.typing.preview

Write. Scope: chat.write, admin. Contract: route_inferred. Chat Typing Preview

chat.whisper.ai.summary

Write. Scope: chat.write, admin. Contract: route_inferred. Chat Whisper Ai Summary

chat.whisper.controls

Write. Scope: chat.write, admin. Contract: declared_dynamic. Chat Whisper Controls

chat.whisper.delete.room

Write. Scope: chat.write, admin. Contract: route_inferred. Chat Whisper Delete Room

chat.whisper.list

Write. Scope: chat.write, admin. Contract: route_inferred. Chat Whisper List

chat.whisper.mentions

Write. Scope: chat.write, admin. Contract: declared_dynamic. Chat Whisper Mentions

chat.whisper.rooms

Write. Scope: chat.write, admin. Contract: declared_dynamic. Chat Whisper Rooms

chat.whisper.save.controls

Write. Scope: chat.write, admin. Contract: route_inferred. Chat Whisper Save Controls

chat.whisper.send

Write. Scope: chat.write, admin. Contract: route_inferred. Chat Whisper Send

chat.whisper.targets

Write. Scope: chat.write, admin. Contract: declared_dynamic. Chat Whisper Targets

chat.whisper.unread

Write. Scope: chat.write, admin. Contract: route_inferred. Chat Whisper Unread

Biashara ya biashara (11)

commerce.analytics.snapshot

Read. Scope: commerce.read, analytics.read, admin. Contract: explicit. Read privacy-safe storefront analytics

commerce.orders.get

Read. Scope: commerce.read, admin. Contract: explicit. Get one Store order with its line items

commerce.orders.list

Read. Scope: commerce.read, admin. Contract: explicit. List Store orders in the bound workspace

commerce.pages.list

Read. Scope: commerce.read, admin. Contract: explicit. List storefront pages and promotional modals

commerce.products.get

Read. Scope: commerce.read, admin. Contract: explicit. Get one Store product with its variants Required fields: product_id.

commerce.products.list

Read. Scope: commerce.read, admin. Contract: explicit. List Store products in the bound workspace

commerce.quotes.create

Write. Scope: commerce.write, admin. Contract: explicit. Quote an item for a customer (creates nothing) Required fields: source, item_id. Retry-safe with idempotency_key.

commerce.readiness.get

Read. Scope: commerce.read, admin. Contract: explicit. Check demo readiness and merchant go-live readiness

commerce.refunds.list

Read. Scope: commerce.read, admin. Contract: explicit. List Store refund requests in the bound workspace

commerce.storefront.catalog.get

Read. Scope: commerce.read, admin. Contract: explicit. Discover Store themes, designs, blocks and promotional shells

commerce.storefront.get

Read. Scope: commerce.read, admin. Contract: explicit. Get the bound workspace storefront configuration

communications (21)

communications.auth.check

Read. Scope: admin. Contract: route_inferred. Email Auth Check

communications.campaign.delete

Write. Scope: communications.write, admin. Contract: route_inferred. Push Campaign Delete

communications.campaign.save

Write. Scope: communications.write, admin. Contract: route_inferred. Push Campaign Save

communications.campaign.send

Write. Scope: communications.write, admin. Contract: route_inferred. Push Campaign Send

communications.campaigns.list

Read. Scope: communications.read, admin. Contract: declared_dynamic. Push Campaigns List

communications.drafts.delete

Write. Scope: communications.write, admin. Contract: route_inferred. Email Drafts Delete

communications.drafts.list

Read. Scope: communications.read, admin. Contract: declared_dynamic. Email Drafts List

communications.drafts.save

Write. Scope: communications.write, admin. Contract: route_inferred. Email Drafts Save

communications.drafts.send

Write. Scope: communications.write, admin. Contract: route_inferred. Email Drafts Send

communications.mailboxes.delete

Write. Scope: communications.write, admin. Contract: route_inferred. Email Mailboxes Delete

communications.mailboxes.list

Read. Scope: communications.read, admin. Contract: route_inferred. Email Mailboxes List

communications.mailboxes.poll

Read. Scope: communications.read, admin. Contract: declared_dynamic. Email Mailboxes Poll

communications.mailboxes.save

Write. Scope: communications.write, admin. Contract: route_inferred. Email Mailboxes Save

communications.mailboxes.test

Read. Scope: communications.read, admin. Contract: declared_dynamic. Email Mailboxes Test

communications.pipe.regen.token

Write. Scope: communications.write, admin. Contract: declared_dynamic. Email Pipe Regen Token

communications.platform.list

Read. Scope: communications.read, admin. Contract: declared_dynamic. Email Platform List

communications.platform.send

Write. Scope: communications.write, admin. Contract: route_inferred. Email Platform Send

communications.settings.get

Read. Scope: communications.read, admin. Contract: declared_dynamic. Email Settings Get

communications.settings.save

Write. Scope: communications.write, admin. Contract: route_inferred. Email Settings Save

communications.settings.test

Read. Scope: communications.read, admin. Contract: route_inferred. Email Settings Test

communications.vapid.generate

Write. Scope: communications.write, admin. Contract: declared_dynamic. Push Vapid Generate

connector_builder (11)

connector_builder.export

Read. Scope: connector_builder.read, admin. Contract: explicit. Export a generated connector Required fields: slug.

connector_builder.generate

Write. Scope: connector_builder.write, admin. Contract: route_inferred. Generate a connector package Required fields: spec.

connector_builder.get

Read. Scope: connector_builder.read, admin. Contract: route_inferred. Load a Builder specification Required fields: slug.

connector_builder.import.curl

Write. Scope: connector_builder.write, admin. Contract: route_inferred. Import cURL into Connector Builder

connector_builder.import.openapi

Write. Scope: connector_builder.write, admin. Contract: route_inferred. Import OpenAPI into Connector Builder

connector_builder.import.postman

Write. Scope: connector_builder.write, admin. Contract: route_inferred. Import Postman into Connector Builder

connector_builder.list

Read. Scope: connector_builder.read, admin. Contract: declared_dynamic. List Builder connectors

connector_builder.profiles

Read. Scope: connector_builder.read, connectors.read, admin. Contract: source_inferred. List Connector Builder profiles and capability contracts

connector_builder.test

Write. Scope: connector_builder.write, admin. Contract: route_inferred. Run Builder conformance tests Required fields: slug.

connector_builder.update

Write. Scope: connector_builder.write, admin. Contract: route_inferred. Update a generated connector Required fields: slug, spec.

connector_builder.validate

Read. Scope: connector_builder.read, admin. Contract: route_inferred. Validate a Builder specification Required fields: spec.

connectors (51)

connectors.action

Write. Scope: connectors.write, admin. Contract: route_inferred. Connectors Action

connectors.backfill

Write. Scope: connectors.write, admin. Contract: route_inferred. Start connector backfill Required fields: slug.

connectors.backfill.route.connectors.backfill

Write. Scope: connectors.write, admin. Contract: route_inferred. Connectors Backfill

connectors.backfill.status

Read. Scope: connectors.read, admin. Contract: route_inferred. Read connector backfill status Required fields: slug.

connectors.backfill.status.route.connectors.backfill.status

Read. Scope: connectors.read, admin. Contract: route_inferred. Connectors Backfill Status

connectors.builder.ai.actions

Read. Scope: connectors.read, admin. Contract: route_inferred. Connectors Builder Ai Actions

connectors.builder.ai.draft

Write. Scope: connectors.write, admin. Contract: route_inferred. Connectors Builder Ai Draft

connectors.builder.ai.handler

Read. Scope: connectors.read, admin. Contract: route_inferred. Connectors Builder Ai Handler

connectors.builder.ai.map

Write. Scope: connectors.write, admin. Contract: route_inferred. Connectors Builder Ai Map

connectors.builder.delete

Write. Scope: connectors.write, admin. Contract: route_inferred. Connectors Builder Delete

connectors.builder.dry.run

Write. Scope: connectors.write, admin. Contract: route_inferred. Connectors Builder Dry Run

connectors.builder.generate

Write. Scope: connectors.write, admin. Contract: route_inferred. Connectors Builder Generate

connectors.builder.import.curl

Write. Scope: connectors.write, admin. Contract: route_inferred. Connectors Builder Import Curl

connectors.builder.import.openapi

Write. Scope: connectors.write, admin. Contract: route_inferred. Connectors Builder Import Openapi

connectors.builder.import.postman

Write. Scope: connectors.write, admin. Contract: route_inferred. Connectors Builder Import Postman

connectors.builder.list

Read. Scope: connectors.read, admin. Contract: declared_dynamic. Connectors Builder List

connectors.builder.load

Read. Scope: connectors.read, admin. Contract: route_inferred. Connectors Builder Load

connectors.builder.marketplace.apply

Write. Scope: connectors.write, admin. Contract: route_inferred. Connectors Builder Marketplace Apply

connectors.builder.marketplace.link

Write. Scope: connectors.write, admin. Contract: route_inferred. Connectors Builder Marketplace Link

connectors.builder.marketplace.status

Read. Scope: connectors.read, admin. Contract: declared_dynamic. Connectors Builder Marketplace Status

connectors.builder.marketplace.submit

Write. Scope: connectors.write, admin. Contract: route_inferred. Connectors Builder Marketplace Submit

connectors.builder.schema

Read. Scope: connectors.read, admin. Contract: declared_dynamic. Connectors Builder Schema

connectors.builder.test

Read. Scope: connectors.read, admin. Contract: route_inferred. Connectors Builder Test

connectors.builder.test.action

Read. Scope: connectors.read, admin. Contract: route_inferred. Connectors Builder Test Action

connectors.builder.update

Write. Scope: connectors.write, admin. Contract: route_inferred. Connectors Builder Update

connectors.builder.validate

Read. Scope: connectors.read, admin. Contract: route_inferred. Connectors Builder Validate

connectors.contacts.import

Write. Scope: connectors.write, admin. Contract: route_inferred. Connector Contacts Import

connectors.contract

Read. Scope: connectors.read, connector_builder.read, admin. Contract: source_inferred. Read the canonical connector capability contract

connectors.customers.sync

Write. Scope: connectors.write, admin. Contract: route_inferred. Synchronize connector customers Required fields: slug.

connectors.disable

Write. Scope: connectors.write, admin. Contract: route_inferred. Disable a connector Required fields: slug.

connectors.disable.route.connectors.disable

Write. Scope: connectors.write, admin. Contract: route_inferred. Connectors Disable

connectors.email.account.department

Read. Scope: connectors.read, admin. Contract: route_inferred. Connector Email Account Department

connectors.email.account.remove

Write. Scope: connectors.write, admin. Contract: route_inferred. Connector Email Account Remove

connectors.email.account.routing

Read. Scope: connectors.read, admin. Contract: route_inferred. Connector Email Account Routing

connectors.enable

Write. Scope: connectors.write, admin. Contract: route_inferred. Enable a connector Required fields: slug.

connectors.enable.route.connectors.enable

Write. Scope: connectors.write, admin. Contract: route_inferred. Connectors Enable

connectors.get

Read. Scope: connectors.read, admin. Contract: source_inferred. Connectors Get

connectors.get.route.connectors.get

Read. Scope: connectors.read, admin. Contract: route_inferred. Connectors Get

connectors.install

Write. Scope: connectors.write, admin. Contract: route_inferred. Connectors Install

connectors.integrity.scan

Read. Scope: connectors.read, admin. Contract: declared_dynamic. Connector Integrity Scan

connectors.list

Read. Scope: connectors.read, admin. Contract: explicit. List installed connectors and capabilities

connectors.list.route.connectors.list

Read. Scope: connectors.read, admin. Contract: declared_dynamic. Connectors List

connectors.oauth.start

Write. Scope: connectors.write, admin. Contract: route_inferred. Connector Oauth Start

connectors.settings.get

Read. Scope: connectors.read, admin. Contract: route_inferred. Read connector settings Required fields: slug.

connectors.settings.save

Write. Scope: connectors.write, admin. Contract: route_inferred. Save connector settings Required fields: slug, settings.

connectors.shared.oauth.delete

Write. Scope: connectors.write, admin. Contract: route_inferred. Connector Shared Oauth Delete

connectors.sync.customers

Write. Scope: connectors.write, admin. Contract: route_inferred. Connectors Sync Customers

connectors.test

Read. Scope: connectors.read, admin. Contract: source_inferred. Connectors Test

connectors.test.route.connectors.test

Read. Scope: connectors.read, admin. Contract: route_inferred. Connectors Test

connectors.uninstall

Write. Scope: connectors.write, admin. Contract: route_inferred. Connectors Uninstall

connectors.workflow.recipes

Read. Scope: connectors.read, admin. Contract: route_inferred. Connectors Workflow Recipes

conversations (38)

conversations.ai.draft

Write. Scope: conversations.write, admin. Contract: route_inferred. Admin Client Chat Ai Draft

conversations.ai.rewrite

Write. Scope: conversations.write, admin. Contract: route_inferred. Admin Client Chat Ai Rewrite

conversations.archive

Write. Scope: conversations.write, admin. Contract: route_inferred. Admin Client Chat Archive

conversations.assign

Write. Scope: conversations.write, admin. Contract: route_inferred. Admin Client Chat Assign

conversations.assignees

Write. Scope: conversations.write, admin. Contract: declared_dynamic. Admin Client Chat Assignees

conversations.bulk

Write. Scope: conversations.write, admin. Contract: route_inferred. Admin Client Chat Bulk

conversations.clear

Write. Scope: conversations.write, admin. Contract: route_inferred. Admin Client Chat Clear

conversations.clear.all

Write. Scope: conversations.write, admin. Contract: route_inferred. Admin Client Chat Clear All

conversations.customer.tickets

Write. Scope: conversations.write, admin. Contract: declared_dynamic. Admin Client Chat Customer Tickets

conversations.decline

Write. Scope: conversations.write, admin. Contract: route_inferred. Admin Client Chat Decline

conversations.delete

Write. Scope: conversations.write, admin. Contract: route_inferred. Admin Client Chat Delete

conversations.delete.last

Write. Scope: conversations.write, admin. Contract: route_inferred. Admin Client Chat Delete Last

conversations.edit.last

Write. Scope: conversations.write, admin. Contract: route_inferred. Admin Client Chat Edit Last

conversations.export

Write. Scope: conversations.write, admin. Contract: route_inferred. Admin Client Chat Export

conversations.forget.visitor

Write. Scope: conversations.write, admin. Contract: route_inferred. Admin Client Chat Forget Visitor

conversations.get

Read. Scope: conversations.read, admin. Contract: source_inferred. Conversations Get

conversations.history

Write. Scope: conversations.write, admin. Contract: route_inferred. Admin Client Chat History

conversations.list

Read. Scope: conversations.read, admin. Contract: source_inferred. Conversations List

conversations.messages

Read. Scope: conversations.read, admin. Contract: source_inferred. Conversations Messages

conversations.ratings.list

Read. Scope: conversations.read, admin. Contract: explicit. List rated Client Chat conversations

conversations.resolve

Write. Scope: conversations.write, admin. Contract: route_inferred. Admin Client Chat Resolve

conversations.saved.replies

Write. Scope: conversations.write, admin. Contract: declared_dynamic. Admin Client Chat Saved Replies

conversations.saved.reply.add

Write. Scope: conversations.write, admin. Contract: route_inferred. Admin Client Chat Saved Reply Add

conversations.saved.reply.ai.generate

Write. Scope: conversations.write, admin. Contract: route_inferred. Admin Client Chat Saved Reply Ai Generate

conversations.saved.reply.delete

Write. Scope: conversations.write, admin. Contract: route_inferred. Admin Client Chat Saved Reply Delete

conversations.saved.reply.save

Write. Scope: conversations.write, admin. Contract: route_inferred. Admin Client Chat Saved Reply Save

conversations.send

Write. Scope: conversations.write, admin. Contract: source_inferred. Conversations Send Retry-safe with idempotency_key.

conversations.send.route.admin.client.chat.send

Write. Scope: conversations.write, admin. Contract: route_inferred. Admin Client Chat Send

conversations.tags.set

Write. Scope: conversations.write, admin. Contract: route_inferred. Admin Client Chat Tags Set

conversations.thread

Write. Scope: conversations.write, admin. Contract: route_inferred. Admin Client Chat Thread

conversations.threads

Write. Scope: conversations.write, admin. Contract: route_inferred. Admin Client Chat Threads

conversations.toggle

Write. Scope: conversations.write, admin. Contract: route_inferred. Admin Client Chat Toggle

conversations.toggle.attachments

Write. Scope: conversations.write, admin. Contract: route_inferred. Admin Client Chat Toggle Attachments

conversations.toggle.call.button

Write. Scope: conversations.write, admin. Contract: route_inferred. Admin Client Chat Toggle Call Button

conversations.typing

Write. Scope: conversations.write, admin. Contract: route_inferred. Admin Client Chat Typing

conversations.unarchive

Write. Scope: conversations.write, admin. Contract: route_inferred. Admin Client Chat Unarchive

conversations.update

Write. Scope: conversations.write, admin. Contract: explicit. Update a conversation status, assignment or subject Retry-safe with idempotency_key.

conversations.upload

Write. Scope: conversations.write, admin. Contract: route_inferred. Admin Client Chat Upload

ya crm (260)

crm.ab.results

Read. Scope: crm.read, admin. Contract: route_inferred. Crm Ab Results

crm.access.set

Write. Scope: crm.write, admin. Contract: route_inferred. Crm Access Set

crm.access_log.list

Read. Scope: admin. Contract: source_inferred. Crm Access Log List

crm.account.health

Read. Scope: crm.read, admin. Contract: declared_dynamic. Crm Account Health

crm.account.health.board

Read. Scope: crm.read, admin. Contract: declared_dynamic. Crm Account Health Board

crm.account.health.refresh

Write. Scope: crm.write, admin. Contract: declared_dynamic. Crm Account Health Refresh

crm.account.plan.get

Write. Scope: crm.write, admin. Contract: route_inferred. Crm Account Plan Get

crm.account.plan.save

Write. Scope: crm.write, admin. Contract: route_inferred. Crm Account Plan Save

crm.account.plans.due

Write. Scope: crm.write, admin. Contract: route_inferred. Crm Account Plans Due

crm.account.timeline

Read. Scope: crm.read, admin. Contract: route_inferred. Crm Account Timeline

crm.activities.list

Read. Scope: crm.read. Contract: explicit. List CRM contact activities

crm.activities.record

Write. Scope: crm.write. Contract: explicit. Record a CRM contact activity Required fields: contact_id, activity_type. Retry-safe with idempotency_key.

crm.activity.feed

Read. Scope: crm.read, admin. Contract: route_inferred. Crm Activity Feed

crm.agent.toggle

Write. Scope: crm.write, admin. Contract: route_inferred. Crm Agent Toggle

crm.ai.policy.get

Write. Scope: crm.write, admin. Contract: route_inferred. Crm Ai Policy Get

crm.ai.policy.save

Write. Scope: crm.write, admin. Contract: route_inferred. Crm Ai Policy Save

crm.ai.policy.simulate

Write. Scope: crm.write, admin. Contract: route_inferred. Crm Ai Policy Simulate

crm.ai.trace

Read. Scope: crm.read, admin. Contract: route_inferred. Crm Ai Trace

crm.approval.decide

Write. Scope: crm.write, admin. Contract: route_inferred. Crm Approval Decide

crm.approval.delegate.set

Write. Scope: crm.write, admin. Contract: route_inferred. Crm Approval Delegate Set

crm.approval.list

Read. Scope: crm.read, admin. Contract: route_inferred. Crm Approval List

crm.approval.policy.get

Write. Scope: crm.write, admin. Contract: route_inferred. Crm Approval Policy Get

crm.approval.policy.save

Write. Scope: crm.write, admin. Contract: route_inferred. Crm Approval Policy Save

crm.approval.settings

Write. Scope: crm.write, admin. Contract: route_inferred. Crm Approval Settings

crm.approve.apply

Write. Scope: crm.write, admin. Contract: declared_dynamic. Crm Approve Apply

crm.approve.list

Read. Scope: crm.read, admin. Contract: declared_dynamic. Crm Approve List

crm.approve.reject

Write. Scope: crm.write, admin. Contract: declared_dynamic. Crm Approve Reject

crm.approve.update

Write. Scope: crm.write, admin. Contract: declared_dynamic. Crm Approve Update

crm.ask

Write. Scope: crm.write, admin. Contract: route_inferred. Crm Ask

crm.assign.owner

Write. Scope: crm.write, admin. Contract: route_inferred. Contact Assign Owner

crm.assignment.get

Read. Scope: crm.read, admin. Contract: declared_dynamic. Crm Assignment Get

crm.assignment.save

Write. Scope: crm.write, admin. Contract: route_inferred. Crm Assignment Save

crm.attachment.delete

Write. Scope: crm.write, admin. Contract: route_inferred. Crm Attachment Delete

crm.attachment.list

Read. Scope: crm.read, admin. Contract: route_inferred. Crm Attachment List

crm.attachment.upload

Write. Scope: crm.write, admin. Contract: route_inferred. Crm Attachment Upload

crm.autobook.meeting

Write. Scope: crm.write, admin. Contract: route_inferred. Crm Autobook Meeting

crm.autodeal.mode

Write. Scope: crm.write, admin. Contract: route_inferred. Crm Autodeal Mode

crm.book.meeting

Write. Scope: crm.write, admin. Contract: route_inferred. Crm Book Meeting

crm.booking.link.save

Write. Scope: crm.write, admin. Contract: declared_dynamic. Crm Booking Link Save

crm.booking.links.list

Read. Scope: crm.read, admin. Contract: declared_dynamic. Crm Booking Links List

crm.build.apply

Write. Scope: crm.write, admin. Contract: declared_dynamic. Crm Build Apply

crm.build.get

Read. Scope: crm.read, admin. Contract: declared_dynamic. Crm Build Get

crm.build.list

Read. Scope: crm.read, admin. Contract: declared_dynamic. Crm Build List

crm.build.plan

Write. Scope: crm.write, admin. Contract: declared_dynamic. Crm Build Plan

crm.build.rollback

Write. Scope: crm.write, admin. Contract: declared_dynamic. Crm Build Rollback

crm.bulk

Write. Scope: crm.write, admin. Contract: route_inferred. Contact Bulk

crm.bundle.set

Write. Scope: crm.write, admin. Contract: route_inferred. Crm Bundle Set

crm.calendar.status

Read. Scope: crm.read, admin. Contract: declared_dynamic. Crm Calendar Status

crm.capture.status

Write. Scope: crm.write, admin. Contract: route_inferred. Crm Capture Status

crm.comm.policy.get

Write. Scope: crm.write, admin. Contract: route_inferred. Crm Comm Policy Get

crm.comm.policy.save

Write. Scope: crm.write, admin. Contract: route_inferred. Crm Comm Policy Save

crm.command.snapshot

Read. Scope: crm.read, admin. Contract: declared_dynamic. Crm Command Snapshot

crm.companies.list

Read. Scope: crm.read, admin. Contract: declared_dynamic. Crm Companies List

crm.company.hierarchy

Read. Scope: crm.read, admin. Contract: route_inferred. Crm Company Hierarchy

crm.company.save

Write. Scope: crm.write, admin. Contract: declared_dynamic. Crm Company Save

crm.company.set.parent

Write. Scope: crm.write, admin. Contract: route_inferred. Crm Company Set Parent

crm.company.suggest.related

Read. Scope: crm.read, admin. Contract: route_inferred. Crm Company Suggest Related

crm.connectors.catalog

Read. Scope: crm.read, admin. Contract: declared_dynamic. Crm Connectors Catalog

crm.consent_log.list

Read. Scope: crm.read. Contract: source_inferred. Crm Consent Log List

crm.contact.churn

Read. Scope: crm.read, admin. Contract: route_inferred. Crm Contact Churn

crm.contact.draft.email

Write. Scope: crm.write, admin. Contract: route_inferred. Crm Contact Draft Email

crm.contact.enrich

Write. Scope: crm.write, admin. Contract: route_inferred. Crm Contact Enrich

crm.contact.propose.email

Write. Scope: crm.write, admin. Contract: route_inferred. Crm Contact Propose Email

crm.contacts.detail

Read. Scope: crm.read. Contract: source_inferred. Crm Contacts Detail

crm.contacts.erase

Write. Scope: admin. Contract: source_inferred. Crm Contacts Erase Retry-safe with idempotency_key.

crm.contacts.export

Read. Scope: crm.read. Contract: source_inferred. Crm Contacts Export

crm.contacts.import.list

Read. Scope: crm.read. Contract: source_inferred. Crm Contacts Import List

crm.contacts.import.run

Write. Scope: crm.write. Contract: source_inferred. Crm Contacts Import Run Retry-safe with idempotency_key.

crm.contacts.list

Read. Scope: crm.read. Contract: source_inferred. Crm Contacts List

crm.contacts.next_action

Read. Scope: crm.read. Contract: source_inferred. Crm Contacts Next Action

crm.contacts.open_chat

Write. Scope: crm.write. Contract: source_inferred. Crm Contacts Open Chat Retry-safe with idempotency_key.

crm.contacts.open_ticket

Write. Scope: crm.write. Contract: source_inferred. Crm Contacts Open Ticket Retry-safe with idempotency_key.

crm.contacts.resync

Write. Scope: crm.write. Contract: source_inferred. Crm Contacts Resync Retry-safe with idempotency_key.

crm.contacts.save

Write. Scope: crm.write. Contract: source_inferred. Crm Contacts Save Retry-safe with idempotency_key.

crm.contacts.send_email

Write. Scope: crm.write. Contract: source_inferred. Crm Contacts Send Email Retry-safe with idempotency_key.

crm.contacts.upsert

Write. Scope: crm.write. Contract: explicit. Crm Contacts Upsert Required fields: email. Retry-safe with idempotency_key.

crm.contract.amend

Write. Scope: crm.write, admin. Contract: route_inferred. Crm Contract Amend

crm.contract.price.set

Write. Scope: crm.write, admin. Contract: route_inferred. Crm Contract Price Set

crm.contract.save

Write. Scope: crm.write, admin. Contract: route_inferred. Crm Contract Save

crm.contract.usage

Write. Scope: crm.write, admin. Contract: route_inferred. Crm Contract Usage

crm.contracts.list

Write. Scope: crm.write, admin. Contract: route_inferred. Crm Contracts List

crm.conversation.intel

Write. Scope: crm.write, admin. Contract: declared_dynamic. Crm Conversation Intel

crm.conversions.goals.delete

Write. Scope: crm.write. Contract: source_inferred. Crm Conversions Goals Delete Retry-safe with idempotency_key.

crm.conversions.goals.list

Read. Scope: crm.read. Contract: source_inferred. Crm Conversions Goals List

crm.conversions.goals.save

Write. Scope: crm.write. Contract: source_inferred. Crm Conversions Goals Save Retry-safe with idempotency_key.

crm.conversions.list

Read. Scope: crm.read. Contract: source_inferred. Crm Conversions List

crm.conversions.record

Write. Scope: crm.write. Contract: source_inferred. Crm Conversions Record Retry-safe with idempotency_key.

crm.create.video.meeting

Write. Scope: crm.write, admin. Contract: route_inferred. Crm Create Video Meeting

crm.customer.auto.sync

Write. Scope: crm.write, admin. Contract: route_inferred. Crm Customer Auto Sync

crm.customer.auto.sync.status

Read. Scope: crm.read, admin. Contract: route_inferred. Crm Customer Auto Sync Status

crm.customer.emails

Read. Scope: crm.read, admin. Contract: route_inferred. Crm Customer Emails

crm.customer.payments

Read. Scope: crm.read, admin. Contract: route_inferred. Crm Customer Payments

crm.data.steward.bulk.propose

Write. Scope: crm.write, admin. Contract: route_inferred. Crm Data Steward Bulk Propose

crm.data.steward.inbox

Read. Scope: crm.read, admin. Contract: declared_dynamic. Crm Data Steward Inbox

crm.data.steward.propose

Write. Scope: crm.write, admin. Contract: route_inferred. Crm Data Steward Propose

crm.deal.advance

Write. Scope: crm.write, admin. Contract: declared_dynamic. Crm Deal Advance

crm.deal.coach

Read. Scope: crm.read, admin. Contract: declared_dynamic. Crm Deal Coach

crm.deal.coach.action

Write. Scope: crm.write, admin. Contract: declared_dynamic. Crm Deal Coach Action

crm.deal.get

Read. Scope: crm.read, admin. Contract: declared_dynamic. Crm Deal Get

crm.deal.save

Write. Scope: crm.write, admin. Contract: route_inferred. Crm Deal Save

crm.deal.splits.get

Read. Scope: crm.read, admin. Contract: route_inferred. Crm Deal Splits Get

crm.deal.splits.set

Write. Scope: crm.write, admin. Contract: route_inferred. Crm Deal Splits Set

crm.deals.advance

Write. Scope: crm.write. Contract: explicit. Advance a CRM deal to another stage Required fields: deal_id, stage_id. Retry-safe with idempotency_key.

crm.deals.create

Write. Scope: crm.write. Contract: explicit. Create a CRM deal Required fields: title. Retry-safe with idempotency_key.

crm.deals.detail

Read. Scope: crm.read. Contract: explicit. Get one CRM deal Required fields: deal_id.

crm.deals.list

Read. Scope: crm.read. Contract: explicit. List CRM deals

crm.deals.list.route.crm.deals.list

Read. Scope: crm.read, admin. Contract: declared_dynamic. Crm Deals List

crm.deals.update

Write. Scope: crm.write. Contract: explicit. Update a CRM deal Required fields: deal_id. Retry-safe with idempotency_key.

crm.detail

Write. Scope: crm.write, admin. Contract: route_inferred. Contact Detail

crm.draft.outreach

Write. Scope: crm.write, admin. Contract: declared_dynamic. Crm Draft Outreach

crm.enrich.account

Write. Scope: crm.write, admin. Contract: route_inferred. Crm Enrich Account

crm.erase

Write. Scope: crm.write, admin. Contract: route_inferred. Contact Erase

crm.events.catalog

Read. Scope: crm.read. Contract: explicit. List subscribable CRM domain events

crm.events.list

Read. Scope: crm.read. Contract: explicit. List durable CRM domain events

crm.export

Write. Scope: crm.write, admin. Contract: route_inferred. Contact Export

crm.export.all

Read. Scope: crm.read, admin. Contract: route_inferred. Contact Export All

crm.field.add

Write. Scope: crm.write, admin. Contract: route_inferred. Crm Field Add

crm.field.policy.get

Write. Scope: crm.write, admin. Contract: route_inferred. Crm Field Policy Get

crm.field.policy.save

Write. Scope: crm.write, admin. Contract: route_inferred. Crm Field Policy Save

crm.field.remove

Write. Scope: crm.write, admin. Contract: route_inferred. Crm Field Remove

crm.fields.list

Read. Scope: crm.read, admin. Contract: declared_dynamic. Crm Fields List

crm.forecast.board

Read. Scope: crm.read, admin. Contract: declared_dynamic. Crm Forecast Board

crm.forecast.snapshot

Write. Scope: crm.write, admin. Contract: declared_dynamic. Crm Forecast Snapshot

crm.form.save

Write. Scope: crm.write, admin. Contract: declared_dynamic. Crm Form Save

crm.forms.list

Read. Scope: crm.read, admin. Contract: declared_dynamic. Crm Forms List

crm.health.repair.catalog

Read. Scope: crm.read, admin. Contract: declared_dynamic. Crm Health Repair Catalog

crm.health.smoke

Write. Scope: crm.write, admin. Contract: declared_dynamic. Crm Health Smoke

crm.health.snapshot

Read. Scope: crm.read, admin. Contract: declared_dynamic. Crm Health Snapshot

crm.home.persona.set

Write. Scope: crm.write, admin. Contract: route_inferred. Crm Home Persona Set

crm.identity.rules.get

Write. Scope: crm.write, admin. Contract: route_inferred. Crm Identity Rules Get

crm.identity.rules.save

Write. Scope: crm.write, admin. Contract: route_inferred. Crm Identity Rules Save

crm.import.list

Read. Scope: crm.read, admin. Contract: route_inferred. Contact Import List

crm.import.run

Write. Scope: crm.write, admin. Contract: route_inferred. Contact Import Run

crm.inbound.activity

Read. Scope: crm.read. Contract: source_inferred. Crm Inbound Activity

crm.inbound.endpoints.delete

Write. Scope: crm.write. Contract: source_inferred. Crm Inbound Endpoints Delete Retry-safe with idempotency_key.

crm.inbound.endpoints.list

Read. Scope: crm.read. Contract: source_inferred. Crm Inbound Endpoints List

crm.inbound.endpoints.save

Write. Scope: crm.write. Contract: source_inferred. Crm Inbound Endpoints Save Retry-safe with idempotency_key.

crm.inbound.endpoints.test

Write. Scope: crm.write. Contract: source_inferred. Crm Inbound Endpoints Test Retry-safe with idempotency_key.

crm.leaderboard

Read. Scope: crm.read, admin. Contract: route_inferred. Crm Leaderboard

crm.lifecycle.evaluate

Write. Scope: crm.write. Contract: source_inferred. Crm Lifecycle Evaluate Retry-safe with idempotency_key.

crm.lifecycle.rules.delete

Write. Scope: crm.write. Contract: source_inferred. Crm Lifecycle Rules Delete Retry-safe with idempotency_key.

crm.lifecycle.rules.list

Read. Scope: crm.read. Contract: source_inferred. Crm Lifecycle Rules List

crm.lifecycle.rules.save

Write. Scope: crm.write. Contract: source_inferred. Crm Lifecycle Rules Save Retry-safe with idempotency_key.

crm.list

Read. Scope: crm.read, admin. Contract: route_inferred. Contacts List

crm.mailbox.status

Read. Scope: crm.read, admin. Contract: declared_dynamic. Crm Mailbox Status

crm.meeting.book

Write. Scope: crm.write, admin. Contract: route_inferred. Crm Meeting Book

crm.meeting.cancel

Write. Scope: crm.write, admin. Contract: route_inferred. Crm Meeting Cancel

crm.meeting.list

Read. Scope: crm.read, admin. Contract: route_inferred. Crm Meeting List

crm.meeting.reschedule.accept

Write. Scope: crm.write, admin. Contract: route_inferred. Crm Meeting Reschedule Accept

crm.meeting.reschedule.reject

Write. Scope: crm.write, admin. Contract: route_inferred. Crm Meeting Reschedule Reject

crm.merge

Write. Scope: crm.write, admin. Contract: route_inferred. Contact Merge

crm.message.send

Write. Scope: crm.write, admin. Contract: route_inferred. Crm Message Send

crm.messaging.provider.delete

Write. Scope: crm.write, admin. Contract: route_inferred. Crm Messaging Provider Delete

crm.messaging.provider.save

Write. Scope: crm.write, admin. Contract: route_inferred. Crm Messaging Provider Save

crm.messaging.provider.test

Read. Scope: crm.read, admin. Contract: route_inferred. Crm Messaging Provider Test

crm.messaging.status

Read. Scope: crm.read, admin. Contract: declared_dynamic. Crm Messaging Status

crm.next.action

Write. Scope: crm.write, admin. Contract: route_inferred. Contact Next Action

crm.object.save

Write. Scope: crm.write, admin. Contract: route_inferred. Crm Object Save

crm.objects.list

Read. Scope: crm.read, admin. Contract: route_inferred. Crm Objects List

crm.offline.pull

Write. Scope: crm.write, admin. Contract: route_inferred. Crm Offline Pull

crm.offline.push

Write. Scope: crm.write, admin. Contract: route_inferred. Crm Offline Push

crm.open.chat

Read. Scope: crm.read, admin. Contract: route_inferred. Contact Open Chat

crm.open.ticket

Write. Scope: crm.write, admin. Contract: route_inferred. Contact Open Ticket

crm.outreach.campaigns.delete

Write. Scope: crm.write. Contract: source_inferred. Crm Outreach Campaigns Delete Retry-safe with idempotency_key.

crm.outreach.campaigns.list

Read. Scope: crm.read. Contract: source_inferred. Crm Outreach Campaigns List

crm.outreach.campaigns.save

Write. Scope: crm.write. Contract: source_inferred. Crm Outreach Campaigns Save Retry-safe with idempotency_key.

crm.outreach.campaigns.send

Write. Scope: crm.write. Contract: source_inferred. Crm Outreach Campaigns Send Retry-safe with idempotency_key.

crm.outreach.send

Write. Scope: crm.write. Contract: source_inferred. Crm Outreach Send Retry-safe with idempotency_key.

crm.outreach.templates.delete

Write. Scope: crm.write. Contract: source_inferred. Crm Outreach Templates Delete Retry-safe with idempotency_key.

crm.outreach.templates.list

Read. Scope: crm.read. Contract: source_inferred. Crm Outreach Templates List

crm.outreach.templates.preview

Read. Scope: crm.read. Contract: source_inferred. Crm Outreach Templates Preview

crm.outreach.templates.save

Write. Scope: crm.write. Contract: source_inferred. Crm Outreach Templates Save Retry-safe with idempotency_key.

crm.payments.status

Read. Scope: crm.read, admin. Contract: declared_dynamic. Crm Payments Status

crm.pipeline.data

Read. Scope: crm.read, admin. Contract: declared_dynamic. Crm Pipeline Data

crm.price.resolve

Write. Scope: crm.write, admin. Contract: route_inferred. Crm Price Resolve

crm.pricebook.entry.set

Write. Scope: crm.write, admin. Contract: route_inferred. Crm Pricebook Entry Set

crm.pricebook.save

Write. Scope: crm.write, admin. Contract: route_inferred. Crm Pricebook Save

crm.pricebooks.list

Write. Scope: crm.write, admin. Contract: route_inferred. Crm Pricebooks List

crm.privacy_settings.get

Read. Scope: crm.read. Contract: source_inferred. Crm Privacy Settings Get

crm.privacy_settings.save

Write. Scope: admin. Contract: source_inferred. Crm Privacy Settings Save Retry-safe with idempotency_key.

crm.product.archive

Write. Scope: crm.write, admin. Contract: route_inferred. Crm Product Archive

crm.product.revenue

Read. Scope: crm.read, admin. Contract: declared_dynamic. Crm Product Revenue

crm.product.save

Write. Scope: crm.write, admin. Contract: declared_dynamic. Crm Product Save

crm.products.list

Read. Scope: crm.read, admin. Contract: route_inferred. Crm Products List

crm.propose.meeting

Read. Scope: crm.read, admin. Contract: route_inferred. Crm Propose Meeting

crm.propose.outreach

Write. Scope: crm.write, admin. Contract: declared_dynamic. Crm Propose Outreach

crm.prospecting.dashboard

Read. Scope: crm.read, admin. Contract: declared_dynamic. Crm Prospecting Dashboard

crm.prospecting.icp.save

Write. Scope: crm.write, admin. Contract: declared_dynamic. Crm Prospecting Icp Save

crm.prospecting.import

Write. Scope: crm.write, admin. Contract: route_inferred. Crm Prospecting Import

crm.prospecting.research

Write. Scope: crm.write, admin. Contract: declared_dynamic. Crm Prospecting Research

crm.prospecting.score

Write. Scope: crm.write, admin. Contract: route_inferred. Crm Prospecting Score

crm.prospecting.sequence

Write. Scope: crm.write, admin. Contract: route_inferred. Crm Prospecting Sequence

crm.qualification.checklist.get

Read. Scope: crm.read, admin. Contract: declared_dynamic. Crm Qualification Checklist Get

crm.qualification.checklist.save

Write. Scope: crm.write, admin. Contract: declared_dynamic. Crm Qualification Checklist Save

crm.quota.save

Write. Scope: crm.write, admin. Contract: route_inferred. Crm Quota Save

crm.quote.get

Read. Scope: crm.read, admin. Contract: route_inferred. Crm Quote Get

crm.quote.save

Write. Scope: crm.write, admin. Contract: route_inferred. Crm Quote Save

crm.quotes.list

Read. Scope: crm.read, admin. Contract: route_inferred. Crm Quotes List

crm.record.delete

Write. Scope: crm.write, admin. Contract: route_inferred. Crm Record Delete

crm.record.fields.get

Read. Scope: crm.read, admin. Contract: route_inferred. Crm Record Fields Get

crm.record.fields.save

Write. Scope: crm.write, admin. Contract: route_inferred. Crm Record Fields Save

crm.record.get

Read. Scope: crm.read, admin. Contract: route_inferred. Crm Record Get

crm.record.history

Read. Scope: crm.read, admin. Contract: route_inferred. Crm Record History

crm.record.save

Write. Scope: crm.write, admin. Contract: route_inferred. Crm Record Save

crm.record.share.set

Write. Scope: crm.write, admin. Contract: route_inferred. Crm Record Share Set

crm.record.share.unset

Write. Scope: crm.write, admin. Contract: route_inferred. Crm Record Share Unset

crm.record.shares

Write. Scope: crm.write, admin. Contract: route_inferred. Crm Record Shares

crm.records.list

Read. Scope: crm.read, admin. Contract: route_inferred. Crm Records List

crm.restore.email.consent

Write. Scope: crm.write, admin. Contract: route_inferred. Contact Restore Email Consent

crm.resync.from.platform

Write. Scope: crm.write, admin. Contract: route_inferred. Contact Resync From Platform

crm.retention.catalog

Write. Scope: crm.write, admin. Contract: route_inferred. Crm Retention Catalog

crm.revert

Write. Scope: crm.write, admin. Contract: declared_dynamic. Crm Revert

crm.runtime.policy.get

Read. Scope: crm.read, admin. Contract: declared_dynamic. Crm Runtime Policy Get

crm.runtime.policy.remote.wipe

Read. Scope: crm.read, admin. Contract: declared_dynamic. Crm Runtime Policy Remote Wipe

crm.runtime.policy.save

Write. Scope: crm.write, admin. Contract: declared_dynamic. Crm Runtime Policy Save

crm.save

Write. Scope: crm.write, admin. Contract: route_inferred. Contact Save

crm.scoring.rule.ai

Write. Scope: crm.write, admin. Contract: route_inferred. Crm Scoring Rule Ai

crm.scoring.rule.delete

Write. Scope: crm.write, admin. Contract: route_inferred. Crm Scoring Rule Delete

crm.scoring.rule.list

Read. Scope: crm.read, admin. Contract: declared_dynamic. Crm Scoring Rule List

crm.scoring.rule.save

Write. Scope: crm.write, admin. Contract: route_inferred. Crm Scoring Rule Save

crm.segments.delete

Write. Scope: crm.write. Contract: source_inferred. Crm Segments Delete Retry-safe with idempotency_key.

crm.segments.list

Read. Scope: crm.read. Contract: source_inferred. Crm Segments List

crm.segments.members

Read. Scope: crm.read. Contract: source_inferred. Crm Segments Members

crm.segments.preview

Read. Scope: crm.read. Contract: source_inferred. Crm Segments Preview

crm.segments.save

Write. Scope: crm.write. Contract: source_inferred. Crm Segments Save Retry-safe with idempotency_key.

crm.segments.suggestions.accept

Write. Scope: crm.write. Contract: source_inferred. Crm Segments Suggestions Accept Retry-safe with idempotency_key.

crm.segments.suggestions.dismiss

Write. Scope: crm.write. Contract: source_inferred. Crm Segments Suggestions Dismiss Retry-safe with idempotency_key.

crm.segments.suggestions.list

Read. Scope: crm.read. Contract: source_inferred. Crm Segments Suggestions List

crm.semantic.search

Read. Scope: crm.read, admin. Contract: route_inferred. Crm Semantic Search

crm.send.email

Write. Scope: crm.write, admin. Contract: route_inferred. Contact Send Email

crm.send.email.route.crm.send.email

Write. Scope: crm.write, admin. Contract: route_inferred. Crm Send Email

crm.send.for.signature

Write. Scope: crm.write, admin. Contract: route_inferred. Crm Send For Signature

crm.send.payment.link

Write. Scope: crm.write, admin. Contract: route_inferred. Crm Send Payment Link

crm.sequence.action

Write. Scope: crm.write, admin. Contract: route_inferred. Crm Sequence Action

crm.sequence.runs

Read. Scope: crm.read, admin. Contract: route_inferred. Crm Sequence Runs

crm.setup.status

Read. Scope: crm.read, admin. Contract: declared_dynamic. Crm Setup Status

crm.sharing.rules.get

Write. Scope: crm.write, admin. Contract: route_inferred. Crm Sharing Rules Get

crm.sharing.rules.save

Write. Scope: crm.write, admin. Contract: route_inferred. Crm Sharing Rules Save

crm.subject.registry

Write. Scope: crm.write, admin. Contract: route_inferred. Crm Subject Registry

crm.subscriptions.list

Read. Scope: crm.read, admin. Contract: route_inferred. Crm Subscriptions List

crm.subscriptions.rollup

Read. Scope: crm.read, admin. Contract: declared_dynamic. Crm Subscriptions Rollup

crm.subscriptions.sync

Write. Scope: crm.write, admin. Contract: declared_dynamic. Crm Subscriptions Sync

crm.task.create

Write. Scope: crm.write, admin. Contract: declared_dynamic. Crm Task Create

crm.tasks.list

Read. Scope: crm.read, admin. Contract: declared_dynamic. Crm Tasks List

crm.team.parent.set

Write. Scope: crm.write, admin. Contract: route_inferred. Crm Team Parent Set

crm.team.rules.set

Write. Scope: crm.write, admin. Contract: route_inferred. Crm Team Rules Set

crm.team.save

Write. Scope: crm.write, admin. Contract: route_inferred. Crm Team Save

crm.teams.list

Read. Scope: crm.read, admin. Contract: declared_dynamic. Crm Teams List

crm.territory.set

Write. Scope: crm.write, admin. Contract: route_inferred. Crm Territory Set

crm.video.status

Read. Scope: crm.read, admin. Contract: declared_dynamic. Crm Video Status

crm.views.delete

Write. Scope: crm.write, admin. Contract: declared_dynamic. Crm Views Delete

crm.views.list

Read. Scope: crm.read, admin. Contract: declared_dynamic. Crm Views List

crm.views.save

Write. Scope: crm.write, admin. Contract: declared_dynamic. Crm Views Save

crm.webhooks.delete

Write. Scope: crm.write. Contract: source_inferred. Crm Webhooks Delete Retry-safe with idempotency_key.

crm.webhooks.list

Read. Scope: crm.read. Contract: explicit. List CRM outbound webhook endpoints and recent deliveries

crm.webhooks.save

Write. Scope: crm.write. Contract: source_inferred. Crm Webhooks Save Retry-safe with idempotency_key.

crm.webhooks.test

Write. Scope: crm.write. Contract: source_inferred. Crm Webhooks Test Retry-safe with idempotency_key.

crm.workflows.delete

Write. Scope: crm.write. Contract: source_inferred. Crm Workflows Delete Retry-safe with idempotency_key.

crm.workflows.list

Read. Scope: crm.read. Contract: source_inferred. Crm Workflows List

crm.workflows.save

Write. Scope: crm.write. Contract: source_inferred. Crm Workflows Save Retry-safe with idempotency_key.

Wateja wa wateja (44)

customers.analyze

Write. Scope: customers.write, journey.write, admin. Contract: route_inferred. Analyze a customer journey with AI Required fields: client_id.

customers.behaviour

Read. Scope: admin. Contract: route_inferred. Cdp Behaviour

customers.behaviour.analyze

Write. Scope: admin. Contract: route_inferred. Cdp Behaviour Analyze

customers.chat.embed.backfill

Write. Scope: customers.write, admin. Contract: route_inferred. Client Chat Embed Backfill

customers.chat.embed.status

Read. Scope: customers.read, admin. Contract: declared_dynamic. Client Chat Embed Status

customers.chat.faq.ai.generate

Write. Scope: customers.write, admin. Contract: route_inferred. Client Chat Faq Ai Generate

customers.chat.faq.approve.all

Write. Scope: customers.write, admin. Contract: route_inferred. Client Chat Faq Approve All

customers.chat.faq.delete

Write. Scope: customers.write, admin. Contract: route_inferred. Client Chat Faq Delete

customers.chat.faq.delete.all

Write. Scope: customers.write, admin. Contract: declared_dynamic. Client Chat Faq Delete All

customers.chat.faq.export

Write. Scope: customers.write, admin. Contract: declared_dynamic. Client Chat Faq Export

customers.chat.faq.generate

Write. Scope: customers.write, admin. Contract: route_inferred. Client Chat Faq Generate

customers.chat.faq.import

Write. Scope: customers.write, admin. Contract: route_inferred. Client Chat Faq Import

customers.chat.faq.list

Write. Scope: customers.write, admin. Contract: route_inferred. Client Chat Faq List

customers.chat.faq.save

Write. Scope: customers.write, admin. Contract: route_inferred. Client Chat Faq Save

customers.chat.faq.set.help

Write. Scope: customers.write, admin. Contract: route_inferred. Client Chat Faq Set Help

customers.chat.faq.set.help.all

Write. Scope: customers.write, admin. Contract: route_inferred. Client Chat Faq Set Help All

customers.chat.faq.status

Write. Scope: customers.write, admin. Contract: route_inferred. Client Chat Faq Status

customers.chat.grant.upload

Write. Scope: customers.write, admin. Contract: route_inferred. Client Chat Grant Upload

customers.chat.help.set.slug

Write. Scope: customers.write, admin. Contract: route_inferred. Client Chat Help Set Slug

customers.chat.knowledge.crawl.step

Write. Scope: customers.write, admin. Contract: route_inferred. Client Chat Knowledge Crawl Step

customers.chat.knowledge.delete

Write. Scope: customers.write, admin. Contract: route_inferred. Client Chat Knowledge Delete

customers.chat.knowledge.delete.all

Write. Scope: customers.write, admin. Contract: declared_dynamic. Client Chat Knowledge Delete All

customers.chat.knowledge.delete.duplicates

Write. Scope: customers.write, admin. Contract: declared_dynamic. Client Chat Knowledge Delete Duplicates

customers.chat.knowledge.duplicates

Write. Scope: customers.write, admin. Contract: declared_dynamic. Client Chat Knowledge Duplicates

customers.chat.knowledge.export.json

Write. Scope: customers.write, admin. Contract: declared_dynamic. Client Chat Knowledge Export Json

customers.chat.knowledge.import.json

Write. Scope: customers.write, admin. Contract: route_inferred. Client Chat Knowledge Import Json

customers.chat.knowledge.preview

Write. Scope: customers.write, admin. Contract: route_inferred. Client Chat Knowledge Preview

customers.chat.knowledge.recrawl

Write. Scope: customers.write, admin. Contract: route_inferred. Client Chat Knowledge Recrawl

customers.chat.knowledge.test.url

Write. Scope: customers.write, admin. Contract: route_inferred. Client Chat Knowledge Test Url

customers.chat.revoke.upload

Write. Scope: customers.write, admin. Contract: route_inferred. Client Chat Revoke Upload

customers.chat.upload.agent.avatar

Write. Scope: customers.write, admin. Contract: declared_dynamic. Client Chat Upload Agent Avatar

customers.chat.upload.ai.avatar

Write. Scope: customers.write, admin. Contract: declared_dynamic. Client Chat Upload Ai Avatar

customers.chat.upload.icon

Write. Scope: customers.write, admin. Contract: declared_dynamic. Client Chat Upload Icon

customers.client.analyze

Write. Scope: admin. Contract: route_inferred. Cdp Client Analyze

customers.client.delete

Write. Scope: admin. Contract: route_inferred. Cdp Client Delete

customers.client.export

Write. Scope: admin. Contract: route_inferred. Cdp Client Export

customers.client.journey

Read. Scope: admin. Contract: route_inferred. Cdp Client Journey

customers.client.prepare.outreach

Write. Scope: customers.write, admin. Contract: route_inferred. Cdp Client Prepare Outreach

customers.clients.list

Read. Scope: admin. Contract: route_inferred. Cdp Clients List

customers.detail

Read. Scope: customers.read, admin. Contract: route_inferred. Client Detail

customers.get

Read. Scope: customers.read, crm.read, admin. Contract: route_inferred. Get a customer profile Required fields: client_id.

customers.journey

Read. Scope: customers.read, journey.read, admin. Contract: route_inferred. Get a complete customer journey Required fields: client_id.

customers.list

Read. Scope: customers.read, crm.read, admin. Contract: route_inferred. List known customers

customers.outreach.prepare

Write. Scope: customers.write, crm.write, admin. Contract: route_inferred. Prepare CRM outreach for a customer Required fields: client_id.

departments (1)

departments.list

Read. Scope: departments.read, admin. Contract: source_inferred. Departments List

barua pepe (2)

email.template.send

Write. Scope: email.write, admin. Contract: source_inferred. Send one governed workspace email template Required fields: template, to. Retry-safe with idempotency_key.

email.templates.list

Read. Scope: email.read, admin. Contract: source_inferred. List email templates available to this workspace

engagement (163)

engagement.ab.autowinner

Write. Scope: engagement.write, admin. Contract: route_inferred. Promo Ab Autowinner

engagement.ab.bandit

Write. Scope: engagement.write, admin. Contract: route_inferred. Promo Ab Bandit

engagement.address.get

Read. Scope: engagement.read, admin. Contract: declared_dynamic. Survey Address Get

engagement.address.save

Write. Scope: engagement.write, admin. Contract: route_inferred. Survey Address Save

engagement.ai.agent

Read. Scope: engagement.read, admin. Contract: route_inferred. Promo Ai Agent

engagement.ai.analyze

Write. Scope: engagement.write, admin. Contract: route_inferred. Promo Ai Analyze

engagement.ai.compile.profile

Read. Scope: engagement.read, admin. Contract: route_inferred. Promo Ai Compile Profile

engagement.ai.copy

Read. Scope: engagement.read, admin. Contract: route_inferred. Promo Ai Copy

engagement.ai.critique

Read. Scope: engagement.read, admin. Contract: declared_dynamic. Promo Ai Critique

engagement.ai.decide

Read. Scope: engagement.read, admin. Contract: route_inferred. Promo Ai Decide

engagement.ai.design

Read. Scope: engagement.read, admin. Contract: route_inferred. Promo Ai Design

engagement.ai.edit

Write. Scope: engagement.write, admin. Contract: route_inferred. Promo Ai Edit

engagement.ai.generate

Write. Scope: engagement.write, admin. Contract: route_inferred. Promo Ai Generate

engagement.ai.ideas

Read. Scope: engagement.read, admin. Contract: declared_dynamic. Promo Ai Ideas

engagement.ai.image

Write. Scope: engagement.write, admin. Contract: route_inferred. Promo Ai Image

engagement.ai.image.edit

Write. Scope: engagement.write, admin. Contract: route_inferred. Promo Ai Image Edit

engagement.ai.localize

Write. Scope: engagement.write, admin. Contract: route_inferred. Promo Ai Localize

engagement.ai.logo

Read. Scope: engagement.read, admin. Contract: route_inferred. Promo Ai Logo

engagement.ai.media.jobs

Read. Scope: engagement.read, admin. Contract: declared_dynamic. Promo Ai Media Jobs

engagement.ai.narrative

Read. Scope: engagement.read, admin. Contract: declared_dynamic. Promo Ai Narrative

engagement.ai.responsive

Read. Scope: engagement.read, admin. Contract: declared_dynamic. Promo Ai Responsive

engagement.ai.variants

Read. Scope: engagement.read, admin. Contract: route_inferred. Promo Ai Variants

engagement.ai.video.start

Write. Scope: engagement.write, admin. Contract: route_inferred. Promo Ai Video Start

engagement.ai.video.status

Write. Scope: engagement.write, admin. Contract: route_inferred. Promo Ai Video Status

engagement.approval.decide

Write. Scope: engagement.write, admin. Contract: route_inferred. Promo Approval Decide

engagement.approval.request

Write. Scope: engagement.write, admin. Contract: route_inferred. Promo Approval Request

engagement.approvals.list

Read. Scope: engagement.read, admin. Contract: route_inferred. Promo Approvals List

engagement.asset.delete

Write. Scope: engagement.write, admin. Contract: route_inferred. Promo Asset Delete

engagement.asset.upload

Write. Scope: engagement.write, admin. Contract: route_inferred. Promo Asset Upload

engagement.assets.list

Read. Scope: engagement.read, admin. Contract: declared_dynamic. Promo Assets List

engagement.audience.materialize

Write. Scope: engagement.write, admin. Contract: route_inferred. Survey Audience Materialize

engagement.audience.save

Write. Scope: engagement.write, admin. Contract: route_inferred. Survey Audience Save

engagement.audience.test

Read. Scope: engagement.read, admin. Contract: route_inferred. Promo Audience Test

engagement.audit.export

Read. Scope: engagement.read, admin. Contract: declared_dynamic. Promo Audit Export

engagement.autoresponder.get

Read. Scope: engagement.read, admin. Contract: route_inferred. Promo Autoresponder Get

engagement.autoresponder.save

Write. Scope: engagement.write, admin. Contract: route_inferred. Promo Autoresponder Save

engagement.bank.delete

Write. Scope: engagement.write, admin. Contract: route_inferred. Survey Bank Delete

engagement.bank.list

Read. Scope: engagement.read, admin. Contract: declared_dynamic. Survey Bank List

engagement.bank.save

Write. Scope: engagement.write, admin. Contract: route_inferred. Survey Bank Save

engagement.bank.used

Write. Scope: engagement.write, admin. Contract: route_inferred. Survey Bank Used

engagement.blackouts.get

Read. Scope: engagement.read, admin. Contract: declared_dynamic. Promo Blackouts Get

engagement.blackouts.save

Write. Scope: engagement.write, admin. Contract: route_inferred. Promo Blackouts Save

engagement.brand.kit.bootstrap

Write. Scope: engagement.write, admin. Contract: route_inferred. Promo Brand Kit Bootstrap

engagement.brand.kit.font.upload

Write. Scope: engagement.write, admin. Contract: route_inferred. Promo Brand Kit Font Upload

engagement.brand.kit.get

Read. Scope: engagement.read, admin. Contract: declared_dynamic. Promo Brand Kit Get

engagement.brand.kit.get.route.survey.brand.kit.get

Read. Scope: engagement.read, admin. Contract: declared_dynamic. Survey Brand Kit Get

engagement.brand.kit.save

Write. Scope: engagement.write, admin. Contract: declared_dynamic. Promo Brand Kit Save

engagement.brand.kit.save.route.survey.brand.kit.save

Write. Scope: engagement.write, admin. Contract: route_inferred. Survey Brand Kit Save

engagement.campaign.archive

Write. Scope: engagement.write, admin. Contract: route_inferred. Promo Campaign Archive

engagement.campaign.delete

Write. Scope: engagement.write, admin. Contract: route_inferred. Promo Campaign Delete

engagement.campaign.duplicate

Read. Scope: engagement.read, admin. Contract: route_inferred. Promo Campaign Duplicate

engagement.campaign.get

Read. Scope: engagement.read, admin. Contract: route_inferred. Promo Campaign Get

engagement.campaign.launch

Write. Scope: engagement.write, admin. Contract: route_inferred. Survey Campaign Launch

engagement.campaign.list

Read. Scope: engagement.read, admin. Contract: route_inferred. Promo Campaign List

engagement.campaign.pause

Read. Scope: engagement.read, admin. Contract: route_inferred. Promo Campaign Pause

engagement.campaign.preview

Read. Scope: engagement.read, admin. Contract: route_inferred. Promo Campaign Preview

engagement.campaign.publish

Write. Scope: engagement.write, admin. Contract: route_inferred. Promo Campaign Publish

engagement.campaign.rollback

Write. Scope: engagement.write, admin. Contract: route_inferred. Promo Campaign Rollback

engagement.campaign.save

Write. Scope: engagement.write, admin. Contract: route_inferred. Promo Campaign Save

engagement.campaign.save.route.survey.campaign.save

Write. Scope: engagement.write, admin. Contract: route_inferred. Survey Campaign Save

engagement.campaign.toggle

Write. Scope: engagement.write, admin. Contract: route_inferred. Promo Campaign Toggle

engagement.campaign.versions

Read. Scope: engagement.read, admin. Contract: route_inferred. Promo Campaign Versions

engagement.comment.add

Write. Scope: engagement.write, admin. Contract: route_inferred. Promo Comment Add

engagement.comments.add

Write. Scope: engagement.write, admin. Contract: route_inferred. Survey Comments Add

engagement.comments.delete

Write. Scope: engagement.write, admin. Contract: route_inferred. Survey Comments Delete

engagement.comments.list

Read. Scope: engagement.read, admin. Contract: route_inferred. Promo Comments List

engagement.comments.list.route.survey.comments.list

Read. Scope: engagement.read, admin. Contract: route_inferred. Survey Comments List

engagement.comments.resolve

Write. Scope: engagement.write, admin. Contract: route_inferred. Survey Comments Resolve

engagement.connectors.catalog

Read. Scope: engagement.read, admin. Contract: declared_dynamic. Promo Connectors Catalog

engagement.coupon.providers

Read. Scope: engagement.read, admin. Contract: declared_dynamic. Promo Coupon Providers

engagement.coupons.clear

Write. Scope: engagement.write, admin. Contract: route_inferred. Promo Coupons Clear

engagement.coupons.stats

Read. Scope: engagement.read, admin. Contract: route_inferred. Promo Coupons Stats

engagement.coupons.upload

Write. Scope: engagement.write, admin. Contract: route_inferred. Promo Coupons Upload

engagement.delete

Write. Scope: engagement.write, admin. Contract: route_inferred. Announcement Delete

engagement.delete.route.tour.delete

Write. Scope: engagement.write, admin. Contract: route_inferred. Tour Delete

engagement.delivery.analytics

Read. Scope: engagement.read, admin. Contract: route_inferred. Survey Delivery Analytics

engagement.delivery.dashboard

Read. Scope: engagement.read, admin. Contract: route_inferred. Survey Delivery Dashboard

engagement.deployment.ab.promote

Write. Scope: engagement.write, admin. Contract: route_inferred. Survey Deployment Ab Promote

engagement.deployment.ab.save

Write. Scope: engagement.write, admin. Contract: route_inferred. Survey Deployment Ab Save

engagement.deployment.publish

Write. Scope: engagement.write, admin. Contract: route_inferred. Survey Deployment Publish

engagement.deployment.save

Write. Scope: engagement.write, admin. Contract: route_inferred. Survey Deployment Save

engagement.deployment.status

Write. Scope: engagement.write, admin. Contract: route_inferred. Survey Deployment Status

engagement.detail

Read. Scope: engagement.read, admin. Contract: route_inferred. Campaign Detail

engagement.digest.save

Write. Scope: engagement.write, admin. Contract: route_inferred. Survey Digest Save

engagement.feed.catalog

Read. Scope: engagement.read, admin. Contract: declared_dynamic. Promo Feed Catalog

engagement.feed.items

Read. Scope: engagement.read, admin. Contract: route_inferred. Promo Feed Items

engagement.geo.preview

Read. Scope: engagement.read, admin. Contract: route_inferred. Promo Geo Preview

engagement.idle.cron.set

Write. Scope: engagement.write, admin. Contract: route_inferred. Proactive Idle Cron Set

engagement.import.create

Write. Scope: engagement.write, admin. Contract: route_inferred. Survey Import Create

engagement.import.replay

Write. Scope: engagement.write, admin. Contract: route_inferred. Survey Import Replay

engagement.leads.export

Read. Scope: engagement.read, admin. Contract: route_inferred. Promo Leads Export

engagement.leads.list

Read. Scope: engagement.read, admin. Contract: route_inferred. Promo Leads List

engagement.list

Read. Scope: engagement.read, admin. Contract: declared_dynamic. Announcements List

engagement.list.route.tours.list

Read. Scope: engagement.read, admin. Contract: declared_dynamic. Tours List

engagement.module.set.ai.live

Write. Scope: engagement.write, admin. Contract: route_inferred. Promo Module Set Ai Live

engagement.module.set.custom.html

Write. Scope: engagement.write, admin. Contract: route_inferred. Promo Module Set Custom Html

engagement.module.set.enabled

Write. Scope: engagement.write, admin. Contract: route_inferred. Promo Module Set Enabled

engagement.module.status

Read. Scope: engagement.read, admin. Contract: declared_dynamic. Promo Module Status

engagement.onsite.preview

Read. Scope: engagement.read, admin. Contract: route_inferred. Promo Onsite Preview

engagement.pause.all

Write. Scope: engagement.write, admin. Contract: declared_dynamic. Promo Pause All

engagement.presence

Read. Scope: engagement.read, admin. Contract: route_inferred. Promo Presence

engagement.preview.share

Read. Scope: engagement.read, admin. Contract: route_inferred. Promo Preview Share

engagement.push.draft

Write. Scope: engagement.write, admin. Contract: route_inferred. Promo Push Draft

engagement.recipients.issue

Write. Scope: engagement.write, admin. Contract: route_inferred. Survey Recipients Issue

engagement.recipients.list

Read. Scope: engagement.read, admin. Contract: route_inferred. Survey Recipients List

engagement.recipients.revoke

Write. Scope: engagement.write, admin. Contract: route_inferred. Survey Recipients Revoke

engagement.response.detail

Read. Scope: engagement.read, admin. Contract: route_inferred. Survey Response Detail

engagement.responses.browse

Read. Scope: engagement.read, admin. Contract: route_inferred. Survey Responses Browse

engagement.rule.delete

Write. Scope: engagement.write, admin. Contract: route_inferred. Proactive Rule Delete

engagement.rule.save

Write. Scope: engagement.write, admin. Contract: route_inferred. Proactive Rule Save

engagement.rule.stats

Read. Scope: engagement.read, admin. Contract: route_inferred. Proactive Rule Stats

engagement.rule.test

Read. Scope: engagement.read, admin. Contract: route_inferred. Promo Rule Test

engagement.rule.toggle

Write. Scope: engagement.write, admin. Contract: route_inferred. Proactive Rule Toggle

engagement.rules.list

Read. Scope: engagement.read, admin. Contract: declared_dynamic. Proactive Rules List

engagement.save

Write. Scope: engagement.write, admin. Contract: route_inferred. Announcement Save

engagement.save.route.tour.save

Write. Scope: engagement.write, admin. Contract: route_inferred. Tour Save

engagement.stats

Read. Scope: engagement.read, admin. Contract: route_inferred. Promo Stats

engagement.stats.route.tour.stats

Read. Scope: engagement.read, admin. Contract: route_inferred. Tour Stats

engagement.studio.a11y

Write. Scope: engagement.write, admin. Contract: route_inferred. Survey Studio A11y

engagement.studio.ai.generate

Write. Scope: engagement.write, admin. Contract: route_inferred. Survey Studio Ai Generate

engagement.studio.ai.insights

Write. Scope: engagement.write, admin. Contract: route_inferred. Survey Studio Ai Insights

engagement.studio.ai.target

Write. Scope: engagement.write, admin. Contract: route_inferred. Survey Studio Ai Target

engagement.studio.archive

Write. Scope: engagement.write, admin. Contract: route_inferred. Survey Studio Archive

engagement.studio.assets

Read. Scope: engagement.read, admin. Contract: declared_dynamic. Survey Studio Assets

engagement.studio.create

Write. Scope: engagement.write, admin. Contract: route_inferred. Survey Studio Create

engagement.studio.delete

Write. Scope: engagement.write, admin. Contract: route_inferred. Survey Studio Delete

engagement.studio.duplicate

Write. Scope: engagement.write, admin. Contract: route_inferred. Survey Studio Duplicate

engagement.studio.event

Read. Scope: engagement.read, admin. Contract: route_inferred. Promo Studio Event

engagement.studio.get

Read. Scope: engagement.read, admin. Contract: route_inferred. Survey Studio Get

engagement.studio.governance

Write. Scope: engagement.write, admin. Contract: route_inferred. Survey Studio Governance

engagement.studio.list

Read. Scope: engagement.read, admin. Contract: declared_dynamic. Survey Studio List

engagement.studio.preview

Read. Scope: engagement.read, admin. Contract: route_inferred. Survey Studio Preview

engagement.studio.preview.link

Read. Scope: engagement.read, admin. Contract: route_inferred. Survey Studio Preview Link

engagement.studio.publish

Write. Scope: engagement.write, admin. Contract: route_inferred. Survey Studio Publish

engagement.studio.rename

Write. Scope: engagement.write, admin. Contract: route_inferred. Survey Studio Rename

engagement.studio.revert

Write. Scope: engagement.write, admin. Contract: route_inferred. Survey Studio Revert

engagement.studio.save.draft

Write. Scope: engagement.write, admin. Contract: route_inferred. Survey Studio Save Draft

engagement.studio.save.targeting

Write. Scope: engagement.write, admin. Contract: route_inferred. Survey Studio Save Targeting

engagement.studio.set.active

Write. Scope: engagement.write, admin. Contract: route_inferred. Survey Studio Set Active

engagement.studio.set.status

Write. Scope: engagement.write, admin. Contract: route_inferred. Survey Studio Set Status

engagement.studio.template.delete

Write. Scope: engagement.write, admin. Contract: route_inferred. Survey Studio Template Delete

engagement.studio.template.save

Write. Scope: engagement.write, admin. Contract: route_inferred. Survey Studio Template Save

engagement.studio.tpl.preview

Write. Scope: engagement.write, admin. Contract: route_inferred. Survey Studio Tpl Preview

engagement.studio.upload

Write. Scope: engagement.write, admin. Contract: route_inferred. Survey Studio Upload

engagement.studio.webhook

Write. Scope: engagement.write, admin. Contract: route_inferred. Survey Studio Webhook

engagement.targeting.simulate

Read. Scope: engagement.read, admin. Contract: route_inferred. Survey Targeting Simulate

engagement.template.apply

Write. Scope: engagement.write, admin. Contract: route_inferred. Promo Template Apply

engagement.template.list

Read. Scope: engagement.read, admin. Contract: route_inferred. Promo Template List

engagement.template.save.custom

Write. Scope: engagement.write, admin. Contract: route_inferred. Promo Template Save Custom

engagement.toggle

Write. Scope: engagement.write, admin. Contract: route_inferred. Announcement Toggle

engagement.toggle.route.tour.toggle

Write. Scope: engagement.write, admin. Contract: route_inferred. Tour Toggle

engagement.trigger.set.save

Write. Scope: engagement.write, admin. Contract: route_inferred. Survey Trigger Set Save

engagement.variant.delete

Write. Scope: engagement.write, admin. Contract: route_inferred. Promo Variant Delete

engagement.variant.list

Read. Scope: engagement.read, admin. Contract: route_inferred. Promo Variant List

engagement.variant.promote

Write. Scope: engagement.write, admin. Contract: route_inferred. Promo Variant Promote

engagement.variant.save

Write. Scope: engagement.write, admin. Contract: route_inferred. Promo Variant Save

engagement.version.compare

Read. Scope: engagement.read, admin. Contract: route_inferred. Survey Version Compare

engagement.version.get

Read. Scope: engagement.read, admin. Contract: route_inferred. Promo Version Get

engagement.version.label

Write. Scope: engagement.write, admin. Contract: route_inferred. Promo Version Label

engagement.webhook.delete

Write. Scope: engagement.write, admin. Contract: route_inferred. Survey Webhook Delete

engagement.webhook.replay

Write. Scope: engagement.write, admin. Contract: route_inferred. Survey Webhook Replay

engagement.webhook.run

Write. Scope: engagement.write, admin. Contract: route_inferred. Survey Webhook Run

engagement.webhook.save

Write. Scope: engagement.write, admin. Contract: route_inferred. Survey Webhook Save

feedback (8)

feedback.analytics

Read. Scope: feedback.read, admin. Contract: source_inferred. Feedback Analytics

feedback.detractors

Read. Scope: feedback.read, admin. Contract: source_inferred. Feedback Detractors

feedback.get

Read. Scope: feedback.read, admin. Contract: source_inferred. Feedback Get

feedback.ingest

Write. Scope: feedback.write, admin. Contract: explicit. Ingest a feedback record or external review

feedback.list

Read. Scope: feedback.read, admin. Contract: source_inferred. Feedback List

feedback.overview

Read. Scope: feedback.read, admin. Contract: source_inferred. Feedback Overview

feedback.sources.list

Read. Scope: feedback.read, admin. Contract: explicit. List Voice of Customer feedback sources

feedback.update

Write. Scope: feedback.write, admin. Contract: source_inferred. Feedback Update Retry-safe with idempotency_key.

files (1)

files.get

Read. Scope: files.read, admin. Contract: source_inferred. Files Get

yahr (48)

hr.agent.incident.close

Write. Scope: hr.write, admin. Contract: route_inferred. Close an agent incident — the same act that lifts the suspension it caused Required fields: incident_uuid, resolution.

hr.agent.step

Write. Scope: hr.write, admin. Contract: route_inferred. Run one agent step: gate verdict, execution and outcome reported separately Required fields: run_uuid, agent_key, tool_key, jurisdiction, purpose.

hr.agent.step.status

Read. Scope: hr.read, admin. Contract: route_inferred. What actually happened at a step (permitted, executed, proven, failed, compensated) Required fields: run_uuid, seq.

hr.agent.takeover

Write. Scope: hr.write, admin. Contract: route_inferred. A human takes an agent run; no further agent steps are accepted Required fields: run_uuid.

hr.agent.tool.grant

Write. Scope: hr.write, admin. Contract: route_inferred. Grant an agent a tool for one jurisdiction and purpose, up to a risk ceiling Required fields: agent_key, tool_key, jurisdiction, max_risk, purpose.

hr.agent.tools

Read. Scope: hr.read, admin. Contract: declared_dynamic. List the registered typed tools an agent may use, and open agent incidents

hr.ai.corrections

Write. Scope: hr.write, admin. Contract: declared_dynamic. Bundle recent reviewer corrections into a dataset; it is pending privacy review and trains nothing

hr.ai.quality.overview

Read. Scope: hr.read, admin. Contract: declared_dynamic. The AI quality board: sampled defect rate, override pressure per workflow, coaching reception

hr.booking.slots_reconcile

Write. Scope: hr.write, admin. Contract: declared_dynamic. Release booking slots whose claim never became a booked meeting

hr.connectors.certify

Write. Scope: hr.write, admin. Contract: route_inferred. Certify an HR connector (scope sandbox|production; production demands provider-side proof under dual control) Required fields: connector_class, connector_key, scope, evidence, submitted_by.

hr.connectors.health

Read. Scope: hr.read, admin. Contract: route_inferred. One connector account's health: certification level and scope, last reconciliation verdict, failures and webhook backlog Required fields: account_uuid.

hr.decisions.appeals

Write. Scope: hr.write, admin. Contract: route_inferred. File an appeal against an AI decision on a person's behalf; it must be heard by an independent human Required fields: decision_uuid, subject_type, subject_id, grounds.

hr.decisions.explanation

Read. Scope: hr.read, admin. Contract: route_inferred. Plain-language explanation of one AI decision: what was looked at, which policy, and how to appeal Required fields: decision_uuid, audience.

hr.employee.provision

Write. Scope: hr.write, admin. Contract: route_inferred. Provision seatless employee access and send the invitation Required fields: person_uuid.

hr.employee.restore

Write. Scope: hr.write, admin. Contract: route_inferred. Lift an employee access suspension (written reason required) and provision again Required fields: person_uuid, reason.

hr.experience.metrics

Read. Scope: hr.read, admin. Contract: route_inferred. Measured persona experience metrics (self-service rate, decision cycle, coaching usefulness, quality) from live journeys

hr.global.readiness

Read. Scope: hr.read, admin. Contract: declared_dynamic. The whole launch picture: 15-gate leadership score, release readiness checks and jurisdiction coverage

hr.identity.facets

Read. Scope: hr.read, admin. Contract: route_inferred. List a person's identity facets and open conflicts Required fields: person_uuid.

hr.identity.link

Write. Scope: hr.write, admin. Contract: route_inferred. Link an identity facet to a person Required fields: person_uuid, facet_type, facet_key.

hr.interview.room.connect

Write. Scope: hr.write, admin. Contract: route_inferred. Connect the AI to interview media; refuses unless media really reaches the worker Required fields: media_uuid.

hr.interview.room.consent

Write. Scope: hr.write, admin. Contract: route_inferred. Record or withdraw consent for ONE interview purpose (recording, biometric_liveness, transcription) Required fields: media_uuid, purpose, state.

hr.interview.room.pause

Write. Scope: hr.write, admin. Contract: route_inferred. Pause a live interview Required fields: media_uuid.

hr.interview.room.provision

Write. Scope: hr.write, admin. Contract: route_inferred. Provision an interview room (a place to meet — NOT AI participation) Required fields: session_uuid, transport, accommodation_route.

hr.interview.room.state

Read. Scope: hr.read, admin. Contract: route_inferred. Read an interview room, including whether the AI is actually participating Required fields: media_uuid.

hr.interview.room.takeover

Write. Scope: hr.write, admin. Contract: route_inferred. A human takes the interview; the AI cannot speak in it again Required fields: media_uuid, reason.

hr.jurisdiction.capabilities

Read. Scope: hr.read, admin. Contract: route_inferred. What this product may do in one country, per feature, with the law behind each answer Required fields: code.

hr.jurisdiction.change.raise

Write. Scope: hr.write, admin. Contract: route_inferred. Report a change in the law; a high or critical one suspends every lane in that jurisdiction at once Required fields: pack_key, summary, severity.

hr.jurisdiction.coverage

Read. Scope: hr.read, admin. Contract: declared_dynamic. Computed coverage for every market: released pack, named counsel owner, cited sources, passing tests

hr.jurisdiction.explain

Read. Scope: hr.read, admin. Contract: route_inferred. Why an action about one person is allowed, reduced or blocked, with the rule and citation Required fields: person_uuid, feature.

hr.jurisdiction.pack.release

Write. Scope: hr.write, admin. Contract: route_inferred. Put a drafted policy pack into effect; refused without a named counsel owner and a cited law Required fields: release_uuid.

hr.learning.overview

Read. Scope: hr.read, admin. Contract: declared_dynamic. Read courses, paths and enrolments

hr.leave.overview

Read. Scope: hr.read, admin. Contract: declared_dynamic. Read leave types and requests

hr.lifecycle.lanes

Read. Scope: hr.read, admin. Contract: declared_dynamic. Every lifecycle lane with its mode, KPIs and whether a live tool path really exists behind it

hr.marketplace.overview

Read. Scope: hr.read, admin. Contract: declared_dynamic. Read HR connector accounts, conflicts and deliveries

hr.org.tree

Read. Scope: hr.read, admin. Contract: declared_dynamic. Read the organisation tree

hr.people.create

Write. Scope: hr.write, admin. Contract: route_inferred. Create an HR person Required fields: display_name.

hr.people.get

Read. Scope: hr.read, admin. Contract: route_inferred. Get one HR person Required fields: person_uuid.

hr.people.list

Read. Scope: hr.read, admin. Contract: declared_dynamic. List HR people

hr.people.update

Write. Scope: hr.write, admin. Contract: route_inferred. Update an HR person Required fields: person_uuid, display_name, primary_email.

hr.postings.list

Read. Scope: hr.read, admin. Contract: declared_dynamic. List job postings

hr.readiness.read

Read. Scope: hr.read, admin. Contract: declared_dynamic. Run the HR release readiness report

hr.release.verify

Write. Scope: hr.write, admin. Contract: declared_dynamic. Run the four HR release gates (schema, manifest, probe, readiness)

hr.requisitions.create

Write. Scope: hr.write, admin. Contract: route_inferred. Create a requisition Required fields: title, openings, justification.

hr.requisitions.list

Read. Scope: hr.read, admin. Contract: declared_dynamic. List requisitions

hr.thread.delete

Write. Scope: hr.write, admin. Contract: route_inferred. Delete a workforce conversation; refused while it is under legal hold Required fields: thread_uuid, reason.

hr.thread.legal_hold

Write. Scope: hr.write, admin. Contract: route_inferred. Place or lift a legal hold on a workforce conversation Required fields: thread_uuid, on, reason.

hr.thread.retention

Write. Scope: hr.write, admin. Contract: route_inferred. Set a conversation's retention class (standard|extended|permanent) Required fields: thread_uuid, retention_class.

hr.threads.retention_sweep

Write. Scope: hr.write, admin. Contract: declared_dynamic. Run the conversation retention sweep; legal holds are never swept

intent (6)

intent.clear

Write. Scope: intent.write, admin. Contract: declared_dynamic. Intent Clear

intent.funnel

Read. Scope: intent.read, analytics.read, admin. Contract: route_inferred. Read the intent funnel

intent.funnel.aggregate

Read. Scope: intent.read, admin. Contract: route_inferred. Intent Funnel Aggregate

intent.funnel.route.intent.funnel

Read. Scope: intent.read, admin. Contract: route_inferred. Intent Funnel

intent.summary

Read. Scope: intent.read, analytics.read, admin. Contract: route_inferred. Read intent summaries

intent.summary.route.intent.summary

Read. Scope: intent.read, admin. Contract: route_inferred. Intent Summary

ya kb (6)

kb.faq.delete

Write. Scope: kb.write, admin. Contract: source_inferred. Kb Faq Delete Retry-safe with idempotency_key.

kb.faq.generate

Write. Scope: kb.write, admin. Contract: source_inferred. Kb Faq Generate Retry-safe with idempotency_key.

kb.faq.import

Write. Scope: kb.write, admin. Contract: source_inferred. Kb Faq Import Retry-safe with idempotency_key.

kb.faq.list

Read. Scope: kb.read, read, admin. Contract: source_inferred. Kb Faq List

kb.faq.save

Write. Scope: kb.write, admin. Contract: source_inferred. Kb Faq Save Retry-safe with idempotency_key.

kb.faq.set_status

Write. Scope: kb.write, admin. Contract: source_inferred. Kb Faq Set Status Retry-safe with idempotency_key.

knowledge (78)

knowledge.analytics.get

Read. Scope: kb.read, admin. Contract: route_inferred. Help Analytics Get

knowledge.analytics.toggle

Write. Scope: kb.write, admin. Contract: route_inferred. Help Analytics Toggle

knowledge.article.ai.refine

Read. Scope: kb.read, admin. Contract: route_inferred. Help Article Ai Refine

knowledge.article.class.bulk

Write. Scope: kb.write, admin. Contract: route_inferred. Help Article Class Bulk

knowledge.article.delete

Write. Scope: kb.write, admin. Contract: route_inferred. Help Article Delete

knowledge.article.publish

Write. Scope: kb.write, admin. Contract: route_inferred. Help Article Publish

knowledge.article.save

Write. Scope: kb.write, admin. Contract: route_inferred. Help Article Save

knowledge.article.set.category

Write. Scope: kb.write, admin. Contract: route_inferred. Help Article Set Category

knowledge.article.set.public

Write. Scope: kb.write, admin. Contract: route_inferred. Help Article Set Public

knowledge.articles.ai.generate

Write. Scope: kb.write, admin. Contract: route_inferred. Help Articles Ai Generate

knowledge.articles.bulk.delete

Write. Scope: kb.write, admin. Contract: route_inferred. Help Articles Bulk Delete

knowledge.articles.count

Read. Scope: kb.read, admin. Contract: declared_dynamic. Help Articles Count

knowledge.articles.get

Read. Scope: kb.read, admin. Contract: explicit. Get one Help Center article Required fields: article_id.

knowledge.articles.ids

Write. Scope: kb.write, admin. Contract: route_inferred. Help Articles Ids

knowledge.articles.list

Read. Scope: kb.read, admin. Contract: route_inferred. Help Articles List

knowledge.articles.set.public.all

Write. Scope: kb.write, admin. Contract: route_inferred. Help Articles Set Public All

knowledge.categories.ai.merge

Write. Scope: kb.write, admin. Contract: declared_dynamic. Help Categories Ai Merge

knowledge.categories.bulk.delete

Write. Scope: kb.write, admin. Contract: route_inferred. Help Categories Bulk Delete

knowledge.categories.list

Read. Scope: kb.read, admin. Contract: declared_dynamic. Help Categories List

knowledge.categories.merge.dupes

Write. Scope: kb.write, admin. Contract: declared_dynamic. Help Categories Merge Dupes

knowledge.category.delete

Write. Scope: kb.write, admin. Contract: route_inferred. Help Category Delete

knowledge.category.get

Read. Scope: kb.read, admin. Contract: route_inferred. Help Category Get

knowledge.category.save

Write. Scope: kb.write, admin. Contract: route_inferred. Help Category Save

knowledge.center.article.image.upload

Write. Scope: kb.write, admin. Contract: declared_dynamic. Help Center Article Image Upload

knowledge.center.favicon.upload

Write. Scope: kb.write, admin. Contract: declared_dynamic. Help Center Favicon Upload

knowledge.center.hero.dark.upload

Write. Scope: kb.write, admin. Contract: declared_dynamic. Help Center Hero Dark Upload

knowledge.center.hero.upload

Write. Scope: kb.write, admin. Contract: declared_dynamic. Help Center Hero Upload

knowledge.center.logo.dark.upload

Write. Scope: kb.write, admin. Contract: declared_dynamic. Help Center Logo Dark Upload

knowledge.center.logo.upload

Write. Scope: kb.write, admin. Contract: declared_dynamic. Help Center Logo Upload

knowledge.center.og.image.upload

Write. Scope: kb.write, admin. Contract: declared_dynamic. Help Center Og Image Upload

knowledge.center.settings.get

Read. Scope: kb.read, admin. Contract: declared_dynamic. Help Center Settings Get

knowledge.center.settings.save

Write. Scope: kb.write, admin. Contract: route_inferred. Help Center Settings Save

knowledge.center.subhero.dark.upload

Write. Scope: kb.write, admin. Contract: declared_dynamic. Help Center Subhero Dark Upload

knowledge.center.subhero.upload

Write. Scope: kb.write, admin. Contract: declared_dynamic. Help Center Subhero Upload

knowledge.center.translate.estimate

Write. Scope: kb.write, admin. Contract: declared_dynamic. Help Center Translate Estimate

knowledge.center.translate.run

Write. Scope: kb.write, admin. Contract: route_inferred. Help Center Translate Run

knowledge.center.translate.status

Read. Scope: kb.read, admin. Contract: declared_dynamic. Help Center Translate Status

knowledge.center.translate.stop

Write. Scope: kb.write, admin. Contract: declared_dynamic. Help Center Translate Stop

knowledge.center.widget.hero.upload

Write. Scope: kb.write, admin. Contract: declared_dynamic. Help Center Widget Hero Upload

knowledge.center.widget.icon.upload

Write. Scope: kb.write, admin. Contract: declared_dynamic. Help Center Widget Icon Upload

knowledge.comments.deliver.notifications

Write. Scope: kb.write, admin. Contract: route_inferred. Kb Comments Deliver Notifications

knowledge.comments.moderate

Write. Scope: kb.write, admin. Contract: route_inferred. Kb Comments Moderate

knowledge.comments.moderation.list

Read. Scope: kb.read, admin. Contract: route_inferred. Kb Comments Moderation List

knowledge.import.batches

Write. Scope: kb.write, admin. Contract: route_inferred. Kb Import Batches

knowledge.import.connectors

Write. Scope: kb.write, admin. Contract: declared_dynamic. Kb Import Connectors

knowledge.import.csv.preview

Read. Scope: kb.read, admin. Contract: route_inferred. Kb Import Csv Preview

knowledge.import.preview

Write. Scope: kb.write, admin. Contract: route_inferred. Kb Import Preview

knowledge.import.resync

Write. Scope: kb.write, admin. Contract: route_inferred. Kb Import Resync

knowledge.import.run

Write. Scope: kb.write, admin. Contract: route_inferred. Kb Import Run

knowledge.import.undo

Write. Scope: kb.write, admin. Contract: route_inferred. Kb Import Undo

knowledge.insights.generate

Write. Scope: kb.write, admin. Contract: route_inferred. Help Insights Generate

knowledge.insights.get

Read. Scope: kb.read, admin. Contract: declared_dynamic. Help Insights Get

knowledge.mark.reviewed

Write. Scope: kb.write, admin. Contract: declared_dynamic. Kb Mark Reviewed

knowledge.missed.dismiss

Write. Scope: kb.write, admin. Contract: route_inferred. Kb Missed Dismiss

knowledge.missed.draft.article

Write. Scope: kb.write, admin. Contract: route_inferred. Kb Missed Draft Article

knowledge.missed.list

Read. Scope: kb.read, admin. Contract: route_inferred. Kb Missed List

knowledge.missed.mark.published

Write. Scope: kb.write, admin. Contract: route_inferred. Kb Missed Mark Published

knowledge.missed.refresh

Write. Scope: kb.write, admin. Contract: declared_dynamic. Kb Missed Refresh

knowledge.organize.descriptions

Write. Scope: kb.write, admin. Contract: declared_dynamic. Help Organize Descriptions

knowledge.organize.status

Write. Scope: kb.write, admin. Contract: declared_dynamic. Help Organize Status

knowledge.organize.step

Write. Scope: kb.write, admin. Contract: route_inferred. Help Organize Step

knowledge.publish

Write. Scope: kb.write, admin. Contract: route_inferred. Kb Publish

knowledge.reformat.revert

Write. Scope: kb.write, admin. Contract: declared_dynamic. Help Reformat Revert

knowledge.reformat.status

Read. Scope: kb.read, admin. Contract: declared_dynamic. Help Reformat Status

knowledge.reformat.step

Write. Scope: kb.write, admin. Contract: route_inferred. Help Reformat Step

knowledge.review.queue

Read. Scope: kb.read, admin. Contract: declared_dynamic. Kb Review Queue

knowledge.search.gaps

Read. Scope: kb.read, admin. Contract: declared_dynamic. Kb Search Gaps

knowledge.set.featured

Write. Scope: kb.write, admin. Contract: route_inferred. Help Set Featured

knowledge.set.visibility

Write. Scope: kb.write, admin. Contract: declared_dynamic. Kb Set Visibility

knowledge.subdomain.allocate

Write. Scope: kb.write, admin. Contract: route_inferred. Help Subdomain Allocate

knowledge.subdomain.check

Read. Scope: kb.read, admin. Contract: route_inferred. Help Subdomain Check

knowledge.subdomain.release

Write. Scope: kb.write, admin. Contract: route_inferred. Help Subdomain Release

knowledge.taxonomy.organize

Write. Scope: kb.write, admin. Contract: declared_dynamic. Kb Taxonomy Organize

knowledge.taxonomy.status

Read. Scope: kb.read, admin. Contract: declared_dynamic. Kb Taxonomy Status

knowledge.taxonomy.step

Write. Scope: kb.write, admin. Contract: route_inferred. Kb Taxonomy Step

knowledge.widget.categories

Read. Scope: kb.read, admin. Contract: route_inferred. Kb Widget Categories

knowledge.widget.publish

Write. Scope: kb.write, admin. Contract: route_inferred. Kb Widget Publish

knowledge.widget.targets

Read. Scope: kb.read, admin. Contract: route_inferred. Kb Widget Targets

leads (6)

leads.delete

Write. Scope: leads.write, crm.write, admin. Contract: route_inferred. Delete a lead Required fields: lead_id.

leads.delete.route.lead.delete

Write. Scope: leads.write, admin. Contract: route_inferred. Lead Delete

leads.list

Read. Scope: leads.read, crm.read, admin. Contract: route_inferred. List leads

leads.stats

Read. Scope: leads.read, analytics.read, admin. Contract: declared_dynamic. Get lead statistics

leads.stats.route.leads.stats

Read. Scope: leads.read, admin. Contract: declared_dynamic. Leads Stats

leads.update

Write. Scope: leads.write, crm.write, admin. Contract: route_inferred. Update a lead Required fields: lead_id, status.

Malengo ya (4)

meta.action

Read. Scope: none. Contract: explicit. Get one General API action contract Required fields: name.

meta.actions

Read. Scope: none. Contract: explicit. List the complete General API contract

meta.me

Read. Scope: none. Contract: explicit. Describe the authenticated API key and active workspace

meta.scopes

Read. Scope: none. Contract: explicit. List API scopes and the actions protected by each scope

notifications (1)

notifications.list

Read. Scope: notifications.read, admin. Contract: source_inferred. Notifications List

Jukwaa la jukwaa (926)

platform.add.announcement

Write. Scope: platform.write, admin. Contract: declared_dynamic. Add Announcement

platform.add.kb.article

Write. Scope: platform.write, admin. Contract: route_inferred. Add Kb Article

platform.add.todo.item

Write. Scope: platform.write, admin. Contract: route_inferred. Add Todo Item

platform.ai.action.lookup

Write. Scope: platform.write, admin. Contract: route_inferred. Ai Action Lookup

platform.ai.anomaly.detect

Read. Scope: platform.read, admin. Contract: route_inferred. Ai Anomaly Detect

platform.ai.brain.add

Write. Scope: platform.write, admin. Contract: route_inferred. Ai Brain Add

platform.ai.brain.delete

Write. Scope: platform.write, admin. Contract: route_inferred. Ai Brain Delete

platform.ai.brain.edit

Write. Scope: platform.write, admin. Contract: route_inferred. Ai Brain Edit

platform.ai.brain.list

Write. Scope: platform.write, admin. Contract: route_inferred. Ai Brain List

platform.ai.brain.pin

Write. Scope: platform.write, admin. Contract: route_inferred. Ai Brain Pin

platform.ai.brain.status

Write. Scope: platform.write, admin. Contract: route_inferred. Ai Brain Status

platform.ai.chat

Write. Scope: platform.write, admin. Contract: route_inferred. Ai Chat

platform.ai.confidence.stats

Read. Scope: platform.read, admin. Contract: declared_dynamic. Ai Confidence Stats

platform.ai.context.lookup

Write. Scope: platform.write, admin. Contract: route_inferred. Ai Context Lookup

platform.ai.daily.brief

Write. Scope: platform.write, admin. Contract: route_inferred. Ai Daily Brief

platform.ai.daily.brief.check

Read. Scope: platform.read, admin. Contract: declared_dynamic. Ai Daily Brief Check

platform.ai.daily.brief.dismiss

Write. Scope: platform.write, admin. Contract: declared_dynamic. Ai Daily Brief Dismiss

platform.ai.daily.brief.fetch

Write. Scope: platform.write, admin. Contract: route_inferred. Ai Daily Brief Fetch

platform.ai.eval.control.summary

Read. Scope: platform.read, admin. Contract: declared_dynamic. Ai Eval Control Summary

platform.ai.eval.feedback.queue

Read. Scope: platform.read, admin. Contract: declared_dynamic. Ai Eval Feedback Queue

platform.ai.eval.kb.gap.queue

Read. Scope: platform.read, admin. Contract: declared_dynamic. Ai Eval Kb Gap Queue

platform.ai.eval.load

Read. Scope: platform.read, admin. Contract: declared_dynamic. Ai Eval Load

platform.ai.eval.replay.history

Write. Scope: platform.write, admin. Contract: declared_dynamic. Ai Eval Replay History

platform.ai.eval.run

Write. Scope: platform.write, admin. Contract: declared_dynamic. Ai Eval Run

platform.ai.eval.save

Write. Scope: platform.write, admin. Contract: declared_dynamic. Ai Eval Save

platform.ai.eval.score.answer

Read. Scope: platform.read, admin. Contract: declared_dynamic. Ai Eval Score Answer

platform.ai.eval.simulate

Read. Scope: platform.read, admin. Contract: route_inferred. Ai Eval Simulate

platform.ai.feedback.analysis

Read. Scope: platform.read, admin. Contract: declared_dynamic. Ai Feedback Analysis

platform.ai.feedback.stats

Read. Scope: platform.read, admin. Contract: declared_dynamic. Ai Feedback Stats

platform.ai.history.archive

Write. Scope: platform.write, admin. Contract: declared_dynamic. Ai History Archive

platform.ai.history.clear.all

Write. Scope: platform.write, admin. Contract: declared_dynamic. Ai History Clear All

platform.ai.history.delete

Write. Scope: platform.write, admin. Contract: declared_dynamic. Ai History Delete

platform.ai.history.export.csv

Write. Scope: platform.write, admin. Contract: declared_dynamic. Ai History Export Csv

platform.ai.history.get

Write. Scope: platform.write, admin. Contract: declared_dynamic. Ai History Get

platform.ai.history.list

Write. Scope: platform.write, admin. Contract: declared_dynamic. Ai History List

platform.ai.history.stats

Write. Scope: platform.write, admin. Contract: declared_dynamic. Ai History Stats

platform.ai.insight.clear

Write. Scope: platform.write, admin. Contract: route_inferred. Ai Insight Clear

platform.ai.insight.history

Read. Scope: platform.read, admin. Contract: route_inferred. Ai Insight History

platform.ai.insight.report.delete

Write. Scope: platform.write, admin. Contract: route_inferred. Ai Insight Report Delete

platform.ai.insight.report.get

Read. Scope: platform.read, admin. Contract: route_inferred. Ai Insight Report Get

platform.ai.instructions.compress

Write. Scope: platform.write, admin. Contract: declared_dynamic. Ai Instructions Compress

platform.ai.instructions.connector.templates

Read. Scope: platform.read, admin. Contract: declared_dynamic. Ai Instructions Connector Templates

platform.ai.instructions.example

Read. Scope: platform.read, admin. Contract: declared_dynamic. Ai Instructions Example

platform.ai.instructions.load

Write. Scope: platform.write, admin. Contract: declared_dynamic. Ai Instructions Load

platform.ai.instructions.preview

Read. Scope: platform.read, admin. Contract: route_inferred. Ai Instructions Preview

platform.ai.instructions.reset

Write. Scope: platform.write, admin. Contract: declared_dynamic. Ai Instructions Reset

platform.ai.instructions.save

Write. Scope: platform.write, admin. Contract: declared_dynamic. Ai Instructions Save

platform.ai.page.insights

Read. Scope: platform.read, admin. Contract: route_inferred. Ai Page Insights

platform.ai.popup.regen

Write. Scope: platform.write, admin. Contract: route_inferred. Ai Popup Regen

platform.ai.quality.view

Read. Scope: platform.read, admin. Contract: declared_dynamic. Ai Quality View

platform.ai.reasoning.chain.get

Read. Scope: platform.read, admin. Contract: route_inferred. Ai Reasoning Chain Get

platform.ai.score.lead

Write. Scope: platform.write, admin. Contract: route_inferred. Ai Score Lead

platform.ai.smart.alerts

Read. Scope: platform.read, admin. Contract: declared_dynamic. Ai Smart Alerts

platform.ai.spoke

Read. Scope: platform.read, admin. Contract: route_inferred. Ai Spoke

platform.ai.triage.accuracy

Read. Scope: platform.read, admin. Contract: declared_dynamic. Ai Triage Accuracy

platform.ai.whmcs.chat

Write. Scope: platform.write, admin. Contract: route_inferred. Ai Whmcs Chat

platform.ai.writing

Write. Scope: platform.write, admin. Contract: route_inferred. Ai Writing

platform.api.keys.catalog

Read. Scope: admin. Contract: declared_dynamic. Api Keys Catalog

platform.api.keys.create

Write. Scope: admin. Contract: route_inferred. Api Keys Create

platform.api.keys.delete

Write. Scope: admin. Contract: route_inferred. Api Keys Delete

platform.api.keys.list

Read. Scope: admin. Contract: declared_dynamic. Api Keys List

platform.api.keys.revoke

Write. Scope: admin. Contract: route_inferred. Api Keys Revoke

platform.api.keys.update

Write. Scope: admin. Contract: route_inferred. Api Keys Update

platform.audit.export

Read. Scope: admin. Contract: route_inferred. Audit Export

platform.blocked

Write. Scope: platform.write, admin. Contract: route_inferred. Blocked

platform.campaigns

Read. Scope: platform.read, admin. Contract: declared_dynamic. Campaigns

platform.chart.browsers

Read. Scope: platform.read, admin. Contract: declared_dynamic. Chart Browsers

platform.chart.countries

Read. Scope: platform.read, admin. Contract: declared_dynamic. Chart Countries

platform.chart.devices

Read. Scope: platform.read, admin. Contract: declared_dynamic. Chart Devices

platform.chart.hourly

Read. Scope: platform.read, admin. Contract: declared_dynamic. Chart Hourly

platform.chart.new.returning

Read. Scope: platform.read, admin. Contract: declared_dynamic. Chart New Returning

platform.chart.os

Read. Scope: platform.read, admin. Contract: declared_dynamic. Chart Os

platform.chart.sources

Read. Scope: platform.read, admin. Contract: declared_dynamic. Chart Sources

platform.chart.visitors

Read. Scope: platform.read, admin. Contract: route_inferred. Chart Visitors

platform.chatbot.flow.delete

Write. Scope: platform.write, admin. Contract: route_inferred. Chatbot Flow Delete

platform.chatbot.flow.get

Read. Scope: platform.read, admin. Contract: route_inferred. Chatbot Flow Get

platform.chatbot.flow.save

Write. Scope: platform.write, admin. Contract: route_inferred. Chatbot Flow Save

platform.chatbot.flow.stats

Read. Scope: platform.read, admin. Contract: route_inferred. Chatbot Flow Stats

platform.chatbot.flow.test.advance

Write. Scope: platform.write, admin. Contract: route_inferred. Chatbot Flow Test Advance

platform.chatbot.flow.test.start

Write. Scope: platform.write, admin. Contract: route_inferred. Chatbot Flow Test Start

platform.chatbot.flow.toggle

Write. Scope: platform.write, admin. Contract: route_inferred. Chatbot Flow Toggle

platform.chatbot.flows.list

Read. Scope: platform.read, admin. Contract: declared_dynamic. Chatbot Flows List

platform.chatbot.node.delete

Write. Scope: platform.write, admin. Contract: route_inferred. Chatbot Node Delete

platform.chatbot.node.save

Write. Scope: platform.write, admin. Contract: route_inferred. Chatbot Node Save

platform.chatbot.nodes.list

Read. Scope: platform.read, admin. Contract: route_inferred. Chatbot Nodes List

platform.clear.admin.chat.history

Write. Scope: platform.write, admin. Contract: declared_dynamic. Clear Admin Chat History

platform.command.center.view

Read. Scope: platform.read, admin. Contract: declared_dynamic. Command Center View

platform.commerce.actf.execute

Write. Scope: commerce.write, admin. Contract: declared_dynamic. Commerce Actf Execute

platform.commerce.actf.policy.save

Write. Scope: commerce.write, admin. Contract: declared_dynamic. Commerce Actf Policy Save

platform.commerce.actf.review

Read. Scope: commerce.read, admin. Contract: declared_dynamic. Commerce Actf Review

platform.commerce.actf.simulate

Read. Scope: commerce.read, admin. Contract: declared_dynamic. Commerce Actf Simulate

platform.commerce.analytics.report

Write. Scope: commerce.write, admin. Contract: declared_dynamic. Commerce Analytics Report

platform.commerce.analytics.report.email

Write. Scope: commerce.write, admin. Contract: declared_dynamic. Commerce Analytics Report Email

platform.commerce.autonomy.issue

Write. Scope: commerce.write, admin. Contract: declared_dynamic. Commerce Autonomy Issue

platform.commerce.autonomy.status

Read. Scope: commerce.read, admin. Contract: declared_dynamic. Commerce Autonomy Status

platform.commerce.collections.delete

Write. Scope: commerce.write, admin. Contract: route_inferred. Commerce Collections Delete

platform.commerce.collections.save

Write. Scope: commerce.write, admin. Contract: declared_dynamic. Commerce Collections Save

platform.commerce.customer.block

Write. Scope: commerce.write, admin. Contract: declared_dynamic. Commerce Customer Block

platform.commerce.customer.credit.add

Write. Scope: commerce.write, admin. Contract: declared_dynamic. Commerce Customer Credit Add

platform.commerce.customer.save

Write. Scope: commerce.write, admin. Contract: declared_dynamic. Commerce Customer Save

platform.commerce.customers.list

Read. Scope: commerce.read, admin. Contract: declared_dynamic. Commerce Customers List

platform.commerce.digital.codes.import

Write. Scope: commerce.write, admin. Contract: declared_dynamic. Commerce Digital Codes Import

platform.commerce.digital.config.save

Write. Scope: commerce.write, admin. Contract: declared_dynamic. Commerce Digital Config Save

platform.commerce.digital.file.upload

Write. Scope: commerce.write, admin. Contract: route_inferred. Commerce Digital File Upload

platform.commerce.fulfilment.transition

Write. Scope: commerce.write, admin. Contract: declared_dynamic. Commerce Fulfilment Transition

platform.commerce.intelligence.economics.save

Write. Scope: commerce.write, admin. Contract: declared_dynamic. Commerce Intelligence Economics Save

platform.commerce.intelligence.market.price.save

Write. Scope: commerce.write, admin. Contract: declared_dynamic. Commerce Intelligence Market Price Save

platform.commerce.intelligence.market.save

Write. Scope: commerce.write, admin. Contract: declared_dynamic. Commerce Intelligence Market Save

platform.commerce.kit.apply

Write. Scope: commerce.write, admin. Contract: route_inferred. Commerce Kit Apply

platform.commerce.kit.preview

Read. Scope: commerce.read, admin. Contract: route_inferred. Commerce Kit Preview

platform.commerce.kits.list

Read. Scope: commerce.read, admin. Contract: declared_dynamic. Commerce Kits List

platform.commerce.launch.readiness

Read. Scope: commerce.read, admin. Contract: declared_dynamic. Commerce Launch Readiness

platform.commerce.menu.ai.build

Write. Scope: commerce.write, admin. Contract: declared_dynamic. Commerce Menu Ai Build

platform.commerce.menus.save

Write. Scope: commerce.write, admin. Contract: declared_dynamic. Commerce Menus Save

platform.commerce.merchandising.save

Write. Scope: commerce.write, admin. Contract: declared_dynamic. Commerce Merchandising Save

platform.commerce.midmarket.operations

Write. Scope: commerce.write, admin. Contract: declared_dynamic. Commerce Midmarket Operations

platform.commerce.onboarding.ai.draft

Write. Scope: commerce.write, admin. Contract: declared_dynamic. Commerce Onboarding Ai Draft

platform.commerce.onboarding.apply

Write. Scope: commerce.write, admin. Contract: declared_dynamic. Commerce Onboarding Apply

platform.commerce.option.sets.generate

Write. Scope: commerce.write, admin. Contract: route_inferred. Commerce Option Sets Generate

platform.commerce.option.sets.save

Write. Scope: commerce.write, admin. Contract: declared_dynamic. Commerce Option Sets Save

platform.commerce.option.templates

Read. Scope: commerce.read, admin. Contract: declared_dynamic. Commerce Option Templates

platform.commerce.order.refundable

Read. Scope: commerce.read, admin. Contract: declared_dynamic. Commerce Order Refundable

platform.commerce.order.ship

Write. Scope: commerce.write, admin. Contract: declared_dynamic. Commerce Order Ship

platform.commerce.order.shipments

Read. Scope: commerce.read, admin. Contract: declared_dynamic. Commerce Order Shipments

platform.commerce.orders.list

Read. Scope: commerce.read, admin. Contract: declared_dynamic. Commerce Orders List

platform.commerce.orders.transition

Write. Scope: commerce.write, admin. Contract: route_inferred. Commerce Orders Transition

platform.commerce.page.ai.draft

Write. Scope: commerce.write, admin. Contract: declared_dynamic. Commerce Page Ai Draft

platform.commerce.page.ai.refine

Write. Scope: commerce.write, admin. Contract: declared_dynamic. Commerce Page Ai Refine

platform.commerce.page.render

Write. Scope: commerce.write, admin. Contract: declared_dynamic. Commerce Page Render

platform.commerce.pages.delete

Write. Scope: commerce.write, admin. Contract: route_inferred. Commerce Pages Delete

platform.commerce.pages.list

Write. Scope: commerce.write, admin. Contract: declared_dynamic. Commerce Pages List

platform.commerce.pages.save

Write. Scope: commerce.write, admin. Contract: declared_dynamic. Commerce Pages Save

platform.commerce.price.advice

Read. Scope: commerce.read, admin. Contract: declared_dynamic. Commerce Price Advice

platform.commerce.products.ai.copy

Read. Scope: commerce.read, admin. Contract: declared_dynamic. Commerce Products Ai Copy

platform.commerce.products.bulk

Write. Scope: commerce.write, admin. Contract: route_inferred. Commerce Products Bulk

platform.commerce.products.catalog.meta

Read. Scope: commerce.read, admin. Contract: declared_dynamic. Commerce Products Catalog Meta

platform.commerce.products.delete

Write. Scope: commerce.write, admin. Contract: route_inferred. Commerce Products Delete

platform.commerce.products.duplicate

Write. Scope: commerce.write, admin. Contract: route_inferred. Commerce Products Duplicate

platform.commerce.products.export.csv

Read. Scope: commerce.read, admin. Contract: declared_dynamic. Commerce Products Export Csv

platform.commerce.products.image.alt.ai

Read. Scope: commerce.read, admin. Contract: route_inferred. Commerce Products Image Alt Ai

platform.commerce.products.image.delete

Write. Scope: commerce.write, admin. Contract: route_inferred. Commerce Products Image Delete

platform.commerce.products.image.update

Write. Scope: commerce.write, admin. Contract: declared_dynamic. Commerce Products Image Update

platform.commerce.products.image.upload

Write. Scope: commerce.write, admin. Contract: route_inferred. Commerce Products Image Upload

platform.commerce.products.images.list

Read. Scope: commerce.read, admin. Contract: route_inferred. Commerce Products Images List

platform.commerce.products.images.reorder

Write. Scope: commerce.write, admin. Contract: declared_dynamic. Commerce Products Images Reorder

platform.commerce.products.import.csv

Write. Scope: commerce.write, admin. Contract: route_inferred. Commerce Products Import Csv

platform.commerce.products.list

Read. Scope: commerce.read, admin. Contract: declared_dynamic. Commerce Products List

platform.commerce.products.save

Write. Scope: commerce.write, admin. Contract: declared_dynamic. Commerce Products Save

platform.commerce.refunds.complete.manual

Write. Scope: commerce.write, admin. Contract: declared_dynamic. Commerce Refunds Complete Manual

platform.commerce.refunds.request

Write. Scope: commerce.write, admin. Contract: declared_dynamic. Commerce Refunds Request

platform.commerce.returns.transition

Write. Scope: commerce.write, admin. Contract: declared_dynamic. Commerce Returns Transition

platform.commerce.size.charts.delete

Write. Scope: commerce.write, admin. Contract: route_inferred. Commerce Size Charts Delete

platform.commerce.size.charts.save

Write. Scope: commerce.write, admin. Contract: declared_dynamic. Commerce Size Charts Save

platform.commerce.store.maturity

Read. Scope: commerce.read, admin. Contract: declared_dynamic. Commerce Store Maturity

platform.commerce.storefront.brand.import

Write. Scope: commerce.write, admin. Contract: route_inferred. Commerce Storefront Brand Import

platform.commerce.storefront.domain.remove

Write. Scope: commerce.write, admin. Contract: route_inferred. Commerce Storefront Domain Remove

platform.commerce.storefront.domain.set

Write. Scope: commerce.write, admin. Contract: route_inferred. Commerce Storefront Domain Set

platform.commerce.storefront.logo.upload

Write. Scope: commerce.write, admin. Contract: route_inferred. Commerce Storefront Logo Upload

platform.commerce.storefront.page.ai.seo

Read. Scope: commerce.read, admin. Contract: declared_dynamic. Commerce Storefront Page Ai Seo

platform.commerce.storefront.slug.save

Write. Scope: commerce.write, admin. Contract: declared_dynamic. Commerce Storefront Slug Save

platform.commerce.supply.chain

Write. Scope: commerce.write, admin. Contract: declared_dynamic. Commerce Supply Chain

platform.commerce.variants.delete

Write. Scope: commerce.write, admin. Contract: route_inferred. Commerce Variants Delete

platform.commerce.variants.save

Write. Scope: commerce.write, admin. Contract: declared_dynamic. Commerce Variants Save

platform.commerce.wallet.topup.refund

Write. Scope: commerce.write, admin. Contract: declared_dynamic. Commerce Wallet Topup Refund

platform.commerce.wallet.topups.list

Read. Scope: commerce.read, admin. Contract: declared_dynamic. Commerce Wallet Topups List

platform.complete.todo.item

Write. Scope: platform.write, admin. Contract: route_inferred. Complete Todo Item

platform.consent.log.list

Read. Scope: platform.read, admin. Contract: route_inferred. Consent Log List

platform.countries

Read. Scope: platform.read, admin. Contract: declared_dynamic. Countries

platform.country.detail

Read. Scope: platform.read, admin. Contract: route_inferred. Country Detail

platform.custom.code.approve

Write. Scope: platform.write, admin. Contract: route_inferred. Custom Code Approve

platform.custom.code.disable

Write. Scope: platform.write, admin. Contract: route_inferred. Custom Code Disable

platform.custom.code.reject

Write. Scope: platform.write, admin. Contract: route_inferred. Custom Code Reject

platform.custom.code.rollback

Write. Scope: platform.write, admin. Contract: route_inferred. Custom Code Rollback

platform.custom.code.status

Read. Scope: platform.read, admin. Contract: route_inferred. Custom Code Status

platform.delete.todo.item

Write. Scope: platform.write, admin. Contract: route_inferred. Delete Todo Item

platform.devices

Read. Scope: platform.read, admin. Contract: declared_dynamic. Devices

platform.diag.check.resolutions

Read. Scope: platform.read, admin. Contract: declared_dynamic. Diag Check Resolutions

platform.diag.dismiss

Write. Scope: platform.write, admin. Contract: route_inferred. Diag Dismiss

platform.diag.event.taxonomy

Read. Scope: platform.read, admin. Contract: declared_dynamic. Diag Event Taxonomy

platform.diag.identity.restitch

Write. Scope: admin. Contract: declared_dynamic. Diag Identity Restitch

platform.diag.recheck

Write. Scope: platform.write, admin. Contract: route_inferred. Diag Recheck

platform.diag.recheck.all

Write. Scope: platform.write, admin. Contract: declared_dynamic. Diag Recheck All

platform.diag.report

Write. Scope: platform.write, admin. Contract: route_inferred. Diag Report

platform.diag.unmute

Write. Scope: platform.write, admin. Contract: route_inferred. Diag Unmute

platform.dismiss.credit.alert

Write. Scope: admin. Contract: route_inferred. Dismiss Credit Alert

platform.domain.knowledge.ai.generate

Write. Scope: platform.write, admin. Contract: route_inferred. Domain Knowledge Ai Generate

platform.domain.knowledge.delete

Write. Scope: platform.write, admin. Contract: route_inferred. Domain Knowledge Delete

platform.domain.knowledge.list

Write. Scope: platform.write, admin. Contract: route_inferred. Domain Knowledge List

platform.domain.knowledge.save

Write. Scope: platform.write, admin. Contract: route_inferred. Domain Knowledge Save

platform.domain.knowledge.toggle

Write. Scope: platform.write, admin. Contract: route_inferred. Domain Knowledge Toggle

platform.domain.verify.add

Write. Scope: platform.write, admin. Contract: route_inferred. Domain Verify Add

platform.domain.verify.list

Read. Scope: platform.read, admin. Contract: declared_dynamic. Domain Verify List

platform.domain.verify.recheck

Write. Scope: platform.write, admin. Contract: route_inferred. Domain Verify Recheck

platform.domain.verify.remove

Write. Scope: platform.write, admin. Contract: route_inferred. Domain Verify Remove

platform.dynamic.action.dispatch

Write. Scope: platform.write, admin. Contract: route_inferred. Dynamic Action Dispatch

platform.events.clear.all

Write. Scope: platform.write, admin. Contract: declared_dynamic. Events Clear All

platform.events.list

Read. Scope: platform.read, admin. Contract: route_inferred. Events List

platform.experiment.delete

Write. Scope: platform.write, admin. Contract: route_inferred. Experiment Delete

platform.experiment.results

Read. Scope: platform.read, admin. Contract: route_inferred. Experiment Results

platform.experiment.save

Write. Scope: platform.write, admin. Contract: route_inferred. Experiment Save

platform.experiments.clear.all

Write. Scope: platform.write, admin. Contract: declared_dynamic. Experiments Clear All

platform.experiments.list

Read. Scope: platform.read, admin. Contract: declared_dynamic. Experiments List

platform.failed.logins.clear.all

Write. Scope: platform.write, admin. Contract: declared_dynamic. Failed Logins Clear All

platform.failed.logins.clear.history

Write. Scope: platform.write, admin. Contract: declared_dynamic. Failed Logins Clear History

platform.failed.logins.journey

Write. Scope: platform.write, admin. Contract: route_inferred. Failed Logins Journey

platform.failed.logins.list

Write. Scope: platform.write, admin. Contract: declared_dynamic. Failed Logins List

platform.failed.logins.unblock

Write. Scope: platform.write, admin. Contract: route_inferred. Failed Logins Unblock

platform.feedback.analysis.get

Read. Scope: platform.read, admin. Contract: declared_dynamic. Feedback Analysis Get

platform.feedback.analysis.run

Write. Scope: platform.write, admin. Contract: route_inferred. Feedback Analysis Run

platform.feedback.analytics.all

Read. Scope: platform.read, admin. Contract: route_inferred. Feedback Analytics All

platform.feedback.analytics.detractors

Read. Scope: platform.read, admin. Contract: route_inferred. Feedback Analytics Detractors

platform.feedback.analytics.metrics

Read. Scope: platform.read, admin. Contract: route_inferred. Feedback Analytics Metrics

platform.feedback.analytics.overview

Read. Scope: platform.read, admin. Contract: route_inferred. Feedback Analytics Overview

platform.feedback.analytics.segments

Read. Scope: platform.read, admin. Contract: route_inferred. Feedback Analytics Segments

platform.feedback.analytics.sentiment

Read. Scope: platform.read, admin. Contract: route_inferred. Feedback Analytics Sentiment

platform.feedback.analytics.themes

Read. Scope: platform.read, admin. Contract: route_inferred. Feedback Analytics Themes

platform.feedback.analytics.trends

Read. Scope: platform.read, admin. Contract: route_inferred. Feedback Analytics Trends

platform.feedback.assignees.list

Read. Scope: platform.read, admin. Contract: declared_dynamic. Feedback Assignees List

platform.feedback.event.outbox.drain

Write. Scope: platform.write, admin. Contract: route_inferred. Feedback Event Outbox Drain

platform.feedback.exports.create

Write. Scope: platform.write, admin. Contract: route_inferred. Feedback Exports Create

platform.feedback.exports.get

Read. Scope: platform.read, admin. Contract: route_inferred. Feedback Exports Get

platform.feedback.external.review.ingest

Write. Scope: platform.write, admin. Contract: route_inferred. Feedback External Review Ingest

platform.feedback.ingest.create

Write. Scope: platform.write, admin. Contract: route_inferred. Feedback Ingest Create

platform.feedback.items.assign

Write. Scope: platform.write, admin. Contract: route_inferred. Feedback Items Assign

platform.feedback.items.evidence

Read. Scope: platform.read, admin. Contract: route_inferred. Feedback Items Evidence

platform.feedback.items.follow.up.complete

Write. Scope: platform.write, admin. Contract: route_inferred. Feedback Items Follow Up Complete

platform.feedback.items.follow.up.set

Write. Scope: platform.write, admin. Contract: route_inferred. Feedback Items Follow Up Set Required fields: bool.

platform.feedback.items.get

Read. Scope: platform.read, admin. Contract: route_inferred. Feedback Items Get

platform.feedback.items.list

Read. Scope: platform.read, admin. Contract: route_inferred. Feedback Items List

platform.feedback.items.mark.read

Write. Scope: platform.write, admin. Contract: route_inferred. Feedback Items Mark Read

platform.feedback.items.notes.add

Write. Scope: platform.write, admin. Contract: route_inferred. Feedback Items Notes Add

platform.feedback.items.set.priority

Write. Scope: platform.write, admin. Contract: route_inferred. Feedback Items Set Priority

platform.feedback.items.set.status

Write. Scope: platform.write, admin. Contract: route_inferred. Feedback Items Set Status

platform.feedback.items.tags.add

Write. Scope: platform.write, admin. Contract: route_inferred. Feedback Items Tags Add

platform.feedback.items.tags.remove

Write. Scope: platform.write, admin. Contract: route_inferred. Feedback Items Tags Remove

platform.feedback.list

Read. Scope: platform.read, admin. Contract: route_inferred. Feedback List

platform.feedback.reconciliation

Read. Scope: platform.read, admin. Contract: declared_dynamic. Feedback Reconciliation

platform.feedback.reports.delete

Write. Scope: platform.write, admin. Contract: declared_dynamic. Feedback Reports Delete

platform.feedback.reports.email

Read. Scope: platform.read, admin. Contract: declared_dynamic. Feedback Reports Email

platform.feedback.reports.get

Read. Scope: platform.read, admin. Contract: declared_dynamic. Feedback Reports Get

platform.feedback.reports.list

Read. Scope: platform.read, admin. Contract: declared_dynamic. Feedback Reports List

platform.feedback.satisfaction.advice.last

Read. Scope: platform.read, admin. Contract: declared_dynamic. Feedback Satisfaction Advice Last

platform.feedback.satisfaction.advise

Read. Scope: platform.read, admin. Contract: declared_dynamic. Feedback Satisfaction Advise

platform.feedback.satisfaction.overview

Read. Scope: platform.read, admin. Contract: declared_dynamic. Feedback Satisfaction Overview

platform.feedback.sources.health

Read. Scope: platform.read, admin. Contract: declared_dynamic. Feedback Sources Health

platform.feedback.sources.list

Read. Scope: platform.read, admin. Contract: declared_dynamic. Feedback Sources List

platform.feedback.sources.rebuild

Write. Scope: platform.write, admin. Contract: route_inferred. Feedback Sources Rebuild

platform.feedback.sources.replay

Write. Scope: platform.write, admin. Contract: route_inferred. Feedback Sources Replay

platform.feedback.stats

Write. Scope: platform.write, admin. Contract: declared_dynamic. Feedback Stats

platform.fx.refresh.now

Write. Scope: platform.write, admin. Contract: declared_dynamic. Fx Refresh Now

platform.geoip.autodetect

Read. Scope: platform.read, admin. Contract: declared_dynamic. Geoip Autodetect

platform.get.admin.chat.history

Read. Scope: platform.read, admin. Contract: declared_dynamic. Get Admin Chat History

platform.get.ai.snapshot

Write. Scope: platform.write, admin. Contract: route_inferred. Get Ai Snapshot

platform.get.campaign.groups

Read. Scope: platform.read, admin. Contract: declared_dynamic. Get Campaign Groups

platform.get.client.chat.knowledge.overview

Write. Scope: platform.write, admin. Contract: declared_dynamic. Get Client Chat Knowledge Overview

platform.get.kb.categories

Read. Scope: platform.read, admin. Contract: route_inferred. Get Kb Categories

platform.get.live.health.snapshot

Read. Scope: platform.read, admin. Contract: route_inferred. Get Live Health Snapshot

platform.get.pwa.chat.prefs

Write. Scope: platform.write, admin. Contract: declared_dynamic. Get Pwa Chat Prefs

platform.get.servers

Read. Scope: platform.read, admin. Contract: declared_dynamic. Get Servers

platform.get.survey.config

Read. Scope: platform.read, admin. Contract: declared_dynamic. Get Survey Config

platform.get.ticket.options

Read. Scope: platform.read, admin. Contract: declared_dynamic. Get Ticket Options

platform.get.ticket.thread

Read. Scope: platform.read, admin. Contract: route_inferred. Get Ticket Thread

platform.get.todo.list

Read. Scope: platform.read, admin. Contract: declared_dynamic. Get Todo List

platform.get.widget.advanced

Read. Scope: platform.read, admin. Contract: route_inferred. Get Widget Advanced

platform.governance.summary

Read. Scope: platform.read, admin. Contract: route_inferred. Governance Summary

platform.groups.create

Write. Scope: platform.write, admin. Contract: route_inferred. Groups Create

platform.groups.delete

Write. Scope: platform.write, admin. Contract: route_inferred. Groups Delete

platform.groups.list

Write. Scope: platform.write, admin. Contract: route_inferred. Groups List

platform.groups.rename

Write. Scope: platform.write, admin. Contract: route_inferred. Groups Rename

platform.groups.set.primary

Write. Scope: platform.write, admin. Contract: route_inferred. Groups Set Primary

platform.hc.preview.mint

Read. Scope: platform.read, admin. Contract: route_inferred. Hc Preview Mint

platform.hc.template.apply

Write. Scope: platform.write, admin. Contract: route_inferred. Hc Template Apply

platform.hc.template.delete

Write. Scope: platform.write, admin. Contract: route_inferred. Hc Template Delete

platform.hc.template.preview

Read. Scope: platform.read, admin. Contract: route_inferred. Hc Template Preview

platform.hc.template.save

Write. Scope: platform.write, admin. Contract: route_inferred. Hc Template Save

platform.hc.templates.list

Read. Scope: platform.read, admin. Contract: declared_dynamic. Hc Templates List

platform.hc.translation.review.get

Read. Scope: platform.read, admin. Contract: declared_dynamic. Hc Translation Review Get

platform.hc.translation.review.list

Read. Scope: platform.read, admin. Contract: declared_dynamic. Hc Translation Review List

platform.hc.translation.review.revert

Write. Scope: platform.write, admin. Contract: declared_dynamic. Hc Translation Review Revert

platform.hc.translation.review.save

Write. Scope: platform.write, admin. Contract: declared_dynamic. Hc Translation Review Save

platform.heatmap

Read. Scope: platform.read, admin. Contract: route_inferred. Heatmap

platform.hr.access.grant.manual

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Access Grant Manual

platform.hr.access.policy.list

Read. Scope: platform.read, admin. Contract: declared_dynamic. Hr Access Policy List

platform.hr.access.policy.set

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Access Policy Set

platform.hr.access.request

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Access Request

platform.hr.access.revoke

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Access Revoke

platform.hr.accommodation.list

Read. Scope: platform.read, admin. Contract: declared_dynamic. Hr Accommodation List

platform.hr.accommodation.resolve

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Accommodation Resolve

platform.hr.agent.assign

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Agent Assign

platform.hr.agent.compensation.retry

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Agent Compensation Retry

platform.hr.agent.compensation.sweep

Write. Scope: platform.write, admin. Contract: declared_dynamic. Hr Agent Compensation Sweep

platform.hr.agent.compensations

Read. Scope: platform.read, admin. Contract: declared_dynamic. Hr Agent Compensations

platform.hr.agent.incident.close

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Agent Incident Close

platform.hr.agent.register

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Agent Register

platform.hr.agent.step

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Agent Step

platform.hr.agent.step.status

Read. Scope: platform.read, admin. Contract: route_inferred. Hr Agent Step Status

platform.hr.agent.tool.auth

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Agent Tool Auth

platform.hr.agent.tool.grant

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Agent Tool Grant

platform.hr.agent.tools

Read. Scope: platform.read, admin. Contract: declared_dynamic. Hr Agent Tools

platform.hr.ai.act.build

Write. Scope: platform.write, admin. Contract: declared_dynamic. Hr Ai Act Build

platform.hr.ai.act.export

Read. Scope: platform.read, admin. Contract: declared_dynamic. Hr Ai Act Export

platform.hr.ai.act.fria.record

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Ai Act Fria Record

platform.hr.ai.act.notice.publish

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Ai Act Notice Publish

platform.hr.ai.act.overseer.assign

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Ai Act Overseer Assign

platform.hr.ai.act.overseer.revoke

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Ai Act Overseer Revoke

platform.hr.ai.act.overview

Read. Scope: platform.read, admin. Contract: declared_dynamic. Hr Ai Act Overview

platform.hr.ai.metering.export

Read. Scope: platform.read, admin. Contract: route_inferred. Hr Ai Metering Export

platform.hr.ai.metering.overview

Read. Scope: platform.read, admin. Contract: route_inferred. Hr Ai Metering Overview

platform.hr.ai.metering.settings.save

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Ai Metering Settings Save

platform.hr.ai.status

Read. Scope: platform.read, admin. Contract: declared_dynamic. Hr Ai Status

platform.hr.analytics.ask

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Analytics Ask

platform.hr.analytics.snapshot

Read. Scope: platform.read, admin. Contract: declared_dynamic. Hr Analytics Snapshot

platform.hr.app.move

Write. Scope: platform.write, admin. Contract: route_inferred. Hr App Move

platform.hr.appeal.list

Read. Scope: platform.read, admin. Contract: declared_dynamic. Hr Appeal List

platform.hr.appeal.resolve

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Appeal Resolve

platform.hr.application.history

Read. Scope: platform.read, admin. Contract: route_inferred. Hr Application History

platform.hr.application.list

Read. Scope: platform.read, admin. Contract: declared_dynamic. Hr Application List

platform.hr.assign

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Assign

platform.hr.auto.offer.run

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Auto Offer Run

platform.hr.autonomy.lane.demote

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Autonomy Lane Demote

platform.hr.autonomy.lane.install

Write. Scope: platform.write, admin. Contract: declared_dynamic. Hr Autonomy Lane Install

platform.hr.autonomy.lane.promote

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Autonomy Lane Promote

platform.hr.autonomy.lane.review

Read. Scope: platform.read, admin. Contract: route_inferred. Hr Autonomy Lane Review

platform.hr.autonomy.lane.shadow

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Autonomy Lane Shadow

platform.hr.autonomy.lanes

Read. Scope: platform.read, admin. Contract: declared_dynamic. Hr Autonomy Lanes

platform.hr.autonomy.overview

Read. Scope: platform.read, admin. Contract: declared_dynamic. Hr Autonomy Overview

platform.hr.availability.save

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Availability Save

platform.hr.band.approve

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Band Approve

platform.hr.band.list

Read. Scope: platform.read, admin. Contract: declared_dynamic. Hr Band List

platform.hr.band.save

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Band Save

platform.hr.benchmarks.contribute.now

Write. Scope: platform.write, admin. Contract: declared_dynamic. Hr Benchmarks Contribute Now

platform.hr.benchmarks.opt.in

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Benchmarks Opt In

platform.hr.benchmarks.opt.out

Write. Scope: platform.write, admin. Contract: declared_dynamic. Hr Benchmarks Opt Out

platform.hr.benchmarks.overview

Read. Scope: platform.read, admin. Contract: declared_dynamic. Hr Benchmarks Overview

platform.hr.benefit.enroll

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Benefit Enroll

platform.hr.benefit.plan.save

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Benefit Plan Save

platform.hr.bias.audit.list

Read. Scope: platform.read, admin. Contract: declared_dynamic. Hr Bias Audit List

platform.hr.bias.audit.run

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Bias Audit Run

platform.hr.booking.link.save

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Booking Link Save

platform.hr.booking.slots.reconcile

Write. Scope: platform.write, admin. Contract: declared_dynamic. Hr Booking Slots Reconcile

platform.hr.breaker.reset

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Breaker Reset

platform.hr.broadcast.audience.options

Read. Scope: platform.read, admin. Contract: declared_dynamic. Hr Broadcast Audience Options

platform.hr.broadcast.list

Read. Scope: platform.read, admin. Contract: declared_dynamic. Hr Broadcast List

platform.hr.broadcast.preview

Read. Scope: platform.read, admin. Contract: route_inferred. Hr Broadcast Preview

platform.hr.broadcast.send

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Broadcast Send

platform.hr.budget.set

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Budget Set

platform.hr.calibration.close

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Calibration Close

platform.hr.calibration.move

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Calibration Move

platform.hr.calibration.open

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Calibration Open

platform.hr.capabilities.get

Read. Scope: platform.read, admin. Contract: route_inferred. Hr Capabilities Get

platform.hr.capability.set

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Capability Set

platform.hr.capability.trail

Read. Scope: platform.read, admin. Contract: route_inferred. Hr Capability Trail

platform.hr.cards.refresh

Write. Scope: platform.write, admin. Contract: declared_dynamic. Hr Cards Refresh

platform.hr.case.assign

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Case Assign

platform.hr.case.attachment.add

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Case Attachment Add

platform.hr.case.attachment.list

Read. Scope: platform.read, admin. Contract: route_inferred. Hr Case Attachment List

platform.hr.case.categories

Read. Scope: platform.read, admin. Contract: declared_dynamic. Hr Case Categories

platform.hr.case.event.add

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Case Event Add

platform.hr.case.get

Read. Scope: platform.read, admin. Contract: route_inferred. Hr Case Get

platform.hr.case.grant.access

Read. Scope: platform.read, admin. Contract: route_inferred. Hr Case Grant Access

platform.hr.case.intake.mailbox

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Case Intake Mailbox

platform.hr.case.list

Read. Scope: platform.read, admin. Contract: declared_dynamic. Hr Case List

platform.hr.case.open

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Case Open

platform.hr.case.route

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Case Route

platform.hr.case.thread

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Case Thread

platform.hr.case.tighten

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Case Tighten

platform.hr.certification.define

Read. Scope: platform.read, admin. Contract: route_inferred. Hr Certification Define

platform.hr.certification.list

Read. Scope: platform.read, admin. Contract: route_inferred. Hr Certification List

platform.hr.certification.record

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Certification Record

platform.hr.certification.state

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Certification State

platform.hr.certification.types

Read. Scope: platform.read, admin. Contract: declared_dynamic. Hr Certification Types

platform.hr.check.list

Read. Scope: platform.read, admin. Contract: declared_dynamic. Hr Check List

platform.hr.check.manual.result

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Check Manual Result

platform.hr.check.order

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Check Order

platform.hr.check.requery

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Check Requery

platform.hr.check.void

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Check Void

platform.hr.checkin.record

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Checkin Record

platform.hr.coach.feedback

Read. Scope: platform.read, admin. Contract: route_inferred. Hr Coach Feedback

platform.hr.coach.me

Read. Scope: platform.read, admin. Contract: declared_dynamic. Hr Coach Me

platform.hr.coach.receive

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Coach Receive

platform.hr.comp.change.approve

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Comp Change Approve

platform.hr.comp.change.request

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Comp Change Request

platform.hr.compliance.build

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Compliance Build

platform.hr.compliance.list

Read. Scope: platform.read, admin. Contract: declared_dynamic. Hr Compliance List

platform.hr.connector.cert.revoke

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Connector Cert Revoke

platform.hr.connector.cert.submissions

Read. Scope: platform.read, admin. Contract: declared_dynamic. Hr Connector Cert Submissions

platform.hr.connector.cert.submit

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Connector Cert Submit

platform.hr.connector.certify

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Connector Certify

platform.hr.connector.health

Read. Scope: platform.read, admin. Contract: route_inferred. Hr Connector Health

platform.hr.connector.options

Read. Scope: platform.read, admin. Contract: route_inferred. Hr Connector Options

platform.hr.connector.revoke

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Connector Revoke

platform.hr.contract.list

Read. Scope: platform.read, admin. Contract: route_inferred. Hr Contract List

platform.hr.copilot.apply

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Copilot Apply

platform.hr.copilot.plan

Read. Scope: platform.read, admin. Contract: route_inferred. Hr Copilot Plan

platform.hr.copilot.recipes

Read. Scope: platform.read, admin. Contract: declared_dynamic. Hr Copilot Recipes

platform.hr.copilot.reject

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Copilot Reject

platform.hr.correction.dataset.build

Write. Scope: platform.write, admin. Contract: declared_dynamic. Hr Correction Dataset Build

platform.hr.correction.datasets

Read. Scope: platform.read, admin. Contract: declared_dynamic. Hr Correction Datasets

platform.hr.correction.privacy.review

Read. Scope: platform.read, admin. Contract: route_inferred. Hr Correction Privacy Review

platform.hr.course.enroll

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Course Enroll

platform.hr.course.save

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Course Save

platform.hr.course.skills.tag

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Course Skills Tag

platform.hr.decision.appeal.assign

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Decision Appeal Assign

platform.hr.decision.appeal.file

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Decision Appeal File

platform.hr.decision.appeal.resolve

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Decision Appeal Resolve

platform.hr.decision.appeals.list

Read. Scope: platform.read, admin. Contract: declared_dynamic. Hr Decision Appeals List

platform.hr.decision.explanation

Read. Scope: platform.read, admin. Contract: route_inferred. Hr Decision Explanation

platform.hr.decisions.recent

Read. Scope: platform.read, admin. Contract: declared_dynamic. Hr Decisions Recent

platform.hr.directory.visibility.get

Read. Scope: platform.read, admin. Contract: declared_dynamic. Hr Directory Visibility Get

platform.hr.directory.visibility.set

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Directory Visibility Set

platform.hr.discipline.decide

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Discipline Decide

platform.hr.discipline.propose

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Discipline Propose

platform.hr.document.access.log

Read. Scope: platform.read, admin. Contract: route_inferred. Hr Document Access Log

platform.hr.document.deletion.request

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Document Deletion Request

platform.hr.document.hold

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Document Hold

platform.hr.document.intake

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Document Intake

platform.hr.document.list

Read. Scope: platform.read, admin. Contract: route_inferred. Hr Document List

platform.hr.document.requirement.add

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Document Requirement Add

platform.hr.document.requirement.remove

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Document Requirement Remove

platform.hr.document.review.approve

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Document Review Approve

platform.hr.document.reviews

Read. Scope: platform.read, admin. Contract: declared_dynamic. Hr Document Reviews

platform.hr.dsr.list

Write. Scope: platform.write, admin. Contract: declared_dynamic. Hr Dsr List

platform.hr.dsr.transition

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Dsr Transition

platform.hr.email.intake.log

Read. Scope: platform.read, admin. Contract: declared_dynamic. Hr Email Intake Log

platform.hr.employee.access.events

Read. Scope: platform.read, admin. Contract: route_inferred. Hr Employee Access Events

platform.hr.employee.provision

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Employee Provision

platform.hr.employee.restore

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Employee Restore

platform.hr.employee.suspend

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Employee Suspend

platform.hr.employment.activate

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Employment Activate

platform.hr.employment.end

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Employment End

platform.hr.enterprise.approve

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Enterprise Approve

platform.hr.equipment.delivered

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Equipment Delivered

platform.hr.equipment.request

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Equipment Request

platform.hr.equipment.returned

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Equipment Returned

platform.hr.escrow.resolve

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Escrow Resolve

platform.hr.evidence.a11y.record

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Evidence A11y Record

platform.hr.evidence.attest

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Evidence Attest

platform.hr.evidence.dr.record

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Evidence Dr Record

platform.hr.evidence.ledgers

Read. Scope: platform.read, admin. Contract: declared_dynamic. Hr Evidence Ledgers

platform.hr.evidence.load.record

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Evidence Load Record

platform.hr.evidence.owner.assign

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Evidence Owner Assign

platform.hr.expense.confirm

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Expense Confirm

platform.hr.expense.decide

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Expense Decide

platform.hr.expense.handoff

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Expense Handoff

platform.hr.expense.overview

Read. Scope: platform.read, admin. Contract: declared_dynamic. Hr Expense Overview

platform.hr.expense.policy.save

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Expense Policy Save

platform.hr.experience.metrics

Read. Scope: platform.read, admin. Contract: route_inferred. Hr Experience Metrics

platform.hr.expiry.run

Write. Scope: platform.write, admin. Contract: declared_dynamic. Hr Expiry Run

platform.hr.fairness.cohort.define

Read. Scope: platform.read, admin. Contract: route_inferred. Hr Fairness Cohort Define

platform.hr.fairness.cohorts

Read. Scope: platform.read, admin. Contract: declared_dynamic. Hr Fairness Cohorts

platform.hr.fairness.evaluate

Read. Scope: platform.read, admin. Contract: route_inferred. Hr Fairness Evaluate

platform.hr.faq.delete

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Faq Delete

platform.hr.faq.draft

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Faq Draft

platform.hr.faq.list

Read. Scope: platform.read, admin. Contract: declared_dynamic. Hr Faq List

platform.hr.faq.save

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Faq Save

platform.hr.faq.state

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Faq State

platform.hr.feedback.list

Read. Scope: platform.read, admin. Contract: declared_dynamic. Hr Feedback List

platform.hr.feedback.record

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Feedback Record

platform.hr.flag.set

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Flag Set

platform.hr.flags.get

Read. Scope: platform.read, admin. Contract: declared_dynamic. Hr Flags Get

platform.hr.frontline.overview

Write. Scope: platform.write, admin. Contract: declared_dynamic. Hr Frontline Overview

platform.hr.gig.decide

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Gig Decide

platform.hr.gig.post

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Gig Post

platform.hr.global.readiness

Read. Scope: platform.read, admin. Contract: declared_dynamic. Hr Global Readiness

platform.hr.goal.create

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Goal Create

platform.hr.goal.draft

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Goal Draft

platform.hr.goal.update

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Goal Update

platform.hr.grievance.file

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Grievance File

platform.hr.grievance.outcome

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Grievance Outcome

platform.hr.headcount.approve

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Headcount Approve

platform.hr.headcount.draft

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Headcount Draft

platform.hr.headcount.list

Read. Scope: platform.read, admin. Contract: declared_dynamic. Hr Headcount List

platform.hr.hire

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Hire

platform.hr.hiring.decide

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Hiring Decide

platform.hr.holiday.save

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Holiday Save

platform.hr.identity.admin.options

Read. Scope: platform.read, admin. Contract: declared_dynamic. Hr Identity Admin Options

platform.hr.identity.conflict.resolve

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Identity Conflict Resolve

platform.hr.identity.coverage.plan

Read. Scope: platform.read, admin. Contract: declared_dynamic. Hr Identity Coverage Plan

platform.hr.identity.facets

Read. Scope: platform.read, admin. Contract: route_inferred. Hr Identity Facets

platform.hr.identity.history

Read. Scope: platform.read, admin. Contract: declared_dynamic. Hr Identity History

platform.hr.identity.link

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Identity Link

platform.hr.identity.revoke

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Identity Revoke

platform.hr.identity.verification.record

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Identity Verification Record

platform.hr.incident.list

Read. Scope: platform.read, admin. Contract: declared_dynamic. Hr Incident List

platform.hr.incident.open

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Incident Open

platform.hr.incident.step

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Incident Step

platform.hr.interview.recording.start

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Interview Recording Start

platform.hr.interview.recording.upload

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Interview Recording Upload

platform.hr.interview.review

Read. Scope: platform.read, admin. Contract: route_inferred. Hr Interview Review

platform.hr.interview.room.answer

Read. Scope: platform.read, admin. Contract: route_inferred. Hr Interview Room Answer

platform.hr.interview.room.ask

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Interview Room Ask

platform.hr.interview.room.connect

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Interview Room Connect

platform.hr.interview.room.consent

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Interview Room Consent

platform.hr.interview.room.end

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Interview Room End

platform.hr.interview.room.leave

Read. Scope: platform.read, admin. Contract: route_inferred. Hr Interview Room Leave

platform.hr.interview.room.list

Read. Scope: platform.read, admin. Contract: declared_dynamic. Hr Interview Room List

platform.hr.interview.room.observe

Read. Scope: platform.read, admin. Contract: route_inferred. Hr Interview Room Observe

platform.hr.interview.room.pause

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Interview Room Pause

platform.hr.interview.room.provision

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Interview Room Provision

platform.hr.interview.room.reconnect

Read. Scope: platform.read, admin. Contract: route_inferred. Hr Interview Room Reconnect

platform.hr.interview.room.resume

Read. Scope: platform.read, admin. Contract: route_inferred. Hr Interview Room Resume

platform.hr.interview.room.state

Read. Scope: platform.read, admin. Contract: route_inferred. Hr Interview Room State

platform.hr.interview.room.takeover

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Interview Room Takeover

platform.hr.interview.schedule

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Interview Schedule

platform.hr.interview.transcript.correct

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Interview Transcript Correct

platform.hr.investigation.close

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Investigation Close

platform.hr.investigation.finding

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Investigation Finding

platform.hr.investigation.hold

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Investigation Hold

platform.hr.investigation.open

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Investigation Open

platform.hr.investigation.triage

Read. Scope: platform.read, admin. Contract: route_inferred. Hr Investigation Triage

platform.hr.iplan.approve

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Iplan Approve

platform.hr.iplan.create

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Iplan Create

platform.hr.iplan.list

Read. Scope: platform.read, admin. Contract: declared_dynamic. Hr Iplan List

platform.hr.iscore.human

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Iscore Human

platform.hr.iscore.run

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Iscore Run

platform.hr.isession.attach.meeting

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Isession Attach Meeting

platform.hr.isession.control

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Isession Control

platform.hr.isession.list

Read. Scope: platform.read, admin. Contract: declared_dynamic. Hr Isession List

platform.hr.isession.liveness

Read. Scope: platform.read, admin. Contract: route_inferred. Hr Isession Liveness

platform.hr.isession.schedule

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Isession Schedule

platform.hr.job.arch.analyse

Write. Scope: platform.write, admin. Contract: declared_dynamic. Hr Job Arch Analyse

platform.hr.job.arch.apply

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Job Arch Apply

platform.hr.job.arch.approve

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Job Arch Approve

platform.hr.job.arch.overview

Read. Scope: platform.read, admin. Contract: declared_dynamic. Hr Job Arch Overview

platform.hr.job.arch.propose

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Job Arch Propose

platform.hr.job.arch.reject

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Job Arch Reject

platform.hr.job.family.save

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Job Family Save

platform.hr.job.level.save

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Job Level Save

platform.hr.job.profile.save

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Job Profile Save

platform.hr.job.version.draft.ai

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Job Version Draft Ai

platform.hr.job.version.publish

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Job Version Publish

platform.hr.job.version.save

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Job Version Save

platform.hr.job.versions

Read. Scope: platform.read, admin. Contract: route_inferred. Hr Job Versions

platform.hr.jurisdiction.capabilities

Read. Scope: platform.read, admin. Contract: route_inferred. Hr Jurisdiction Capabilities

platform.hr.jurisdiction.case.run

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Jurisdiction Case Run

platform.hr.jurisdiction.case.save

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Jurisdiction Case Save

platform.hr.jurisdiction.change.assess

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Jurisdiction Change Assess

platform.hr.jurisdiction.change.close

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Jurisdiction Change Close

platform.hr.jurisdiction.change.raise

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Jurisdiction Change Raise

platform.hr.jurisdiction.coverage

Read. Scope: platform.read, admin. Contract: declared_dynamic. Hr Jurisdiction Coverage

platform.hr.jurisdiction.explain

Read. Scope: platform.read, admin. Contract: route_inferred. Hr Jurisdiction Explain

platform.hr.jurisdiction.overlay.list

Read. Scope: platform.read, admin. Contract: route_inferred. Hr Jurisdiction Overlay List

platform.hr.jurisdiction.overlay.save

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Jurisdiction Overlay Save

platform.hr.jurisdiction.pack.draft

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Jurisdiction Pack Draft

platform.hr.jurisdiction.pack.release

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Jurisdiction Pack Release

platform.hr.jurisdiction.pack.withdraw

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Jurisdiction Pack Withdraw

platform.hr.jurisdiction.release.list

Read. Scope: platform.read, admin. Contract: declared_dynamic. Hr Jurisdiction Release List

platform.hr.jurisdiction.rule.save

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Jurisdiction Rule Save

platform.hr.jurisdiction.source.declare

Read. Scope: platform.read, admin. Contract: route_inferred. Hr Jurisdiction Source Declare

platform.hr.jurisdiction.transfer.declare

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Jurisdiction Transfer Declare

platform.hr.kill.flip

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Kill Flip

platform.hr.kill.toggle

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Kill Toggle

platform.hr.kiosk.register

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Kiosk Register

platform.hr.kiosk.revoke

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Kiosk Revoke

platform.hr.knowledge.pack.install

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Knowledge Pack Install

platform.hr.knowledge.pack.remove

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Knowledge Pack Remove

platform.hr.knowledge.packs

Read. Scope: platform.read, admin. Contract: declared_dynamic. Hr Knowledge Packs

platform.hr.leadership.score

Read. Scope: platform.read, admin. Contract: declared_dynamic. Hr Leadership Score

platform.hr.learning.assign.mandatory

Write. Scope: platform.write, admin. Contract: declared_dynamic. Hr Learning Assign Mandatory

platform.hr.learning.overview

Read. Scope: platform.read, admin. Contract: declared_dynamic. Hr Learning Overview

platform.hr.leave.decide

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Leave Decide

platform.hr.leave.overview

Read. Scope: platform.read, admin. Contract: declared_dynamic. Hr Leave Overview

platform.hr.leave.policy.save

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Leave Policy Save

platform.hr.leave.type.save

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Leave Type Save

platform.hr.letter.issue

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Letter Issue

platform.hr.letter.kinds

Read. Scope: platform.read, admin. Contract: declared_dynamic. Hr Letter Kinds

platform.hr.letter.preview

Read. Scope: platform.read, admin. Contract: route_inferred. Hr Letter Preview

platform.hr.listening.close

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Listening Close

platform.hr.listening.overview

Read. Scope: platform.read, admin. Contract: declared_dynamic. Hr Listening Overview

platform.hr.listening.run.due

Write. Scope: platform.write, admin. Contract: declared_dynamic. Hr Listening Run Due

platform.hr.listening.schedule.save

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Listening Schedule Save

platform.hr.listening.schedule.state

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Listening Schedule State

platform.hr.loop.approve

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Loop Approve

platform.hr.loop.correct

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Loop Correct

platform.hr.loop.evaluate

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Loop Evaluate

platform.hr.loop.overview

Read. Scope: platform.read, admin. Contract: declared_dynamic. Hr Loop Overview

platform.hr.loop.propose

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Loop Propose

platform.hr.loop.release

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Loop Release

platform.hr.loop.rollback

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Loop Rollback

platform.hr.loop.snapshot

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Loop Snapshot

platform.hr.marketplace.overview

Read. Scope: platform.read, admin. Contract: declared_dynamic. Hr Marketplace Overview

platform.hr.meeting.book

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Meeting Book

platform.hr.meeting.cancel

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Meeting Cancel

platform.hr.meeting.propose

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Meeting Propose

platform.hr.meeting.reschedule

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Meeting Reschedule

platform.hr.meetings.overview

Read. Scope: platform.read, admin. Contract: declared_dynamic. Hr Meetings Overview

platform.hr.meetings.reconcile

Write. Scope: platform.write, admin. Contract: declared_dynamic. Hr Meetings Reconcile

platform.hr.mentor.propose

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Mentor Propose

platform.hr.module.toggle

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Module Toggle

platform.hr.new.hire.checkin.state

Read. Scope: platform.read, admin. Contract: route_inferred. Hr New Hire Checkin State

platform.hr.offer.approve

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Offer Approve

platform.hr.offer.draft

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Offer Draft

platform.hr.offer.esign.confirm

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Offer Esign Confirm

platform.hr.offer.list

Read. Scope: platform.read, admin. Contract: declared_dynamic. Hr Offer List

platform.hr.offer.send

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Offer Send

platform.hr.offer.withdraw

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Offer Withdraw

platform.hr.onboarding.checkins.book

Read. Scope: platform.read, admin. Contract: route_inferred. Hr Onboarding Checkins Book

platform.hr.onboarding.draft.tasks

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Onboarding Draft Tasks

platform.hr.onboarding.overview

Read. Scope: platform.read, admin. Contract: declared_dynamic. Hr Onboarding Overview

platform.hr.onboarding.plan.buddy

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Onboarding Plan Buddy

platform.hr.onboarding.plan.close

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Onboarding Plan Close

platform.hr.onboarding.plan.create

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Onboarding Plan Create

platform.hr.onboarding.task.block

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Onboarding Task Block

platform.hr.onboarding.task.done

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Onboarding Task Done

platform.hr.onboarding.task.skip

Read. Scope: platform.read, admin. Contract: route_inferred. Hr Onboarding Task Skip

platform.hr.onboarding.task.unblock

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Onboarding Task Unblock

platform.hr.onboarding.task.verify

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Onboarding Task Verify

platform.hr.onboarding.template.save

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Onboarding Template Save

platform.hr.one.on.one.list

Read. Scope: platform.read, admin. Contract: declared_dynamic. Hr One On One List

platform.hr.one.on.one.record

Write. Scope: platform.write, admin. Contract: route_inferred. Hr One On One Record

platform.hr.opportunity.decide

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Opportunity Decide

platform.hr.opportunity.post

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Opportunity Post

platform.hr.org.chart

Read. Scope: platform.read, admin. Contract: declared_dynamic. Hr Org Chart

platform.hr.org.legal.entities

Read. Scope: platform.read, admin. Contract: declared_dynamic. Hr Org Legal Entities

platform.hr.org.legal.entity.create

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Org Legal Entity Create

platform.hr.org.location.create

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Org Location Create

platform.hr.org.locations

Read. Scope: platform.read, admin. Contract: declared_dynamic. Hr Org Locations

platform.hr.org.map.overview

Write. Scope: platform.write, admin. Contract: declared_dynamic. Hr Org Map Overview

platform.hr.org.map.remove

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Org Map Remove

platform.hr.org.map.save

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Org Map Save

platform.hr.org.tree

Read. Scope: platform.read, admin. Contract: declared_dynamic. Hr Org Tree

platform.hr.org.unit.create

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Org Unit Create

platform.hr.org.unit.move

Read. Scope: platform.read, admin. Contract: route_inferred. Hr Org Unit Move

platform.hr.override.record

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Override Record

platform.hr.overtime.decide

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Overtime Decide

platform.hr.path.enroll

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Path Enroll

platform.hr.path.save

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Path Save

platform.hr.pay.equity.overview

Write. Scope: platform.write, admin. Contract: declared_dynamic. Hr Pay Equity Overview

platform.hr.pay.gap.evaluate

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Pay Gap Evaluate

platform.hr.payroll.import

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Payroll Import

platform.hr.payroll.overview

Read. Scope: platform.read, admin. Contract: declared_dynamic. Hr Payroll Overview

platform.hr.payroll.provider.exceptions

Read. Scope: platform.read, admin. Contract: declared_dynamic. Hr Payroll Provider Exceptions

platform.hr.payroll.reconcile

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Payroll Reconcile

platform.hr.payslips.issue

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Payslips Issue

platform.hr.people.list

Read. Scope: platform.read, admin. Contract: declared_dynamic. Hr People List

platform.hr.perf.overview

Read. Scope: platform.read, admin. Contract: declared_dynamic. Hr Perf Overview

platform.hr.person.create

Write. Scope: platform.write, admin. Contract: route_inferred. Create an HR person Required fields: display_name.

platform.hr.person.get

Read. Scope: platform.read, admin. Contract: route_inferred. Hr Person Get

platform.hr.person.identifier.add

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Person Identifier Add

platform.hr.person.identifier.read

Read. Scope: platform.read, admin. Contract: route_inferred. Hr Person Identifier Read

platform.hr.person.identifiers

Read. Scope: platform.read, admin. Contract: route_inferred. Hr Person Identifiers

platform.hr.person.update

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Person Update

platform.hr.pilot.outcome.record

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Pilot Outcome Record

platform.hr.pipeline

Read. Scope: platform.read, admin. Contract: declared_dynamic. Hr Pipeline

platform.hr.policy.activate

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Policy Activate

platform.hr.policy.compile

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Policy Compile

platform.hr.pool.create

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Pool Create

platform.hr.pool.member.add

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Pool Member Add

platform.hr.pool.member.remove

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Pool Member Remove

platform.hr.pool.overview

Read. Scope: platform.read, admin. Contract: declared_dynamic. Hr Pool Overview

platform.hr.portal.address

Read. Scope: platform.read, admin. Contract: declared_dynamic. Hr Portal Address

platform.hr.portal.slug.save

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Portal Slug Save

platform.hr.position.assign

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Position Assign

platform.hr.position.create

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Position Create

platform.hr.position.overview

Read. Scope: platform.read, admin. Contract: declared_dynamic. Hr Position Overview

platform.hr.position.profile.set

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Position Profile Set

platform.hr.position.reports.to

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Position Reports To

platform.hr.position.state

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Position State

platform.hr.position.vacate

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Position Vacate

platform.hr.posting.close

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Posting Close

platform.hr.posting.create

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Posting Create

platform.hr.posting.list

Read. Scope: platform.read, admin. Contract: declared_dynamic. Hr Posting List

platform.hr.posting.publish

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Posting Publish

platform.hr.probation.open

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Probation Open

platform.hr.probation.review

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Probation Review

platform.hr.profile.address.format

Read. Scope: platform.read, admin. Contract: route_inferred. Hr Profile Address Format

platform.hr.profile.address.write

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Profile Address Write

platform.hr.profile.decide

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Profile Decide

platform.hr.profile.ownership.get

Read. Scope: platform.read, admin. Contract: declared_dynamic. Hr Profile Ownership Get

platform.hr.profile.ownership.set

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Profile Ownership Set

platform.hr.profile.pending

Read. Scope: platform.read, admin. Contract: declared_dynamic. Hr Profile Pending

platform.hr.profile.photo.clear

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Profile Photo Clear

platform.hr.profile.photo.set

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Profile Photo Set

platform.hr.profile.reveal

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Profile Reveal

platform.hr.profile.section.end

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Profile Section End

platform.hr.profile.section.write

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Profile Section Write

platform.hr.profile.sections

Read. Scope: platform.read, admin. Contract: route_inferred. Hr Profile Sections

platform.hr.pulse.close

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Pulse Close

platform.hr.pulse.issue

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Pulse Issue

platform.hr.pulse.list

Read. Scope: platform.read, admin. Contract: declared_dynamic. Hr Pulse List

platform.hr.pulse.open

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Pulse Open

platform.hr.pulse.results

Read. Scope: platform.read, admin. Contract: route_inferred. Hr Pulse Results

platform.hr.quality.overview

Read. Scope: platform.read, admin. Contract: declared_dynamic. Hr Quality Overview

platform.hr.quality.sample.draw

Write. Scope: platform.write, admin. Contract: declared_dynamic. Hr Quality Sample Draw

platform.hr.quality.samples

Read. Scope: platform.read, admin. Contract: declared_dynamic. Hr Quality Samples

platform.hr.quality.verdict

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Quality Verdict

platform.hr.queue.agent.add

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Queue Agent Add

platform.hr.queue.agent.remove

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Queue Agent Remove

platform.hr.queue.save

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Queue Save

platform.hr.readiness.report

Read. Scope: platform.read, admin. Contract: declared_dynamic. Hr Readiness Report

platform.hr.recognise

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Recognise

platform.hr.relations.overview

Read. Scope: platform.read, admin. Contract: declared_dynamic. Hr Relations Overview

platform.hr.release.gates

Read. Scope: platform.read, admin. Contract: declared_dynamic. Hr Release Gates

platform.hr.release.verify

Write. Scope: platform.write, admin. Contract: declared_dynamic. Hr Release Verify

platform.hr.req.create

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Req Create

platform.hr.req.list

Read. Scope: platform.read, admin. Contract: declared_dynamic. Hr Req List

platform.hr.req.reject

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Req Reject

platform.hr.req.transition

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Req Transition

platform.hr.review.cycle.open

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Review Cycle Open

platform.hr.review.include

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Review Include

platform.hr.review.respond

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Review Respond

platform.hr.review.template.save

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Review Template Save

platform.hr.rubric.approve

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Rubric Approve

platform.hr.rubric.create

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Rubric Create

platform.hr.rubric.list

Read. Scope: platform.read, admin. Contract: declared_dynamic. Hr Rubric List

platform.hr.run.replay

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Run Replay

platform.hr.run.start

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Run Start

platform.hr.run.step

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Run Step

platform.hr.run.takeover

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Run Takeover

platform.hr.scenario.run

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Scenario Run

platform.hr.schedule.save

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Schedule Save

platform.hr.screening.correct

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Screening Correct

platform.hr.screening.list

Read. Scope: platform.read, admin. Contract: declared_dynamic. Hr Screening List

platform.hr.screening.review

Read. Scope: platform.read, admin. Contract: route_inferred. Hr Screening Review

platform.hr.screening.run

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Screening Run

platform.hr.screening.verify

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Screening Verify

platform.hr.security.assurance.record

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Security Assurance Record

platform.hr.service.item.save

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Service Item Save

platform.hr.servicedesk.overview

Read. Scope: platform.read, admin. Contract: declared_dynamic. Hr Servicedesk Overview

platform.hr.shadow.compare

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Shadow Compare

platform.hr.shift.add

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Shift Add

platform.hr.shift.assign

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Shift Assign

platform.hr.signature.cancel

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Signature Cancel

platform.hr.signature.confirm

Read. Scope: platform.read, admin. Contract: route_inferred. Hr Signature Confirm

platform.hr.signature.list

Read. Scope: platform.read, admin. Contract: route_inferred. Hr Signature List

platform.hr.signature.request

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Signature Request

platform.hr.signin.design.get

Read. Scope: platform.read, admin. Contract: declared_dynamic. Hr Signin Design Get

platform.hr.signin.design.save

Write. Scope: platform.write, admin. Contract: declared_dynamic. Hr Signin Design Save

platform.hr.skill.challenge.resolve

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Skill Challenge Resolve

platform.hr.skills.infer.sweep

Read. Scope: platform.read, admin. Contract: route_inferred. Hr Skills Infer Sweep

platform.hr.skills.infer.text

Read. Scope: platform.read, admin. Contract: route_inferred. Hr Skills Infer Text

platform.hr.skills.overview

Read. Scope: platform.read, admin. Contract: declared_dynamic. Hr Skills Overview

platform.hr.skills.taxonomy.adopt

Write. Scope: platform.write, admin. Contract: declared_dynamic. Hr Skills Taxonomy Adopt

platform.hr.status

Write. Scope: platform.write, admin. Contract: declared_dynamic. Hr Status

platform.hr.succession.nominate

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Succession Nominate

platform.hr.succession.open

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Succession Open

platform.hr.succession.overview

Read. Scope: platform.read, admin. Contract: declared_dynamic. Hr Succession Overview

platform.hr.swap.approve

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Swap Approve

platform.hr.swap.decline

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Swap Decline

platform.hr.sync.conflict.resolve

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Sync Conflict Resolve

platform.hr.talent.overview

Read. Scope: platform.read, admin. Contract: declared_dynamic. Hr Talent Overview

platform.hr.thread.delete

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Thread Delete

platform.hr.thread.dm

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Thread Dm

platform.hr.thread.legal.hold

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Thread Legal Hold

platform.hr.thread.outreach

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Thread Outreach

platform.hr.thread.post

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Thread Post

platform.hr.thread.read

Read. Scope: platform.read, admin. Contract: route_inferred. Hr Thread Read

platform.hr.thread.retention

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Thread Retention

platform.hr.thread.search

Read. Scope: platform.read, admin. Contract: route_inferred. Hr Thread Search

platform.hr.threads.inbox

Read. Scope: platform.read, admin. Contract: declared_dynamic. Hr Threads Inbox

platform.hr.threads.retention.sweep

Write. Scope: platform.write, admin. Contract: declared_dynamic. Hr Threads Retention Sweep

platform.hr.time.decide

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Time Decide

platform.hr.time.overview

Read. Scope: platform.read, admin. Contract: declared_dynamic. Hr Time Overview

platform.hr.title.history

Read. Scope: platform.read, admin. Contract: route_inferred. Hr Title History

platform.hr.title.record

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Title Record

platform.hr.training.requirement.save

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Training Requirement Save

platform.hr.truth.register

Read. Scope: platform.read, admin. Contract: declared_dynamic. Hr Truth Register

platform.hr.turnover.run

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Turnover Run

platform.hr.verifier.verdict

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Verifier Verdict

platform.hr.wb.grant

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Wb Grant

platform.hr.wb.identity

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Wb Identity

platform.hr.wb.list

Read. Scope: platform.read, admin. Contract: declared_dynamic. Hr Wb List

platform.hr.wb.read

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Wb Read

platform.hr.wb.state

Write. Scope: platform.write, admin. Contract: route_inferred. Hr Wb State

platform.hr.workforce.dashboard

Read. Scope: platform.read, admin. Contract: declared_dynamic. Hr Workforce Dashboard

platform.inbound.activity.feed

Write. Scope: platform.write, admin. Contract: route_inferred. Inbound Activity Feed

platform.inbound.endpoints.delete

Write. Scope: platform.write, admin. Contract: route_inferred. Inbound Endpoints Delete

platform.inbound.endpoints.list

Write. Scope: admin. Contract: route_inferred. Inbound Endpoints List

platform.inbound.endpoints.save

Write. Scope: platform.write, admin. Contract: route_inferred. Inbound Endpoints Save

platform.inbound.endpoints.test

Write. Scope: platform.write, admin. Contract: route_inferred. Inbound Endpoints Test

platform.interrupted

Read. Scope: platform.read, admin. Contract: declared_dynamic. Interrupted

platform.ip.classify

Read. Scope: platform.read, admin. Contract: route_inferred. Ip Classify

platform.js.errors.clear.all

Write. Scope: platform.write, admin. Contract: declared_dynamic. Js Errors Clear All

platform.js.errors.list

Read. Scope: platform.read, admin. Contract: route_inferred. Js Errors List

platform.js.issue.assign

Write. Scope: platform.write, admin. Contract: route_inferred. Js Issue Assign

platform.js.issue.update

Write. Scope: platform.write, admin. Contract: route_inferred. Js Issue Update

platform.js.sourcemap.delete

Write. Scope: platform.write, admin. Contract: route_inferred. Js Sourcemap Delete

platform.js.sourcemap.upload

Write. Scope: platform.write, admin. Contract: route_inferred. Js Sourcemap Upload

platform.js.sourcemaps.list

Read. Scope: platform.read, admin. Contract: declared_dynamic. Js Sourcemaps List

platform.leads

Read. Scope: platform.read, admin. Contract: route_inferred. Leads

platform.license.delete

Write. Scope: admin. Contract: declared_dynamic. License Delete

platform.license.diagnostics

Read. Scope: platform.read, admin. Contract: declared_dynamic. License Diagnostics

platform.license.force.check

Read. Scope: platform.read, admin. Contract: declared_dynamic. License Force Check

platform.license.preflight

Read. Scope: platform.read, admin. Contract: declared_dynamic. License Preflight

platform.license.save

Write. Scope: admin. Contract: route_inferred. License Save

platform.license.status

Read. Scope: platform.read, admin. Contract: declared_dynamic. License Status

platform.license.verify.now

Write. Scope: platform.write, admin. Contract: declared_dynamic. License Verify Now

platform.lifecycle.evaluate

Read. Scope: platform.read, admin. Contract: route_inferred. Lifecycle Evaluate

platform.lifecycle.rule.delete

Write. Scope: platform.write, admin. Contract: route_inferred. Lifecycle Rule Delete

platform.lifecycle.rule.list

Read. Scope: platform.read, admin. Contract: route_inferred. Lifecycle Rule List

platform.lifecycle.rule.save

Write. Scope: platform.write, admin. Contract: route_inferred. Lifecycle Rule Save

platform.list.assignable.sites

Read. Scope: platform.read, admin. Contract: declared_dynamic. List Assignable Sites

platform.list.network.issues

Read. Scope: platform.read, admin. Contract: declared_dynamic. List Network Issues

platform.lookup.client.full

Read. Scope: platform.read, admin. Contract: route_inferred. Lookup Client Full

platform.mark.feedback.read

Write. Scope: platform.write, admin. Contract: route_inferred. Mark Feedback Read

platform.marketplace.local.install

Write. Scope: platform.write, admin. Contract: route_inferred. Marketplace Local Install

platform.marketplace.local.uninstall

Write. Scope: platform.write, admin. Contract: route_inferred. Marketplace Local Uninstall

platform.marketplace.session.get

Read. Scope: platform.read, admin. Contract: declared_dynamic. Marketplace Session Get

platform.marketplace.session.set

Write. Scope: platform.write, admin. Contract: route_inferred. Marketplace Session Set

platform.media.ready

Read. Scope: platform.read, admin. Contract: route_inferred. Media Ready

platform.message.contact.locale

Write. Scope: platform.write, admin. Contract: route_inferred. Message Contact Locale

platform.message.outbound.convert

Write. Scope: platform.write, admin. Contract: route_inferred. Message Outbound Convert

platform.message.translate

Write. Scope: platform.write, admin. Contract: route_inferred. Message Translate

platform.message.translation.delete

Write. Scope: platform.write, admin. Contract: route_inferred. Message Translation Delete

platform.message.translation.save

Write. Scope: platform.write, admin. Contract: route_inferred. Message Translation Save

platform.meta.channels.disconnect

Write. Scope: platform.write, admin. Contract: declared_dynamic. Meta Channels Disconnect

platform.meta.channels.switch.page

Write. Scope: platform.write, admin. Contract: route_inferred. Meta Channels Switch Page

platform.observe

Read. Scope: platform.read, admin. Contract: declared_dynamic. Observe

platform.onboarding.action

Read. Scope: platform.read, admin. Contract: declared_dynamic. Onboarding Action

platform.onboarding.readiness

Read. Scope: platform.read, admin. Contract: declared_dynamic. Onboarding Readiness

platform.open.network.issue

Read. Scope: platform.read, admin. Contract: declared_dynamic. Open Network Issue

platform.open.ticket

Read. Scope: platform.read, admin. Contract: route_inferred. Open Ticket

platform.operator.text.translate

Write. Scope: platform.write, admin. Contract: route_inferred. Operator Text Translate

platform.opsiq.backup.export

Read. Scope: platform.read, admin. Contract: declared_dynamic. Download a full backup in one request (retired)

platform.opsiq.backup.import

Write. Scope: platform.write, admin. Contract: route_inferred. Opsiq Backup Import

platform.opsiq.backup.import.start

Write. Scope: platform.write, admin. Contract: route_inferred. Opsiq Backup Import Start

platform.opsiq.backup.job.start

Write. Scope: platform.write, admin. Contract: route_inferred. Opsiq Backup Job Start

platform.opsiq.backup.job.status

Write. Scope: platform.write, admin. Contract: route_inferred. Opsiq Backup Job Status

platform.outreach.campaign.delete

Write. Scope: platform.write, admin. Contract: route_inferred. Outreach Campaign Delete

platform.outreach.campaign.list

Read. Scope: platform.read, admin. Contract: route_inferred. Outreach Campaign List

platform.outreach.campaign.save

Write. Scope: platform.write, admin. Contract: route_inferred. Outreach Campaign Save

platform.outreach.campaign.send

Write. Scope: platform.write, admin. Contract: route_inferred. Outreach Campaign Send

platform.outreach.compose.send

Write. Scope: platform.write, admin. Contract: route_inferred. Outreach Compose Send

platform.outreach.draft.delete

Write. Scope: platform.write, admin. Contract: route_inferred. Outreach Draft Delete

platform.outreach.draft.list

Read. Scope: platform.read, admin. Contract: route_inferred. Outreach Draft List

platform.outreach.draft.save

Write. Scope: platform.write, admin. Contract: route_inferred. Outreach Draft Save

platform.outreach.messages.delete

Write. Scope: platform.write, admin. Contract: route_inferred. Outreach Messages Delete

platform.outreach.replies.list

Read. Scope: platform.read, admin. Contract: route_inferred. Outreach Replies List

platform.outreach.reply.ai

Write. Scope: platform.write, admin. Contract: route_inferred. Outreach Reply Ai

platform.outreach.reply.mark

Write. Scope: platform.write, admin. Contract: route_inferred. Outreach Reply Mark

platform.outreach.reply.pref

Write. Scope: platform.write, admin. Contract: route_inferred. Outreach Reply Pref

platform.outreach.reply.send

Write. Scope: platform.write, admin. Contract: route_inferred. Outreach Reply Send

platform.outreach.reply.thread

Write. Scope: platform.write, admin. Contract: route_inferred. Outreach Reply Thread

platform.outreach.send.detail

Read. Scope: platform.read, admin. Contract: route_inferred. Outreach Send Detail

platform.outreach.send.retry

Write. Scope: platform.write, admin. Contract: route_inferred. Outreach Send Retry

platform.outreach.sends.list

Read. Scope: platform.read, admin. Contract: route_inferred. Outreach Sends List

platform.outreach.template.delete

Write. Scope: platform.write, admin. Contract: route_inferred. Outreach Template Delete

platform.outreach.template.list

Read. Scope: platform.read, admin. Contract: route_inferred. Outreach Template List

platform.outreach.template.preview

Read. Scope: platform.read, admin. Contract: route_inferred. Outreach Template Preview

platform.outreach.template.save

Write. Scope: platform.write, admin. Contract: route_inferred. Outreach Template Save

platform.overview

Read. Scope: platform.read, admin. Contract: declared_dynamic. Overview

platform.overview.hub.view

Read. Scope: platform.read, admin. Contract: route_inferred. Overview Hub View

platform.overview.intelligence.graph

Read. Scope: platform.read, admin. Contract: declared_dynamic. Overview Intelligence Graph

platform.pages

Read. Scope: platform.read, admin. Contract: route_inferred. Pages

platform.paths.data

Read. Scope: platform.read, admin. Contract: route_inferred. Paths Data

platform.pause

Read. Scope: platform.read, admin. Contract: declared_dynamic. Pause

platform.profile.change.password

Write. Scope: platform.write, admin. Contract: declared_dynamic. Profile Change Password

platform.profile.get

Read. Scope: platform.read, admin. Contract: route_inferred. Profile Get

platform.profile.reward.claim

Write. Scope: platform.write, admin. Contract: route_inferred. Profile Reward Claim

platform.profile.reward.claim.cancel

Write. Scope: platform.write, admin. Contract: route_inferred. Profile Reward Claim Cancel

platform.profile.save

Write. Scope: platform.write, admin. Contract: declared_dynamic. Profile Save

platform.profile.session.revoke

Write. Scope: platform.write, admin. Contract: route_inferred. Profile Session Revoke

platform.profile.sessions.list

Read. Scope: platform.read, admin. Contract: declared_dynamic. Profile Sessions List

platform.profile.sessions.revoke.others

Write. Scope: platform.write, admin. Contract: declared_dynamic. Profile Sessions Revoke Others

platform.profile.team.dispute.file

Write. Scope: platform.write, admin. Contract: route_inferred. Profile Team Dispute File

platform.purge

Write. Scope: admin. Contract: route_inferred. Purge

platform.purge.all

Write. Scope: admin. Contract: route_inferred. Purge All

platform.realtime

Read. Scope: platform.read, admin. Contract: route_inferred. Realtime

platform.realtime.test

Write. Scope: platform.write, admin. Contract: route_inferred. Realtime Test

platform.resume

Read. Scope: platform.read, admin. Contract: declared_dynamic. Resume

platform.retention.data

Read. Scope: platform.read, admin. Contract: route_inferred. Retention Data

platform.routes.list

Read. Scope: admin. Contract: source_inferred. List every registered OpsIQ operation

platform.routes.read

Read. Scope: admin. Contract: explicit. Execute a registered read operation Required fields: route.

platform.routes.write

Write. Scope: admin. Contract: explicit. Execute a registered write operation Required fields: route, idempotency_key. Retry-safe with idempotency_key.

platform.run.ai.analysis

Write. Scope: platform.write, admin. Contract: route_inferred. Run Ai Analysis

platform.save.admin.chat.history

Write. Scope: platform.write, admin. Contract: route_inferred. Save Admin Chat History

platform.save.pwa.chat.prefs

Write. Scope: platform.write, admin. Contract: declared_dynamic. Save Pwa Chat Prefs

platform.save.survey.config

Write. Scope: platform.write, admin. Contract: route_inferred. Save Survey Config

platform.save.widget.advanced

Write. Scope: platform.write, admin. Contract: declared_dynamic. Save Widget Advanced

platform.scim.token.issue

Read. Scope: platform.read, admin. Contract: route_inferred. Scim Token Issue

platform.scim.token.list

Read. Scope: platform.read, admin. Contract: declared_dynamic. Scim Token List

platform.scim.token.revoke

Write. Scope: platform.write, admin. Contract: route_inferred. Scim Token Revoke

platform.segment.delete

Write. Scope: platform.write, admin. Contract: route_inferred. Segment Delete

platform.segment.list

Read. Scope: platform.read, admin. Contract: route_inferred. Segment List

platform.segment.members

Read. Scope: platform.read, admin. Contract: route_inferred. Segment Members

platform.segment.preview

Read. Scope: platform.read, admin. Contract: route_inferred. Segment Preview

platform.segment.save

Write. Scope: platform.write, admin. Contract: route_inferred. Segment Save

platform.segment.suggestion.accept

Write. Scope: platform.write, admin. Contract: route_inferred. Segment Suggestion Accept

platform.segment.suggestion.dismiss

Write. Scope: platform.write, admin. Contract: route_inferred. Segment Suggestion Dismiss

platform.segment.suggestion.list

Read. Scope: platform.read, admin. Contract: route_inferred. Segment Suggestion List

platform.send.campaign

Write. Scope: platform.write, admin. Contract: route_inferred. Send Campaign

platform.send.client.email

Write. Scope: platform.write, admin. Contract: route_inferred. Send Client Email

platform.send.ticket.reply

Write. Scope: platform.write, admin. Contract: route_inferred. Send Ticket Reply

platform.service.studio.get

Read. Scope: platform.read, admin. Contract: declared_dynamic. Service Studio Get

platform.set.active.site

Write. Scope: platform.write, admin. Contract: route_inferred. Set Active Site

platform.silence

Read. Scope: platform.read, admin. Contract: declared_dynamic. Silence

platform.site.set.group

Write. Scope: platform.write, admin. Contract: route_inferred. Site Set Group

platform.sites.add

Write. Scope: platform.write, admin. Contract: route_inferred. Sites Add

platform.sites.edit

Write. Scope: platform.write, admin. Contract: route_inferred. Sites Edit

platform.sites.list

Write. Scope: platform.write, admin. Contract: route_inferred. Sites List

platform.sites.picker

Write. Scope: platform.write, admin. Contract: route_inferred. Sites Picker

platform.sites.regenerate.secret

Write. Scope: platform.write, admin. Contract: route_inferred. Sites Regenerate Secret

platform.sites.remove

Write. Scope: platform.write, admin. Contract: route_inferred. Sites Remove

platform.stats

Read. Scope: platform.read, admin. Contract: declared_dynamic. Stats

platform.stepup.verify

Write. Scope: platform.write, admin. Contract: declared_dynamic. Stepup Verify

platform.submit.agent.ai.feedback

Write. Scope: platform.write, admin. Contract: route_inferred. Submit Agent Ai Feedback

platform.submit.triage.feedback

Write. Scope: platform.write, admin. Contract: route_inferred. Submit Triage Feedback

platform.takeover

Read. Scope: platform.read, admin. Contract: declared_dynamic. Takeover

platform.terminate

Read. Scope: platform.read, admin. Contract: route_inferred. Terminate

platform.test.geoip

Read. Scope: platform.read, admin. Contract: route_inferred. Test Geoip

platform.top.pages

Read. Scope: platform.read, admin. Contract: route_inferred. Top Pages

platform.train.client.chat.knowledge

Write. Scope: platform.write, admin. Contract: route_inferred. Train Client Chat Knowledge

platform.triggers

Read. Scope: platform.read, admin. Contract: declared_dynamic. Triggers

platform.trust.evidence.report

Write. Scope: platform.write, admin. Contract: declared_dynamic. Trust Evidence Report

platform.turn.pool.add

Write. Scope: platform.write, admin. Contract: route_inferred. Turn Pool Add

platform.turn.pool.list

Read. Scope: platform.read, admin. Contract: declared_dynamic. Turn Pool List

platform.turn.pool.pick.test

Write. Scope: platform.write, admin. Contract: route_inferred. Turn Pool Pick Test

platform.turn.pool.remove

Write. Scope: platform.write, admin. Contract: route_inferred. Turn Pool Remove

platform.turn.pool.update

Write. Scope: platform.write, admin. Contract: route_inferred. Turn Pool Update

platform.update.lead.status

Write. Scope: platform.write, admin. Contract: route_inferred. Update Lead Status

platform.wa.embedded.signup.exchange

Write. Scope: platform.write, admin. Contract: route_inferred. Wa Embedded Signup Exchange

platform.warehouse.export.run

Read. Scope: platform.read, admin. Contract: declared_dynamic. Warehouse Export Run

platform.warehouse.exports.list

Read. Scope: platform.read, admin. Contract: declared_dynamic. Warehouse Exports List

platform.webhook.deliveries.list

Read. Scope: platform.read, admin. Contract: route_inferred. Webhook Deliveries List

platform.webhook.endpoint.delete

Write. Scope: platform.write, admin. Contract: route_inferred. Webhook Endpoint Delete

platform.webhook.endpoint.list

Read. Scope: platform.read, admin. Contract: declared_dynamic. Webhook Endpoint List

platform.webhook.endpoint.save

Write. Scope: platform.write, admin. Contract: route_inferred. Webhook Endpoint Save

platform.webhook.endpoint.test

Write. Scope: platform.write, admin. Contract: route_inferred. Webhook Endpoint Test

platform.webhook.redeliver

Write. Scope: platform.write, admin. Contract: route_inferred. Webhook Redeliver

platform.weekly.digest.view

Read. Scope: platform.read, admin. Contract: route_inferred. Weekly Digest View

platform.whmcs.op.dispatch

Read. Scope: platform.read, admin. Contract: declared_dynamic. Whmcs Op Dispatch

platform.workspace.custom.domain.remove

Write. Scope: platform.write, admin. Contract: route_inferred. Workspace Custom Domain Remove

platform.workspace.custom.domain.set

Write. Scope: platform.write, admin. Contract: route_inferred. Workspace Custom Domain Set

platform.writing.json.knowledge.clear

Write. Scope: platform.write, admin. Contract: declared_dynamic. Writing Json Knowledge Clear

platform.writing.json.knowledge.count

Read. Scope: platform.read, admin. Contract: declared_dynamic. Writing Json Knowledge Count

platform.writing.json.knowledge.import

Write. Scope: platform.write, admin. Contract: route_inferred. Writing Json Knowledge Import

portal_studio (169)

portal_studio.accessibility.evidence.save

Write. Scope: portal_studio.write, admin. Contract: route_inferred. Portal Studio Accessibility Evidence Save

portal_studio.add

Write. Scope: portal_studio.write, admin. Contract: route_inferred. Portal Domain Add

portal_studio.allocate

Write. Scope: portal_studio.write, admin. Contract: route_inferred. Portal Subdomain Allocate

portal_studio.analytics.breakdown

Read. Scope: portal_studio.read, admin. Contract: declared_dynamic. Portal Studio Analytics Breakdown

portal_studio.analytics.load

Read. Scope: portal_studio.read, admin. Contract: declared_dynamic. Portal Studio Analytics Load

portal_studio.apply.kit

Write. Scope: portal_studio.write, admin. Contract: route_inferred. Portal Studio Apply Kit

portal_studio.apply.theme

Write. Scope: portal_studio.write, admin. Contract: route_inferred. Portal Design Apply Theme

portal_studio.approval

Read. Scope: portal_studio.read, admin. Contract: route_inferred. Portal Design Approval

portal_studio.approve

Write. Scope: portal_studio.write, admin. Contract: declared_dynamic. Portal Studio Approve

portal_studio.ask

Write. Scope: portal_studio.write, admin. Contract: route_inferred. Portal Studio Ask

portal_studio.audience.delete

Write. Scope: portal_studio.write, admin. Contract: declared_dynamic. Portal Studio Audience Delete

portal_studio.audience.explain

Read. Scope: portal_studio.read, admin. Contract: declared_dynamic. Portal Studio Audience Explain

portal_studio.audience.list

Read. Scope: portal_studio.read, admin. Contract: declared_dynamic. Portal Studio Audience List

portal_studio.audience.preview

Read. Scope: portal_studio.read, admin. Contract: declared_dynamic. Portal Studio Audience Preview

portal_studio.audience.save

Write. Scope: portal_studio.write, admin. Contract: declared_dynamic. Portal Studio Audience Save

portal_studio.brand.generate

Write. Scope: portal_studio.write, admin. Contract: route_inferred. Portal Design Brand Generate

portal_studio.brand.import

Write. Scope: portal_studio.write, admin. Contract: route_inferred. Portal Design Brand Import

portal_studio.cancel.schedule

Write. Scope: portal_studio.write, admin. Contract: declared_dynamic. Portal Design Cancel Schedule

portal_studio.certify

Read. Scope: portal_studio.read, admin. Contract: declared_dynamic. Portal Studio Certify

portal_studio.check

Read. Scope: portal_studio.read, admin. Contract: route_inferred. Portal Host Check

portal_studio.check.route.portal.subdomain.check

Read. Scope: portal_studio.read, admin. Contract: route_inferred. Portal Subdomain Check

portal_studio.comment.add

Write. Scope: portal_studio.write, admin. Contract: declared_dynamic. Portal Studio Comment Add

portal_studio.comment.resolve

Write. Scope: portal_studio.write, admin. Contract: declared_dynamic. Portal Studio Comment Resolve

portal_studio.component.package.inspect

Read. Scope: portal_studio.read, admin. Contract: declared_dynamic. Portal Studio Component Package Inspect

portal_studio.component.package.install

Write. Scope: portal_studio.write, admin. Contract: declared_dynamic. Portal Studio Component Package Install

portal_studio.component.validate

Read. Scope: portal_studio.read, admin. Contract: declared_dynamic. Portal Studio Component Validate

portal_studio.config

Read. Scope: portal_studio.read, admin. Contract: declared_dynamic. Portal Handoff Config

portal_studio.data.resolve

Read. Scope: portal_studio.read, admin. Contract: declared_dynamic. Portal Studio Data Resolve

portal_studio.delete.theme

Write. Scope: portal_studio.write, admin. Contract: route_inferred. Portal Design Delete Theme

portal_studio.developer.contract

Read. Scope: portal_studio.read, admin. Contract: declared_dynamic. Portal Studio Developer Contract

portal_studio.discovery.preview

Read. Scope: portal_studio.read, admin. Contract: route_inferred. Portal Studio Discovery Preview

portal_studio.discovery.save

Write. Scope: portal_studio.write, admin. Contract: route_inferred. Portal Studio Discovery Save

portal_studio.document.load

Read. Scope: portal_studio.read, admin. Contract: declared_dynamic. Portal Studio Load

portal_studio.document.save

Write. Scope: portal_studio.write, admin. Contract: route_inferred. Portal Studio Save

portal_studio.experiment.control

Write. Scope: portal_studio.write, admin. Contract: declared_dynamic. Portal Studio Experiment Control

portal_studio.experiment.results

Read. Scope: portal_studio.read, admin. Contract: declared_dynamic. Portal Studio Experiment Results

portal_studio.experiment.save

Write. Scope: portal_studio.write, admin. Contract: declared_dynamic. Portal Studio Experiment Save

portal_studio.experiments.list

Read. Scope: portal_studio.read, admin. Contract: declared_dynamic. Portal Studio Experiments List

portal_studio.form.archive

Write. Scope: portal_studio.write, admin. Contract: declared_dynamic. Portal Studio Form Archive

portal_studio.form.catalog

Read. Scope: portal_studio.read, admin. Contract: declared_dynamic. Portal Studio Form Catalog

portal_studio.form.create

Write. Scope: portal_studio.write, admin. Contract: route_inferred. Portal Studio Form Create

portal_studio.form.delete

Write. Scope: portal_studio.write, admin. Contract: route_inferred. Portal Studio Form Delete

portal_studio.form.duplicate

Write. Scope: portal_studio.write, admin. Contract: route_inferred. Portal Studio Form Duplicate

portal_studio.form.evaluate

Read. Scope: portal_studio.read, admin. Contract: route_inferred. Portal Studio Form Evaluate

portal_studio.form.group.apply

Write. Scope: portal_studio.write, admin. Contract: route_inferred. Portal Studio Form Group Apply

portal_studio.form.group.delete

Write. Scope: portal_studio.write, admin. Contract: route_inferred. Portal Studio Form Group Delete

portal_studio.form.group.save

Write. Scope: portal_studio.write, admin. Contract: route_inferred. Portal Studio Form Group Save

portal_studio.form.publish

Write. Scope: portal_studio.write, admin. Contract: route_inferred. Portal Studio Form Publish

portal_studio.form.restore

Write. Scope: portal_studio.write, admin. Contract: declared_dynamic. Portal Studio Form Restore

portal_studio.form.save

Write. Scope: portal_studio.write, admin. Contract: route_inferred. Portal Studio Form Save

portal_studio.form.template

Write. Scope: portal_studio.write, admin. Contract: route_inferred. Portal Studio Form Template

portal_studio.form.test

Read. Scope: portal_studio.read, admin. Contract: route_inferred. Portal Studio Form Test

portal_studio.form.version.restore

Write. Scope: portal_studio.write, admin. Contract: route_inferred. Portal Studio Form Version Restore

portal_studio.history

Read. Scope: portal_studio.read, admin. Contract: route_inferred. Portal Design History

portal_studio.identity.discover

Read. Scope: portal_studio.read, admin. Contract: declared_dynamic. Portal Studio Identity Discover

portal_studio.identity.load

Read. Scope: portal_studio.read, admin. Contract: declared_dynamic. Portal Studio Identity Load

portal_studio.identity.save

Write. Scope: portal_studio.write, admin. Contract: declared_dynamic. Portal Studio Identity Save

portal_studio.integration.activate

Write. Scope: portal_studio.write, admin. Contract: route_inferred. Portal Studio Integration Activate

portal_studio.integration.install

Write. Scope: portal_studio.write, admin. Contract: route_inferred. Portal Studio Integration Install

portal_studio.integration.kill.switch

Write. Scope: portal_studio.write, admin. Contract: route_inferred. Portal Studio Integration Kill Switch

portal_studio.integration.list

Read. Scope: portal_studio.read, admin. Contract: declared_dynamic. Portal Studio Integration List

portal_studio.integration.policy

Read. Scope: portal_studio.read, admin. Contract: declared_dynamic. Portal Studio Integration Policy

portal_studio.integration.policy.save

Write. Scope: portal_studio.write, admin. Contract: declared_dynamic. Portal Studio Integration Policy Save

portal_studio.integration.preflight

Write. Scope: portal_studio.write, admin. Contract: route_inferred. Portal Studio Integration Preflight

portal_studio.integration.revise

Write. Scope: portal_studio.write, admin. Contract: route_inferred. Portal Studio Integration Revise

portal_studio.integration.rollback

Write. Scope: portal_studio.write, admin. Contract: route_inferred. Portal Studio Integration Rollback

portal_studio.integration.transition

Write. Scope: portal_studio.write, admin. Contract: route_inferred. Portal Studio Integration Transition

portal_studio.journey.archive

Write. Scope: portal_studio.write, admin. Contract: route_inferred. Portal Studio Journey Archive

portal_studio.journey.catalog

Read. Scope: portal_studio.read, admin. Contract: declared_dynamic. Portal Studio Journey Catalog

portal_studio.journey.delete

Write. Scope: portal_studio.write, admin. Contract: route_inferred. Portal Studio Journey Delete

portal_studio.journey.duplicate

Write. Scope: portal_studio.write, admin. Contract: route_inferred. Portal Studio Journey Duplicate

portal_studio.journey.evaluate

Read. Scope: portal_studio.read, admin. Contract: route_inferred. Portal Studio Journey Evaluate

portal_studio.journey.instantiate

Write. Scope: portal_studio.write, admin. Contract: route_inferred. Portal Studio Journey Instantiate

portal_studio.journey.restore

Write. Scope: portal_studio.write, admin. Contract: route_inferred. Portal Studio Journey Restore

portal_studio.journey.save

Write. Scope: portal_studio.write, admin. Contract: route_inferred. Portal Studio Journey Save

portal_studio.kb.category.delete

Write. Scope: portal_studio.write, admin. Contract: declared_dynamic. Portal Studio Kb Category Delete

portal_studio.kb.category.reorder

Write. Scope: portal_studio.write, admin. Contract: declared_dynamic. Portal Studio Kb Category Reorder

portal_studio.kb.category.save

Write. Scope: portal_studio.write, admin. Contract: route_inferred. Portal Studio Kb Category Save

portal_studio.kb.governance

Read. Scope: portal_studio.read, admin. Contract: declared_dynamic. Portal Studio Kb Governance

portal_studio.kb.governance.save

Write. Scope: portal_studio.write, admin. Contract: route_inferred. Portal Studio Kb Governance Save

portal_studio.kb.languages

Read. Scope: portal_studio.read, admin. Contract: declared_dynamic. Portal Studio Kb Languages

portal_studio.kb.languages.save

Write. Scope: portal_studio.write, admin. Contract: declared_dynamic. Portal Studio Kb Languages Save

portal_studio.kb.parity

Read. Scope: portal_studio.read, admin. Contract: declared_dynamic. Portal Studio Kb Parity

portal_studio.kb.search.tuning

Read. Scope: portal_studio.read, admin. Contract: declared_dynamic. Portal Studio Kb Search Tuning

portal_studio.kb.search.tuning.save

Write. Scope: portal_studio.write, admin. Contract: declared_dynamic. Portal Studio Kb Search Tuning Save

portal_studio.kb.tree

Read. Scope: portal_studio.read, admin. Contract: declared_dynamic. Portal Studio Kb Tree

portal_studio.knowledge.summary

Read. Scope: portal_studio.read, admin. Contract: declared_dynamic. Portal Studio Knowledge Summary

portal_studio.list

Write. Scope: portal_studio.write, admin. Contract: route_inferred. Portal Domain List

portal_studio.load

Read. Scope: portal_studio.read, admin. Contract: route_inferred. Portal Analytics Load

portal_studio.load.route.portal.design.load

Write. Scope: portal_studio.write, admin. Contract: declared_dynamic. Portal Design Load

portal_studio.load.route.portal.form.load

Read. Scope: portal_studio.read, admin. Contract: declared_dynamic. Portal Form Load

portal_studio.lock

Write. Scope: portal_studio.write, admin. Contract: declared_dynamic. Portal Studio Lock

portal_studio.migration.apply

Write. Scope: portal_studio.write, admin. Contract: declared_dynamic. Portal Studio Migration Apply

portal_studio.migration.approve

Write. Scope: portal_studio.write, admin. Contract: declared_dynamic. Portal Studio Migration Approve

portal_studio.migration.list

Read. Scope: portal_studio.read, admin. Contract: declared_dynamic. Portal Studio Migration List

portal_studio.migration.reconcile

Write. Scope: portal_studio.write, admin. Contract: declared_dynamic. Portal Studio Migration Reconcile

portal_studio.migration.report

Read. Scope: portal_studio.read, admin. Contract: declared_dynamic. Portal Studio Migration Report

portal_studio.migration.rollback

Write. Scope: portal_studio.write, admin. Contract: declared_dynamic. Portal Studio Migration Rollback

portal_studio.migration.rollout

Write. Scope: portal_studio.write, admin. Contract: declared_dynamic. Portal Studio Migration Rollout

portal_studio.migration.start

Write. Scope: portal_studio.write, admin. Contract: declared_dynamic. Portal Studio Migration Start

portal_studio.node.add

Write. Scope: portal_studio.write, admin. Contract: route_inferred. Portal Studio Node Add

portal_studio.node.delete

Write. Scope: portal_studio.write, admin. Contract: route_inferred. Portal Studio Node Delete

portal_studio.node.duplicate

Write. Scope: portal_studio.write, admin. Contract: route_inferred. Portal Studio Node Duplicate

portal_studio.node.move

Write. Scope: portal_studio.write, admin. Contract: route_inferred. Portal Studio Node Move

portal_studio.node.update

Write. Scope: portal_studio.write, admin. Contract: route_inferred. Portal Studio Node Update

portal_studio.operations.control

Write. Scope: portal_studio.write, admin. Contract: declared_dynamic. Portal Studio Operations Control

portal_studio.operations.feed

Read. Scope: portal_studio.read, admin. Contract: declared_dynamic. Portal Studio Operations Feed

portal_studio.operations.record

Write. Scope: portal_studio.write, admin. Contract: declared_dynamic. Portal Studio Operations Record

portal_studio.operations.summary

Read. Scope: portal_studio.read, admin. Contract: declared_dynamic. Portal Studio Operations Summary

portal_studio.org.context

Read. Scope: portal_studio.read, admin. Contract: declared_dynamic. Portal Studio Org Context

portal_studio.org.member.save

Write. Scope: portal_studio.write, admin. Contract: declared_dynamic. Portal Studio Org Member Save

portal_studio.org.members

Read. Scope: portal_studio.read, admin. Contract: declared_dynamic. Portal Studio Org Members

portal_studio.org.requests

Read. Scope: portal_studio.read, admin. Contract: declared_dynamic. Portal Studio Org Requests

portal_studio.page.archive

Write. Scope: portal_studio.write, admin. Contract: route_inferred. Portal Studio Page Archive

portal_studio.page.create

Write. Scope: portal_studio.write, admin. Contract: route_inferred. Portal Studio Page Create

portal_studio.page.delete

Write. Scope: portal_studio.write, admin. Contract: route_inferred. Portal Studio Page Delete

portal_studio.page.duplicate

Write. Scope: portal_studio.write, admin. Contract: route_inferred. Portal Studio Page Duplicate

portal_studio.page.restore

Write. Scope: portal_studio.write, admin. Contract: route_inferred. Portal Studio Page Restore

portal_studio.page.update

Write. Scope: portal_studio.write, admin. Contract: route_inferred. Portal Studio Page Update

portal_studio.parity.accept

Write. Scope: portal_studio.write, admin. Contract: declared_dynamic. Portal Studio Parity Accept

portal_studio.parity.capture

Write. Scope: portal_studio.write, admin. Contract: declared_dynamic. Portal Studio Parity Capture

portal_studio.parity.compare

Write. Scope: portal_studio.write, admin. Contract: declared_dynamic. Portal Studio Parity Compare

portal_studio.parity.create

Write. Scope: portal_studio.write, admin. Contract: declared_dynamic. Portal Studio Parity Create

portal_studio.parity.list

Read. Scope: portal_studio.read, admin. Contract: declared_dynamic. Portal Studio Parity List

portal_studio.personalization.delete

Write. Scope: portal_studio.write, admin. Contract: declared_dynamic. Portal Studio Personalization Delete

portal_studio.personalization.list

Read. Scope: portal_studio.read, admin. Contract: declared_dynamic. Portal Studio Personalization List

portal_studio.personalization.save

Write. Scope: portal_studio.write, admin. Contract: declared_dynamic. Portal Studio Personalization Save

portal_studio.presence

Read. Scope: portal_studio.read, admin. Contract: declared_dynamic. Portal Studio Presence

portal_studio.preview

Write. Scope: portal_studio.write, admin. Contract: route_inferred. Portal Design Preview

portal_studio.preview.catalog

Read. Scope: portal_studio.read, admin. Contract: declared_dynamic. Portal Studio Preview Catalog

portal_studio.publish

Write. Scope: portal_studio.write, admin. Contract: route_inferred. Portal Design Publish

portal_studio.quality

Read. Scope: portal_studio.read, admin. Contract: declared_dynamic. Portal Studio Quality

portal_studio.redirect.delete

Write. Scope: portal_studio.write, admin. Contract: route_inferred. Portal Studio Redirect Delete

portal_studio.redirect.save

Write. Scope: portal_studio.write, admin. Contract: route_inferred. Portal Studio Redirect Save

portal_studio.release.diff

Write. Scope: portal_studio.write, admin. Contract: route_inferred. Portal Design Release Diff

portal_studio.release.evidence

Read. Scope: portal_studio.read, admin. Contract: route_inferred. Portal Design Release Evidence

portal_studio.release.history

Read. Scope: portal_studio.read, admin. Contract: declared_dynamic. Portal Studio Release History

portal_studio.release.publish

Write. Scope: portal_studio.write, admin. Contract: declared_dynamic. Portal Studio Publish

portal_studio.release.rollback

Write. Scope: portal_studio.write, admin. Contract: declared_dynamic. Portal Studio Rollback

portal_studio.release.schedule

Write. Scope: portal_studio.write, admin. Contract: declared_dynamic. Portal Studio Schedule

portal_studio.remove

Write. Scope: portal_studio.write, admin. Contract: route_inferred. Portal Domain Remove

portal_studio.request.changes

Write. Scope: portal_studio.write, admin. Contract: declared_dynamic. Portal Studio Request Changes

portal_studio.restore.field

Write. Scope: portal_studio.write, admin. Contract: route_inferred. Portal Design Restore Field

portal_studio.restore.published

Write. Scope: portal_studio.write, admin. Contract: declared_dynamic. Portal Studio Restore Published

portal_studio.revert

Read. Scope: portal_studio.read, admin. Contract: declared_dynamic. Portal Design Revert

portal_studio.review

Write. Scope: portal_studio.write, admin. Contract: declared_dynamic. Portal Studio Review

portal_studio.review.link

Write. Scope: portal_studio.write, admin. Contract: route_inferred. Portal Design Review Link

portal_studio.rollback

Write. Scope: portal_studio.write, admin. Contract: route_inferred. Portal Design Rollback

portal_studio.save

Write. Scope: portal_studio.write, admin. Contract: route_inferred. Portal Design Save

portal_studio.save.route.portal.form.save

Write. Scope: portal_studio.write, admin. Contract: route_inferred. Portal Form Save

portal_studio.save.theme

Write. Scope: portal_studio.write, admin. Contract: route_inferred. Portal Design Save Theme

portal_studio.saved.section.delete

Write. Scope: portal_studio.write, admin. Contract: route_inferred. Portal Studio Saved Section Delete

portal_studio.saved.section.instantiate

Write. Scope: portal_studio.write, admin. Contract: route_inferred. Portal Studio Saved Section Instantiate

portal_studio.saved.section.save

Write. Scope: portal_studio.write, admin. Contract: route_inferred. Portal Studio Saved Section Save

portal_studio.schedule

Read. Scope: portal_studio.read, admin. Contract: route_inferred. Portal Design Schedule

portal_studio.schedule.cancel

Write. Scope: portal_studio.write, admin. Contract: declared_dynamic. Portal Studio Schedule Cancel

portal_studio.scim.config

Write. Scope: portal_studio.write, admin. Contract: declared_dynamic. Portal Studio Scim Config

portal_studio.service.archive

Write. Scope: portal_studio.write, admin. Contract: route_inferred. Portal Studio Service Archive

portal_studio.service.catalog

Read. Scope: portal_studio.read, admin. Contract: declared_dynamic. Portal Studio Service Catalog

portal_studio.service.duplicate

Write. Scope: portal_studio.write, admin. Contract: route_inferred. Portal Studio Service Duplicate

portal_studio.service.reorder

Write. Scope: portal_studio.write, admin. Contract: route_inferred. Portal Studio Service Reorder

portal_studio.service.restore

Write. Scope: portal_studio.write, admin. Contract: route_inferred. Portal Studio Service Restore

portal_studio.service.save

Write. Scope: portal_studio.write, admin. Contract: route_inferred. Portal Studio Service Save

portal_studio.service.template

Write. Scope: portal_studio.write, admin. Contract: route_inferred. Portal Studio Service Template

portal_studio.sign.in.flow.save

Write. Scope: portal_studio.write, admin. Contract: declared_dynamic. Portal Studio Sign In Flow Save

portal_studio.signin.methods

Write. Scope: portal_studio.write, admin. Contract: route_inferred. Portal Design Signin Methods

portal_studio.test.link

Write. Scope: portal_studio.write, admin. Contract: route_inferred. Portal Handoff Test Link

portal_studio.unlock

Write. Scope: portal_studio.write, admin. Contract: declared_dynamic. Portal Studio Unlock

portal_studio.upload

Write. Scope: portal_studio.write, admin. Contract: route_inferred. Portal Image Upload

sales (14)

sales.ai.insight

Write. Scope: sales.write, admin. Contract: route_inferred. Sales Ai Insight

sales.analyze

Write. Scope: sales.write, analytics.write, admin. Contract: route_inferred. Analyze sales with AI

sales.chart

Write. Scope: sales.write, admin. Contract: route_inferred. Sales Chart

sales.compare

Read. Scope: sales.read, analytics.read, admin. Contract: route_inferred. Compare sales periods

sales.compare.route.sales.compare

Read. Scope: sales.read, admin. Contract: route_inferred. Sales Compare

sales.goal.delete

Write. Scope: sales.write, admin. Contract: route_inferred. Conversion Goal Delete

sales.goal.list

Read. Scope: sales.read, admin. Contract: route_inferred. Conversion Goal List

sales.goal.save

Write. Scope: sales.write, admin. Contract: route_inferred. Conversion Goal Save

sales.list

Read. Scope: sales.read, analytics.read, admin. Contract: route_inferred. List sales and conversions

sales.list.route.conversion.list

Read. Scope: sales.read, admin. Contract: route_inferred. Conversion List

sales.record

Write. Scope: sales.write, admin. Contract: route_inferred. Conversion Record

sales.stats

Read. Scope: sales.read, analytics.read, admin. Contract: declared_dynamic. Read sales statistics

sales.stats.route.sales.stats

Read. Scope: sales.read, admin. Contract: declared_dynamic. Sales Stats

sales.table

Read. Scope: sales.read, admin. Contract: route_inferred. Sales Table

Usalama wa usalama (21)

security.ai.analyze

Write. Scope: security.write, admin. Contract: route_inferred. Security Ai Analyze

security.ai.ask

Write. Scope: security.write, admin. Contract: route_inferred. Security Ai Ask

security.ai.briefs

Read. Scope: security.read, admin. Contract: declared_dynamic. Security Ai Briefs

security.ai.chain.explain

Read. Scope: security.read, admin. Contract: route_inferred. Security Ai Chain Explain

security.ai.incident.action

Write. Scope: security.write, admin. Contract: route_inferred. Security Ai Incident Action

security.ai.incidents

Read. Scope: security.read, admin. Contract: route_inferred. Security Ai Incidents

security.ai.js.triage

Read. Scope: security.read, admin. Contract: route_inferred. Security Ai Js Triage

security.ai.policies

Read. Scope: security.read, admin. Contract: declared_dynamic. Security Ai Policies

security.ai.policy.action

Write. Scope: security.write, admin. Contract: route_inferred. Security Ai Policy Action

security.ai.verdicts

Read. Scope: security.read, admin. Contract: route_inferred. Security Ai Verdicts

security.blocklist.add

Write. Scope: security.write, admin. Contract: source_inferred. Add a spam rule (email, domain or IP) to the ticket blocklist Required fields: kind, value. Retry-safe with idempotency_key.

security.blocklist.list

Read. Scope: security.read, admin. Contract: explicit. List the current ticket spam rules

security.chain.reanchor

Write. Scope: security.write, admin. Contract: declared_dynamic. Security Chain Reanchor

security.check

Read. Scope: security.read, admin. Contract: source_inferred. Check an IP or email against the platform blocklists and Security AI verdicts

security.ip

Write. Scope: security.write, admin. Contract: route_inferred. Block Ip

security.ip.route.unblock.ip

Write. Scope: security.write, admin. Contract: route_inferred. Unblock Ip

security.list

Write. Scope: security.write, admin. Contract: route_inferred. Access Log List

security.overview.chains

Read. Scope: security.read, admin. Contract: declared_dynamic. Security Overview Chains

security.overview.data

Read. Scope: security.read, admin. Contract: declared_dynamic. Security Overview Data

security.report

Write. Scope: security.write, admin. Contract: source_inferred. Report abuse a connector observed (spam, login attack, scan, fraud) Retry-safe with idempotency_key.

security.visitor

Write. Scope: security.write, admin. Contract: route_inferred. Block Visitor

sessions (5)

sessions.detail

Read. Scope: sessions.read, admin. Contract: route_inferred. Session Detail

sessions.get

Read. Scope: sessions.read, analytics.read, admin. Contract: route_inferred. Get a session journey Required fields: session_id.

sessions.list

Read. Scope: sessions.read, analytics.read, admin. Contract: route_inferred. List sessions

sessions.merged

Read. Scope: sessions.read, admin. Contract: route_inferred. Sessions Merged

sessions.table

Read. Scope: sessions.read, admin. Contract: route_inferred. Sessions Table

settings (11)

settings.ai.eval.watchtower.config

Write. Scope: settings.write, admin. Contract: declared_dynamic. Ai Eval Watchtower Config

settings.get.client.chat.settings

Read. Scope: settings.read, admin. Contract: route_inferred. Get Client Chat Settings

settings.get.settings

Read. Scope: settings.read, admin. Contract: route_inferred. Get Settings

settings.opsiq.branding.clear

Write. Scope: admin. Contract: route_inferred. Opsiq Branding Clear

settings.opsiq.branding.upload

Write. Scope: admin. Contract: route_inferred. Opsiq Branding Upload

settings.privacy.settings.get

Read. Scope: settings.read, admin. Contract: declared_dynamic. Privacy Settings Get

settings.privacy.settings.save

Write. Scope: settings.write, admin. Contract: route_inferred. Privacy Settings Save

settings.save.ai.settings

Write. Scope: settings.write, admin. Contract: route_inferred. Save Ai Settings

settings.save.chat.widget.settings

Write. Scope: settings.write, admin. Contract: declared_dynamic. Save Chat Widget Settings

settings.save.client.chat.settings

Write. Scope: settings.write, admin. Contract: route_inferred. Save Client Chat Settings

settings.save.settings

Write. Scope: settings.write, admin. Contract: route_inferred. Save Settings

site_intelligence (221)

site_intelligence.action.audit.chain

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Action Audit Chain

site_intelligence.action.execute

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Action Execute

site_intelligence.action.preview

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Action Preview

site_intelligence.action.token

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Action Token

site_intelligence.agent.auto.bg

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Agent Auto Bg

site_intelligence.agent.auto.bg.stop

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Agent Auto Bg Stop

site_intelligence.agent.auto.step

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Agent Auto Step

site_intelligence.agent.chat

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Agent Chat

site_intelligence.agent.conn.delete

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Agent Conn Delete

site_intelligence.agent.conn.get

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Agent Conn Get

site_intelligence.agent.conn.save

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Agent Conn Save

site_intelligence.agent.conn.test

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Agent Conn Test

site_intelligence.agent.coverage

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Agent Coverage

site_intelligence.agent.events

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Agent Events

site_intelligence.agent.hosted.apply

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Agent Hosted Apply

site_intelligence.agent.hosted.finalize

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Agent Hosted Finalize

site_intelligence.agent.hosted.live.set

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Agent Hosted Live Set

site_intelligence.agent.hosted.preview

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Agent Hosted Preview

site_intelligence.agent.hosted.rollback

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Agent Hosted Rollback

site_intelligence.agent.hosted.start

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Agent Hosted Start

site_intelligence.agent.hosted.verify

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Agent Hosted Verify

site_intelligence.agent.run.delete

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Agent Run Delete

site_intelligence.agent.run.finalize

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Agent Run Finalize

site_intelligence.agent.run.rollback

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Agent Run Rollback

site_intelligence.agent.run.start

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Agent Run Start

site_intelligence.agent.run.status

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Agent Run Status

site_intelligence.agent.run.verify

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Agent Run Verify

site_intelligence.agent.runs.list

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Agent Runs List

site_intelligence.agent.set.mode

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Agent Set Mode

site_intelligence.agent.status

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Agent Status

site_intelligence.agent.step.apply

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Agent Step Apply

site_intelligence.agent.step.skip

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Agent Step Skip

site_intelligence.agent.turn.status

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Agent Turn Status

site_intelligence.ai.activity

Read. Scope: site_intelligence.read, admin. Contract: declared_dynamic. Si Ai Activity

site_intelligence.ai.alert.enrich

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Ai Alert Enrich

site_intelligence.ai.alerts

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Ai Alerts

site_intelligence.ai.analyst

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Ai Analyst

site_intelligence.ai.analyst.ask

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Ai Analyst Ask

site_intelligence.ai.analyst.email

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Ai Analyst Email

site_intelligence.ai.analyst.run

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Ai Analyst Run

site_intelligence.ai.badges

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Ai Badges

site_intelligence.ai.badges.portfolio

Read. Scope: site_intelligence.read, admin. Contract: declared_dynamic. Si Ai Badges Portfolio

site_intelligence.ai.badges.preview

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Ai Badges Preview

site_intelligence.ai.bl.plan

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Ai Bl Plan

site_intelligence.ai.bl.plan.run

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Ai Bl Plan Run

site_intelligence.ai.brief

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Ai Brief

site_intelligence.ai.brief.run

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Ai Brief Run

site_intelligence.ai.comp.analyse

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Ai Comp Analyse

site_intelligence.ai.comp.analyse.run

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Ai Comp Analyse Run

site_intelligence.ai.content.get

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Ai Content Get

site_intelligence.ai.content.list

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Ai Content List

site_intelligence.ai.content.publish

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Ai Content Publish

site_intelligence.ai.content.write

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Ai Content Write

site_intelligence.ai.daily.digest

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Ai Daily Digest

site_intelligence.ai.discover

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Ai Discover

site_intelligence.ai.fix.apply

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Ai Fix Apply

site_intelligence.ai.fix.apply.bulk

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Ai Fix Apply Bulk

site_intelligence.ai.fix.dismiss

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Ai Fix Dismiss

site_intelligence.ai.fix.dismiss.bulk

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Ai Fix Dismiss Bulk

site_intelligence.ai.fix.generate

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Ai Fix Generate

site_intelligence.ai.fix.generate.all

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Ai Fix Generate All

site_intelligence.ai.fix.list

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Ai Fix List

site_intelligence.ai.kw.coach

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Ai Kw Coach

site_intelligence.ai.kw.coach.run

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Ai Kw Coach Run

site_intelligence.ai.overview

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Ai Overview

site_intelligence.ai.page.audit

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Ai Page Audit

site_intelligence.ai.page.audit.run

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Ai Page Audit Run

site_intelligence.ai.portfolio

Read. Scope: site_intelligence.read, admin. Contract: declared_dynamic. Si Ai Portfolio

site_intelligence.ai.portfolio.history

Read. Scope: site_intelligence.read, admin. Contract: route_inferred. Si Ai Portfolio History

site_intelligence.ai.portfolio.run

Write. Scope: site_intelligence.write, admin. Contract: declared_dynamic. Si Ai Portfolio Run

site_intelligence.ai.probe

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Ai Probe

site_intelligence.ai.prompt.add

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Ai Prompt Add

site_intelligence.ai.prompt.history

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Ai Prompt History

site_intelligence.ai.prompt.remove

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Ai Prompt Remove

site_intelligence.ai.prompts

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Ai Prompts

site_intelligence.ai.readiness

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Ai Readiness

site_intelligence.ai.ready

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Ai Ready

site_intelligence.alert.resolve

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Alert Resolve

site_intelligence.alerts

Read. Scope: site_intelligence.read, admin. Contract: route_inferred. Si Alerts

site_intelligence.alerts.list

Read. Scope: site_intelligence.read, admin. Contract: route_inferred. List Site Intelligence alerts

site_intelligence.alerts.resolve

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Resolve a Site Intelligence alert Required fields: alert_id.

site_intelligence.analyze

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Analyze

site_intelligence.ask

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Ask

site_intelligence.audit.hint

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Audit Hint

site_intelligence.backlink.disavow

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Backlink Disavow

site_intelligence.backlinks

Read. Scope: site_intelligence.read, admin. Contract: route_inferred. Si Backlinks

site_intelligence.backlinks.list

Read. Scope: site_intelligence.read, admin. Contract: route_inferred. List backlinks

site_intelligence.backlinks.refresh

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Backlinks Refresh

site_intelligence.billing.overview

Read. Scope: site_intelligence.read, admin. Contract: declared_dynamic. Si Billing Overview

site_intelligence.brand.get

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Brand Get

site_intelligence.brand.radar

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Brand Radar

site_intelligence.brand.save

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Brand Save

site_intelligence.cannibalisation

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Cannibalisation

site_intelligence.compare

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Compare

site_intelligence.competitor.add

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Competitor Add

site_intelligence.competitor.refresh

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Competitor Refresh

site_intelligence.competitor.remove

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Competitor Remove

site_intelligence.competitors

Read. Scope: site_intelligence.read, admin. Contract: route_inferred. Si Competitors

site_intelligence.competitors.list

Read. Scope: site_intelligence.read, admin. Contract: route_inferred. List competitors

site_intelligence.content.brief

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Content Brief

site_intelligence.content.decay

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Content Decay

site_intelligence.content.draft

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Content Draft

site_intelligence.crawl.budget

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Crawl Budget

site_intelligence.crawl.list

Read. Scope: site_intelligence.read, admin. Contract: route_inferred. Si Crawl List

site_intelligence.crawl.status

Read. Scope: site_intelligence.read, admin. Contract: route_inferred. Si Crawl Status

site_intelligence.crawls.list

Read. Scope: site_intelligence.read, admin. Contract: route_inferred. List Site Intelligence crawls

site_intelligence.crawls.status

Read. Scope: site_intelligence.read, admin. Contract: route_inferred. Get crawl status

site_intelligence.dashboard

Read. Scope: site_intelligence.read, admin. Contract: route_inferred. Read the Site Intelligence dashboard

site_intelligence.dashboard.route.si.dashboard

Read. Scope: site_intelligence.read, admin. Contract: route_inferred. Si Dashboard

site_intelligence.dashboard.save

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Dashboard Save

site_intelligence.diag.backfill

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Diag Backfill

site_intelligence.diag.compare

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Diag Compare

site_intelligence.diag.portfolio

Read. Scope: site_intelligence.read, admin. Contract: declared_dynamic. Si Diag Portfolio

site_intelligence.diag.recs.regen

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Diag Recs Regen

site_intelligence.diag.thresholds

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Diag Thresholds

site_intelligence.diag.thresholds.eval

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Diag Thresholds Eval

site_intelligence.diag.thresholds.history

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Diag Thresholds History

site_intelligence.diag.thresholds.profile

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Diag Thresholds Profile

site_intelligence.diag.thresholds.save

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Diag Thresholds Save

site_intelligence.diagnostics

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Diagnostics

site_intelligence.exec.report

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Exec Report

site_intelligence.export

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Export

site_intelligence.ga4.connect

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Ga4 Connect

site_intelligence.ga4.list.properties

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Ga4 List Properties

site_intelligence.ga4.map

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Ga4 Map

site_intelligence.ga4.status

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Ga4 Status

site_intelligence.ga4.sync

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Ga4 Sync

site_intelligence.gbp

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Gbp

site_intelligence.gbp.draft.approve

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Gbp Draft Approve

site_intelligence.gbp.draft.dismiss

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Gbp Draft Dismiss

site_intelligence.gbp.draft.sync

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Gbp Draft Sync

site_intelligence.gbp.drafts

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Gbp Drafts

site_intelligence.gbp.locations

Read. Scope: site_intelligence.read, admin. Contract: declared_dynamic. Si Gbp Locations

site_intelligence.gbp.map

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Gbp Map

site_intelligence.gbp.post.draft

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Gbp Post Draft

site_intelligence.gbp.post.publish

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Gbp Post Publish

site_intelligence.gbp.qa

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Gbp Qa

site_intelligence.gbp.qa.approve

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Gbp Qa Approve

site_intelligence.gbp.qa.dismiss

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Gbp Qa Dismiss

site_intelligence.gbp.qa.sync

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Gbp Qa Sync

site_intelligence.gbp.site.prefs

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Gbp Site Prefs

site_intelligence.gbp.sync

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Gbp Sync

site_intelligence.google.truth.schedule.save

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Google Truth Schedule Save

site_intelligence.growth

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Growth

site_intelligence.gsc.connect

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Gsc Connect

site_intelligence.gsc.list.properties

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Gsc List Properties

site_intelligence.gsc.map

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Gsc Map

site_intelligence.gsc.opportunities

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Gsc Opportunities

site_intelligence.gsc.status

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Gsc Status

site_intelligence.gsc.sync

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Gsc Sync

site_intelligence.image.audit

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Image Audit

site_intelligence.internal.links

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Internal Links

site_intelligence.issue.history

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Issue History

site_intelligence.issues

Read. Scope: site_intelligence.read, admin. Contract: route_inferred. Si Issues

site_intelligence.issues.list

Read. Scope: site_intelligence.read, admin. Contract: route_inferred. List Site Intelligence issues

site_intelligence.keyword.add

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Keyword Add

site_intelligence.keyword.remove

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Keyword Remove

site_intelligence.keyword.research

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Keyword Research

site_intelligence.keywords

Read. Scope: site_intelligence.read, admin. Contract: route_inferred. Si Keywords

site_intelligence.keywords.list

Read. Scope: site_intelligence.read, admin. Contract: route_inferred. List tracked keywords

site_intelligence.local

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Local

site_intelligence.local.grid

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Local Grid

site_intelligence.local.grid.scan

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Local Grid Scan

site_intelligence.log.ingest

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Log Ingest

site_intelligence.log.summary

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Log Summary

site_intelligence.metadata.audit

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Metadata Audit

site_intelligence.overview

Read. Scope: site_intelligence.read, admin. Contract: declared_dynamic. Si Overview

site_intelligence.page

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Page

site_intelligence.page.experience

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Page Experience

site_intelligence.page.optimize

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Page Optimize

site_intelligence.pages

Read. Scope: site_intelligence.read, admin. Contract: route_inferred. Si Pages

site_intelligence.pages.list

Read. Scope: site_intelligence.read, admin. Contract: route_inferred. List Site Intelligence pages

site_intelligence.pagespeed.bridge.status

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Pagespeed Bridge Status

site_intelligence.portfolio.export

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Portfolio Export

site_intelligence.provider.health

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Provider Health

site_intelligence.rank.check

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Rank Check

site_intelligence.rec.action

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Rec Action

site_intelligence.recommendations

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Recommendations

site_intelligence.redirect.audit

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Redirect Audit

site_intelligence.report

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Report

site_intelligence.report.generate

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Report Generate

site_intelligence.reports

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Reports

site_intelligence.reports.list

Read. Scope: site_intelligence.read, admin. Contract: source_inferred. Site Intelligence Reports List

site_intelligence.reset.google.oauth

Write. Scope: site_intelligence.write, admin. Contract: declared_dynamic. Si Reset Google Oauth

site_intelligence.revenue

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Revenue

site_intelligence.revenue.portfolio

Read. Scope: site_intelligence.read, admin. Contract: declared_dynamic. Si Revenue Portfolio

site_intelligence.save.shared.google.oauth

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Save Shared Google Oauth

site_intelligence.scan.run

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Start a Site Intelligence analysis

site_intelligence.schedule.delete

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Schedule Delete

site_intelligence.schedule.run.now

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Schedule Run Now

site_intelligence.schedule.save

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Schedule Save

site_intelligence.schedules.list

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Schedules List

site_intelligence.schema.audit

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Schema Audit

site_intelligence.server.engineer

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Server Engineer

site_intelligence.settings.save

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Settings Save

site_intelligence.sites.list

Read. Scope: site_intelligence.read, admin. Contract: explicit. List Site Intelligence monitored sites

site_intelligence.speed

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Speed

site_intelligence.speed.progress

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Speed Progress

site_intelligence.speed.run

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Speed Run

site_intelligence.speed.v2

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Speed V2

site_intelligence.speed.v2.build.task

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Speed V2 Build Task

site_intelligence.speed.v2.collect

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Speed V2 Collect

site_intelligence.speed.v2.read

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Speed V2 Read

site_intelligence.speed.v2.run

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Speed V2 Run

site_intelligence.start.crawl

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Start Crawl

site_intelligence.task.approve

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Task Approve

site_intelligence.task.assign

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Task Assign

site_intelligence.task.bulk.apply

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Task Bulk Apply

site_intelligence.task.bulk.assign

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Task Bulk Assign

site_intelligence.task.bulk.deadline

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Task Bulk Deadline

site_intelligence.task.bulk.dismiss

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Task Bulk Dismiss

site_intelligence.task.deadline

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Task Deadline

site_intelligence.task.note

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Task Note

site_intelligence.task.proof

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Task Proof

site_intelligence.task.reject

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Task Reject

site_intelligence.task.review

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Task Review

site_intelligence.topical.map

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Topical Map

site_intelligence.webhook.delete

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Webhook Delete

site_intelligence.webhook.save

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Webhook Save

site_intelligence.webhooks.list

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Webhooks List

site_intelligence.workflow

Write. Scope: site_intelligence.write, admin. Contract: route_inferred. Si Workflow

Hali ya (6)

status.component.save

Write. Scope: status.write, admin. Contract: declared_dynamic. Status Component Save

status.components.save

Write. Scope: status.write, admin. Contract: explicit. Create or update a public status component Required fields: name. Retry-safe with idempotency_key.

status.incident.create

Write. Scope: status.write, admin. Contract: declared_dynamic. Status Incident Create

status.incident.resolve

Read. Scope: status.read, admin. Contract: route_inferred. Status Incident Resolve

status.incidents.create

Write. Scope: status.write, admin. Contract: explicit. Create a status-page incident Required fields: title. Retry-safe with idempotency_key.

status.incidents.resolve

Write. Scope: status.write, admin. Contract: source_inferred. Status Incidents Resolve Retry-safe with idempotency_key.

Uchunguzi wa Uchunguzi (22)

surveys.analytics.get

Read. Scope: surveys.read, admin. Contract: source_inferred. Surveys Analytics Get

surveys.audiences.list

Read. Scope: surveys.read, admin. Contract: explicit. List survey audiences

surveys.audiences.materialize

Write. Scope: surveys.write, admin. Contract: source_inferred. Surveys Audiences Materialize Retry-safe with idempotency_key.

surveys.campaigns.create

Write. Scope: surveys.write, admin. Contract: explicit. Create or update a survey campaign Required fields: deployment_id. Retry-safe with idempotency_key.

surveys.campaigns.launch

Write. Scope: surveys.write, admin. Contract: source_inferred. Surveys Campaigns Launch Retry-safe with idempotency_key.

surveys.campaigns.list

Read. Scope: surveys.read, admin. Contract: explicit. List survey campaigns

surveys.deployments.list

Read. Scope: surveys.read, admin. Contract: explicit. List survey deployments

surveys.deployments.set_status

Write. Scope: surveys.write, admin. Contract: source_inferred. Surveys Deployments Set Status Retry-safe with idempotency_key.

surveys.get

Read. Scope: surveys.read, admin. Contract: source_inferred. Surveys Get

surveys.imports.create

Write. Scope: surveys.write, admin. Contract: explicit. Create and run a survey import Required fields: kind. Retry-safe with idempotency_key.

surveys.imports.process

Write. Scope: surveys.write, admin. Contract: source_inferred. Surveys Imports Process Retry-safe with idempotency_key.

surveys.invitations.list

Read. Scope: surveys.read, admin. Contract: explicit. List survey invitations

surveys.links.create

Write. Scope: surveys.write, admin. Contract: source_inferred. Surveys Links Create Retry-safe with idempotency_key.

surveys.list

Read. Scope: surveys.read, admin. Contract: explicit. List survey definitions

surveys.responses.get

Read. Scope: surveys.read, admin. Contract: source_inferred. Surveys Responses Get

surveys.responses.list

Read. Scope: surveys.read, admin. Contract: explicit. List survey responses

surveys.triggers.list

Read. Scope: surveys.read, admin. Contract: explicit. List survey trigger sets

surveys.types.list

Read. Scope: surveys.read, admin. Contract: explicit. List supported question types and Studio templates

surveys.versions.list

Read. Scope: surveys.read, admin. Contract: source_inferred. Surveys Versions List

surveys.webhooks.delete

Write. Scope: surveys.write, admin. Contract: source_inferred. Surveys Webhooks Delete Retry-safe with idempotency_key.

surveys.webhooks.list

Read. Scope: surveys.read, admin. Contract: explicit. List survey webhook subscriptions

surveys.webhooks.save

Write. Scope: surveys.write, admin. Contract: explicit. Create or update a survey webhook subscription Required fields: url. Retry-safe with idempotency_key.

Timu ya timu (63)

team.delete

Write. Scope: team.write, admin. Contract: route_inferred. Admin Users Delete

team.delete.route.departments.delete

Write. Scope: team.write, admin. Contract: route_inferred. Departments Delete

team.list

Read. Scope: team.read, admin. Contract: route_inferred. Admin Users List

team.list.route.departments.list

Read. Scope: team.read, admin. Contract: declared_dynamic. Departments List

team.perf.activity

Write. Scope: admin. Contract: route_inferred. Team Perf Activity

team.perf.ai.compare

Write. Scope: admin. Contract: route_inferred. Team Perf Ai Compare

team.perf.ai.review

Write. Scope: admin. Contract: route_inferred. Team Perf Ai Review

team.perf.availability

Write. Scope: admin. Contract: route_inferred. Team Perf Availability

team.perf.award.finalize

Write. Scope: admin. Contract: route_inferred. Team Perf Award Finalize

team.perf.award.history

Read. Scope: team.read, admin. Contract: route_inferred. Team Perf Award History

team.perf.award.void

Write. Scope: admin. Contract: route_inferred. Team Perf Award Void

team.perf.claim.pay

Write. Scope: admin. Contract: route_inferred. Team Perf Claim Pay

team.perf.claim.recover

Write. Scope: admin. Contract: route_inferred. Team Perf Claim Recover

team.perf.claim.reject

Write. Scope: admin. Contract: route_inferred. Team Perf Claim Reject

team.perf.clear

Write. Scope: admin. Contract: route_inferred. Team Perf Clear

team.perf.coaching.action.item.add

Write. Scope: team.write, admin. Contract: route_inferred. Team Perf Coaching Action Item Add

team.perf.coaching.action.item.complete

Write. Scope: team.write, admin. Contract: route_inferred. Team Perf Coaching Action Item Complete

team.perf.coaching.evidence.pin

Write. Scope: team.write, admin. Contract: route_inferred. Team Perf Coaching Evidence Pin

team.perf.coaching.evidence.unpin

Write. Scope: team.write, admin. Contract: route_inferred. Team Perf Coaching Evidence Unpin

team.perf.coaching.session

Write. Scope: team.write, admin. Contract: route_inferred. Team Perf Coaching Session

team.perf.coaching.session.create

Write. Scope: team.write, admin. Contract: route_inferred. Team Perf Coaching Session Create

team.perf.coaching.session.update

Write. Scope: team.write, admin. Contract: route_inferred. Team Perf Coaching Session Update

team.perf.coaching.sessions

Write. Scope: team.write, admin. Contract: route_inferred. Team Perf Coaching Sessions

team.perf.coaching.status

Write. Scope: team.write, admin. Contract: route_inferred. Team Perf Coaching Status

team.perf.data

Write. Scope: admin. Contract: route_inferred. Team Perf Data

team.perf.heatmap

Write. Scope: admin. Contract: route_inferred. Team Perf Heatmap

team.perf.history

Write. Scope: admin. Contract: route_inferred. Team Perf History

team.perf.pay.all.claims

Write. Scope: admin. Contract: route_inferred. Team Perf Pay All Claims

team.perf.qa.calibration.record

Write. Scope: team.write, admin. Contract: route_inferred. Team Perf Qa Calibration Record

team.perf.qa.dispute.resolve

Write. Scope: admin. Contract: route_inferred. Team Perf Qa Dispute Resolve

team.perf.qa.disputes

Write. Scope: team.write, admin. Contract: route_inferred. Team Perf Qa Disputes

team.perf.qa.evaluation.submit

Write. Scope: team.write, admin. Contract: route_inferred. Team Perf Qa Evaluation Submit

team.perf.qa.overview

Write. Scope: team.write, admin. Contract: route_inferred. Team Perf Qa Overview

team.perf.qa.scorecard.publish

Write. Scope: team.write, admin. Contract: route_inferred. Team Perf Qa Scorecard Publish

team.perf.qa.scorecard.save

Write. Scope: team.write, admin. Contract: route_inferred. Team Perf Qa Scorecard Save

team.perf.quest.record

Write. Scope: team.write, admin. Contract: route_inferred. Team Perf Quest Record

team.perf.quest.save

Write. Scope: team.write, admin. Contract: route_inferred. Team Perf Quest Save

team.perf.quest.status

Write. Scope: team.write, admin. Contract: route_inferred. Team Perf Quest Status

team.perf.quests

Write. Scope: team.write, admin. Contract: route_inferred. Team Perf Quests

team.perf.recognition

Write. Scope: team.write, admin. Contract: route_inferred. Team Perf Recognition

team.perf.recognition.settings.save

Write. Scope: admin. Contract: route_inferred. Team Perf Recognition Settings Save

team.perf.recognition.streak.history

Write. Scope: team.write, admin. Contract: route_inferred. Team Perf Recognition Streak History

team.perf.recognition.streaks.record

Write. Scope: team.write, admin. Contract: route_inferred. Team Perf Recognition Streaks Record

team.perf.reward.budget.authorize

Write. Scope: admin. Contract: route_inferred. Team Perf Reward Budget Authorize

team.perf.reward.claims

Write. Scope: admin. Contract: route_inferred. Team Perf Reward Claims

team.perf.reward.pay

Write. Scope: admin. Contract: route_inferred. Team Perf Reward Pay

team.perf.reward.payouts

Write. Scope: admin. Contract: route_inferred. Team Perf Reward Payouts

team.perf.reward.period.finalize

Write. Scope: admin. Contract: route_inferred. Team Perf Reward Period Finalize

team.perf.reward.period.history

Write. Scope: team.write, admin. Contract: route_inferred. Team Perf Reward Period History

team.perf.reward.period.preview

Write. Scope: team.write, admin. Contract: route_inferred. Team Perf Reward Period Preview

team.perf.reward.period.reverse

Write. Scope: admin. Contract: route_inferred. Team Perf Reward Period Reverse

team.perf.reward.period.void

Write. Scope: admin. Contract: route_inferred. Team Perf Reward Period Void

team.perf.reward.save

Write. Scope: admin. Contract: route_inferred. Team Perf Reward Save

team.perf.reward.state

Write. Scope: admin. Contract: route_inferred. Team Perf Reward State

team.perf.trends

Write. Scope: admin. Contract: route_inferred. Team Perf Trends

team.perf.v2.data

Write. Scope: admin. Contract: route_inferred. Team Perf V2 Data

team.perf.v2.export

Write. Scope: admin. Contract: route_inferred. Team Perf V2 Export

team.perf.v2.live

Write. Scope: admin. Contract: route_inferred. Team Perf V2 Live

team.perf.v2.reward.sheet

Write. Scope: admin. Contract: route_inferred. Team Perf V2 Reward Sheet

team.perf.v2.settings

Write. Scope: admin. Contract: route_inferred. Team Perf V2 Settings

team.perf.v2.settings.save

Write. Scope: admin. Contract: route_inferred. Team Perf V2 Settings Save

team.save

Write. Scope: team.write, admin. Contract: route_inferred. Admin Users Save

team.save.route.departments.save

Write. Scope: team.write, admin. Contract: route_inferred. Departments Save

tiketi za ndege (77)

tickets.ai.summary

Write. Scope: tickets.write, admin. Contract: route_inferred. Ticket Ai Summary

tickets.analytics

Read. Scope: tickets.read, admin. Contract: route_inferred. Ticket Analytics

tickets.approval.decide

Read. Scope: tickets.read, admin. Contract: route_inferred. Ticket Approval Decide

tickets.approval.request

Read. Scope: tickets.read, admin. Contract: route_inferred. Ticket Approval Request

tickets.approvals.pending

Read. Scope: tickets.read, admin. Contract: declared_dynamic. Ticket Approvals Pending

tickets.assignment.rule.delete

Write. Scope: tickets.write, admin. Contract: route_inferred. Ticket Assignment Rule Delete

tickets.assignment.rule.list

Read. Scope: tickets.read, admin. Contract: declared_dynamic. Ticket Assignment Rule List

tickets.assignment.rule.save

Write. Scope: tickets.write, admin. Contract: declared_dynamic. Ticket Assignment Rule Save

tickets.assignment_rules.delete

Write. Scope: tickets.write, admin. Contract: source_inferred. Tickets Assignment Rules Delete Retry-safe with idempotency_key.

tickets.assignment_rules.save

Write. Scope: tickets.write, admin. Contract: explicit. Create or update a ticket assignment rule Required fields: name. Retry-safe with idempotency_key.

tickets.bulk

Write. Scope: tickets.write, admin. Contract: source_inferred. Tickets Bulk Retry-safe with idempotency_key.

tickets.bulk.route.tickets.bulk

Write. Scope: tickets.write, admin. Contract: route_inferred. Tickets Bulk

tickets.calendar.delete

Write. Scope: tickets.write, admin. Contract: route_inferred. Sla Calendar Delete

tickets.calendar.save

Write. Scope: tickets.write, admin. Contract: declared_dynamic. Sla Calendar Save

tickets.claim

Write. Scope: tickets.write, admin. Contract: route_inferred. Ticket Claim

tickets.csat.get

Read. Scope: tickets.read, admin. Contract: explicit. Get the CSAT response for one ticket Required fields: ticket_id.

tickets.csat.list

Read. Scope: tickets.read, admin. Contract: explicit. List ticket CSAT responses in the bound workspace

tickets.csat.metrics

Read. Scope: tickets.read, admin. Contract: explicit. CSAT metrics for a period (the tickets dashboard numbers)

tickets.embed.load

Write. Scope: tickets.write, admin. Contract: route_inferred. Ticket Embed Load

tickets.embed.save

Write. Scope: tickets.write, admin. Contract: route_inferred. Ticket Embed Save

tickets.embed.secret

Write. Scope: tickets.write, admin. Contract: route_inferred. Ticket Embed Secret

tickets.field.save

Write. Scope: tickets.write, admin. Contract: route_inferred. Ticket Field Save

tickets.follower.add

Write. Scope: tickets.write, admin. Contract: route_inferred. Ticket Follower Add

tickets.follower.remove

Write. Scope: tickets.write, admin. Contract: route_inferred. Ticket Follower Remove

tickets.get

Read. Scope: tickets.read, admin. Contract: source_inferred. Tickets Get

tickets.kb.deflection

Read. Scope: tickets.read, admin. Contract: route_inferred. Ticket Kb Deflection

tickets.kb.draft

Write. Scope: tickets.write, admin. Contract: route_inferred. Ticket Kb Draft

tickets.kb.save

Write. Scope: tickets.write, admin. Contract: route_inferred. Ticket Kb Save

tickets.kb.version.restore

Read. Scope: tickets.read, admin. Contract: route_inferred. Ticket Kb Version Restore

tickets.kb.versions

Read. Scope: tickets.read, admin. Contract: route_inferred. Ticket Kb Versions

tickets.link.add

Write. Scope: tickets.write, admin. Contract: route_inferred. Ticket Link Add

tickets.link.remove

Write. Scope: tickets.write, admin. Contract: route_inferred. Ticket Link Remove

tickets.list

Read. Scope: tickets.read, admin. Contract: source_inferred. Tickets List

tickets.open

Write. Scope: tickets.write, admin. Contract: source_inferred. Tickets Open Retry-safe with idempotency_key.

tickets.open_guest

Write. Scope: tickets.write, admin. Contract: source_inferred. Tickets Open Guest Retry-safe with idempotency_key.

tickets.ops.summary

Read. Scope: tickets.read, admin. Contract: declared_dynamic. Ticket Ops Summary

tickets.policy.delete

Write. Scope: tickets.write, admin. Contract: route_inferred. Sla Policy Delete

tickets.policy.save

Write. Scope: tickets.write, admin. Contract: declared_dynamic. Sla Policy Save

tickets.presence.leave

Read. Scope: tickets.read, admin. Contract: route_inferred. Ticket Presence Leave

tickets.presence.ping

Read. Scope: tickets.read, admin. Contract: route_inferred. Ticket Presence Ping

tickets.quick.replies

Write. Scope: tickets.write, admin. Contract: declared_dynamic. Ticket Quick Replies

tickets.quick.reply.save

Write. Scope: tickets.write, admin. Contract: route_inferred. Ticket Quick Reply Save

tickets.relations.get

Read. Scope: tickets.read, admin. Contract: route_inferred. Ticket Relations Get

tickets.reply

Write. Scope: tickets.write, admin. Contract: source_inferred. Tickets Reply Retry-safe with idempotency_key.

tickets.reply.delete

Write. Scope: tickets.write, admin. Contract: route_inferred. Ticket Reply Delete

tickets.reply.edit

Write. Scope: tickets.write, admin. Contract: route_inferred. Ticket Reply Edit

tickets.reply.outbound.convert

Write. Scope: tickets.write, admin. Contract: route_inferred. Ticket Reply Outbound Convert

tickets.reply.translate

Write. Scope: tickets.write, admin. Contract: route_inferred. Ticket Reply Translate

tickets.reply.translation.delete

Write. Scope: tickets.write, admin. Contract: route_inferred. Ticket Reply Translation Delete

tickets.reply.translation.save

Write. Scope: tickets.write, admin. Contract: route_inferred. Ticket Reply Translation Save

tickets.rule.compose

Read. Scope: tickets.read, admin. Contract: route_inferred. Ticket Rule Compose

tickets.side.ai.draft

Write. Scope: tickets.write, admin. Contract: route_inferred. Ticket Side Ai Draft

tickets.side.assign.department

Write. Scope: tickets.write, admin. Contract: route_inferred. Ticket Side Assign Department

tickets.side.create

Write. Scope: tickets.write, admin. Contract: route_inferred. Ticket Side Create

tickets.side.list

Read. Scope: tickets.read, admin. Contract: route_inferred. Ticket Side List

tickets.side.mention

Read. Scope: tickets.read, admin. Contract: route_inferred. Ticket Side Mention

tickets.side.recipients

Read. Scope: tickets.read, admin. Contract: declared_dynamic. Ticket Side Recipients

tickets.side.reply

Write. Scope: tickets.write, admin. Contract: route_inferred. Ticket Side Reply

tickets.sla.delete

Write. Scope: tickets.write, admin. Contract: source_inferred. Tickets Sla Delete Retry-safe with idempotency_key.

tickets.sla.save

Write. Scope: tickets.write, admin. Contract: explicit. Create or update an SLA policy Required fields: name. Retry-safe with idempotency_key.

tickets.split

Write. Scope: tickets.write, admin. Contract: route_inferred. Ticket Split

tickets.split.candidates

Write. Scope: tickets.write, admin. Contract: route_inferred. Ticket Split Candidates

tickets.tag.add

Write. Scope: tickets.write, admin. Contract: route_inferred. Ticket Tag Add

tickets.tag.list

Read. Scope: tickets.read, admin. Contract: route_inferred. Ticket Tag List

tickets.tag.remove

Write. Scope: tickets.write, admin. Contract: route_inferred. Ticket Tag Remove

tickets.tags.add

Write. Scope: tickets.write, admin. Contract: source_inferred. Tickets Tags Add Retry-safe with idempotency_key.

tickets.tags.list

Read. Scope: tickets.read, admin. Contract: source_inferred. Tickets Tags List

tickets.tags.remove

Write. Scope: tickets.write, admin. Contract: source_inferred. Tickets Tags Remove Retry-safe with idempotency_key.

tickets.update

Write. Scope: tickets.write, admin. Contract: source_inferred. Update a ticket status, priority, subject, department or assignment Retry-safe with idempotency_key.

tickets.view.delete

Write. Scope: tickets.write, admin. Contract: route_inferred. Ticket View Delete

tickets.view.list

Read. Scope: tickets.read, admin. Contract: declared_dynamic. Ticket View List

tickets.view.save

Write. Scope: tickets.write, admin. Contract: route_inferred. Ticket View Save

tickets.views.delete

Write. Scope: tickets.write, admin. Contract: source_inferred. Tickets Views Delete Retry-safe with idempotency_key.

tickets.views.save

Write. Scope: tickets.write, admin. Contract: source_inferred. Tickets Views Save Retry-safe with idempotency_key.

tickets.worklog.add

Write. Scope: tickets.write, admin. Contract: route_inferred. Ticket Worklog Add

tickets.worklog.delete

Write. Scope: tickets.write, admin. Contract: route_inferred. Ticket Worklog Delete

tickets.worklog.list

Read. Scope: tickets.read, admin. Contract: route_inferred. Ticket Worklog List

todos (1)

todos.add

Write. Scope: todos.write, admin. Contract: source_inferred. Todos Add Retry-safe with idempotency_key.

visitors (3)

visitors.block

Write. Scope: visitors.write, security.write, admin. Contract: route_inferred. Block a visitor Required fields: visitor_id.

visitors.list

Read. Scope: visitors.read, analytics.read, admin. Contract: route_inferred. List visitors

visitors.table

Read. Scope: visitors.read, admin. Contract: route_inferred. Visitors Table

Mtandao wa Yahoo (1)

webhooks.events.list

Read. Scope: webhooks.read, crm.read, admin. Contract: explicit. List outbound webhook events and their payloads

Kuandika kuandika (6)

writing.analyze

Write. Scope: writing. Contract: source_inferred. Writing Analyze Retry-safe with idempotency_key.

writing.compose

Write. Scope: writing. Contract: source_inferred. Writing Compose Retry-safe with idempotency_key.

writing.reply

Write. Scope: writing. Contract: source_inferred. Writing Reply Retry-safe with idempotency_key.

writing.rewrite

Write. Scope: writing. Contract: source_inferred. Writing Rewrite Retry-safe with idempotency_key.

writing.summarize

Write. Scope: writing. Contract: source_inferred. Writing Summarize Retry-safe with idempotency_key.

writing.translate

Write. Scope: writing. Contract: source_inferred. Writing Translate Retry-safe with idempotency_key.

Je, ni OpenAPI na Postman inapatikana?+

Ndio, ni wazi kuwa OpenAPI 3.0 Taarifa hiyo ni kuwa katika /api/v1/openapi.php, Orodha ya washindi wa tuzo hiyo ni katika /api/v1/postman.php, Na kwa upande wa wafanyakazi wenye ujuzi, Dk. /api/docs/.

Jinsi ya kufanya kazi na zaidi ya moja?+

Tuma tovuti_key katika mwili wa ombi kuchagua nafasi ya kazi. ufunguo uliotolewa kwa sehemu moja ya kazi unabakia imewekwa kwenye hiyo; ufunguo na muktadha wa admin unaweza kuchagua nafasi yoyote ya kazi inaruhusiwa kuona, na ni kukataliwa kwa yoyote ambayo sio.

Ni hatua gani zinaweza kuchukuliwa kuwa muhimu?+

Hatua yoyote iliyoonyeshwa kama kusoma. Weka ruhusa ya mode kwenye ufunguo wa kusoma_tu na kila kuandika inakataliwa na read_only_key, kwa hivyo ushirikiano wa taarifa hauwezi kubadilisha chochote hata kwa makosa.

Kwa nini nisifanye chochote ambacho ninaweza kuona katika ofisi ya tawi?+

Funguo linawekwa kwenye nafasi ya kazi. Rekodi katika maeneo mengine ya kazi hurudi sio_found badala ya kosa la ruhusa, kwa hivyo API hazithibitishi ikiwa kuna kitu mahali pengine.

Developer ya developer

Usalama wa usalama API

Mkataba mmoja wa usalama kwa kila kontakt na ushirikiano: kuuliza OpsIQ Nini kujua kuhusu moja ya IP Au unaweza kununua mara moja mbegu tayari katika kitalu, basi unapaswa kuwaza kwa usahihi.

OpsIQ Kwa upande wake, Mbunge huyo amesema kuwa kwa sasa IP firewall inazuia washambuliaji, bomba la tiketi filters spam, na AI ya Usalama inaainisha wahalifu na inapendekeza sheria za kuzuia. API kufungua akili hiyo kwa mifumo yako mingine. jukwaa la bili, bandari ya mteja au programu ya desturi inaweza kuangalia mgeni kabla ya kuamini, na kuripoti nini aliona hivyo kufunga nzima kujifunza kutoka kila uso.

Nini unaweza kufanya

Angalia Kabla ya Kuamini

Usalama. kuangalia majibu na hali ya firewall, utawala wowote wa spam unaolingana na mtumaji, na uamuzi wa AI uliohifadhiwa kwa IP. wito mmoja, maoni yaliyoimarishwa.

Kuripoti kile ulichoona

Ripoti ya usalama inarekodi uchunguzi kama tukio la usalama, ina AI ya Usalama IP Mara moja, na anawaonya admins wakati hukumu inakuja nyuma hatari kubwa. kurudia ripoti makundi katika matukio, hasa kama mashambulizi OpsIQ kuona moja kwa moja.

Shirikisha Sheria za Spam

Usalama. blocklist. add na usalama. com kusoma na kuandika sheria sawa spam ukurasa wa tiketi hutumia, hivyo mtu aliyezuiwa katika mfumo mmoja anazuiliwa kila mahali.

Kuripoti unyanyasaji kutoka kwa kontakt
POST /api/v1.php
Authorization: Bearer opq_your_api_key
Content-Type: application/json

{
  "action": "security.report",
  "ip": "203.0.113.7",
  "kind": "spam",
  "reason": "Sent 40 junk tickets in 10 minutes",
  "source": "whmcs:example.com"
}

Scopes na Usalama wa

security.read

Unahitaji usalama. check na usalama. blocklist. com salama kutoa ushirikiano wa taarifa.

security.write

Unahitaji usalama. ripoti na usalama. blocklist. add. Kutoa tu kwa mifumo unataka kulisha sheria na ripoti katika.

Hakuna kitu kilichoharibiwa kimya

Mtumaji aliyezuiwa bado anatua katika mtazamo wa Spam ambapo tiketi inaweza kusomwa na kurejeshwa.

Mfumo wa kujilinda

server ya mwenyewe IP Anwani haziwezi kamwe kufungwa, kuorodheshwa au kuripotiwa kupitia hii API Kwa hiyo, ushirikiano usiofaa hauwezi kuchukua jukwaa chini.

💡
Weka ufunguo chini ya Ushirikiano, kisha API Keys, na uipe tu mawanda ya usalama ambayo inahitaji. mkataba kamili wa ombi kwa kila hatua ni katika meta. actions na hati ya OpenAPI.
Je, watumiaji wa simu za mkononi wanatumia hii moja kwa moja?+

Sync nje ni tayari moja kwa moja: wakati kuziba IP, majukwaa kushikamana ni alisema kupitia sync usalama connector. Usalama API ni inbound nusu. Point connector yako au kanuni desturi katika hatua hizi nne na muhimu kubeba nyanja za usalama.

Je, ni wapi spam ya rufaa inaishi?+

Duka moja. ukurasa wa Tiketi Block udhibiti, spam AI katika Mipangilio, na hii API yote kazi dhidi ya orodha hiyo, kwa hivyo kuna mahali pa kuangalia.

Developer ya developer

Matukio ya matukio API

Tuma matukio ya desturi kutoka kwa seva yako au tovuti kwa OpsIQ kwa uchambuzi, majaribio, CRM husababisha, na hali ya wavuti.

Jinsi ya kufanya kazi
Matukio ya matukio APINjia () wito kutuma tukio la demo_booked katika OpsIQ, ambalo linalisha malengo ya uongofu, sehemu na kuchochea.OpsIQ^ Tnn., “msichana wa maandishi.”Thamani ya: 0^ Tnn., “kwa ajili ya.”});Malengo ya KubadilishaUgawaji waWatangazaji na wavutiBrowser (OpsIQ. track) au post ya upande wa seva /v1/events
Matukio ya matukio API

Matukio ya Browser

Ufuatiliaji wa Matukio ya Browser
window.OpsIQ = window.OpsIQ || [];
window.OpsIQ.push(["track", "button_clicked", {
  button: "signup",
  page: "/pricing",
  variant: "green"
}]);

Matukio ya upande wa Server

upande wa seva, shughuli za rekodi na uongofu dhidi ya kuwasiliana kupitia hatua API. crm.activities.record kwa shughuli ya maisha / biashara na crm.conversions.record Kwa ajili ya mabadiliko, hakuna events.send Hatua; Inbound CRM tukio mpokeaji anaishi katika /v1/inbound.php?t=<token> kwa ajili ya mifumo ya vyama vya tatu ambayo husukuma matukio katika

Shughuli ya upande wa seva (action) API)
POST /api/v1.php
Authorization: Bearer opq_your_key
Content-Type: application/json

{
  "action": "crm.activities.record",
  "site_key": "site_abc123",
  "email": "[email protected]",
  "event": "subscription.upgraded",
  "value": 50,
  "currency": "USD"
}

Mkataba wa Jina

Dots

"Maombi ya bure" hayakutolewa "kulipwa".

Wakati wa zamani

"Chat. click" sio "button. click."

Kuwa specific

"Piga simu" - si "user_action".

Developer ya developer

Jinsi data inavyoingia kupitia OpsIQ

Kuelewa mtiririko wa data husaidia kupunguza ushirikiano na kuongeza utendaji.

Jinsi ya kufanya kazi
Jinsi data inavyoingiaData hutiririka kutoka kwa widget na beacon katika OpsIQ msingi (CDP, graph utambulisho, ubongo AI, analytics, CRM) kisha nje kupitia webhooks na REST API.Widget ya& beacon yaOpsIQ Msingi wa msingiCDP · Orodha ya utambulishoUbongo waUchambuzi wa CRMWebmails ya Njeya ya API
Data ya mtiririko

Data ya ndani

1
Widget ya beacon

widget ya JavaScript inatuma maoni ya ukurasa, bonyeza, na ujumbe wa mazungumzo kwa /beacon.php.

2
Matukio ya kusisimua

Matukio yaliyohifadhiwa katika matukio ya opsiq_events na tovuti_key, aina ya tukio, mteja, na mali.

3
Mkutano wa Session

Maoni ya makundi ya wajenzi wa kikao katika vikao (kupitia cron).

4
Azimio la utambulisho

Wakati kutambuliwa, kumbukumbu zisizojulikana zinahusishwa na wasifu wa mteja.

5
Kuunganisha sync

Waunganishaji huchota data kutoka majukwaa ya nje na kuhifadhi katika cache ya kontakt.

6
Kwa muktadha

AI inakusanya muktadha kutoka: historia ya mgeni, maelezo ya mteja, data ya kontakt, KB, na haraka.

Data ya Outline

1
Matukio ya moto

Moto wa tukio la ndani (ticket. created, chat. ujumbe, utaratibu. completed).

2
Kazi ya Metro

Kazi ya msingi katika mstari wa async.

3
Mtandao wa WhatsApp

Kusambaza taarifa na kuwasilisha nyaraka zote za uwongo.

4
Kujiandaa kwa kushindwa

Kuondolewa kwa mbegu za kiume kumetokana na kurudi nyuma.

Mipangilio ya

Maelezo ya kumbukumbu

Mipangilio ni kituo cha udhibiti wa nafasi ya kazi. Kila kitu chini kinawekwa kwenye nafasi ya kufanya kazi unayoingia, hivyo akaunti moja inaweza kukimbia bidhaa kadhaa na vitambulisho tofauti, tabia ya kuzungumza na sheria za uhifadhi.

Kutafuta mpangilio

Kuna udhibiti wa watu mia sita katika Mipangilio, kuenea kwenye tabo kumi na moja zilizogawanyika chini ya menus nne. Hutarajiwa kuvinjari kwao.

Mipangilio ya Utafutaji (Ctrl + K)

Press Ctrl + K, au Cmd + K kwenye Mac, mahali popote kwenye ukurasa wa Mipangilio. Aina kwa maneno wazi na vyombo vya habari Kuingia moja kwa moja kwenye udhibiti. Utafutaji unavumilia typos ndogo na anaelewa maneno yanayohusiana, hivyo ratiba hupata Cron na faragha inapata udhibiti wa kufuatilia. Inaonyesha tu mipangilio ya jukumu lako inaweza kufungua.

Kazi ya Mradi na Mpango

ya jumla na wajibu.

Msaada wa Wateja na AI

Admin AI Msaidizi, Mteja Chat, OpsIQ Kuandika na Msaada Portal.

Data na Utawala

Kufuatilia na faragha, ruhusa na usalama.

Mfumo wa mfumo

Eneo la hatari (kwa ajili ya kujilinda) na eneo la hatari.

Kuhifadhi

Kila tab inaokoa peke yake na kifungo chake cha Hifadhi. Wateja wa Chat na OpsIQ Kuandika pin yao kwenye skrini. Hifadhi kabla ya kubadili tabo; mabadiliko hayachukuliwi kote.

Viungo vya ndani

Kichupo cha kazi kinaandikwa kwenye anwani ya ukurasa, kwa hivyo tab inaweza kuorodheshwa au kutumwa kwa mwenzake.

Jamii:Utambulisho wa Biashara

AI inasoma maadili haya kwenye kila jibu, ripoti na muhtasari wa kila siku.

Jina la biashara

Kutumiwa katika ripoti za AI, muhtasari wa kila siku na maneno ya wateja. Mechi mguu wako wa tovuti.

Biashara ya Viwanda

Uchanganuzi wa AI, kufunga bao la kuongoza, muhtasari na presets za uchunguzi. Chagua kutoka kwa mwenyeji wa wavuti, e-biashara, SaaS, mali isiyohamishika, shirika, ushauri, huduma ya afya, elimu, fedha au biashara ya jumla.

Mfumo wa lugha

Lugha iliyoonyeshwa kwa mtu yeyote ambaye hajachagua mwenyewe, kila wakala anaweza kuishinda katika wasifu wake.

Kutumia lugha ya browser

Inaonyesha ukurasa wa kuingia katika lugha ya mgeni mwenyewe. Mara mtu anapochagua lugha huko, uchaguzi wao unashinda na hii kamwe haizidi.

Mfumo wa Timezone

Eneo mfumo mzima anaendesha katika: tarehe, ripoti, ratiba na cron background. Tumia shughuli yako timezone, si wateja wako.

Tag: GeoIP na Ufuatiliaji

Hifadhi ya GeoIP2 Database

Njia kamili ya GeoLite2-City. mmdb. Auto-detects kwenye mzigo wa kwanza katika cPanel, Plesk, DirectAdmin, Cloudways, Docker na Linux wazi au Windows. Ongeza GeoLites2-ASN. mmDb katika folda moja kwa mtoa huduma wa wavuti mgeni.

Mfumo wa Vyanzo vya Geo

GeoLite2, geoLite 2 na sehemu ya pili Cloudflare Kugeuka nyuma, au Cloudflare ya pekee.Cloudflare Njia za maombi zinahitaji tovuti kuwa proxied kupitia Cloudflare, na viongozi wa eneo la wageni kuwezeshwa kwa maelezo ya jiji na mkoa.

Muda wa Kujiandikisha (s)

Ukosefu wa utendaji kabla ya kikao cha wageni kinachukuliwa kumalizika. Default 14400 ambayo ni ya masaa manne.

Kuingiliana kwa Interval (s)

Ni mara ngapi chakula cha uzima huburudisha. Default 30 Sekunde moja kwa ajili ya.

Kushikilia kwa nguvu (min)

Ni muda gani mgeni anahesabu kama kuishi baada ya mzigo wao wa mwisho wa ukurasa. Default 2 Hii ni kushuka kwa chakula cha kuishi, sio urefu wa kikao.

Data ya muda (siku)

Inafuta kumbukumbu zilizokusanywa na zinazozalishwa zamani ya umri huu: analytics, chat, tiketi, maoni, shughuli, AI telemetry, magogo ushirikiano na CRM shughuli. 0 Weka kila kitu milele. Mipangilio, maudhui yaliyoandikwa na risiti za idhini hazijaondolewa kamwe.

Wakati wa mazungumzo ya bure

Chagua kiasi gani cha mazungumzo yaliyofutwa hukaa kwenye rekodi: rekodi kamili, rekodi bila ya mazungumzo, au alama tu. Kuondoa daima huficha mazungumzo kutoka kwa kikasha na historia ya mgeni.

Ufuatiliaji wa trafiki ya bot

Inahesabu wa kutambaa kama wageni. Acha; inawasha hesabu za mgeni na hugonga kila ripoti.

Utafiti wa maoni ya popup kuwezeshwa

Inaonyesha widget ya maoni ya tovuti kwa wageni. Kujitenga na tafiti za mazungumzo chini ya Chat ya Mteja, Msaada wa Flow.

Jamii:Waliozaliwa

Master swichi kwa kila uso wa AI. Wote default juu na kuokoa kwa nafasi ya kazi.

Jaribu kwenye tiketi

Inaainisha kila tiketi kwa jamii, kipaumbele na hisia, na anaandika muhtasari wa thread juu ya tiketi.

Maelezo ya mchezo Monster

Inaonyesha vitambulisho vya triage na muhtasari katika tooltip wakati wakala hovers mstari katika orodha ya tiketi.

Inbox Copilot (kwa Kiingereza: copilot)

Inaongeza Rasimu ya AI kujibu, Warmer, Shorter, vifungo rasmi zaidi na vya msamaha chini ya sanduku la jibu la tiketi. Hakuna chochote kinachotuma bila wakala.

Kwa kuuliza-OpsIQ Copilot ya

Hakikisha unautazama ukurasa unaozunguka kwenye kila ukurasa wa admin. Unajua ni mteja gani, ankara au tiketi inafunguliwa.

Asubuhi ya leo

On kwanza wazi kila siku copilot inatoa tiketi za haraka, majibu ya kuchelewa na kuzungumza kusubiri. Jumapili kuzalisha wiki katika mapitio.

Fedha, Brand, Backup

OpsIQ Msingi wa Fedha

Kila fedha jumla katika admin ni waongofu katika sarafu hii kwa ajili ya kuonyesha. Waunganishaji kuhifadhi yao wenyewe chanzo sarafu; kuweka kwamba kwa kontakt.

Viwango vya Forex

Refreshes viwango kila masaa sita kutoka kwa kulisha bure ya umma bila ufunguo wa API. Unaweza kuongeza viwango vya mwongozo ambavyo hufunika malisho. Kwa kuacha moja kwa moja, sarafu bila kiwango cha mwongozo hutolewa.

Kuwezesha biashara na vipengele vya kulipa

Kugeuza kwenye ukurasa wa Mauzo na Kubadilisha, kadi za mapato ya dashibodi na Chakula cha Akili cha Kuishi. Kwa hiyo, kila uso wa bei umefichwa na ukurasa wa mauzo unaacha orodha.

Biashara ya msamiati

Mafunzo ya OpsIQ Neno lako: kama unafanya upya, neno la kufanya upya, kile unachouza, na kile wanunuzi wanaitwa.

Bidhaa na Logos

Vipakia viwili, moja kwa background nyepesi (admin sidebar) na moja kwa giza (ukurasa wa ishara). PNG, JPG, WebP au SVG hadi 3 MB.

Tovuti ya Upelelezi wa Tovuti, kuruhusu binafsi SSH Malengo ya malengo

Wakala wa SEO ya Auto-Implement unaunganisha juu ya SSH. Private, kitanzi na anwani zilizohifadhiwa zimezuiwa kwa default kama kipimo cha kupambana naSSRF. Tu kuwezesha kwenye vituo vya kibinafsi ambavyo lazima kufikia seva ya ndani.

OpsIQ Backup / Rejesha upya

na kutoa huduma kwa kila mkoa na OpsIQ- meza inayomilikiwa pamoja files uploaded.Rejea nafasi OpsIQ usanidi na kumbukumbu tu; kamwe hugusa wateja, ankara, tiketi, huduma, vikoa, maagizo au shughuli.

⚠️
Chukua chelezo kabla ya kutumia kitu chochote katika Eneo la Hatari. Backup huishi kwa ujumla na vitendo vya kufuta kuishi katika eneo la hatari, hivyo ni rahisi kufikia kifungo cha kufuta bila kuwa nje kwanza.
Mipangilio ya

Tag: Usalama wa

Ulinzi kwa ishara ya admin-katika, akaunti za wafanyakazi wako na data OpsIQ Inakusanya. ishara ya mteja kwa bandari ya msaada imesanidiwa tofauti.

Ulinzi wa Sign-in

Google ya GooglereCAPTCHA

Inaacha bots na stuffing ya uaminifu kwenye ishara ya admin. Chagua v3 (invisible, alifunga) au v2 (checkbox), kuweka kizingiti cha alama ya V3, na kusambaza tovuti na funguo za siri. funguo hizi hizo hutumiwa tena na fomu ya ombi la bandari ya msaada.

Kushindwa kwa Auto-Lockout

Inazuia anwani baada ya kushindwa kadhaa ndani ya dirisha, kwa masaa kadhaa. Unaweza Customize ujumbe wa ukurasa imefungwa na kuonyesha usumbufu mdogo wa kusubiri-screen.

Kuvunjika kwa Harding

Sera ya nywila kwa urefu wa chini, kukataa nywila zilizopatikana katika uvunjaji unaojulikana, lockout ya akaunti dhidi ya stuffing credential, lazima mbili-sababu kwa kila admin, password re-entry kabla ya vitendo hatari, na mpya vifaa ishara-katika alerts.

Ishara ya pekee (OIDC)

Wafanyakazi wanajiandikisha kupitia mtoa huduma wako wa utambulisho. Anahitaji mtoaji URL, ID ya mteja na siri ya mteja. vikoa vya utangazaji wa Auto, moja kwa kila mstari, huunda watumiaji moja kwa moja kwenye ishara ya kwanza.

Ujumbe wa moja kwa moja (SAML 2.0)

Kwa wale ambao wanaongea SAML. OpsIQ Majibu ya ACS URL na kitambulisho cha chombo cha SP; unapeana ID ya IdP, kuingia URL- Kujiandikisha kwa hiari URL ya X.509 Hati ya usajili. Mashamba ya sifa za barua pepe na jina zinahitajika tu kwa majina yasiyo ya kawaida ya sifa.

Utoaji wa SCIM

Kuundwa kwa Directory, update na deactivation ya OpsIQ Akaunti ya.OpsIQ Utoaji wa SCIM Msingi wa msingi URL; unazalisha ishara zilizowekwa hapa ili mtu aweze kufutwa bila kuvunja wengine.

Tishio, kuzuia na kukusanya

Orodha ya Egress Allow

Vikwazo ambavyo majeshi ya nje haya viunganisho vya workspace vinaweza kupiga simu. SSH Udhibiti wa Malengo kwa ujumla.

Kuharibu na Auto-Block

Kumzuia mgeni mara moja alama yao ya tishio hupita kizingiti chako. 0 Angalia ukurasa wa usalama kwa wiki moja kabla ya kuchagua idadi.

Weka ujumbe wa ukurasa

Ujumbe mgeni aliyezuiwa anaona, kama maandishi wazi au desturi yako mwenyewe HTML kuzuia screen.

Mtandao wa Vital kutoka kwa wageni halisi

Inapima LCP, INP na CLS kutoka vikao halisi.

Kuunganishwa, utoaji wa tukio la usalama

Matukio ya kawaida foleni katika browser na kutoa katika makundi na retries, kupunguza hasara kwenye uhusiano mbaya wa simu.

Ufuatiliaji wa Beacons

Vigae vilivyoandikwa halisi hubeba ishara ya cryptographic inayozunguka hivyo data ya kufuatilia iliyobuniwa inaweza kukataliwa. Off kwa default; kuwezesha mabadiliko jinsi embedi zinavyothibitisha, hivyo mtihani kwanza.

Tahadhari ya usalama

Kukataa na kuzuia kukimbia bila kujali. Kadi hii inadhibiti ikiwa unaambiwa, na ni kiasi gani AI inasaidia.

Kuwezesha tahadhari za usalama

Badilisha kwa ajili ya kadi hii.

Kiwango cha chini cha ve

Ni wangapi walioshindwa kuingia katika kipindi kifupi cha kuhesabu kama wimbi la thamani ya tahadhari.

IP Ufahamu wa akili

Inaongeza alama ya tishio kwa wageni wanaoonekana katika feeds za unyanyasaji wa umma.

Tovuti ya Watch

Uptime wa saa na TLS ukaguzi wa expiry, ukionya kabla ya lapses hati.

Mchambuzi wa Usalama na Ripoti ya Tukio la AI

Inaongeza hukumu inayoelezea shughuli za tuhuma, na vikundi vinavyohusika katika tukio moja linalosomwa badala ya mkondo wa matukio.

Sera ya Autopilot

Matendo peke yake, kugeuka kile kinachojifunza kutoka tukio katika sheria iliyopendekezwa au kutumika. kuondoka mbali mpaka wewe upya mapendekezo yake na kukubaliana nao.

Mshauri wa Usalama wa Kila siku na mshauri wa kila wiki

Recap ya kila siku kwenye ukurasa wa Usalama wa Usalama, na orodha ya kila wiki ya ugumu inayoonyesha kile kinacholindwa na ambacho bado kinafunguliwa.

Auto-expire Mapendekezo ya Kujitegemea

Sheria iliyopendekezwa ya kuzuia ambayo haujawahi kutenda inamalizika yenyewe badala ya kukusanya.

Mkutano wa DOM wa Replay

Kuwezesha Mkutano wa DOM

Wakati wa maktaba ya replay haijawahi kupakia, kwa hivyo hakuna gharama ya kuiacha. Rekodi ni sampuli na faragha-masked, na zinaangaliwa kwenye ukurasa wa Session Replay chini ya Analytics.

Kiwango cha sampuli, max kukamata, uhifadhi

Ni kiasi gani cha vikao vya kurekodi, muda wa rekodi moja unaweza kukimbia, na ni rekodi ngapi za siku zinahifadhiwa.

⚠️
Session replay rekodi watu halisi kutumia tovuti yako. Weka kiwango cha sampuli na uhifadhi kama chini kama bado kujibu swali lako, na kutoa katika taarifa yako ya faragha.
Mipangilio ya

Mipangilio: Ufuatiliaji na faragha

Nini maana ya nini OpsIQ Inaweza kukusanya, na ni muda gani kila aina ya rekodi inaishi.

Kuondolewa kwa

Kuondolewa kwa IPs Rangi ya CIDR

Anwani kamwe kufuatiliwa, moja kwa kila mstari, anwani halisi au safu za CIDR. Njia safi ya kuweka timu yako mwenyewe nje ya analytics yako, kwa sababu inashughulikia kila mtu katika anwani hiyo badala ya admins saini tu.

Kuondolewa kwa URL Barabara ya

Mipangilio ya ukurasa haijawahi kufuatilia, moja kwa kila mstari, wildcards na asterisk. Kwa mfano /admin/* inaweka ofisi yote ya nyuma nje ya logi ya wageni.

Sera ya Kufufua Data

Kusafisha kwa mfumo wa auto-purge katika siku. tofauti na kuweka jumla ya Data Retention katika General na kutoka eneo la hatari jitakasa.

Mawasiliano ya Logan

Kuaminika telemetry kushikilia hakikisho fupi ya swala na majibu. Default 90 siku. Hii ina ujumbe wa wateja zaidi, hivyo shorten kwanza wakati kukaza faragha.

Matukio ya Matumizi

Kwa kila simu token idadi kwa ajili ya gharama ya kuripoti. Default siku 90. Namba tu, hakuna maudhui ujumbe.

Hatua ukaguzi trail

Hatua ya kuharibu na logi ya usalama. Default 365 Tumia muda wako mwingi zaidi; hii ni njia ya ushuhuda.

Ugonjwa wa zinaa

Taarifa ya Afya ya Mfumo. Default 30 Siku za

Maswali yasiyo na majibu

Makundi ya maswali AI hakuweza kujibu. Default 90 siku. Kazi kupitia yao juu ya Maswali AI alikosa ukurasa kabla ya kumalizika.

Watchdogs na mauzo ya nje

Tahadhari ya Anomaly

Ulinganishaji wa kila siku wa jana dhidi ya msingi wa hivi karibuni, kuonya wakati metric inakwenda zaidi kuliko kizingiti chako. 35 kwa asilimia moja. na kwa bahati mbaya.

Uhamisho wa Ghala

dumps ya vikao, wageni, maoni ya ukurasa na meza zinazohusiana kwa stack yako mwenyewe ya BI, katika muundo unaochagua, umehifadhiwa kwa siku kadhaa.

Mipangilio ya

Msaada wa Admin

Msaidizi wa kuelea wafanyakazi wako hutumia ndani ya admin, na upatikanaji wa kusoma moja kwa moja kwa wateja, ankara, tiketi, seva na magogo ya cron. Msaidizi tofauti kutoka kwa mteja anayeshughulikia moja chini ya Mteja Chat.

Uwezo wa OpsIQ ya Widget

Onyesha kifungo cha msaidizi kwenye kila ukurasa wa admin. Off inaficha kwa kila mtu.

Kujali na tabia

Sehemu ya kona, upana wa jopo (320 Kwa ajili ya 600 Ukubwa wa juu ( max)400 Kwa ajili ya 900 Kwa upande mwingine, radius ya kona (0Kwa ajili ya 24), ukubwa wa font, na kioo kilichopigwa nyuma ya jopo.

Onyesha chips haraka

Moja-click vifungo vya mkato chini ya kichwa. njia ya haraka zaidi kwa wafanyakazi wengi.

Kuonyesha Model Info

Maonyesho ambayo mfano alijibu na muda gani ilichukua. Inatumia wakati tuning gharama, kelele kwa matumizi ya kila siku.

Mlango wa kuingia kwa admin

Tu inaonyesha msaidizi wa admin saini ambaye jina la mtumiaji na barua pepe wote mechi wakala OpsIQ aliyepewa nafasi hii ya kazi. Wamiliki daima kupita. Tumia Angalia kifungo changu cha upatikanaji kabla ya kuwezesha au unaweza kufunga timu yako mwenyewe nje.

Mtu wa

Jina la kuonyesha, tagline ya kichwa na ujumbe wa kuwakaribisha desturi ulioonyeshwa wakati jopo linafungua.

Smart-Action Chips ya haraka

Badilisha lebo na haraka kwa kila njia ya mkato, ongeza yako mwenyewe, au upya kwa default. Lebo ni nini wafanyakazi wanaona, haraka ni kile AI anapokea.

Rangi na maumbo

Chip sura (pill, rounded, mraba), rangi chip, mandhari kadi na umbo launcher (round, squircle, square), kwa preview kuishi.

Kumbukumbu ya mazungumzo

Msaidizi anakumbuka kila mtu historia katika vikao browser, hadi ujumbe wa 120, kuhifadhiwa katika database yako mwenyewe.

Mipangilio ya

Mtumiaji:Mteja wa Chat

Ya chat widget wateja wako kutumia, na eneo kubwa ya Mipangilio. sita sub-tabs, na bwana kubadili na Save pinned juu ya tab.

Kazi kupitia vifungu vidogo ili kwenye usanikishaji mpya: Utambulisho na nakala, Kuonekana, Tabia, Msaada wa Flow, Mafunzo ya Maarifa. Advanced ni miundombinu na inaweza kusubiri.

Utambulisho na Copy

Utambulisho wa Brand

Jina la Widget, tagline, jina la AI, jina linalotumiwa kwa mfumo na matangazo ya kazi, na jinsi majina ya wakala yanaonekana. Chanzo cha Jina la Agent huamua kati ya majina halisi, jina maalum au lebo ya timu.

Salamu za ndani

Salamu mbili, moja kwa wageni wote na moja kwa ajili ya wageni kutambuliwa. swali huanza mazungumzo zaidi kuliko taarifa.

Mchezaji wa Pop

Ujumbe unaozunguka kabla ya mazungumzo kufunguliwa, na jina lake mwenyewe, ukubwa wa font na rangi. AI inaweza kuandika teasers, na udhibiti wa wangapi kuzalisha, ni wangapi wa kuonyesha kwa ziara na pengo kati yao.

Kusafisha na kusafisha mikono

script kamili: kuuliza kwa jina na barua pepe, uthibitisho, kuomba binadamu, hakuna mawakala inapatikana, tiketi kuundwa au kufutwa, handoff inasubiri.

Taarifa ya Idle

Ujumbe wa tatu unaoonekana kwa wateja: wakala anafunga mazungumzo, mgeni amepumzika, na wakala ana mikono nyuma ya AI.

Kukubaliana na mapendekezo

Kuweka placeholder, studio ya kifungo cha kuzungumza-kwa-kibinadamu, na maswali yaliyopendekezwa ya ufunguzi. Mapendekezo matatu mazuri yanaonyesha tiketi zaidi kuliko ukurasa wa makala.

Wachezaji wa Icon na Avatars

Icon ya Launcher, icon tofauti ya hiari wakati wa kufungua, ukubwa wa uzinduzi, na picha kwa wakala wa binadamu na AI.

Kuonekana kwa

Mandhari na glasi

mode mandhari, premium rangi preset, blur kiwango na opacity, pamoja na toggles kwa ajili ya uhuishaji, mistari separator, maficho mstari wa hali, kujificha kadi sanduku la ujumbe na kuficha kifungo cha karibu. Kuanza na preset; unaweka kadhaa ya rangi mara moja.

Rangi kuu

Mjenzi, kichwa, kusaidia jopo, viungo, vifungo, matangazo ya mfumo na mtunzi, kila mmoja kwa rangi ya mwanzo na mwisho kwa gradients. Chaguo la kutumia kioo cha default hupuuza haya na huweka kumaliza wazi.

Paneli, Bubbles na Chips

Karibu wapiga kura thelathini kufunika jopo, mpaka, maandishi, eneo la pembejeo na kila aina ya Bubble (mgeni, AI, wakala, kuandika, mfumo) pamoja na chips mapendekezo na hali yao ya hover. Tu kufungua hii kwa ajili ya brand halisi vinavyolingana, na kuangalia tofauti juu ya maandiko ya Bubble.

Kulisha na kutengeneza

Ukubwa wa jopo na urefu, radius ya kona, ukubwa wa font, nafasi ya skrini, sura ya launcher, mtindo wa Bubble na ikiwa avatars zinaonyesha. mtihani upana kwenye simu.

Tabia ya tabia

Majibu ya moja kwa moja

Kugeuka kwa AI ni maana kila ujumbe unangojea kwa mwanadamu.

Kuingiliana kwa binadamu na asili ya maandishi

Ufuatiliaji wa upole wakati mgeni anapumzika, na ujumbe mfupi wa hiari wa pili njia ambayo mtu atatuma. Kuhusiana na ufuatiliaji wa max kwa kimya, kuchelewa kwanza, baadaye multiplier, dirisha la uwepo na dirisha la mlolongo wa kiwango cha juu. Inaweza kuwa mdogo kwa masaa ya biashara, na kuzimwa baada ya shukrani rahisi.

Majibu ya haraka na majibu

Ikiwa majibu yanaandika neno kwa maneno, na jinsi ya haraka majibu ya msaidizi, kwa kuweka mapema au kuchelewa kwako mwenyewe na kiwango cha juu katika milliseconds. Kuchelewa kidogo kusoma kama binadamu zaidi kuliko jibu la papo hapo.

Tafsiri ya Maisha

Kila wakala anasoma na kuandika katika lugha yake mwenyewe wakati mgeni anasoma yao.

Kurejea kwa A baada ya Agent idle

Dakika ya utendaji wa wakala kabla ya AI kuanza tena mazungumzo.

Kujiandaa kwa ajili ya chat

Kwanza kabla ya kupanda mbegu yenyewe.0Kamwe usifungue, ingia kwenye simu; ondoka0isipokuwa tu kwa ajili ya majaribio.

Majibu ya Smart

Kupanga mbele kwa majibu ya kupita moja, kutafakari kina, mfano wa hiari tofauti wa majibu ya wakala, kuonyesha hoja kwa wageni, kupunguza kumbukumbu za mazungumzo ya muda mrefu, kuzuia msaidizi wa biashara yako tu, bei katika sarafu ya mgeni, na jinsi viungo vinaonekana.

Gharama ya kuokoa

Ruka maarifa kutafuta kwa salamu kama vile hi na shukrani, na caps majibu ya muda mrefu katika ishara. Trims gharama bila kubadilisha jibu ubora juu ya maswali halisi.

Lugha za lugha

Lugha ambayo widget inasaidia na jinsi inachukua moja kwa mgeni.

Akaunti ya Wateja

Majibu kutoka kwa akaunti ya mteja iliyosainiwa, ilionekana kuishi, na imepakiwa tu wakati inahitajika.

Malipo ya

Maombi ya marejesho yaliyosaidiwa ambapo msaidizi hukusanya maelezo na mikono kwa mtu. Haikamilisha marejesho yenyewe.

Majadiliano na Widget

Kuweka mazungumzo ya zamani, kuendelea kuzungumza katika maeneo yako kushikamana, draggable dirisha, kuuliza wageni kwa barua pepe, na kuruhusu timu yako kugeuka chat katika tiketi.

Vipengele vya Widget

Emoji picker, viungo na mode ya kuchagua kuweka-pekee, AI picha uelewa, inline icons, mic, kuzungumza-kwa-agent kifungo, mgeni sauti, attachment preview, sauti-kupiga simu kifungo na mkutano kujitenga. AI picha kuelewa ni nini inaruhusu mgeni kuweka screenshot kosa na kupata jibu muhimu.

Admin Inbox, Notifications na kuwakaribisha popup

Mgeni kuwakaribisha popup, pamoja na mawakala wako tahadhari: sauti za kikasha, arifa za desktop, sauti Whispers binafsi Whispers beep, na kikao cha kura ya maoni.

Msaada wa Flow

Mkono wa binadamu

Jinsi maombi ya mtu yanapewa, sekunde wakala ana kujibu, ikiwa kupungua anarudi mazungumzo kwa AI, na kama AI inarudi wakati muda wa mwisho unamalizika.

Masaa ya kazi

Nyakati za kufungua, wakati wa ukanda na ujumbe wa saa zilizofungwa. Nje ya masaa haya AI haitatoa binadamu. ratiba tofauti kutoka kwa masaa ya biashara ya tiketi chini ya saa hizi OpsIQ kuandika.

Majibu ya A-A

Jibu la kwanza kwa ujumbe mpya, jibu wakati mtu tayari ame foleni, na muda gani kabla ya kurudia.

Fomu ya Nje

Inaonesha fomu ya kuwasiliana badala ya chat.

Ukaguzi wa tiketi na taarifa za Idara

Uelewa wa tiketi ya AI, hivyo mgeni akinukuu nambari ya tikiti anapata hali yake halisi, na ambayo idara AI inaweza kwenda. Jopo la kujengwa linaonyesha wapokeaji halisi kwa kila idara, limetatua njia sawa na notifier inawasuluhisha, ili uweze kuona kabla ya mteja kufanya hivyo kwamba idara inaonya mtu yeyote.

Msaada wa kituo cha widget ya chat

Hebu wageni kuvinjari makala zilizochapishwa bila kuacha chat. Wewe kuchagua ambapo hatua ya kuingia inaonekana, chini bar studio na icon, na kama kutoa kiungo kwa kituo kamili cha msaada.

Majadiliano ya Rating

Star rating yalisababisha wakati wakala kufunga chat, wakati handoff mwisho, au baada ya kipindi inactivity wewe kuweka. Pick moja au mbili triggers, si wote wao.

Utafiti wa Post-Chat

Utafiti mfupi wakati mgeni anafunga mazungumzo, na swali lako, kuchelewa, utawala wa muda na cap kwa ziara. Wageni wanaweza pia barua pepe au kupakua nakala. Swali moja linajibiwa; tatu hazijibu.

Utafiti wa Email Post-Chat

Uchunguzi wa kufuatilia na barua pepe baada ya mazungumzo kumalizika, kwa hiari katika lugha mgeni aliyezungumza, na udhibiti juu ya kuchelewa, somo, utangulizi, swali, maandiko yote ya kifungo na mstari wa kushukuru.

Majibu ya Maoni

Thumbs juu na thumbs chini kila jibu AI, kulisha dashibodi ubora.

Majadiliano ya Archive

Auto-archive baada ya siku, auto-resolve baada ya dakika ya ukimya, na kufuta mazungumzo archived baada ya Siku. nafasi ya tatu uhifadhi ni kuweka, pamoja Mkuu na Tracking.

Mafunzo ya Maarifa

Nini msaidizi kweli anajua. hakuna kitu kingine katika Wateja Chat mambo kama mengi.

Mafunzo ya ujuzi wa tovuti

Weka tovuti yako ili Msaidizi anaweza kujibu kutoka kwake. Hadi viungo kumi vya kuanzia, kikomo cha ukurasa, kina cha kiungo, na folda zilizotengwa. moja URL inaweza kupimwa kabla ya kutambaa kamili.

Kuingiliana

Kiolesura cha API muhimu na mfano ambao unageuza kurasa kuwa maana ya utafutaji badala ya mechi za neno la msingi.

Mtaalam wa Semalt

Bofya moja na AI inasoma kila FAQ na ukurasa wa kutambaa na unawaweka katika makundi.

Maswali, majibu yaliyothibitishwa

Swali na jibu jozi kutibiwa kama chanzo cha juu kipaumbele, kila mmoja na hali, uzito na jamii. Searchable, kuagiza kutoka JSON, na AI inaweza kuandika yao kutoka maelezo ya biashara yako. Wakati msaidizi anapata kitu kibaya, kuandika FAQ: ni outranks kurasa crawled, hivyo kurekebisha ni mara moja.

Maendeleo

Utendaji na mipaka

Kupiga kura muda, kikomo cha kiwango cha ujumbe na dirisha, ukubwa wa upeo wa attachment, majaribio ya vifungo kwa kila dirisha, na kuruhusu upanuzi wa faili. Orodha ya ugani ni udhibiti wa usalama; kuiweka imara.

Utoaji wa muda halisi

Ujumbe wa papo hapo na utoaji wa hali badala ya kupiga kura, kupitia Pusher, Ably au Firebase, na kipindi cha uchaguzi wa kurudi nyuma. Upigaji kura ni faini kwa maeneo mengi.

Taarifa ya dharura

Vifaa vya tahadhari kwa mawakala kupitia Pusher Beams au OneSignal, na maslahi ya kifaa.

Mtandao wa Push (VAPID)

Browser kushinikiza kutumia funguo yako mwenyewe yanayotokana na hakuna mtoa huduma wa tatu. Generated hapa, si katika Hatari Zone.

Sauti, Video na Screen kushiriki

Vyeti vya TURN hivyo wito kuunganisha kupitia mitandao ya kuzuia, kwa kutumia Cloudflare au hati miliki ya Twilio au TURN yako mwenyewe URL Jina la mtumiaji na imani.

Ndani ya Box Workflow

Mipangilio ya nafasi za kazi za wakala badala ya mipangilio ya mgeni: majibu ya kwanza SLA katika dakika, maoni ya foleni yaliyohifadhiwa, njia za mkato za kibodi na palette ya amri, utafutaji wa mazungumzo, na tiketi za wateja katika mkaguzi.

Njia za mawasiliano

WhatsApp, SMS, Facebook Messenger, Instagram, Telegram, X ujumbe wa moja kwa moja na LINE, kila mmoja na kubadili AI yake mwenyewe ya auto-reply, pamoja na kubadili sera kwa vitendo vya AI kwenye njia, jibu debounce na template ya kuunganishwa tena kwa WhatsApp. Kila kituo kinabaki katika sanduku sawa kama soga la wavuti.

Preview ya Widget Live chini ya sasisho za tab kama unavyohariri. Tumia badala ya kupakia upya tovuti yako ili kuangalia mabadiliko.
Mipangilio ya

Jamii:Mipangilio ya Templates

Kila barua pepeOpsIQKwa hiyo, nashauri kila mmoja wenu asome barua za Halmashauri yake ili aweze kusoma.OpsIQKwa hiyo, si tayari kutuma.

Moja ya kubuni, ujumbe wengi

Kwa kuwa Template ya barua pepe Ni wrapper: alama yako, kichwa, kadi, typography na footer, na katikati tupu. Kila ujumbe OpsIQ hutuma ni kuingizwa katika katikati hiyo. Edit wrapper mara moja na kila barua pepe mabadiliko pamoja - tiketi majibu, risiti ya Hifadhi, password upya, kumbukumbu booking, barua PeopleOS, na chochote kuandika mwenyewe.

Hakuna njia ya kutuma barua pepe kutoka kwa OpsIQ bila wrapper hii. Inatumika katika hatua moja kila ujumbe unaondoka, hivyo ujumbe ulioongezwa baadaye hauwezi kuikosa.

Kuchapisha ujumbe

1
Fungua Mipangilio, kisha Templates

Ujumbe umegawanywa na kile wao ni: tiketi na bandari, Hifadhi, kuingia na usalama wa akaunti, uhifadhi, mazungumzo na taarifa, ripoti, barua za PeopleOS, na yako mwenyewe.

2
Badilisha maudhui kwenye kile unachotaka

Unapata somo, mhariri wa maandishi tajiri na mtazamo wa HTML unaweza kubadili kuishi, na hakikisho la barua pepe iliyomalizika hasa kama mpokeaji anapokea - wrapper yako ni pamoja.

3
Tumia chips za variable

chips juu mhariri ni ukweli kwamba mabadiliko: tiketi namba, kumbukumbu ya utaratibu, wakati wa uhifadhi. Click moja kuacha ambapo mshale ni.

4
Kuokoa

Ujumbe huo tu imeandikwa. Acha shamba tupu na inaendelea kujengwa katika maneno; kidonge juu ya mstari anaelezea ni hali gani iko ndani.

💡
variable huna kutumia ni kuondolewa wakati barua pepe ni kutumwa, na hivyo ni mstari ni ameketi juu. Hiyo ni kwa nini booking bila namba ya simu kamwe kutuma "Phone:" na kitu baada yake.

Andika template yako mwenyewe

Tumia hii kwa ujumbeOpsIQJe, si tayari kutuma: taarifa ya utoaji, kukumbusha upya, pakiti kukaribisha, ufunguo wa leseni. inapata kila kitu ujumbe kujengwa katika anapata - mhariri, preview, sheria za mpango na kubuni yako ya kimataifa - na mfumo wako mwenyewe hutuma kupitia kwa njia yaAPI.

1
Kuongeza template

Kifungo hiki kiko juu ya ukurasa wa Templates na tena kando ya "Vidokezo vyako mwenyewe".

2
Jina la

Jina inakuwa kumbukumbu mfumo wako unatuma, kuonyeshwa chini ya shamba kama wewe aina - kwa mfano x_custom_delivery_booked. haiwezi kubadilika baadaye, kwa sababu kitu tayari itakuwa kutuma na hiyo.

3
Sema nini na wakati gani.

Mistari hii miwili ni kile wewe na wenzake kusoma kwenye ukurasa wa Templates mwaka kutoka sasa.

4
Chagua sehemu ambazo zinabadilika

Kutengwa, kwa mfano: jina, wakati, kufuatilia_link. Kila inakuwa {{variable}} unaweza kushuka kwenye somo au ujumbe, na mfumo wako unaijaza wakati wa kutuma.

5
Andika ujumbe na mada

Sentensi za wazi ni sawa - mapumziko ya mstari kuwa aya. Andika Ujumbe tu; nembo, kichwa na mguu huja kutoka template ya kimataifa.

6
Kuumba, kisha kufungua

Inaonekana chini ya "Violezo vyako mwenyewe" na mhariri kamili na hakikisho la kuishi, sawa na kila ujumbe uliojengwa.

⚠️
Write the message, not the whole page. A template that carries its own <html> document is refused, because a whole document would slip past the wrapper and your email would go out with none of your branding on it.

Kuhamisha template yako mwenyewe

Wito mbili juu ya bidhaa API. mpiga simu hutoa mpokeaji na vigezo - kamwe maneno na kamwe kubuni, hivyo ushirikiano hauwezi kutuma barua isiyo na alama kupitia nafasi yako ya kazi wala kubadilisha kimya kile unachowaambia wateja wako.

Chagua templeti zako na vigezo ambavyo kila mmoja huchukua
POST /api/v1.php
Authorization: Bearer YOUR_API_KEY

{ "action": "email.templates.list", "mine": true }
Acha kuwa
POST /api/v1.php
Authorization: Bearer YOUR_API_KEY

{
  "action": "email.template.send",
  "template": "x_custom_delivery_booked",
  "to": "[email protected]",
  "to_name": "Ada Obi",
  "variables": {
    "name": "Ada",
    "when": "Thursday 11 September, 14:00",
    "tracking_link": "https://track.example.com/AB12"
  }
}
💡
Majina tofauti kwenda bila braces katika API call. email. templates. list mikono yao nyuma katika sura hasa wewe kupita yao katika.

Templates na mpango wako

Ujumbe ambao hauna huduma kwa

Kukaa waliotajwa na kiungo "Angalia mipango" na hakuna mhariri - hivyo unaweza kuona niniOpsIQNi nini, na ni nini cha kufanya.

Template yako mwenyewe

Chagua huduma template ni ya wakati unapoiunda, au uiachie kwenye kila mpango. nafasi ya kazi bila huduma hiyo inaona imeorodheshwa lakini haiwezi kuhariri au kuituma.

Kuingia, usalama, arifa na mtihani wa barua pepe

Kamwe mpango-gated. Kuwa na uwezo wa kurekebisha neno la nywila upya admins yako mwenyewe kupokea itakuwa aina ya makosa ya kufuli.

Maswali ya Maswali

Ninawezaje kubadilisha muundo kwa ujumbe mmoja tu?+

Bali, na kwa makusudi. kubuni ni wrapper na ni pamoja, ambayo ni nini anaendelea kila barua pepe kutambua yako. Nini ni ujumbe wa kila mmoja ni neno, jopo la ukweli na vifungo yoyote wewe kuongeza ndani ya ujumbe.

Nini kinatokea ikiwa ninaweka upya?+

Reset inaonekana kwenye template ya kimataifa tu, na inachukua nafasi ya kile kilicho katika mhariri na kubuni iliyojengwa. Hakuna kitu kilichoandikwa mpaka bonyeza Save, hivyo unaweza kufunga mazungumzo ili kubadilisha akili yako.

Niliondoa moja ya templeti zangu kwa makosa.+

Kuondoa inachukua clicks mbili kwa sababu hiyo - silaha ya kwanza na kukuambia nini kuacha kufanya kazi. Kama tayari gone, kujenga tena na jina moja na kumbukumbu sawa huja nyuma; tu maneno lazima kuwa retyped.

Je, unaweza kuunganisha au kuongeza kwenye templeti zake mwenyewe?+

Ndiyo. pakiti meli ya mail_templates.json katika saraka yake mwenyewe, na jumbe zake zinaonekana chini ya " templates zaDeveloper" na mhariri huo, preview, wrapper na lango la mpango. hariri zako za maneno ni za nafasi yako ya kazi na kuishi mfuko wa kusasisha.

Mipangilio ya

Mipangilio ya: OpsIQ Kuandika kuandika

Tiketi zilijibiwa kwa maandishi: majibu ya moja kwa moja, mfumo wa tiketi ya asili, kuongezeka, masaa ya biashara, routing na barua pepe zinazoingiliana na wateja.

Auto-Reply

Maonyesho ya Show OpsIQ Kujiandikisha kwa Buttons

Ongeza vifungo vya msaada wa kuandika kwa mawakala wako katika admin.

Kuwezesha tiketi ya gari kwa usahihi

Chagua tiketi mpya na majibu na majibu yao baada ya kuchelewa. Kuanza nayo mbali na mapitio rasimu kwa wiki. Refunds, kufuta na mabadiliko ya upatikanaji lazima daima kufikia mtu.

Huduma za Auto-Reply

Ambayo idara auto-reply inaweza kujibu katika. chochote si waliotajwa ni kushoto kwa ajili ya binadamu, ambayo ni default salama.

Muda wa majibu (dakika)

Jibu la haraka linasoma kama roboti; dakika chache zinasoma kama timu ya haraka.

Max AI anajibu kwa kila tiketi ya idara

kifuniko kwa idara, kwa mfano Billing 1 na Msaada 3. Bila cap thread kuchanganyikiwa inaweza loop.

Kushughulikia urefu, hadhi na utambulisho

Ishara za kuandika juu, hali ya tiketi baada ya jibu na baada ya kuongezeka, na ambayo admin akaunti majibu moja kwa moja ni kuhusishwa na. Tumia akaunti wazi jina ili wafanyakazi wanaweza kuwaambia AI majibu kutoka kwa wanadamu.

Shughuli za tiketi ya asili

Mfumo wa tiketi za ndege

Mfumo wa tiketi umejengwa katika OpsIQ, kwa ajili ya kufunga bila msaada wa nje.

Bomba la Inbound Email kwenye Tiketi za Asili

Inabadilisha barua pepe zinazoingia kwenye tiketi. OpsIQ Kutoa Mwisho wa Point URL, ishara ya auth, njia ya script na PHP binary. Kitu chochote ambacho kinaweza post kwa endpoint hiyo inaweza kuunda tiketi, hivyo kuweka siri ya ishara.

Majibu ya mara kwa mara na kuchelewa na debounce

Ikiwa AI anaendelea kujibu wakati mazungumzo yanaendelea, na ikiwa inasubiri dirisha la utulivu hivyo jumbe tatu za haraka kupata jibu linalozingatiwa. Dirisha la utulivu ni mpangilio bora wa kufanya majibu ya kiotomatiki kujisikia kuchukuliwa.

Mtandao wa Msaada wa Umma

Ukurasa unaozingatia wateja ambapo mtu yeyote anaweza kuinua na kufuatilia tiketi, na mstari wa kuwakaribisha wa hiari. Anwani yake na kuangalia imesanidiwa katika tabo ya Msaada Portal.

Fomu ya Usajili

Ni barua ngapi za nasibu zinaonekana katika idadi ya tiketi zilizozalishwa.

Watumiaji wa barua pepe katika lugha yao wenyewe

Barua pepe za tiketi zinafuata lugha ya mteja. barua pepe ya wafanyakazi haibadilishi lugha: arifa, tahadhari za idara, mkutano na ripoti zilizopangwa kukaa katika lugha yako ya mfumo.

Kutambuliwa na kuthibitishwa

Kukiri fasta kwenye tiketi mpya, pamoja na ujumbe wa uthibitisho wakati tiketi ni kufunguliwa, wakati maoni ni kushoto na wakati tiketi imefungwa, kila mmoja na hakikisho kuishi. Kuna pia ya kimataifa template wrapper na kiungo nyuma ya mtazamo wako tiketi kifungo.

Uchunguzi wa spam

Tiketi za skrini kutoka kwa watu wasiojulikana, na zinaweza kuhamisha spam ya watuhumiwa peke yake. Acha hoja moja kwa moja hadi uone hukumu yake.

tiketi za ndege za karibu

Kufunga tiketi baada ya siku kadhaa za utulivu. Mwambie mteja katika ujumbe wa kufunga jinsi ya kufungua tena.

Masaa ya Biashara (SLA kalenda)

Timezone, ufunguzi na kufunga nyakati, siku za kazi na likizo kwa mara ya kwanza na wakati wa azimio. ratiba tofauti kutoka Masaa ya Kazi chini ya Wateja Chat.

Auto-kununua tiketi mpya

Kazi moja kwa moja, kwa hiari tu kwa mawakala ambao ni mtandaoni, na ujuzi wa wakala na unyeti wa mechi kwa uendeshaji wa msingi wa ujuzi.

Kuwasilisha kwa duplicate

Spots wakati mteja kufungua tiketi karibu na moja wao tayari, na mechi adjustable unyeti.

Utafiti wa kuridhika baada ya kumaliza

Barua pepe utafiti siku baada ya kufunga. matokeo kuonekana kwenye ukurasa wa CSAT.

Kuthibitisha huduma kwa njia ya barua pepe

Barua pepe idara wakati tiketi mpya fika. Wapokeaji ni wanachama wa idara hiyo, si idara mailbox anwani, ambayo ni inbound anwani ya tiketi kuwasili.

Nini ambacho mtu anaweza kusoma

Upatikanaji wa data ya mteja

Kubadilisha bwana pamoja na ruhusa ya kusoma tu kwa muhtasari wa wasifu wa mteja, ankara, shughuli, usawa wa mkopo, bidhaa na huduma, vikoa, seva zilizounganishwa na maelezo ya akaunti ya juu. Anza na muhtasari wa maelezo ya wasifu na kuongeza makundi kama majibu yanavyohitaji.

Elimu na Maarifa

Kuwezesha upatikanaji wa tiketi

Unahamisha tiketi kwa idara inayofaa zaidi kabla ya kujibu. Unachagua idara zilizoruhusiwa, kuchelewesha ukaguzi, na unaweza kuandika maagizo yako ya kuongeza kasi.

Ujuzi wa mazingira

Kama majibu kutumia lugha ya mteja, kama wao kuvuta juu ya viungo crawled na FAQs, kama AI anasoma picha na PDF viungo, mode jibu maarifa, kama kuagiza JSON maarifa ni kutumika, na kama chanzo viungo inaweza kuonekana. Matumizi crawled viungo na FAQs lazima juu, au AI ni guessing.

Kusimama nyuma ya gari baada ya majibu ya kibinadamu

Mara baada ya wafanyakazi kujibu, AI ataacha kujibu tiketi hiyo. Bila hiyo AI inaweza kuzungumza juu ya wakala wako mwenyewe.

Maelekezo ya tiketi na barua pepe

Maelekezo ya maandishi ya bure kuunda sauti na maudhui kwa kila jibu, na mfano wa kazi unaoweza kupakiwa. Kuwa maalum kuhusu kile AI haipaswi kufanya kamwe.

Uagizaji wa bidhaa JSON Ujuzi wa ujuzi

Pakia au kuweka faili ya elimu ya JSON kwa msaidizi wa kuandika.

Studio ya Button

designer kamili kwa ajili ya mteja-inatumia kifungo: kuonyesha style, ukubwa, studio, icon, sura, upana wa chini, background mtindo na rangi za msingi na sekondari, pembe gradient, mpaka, kona radius, kivuli, typography, padding, uhuishaji wavivu, hover mwendo na rangi, na lengo pete, pamoja na desturi CSS sanduku kwa chochote udhibiti hawana kufunika.

Mipangilio ya

Mipangilio: Msaada wa Portal

Tovuti inayozingatia wateja ambapo watu wanainua na kufuatilia tiketi na kusoma makala zako za usaidizi. Kifungu hiki kinadhibiti jinsi inavyofikiwa na jinsi wateja wanavyoingia; muundo wake wa kuona unafanywa katika Studio ya Usaidizi Portal.

Tovuti ya Kuingiza au Kuhamisha Tiketi: Ni nini kingine ninachotaka?

Hizi ni bidhaa mbili tofauti na watu huchanganya mara kwa mara. Wanatatua matatizo mbalimbali, na kuendesha yote mawili ni kawaida.

Msaada Portal Studio: mahali unapotuma wateja kwa

Studio ya A Tovuti kamili ya msaada ambayo OpsIQ majeshi kwakoIna anwani yake ya wavuti, au kikoa chako mwenyewe, na hubeba uzoefu wote wa huduma ya kibinafsi: kusaidia makala kwa kutafuta, fomu ya ombi, historia ya tiketi, ishara ya mteja na msaidizi. Chagua template, fanya kazi kupitia Mandhari, Navigation, Layout, Knowledge, Footer, Brand, Tiketi, Msaidizi, Fomu na Msaidizi. CSS, preview katika desktop, kibao na ukubwa wa simu, kisha kuchapisha.

Tumia wakati Unataka marudio moja ya branded unaweza kuonyesha kila mteja, na ungependa kujenga au kudumisha eneo la msaada ndani ya tovuti yako mwenyewe.

Tiketi ya tiketi: tiketi ndani ya tovuti yako mwenyewe

Kuingiza kwa kuweka Uzoefu wa tiketi tu kwenye ukurasa wa tovuti yako mwenyeweWateja kufungua, kufuatilia na kujibu maombi ya msaada bila kuacha kurasa zako, na kichwa chako mwenyewe, urambazaji na kubuni kukaa hasa kama wao ni. Weka mpangilio, kuonekana na sheria za upatikanaji katika wajenzi wa widget, preview matokeo, kisha nakala snippet embed katika ukurasa wako.

Tumia wakati Tayari una tovuti au programu na muundo wake mwenyewe, na unataka msaada wa kutokea ndani yake badala ya kumpa mteja mbali kwa anwani tofauti.

Tafsiri ya fupi

Studio hiyo ilijenga mahali ambapo wateja wako wanatuma· Kuingiza tiketi za ndege ambapo wateja wako tayariBiashara nyingi huendesha zote mbili, kuingiza widget ya tiketi katika eneo la akaunti yao kwa maombi ya maandishi wakati wa kuweka bandari iliyohifadhiwa kama marudio kamili ya huduma na makala na utafutaji.

Mawasiliano na upatikanaji

Njia ya Upatikanaji wa

Ikiwa bandari ni wazi kwa mtu yeyote au vikwazo kwa wateja waliojiandikisha. Open portals kupata tiketi zaidi na spam zaidi.

Chagua chaguo

Ikiwa bandari na kituo cha msaada hushiriki shujaa mmoja au kutumia mbili, ambayo urambazaji na mguu huonekana kwenye nyuso zote mbili, na studio ya sehemu ya urambazaji.

Anwani ya Portal

Chagua jina na OpsIQ inaonyesha bandari inayosababisha na anwani za kituo cha usaidizi. Kubadilisha baadaye huvunja viungo ambavyo umetuma tayari.

Domain yako mwenyewe

Inatumikia bandari kutoka kwa kikoa chako mwenyewe, kama vile support. yourdomain. com.

Tovuti ya Tiketi ya Kujiandikisha

Badilisha kwenye widget ya kushuka iliyoelezwa hapo juu, na kufungua wajenzi wa embed ambapo unachagua mpangilio, kuonekana na sheria za upatikanaji, utathmini matokeo na nakala ya snippet kwa ukurasa wako. Hii sio Portal Studio: Studio inaunda bandari iliyohudhuria, hii inaweka tiketi ndani ya tovuti yako mwenyewe.

Jinsi wateja wanavyoingia katika

Hizi ni wateja wako ishara katika chaguzi. wafanyakazi ishara-katika ni configured chini ya Mipangilio, Usalama.

Mbinu za kuingia

Chaguo ambazo zinaonekana kwenye ukurasa wa kuingia. Connector na barua pepe ya kazi moja kwa moja.

Ishara ya kijamii

Watoa huduma wa akaunti ya watumiaji, kila mmoja anahitaji kitambulisho cha mteja na siri, na anwani ya moja kwa moja inayotolewa na OpsIQ kujiandikisha na mtoa huduma huyo.

Ishara ya pekee (OIDC)

Kuingia kwa wateja kupitia mtoa huduma wa utambulisho, na mtoaji wa habari URL, ID ya mteja, siri na orodha ya hiari ya kikoa cha barua pepe.

Wateja wa SAML 2.0

Mfano SAML sawa. OpsIQ hutoa jibu ACS URLna SP chombo ID; wewe usambazaji IdP chombo id, kujiandikisha-katika na kujisajili-out URLs X 509 cheti na majina ya hiari sifa. Kugeuka SAML juu ya katika Sign-katika mbinu au haitakuwa kuonekana.

Ingia kwenye akaunti yako ya YouVersion

Kiungo cha kina kilichosainiwa ili mteja tayari alitia saini kwenye nchi yako ya maombi katika bandari bila kusaini tena. OpsIQ Kutoa siri ya usajili, portal URL na ufunguo wa kazi, njia kamili ya lugha yako (PHP, Laravel, WordPress, WHMCS, Node.jsFlask, Django, NET, Rails, Java, Go, na juu ya kufunga binafsi OpsIQ Seva yenyewe), maelezo ya usanidi wa hatua kwa hatua, na jenereta ya kiungo cha mtihani uliosainiwa. Tumia jenereta kabla ya kuandika msimbo wowote.

Jinsi njia inavyofanya kazi

Njia ya kupata mteja aliyesainiwa kwenye programu yako (mgeni anatumwa kuingia kwako na nyuma), anasoma siri kutoka kwa seva yako, ishara ya wakati mmoja ambayo inaisha katika dakika mbili, na kuelekeza tena kwenye bandari bila kichwa cha kukodisha na hakuna-jengo ili ishara hiyo haijafungwa au kuvuja.

Ishara ya portal mwenyewe katika button

Katika Portal Studio, Ingia ukurasa, kurejea kwenye Tumia kuingia kwa tovuti yangu na kuweka ukurasa wako wa kuingia URL kwenye njia hiyo. portal anaongeza “opsiq_portal_return (ukurasa mteja alikuwa juu); njia inaheshimu tu wakati iko ndani ya anwani yako ya bandari na huleta mteja huko, iliyosainiwa.

WHMCS

Hakuna kitu cha kuandika: WHMCS ndoana kutoka maeneo ya mbali tayari ishara wateja katika bandari na inashughulikia anwani ya kurudi. kuweka ukurasa wako login URL Kwa ajili yako WHMCS Eneo la kuingia kwa mteja.

Kujiandikisha kila mahali

Kuingia nje ya bandari pia ishara mteja nje ya programu yako.

Uwindaji na ulinzi

Maombi ya Fomu za maombi

Ambayo mashamba muundo fomu ya maombi kukusanya. Kila uwanja wa ziada kupoteza maoni, hivyo kuuliza tu kwa nini unahitaji triage.

Ulinzi wa Spam na Matumizi mabaya

Hifadhi ya asali na kiwango cha kuzuia daima kulinda fomu ya umma. Juu unaweza kuzuia anwani za barua pepe zinazoweza kutumiwa, kuongeza vikoa vyako vilivyozuiwa, na kuongeza CAPTCHA kwa kutumia Google reCAPTCHA au Cloudflare Turnstile. reCAPtcha inabadilisha funguo zilizowekwa tayari chini ya Mipangilio, Usalama; Funguo za Turnstil zimeingia hapa.

Portal analytics ya tovuti

Muhtasari wa kusoma tu wa shughuli za portal katika siku thelathini zilizopita.

Mipangilio ya

Mipangilio: Ruhusa, Leseni, Cron na Eneo la Hatari

Kundi la Mfumo, pamoja na udhibiti wa upatikanaji wa timu ambayo huamua nani anaweza kuona ni tab gani ya Mipangilio.

Upatikanaji wa timu na ruhusa

Ruhusa ya Usimamizi wa Ad

Kila msimamizi anapata wazi seti ya ruhusa kuzunguka mazungumzo inbox upatikanaji, ambayo Settings sehemu wanaweza hariri, na idara zao. Mtu yeyote na jukumu la Msimamizi kamili daima ina kila idhini. Settings ruhusa kufanya uamuzi ambao tabs mtu anayaona, hivyo kutoa set finest kwamba inaruhusu kazi yao.

Wajibu wa

Onyesha leseni yako ya sasa, kile kinachokupa na hali yake.

Cron Setup ya Kupumua

Kujitegemea kufunga tu. Kwenye wingu la OpsIQ kazi zilizopangwa zinakuendesha na tab imefichwa. Mstari mmoja wa crontab hutoa kila kazi iliyopangwa: tiketi ya gari-reply, routing ya kuongezeka, ubadilishaji wa kiwango cha kuburudisha, kura ya sanduku la barua na maingiliano ya kontakt.

1
Andika mstari wa

Kichupo kinaonyesha mstari halisi wa crontab kwa seva yako na PHP sahihi binary tayari iliyochaguliwa.

2
Ongeza kwenye crontab

Tumia crontab - kama mtumiaji anayeendesha PHP na kuweka mstari mmoja. kwenye cPanel kutumia chombo cha Cron Jobs badala yake.

3
Ukaguzi

Ndani ya dakika, vigae vya mapigo ya moyo vinaangaza. Tumia Run sasa kupima mara moja badala ya kusubiri.

Jopo la mapigo ya moyo linaonyesha kukimbia kwa mwisho, muda na kile kilichochakatwa kwa foleni ya auto-reply na barua pepe na kontakt poll. Inaonya wakati kukimbia kwa mara ya mwisho kulikuja kutoka kwenye kifungo cha mtandao wa mwongozo badala ya cron halisi ya seva, na wakati mapigo ya mioyo yamekwenda.

Eneo la hatari

Kufuta data zote za kufuatilia

Unashughulikia kila kitu OpsIQ kilichokusanywa au kuzalishwa. Unashughulikia kile cha kujumuisha na kuunda maneno ya uthibitisho hasa. Mipangilio na usanidi wa tovuti, anwani zilizozuiwa, kila kitu ambacho timu yako iliandika (msingi wa ujuzi, Maswali, tafsiri, miundo ya bandari, ufafanuzi wa hatua) na risiti za idhini zote zimehifadhiwa.

Data ya awali zaidi kuliko

Sweep Same mdogo kwa rekodi za zamani kuliko. 30, 60, 90 au 180 siku, au mwaka. Kwa ajili ya moja kwa moja rolling uhifadhi kutumia maadili uhifadhi katika Ujumla na Tracking badala yake na hebu kazi iliyopangwa kufanya hivyo.

🚫
Kusafirisha nakala kutoka kwa Mipangilio, Mkuu kabla ya kutumia kitu chochote katika Eneo la Hatari. vitendo hivi haviwezi kufutwa.
Mipangilio ya

Kusimamia timu yako

Kuwakaribisha wanachama wa timu na kutoa majukumu ya kudhibiti nani anaweza kupata nini.

Timu ya Timu
Timu na idaraScreen ya timu: meza ya admins na mawasiliano, jukumu badge (Owner, Full Admin, Agent) na idara kila mmoja anaweza kupata.Timu na idaraNafasi ya KaziTimu na idara+ Hifadhi ya mtumiajiMawasiliano ya simuUhusikaMiradi yaAo[email protected]Ada yaMmiliki wa MmilikiWoteKM KM KMKM[email protected]Mji mkuu ni Mensah.Usimamizi kamiliWoteRT ya[email protected]Rita Tetteh yaAgent waBilling yaya SB[email protected]Agent waMsaada wa msaada1TEAMKuwakaribisha na kusimamia admins2ROLESMmiliki · Admin kamili · Afisa3SCOPEDUpatikanaji wa sehemu
screen halisi ya timu: kila admin na mawasiliano yao, jukumu na idara wanaweza kufikia, mawakala scoped, wamiliki kamili.

Majukumu ya

Mmiliki wa Mmiliki

Upatikanaji kamili ikiwa ni pamoja na leseni, bili, na eneo la hatari. moja kwa kila ufungaji.

Usimamizi kamili

Leseni kamili ya upatikanaji isipokuwa na eneo la hatari. inaweza kusimamia admins.

Agent wa

Limited kwa idara zilizopewa. Tiketi, mazungumzo, na analytics tu.

Kuwavutia wanachama wa timu

1
Nenda kwa timu

Kujiandaa kwa timu katika uwanja wa mpira.

2
Bonyeza hapa

Kuingia kwa barua pepe ya mwanachama wa timu.

3
Kuundwa kwa jukumu

Chagua mmiliki, msimamizi kamili au wakala.

4
Idara ya Assign

Kwa wafanyakazi, chagua idara za kupatikana.

5
Tuma maombi

Wanapokea barua pepe na kiungo cha kuanzisha.

Mipangilio ya

Utendaji wa Timu

Upatikanaji ni kwa ruhusa, sio kwa jukumu: idhini ya maoni inafungua ukurasa, idhini ya kusimamia kufungua malengo, QA na usomaji wa kutambua mwenzake, na kibali cha kifedha cha tuzo ni kile kinachoongeza tabo ya Zawadi. Kiongozi wa timu anaweza kupewa yoyote kati ya haya bila kuwa msimamizi kamili.

Utendaji wa Timu
Utendaji wa Timuscreen ya utendaji wa timu: mawakala nafasi na mchanganyiko alama bar, CSAT na usawa malipo na kifungo cha kulipa kwa kila mstari.Utendaji wa TimuNafasi ya KaziUtendaji wa TimuMwakilishiMatokeoCSAT ya CSATKwa mara yaRT yaRita Tetteh ya4.8$42Malipo ya kulipaya SBSam Boateng4.5$28Malipo ya kulipaKM KM KMKMMji mkuu ni Mensah.4.2$15Malipo ya kulipaAoAda ya4.9$51Malipo ya kulipa1SCOREDUwasilishaji wa Utendaji2CSAT & LOADUkubwa wa + volume3REWARDSMalipo ya wakala
screen halisi ya utendaji wa timu: kila wakala alifunga juu ya kiasi na CSAT, na usawa wa tuzo unaweza kulipa kwa kila mstari.

Jinsi ukurasa ulivyoandaliwa

Kila mmoja ana jibu la swali tofauti, na wanaamriwa kwa jinsi ya haraka wanavyohitaji wewe.

01 Kituo cha Central Command Center

Hali ya foleni ya moja kwa moja, matokeo ya wateja dhidi ya malengo yako, jinsi uwezo ulivyotumika, hali zinazohitaji uamuzi, na ripoti ya usawa wa ushahidi.

02 Wachezaji wa timu

Kiongoziboard, utambuzi (bora zaidi na streaks), Jumuia, na opt-katika kudhibiti kwa nani anaweza kuona cheo.

03 Ubora wa ubora

Scorecards, tathmini zilizorekodiwa, makubaliano ya mapitio ya nafasi, drift reviewer, na migogoro ya ushahidi.

04 Malipo ya

Thamani ya Token, madai ya malipo, na ugawaji wa kipindi cha utawala: kuidhinisha dari iliyofadhiliwa, kukagua hakiki, kukamilisha.

05 Historia ya historia

Jinsi nafasi ya kazi imehamia kwa muda: metrics za mwenendo na chati, na 28-Siku chanjo ya joto kuonyesha wakati timu ilikuwa kweli kazi. Kila kadi kujificha mwenyewe mpaka kuna historia ya kutosha kuteka ni.

Hakuna kikomo cha 0

Mshiriki bila kiasi cha kutosha kilichoshughulikiwa - au vipimo vyake vinavyobeba ushahidi vinaongeza hadi chini ya nusu ya uzito uliosanidiwa - imeonyeshwa kama Unscored. Alama yao, cheo na bendi ni tupu na kuvunjika kwao kumefichwa. Hii ni kwa makusudi: kutoa kipimo kisichokuwepo kama sifuri inaweka mtu chini ya cheo cha kuwa na wiki ya utulivu. Vifungu vya Ushahidi vinaweza kuunganishwa kwa nafasi ya kazi katika Malengo & kufunga.

Vifungu viwili vya ushahidi hufanya kazi tofauti na ni thamani ya kuwaweka mbali. Kima cha chini kinachoshughulikiwa huamua kama mtu anapigwa kabisa. Kiwango cha chini hakiathiri alama: kinaamua tuzo na ustahiki wa malipo. Kwa hivyo mchezaji anaweza kufungwa kikamilifu na kuwekwa nafasi na bado hawezi kwa kipindi hicho, kwa sababu wateja wachache sana walipimwa.

💡
Kila takwimu ina wigo wa nafasi ya kazi unayotazama na wakati unaochagua. Mshiriki anayefanya kazi katika maeneo mawili tofauti ana rekodi ya kujitegemea katika kila mmoja. isipokuwa mbili zenye thamani ya kujua: tovuti ni sehemu moja ya kazi, hivyo vikoa vyake vya wanachama vinapimwa pamoja; na Watesi wanaona kwa makusudi hatua kila kitu kwa mara moja.

index ya utendaji

Mchanganyiko wa vipimo vitano, kila kipimo dhidi ya lengo wewe kuweka badala ya kinyume na wenzake, kisha vunjwa kuelekea katikati wakati ushahidi nyuma ni nyembamba. Kumbuka mwelekeo: marekebisho hatua takwimu kuelekea 70, hivyo nyembamba alama bora ni vunjwa chini na nyembamba alama maskini ni pulled up. mbaya wiki ya kwanza juu ya mazungumzo manne si hukumu makazi pia. Kama ushahidi hujilimbikiza takwimu kurekebishwa converges kwenye moja mbichi.

Ubora wa ubora

kuridhika kwa wateja kutoka maoni kuthibitishwa. Supplemented na matokeo ya alama ya QA ambapo wale wapo na wanasimamiwa.

Ujibu wa

Mara ya kwanza majibu katika P50 na P90 asilimia, dhidi ya malengo yako.

Azimio la

Muda wa azimio na kiwango cha kugusa moja.

SLA

Ukamataji dhidi ya SLA umesanidi, pamoja na makosa ya hatari na yaliyovunjwa.

Uendelezaji wa

Kurejesha na kurejesha - kazi ambayo inakuja.

💡
Uzito ni configurable na jamaa; hawana haja ya jumla 100. Kukosekana ushahidi inaweza tu kupunguza index, kamwe kuinua - uzito kamili uliowekwa unakaa katika denominator.

Uwezo na muda wa uzalishaji

Uandaaji, wakati wa uzalishaji, kutatuliwa kwa saa ya uzalishaji na sehemu ya mtandaoni ya dirisha. Matumizi hayaripotiwi kwa makusudi: inahitaji masaa yaliyopangwa kama msimamizi,OpsIQ haina orodha au chanzo cha kuhama, na denominator mbadala itakuwa nadhani amevaa alama ya asilimia. Inasoma kama haipatikani kwa sababu hiyo iliyoambatanishwa.

⚠️
Ripoti tu. Occupancy inasema jinsi muda ulivyotumika, kamwe haukutumia vizuri kiasi gani, na kamwe hautumii fedha, milango au ukubwa wa malipo. Mfanyakazi asiye na ushahidi wa wakati wa kushughulikia anasoma kama haipatikani, kamwe si sifuri.

Ubora wa uhakika

Alama ya alama ni wahakiki wa rubric wanafunga mazungumzo halisi dhidi. Ni toleo lililochapishwa tu linaweza kupokea tathmini, na kuchapisha toleo jipya ambalo halijaandika upya kile ambacho tayari kimefungwa. Mapitio ni ushahidi kuhusu mazungumzo moja, sio uamuzi juu ya mtu.

Mkataba wa

Taarifa kama takwimu iliyorekebishwa ya nafasi (Cohen na Fleis' kappa), sio asilimia ya makubaliano ghafi. Wahakiki wawili ambao wanapitisha kila kitu wanakubaliana 100% ya wakati huo wakiwa hawana habari.

Ufuatiliaji wa drift

Ikiwa mhakiki ana alama ngumu au laini zaidi kuliko wenzake kwenye mazungumzo hayo - kulinganisha dhidi ya jopo lote, sio mwenendo baada ya muda. Inahitaji mwingiliano uliopitiwa kwa kujitegemea zaidi ya mara moja.

Migogoro ya

Mshiriki wa timu anaweza kupinga ushahidi rasmi uliorekodiwa juu yao. Mwisho wa muda wa tuzo hadi utakapotatuliwa.

Uchunguzi wa kujitegemea

Kwa bahati mbaya, mtu hawezi kufanya uchunguzi wa kibinafsi.

⚠️
Tathmini ya AI-iliyojengwa haiwezi kushawishi malipo mpaka calibration kuchapishwa kuonyesha mfano unakubaliana na wahakiki wa binadamu kwa karibu kutosha, kupimwa na kappa dhidi ya sampuli ya chini. Lango la wazi lina maana kwamba mfano unakubali watu karibu kutosha kuhesabu - kamwe inamaanisha mfano ni sahihi.

Utambuzi wa utambuzi

cheo peke yake ina kumbukumbu kushindwa modes: michezo ya kubahatisha metric, burnout, na shaming umma wa yeyote ni mwisho. tatu mbadala kukaa pamoja nayo.

Uboreshaji wa

Kupimwa dhidi ya rekodi ya mchezaji mwenyewe mapema, kamwe dhidi ya wenzake, na shrinkage hivyo denominator ndogo haiwezi kununua kushinda.

Kuwa na

Kipindi cha kupunguzwa hukutana na bar iliyowekwa, iliyotangazwa - wastani wa rating, kiasi kilichoshughulikiwa, hesabu ya ratings na kiwango cha biofeedback hasi, takwimu zote kabisa. Kila mtu anaweza kushikilia streak wakati huo huo, kwa hivyo inajenga hakuna cheo, na mwenzake mwenye mwezi wa kipekee hawezi kuvunja yako.

Orodha ya kuingia

Mshiriki daima anaona index yao wenyewe; kama wao kuona wenzake ni uamuzi wa nafasi ya kazi. bendi asilimia inaweza kuchapishwa badala ya nafasi kabisa.

💡
Utambuzi kamwe haugusa fedha. streak haiwezi kufadhili malipo au kuvunja moja, na kuboreshwa zaidi sio kikundi cha tuzo.

Jumuia ya

Lengo la timu hufanya kazi kuelekea, kupimwa dhidi ya bar iliyowekwa iliyotangazwa badala ya dhidi ya kila mmoja - hivyo kila mtu anaweza kufuta jitihada sawa katika kipindi hicho.

Scope na cadence

Mtu binafsi au timu; moja ya nje, kurudia, au msimu na dirisha wazi.

Vigezo vya

Mazungumzo kushughulikiwa, ratings kupokea, siku kazi, wastani rating, au hasi kiwango cha maoni. wote kabisa - hakuna metric ambayo thamani inategemea nini wenzake alifanya.

Ulinzi wa Ubora

Inahitajika juu ya jitihada yoyote na lengo la kiasi. Kupiga idadi wakati ubora huanguka chini ya sakafu huzuia jitihada badala ya kukamilisha, na imeonyeshwa kama imezuiliwa, sio isiyokamilika.

Mara kwa mara mipaka

cap ya kila kipindi, inaendeshwa na kipimo cha polepole zaidi, pamoja na baridi ya hiari kabla ya kurudia inaweza kuhesabu.

Timu ya Jumuia

Maendeleo ya pamoja bila attribution ya kila timu iliyochapishwa, kwa hivyo jitihada ya timu haiwezi kuwa kiongozi.

Mafunzo ya vikao

Kipindi cha kufundisha ni rekodi, sio mazungumzo. Ina kocha, mchezaji wa timu kuwa kocha, wakati uliopangwa, walikubaliana pointi za kuzungumza, na muhtasari ulioandikwa baadaye. Mazungumzo ya kweli, tiketi na tathmini za QA zinaonyeshwa kama ushahidi, kwa hivyo mazungumzo yanaunganishwa kufanya kazi ambayo kweli yalitokea badala ya hisia kukumbukwa.

Majadiliano ya pointi

Ilikubaliwa kabla ya kikao, kwa hivyo mchezaji huyo hakwenda katika mshangao.

Ushahidi wa uwongo

Mazungumzo, tiketi na tathmini za QA zinazohusiana na kikao. Pin huhifadhi kumbukumbu - aina na kitambulisho - sio nakala, kwa hivyo daima inaonyesha kwenye rekodi ya kuishi.OpsIQ Haithibitishi kitambulisho kabla ya kukubali.

Mambo ya hatua

Kila mmoja na mmiliki na tarehe ya kufaa. kipengee iliyopita tarehe yake ni kuonyeshwa kama overdue - hali inayotokana, si hadhi mtu ana kukumbuka kuweka.

Maelezo ya kibinafsi

Mchezaji wa timu ya kocha hawezi kusoma kamwe - sio kama wakala, si kama meneja, sio kama mmiliki. ukaguzi huo unapita mbele ya ruhusa nyingine yoyote na hauwezi kuzidiwa.

Nani anaweza kuona mkutano wa

Kocha, mchezaji, na mtu yeyote aliye na idhini ya utendaji wa timu. Hakuna mwingine, ikiwa ni pamoja na wachezaji wengine katika idara hiyo.

Ukaguzi

Kila uumbaji, update, pin, unpin na kukamilika ni kumbukumbu na nini kilichobadilika, ambaye.

💡
Kufundisha ni kwa makusudi tofauti na kufunga na kutoka fedha. kikao hakibadilishi index ya mtu yeyote, haina lango la tuzo, na haionekani kwenye ubao wa kiongozi.

Tuzo na tuzo za

Shughuli zilizorekodiwa zinabadilika kuwa ishara na thamani ya fedha uliyoweka. Njia ya malipo ni polepole kwa makusudi na kila hatua inarekodi.

1
Weka thamani ya ishara

Ni ishara ngapi sawa na kiasi gani cha fedha, na kila shughuli ni thamani.

2
Kuwezesha upatikanaji wa fedha za

Kwa kipindi cha kalenda ya kufungwa, msimamizi kamili anasema ishara za kiwango cha juu ambacho kinaweza kulipa. Kuhifadhi fomu ya mipangilio haiidhinisha bajeti, na haiwezi kubadilisha dari ambayo tayari imeidhinishwa.

3
Maoni ya preview

Wapokeaji, hifadhi, na sababu mtu yeyote hawezi. migogoro ya ushahidi wazi kuzuia hatua hii.

4
Mwisho wa

Ugawaji huo umerekodiwa kwa kudumu na ushahidi nyuma yake. Kipindi ambacho hakikutengwa chochote kinaweza kufutwa na kukimbia tena wazi. Moja ambayo ilitoa ishara lazima ibadilishwe kwanza:OpsIQ Kuandika kuingia kulinganisha dhidi ya kila mkoba na kamwe kufuta asili, hivyo ledger bado inaonyesha nini kilichotokea na kwa nini, na wakati huo tu ni kipindi kilichotolewa. reversal anakataa kama mtu yeyote tayari fedha nje zaidi ya kiasi kuwa kulipwa, na majina ambao na kwa kiasi gani.

⚠️
Uhalali unahitaji maoni ya wateja kuthibitishwa. alama za ubora wa AI zinaweza kuongeza hukumu hiyo lakini kamwe sio mbadala, na mwenzake anayeonyeshwa kama Unscored haifai. Kila mchangiaji anafungwa kwa kila mshiriki.25% Zaidi ya sehemu yao inayotarajiwa ya kipindi, hivyo mwezi mmoja wa juu sana hauwezi kuchukua bajeti nzima.
💡
Mmiliki wa akaunti hashiriki katika tuzo au zawadi za ishara, bila kubadili: wanaidhinisha dari iliyofadhiliwa na kukamilisha kila ugawaji, na hakuna mtu aliye juu yao kupitisha kile wanacholipa wenyewe. Kazi yao inapimwa, imefungwa na imewekwa kwenye bodi kama mtu mwingine yeyote.

Kila mtu mwingine anashiriki kwa chaguo-msingi, timu inaongoza na wamiliki wa ushirikiano ni pamoja na. Kumwacha mtu nje, kuwafungua katika Timu & Idara na kubadili kutoka kwenye Sehemu ya Tuzo na chaguo la tuzo. Kazi yao bado imefungwa na kuonyeshwa; wanaacha kuwa mgombea kutoka hatua hiyo kuendelea, na hakuna kitu kilichokamilishwa tayari kimeguswa.

⚠️
Hakuna mtu anayekubali pesa kwa ajili yake mwenyewe. Kwa sababu watu ambao wanaweza kushiriki pia ni watu ambao wataweza kupitisha malipo, OpsIQ wanakataa malipo au mikopo kwenye mkoba wako mwenyewe, kulipa madai yako mwenyewe, kukamilisha kipindi ambacho utalipwa, na kumaliza tuzo ambayo ungeshinda. msimamizi mwingine kamili au mmiliki lazima afanye hivyo.

ambao wanaweza kuona na kufanya kile ambacho

Kuangalia utendaji wa timu

Bodi, hali ya kuishi, uwezo na mtazamo wa ubora kwa nafasi ya kazi.

Kusimamia utendaji wa timu

Malengo na kufunga, mauzo ya nje, alama za QA na tathmini, kufundisha, Jumuia, na kusoma kwamba hubeba data ya kutambua wenzake kama historia ya uongozi na historia ya tuzo.

Kuangalia timu ya malipo

Mizani, maadili ya fedha, maelezo ya madai na marejeo ya malipo - yametenganishwa na ushahidi wa utendaji kwa sababu ni malipo-adjacent.

Kiongozi wa pekee

Kila mabadiliko ya fedha: kulipa tuzo, kulipa au kukataa madai, kuidhinisha bajeti, kukamilisha, kufuta au kubadilisha ugawaji, na kuweka kiwango cha ishara-kwa-kash. Hizi haziwezi kutumwa kwa kutoa ruhusa.

Kwa kutumia kwa usahihi

Fahirisi ya utendaji ni ushahidi wa usimamizi, sio uamuzi wa ajira moja kwa moja. Fungua mazungumzo ya chanzo nyuma ya idadi kabla ya kutenda juu yake, na kupima utata wa kesi, ratiba, kuondoka na mahitaji ya upatikanaji. wiki moja ngumu inaonekana hakuna kitu kama muundo endelevu.

Mipangilio ya

Tovuti yako (sehemu za kazi)

Tovuti (kazi) inakuwezesha kusimamia tovuti nyingi kutoka kwa ufungaji mmoja wa OpsIQ. Kila moja ina ufuatiliaji wake mwenyewe, AI, viunganisho, na upatikanaji wa timu.

Maeneo ya Tovuti
Tovuti yakoUkurasa wa tovuti: orodha ya nafasi za kazi, kila mmoja na kikoa chake, aina, kontakt, hali mbaya na kifungo cha wazi, pamoja na Ongeza-new-site.Tovuti yakoNafasi ya KaziTovuti yakoOngeza tovuti mpyaSshop.acme.comBiashara ya eCommerce · Shopify Mawasiliano ya simuKazi ya ActiveKufunguaHhost.acme.comHosting ya · WHMCS Mawasiliano ya simuKazi ya ActiveKufunguaBblog.acme.com· Hakuna mawasiliano ya simuKuundwaKufungua1MULTI-SITESehemu ya kazi kwa tovuti2ISOLATEDData haijawahi kuunganisha3PER-SITEMipangilio ya kibinafsi na unganisho
screen ya tovuti halisi: kila tovuti ni sehemu yake mwenyewe ya pekee (eneo la kibinafsi, kontakt na mipangilio), aliongeza na kufunguliwa kutoka orodha moja.

Kujenga tovuti

1
Nenda kwenye tovuti za kuunganisha

Kuunganishwa kwa maeneo ya kuunganisha.

2
Ongeza tovuti mpya

Ingiza jina, kikoa na maelezo.

3
Kuhamisha tovuti ya Key

Kila tovuti inapata ufunguo wa kipekee (site_xxx) kwa snippet ya widget.

4
Kujiandikisha kwa kujitegemea

Kila tovuti ina AI yake mwenyewe, viunganisho na mipangilio.

Ni tovuti ngapi ninaweza kupata?+

Inategemea mpango wako wa leseni. Angalia maelezo yako ya leseni.

Mipangilio ya

Leseni na mpango

yako ya OpsIQ Udhibiti wa leseni vipengele, mipaka ya tovuti, na usawa wa mkopo wa AI.

Leseni ya leseni
Kituo cha LeseniKituo cha Leseni ya OpsIQ: mpango, badge ya hali ya Active, ufunguo wa leseni iliyofichwa, mita ya kibali cha AI, na kitufe cha ukaguzi wa nguvu.Kituo cha LeseniNafasi ya KaziOpsIQ Kituo cha LeseniMpango wa MpangoBiasharaHali yaKazi ya ActiveKey ya muhimuOPSIQ-••••-••••-2F9CKuwa Credits$68 Kuondoka kwaUfuatiliaji wa Remote1PLAN & STATUSKazi, kwa mtazamo2KEYHMAC-Cookies ya Ndani3CREDITSKiwango cha chini na mipaka
Kituo cha Leseni halisi: mpango wako na hali ya kazi, ufunguo uliofunikwa, usawa wako wa idhini ya AI, na nguvu moja ya bonyeza kuthibitisha tena.
Leseni ya Key

Kuingia katika Settings > License. OpsIQ Huduma ya leseni server.

Kujiandikisha kwa ajili ya usajili / uthibitisho

OpsIQ kawaida kusoma yake saini leseni cache na refreshes uthibitishoation wakati inahitajika. Matumizi ya nguvu kijijini kuangalia wakati unahitaji matokeo ya haraka; Diagnostics kubainisha DNS HTTPS au matatizo ya wakati wa seva.

Mpango wa Mpango

Inaamua upatikanaji na mipaka.

Kiwango cha ukomo wa tovuti

Idadi kubwa ya nafasi za kazi.

Kuwa Credits

Ikiwa unatumia AI iliyosimamiwa, usawa wako wa mkopo unaonyeshwa hapa.

Uendelezaji wa

Kurejea kabla ya kumalizika kwa muda ili kuepuka usumbufu wa huduma.

Nini kinatokea wakati leseni yangu inaisha?+

Kufuatilia, tiketi, na CRM kuendelea. AI makala pause mpaka upya Data ni kuhifadhiwa.

Mipangilio ya

Maelezo ya kibinafsi, nenosiri na uthibitisho wa sababu mbili

Kila msimamizi anaweza kudumisha utambulisho wao wenyewe, mapendekezo ya kazi, nenosiri na uthibitisho wa sababu mbili.

Bidhaa ya Screen
Maelezo yanguUkurasa wa wasifu hutenganisha maelezo ya kibinafsi, lugha / eneo la wakati, avatar / ishara, nenosiri na uthibitishaji wa sababu mbili.Maelezo yanguNafasi ya KaziAhadi yaKukamilikaTIMEZONEUlaya / Athens2FA ya 2FAImewezeshwaMaisha ya kazi ya VIEWJina na barua pepeUtambulisho wa kibinafsiEdith yaLugha na Eneo la TimezoneTarehe na interfaceEdith yaAvatar na sainiMajibu na uwepo wa timuEdith yaNeno la siri na 2FAUlinzi wa AkauntiKuwa salama1UPDATE PROFILEUtambulisho na Utaifa2SECURE LOGINNeno la siri na 2FA3SAVENaomba maelekezo ya hii admin
Ukurasa wa wasifu hutenganisha maelezo ya kibinafsi, lugha / eneo la wakati, avatar / ishara, nenosiri na uthibitishaji wa sababu mbili.

Mipangilio ya wasifu ni ya msimamizi aliyesainiwa na usibadilishe alama ya nafasi ya kazi. Tumia nenosiri la kipekee na kuwezesha uthibitishaji wa sababu mbili. Kubadilisha barua pepe au kuweka uthibitisho kunaweza kuhitaji upya-uhakiki au kuingia kwa ishara mpya.

Mipangilio ya

Mapendekezo ya kutambua

Kuthibitisha upendeleo udhibiti ambayo matukio ya uendeshaji kufikia msimamizi katika bidhaa au kwa barua pepe.

Bidhaa ya Screen
Mapendekezo ya kutambuaUkurasa wa taarifa hutoa kwa kila tukio katika programu na uchaguzi wa barua pepe pamoja na orodha ya hivi karibuni ya arifa.Mapendekezo ya kutambuaNafasi ya KaziIN-APPJuu yaBarua pepeUchaguzi wa kuchaguaUNREAD4Maisha ya kazi ya VIEWTiketi zilizopokelewaKwa kutumia app na emailJuu yaWateja walijibuKwa kutumia AppJuu yaSLA Hatari ya hatariKwa kutumia app na emailJuu yaRuhusa yaKwa kutumia app na emailJuu ya1CHOOSE EVENTSIshara muhimu tu2CHOOSE CHANNELKwa kutumia app au email3Upotoshwaji waTaarifa za hivi karibuni
Ukurasa wa taarifa hutoa kwa kila tukio katika programu na uchaguzi wa barua pepe pamoja na orodha ya hivi karibuni ya arifa.

Mapendekezo ya kufunika tiketi ya kazi, majibu ya wateja, tahadhari za SLA, matukio ya mazungumzo na idhini ya AI. Weka ishara za uendeshaji wa haraka mahali fulani; kuzima barua pepe sio lazima kuacha taarifa ya programu.

Mipangilio ya

Mtazamo wa Usalama

Muhtasari wa Usalama ni skrini ya kwanza ya kutathmini vitalu, mashambulizi ya kuingia, vikao vya tishio, mwenendo wa usalama na uadilifu wa tukio.

Bidhaa ya Screen
Mtazamo wa UsalamaMaelezo ya usalama yanachanganya kadi za hatari za sasa, mwenendo wa siku ya 14-siku, orodha ya washambuliaji, kulisha tukio na hali ya uadilifu.Mtazamo wa UsalamaNafasi ya KaziACTIVE BLOCKS18FAILED LOGINS42HIGH THREAT3Maisha ya kazi ya VIEWAuto-blocked kwa ajili ya7Jumla ya siku na chanzoMwelekeo wa TrendWashambuliaji wa mwishoIP Nchi na sababu zakeMapitio yaMatukio ya UsalamaMatokeo ya Hatari na HatuaChakula cha chakulaHash-chain uadilifuMaonyesho ya wazi ya TukioValid ya1READ HEADLINEUfichuzi wa sasa2OPEN EVIDENCEMashambulizi na matukio3KAZIKuwekeza, kufanya utafiti, kuuza nje
Maelezo ya usalama yanachanganya kadi za hatari za sasa, mwenendo wa siku ya 14-siku, orodha ya washambuliaji, kulisha tukio na hali ya uadilifu.

Matumizi ya kadi kichwa cha habari kwa ajili ya triage, kisha kufungua Audit zinazohusiana, Failed Logins, Kuzuiwa IPs au JavaScript Makosa ukurasa kwa ajili ya kazi rekodi-kiwango. 14-siku mwelekeo ni muhimu zaidi kuliko spike moja. High-tishio vikao lazima uchunguzi dhidi ya mgeni, ombi na ushahidi uthibitishaji kabla kuzuia kudumu ni kutumika.

Mipangilio ya

Ingia ya ukaguzi wa wazi

Kumbukumbu za kumbukumbu ya ukaguzi ambao walifanya nini, wakati gani, kwa kitu gani, katika kiwango cha hatari na ikiwa imefanikiwa.

Bidhaa ya Screen
Ukaguzi wa Shughuli zaUkurasa wa ukaguzi hutoa shughuli za wazi za kuchezewa na hatua, mwigizaji, hatari, lengo na matokeo.Ukaguzi wa Shughuli zaNafasi ya KaziMatukio ya18.2kHIGH RISK21INTEGRITYValid yaMaisha ya kazi ya VIEWKuunganisha Imewezeshwa[email protected] · ShopifyMafanikio ya mafanikioAPI Key ya Kuondolewa[email protected] • Msingi wa msingi 19Mafanikio ya mafanikioMipangilio ya kubadilisha[email protected] · A yaMafanikio ya mafanikioRuhusa ya Kukataliwa[email protected] · Uwekezaji wa njeKufungwa kwa1FILTERHatua, Hatari na mwigizaji2Kutokuwa na uhakikaMalengo na Matokeo3EXPORTCSV au _JSON
Ukurasa wa ukaguzi hutoa shughuli za wazi za kuchezewa na hatua, mwigizaji, hatari, lengo na matokeo.

Chuja kwa hatua, hatari na mwigizaji; kuuza nje CSV au JSON kwa uchunguzi. mnyororo hash husaidia kugundua kukosekana au kubadilishwa safu ukaguzi, lakini haina kuchukua nafasi ya backups ulinzi na upatikanaji database vikwazo. Kutibu mauzo ukaguzi kama nyeti kwa sababu wanaweza kutambua watumiaji, rekodi na hatua za usalama.

Uendeshaji wa Operesheni

Ugonjwa wa zinaa

Maambukizi ya virusi vya ukimwi hugeuza mfumo wa subsystem kuangalia katika matokeo wazi-Kiingereza afya na moja kwa moja hatua zinazofuata.

Bidhaa ya Screen
Ugonjwa wa zinaaMakundi ya utambuzi wa afya hundi kwa widget, AI, tiketi, ushirikiano, Site Intelligence, kazi za background, CRM automatisering, leseni na kuhifadhi.Ugonjwa wa zinaaNafasi ya KaziAfya ya13WARNING2Kushindwa1Maisha ya kazi ya VIEWWidget yaBeacon na chat mwishoAfya ya afyaMajukumu ya msingiMoyo wa marehemuTahadhari ya tahadhariBarua pepeJaribio la nje lilishindwaKushindwaViunganishiUsajili na Tukio la KulipwaAfya ya afya1REFRESHKukagua ukaguzi wa sasa2OPEN WARNINGKusoma ushahidi3FIX AND RETESTKuthibitisha recovery
Makundi ya utambuzi wa afya hundi kwa widget, AI, tiketi, ushirikiano, Site Intelligence, kazi za background, CRM automatisering, leseni na kuhifadhi.

Ukurasa unaangalia kasi ya Site, cheo / neno muhimu / data ya nyuma / ndani, AI na lango la hatua, tiketi, crawler / sauti, ushirikiano / ulaji wa tukio, kazi za background, automatisering CRM, leseni, widget na huduma zinazohusiana. Inaripoti kwa makusudi sababu zinazosoma badala ya kufichua siri mbichi.

Baada ya mabadiliko, Refresh na kuthibitisha subsystem iliyoathirika inarudi afya. ukurasa wa uchunguzi wa kijani ni muhimu lakini haitoshi kwa uzinduzi; kukamilisha orodha ya kabla ya uzinduzi pia.

Mipangilio ya

Usalama na upatikanaji

OpsIQ Inajumuisha tabaka nyingi za usalama kulinda admin yako, data, na API upatikanaji.

Jinsi ya kufanya kazi
Usalama na upatikanajiUlinzi kando ya udhibiti uliowezeshwa: sababu mbili, OIDC SSO, SCIM 2.0 OAuth2 PKCE, CSRF / CSP. IP firewall, mipaka ya kiwango na kuba siri.Sababu mbili (TOTP)OIDC SSOSCIM 2.0OAuth2 PKCECSI + CSP ya kiwango cha juuIP Moto wa firewallKiwango cha ukomoSiri ya Kujificha
Usalama

Vipengele vya Usalama

Usimamizi wa Uthibitishaji

Barua pepe / nenosiri na hiari 2FA.

Ingia kwenye Lockout

Kufungwa kwa muda mfupi baada ya majaribio mengi kushindwa.

IP Kuzuia kuzuia

Block ya block IPs Au, CIDR inaenea kutoka kwenye maeneo yaliyofuatiliwa.

Tishio la

Alama za tishio la tabia. wageni wa juu wathreat wanaweza kuzuiwa auto.

Utekelezaji wa HTTPS

Inahitajika kwa uhusiano wote. HTTP inaelekeza kwenye HTTPS.

Viongozi wa HS

Ubinafsishaji wa vyombo vya habari unazuia mashambulizi ya chini.

Ulinzi wa CSRF

Aina zote za admin ni pamoja na ishara za CSRF.

Ulinzi wa XSS

Kila mtumiaji anaepuka. viongozi wa CSP wanazuia utekelezaji wa script.

Ulinzi wa SSRF

Tovuti za Nje zinazuia binafsi / ndani IP ya mawasiliano.

Kujiandaa kwa ajili ya

1
Kuwezesha 2FA

Kwa akaunti zote za admin.

2
Password ya nguvu

Kiwango cha chini 12 Kwa mfano, mchanganyiko.

3
Ukaguzi wa Hesabu

Kuondolewa kwa wanachama wa zamani wa timu.

4
Ufuatiliaji wa kushindwa logins

Angalia kila wiki kwa ajili ya kubuni.

5
Endelea kuwa updated

Tumia sasisho za haraka kwa patches za usalama.

Mipangilio ya

Majukumu na ruhusa

Udhibiti wa Upatikanaji wa Msingi unakuwezesha kudhibiti kila mwanachama wa timu anaweza kufanya.

Majukumu na ruhusa
Majukumu na ruhusamatrix ya uwezo: Mmiliki ana kila kitu; Msimamizi kamili hana bili na eneo la hatari; Wakala amepanua tu tiketi.Majukumu na ruhusaNafasi ya KaziMaandalizi yaUchoraji waHataritiketiMmiliki wa MmilikiUsimamizi kamiliAgent wascoped13 ROLESMmiliki · Admin kamili · Afisa2GRANULARKwa ukurasa + kwa idara3DEFAULT-DENYBarabara zilizoharibiwa
Jukumu la matrix kwa mtazamo: Mmiliki anapata kila kitu, Full Admin kila kitu lakini bili na eneo hatari, Wakala tu tiketi zao zilizotengwa.

Majukumu ya default

Mmiliki wa Mmiliki

Kila kitu ikiwa ni pamoja na leseni, eneo la hatari, na usimamizi wa ufungaji.

Usimamizi kamili

Kila kitu isipokuwa leseni na eneo la hatari. inaweza kusimamia timu.

Agent wa

Jibu kwa tiketi za sehemu zilizopewa na mazungumzo, angalia analytics. Hakuna mipangilio, timu, au upatikanaji wa usalama.

Ninawezaje kuunda majukumu ya kawaida?+

Si sasa. majukumu matatu kujengwa katika pamoja na kazi idara anatoa granular kudhibiti.

Mipangilio ya

Kufungwa kwa IPs

Usimamizi wa IP Anwani imefungwa kutoka kwa kufikia tovuti zako zilizofuatiliwa.

Kufungwa kwa IPs
Kufungwa kwa IPsLicha ya kufungwa-IPs Picha zote na Wizara ya Mambo ya Ndani...IPFomu yaCIDR kando ya meza ya Anwani zilizozuiwa na kila kuingia, tarehe, sababu na kifungo cha Unblock.Kufungwa kwa IPsNafasi ya KaziKuzuia moja IP Kwa upande wake, Dk.203.0.113.0/24Sababu (kwa kawaida)Block ya blockAnwani zilizozuiwa203.0.113.9Juni 12 · nguvu ya kinyamaUzuiaji wa45.12.0.0/16Juni 10 · spamUzuiaji wa102.89.6.2Juni 9 · unyanyasajiUzuiaji wa1Kufungwa kwaIP Aina ya CDR2LISTNani na wakati gani, kwa sababu3UNBLOCKMoja ya click moja
halisi imezuiliwa IPs skrini: kuzuia moja IP au CIDR mbalimbali, na kusimamia orodha, kila mmoja na tarehe yake, sababu na moja-click unblock.

Jinsi ya kuzuia

1
Kuingia kwenye usalama > imefungwa IPs

2
Ongeza moja IP Aina ya CDR

Mfano: 203.0.113.42 au 203.0.113.0/24

3
Ongeza sababu

Nyaraka kwa nini: spam, unyanyasaji, kupiga, nk.

Je, kuzuia kunaweza kuathiri watumiaji wa halali?+

Kama wateja wana kampuni IP VPN, ambayo inaweza kuzuia IP Tumia kila mtu kwenye tovuti hii.

Mipangilio ya

Kushindwa kwa login

Jaribio lolote la kuingia halikufanikiwa kwako OpsIQ ya admin.

Kushindwa kwa login
Kushindwa kwa loginScreen ya kushindwa: meza ya akaunti /IPs na makosa ya kushindwa, wakati wa jaribio la mwisho, na kifungo cha kuzuia kwa kila mstari.Kushindwa kwa loginNafasi ya KaziJaribio la login halikufanikiwaAkaunti ya benki / IPKushindwaMwisho waHatua[email protected] · 41.62.10.472 ya zamaniBlock ya block[email protected] · 102.89.6.2318 zaidi ya mwaka mmoja uliopitaBlock ya blockWasiojulikana · 45.12.9.71226 zaidi ya mwaka mmoja uliopitaBlock ya block[email protected] · 88.21.4.921h iliyopita iliyopitaBlock ya block1WATCHJaribio la login halikufanikiwa2COUNTSKwa akaunti/ IP3KAZIKuondolewa kwa mstari
screen halisi Failed logins: kila akaunti /IP na kushindwa kuhesabu yake na jaribio la mwisho, kuzuia chanzo brute-nguvu moja kwa moja kutoka mstari.

Nini kila kuingia inaonyesha

Tarehe ya tarehe/time

wakati wa jaribio hilo.

Barua pepe

Email address ya matumizi.

IP Anwani ya anwani

Chanzo cha jaribio hilo.

Nchi ya nchi

eneo la kijiografia.

Sababu ya sababu

Neno la siri, limefungwa au halikupatikana.

Maonyo ya Qur'ani

Baadhi ya majaribio, email moja

Kuwezesha upatikanaji wa nywila. kuhakikisha 2FA inawezeshwa.

Baadhi ya majaribio, barua pepe tofauti

Kushambuliwa kwa gari, kuzuia chanzo IP.

Nchi zisizo za kawaida

Kama timu yako ni ya ndani, majaribio ya kigeni yanaweza kuwa mashambulizi.

Mipangilio ya

Mchambuzi wa Usalama

opt-katika tabaka mchambuzi juu ya kurasa Usalama: hukumu, matukio muhtasari, digest kila siku, kuangalia kila wiki msimamo, Kuuliza Usalama, na 0-token kuzuia sera. Ni kamwe anaendesha katika njia ya ombi wageni.

Kila ukurasa wa usalama unarekodi kilichotokea, lakini kusoma bado inachukua hukumu. Mchambuzi wa usalama wa AI anaongeza kuwa hukumu mahali, na imejengwa kutumia karibu hakuna: haijawahi kukaa katika njia ya beacon au kuingia, sheria za kuamua zinashughulikia kesi zilizo wazi bila wito wa AI, maamuzi ni cached, na pato bora la mchambuzi ni utawala wa uamuzi ambao kisha hutekeleza milele kwa ishara za sifuri. Mipangilio ya Mipangilio→Usalama wa usalamaWote wa default.

Nini cha kuongeza

Jinsi ya kufanya chips + maelezo

Kufungwa kwa IPs Na safu za Ingia zilizoshindwa zinaonyesha chip ya benign / yenye wasiwasi na alama ya ujasiri. Eleza kufungua hoja, ukweli uliotumiwa, na hatua moja-click Block / Release. 24h Kwa hiyo, kwa kuangalia upya IPkuwa huru.

Taarifa ya Matukio

Matukio yanayohusiana na nguzo katika tukio moja (login wimbi, URL skanning, auto-block kupasuka) na mstari wazi wa Kiingereza na hatua moja iliyopendekezwa ijayo. mashambulizi yanayoendelea yanaingia kwenye tukio hilo.

Kila siku ya mapumziko

Recap moja kwa siku: jana dhidi ya msingi wako, vitalu, matukio, na jambo moja la kufanya. Siku za kimya hutuma ujumbe wa makusudi wazi kabisa katika ishara sifuri.

Mapitio ya kila wiki

Jumatatu orodha ya kufanya kazi ngumu (2FA mapungufu, lockout kizingiti dhidi ya kiasi halisi cha shambulio, alerts mbali) na ukali, juhudi na kurekebisha hasa kwa kila kitu.

Kuuliza Usalama

Sanduku la swali kwenye Muhtasari wa Usalama ambao hujibu kutoka kwa hali yako ya usalama wa kuishi. Maswali ya seva ya kina yanakabidhiwa kwa mazungumzo ya mhandisi wa admin badala ya kubahatisha.

Mapendekezo ya sera za + autopilot

Mchambuzi inapendekeza sheria za kuzuia halisi kama kadi za Approve / Dismiss; sheria zilizoidhinishwa kutekeleza ishara za sifuri na counter ya moja kwa moja.

Mipangilio ya

Mchambuzi wa Usalama (security_ai_enabled)

Badilisha Master. Huwezesha chips hukumu, Eleza, na kuuliza Usalama. tu ambiguous IPs kufikia mfano, iliyowekwa katika wito mmoja.

Taarifa ya Matukio (Uhakiki_Asili_Incidents)

Matukio ya kuunganisha katika matukio na kuandika kila hadithi mpya. Huendesha juu ya cron ya usalama wa saa zilizopo.

Mkojo wa kila siku (security_ai_digest)

Usalama mmoja recap kwa siku kwenye kengele na muhtasari. Siku kimya gharama chochote.

Ufuatiliaji wa kila wiki (security_ai_posture)

Jumatatu ngumu orodha juu ya Overview. orodha ni kikamilifu kuamua.

Sera ya Faragha (security_ai_autopilot)

Hebu mchambuzi aamilishe mapendekezo yake salama bila kushughulikiwa: vitalu vya muda mfupi tu, moja IPs au kwa kiwango cha chini kuliko kile kilichopendekezwa. /24, Sijawahi kushiriki / mobile / kibinafsi, imefungwa 10 Kwa muda wa saa, daima hukaguliwa na kuondolewa.

💡
Kila simu ni tagged usalama_ai na cap yake mwenyewe ya kila mwezi katika AI Config → Cost Guardrails (default 300k ishara). Kama cap ni hit, makala degrade kwa deterministic kusoma. kuzuia, lockouts na alerts kamwe hutegemea bajeti hii. Mchambuzi hawezi kamwe kufuta data, mabadiliko mazingira, kugusa kiongo cha ukaguzi, au kufanya marufuku ya kudumu.
Uendeshaji wa Operesheni

Cron na automatisering ya

OpsIQ hutumia ratiba moja ya bidhaa kuendesha uchaguzi wa barua pepe, automatisering ya tiketi, rollups za analytics, uhifadhi, foleni za AI, kazi ya CRM, ripoti na kazi za kontakt.

Bidhaa ya Screen
Cron na automatisering yaBidhaa moja ya kuingia kwa cron hutoa mapigo ya moyo; OpsIQ huamua ni kazi gani za ndani zinastahili.Cron na automatisering yaKiolesura chako cha akaunti na templeti za barua pepe hutumia lugha hii.Afya ya moyoKila dakikaRUNNERcron/all.phpHEALTHMipangilio yaMaisha ya kazi ya VIEWBidhaa ya kipekee yarunneropsiq/cron/all.phpinapohitajikatiketi na barua pepe ya maombiKazi ya muda mfupiKazi ya ActiveAnalytics na Uhifadhicalibre ya ndaniMipango yaKuunganisha WajumbeMatukio ya cronKuonekana1INSTALL ONE LINETumia ratiba ya bidhaa kila dakika2CHECK CRON SETUPKuthibitisha mapigo ya moyo3USE DIAGNOSTICSKuwekeza katika kazi ya mwisho au kushindwa
Bidhaa moja ya kuingia kwa cron hutoa mapigo ya moyo; OpsIQ huamua ni kazi gani za ndani zinastahili.

Bidhaa zinazohitajika kuingia

Ongeza mstari huu mmoja kwa crontab kwa seva moja na mazingira ya PHP ambayo huendesha OpsIQ:

OpsIQ Kuingia kwa bidhaa za crontab
* * * * * php /path/to/opsiq/opsiq/cron/all.php >> /tmp/opsiq-cron.log 2>&1

Kubadilishwa kwa /path/to/opsiq Tumia njia kamili ya PHP CLI wakati mwenyeji anahitaji moja, kwa mfano. /usr/bin/php8.4.

Usiwahi kutumia kiwango cha juu /cron.php kwa ajili ya kazi za bidhaa. Katika kumbukumbu hii kwamba mkimbiaji ni wa huduma tofauti zisizo za bidhaa nje ya kitabu hiki. OpsIQ Mkimbiaji wa bidhaa ni opsiq/cron/all.php.

Nini mpango wa Muungano unatekelezwa

tiketi na tiketi ya ndege

Mchakato kutokana na replies auto, makadirio, idhini na nyingine foleni bidhaa kazi.

Email ya Inbound

Polls configured mailboxes ambapo uchaguzi ni kuchaguliwa ulaji mbinu.

Analytics na vikao

Kugeuza vikao na kurudia mkusanyiko uliopangwa wakati wa.

CRM na Ushirikiano

Inafunga, mzunguko wa maisha, kazi ya kazi, kampeni na majukumu ya ripoti iliyopangwa ambayo yamewezeshwa.

Uendelezaji na Uhifadhi

Hufanya kazi ya kusafisha, nyaraka, expiry na uadilifu.

Viunganishi

Dispatches kontakt wanaounganisha na kupiga kura tu kwa ajili ya kusanikishwa, kuwezeshwa na kusanidi viunganisho.

Kuthibitisha cron

  1. Kufungua Mipangilio ya Cron Setup kuthibitisha kuwa bidhaa hiyo ipo.
  2. Matumizi ya matumizi Sasa kwa Mara moja, kisha kuthibitisha admin na kupiga kura mapigo ya moyo update.
  3. Angalia ukaguzi Ugonjwa wa zinaa Kwa mapigo ya moyo ya mwisho, PHP CLI, database au tatizo la njia ya faili.
  4. Matarajio ya /tmp/opsiq-cron.log Au unaweza kununua mara moja mbegu tayari katika kitalu, basi unapaswa kuwaza kwa usahihi.

Weka vishughulikiaji vya kontakt fupi, idempotent na nafasi ya kazi. synchronizations za muda mrefu za kundi na kuhifadhi mshale / angalia ili kukimbia ijayo inaweza kuendelea salama.

🚫
Wakati bidhaa inaposimama, kazi ya wakati-msingi OpsIQ inaacha au inakuwa marehemu hata ingawa kurasa za kawaida za admin bado zinaweza kupakia.
Uendeshaji wa Operesheni

Shughuli za kupelekwa

Kupelekwa kwa OpsIQ hutumia skrini sawa za bidhaa na kazi wakati mwendeshaji wa mwenyeji anasimamia safu ya seva. ishara ya biashara, mipango, taratibu za malipo na akaunti ziko nje ya kitabu hiki cha mkononi.

Bidhaa ya Screen
Kulipwa kwa kupelekwaMabadiliko ya uendeshaji wa makazi ambayo yanaendelea miundombinu; haibadilishi jinsi wateja hutumia OpsIQ.Kulipwa kwa kupelekwaNafasi ya KaziPRODUCT UIOpsIQ sawaINFRASTRUCTUREUsimamizi wa UendeshajiWORKSPACE DATAIsiyo ya kawaidaMaisha ya kazi ya VIEWMaombi ya kukimbiaPHP, seva ya wavuti na databaseKusimamiwaBidhaa ya cronImeandaliwa na operator wa mwenyejiUkaguziBackups na updatesSera ya Faragha na UshahidiMapitio yaOpsIQ Mipangilio ya mipangilioTovuti, AI, timu na unganishoTimu yako1OPERATE OPSIQ NORMALLYTumia urambazaji wa bidhaa sawa2VERIFY SERVICE HEALTHTumia ushahidi wa utambuzi na hali3KNOW RESPONSIBILITYMipangilio ya bidhaa tofauti kutoka kwa kazi ya mwenyeji
Mabadiliko ya uendeshaji wa makazi ambayo yanaendelea miundombinu; haibadilishi jinsi wateja hutumia OpsIQ.

Nini mmiliki wa mwenyeji kawaida anaweza kufanya

  • Seva ya wavuti, kukimbia kwa PHP, huduma ya database, TLS na kuhifadhi.
  • Bidhaa ya umoja na magogo yake ya ngazi ya seva.
  • Sasisho za maombi, ufuatiliaji wa miundombinu na mchakato wa salama unaofafanuliwa na makubaliano ya mwenyeji.

Nini cha kufanya OpsIQ Hata hivyo, Serikali bado inasimamia

  • Tovuti na ufungaji wa widget, mipangilio ya AI, maarifa, masanduku ya barua na kazi za msaada wa wateja.
  • Upatikanaji wa timu, idara, udhibiti wa usalama, API funguo, kontakt, automatiserings na mipangilio ya data-kuongeza.
  • Uhakikisho wa bidhaa kupitia Diagnostics, logi ya ukaguzi, vipimo vya kontakt na hundi halisi za mwisho hadi mwisho.

Uchunguzi wa utendaji

Usifikiri kuwa huduma iliyosimamiwa inamaanisha kila ujumuishaji wa bidhaa ni afya. kuthibitisha ushahidi wa hivi karibuni na sera ya uhifadhi na mwendeshaji mwenyeji, na kutumia OpsIQ Ugonjwa wa Ukimwi baada ya mabadiliko DNS, barua pepe, watoa AI, tovuti au viunganisho.

Sehemu hii inashughulikia shughuli za bidhaa tu. Biashara ya ndani, usajili, bili na usimamizi wa akaunti ya mteja inabaki nje ya kitabu cha mkono cha OpsIQ.

Uendeshaji wa Operesheni

Kujitoa mwenyewe OpsIQ

Mtu mwenye ubinafsi OpsIQ ufungaji anaendesha juu ya miundombinu wewe kudhibiti. Wewe ni kuwajibika kwa runtime, database, TLS, bidhaa cron, backups, updates na ufuatiliaji.

Bidhaa ya Screen
Kujitoa mwenyeweKumiliki mwenyewe hutoa udhibiti wa miundombinu na hufanya timu yako kuwajibika kwa kila utegemezi wa uendeshaji.Kujitoa mwenyeweKiolesura chako cha akaunti na templeti za barua pepe hutumia lugha hii.PHP8.4+DATABASEMySQL 5.7+SCHEDULERKila dakikaMaisha ya kazi ya VIEWMuda wa nyongezaPicha zote na Wizara ya Mambo ya Ndani ya Nchi. ... jsoninapohitajikaNyongeza yaxml Inafungua, zip, intl, gdinapohitajikaDatabase ya mbadalaMariaDB 10.3+ ya innoDBMsaada waUsafiri wa UsafiriHTTPS na upatikanaji wa mtoa huduma aliye njeUkaguzi1PREPARE THE SERVERMahitaji ya mchezo wa kukimbia2INSTALL AND CONFIGURETumia database ya kujitolea na HTTPS3ADD PRODUCT CRONKuendesha opsiq/cron/all. php
Kumiliki mwenyewe hutoa udhibiti wa miundombinu na hufanya timu yako kuwajibika kwa kila utegemezi wa uendeshaji.

Mkataba wa Software

PHP

PHP 8.4 au mpya. Inahitajika upanuzi: curl, pdo_mysql, mbstring, json, xml, openssl, zip, intl na gd.

Database ya database

MySQL 5.7+ au ya MariaDB 10.3+ kutumia InnoDB. Kujenga database ya kujitolea na mtumiaji mdogo wa maombi.

Mtandao wa server

Apache au Nginx imesanidiwa kwa mtawala wa mbele wa OpsIQ, mali za tuli na zinahitaji kuandika upya.

HTTPS ya

Inahitaji vikao vya admin, trafiki ya widget, API Simu za mkononi, webhooks na huduma.

Upatikanaji wa nje

Ruhusa ya DNS na HTTPS upatikanaji wa AI, barua pepe, kontakt na leseni endpoints wewe kweli kuwezesha.

Upatikanaji wa faili

Watumiaji wa wavuti na CLI lazima waweze kusoma faili za maombi na kuandika tu kwenye maeneo ya kukimbia / kuhifadhi kumbukumbu.

Cron ya

Tumia ratiba ya bidhaa ya OpsIQ kila dakika na usanidi sawa wa programu na upatikanaji wa database kama mchakato wa wavuti.

Ufungaji wa ufungaji

  1. Pakia kutolewa kwa mizizi ya hati iliyokusudiwa na kuhifadhi muundo wa saraka unaotolewa.
  2. Unda database na mtumiaji wa maombi, kisha uingie hifadhidata, mipangilio ya leseni ya Canonical URL.
  3. Tumia mtiririko wa ufungaji / kuweka na kuunda akaunti ya kwanza ya mmiliki.
  4. Kuwezesha HTTPS na kuthibitisha redirects, cookies na widget ya umma /API njia ya kwenda.
  5. Kuongeza umoja OpsIQ Bidhaa ya cron:
Bidhaa za kibinafsi zinazohifadhiwa cron
* * * * * php /path/to/opsiq/opsiq/cron/all.php >> /tmp/opsiq-cron.log 2>&1
  1. Mipangilio ya wazi - Cron Setup na Utambuzi; kukimbia ratiba mara moja na kutatua kila utegemezi ulioshindwa.
  2. Weka Backup, kurejesha upimaji, uhifadhi wa kumbukumbu na taratibu za update kabla ya kuongeza data ya uzalishaji.

Kupumzika kwa usalama

  1. Soma maelezo ya kutolewa na angalia PHP / extensions zinazohitajika kabla ya kubadilisha faili.
  2. Nyuma database na faili za maombi / usanidi, kisha kuthibitisha chelezo inaweza kurejeshwa katika eneo la mtihani.
  3. Tumia faili mpya bila kufuta usanidi maalum wa ufungaji au data ya muda.
  4. Kuendesha mchakato wa uhamiaji / preflight unaotolewa na kuthibitisha kuingia, kufuatilia widget, tiketi, barua pepe, AI, viunganisho na cron.
  5. Weka toleo la awali na salama ya database inapatikana kwa dirisha la kumbukumbu la rollback.
🚫
Orodha ya juu /cron.php Je, si kuwa OpsIQ Uzalishaji wa Bidhaa ya Point Automation tu opsiq Picha zote na Wizara ya Mambo ya Ndani ya Nchi.php
⚠️
Usifute . schema_cache.json kama matengenezo ya kawaida. Ondoa tu wakati maelekezo ya bidhaa yanahitaji wazi muundo wa schema-cache
Uendeshaji wa Operesheni

Mwongozo wa Uzalishaji

Checklists na mazoea bora ya kuendesha OpsIQ katika uzalishaji.

Mwongozo wa Uzalishaji
Mwongozo wa UzalishajiOrodha ya kuishi: uwanja wa desturi na SSL, AI mafunzo, viunganisho na cron, backups na uhifadhi, na majukumu ya timu.Orodha ya kuishiNafasi ya KaziKabla ya kwenda kuishiUtawala wa Domain + SSL ImeundwaMafunzo juu ya maudhui yakoKuingiliana na · cron mbioBackups iliyopangwa · UhifadhiTimu zilizopewa jukumu la kusimamia na kutathmini1GO-LIVEOrodha ya Pre-launch2ya waUwanja · SSL · backups3CONFIDENTWakati wa kupanda ni kijani
Orodha ya kuishi kwa hivyo hakuna kitu kilichokosa: kikoa + SSL, AI iliyofundishwa, viunganisho vilivyojaribiwa na cron, salama na uhifadhi, na majukumu ya timu.

Kabla ya kuishi

HTTPS imeunganishwa

SSL Imesanidiwa, HTTP redirects, HSTS kuwezeshwa.

Cron yaendelea

Angalia kwa njia ya ukurasa wa uchunguzi.

AI kupimwa

Kuzungumza kama mteja, kuthibitisha usahihi na tone.

Widget imewekwa

Katika kurasa zote za wavuti, angalia na Chakula cha Kuishi.

Backup ya Kupakuliwa

Hifadhi ya data ya kila siku na backups za faili.

Makosa ya kufanya

Faili ya makosa ya PHP imewezeshwa na kufuatiliwa.

Timu zilizoalikwa

Kila mwanachama ana akaunti na majukumu sahihi.

Msingi wa ujuzi wa watu

Kwa uchache 5-10 makala ya.

Kila siku: Angalia dashibodi, foleni ya tiketi wazi, mazungumzo ya kuangalia-angalia AI.

Weekly: Mapitio ya AI Insights, update KB, kuangalia utendaji wa timu, ukaguzi wa usalama.

Kila mwezi: Tathmini ya uchambuzi wa mwenendo, viunganisho vya ukaguzi, update mafunzo ya AI, kuthibitisha backups.

Uendeshaji wa Operesheni

Orodha ya Pre-launch

Tumia milango ya chanzo na ukaguzi kamili wa bidhaa kabla ya kutolewa au uzinduzi wa kwanza wa uzalishaji. Amri inapatikana sio ushahidi kwamba ilipita katika mazingira yako.

Bidhaa ya Screen
Uhakiki waMtazamo wa kutolewa unaonyesha malango yanayohitajika kukimbia; hauwatangulizi kama ilivyopitishwa.Uhakiki waKiolesura chako cha akaunti na templeti za barua pepe hutumia lugha hii.Muda waPHP 8.4SOURCE GATESKuendesha nchiOUTCOMEUshahidi wa msingiMaisha ya kazi ya VIEWInahitaji nyongezaAngalia kabla ya chumbaLango la langoPHP syntax ya kufutaFaili zote za PHPLango la langoUchambuzi wa PHPUnitKusubiri wakati wa kuwasiliLango la langoUfuatiliaji wa browser na browserKujiandaa wakati wa kujifunguaLango la lango1RUN THE CHECKSKupata matokeo halisi2FIX EVERY REQUIRED FAILUREUsitoe ushahidi wa uwongo kwa hoja zilizo wazi.3TEST THE PRODUCTKuthibitisha safari halisi ya mtumiaji
Mtazamo wa kutolewa unaonyesha malango yanayohitajika kukimbia; hauwatangulizi kama ilivyopitishwa.

Chanzo na kufungua milango

Tumia hundi za kuhifadhi kutoka mizizi ya ufungaji na kuweka pato lao kamili na rekodi ya kutolewa.

Mlango wa kwanza wa mlango
php tools/preflight.php
Mlango wa Kufunguliwa
php tools/release_gate.php

Preflight hundi PHP 8.4 kukimbia na upanuzi unaohitajika, hufanya kufagia syntax ya PHP, anaendesha lango la meli ya tathmini ya AI na Suite kamili ya PHPUnit, na inaendesha ukaguzi wa PHPStan / Node wakati zana hizo zimewekwa. Lango lililopanuliwa pia ni pamoja na moshi, kufunga-install/schema na ukaguzi wa mwisho wa kivinjari wakati mazingira yao yameundwa.

Rekodi ya kwa nini haipatikani, kufunga utegemezi uliokosekana au kukimbia katika mazingira sahihi ya CI / ishara kabla ya kutolewa.

Ukaguzi wa bidhaa

1Uthibitisho na majukumu

Kuingia kama kila jukumu lililokusudiwa; kuthibitisha kurasa zilizoruhusiwa na kukataliwa / hatua.

2Widget na ufuatiliaji

Load tovuti halisi katika browser binafsi; kuthibitisha trafiki beacon, Live Feed, mgeni na kumbukumbu kikao.

3Chat na ya

Uliza maswali ya mwakilishi; kuthibitisha ujuzi, usalama, kuongezeka na historia ya AI.

4Tiketi ya

Unda, teua, jibu, kuenea, karibu na kufungua kwa kila njia ya ulaji wa kuwezeshwa.

5Barua pepe

Kuthibitisha na kuthibitisha kila kitu katika barua pepe au kwa njia ya mtandao.

6 CRM na uchambuzi

Kujenga mawasiliano ya kudhibitiwa / mpango / ubadilishaji na kuthibitisha dashibodi, funnels, kufunga na ripoti.

7· Mawasiliano ya

Kukimbia vipimo uhusiano, kusoma moja salama kuandika / kukimbia na webhook / poling njia kwa kila kontakt kuwezeshwa.

8. API Mtandao wa Yahoo

Kuthibitisha mawanda nyembamba, mipaka ya kiwango, retries idempotent, saini na utunzaji duplicate.

9Cron ya

Tumia ratiba ya bidhaa iliyoungana na kuthibitisha mapigo yote ya moyo yanayohitajika katika Cron Setup / Diagnostics.

10 Usalama wa

Kuthibitisha 2FA, udhibiti wa CSRF / uchunguzi, kuingia kwa ukaguzi, uondoaji muhimu na kutengwa kwa nafasi ya kazi.

11 Backup na kurejesha

Kurejesha chelezo ya sasa katika mazingira tofauti ya mtihani na kuthibitisha data na usanidi.

12 Ufuatiliaji na Kurudi

Thibitisha kumbukumbu / maneno, kuhifadhi vitambulisho vya ombi na kuthibitisha utaratibu wa kurudi.

⚠️
Kuajiri tu baada ya kila lango na safari muhimu ya biashara ina ushahidi wa sasa wa kutolewa halisi na mazingira.
Developer ya developer

Kuhamasisha mtandao kwenye tovuti za tatu

Kuhamisha taarifa (ikiwa ni pamoja na OpsIQ Kampeni za Push) zinahitaji mfanyakazi wa huduma aliyehudumu kutoka SAME ORIGIN kama ukurasa.OpsIQ Vipeperushi kutoka kwenye uso wako OpsIQ Kujiandikisha, kwa hivyo tovuti ya tatu haiwezi kujiandikisha OpsIQ Mhudumu moja kwa moja. Weka faili moja ndogo kwenye kikoa cha tovuti ili kuwezesha kushinikiza huko. Kampeni hutoa kupitia njia za mkono wa BOTH.

Jinsi ya kufanya kazi
Mtandao wa pushKuarifiwa kwa mtindo wa OS juu ya kadi mbili za njia ya utoaji: Kujengwa katika VAPID na Pusher Beams.Bidhaa yakoGari yako inasubiri 10% Kuondoka kwa leosasaKuundwa kwa ndani (VAPID)Hakuna chama cha tatuKuhamisha faili mojaPusher MiferejiTumia akaunti yakoKuajiri mfanyakazi
Mtandao wa push

Kwa nini hii inahitajika

Browsers tu kuruhusu ukurasa kujiandikisha mfanyakazi huduma kutoka asili yake mwenyewe. widget mizigo msalaba-origin kutoka yako OpsIQ kupelekwa, hivyo haiwezi kufunga mfanyakazi kushinikiza kwenye tovuti ya mteja, mpaka wewe mwenyeji wa mfanyakazi juu ya asili ya tovuti hiyo, widget huruka kimya kushinikiza (hakuna kosa, hakuna usajili). Una chaguzi mbili hapa chini;OpsIQ Kampeni za uchaguzi zinaendeshwa kwa njia zote mbili.

Chaguo A · Kujiandaa kwa Mtandao (VAPID, hakuna mtu wa tatu)

1. Download kazi kutoka kwa mikono yako OpsIQ Uwasilishaji: https://YOUR-OPSIQ/opsiq/opsiq-push-sw.js

2. Ongeza kwenye yako Mtandao wa mizizi Hivyo basi, ni lazima kuwa na https://yoursite.com/opsiq-push-sw.js- Wizi wa widget Kujiandaa kwa njia hii kwenye asili ya ukurasa mwenyewe na hujiandikisha, hakuna mabadiliko ya snippet inahitajika. (Inatumia wigo mdogo, kwa hivyo haibadilishi mfanyakazi wa huduma ambaye tayari unakimbia.)

Chaguo la: Ikiwa unahitaji kuingia kwenye njia isiyo ya kawaida, bonyeza widget ndani yake Kabla ya kabla ya kabla ya Ni tu kukubalika wakati sawa-origin:

Chaguo · Tu ikiwa faili haipo kwenye mizizi ya wavuti
<script>window.OpsIQ=window.OpsIQ||{};window.OpsIQ.pushSwUrl="/custom/opsiq-push-sw.js";</script>

3. Katika OpsIQ, kuzalisha funguo za VAPID (Mipangilio → Mteja Chat AI → Advanced → Mtandao Push). widget kisha anauliza wageni kwa ruhusa ya taarifa na kujiunga nao.

Nyuma ya CDN /Cloudflare Kuwa na uhakika /opsiq-push-sw.js Kurudi kwa HTTP 200 (Kama ingekuwa gerezani, basi 404 Kabla ya kutunuku Kamisheni Mhe.404 itazuia usajili).

Chaguo B · Pusher Beams (Mtoaji aliyesimamiwa)

1. Ndani ya OpsIQ Watangazaji wa promosheni hiyo Pusher Mifereji Kuingia kwa akaunti yako Utambulisho wa ID Na kwa kuwa Siri ya siri.

2. Kuwakaribisha wafanyakazi wa huduma ya Beams kwenye mizizi ya tovuti kama /service-worker.jsNakala ya nakala https://YOUR-OPSIQ/opsiq/pusher-beams-service-worker.jsAu kuunganisha mstari huu katika mfanyakazi wako wa mizizi iliyopo:

Wafanyakazi wa Beams, mwenyeji katika https://yoursite.com/service-worker.js
importScripts("https://js.pusher.com/beams/service-worker.js");

3. Hiyo ni. widget auto-loads Beams SDK na inajiunga kila mgeni kwa maslahi ya tovuti opsiq-site-<your-site-key>Hakuna aina nyingine ya udongo inahitajika.

Jinsi kampeni zinavyoendeshwa

Kampeni za uchaguzi zinaendeshwa kupitia wawili hao wawili wawili Njia mara moja: wageni kwenye mfanyakazi wa VAPID aliyehifadhiwa hupata Push ya Mtandao iliyofichwa, na wageni waliosajiliwa kupitia Pusher Beams wanapata BeamS kuchapisha. Kila mgeni anafikia kwa njia yoyote aliyojiunga nayo, ili uweze kukimbia VAP ID sawa ya asili kwenye tovuti zingine na Beginams za msalaba kwa wengine.

HTTPS inahitajika Kwa wafanyakazi wa huduma na Push Web (localhost ni msamaha kwa ajili ya kupima). Kabrasha la mazungumzo ya admin tayari hutumia utaratibu sawa wa riba ya Beams kwa tahadhari za operator.

Uendeshaji wa Operesheni

Matatizo ya Kutatua

masuala ya kawaida na jinsi ya kuyashughulikia.

Jenerali Mkuu

Ukurasa wa+

Angalia kumbukumbu za kosa la PHP. Sababu: PHP ya zamani (haja ya 8.4+), upanuzi wakosekana, uunganisho wa DB umeshindwa, ruhusa za faili zisizo sahihi.

Dashibodi ya kuonyesha zeros+

Angalia: widget imewekwa? Cron kukimbia? tarehe mbalimbali sahihi. IP Kuondolewa?

I

A. Hakujibu+

Angalia: mtoa huduma amesanidiwa? API ufunguo halali (kutumia uunganisho wa mtihani)? Bajeti imechoka?

Atoa majibu ya uongo+

Angalia: maarifa msingi hadi tarehe? haraka wazi? Kuunganisha kuangalia nyuma data sahihi? Tathmini mazungumzo katika historia ya AI.

Kuwa mwepesi+

Inategemea: mtoa huduma API kasi, ukubwa wa muktadha (large KB = ishara zaidi = polepole), latency ya mtandao.

Ufuatiliaji wa kufuatilia

Widget ya missing+

Angalia: script katika chanzo cha ukurasa? makosa ya JS katika console? CSP kuzuia?

Nchi isiyojulikana+

GeoIP si configured. Matumizi Cloudflare (kiotomatiki) au MaxMind GeoLite2 database.

Tiketi za tiketi

Emails si kuunda tiketi+

Angalia: mailbox kushikamana? Cron kuendesha password ya programu iliyopita. IMAP Je, ni sahihi?

Kazi ya Auto-Haifanyi kazi+

Angalia: Idara iliruhusu? AI imesanidiwa? Cron anaendesha? Binadamu alijibu kwanza.

Viunganishi

Uhusiano wa kushindwa+

Wakili: Je, nyaraka za siri zilifutwa? API Uwezo wa kutumia server? msingi URL sahihi?

Kuunganishwa lakini hakuna data+

Angalia: API mawanda muhimu? Webhook sync enabled? Cron kukimbia?

Utendaji wa utendaji

Ukurasa wa polepole+

Angalia: utendaji wa database (SHOW PROCESSLIST), kumbukumbu ya PHP (kuongeza kwa 1GB), kuwezesha opcache, kupunguza kipindi cha uhifadhi.

Uendeshaji wa Operesheni

Wiget si ziara ya magogo

Tumia hii kuangalia umakini wakati widget mizigo kimakosa au Live Feed anakaa tupu.

Wakati wa Wizi wa magogo sio ziara za magogo, kuthibitisha ufunguo wa tovuti, kupakia ukurasa katika kivinjari cha kibinafsi, angalia paneli za mtandao wa kivinjari / console kwa maombi ya kuzuia beacon au widget, ukaguzi wa Maudhui-Security-Policy na blockers ya matangazo, kuthibitisha kuwa tovuti hiyo inafanya kazi katika OpsIQ, na Utambuzi wazi. Bubble inayoonekana ya kuzungumza haithibitishi yenyewe kwamba kiashiria cha uchambuzi kilikubaliwa.

Marejeo ya kumbukumbu

Kwa ujumla, gloria

Ufafanuzi wa maneno yanayotumika wakati wote OpsIQ.

Hatua ya hatua

Kitu ambacho AI inaweza kufanya kupitia kontakt au jukwaa.

Agent wa

Mwanachama wa timu yenye upatikanaji mdogo, au wakala wa AI.

BYOK

Kuwasilisha yako mwenyewe, wewe kutoa mwenyewe API ya muhimu.

Mawasiliano ya

Plugin inayounganisha jukwaa la nje na OpsIQ.

CSAT ya CSAT

Matokeo ya kuridhisha kwa wateja.

Mkataba wa

Fursa ya mapato katika CRM.

Idara ya Idara ya Idara

Aina ya tiketi kwa ajili ya uendeshaji na upatikanaji wa udhibiti.

Uendelezaji wa

Kuhamisha tiketi kwenda idara tofauti au kutoka AI hadi kwa binadamu.

GeoIP

Utambuzi wa eneo la kutembelea kutoka IP Anwani ya.

Handy ya

Kuhamisha mazungumzo kutoka kwa mtu hadi mtu.

Utambulisho wa utambulisho

Ishara iliyosainiwa kutambua mgeni wa tovuti.

Msingi wa ujuzi

Makala ambayo AI hutumia kujibu maswali.

Kiongozi wa

Mgeni rasmi akionesha nia ya kununua

Matokeo ya alama

0-100 Idadi inayoonyesha uwezekano wa kubadilika.

Maisha ya Stage

Ambapo mteja ni: Kiongozi, matarajio, Wateja, Hatari, Churned.

AI Iliyosimamiwa

Kama sehemu ya kazi yako, OpsIQ mpango.

Bomba la mafuta

Visual ya hatua za mpango.

RBAC ya

Udhibiti wa Upatikanaji wa Msingi.

Mkutano wa

Baadhi ya maoni ya ukurasa ndani ya dirisha la muda.

Tovuti ya Key

Kitambulisho cha kipekee kwa tovuti iliyofuatiliwa.

SLA

Mkataba wa kiwango cha huduma, nyakati za majibu ya lengo.

Toni ya

Kwa mfano, katika sehemu ya maandishi ya AI. 4 Wahusika = 1 ya wa.

Uhakiki wa dhana

Mfumo wa usalama unadhibiti uhuru wa AI.

Mtandao wa Yahoo

HTTP Callback kwa taarifa za tukio.

Widget ya

JavaScript msimbo ulioingizwa kwenye tovuti yako.

Nafasi ya Kazi

Tovuti yenye ufuatiliaji wake mwenyewe, AI, viunganisho, na timu. sawa kama "tovuti."

Marejeo ya kumbukumbu

Kupata msaada zaidi

Ikiwa nyaraka hizi hazijibu swali lako:

Usimamizi wa AI

Bonyeza "Kuuliza"OpsIQ"Katika admin. ina upatikanaji wa nyaraka hii na data yako jukwaa.

tiketi ya msaada

Sema: Kilicho chepesi, na kiogopa kuwa hamwezi kufanya uadilifu, basi mmoja tu.

Barua pepe

Msaada wa barua pepe na maelezo yako ya leseni muhimu na kutoa maelezo.

Tips kwa ajili ya maombi ya msaada wa ufanisi

Ongeza ukurasa

Ukurasa wa admin (URL jina la mtumiaji).

Ni pamoja na kuweka

Jina la kikoa na thamani ya sasa.

Kuthibitisha makosa

Tumia ujumbe wa makosa kwa kutumia codes.

Kujumuisha hatua

Chochote unachofanya, fanya hatua kwa hatua.

Kutarajia vs halisi

Nini cha kufanya na nini kilichotokea.

💡
Kwa maelezo zaidi, jibu la haraka: "Haifanyi kazi" inahitaji uchunguzi. "Clicking Save on AI Configuration inatoa msimbo wa makosa 502" inapata jibu moja kwa moja.