{"accent":"Accent","active":"Active","analyticsNavDesc":"Dashboards, ad-hoc queries, insights","analyticsNavLabel":"Analytics","analyticsTry1":"Merge Wildberries and Ozon sales for [period] and compare with [the previous period / the same period\nlast year].\nFor each marketplace, category and SKU show revenue, orders, average order value and returns.\nBreak every decline down into factors: order count fell, selling price fell\nor returns grew — and show each factor's contribution in rubles.\nDon't explain a decline by \"falling demand\" or \"seasonality\" until you show a figure that\nconfirms it. If an item didn't sell because it was out of stock, say exactly that —\nthat isn't a demand decline.\nOutput a SKU table sorted by lost revenue, and the ten items\nthat account for half of the decline.","analyticsTry2":"Build a revenue dashboard in Google Sheets by channel [Ozon / Wildberries / others — list them]\nand refresh it [every Monday morning].\nOverwrite the \"Data\" sheet in full, don't touch the charts sheet — it references \"Data\".\nDon't wipe the history of previous weeks: each week is its own row.\nIf a source didn't respond or returned an obviously incomplete period — don't substitute a zero and don't carry\nthe previous week over. Leave the cell empty, put the week into a \"Gaps\" sheet with the reason\nand mention it in the update message.\nAfter every run send a short summary: what was refreshed, which channels didn't come through,\nand the revenue change versus the previous week in one line.","analyticsTry3":"Analyze Wildberries returns for [period] and compare with [the previous period].\nCalculate the return rate against orders for each SKU, category and warehouse. Break it down by the reasons\nfrom the marketplace report; keep defects, \"wrong size\" and \"doesn't match the description\" separate —\nthose are different areas of responsibility.\nDon't explain growth by seasonality until you show the same happened last year. If there is no data\nfor last year, say so.\nSingle out SKUs where the return rate is more than one and a half times the category average, and estimate\nthe losses including logistics.\nOutput a SKU table and the five items to start with.","analyticsTry4":"Merge sales from 1C, Bitrix24, Ozon and Wildberries for [period] into a single table.\nMatch items by [SKU / barcode / the attached mapping reference],\nnot by name. Bring units of measure and currency to a single form, and fix whether we count\nrevenue with or without VAT.\nRemove duplicates: one shipment that landed both in 1C and in the CRM as a deal is one row.\nIf an item didn't match, or matched only on a similar name — don't merge it by eye,\nmove it to a \"Not matched\" sheet with the candidate options.\nOutput an XLSX: a \"Sales\" sheet broken down as date — channel — unified SKU — quantity — amount,\na \"Not matched\" sheet and a \"Mapping reference\" sheet that I can extend.","analyticsTry5":"Calculate margin by SKU by week for [period] using Ozon and Wildberries sales\nand cost of goods from 1C.\nFor each week break the selling price down into marketplace commission, logistics, discounts and promos,\nand cost of goods. Find SKUs whose margin deviated from their own average for the period by more\nthan [threshold].\nFor every deviation name the factor with a figure: how many rubles came from the increased commission,\nhow many from the discount, how many from purchase cost. Don't name a cause if the breakdown doesn't show it —\nwrite \"factor not determined\".\nTake cost of goods as of the shipment date. Where it's missing, don't substitute the category average,\nmove the SKU into a \"no cost of goods\" list.\nOutput a table by SKU and week and the top deviations in rubles.","analyticsTry6":"Compare [month] with [the previous month] across Ozon, Wildberries and 1C sales.\nShow revenue, order count, average order value and returns — in total, by channel and by category.\nFor each row give the change in rubles and in percent and state what produced it:\nmore orders or a higher average order value.\nList separately everything that makes the months non-comparable: a different number of working days,\nmarketplace promos, a large one-off order, unsettled returns. Show large one-off deals\nboth in the total figure and as a separate \"excluding one-offs\" line.\nCount revenue by [shipment / payment] — the same way for both months.\nOutput a comparison table and the five categories that drove most of the change.","analyticsTry7":"Calculate the sales funnel from [Bitrix24 / amoCRM] data for [period] and compare with [the previous\nperiod].\nFor each stage: how many deals entered, how many moved on, the conversion into the next stage\nand the end-to-end conversion from the first stage, the mean and median time in status.\nCount from the transition history, not from the deal's current status. Show deals that skipped a stage\non a separate line rather than spreading them across the adjacent ones.\nDon't give a list of specific deals or recommendations on them — only figures and the differences between periods.\nIf a stage has fewer than [30] deals, mark its conversion as unreliable and don't draw conclusions from it.\nOutput a table by stage with the two periods side by side and the three stages with the largest conversion\ndrop.","analyticsTry8":"Calculate ad cost share for every campaign for [period]: Yandex Direct and the ad dashboards\nof Ozon and Wildberries.\nFor each campaign: spend, revenue by the dashboard's attribution, ad cost share, order count, average order value.\nWithin a single platform use one attribution model and state which one. Don't add up revenue\nfrom different dashboards for the same order — that's double counting.\nIf a campaign's revenue can't be tied to its spend, move it into \"attribution not determined\"\nrather than crediting it with the category's overall sales.\nSeparate campaigns with an ad cost share above [target] from those with too little data for a conclusion: at spend below\n[threshold] or fewer than [20] orders, mark the row as unreliable.\nOutput a table of campaigns in descending order of spend and a bottom line: how much budget went into campaigns\nwith an ad cost share above target.","appLockPromptTitle":"Verify it's you","appLockUsePasscode":"Use passcode","billingRenewal":"Renews {date}","billingRenewalExternal":"Renews {date} on the {provider} side","bookDemoNavDesc":"See the product on your own tasks","businessHeroTitle":"One AI agent for the whole team","businessNavOverview":"Samreshuuu for business","businessNavOverviewDesc":"One AI agent for the whole team","cancel":"Cancel","canceledNoMoreCharges":"No more charges — access until {date}","compareCellExpandedPerSeat":"Same as the plan, per paid seat","compareCellImagesFree":"Up to 3","compareCellImagesMax":"Up to 75 — 2.5× Pro","compareCellImagesPro":"Up to 30","compareCellPerPlan":"Same as the chosen plan","compareCellRequestsMax":"Up to 160 — 4× Pro","compareCellTasksFree":"Up to 5","compareCellTasksPro":"Up to 40","compareCellVideoMax":"Up to 15","compareHubEyebrow":"Comparisons","compareRowAudit":"Audit log","compareRowBilling":"Unified billing","compareRowCRM":"CRM and marketplaces","compareRowDailyTasks":"Requests per day","compareRowDocs":"Document generation","compareRowDrive":"Shared team drive","compareRowEmailSupport":"Email support","compareRowImages":"Images per day","compareRowLegal":"Legal database","compareRowMemory":"Memory of projects and clients","compareRowPriorityQueue":"Priority queue","compareRowRefund":"Refund for unused","compareRowRoles":"Roles and access","compareRowSandbox":"Calculations and table analysis","compareRowSchedule":"Scheduled tasks and triggers","compareRowSeats":"Up to {maxSeats} seats","compareRowTGSupport":"Priority Telegram support","compareRowVideo":"Videos per month","compareRowWeb":"Web search","compareSectionGeneration":"Content generation","compareSectionIntegrations":"Integrations and tools","compareSectionSupport":"Support","compareSectionTeam":"Team features","compareSectionUsage":"Usage","connectorAccessToken":"Access token","connectorAddCustomApi":"Add API","connectorAddInstance":"Add another","connectorAddKeyValue":"Add","connectorAddMcpServer":"Add server","connectorAddSecret":"Add secret","connectorAlfaBankApiKey":"API Key","connectorAlfaBankCert":"Client certificate","connectorAlfaBankKey":"Certificate private key","connectorAlfabankConnectHint":"You need a settlement account and Alfa-Business Online. Email the request to alfa_api@alfabank.ru; the ITV agreement is signed by the director in Alfa-Business Online. Then openssl req -new -key name.key -out name.csr: the bank returns the certificate in PEM, and name.key stays with you only. The production key for baas.alfabank.ru comes after the Sandbox and the “Завершено тестирование” email.","connectorAmoCRMAuthCode":"Authorization code","connectorAmoCRMClientId":"Integration Client ID","connectorAmoCRMClientSecret":"Integration Client Secret","connectorAmoCRMDomain":"Account domain","connectorAmoCRMSubdomain":"AmoCRM subdomain","connectorAmocrmConnectHint":"Settings → Integrations → Create integration → external integration, as an account administrator. Put your account's own address in the redirect link — https://<subdomain>.amocrm.ru for Russian accounts, https://<subdomain>.kommo.com for Kommo — and enter the same domain in «Account domain», otherwise OAuth rejects the redirect and keep leads, contacts, companies and tasks in the Allow access block. On the Keys and scopes tab take the ID, the secret key (shown only once) and the authorization code starting with def502 — it lives 20 minutes, copy it last.","connectorAnonGateBody":"Connecting needs an account. Signing up is free and takes 20 seconds — we'll bring you back here and open the connection.","connectorApiKey":"API Key","connectorApiSalt":"API Salt","connectorApiSecret":"API Secret","connectorApiToken":"API Token","connectorApifyConnectHint":"console.apify.com → Settings → «API & Integrations» → the personal API token: the value is hidden and reveals on click. Copy the string with no spaces at the edges — one extra character gives an unauthorized error. There is one token per account. The free plan gives $5 of usage a month with no card and 25 concurrent runs. The agent runs a scraper by its name from the Apify Store, like apify~instagram-hashtag-scraper.","connectorAppPassword":"App Password","connectorAppmetricaConnectHint":"Sign in at appmetrica.yandex.ru with the Yandex ID that sees the app in its list — the confirmation code goes under the same account. If the app is missing, ask the owner to add your email under “Access management”: “Read only” for reports, “Read/edit” for settings and push campaigns. “Agency: read” exposes only selected sources and events, so the summary comes out incomplete.","connectorApps":"Apps","connectorAtiSuConnectHint":"Developer portal ati.su/developers/tokens/ → “Мои токены” (My tokens). For a trial run the “Создать временный токен” button is enough: it comes from the api-panda-portal application and lives 7 days. For permanent work request a client_id at api@ati.su — employee name and email, product name, purpose — then enter it and press “Создать токен”. Copy the value from the Token column.","connectorAuthToken":"Auth Token","connectorAvitoClientId":"Client ID","connectorAvitoClientSecret":"Client Secret","connectorAvitoConnectHint":"Avito account: «Управление профилем» → «Настройки» → «Интеграции» (direct address avito.ru/professionals/api) → «Получить ключи» (Get keys). Keys are issued only on an account with a paid plan and work only for the account that issued them, so sign in under the one holding your listings. A Client ID and Client secret pair appears; if empty, reload after a minute. The pair stays in the section and can be copied again.","connectorBaseUrl":"1C base URL","connectorBeelineCloudpbxConnectHint":"Cloud PBX account at cloudpbx.beeline.ru → «Настройки» (Settings) → the «API» tab → the «Интеграция по API» switch. The add-on is paid, 500 RUB per month incl. VAT, and nothing goes through while it is off. Take the «логин» + «пароль» pair for external-system integration, not the portal token; if the tab has no pair, ask your account manager or vassupport@beeline.ru.","connectorBeforeYouConnect":"Check this before connecting","connectorBetterstackConnectHint":"Better Stack dashboard → «API tokens». Only the Admin role can open it — Team lead, Responder and Member cannot create a token. Under «Team-based tokens» pick the team and copy the value from the «Uptime API tokens» block: it only sees that team's monitors, so for several teams take a «Global API token». It is a Bearer token for https://uptime.betterstack.com/api/v2.","connectorBitrixConnectHint":"\"Applications → Developer resources\", the \"Ready-made scenarios\" tab → \"Other\" → \"Incoming webhook\". CRM alone is enough to read the funnel; add \"Tasks\" to create tasks and move deals. You need a link shaped like https://<your-domain>.bitrix24.com/rest/1/<secret code>/ — with a trailing slash and no method name. A webhook runs with the creator's permissions, and the REST API is closed on the free plan.","connectorBitrixInboundWebhookUrl":"Inbound Webhook URL","connectorBotToken":"Bot token","connectorBoxId":"Box ID","connectorBpmsoftConnectHint":"Server address — from your BPMSoft address bar up to the first slash (https://crm.company.ru). Login and password — of a dedicated user: System Designer → «Пользователи и администрирование» → «Пользователи системы» → «Добавить пользователя», type «Сотрудник компании». Tick a license on the «Лицензии» tab, otherwise sign-in is rejected. Then grant the «Доступ к OData» operation under «Права доступа на операции».","connectorBrandAnalyticsConnectHint":"Brand Analytics cabinet → «Настройки» (Settings) → «Интеграции» (Integrations) → «Статистический API» (Statistical API) → «Подключить» (Connect). You need «Администратор» or «Супер Администратор» rights and the «Расширенный» plan or higher, otherwise the item is missing. Tick «Интеграция активна», save, copy the API key. Data is per topic: with no monitoring topic the reply is empty.","connectorBybitConnectHint":"Bybit account → «API Management» (www.bybit.com/app/user/api-management) → «Create New Key» → «System-generated API Keys»: an RSA key will not work, requests are signed with HMAC-SHA256. «Read-Only» covers balances, positions, orders and history; the Wallet permission group is not needed. With no IP whitelist the key expires after 90 days. Copy the API Key and Secret right after creation.","connectorCdekConnectHint":"Cabinet at lk.cdek.ru → «Интеграция» (Integration) → «Создать новый ключ». API access is granted only under a contract with a company or sole proprietor; without one the section is absent. Copy the Account (the client_id) and the Secure password (the client_secret) — the Secure password is shown only once at creation, and a lost one means issuing a new key.","connectorCertChooseFile":"Choose file","connectorCertLoaded":"File loaded","connectorCertReadFailed":"Could not read the file","connectorCertTooLarge":"File is over 64 KB — that is not a certificate","connectorChat2deskApiToken":"API Token","connectorChat2deskConnectHint":"chat2desk.com → Settings → API and scripts → API. The section is visible to the account administrator only — operators and supervisors do not see it. Click Show and copy the whole string, without surrounding spaces and with no Bearer prefix; a channel token (Telegram, for example) will not work. The same page shows what is left of the 100,000 monthly requests, and generating a new token invalidates the previous one.","connectorChestnyznakConnectHint":"Sign in to the marking cabinet with your УКЭП, then click your user name in the top right corner → «Профиль» → the «Данные участника» tab → the «Участие в системе» block → «Сгенерировать токен». The product group you trade in must be added there via «Редактировать». The value is a long string of three dot-separated parts; the field empties after a page refresh, so copy it at once.","connectorClearFilters":"Reset","connectorClientId":"Client ID","connectorClientSecret":"Client Secret","connectorConnect":"Connect","connectorConnectSlow":"Checking the connection… the provider is responding slowly","connectorConnectSuccess":"{service} connected successfully","connectorConnectTimeout":"The service didn't respond in time. Please try again.","connectorConnectTitle":"Connect {service}","connectorConnectUnverifiedBody":"The key was saved, but we couldn't verify it — the provider didn't respond. If the integration doesn't work, check the key and reconnect.","connectorConnectUnverifiedTitle":"{service}: key saved","connectorConnectWebhookUnavailable":"{service} connected — events unavailable","connectorConnected":"Connected","connectorCreateSkill":"Create skill","connectorCreateSkillDescription":"A skill provides detailed instructions for the assistant on how to work with this API","connectorCreateSkillPrompt":"Create a skill for this connector?","connectorCreatomateConnectHint":"Creatomate dashboard → pick the project → «Project Settings» → the «API Key» field: the value is hidden and reveals on click. Each project has its own key, and a neighbouring one returns someone else's template list. An empty project returns an empty list, so create at least one template in the editor. The API works on every plan; the free trial is 50 credits with no card.","connectorCredentialsSection":"Connected keys","connectorCustomApiBaseUrl":"Base URL","connectorCustomApiDescription":"Connect third-party services via their API to extend assistant capabilities","connectorCustomApiName":"Name","connectorCustomMcpDescription":"Connect MCP servers to extend assistant capabilities","connectorDadataApiKey":"API Key (Token)","connectorDadataApiSecret":"Secret Key","connectorDadataConnectHint":"Register at dadata.ru and confirm your email — the keys are generated automatically. Both sit in the profile at dadata.ru/profile/#info, side by side: copy the API key and the secret key. The secret one is required by «Стандартизация» (Standardization), billed separately at 20 kopecks per address; lookups by INN and OGRN are free within 10,000 requests per day.","connectorDataSection":"Connection data","connectorDbAnalyzeCta":"Analyze","connectorDbAnalyzePrefill":"I connected a PostgreSQL database. Show me what tables it has and suggest 3–5 useful reports over this data.","connectorDbHost":"Host","connectorDbHostHint":"Database address without a protocol, e.g. db.xxxx.supabase.co (Supabase pooler: aws-0-….pooler.supabase.com).","connectorDbName":"Database","connectorDbPort":"Port","connectorDbPortHint":"Direct connection — 5432, pooler (Supabase/Neon) — 6543.","connectorDbSslmode":"SSL mode","connectorDbSslmodeHint":"require works for cloud databases (Supabase, Neon, RDS, Yandex Cloud). verify-full — when you need CA-chain verification.","connectorDbUserHint":"Database user, e.g. postgres (Supabase pooler: postgres.<ref>).","connectorDiadocConnectHint":"diadoc.ru/integrations/api → integration request: a manager opens the Integrator Cabinet and issues client_id, and client_secret is issued there too. Get the token via OpenID Connect with scope «openid profile email offline_access Diadoc.PublicAPI» — without Diadoc.PublicAPI the production API rejects it. The box id is the 32 characters between https://diadoc.kontur.ru/ and /Folder/Inbox.","connectorDisconnect":"Disconnect","connectorDisconnectConfirm":"Disconnect {service}?","connectorDisconnectDescription":"Assistant will lose access to this service","connectorDisconnectSuccess":"{service} disconnected","connectorDisconnected":"Disconnected","connectorEditCredentials":"Edit credentials","connectorEditCustomApi":"Edit Custom API","connectorEmail":"Email","connectorExpandTitle":"Expand access to {service}","connectorFieldDefault":"Default: {value}","connectorFillAllFields":"Fill in all fields","connectorFullGuide":"Step-by-step guide","connectorGenerateWebhook":"Generate Webhook URL","connectorGitHubOAuthButton":"Connect via GitHub","connectorGitHubOAuthError":"Failed to connect GitHub. Please try again","connectorGitHubOAuthPopupBlocked":"Browser blocked the popup. Allow popups and try again","connectorGitHubOAuthWaiting":"Waiting for GitHub authorization...","connectorGithubConnectHint":"Sign in with the account that has access to the repositories you need. In an organization only an owner can install the app — a member can only send \"Install and request\"; with SAML SSO start a session at github.com/orgs/ORG/sso first, or the organization will not be listed. At install pick \"All repositories\" or \"Only select repositories\" — the agent works only with those, and you can widen access later via \"Configure\".","connectorGitlabConnectHint":"Avatar → «Edit profile» → «Access» → «Personal access tokens», then pick «Legacy token» from the «Generate token» list. Tick the «api» scope: «read_api» leaves read-only. Expiry is mandatory, 365 days by default, and the glpat-… token is shown only once. Address is https://gitlab.com or your own instance root without /api/v4. A token never exceeds your account's own permissions.","connectorGitlabUrl":"GitLab server URL","connectorGoogleCalendarConnectHint":"Sign in to the Google account you actually run your meetings from — only calendars on its left-hand list are visible. Subscribe to a colleague's calendar first: «Other calendars» → «Subscribe to calendar». For the agent to edit and not just read, the owner sets «Make changes to events» in «Settings and sharing» → «Shared with». On a corporate domain the app may be blocked under «API controls».","connectorGoogleCalendarOAuthError":"Failed to connect Google Calendar. Please try again","connectorGoogleDocsConnectHint":"Sign in with the Google account that already has access to your working documents — access is granted to the active account. On each document click «Share» and set that account to «Editor»: with «Viewer» or «Commenter» edits are rejected. Keep links shaped like https://docs.google.com/document/d/DOCUMENT_ID/edit at hand — there is no search by title. In Google Workspace an admin unblocks third-party apps.","connectorGoogleDocsOAuthError":"Failed to connect Google Docs. Please try again","connectorGoogleOAuthButton":"Connect via Google","connectorGoogleOAuthPopupBlocked":"Browser blocked the popup. Allow popups and try again","connectorGoogleOAuthWaiting":"Waiting for Google authorization...","connectorGoogleSheetsConnectHint":"Open sheets.google.com under the account that holds the files. For someone else's spreadsheets ask for “Share” with the “Editor” role: with “Viewer” writing cells will fail. An uploaded .xlsx is not readable over the API — use “File” → “Save as Google Sheets”. In a corporate domain an admin marks the app “Trusted” under “Security” → “Access and data control” → “API controls”.","connectorGoogleSheetsOAuthError":"Failed to connect Google Sheets. Please try again","connectorGoogleSlidesConnectHint":"Sign in with the account that owns the decks — the connection sees this account only. For someone else's deck the owner grants your address the “Editor” role via “Share”; with “Viewer” the agent can only read the slides. Keep the link https://docs.google.com/presentation/d/…/edit at hand: the access does not include Google Drive, so a deck cannot be found by name. In Workspace sign-in can be blocked by policy — the admin needs “API controls”.","connectorGoogleSlidesOAuthError":"Failed to connect Google Slides. Please try again","connectorGravitelConnectHint":"PBX cabinet → «Интеграции» → «Интеграция по REST API» → «Установить», then «Настройки» → the «Авторизация» subsection. The «Адрес вашей CRM» and «Ключ для авторизации в Вашей CRM» fields are the reverse direction and are not needed here; take the PBX address and key. From the address you only need the domain — the path segment after /v1/, not the whole URL. «Интеграция по API Гравител» is the previous generation and will not work.","connectorGravitelDomain":"Gravitel domain","connectorHHOAuthButton":"Connect via hh.ru","connectorHHOAuthError":"Failed to connect HeadHunter. Please try again","connectorHHOAuthPopupBlocked":"Browser blocked the popup. Allow popups and try again","connectorHHOAuthWaiting":"Waiting for hh.ru authorization...","connectorHeadhunterConnectHint":"Sign in to hh.ru with the employer account the agent needs: the token goes to the current browser session. Find yourself under «Управление и автоматизация» → «Менеджеры»; only the administrator adds managers. On «Менеджеры вакансий» use the «…» menu to enable «К активным вакансиям», «К архиву вакансий» and «Открытие контактов в резюме из базы». Search cap: 500 unique resumes per manager per day.","connectorHrlinkConnectHint":"You need the «Кадровик» (HR) role in the legal entity — without it the token item never appears and registries return 403. Initials icon in the top right corner → «Получить API-токен» → «Скопировать»; the token lasts one year. The address is the one you sign in at, like company.hr-link.ru. Take clientId from currentUser.clientUsers[].client.id in GET /api/v2/currentUser.","connectorInstagramConnectHint":"The Instagram account must be professional — business or creator. In your app on developers.facebook.com open “Instagram” → “API setup with Instagram business login”, enable instagram_business_basic plus instagram_business_content_publish and instagram_business_manage_comments for posting and comments, then click “Generate token”. The token starts with IGAA and lasts 60 days.","connectorInstanceId":"Instance","connectorJwtToken":"JWT Token","connectorKaitenConnectHint":"Avatar in the top right corner → \"Profile settings\" → \"API access key\" → \"Create key\". The key inherits the rights of whoever created it, so sign in with an account that sees the right boards. The value is a 36-character UUID with hyphens, like 296a5709-99bc-49a7-96e0-c0a1b236091f. Take the address from the browser bar: https://your-company.kaiten.ru, or your own domain if self-hosted.","connectorKaspiConnectHint":"Web version of the merchant cabinet at kaspi.kz/mc → «Настройки» (Settings) → «Токен API» (API token) → «Сформировать» (Generate), then copy the whole string. Only the company's head can issue it: an employee account will not show the item, and neither will the Kaspi Pay mobile app. The token does not rotate — if you lose it, open the same page and copy it again.","connectorKonturExternConnectHint":"Request at kontur.ru/extern/api → email with client_id and a link → «Выпустить ключ» at integrations.kontur.ru. The api-key is a GUID (8-4-4-4-12 with hyphens). The Access Token comes separately from identity.kontur.ru: scope «openid extern.api», client_secret is that same api-key, signed in with an account that has access to the organizations. The token lives 3600 seconds; production requires a contract with Kontur.","connectorKonturFocusConnectHint":"The Focus key is not issued inside the account: at focus.kontur.ru/site/api click «Бесплатная консультация» and leave a request naming lookups by INN and OGRN — without the «Реквизиты» (/api3/req) method requests return a permissions error. The key arrives by email to the contract address: a long string of digits and Latin letters, no dashes. Test it at focus-api.kontur.ru/api3/req/userform in the «Ключ доступа» field.","connectorLangfuseConnectHint":"Langfuse → the project you need → Settings → \"API Keys\" → create a new key pair. Owner or Admin role required: Member and Viewer cannot open project settings. The public key is prefixed pk-lf-, the secret one sk-lf- — copy both at once. Keys are scoped to a single project. Outside the EU region add the host: https://us.cloud.langfuse.com, https://jp.cloud.langfuse.com, or your self-hosted domain.","connectorLangfuseHost":"Host","connectorLangfusePublicKey":"Public Key","connectorLangfuseSecretKey":"Secret Key","connectorLinearConnectHint":"Settings → “Security & access” → “Personal API keys” block → “New API key”. No button means an admin disabled “Member API keys” in Settings → Administration → API. Scope: full access or Read, Write, Admin, Create issues, Create comments — without Write the agent cannot create an issue; access can be limited to specific teams. The key starts with lin_api_ and is shown only once.","connectorMailruConnectHint":"«Настройки» → «Все настройки» → «Безопасность» → «Пароли для внешних приложений» (Passwords for external applications) → «Создать». Check first that a phone is linked and that «Доступ к почте по IMAP, POP и SMTP» is on. Protocol type — «Полный доступ к Почте»: «Только отправка писем в Почте» reads no folders. The password is shown once and stored nowhere.","connectorMangoOfficeConnectHint":"Cabinet lk.mango-office.ru → «Интеграции» (Integrations) → «API коннектор» (API connector). If no credentials are shown, click «Подключить API коннектор», tick «Я принимаю условия» and confirm — while the connector is off, API requests are rejected. Then copy two different values: «Уникальный код вашей АТС» is the key, «Ключ для создания подписи» is the salt. Sign in as the virtual PBX owner or administrator.","connectorMaxMessengerConnectHint":"business.max.ru → «Чат-боты» → «Создать»: fill the card with a 500×500 px logo, a name and a description; the nickname is auto-generated as idИНН_bot. Only Russian residents — a company, a sole proprietor or a self-employed person — may create bots. Moderation takes up to 48 business hours, and the token appears in the bot card only after the status «создан». Copy the whole string.","connectorMcpAddHeaders":"Add HTTP headers","connectorMcpAddNote":"Add note","connectorMcpAuthApiKey":"API key header","connectorMcpAuthBearer":"Bearer token","connectorMcpAuthNone":"not required","connectorMcpAuthOAuth":"OAuth","connectorMcpAuthorize":"Authorize","connectorMcpBackToPaste":"Back to paste","connectorMcpBrowseFile":"browse","connectorMcpDropZoneHint":"URL, JSON, or .json file","connectorMcpDropZoneTitle":"Paste config or drop a file","connectorMcpEditDetails":"Edit","connectorMcpFileNotJson":"Only .json files are supported","connectorMcpHeaders":"HTTP headers","connectorMcpImportSkipped":"Skipped {count} local server(s) — cloud supports hosted URLs only","connectorMcpImportSuccess":"Imported {count} server(s)","connectorMcpManualLink":"Configure manually","connectorMcpOAuthPopupBlocked":"Popup was blocked by the browser","connectorMcpOAuthSuccess":"MCP server connected via OAuth","connectorMcpParseError":"Couldn't read this config. Check the format.","connectorMcpPastePlaceholder":"https://server/mcp or {\"mcpServers\": {…}}","connectorMcpProbeAuthLabel":"Authentication","connectorMcpProbeError":"Cannot reach server: {error}","connectorMcpProbeTools":"Tools detected ({count})","connectorMcpProbing":"Probing server…","connectorMcpServerName":"Server name","connectorMcpTokenLabel":"Authentication token","connectorMcpTokenPlaceholderApiKey":"your API key","connectorMcpTokenPlaceholderBearer":"Bearer …","connectorMcpTokenRequired":"Enter the token to continue","connectorMcpTransport":"Transport","connectorMcpUrl":"Server URL","connectorMedialogiaConnectHint":"Sign in to the SocMedia workspace at https://sm.mlg.ru — the API wants that same login and password, no separate key. Your personal manager switches API access on; contacts sit in «Профиль» (Profile), the initials badge at the top right, with the account expiry and remaining limits. Add a dedicated user: Settings → «Системные» → «Пользователи» → «Добавить», role «Администратор» or «Редактор» — «Просмотр» cannot create reports.","connectorMegamarketConnectHint":"partner.megamarket.ru → «Настройки» → «Интеграция по API» (Settings → API integration) → the «Авторизационный токен» row with a copy button. Sign in as a cabinet administrator: without those rights the section is hidden, same as for FBO-only accounts — Megamarket support enables it via chat. Sandbox and production tokens differ; a sandbox one returns 401.","connectorMegaplanConnectHint":"The account address comes from the address bar: company.megaplan.ru or m123456789.megaplan.ru, https:// included. The agent sees exactly what the employee sees — «Директор» and «Администратор» carry the widest rights, a regular employee only their own deals and tasks. A separate account is created in the «Сотрудники» section: the invitation arrives by e-mail, where the employee sets a permanent password. Verify via /api/v3/docs.","connectorMerchantLogin":"Merchant Login","connectorModulbankConnectHint":"In the «+» menu pick «Интеграция с банком», or go «Настройки» → «Услуги» → «API Банка» → «Генерация токена авторизации» (Settings → Services → Bank API → Authorization token generation). Confirm account-info and operation-history access: without account-info no account shows up. The token is issued for 3 years and only sees the login's own companies and accounts.","connectorMoyskladConnectHint":"«Меню пользователя → Настройки → Сотрудники» → «+Сотрудник»: create a robot employee, pick «Пользователь» under «Системные роли» and press «Настроить права» (only on the «Профессиональный» and «Корпоративный» plans). Turn on «Доступ по API» — an «Администратор» alone can. POST https://api.moysklad.ru/api/remap/1.2/security/token returns «access_token».","connectorMpstatsConnectHint":"mpstats.io/account → the «API токен» block: the token is already generated, no request needed. The account must be on a paid plan — the request quota is tied to it, and the API answers 429 once it runs out. The value is two hex strings joined by a dot (5a2a5f0e538dd5.6691914...) — copy it whole. Changing the password or pressing «Сменить API токен» regenerates it.","connectorNoConnectedDescription":"Connect a service and it will appear here","connectorNoConnectedTitle":"No connected integrations","connectorNoCustomApis":"No custom APIs added yet","connectorNoMcpServers":"No MCP servers added yet","connectorNoPopularDescription":"Popular services will appear here later","connectorNoPopularTitle":"No popular services yet","connectorNoResultsDescription":"Try changing your search or resetting the filters","connectorNoResultsTitle":"Nothing found","connectorNote":"Hint for the assistant (optional)","connectorNotePlaceholder":"E.g.: \"Use this service to search customers by email\"","connectorOAuthOffline":"We could not reach the server, so the connection status is unknown. It may already be done — press Retry to check.","connectorOAuthTimeout":"The code has expired and no longer works. Please try again.","connectorOnecAccountingConnectHint":"Designer → «Администрирование» → «Публикация на веб-сервере…», tick «Публиковать стандартный интерфейс OData». Then «Администрирование» → «Синхронизация данных» → «Настройки стандартного интерфейса OData»: «Состав» tab — tick the objects, «Авторизация» tab — a dedicated user with a password. The address is https://сервер/имя-публикации, verify it on /odata/standard.odata/$metadata.","connectorOnecCustomConnectHint":"Configurator → «Администрирование» → «Публикация на веб-сервере…» → tick «Публиковать стандартный интерфейс OData». Then in «1С:Предприятие»: «Администрирование» → «Синхронизация данных» → «Настройка состава стандартного интерфейса OData», otherwise the composition is empty. The dedicated user needs a password and the role «Удаленный доступ OData». The address stops before /odata/standard.odata — check it with $metadata in a browser.","connectorOnecDocumentFlowConnectHint":"Designer → Administration → «Публикация на веб-сервере…»: base name in Latin letters, tick «Публиковать стандартный интерфейс OData». Then Administration → Data synchronisation → «Настройка стандартного интерфейса OData»: tab «Состав» → «Загрузить метаданные», tab «Авторизация» → «Создать отдельные имя пользователя и пароль» (role «Удаленный доступ OData»). Address without the tail: https://your-server/base-name.","connectorOnecErpConnectHint":"Designer → «Администрирование» → «Публикация на веб-сервере…», tick «Публиковать стандартный интерфейс OData». Then «Администрирование» → «Синхронизация данных» → «Настройки стандартного интерфейса OData»: «Состав» — tick the objects, «Авторизация» — a dedicated user with a password. The address is https://сервер/имя-публикации, verify it on /odata/standard.odata/$metadata: a 401 means the user lacks the role.","connectorOnecHrConnectHint":"Designer → «Публикация на веб-сервере»: Latin name plus the «Публиковать стандартный интерфейс OData» tick — that published address is the database URL. In «Настройка стандартного интерфейса OData», tab «Состав», tick the objects or /$metadata comes back empty. Use a dedicated user with the «Удаленный доступ OData» role and no two-factor auth.","connectorOnecSmallBusinessConnectHint":"Designer → «Администрирование → Публикация на веб-сервере», tick «Публиковать стандартный интерфейс OData». Then «Администрирование → Синхронизация данных → Настройки стандартного интерфейса OData»: «Состав» → «Загрузить метаданные», tick the objects; «Авторизация» → a separate username and password. URL goes up to the database name: https://server/base-name.","connectorOnecTradeConnectHint":"Designer → «Администрирование» → «Публикация на веб-сервере…» → tick «Публиковать стандартный интерфейс OData». Then «НСИ и администрирование» → «Синхронизация данных» → «Настройка состава стандартного интерфейса OData» — tick the objects, it is empty by default. The dedicated user needs the «УдаленныйДоступOData» role, otherwise 401. The part before /odata is the database address: /odata/standard.odata/$metadata must return XML.","connectorOrdConnectHint":"ord.beeline.ru → «Регистрация» → «Отправить заявку»: login and password arrive by email after the account is activated. The offer of ООО «Первый ОРД» is accepted by the organization administrator only, otherwise the API stays closed. For the agent: «Пользователи» → «Добавить пользователя», role «Пользователь API» (missing in the form — support@1ord.ru). Lost the password — «Восстановление пароля».","connectorOzonAccessBulletActions":"Manage promotions and discount requests","connectorOzonAccessBulletChat":"Reply in chat and to buyer questions","connectorOzonAccessBulletPrices":"Change prices and stock","connectorOzonAccessBulletRead":"Read products, orders and analytics","connectorOzonAccessBulletReadOnly":"Read products, orders and analytics — no changes","connectorOzonAccessFull":"Full access","connectorOzonAccessRead":"Read only","connectorOzonApiKey":"API Key","connectorOzonApiKeyConnectHint":"Ozon Seller account → Settings → Seller API → “Generate key”. When creating, pick a role with access to the sections you need (writing prices and stocks requires a role with write access). Permissions are fixed at creation — to expand access, generate a new key. This key does not open advertising: the Performance API has its own authorization — connect “Ozon Ads” for that.","connectorOzonClientId":"Client ID","connectorOzonConnectHint":"seller.ozon.ru → sign in as an Administrator or a Manager: courier and warehouse operator roles cannot grant access. Pick the right company in the Ozon window — access goes to one seller account, a second shop is connected separately. Decide the scope: read-only, or full access with chat and question replies, discount requests and supply orders. Granted access is listed and revoked under Settings → “Applications and permissions”.","connectorOzonOAuthButton":"Connect via Ozon","connectorOzonOAuthError":"Failed to connect Ozon. Please try again","connectorOzonOAuthPopupBlocked":"Browser blocked the popup. Allow popups and try again","connectorOzonOAuthWaiting":"Waiting for Ozon authorization...","connectorOzonPerformanceClientId":"Advertising account Client ID","connectorOzonPerformanceClientSecret":"Client Secret","connectorOzonPerformanceConnectHint":"This is the advertising account key, not the Seller API one: Ozon advertising account → Settings → API keys → create a service account if needed → “Add new key”. The Client ID looks like “12345678-1712345678901@advertising.performance.ozon.ru”, and the Client Secret is shown once — copy it right away. A Seller API key (Client-Id + API key) will not work here: advertising lives on a separate host with separate authorization. Permission to change bids and campaigns depends on the service account role in the advertising account.","connectorPassword":"Password","connectorPassword1":"Password #1","connectorPassword2":"Password #2","connectorPochtaRussiaConnectHint":"«Настройки» → «API» (Settings → API) in the otpravka.pochta.ru account (otpravka.pochta.ru/settings#/api-settings): the «API токен» field is the app token, also emailed to you at registration. The login and password are those of the otpravka.pochta.ru account itself; a phone in +7XXXXXXXXXX format authenticates more reliably than an e-mail. Keys appear only after the access request and contract are approved — up to 3 business days.","connectorPolymarketConnectHint":"polymarket.com → profile menu → copy the account wallet address. If you signed up with Google or email, you need the account address, not your MetaMask signer address: positions live under the former, the latter returns nothing. The address is 0x plus 40 hexadecimal characters, 42 in total. There is no API key to create — only public data is read.","connectorPostgresConnectHint":"In your SQL console: CREATE ROLE analytics_ro LOGIN PASSWORD '…', then GRANT pg_read_all_data TO analytics_ro (from PostgreSQL 14). It does not bypass row-level security — tables under RLS return zero rows without a SELECT policy. Host, port, database: Supabase — the “Connect” button at the top of the dashboard, Neon — “Connect” on the project dashboard, Yandex — the FQDN and port 6432. The host must be reachable from the internet, SSL — require.","connectorPostizConnectHint":"Postiz → «Settings» → «Developers» → «Public API» — copy the whole key; it is sent with no prefix. The key belongs to the whole workspace, so connect at least one social channel first or there is nowhere to publish. Cloud address is https://api.postiz.com; for self-hosted use the root address of your instance, the same one the dashboard opens at.","connectorPostizUrl":"Postiz server URL","connectorPublicKey":"Public Key","connectorRecommended":"Connected","connectorReconnect":"Reconnect","connectorReconnectBanner":"Access expired. Reconnect {service} to resume syncing.","connectorReconnectNeeded":"Reconnection required","connectorReconnectTitle":"Reconnect {service}","connectorRetailCRMApiKey":"API Key","connectorRetailCRMDomain":"Account domain","connectorRetailCRMSubdomain":"Subdomain","connectorRetailcrmConnectHint":"«Administration» → «Integration» → «Add». Set «Access type» to «Access to all shops» or tick the ones you need, and in «Allowed API methods» enable orders, customers, products, reference books, tasks and users — a disabled method answers with an access error. The key token is generated automatically, at least 32 characters. The subdomain is the part before the first dot: in «https://myshop.retailcrm.ru» it is myshop, and «Account domain» is everything after it. The domain belongs to the account, not to the interface language: if your account opens on retailcrm.ru, keep retailcrm.ru, otherwise the retailcrm.pro default is right.","connectorRevealFailed":"Failed to reveal credentials","connectorRevokeAnytime":"You can revoke access at any time.","connectorRobokassaConnectHint":"Robokassa cabinet → «Мои магазины» → «Технические настройки» (My shops → Technical settings). MerchantLogin is the shop login, not your account e-mail. Check that the hash algorithm is MD5, otherwise signatures will not match, and copy the live pair: Password #1 signs the payment, Password #2 signs notifications and status. Test passwords return error 29.","connectorSberAuthCode":"Authorization code","connectorSberClientCert":"Client certificate","connectorSberClientId":"Client ID","connectorSberClientKey":"Certificate private key","connectorSberClientSecret":"Client Secret","connectorSberConnectHint":"«Все продукты и услуги» → «Сбербанк API» → «Sber API» → «Подключить»; only the CEO signs. Client ID and Client Secret sit in «Параметры промышленного сервиса»; rotate the secret every 40 days or access is blocked. Certificate and private key: «Сертификаты шифрования» → «Сгенерировать сертификат». The code lands in the address bar after https://sbi.sberbank.ru:9443/ic/sso/api/v2/oauth/authorize with openid in scope.","connectorSberRedirectUri":"Redirect URI","connectorSbisAppSecret":"App Secret","connectorSbisClientId":"App Client ID","connectorSbisConnectHint":"«Настройки» → «Система» → «Безопасность» → «Подключения к Saby», then add an application. Rights: «Разрешен полностью» or «С ограничением по правам»; authorization type must be «по сервисному ключу», otherwise background login will not work. In the card copy «ID подключения», reveal «Защищенный ключ» with the eye icon, and save the service key from the «с авторизацией по сервисному ключу» row — it arrives as a file.","connectorSbisSecretKey":"Secret Key","connectorScanInterfaxConnectHint":"SCAN API access is granted on request: on scan-interfax.ru open «API для проверки деловой репутации» → «Обсудить внедрение», or email scan-sales@interfax.ru. Interfax provisions the account and hands over the login and password — they never appear on their own in the web.scan-interfax.ru account. Check the pair at https://gateway.scan-interfax.ru/index.html: POST /api/v1/account/login returns accessToken, or 401 if access is not live.","connectorSearch":"Search","connectorSecretKey":"Secret Key","connectorSecrets":"Secrets (sent as headers)","connectorSecretsEditHint":"Leave values empty to keep current keys","connectorSecretsKey":"Header","connectorSecretsValue":"Value","connectorSenderSign":"Sender Name","connectorSendsayAccount":"Account name","connectorSendsayConnectHint":"Account menu → «Настройки системы» (System settings) → «Пользователи» (Users) → «Добавить пользователя»: create a separate sublogin, the owner cannot be issued an API key. Use the «Менеджер» role and no 2FA — it breaks key requests. Then user card → «Настройка пользователя» tab → «API-ключ» → «Сгенерировать ключ»; shown once. Account name is your main login from the account menu.","connectorServerUrl":"Server URL","connectorShopId":"Shop ID","connectorSkipSkill":"Skip","connectorSmsaeroConnectHint":"SMS Aero cabinet → Settings → \"API\" (smsaero.ru/cabinet/settings/apikey). The key only works paired with the account email — both values are required. The sender name (sign) is optional, but SMS Aero rejects sending under a name that is not approved, so enter only a moderated signature. The service is prepaid: with insufficient funds the API returns a payment error.","connectorStarlineAppId":"App ID","connectorStarlineAppSecret":"App Secret","connectorStarlineConnectHint":"my.starline.ru → «Разработчикам» → «Создать приложение». The section shows up only when the interface language is set to Russian, requests without a stated purpose are not reviewed, and approval arrives by email — after that the app card carries the AppId and Secret. The login and password are those of the StarLine ID account whose device list holds the car. A personal account gets 1000 requests per day.","connectorStarlineLogin":"StarLine ID Login","connectorStarlinePassword":"StarLine ID Password","connectorSupadataConnectHint":"dash.supadata.ai: the key is generated automatically during onboarding and sits in the dashboard, so you do not create it manually. Copy the whole string with no stray spaces — an extra character returns an unauthorized error. Free plan: 100 requests per month, no card; transcript and metadata cost 1 credit per call, AI captions 2 credits per minute, batch over a playlist or channel is paid plans only.","connectorSuspended":"Suspended","connectorTBankOAuthButton":"Connect via T-Bank","connectorTBankOAuthError":"Failed to connect T-Bank. Please try again","connectorTBankOAuthPopupBlocked":"Browser blocked the popup. Allow popups and try again","connectorTBankOAuthWaiting":"Waiting for T-Bank authorization...","connectorTabApps":"Apps","connectorTaxiCrmConnectHint":"The cabinet address is https://yourfleet.taxicrm.ru; the part before .taxicrm.ru is the subdomain. The key sits in «Компания» → «Настройки компании» → «API» (Company → Company settings → API), one key for the whole fleet, opening drivers, trips, shifts, payouts, penalties and rentals. Driver payout, balance change and payout-block change open only on request through taxiCRM support; without it they answer 402.","connectorTaxiCrmSubdomain":"Subdomain","connectorTelegramConnectHint":"@BotFather → /newbot → a name and a username ending in «bot». The token arrives in a reply: digits, a colon, letters — 110201543:AAHdqTcvCH1vGWJxfSeofSAs0K5PALDsaw. Lost it — send /token to @BotFather. For groups turn off /mybots → «Bot Settings» → «Group Privacy», otherwise the bot only sees commands and replies. A bot has one webhook: if it is already taken, create a separate bot.","connectorTestConnection":"Test","connectorTestFailed":"Connection failed: {error}","connectorTestSuccess":"Connection successful (HTTP {status})","connectorTestingConnection":"Testing...","connectorTgstatConnectHint":"The token lives in your TGStat profile at tgstat.ru/my/profile and is issued to any registered user. First switch on a Stat API plan in «Личный кабинет» (Personal account): FREE only allows querying 2 channels you own. The token is 32 hex characters with no prefix, like 6d15f8ff6b9b9b134457c4aed9c2f7cb; it never expires, but regenerating it kills the previous one instantly.","connectorTiktokConnectHint":"developers.tiktok.com → “Manage apps” → “Connect an app”. Under “Add products” add Login Kit and Content Posting API; under “Scopes” tick video.publish, video.list, user.info.basic, user.info.stats — without video.publish the connection test fails. Client key and Client secret sit in “Credentials”; the access token starts with act. and lasts 24 hours. An unaudited client can only post privately (SELF_ONLY).","connectorTildaConnectHint":"The keys are issued on the Business plan only. Path in the account: Site Settings → Export → API Integration («Настройки сайта» → «Экспорт» → «API» in the Russian locale). The public key and the secret key sit side by side there — long alphanumeric strings with no prefix; take both, the API will not answer with the public one alone.","connectorTinkoffConnectHint":"Sign in at business.tbank.ru with the number that holds access to the company, and check the INN if there are several. Your level is in «Настройки профиля и доступы» → «Компания» → «Пользователи»: only a Director changes access. Access is per account: account → «Настройки» → «Доступ к счету» → «Сохранить». Operations go back to June 2023.","connectorTinkoffInvestConnectHint":"The token is issued in the web version only: настройки профиля Т-Инвестиции (T-Investments profile settings) at tbank.ru/invest/settings → issue a T-Invest API token for the exchange. read-only covers portfolio and quotes; full-access is for orders. Turn off «Подтверждение сделок кодом» first, otherwise issuing is blocked. The value is shown once and lives three months from last use — after idling the API returns error 40003.","connectorTinkoffInvestToken":"T-Invest API Token","connectorTochkaConnectHint":"Tochka internet bank → «Сервисы» → «Все сервисы» → «Интеграции и API» → «Создать JWT-ключ». Set a name and an access period, keep the permissions for accounts and statements — without them requests fail with «Forbidden by consent». Creation is confirmed by SMS. Copy the token in the «JWT-ключи» section right away, along with the client_id shown next to it. There is no refresh token: after expiry you reissue the key by hand.","connectorTwitterConnectHint":"Sign up at twitterapi.io with just an email, no card, no X Developer account. After signing in open the «Dashboard» — the key is displayed right on its home page, copy the whole string. Signup gives $0.1 in free credits; after that billing is per call — $0.15 per 1k tweets and $0.18 per 1k user profiles, so regular monitoring needs a top-up.","connectorUnisenderConnectHint":"Account at app.unisender.com → click your email in the bottom-left corner → «Настройки» (Settings) → «Интеграция и API» (Integration and API) tab. In «Доступ к API» (API access) press «Включить» (Enable) if access is off, then «Показать полностью» (Show in full) and confirm your Unisender account password — the key stays truncated until you do. The login is the same email you signed in with.","connectorUnisenderLogin":"Unisender Login","connectorUpdateSuccess":"{service} updated","connectorUsername":"Username","connectorUzumMarketApiToken":"API Token","connectorUzumMarketConnectHint":"Seller cabinet seller.uzum.uz → profile settings → API and integrations section → issue a Seller API token. The token covers the whole seller account, which needs at least one active shop, otherwise the shop list comes back empty. The value is one long string with no prefix — no Bearer word is added to it. Copy it right after creation; an old token cannot be recovered.","connectorViaYourComputer":"Requests go through your computer","connectorVkAdsAccessToken":"Access Token","connectorVkAdsClientId":"Client ID","connectorVkAdsClientSecret":"Client Secret","connectorVkAdsConnectHint":"In the VK Ads cabinet at ads.vk.ru go to “Settings” → “API access”: fill in the employee details and request access. The client_id is issued immediately, while the client_secret is revealed by a button and only within 10 minutes — copy it at once, it cannot be retrieved again. We obtain and refresh the access token ourselves via client_credentials, so there is nothing to paste by hand. The legacy VKontakte ads cabinet (api.vk.com/method/ads.*) is a different API: a token from there will not work here.","connectorVkteamsConnectHint":"VK Teams → chat search → «Метабот» (Metabot) → the /newbot command; the new bot's name must end with bot. The account you create it from stays the owner and cannot be changed. To let the bot into group chats, send /setjoingroups, the bot's nick and the word enable to Metabot. The token arrives in a reply, like 001.2659914704.0218887601:747432131; a lost one comes back with /token.","connectorWalletAddress":"Wallet Address","connectorWazzupConnectHint":"Wazzup account → «Каналы» (Channels): without at least one connected channel the API integration cannot be switched on. Then «Интеграция с CRM» (CRM integration) → pick API → «Подключить» (Connect) and copy the API key — a 32-character string of digits and lowercase Latin letters. Closed the window? The key stays in «Интеграция с CRM» → «Дополнительно» (Additional) tab.","connectorWebhookAutoRegisterFailed":"Could not register the webhook automatically. Register manually:","connectorWebhookAutoRegistered":"{service} connected, webhook registered","connectorWebhookCopyFailed":"Couldn't copy — copy manually","connectorWebhookOutboundUrl":"Outbound Webhook URL","connectorWebhookReady":"Copy the URL and paste it into the outbound webhook settings in {service}","connectorWebhookSection":"Notification URL","connectorWebhookUrlUnavailable":"Webhook URL is not available yet","connectorWhereToGetKey":"Where do I get the key?","connectorWildberriesApiToken":"API Token","connectorWildberriesConnectHint":"seller.wildberries.ru → «Settings → API access» → «Create new token»; only the account owner can issue it. Pick the «Service» type and find our service in the WB solutions catalogue — categories fill in automatically: WB cut request limits for the «Basic» type on 30.03.2026, so long reports take weeks. The token starts with eyJ, is shown once and lives 180 days — copy it right away.","connectorYandexCalendarConnectHint":"Sign in with the Yandex account that holds the calendars you need: the agent only sees calendars from the left-hand panel at calendar.yandex.ru. Someone else's calendar shows up after you click «Accept» in the invitation email. For the agent to edit and not just read, the owner uses the «Access» tab → «Grant access rights» and picks «Edit calendar contents». Calendars added via «New subscription» stay read-only.","connectorYandexCloudConnectHint":"Management console → “Identity and Access Management” → “Create service account”. Grant the role on the cloud itself: “Access bindings” tab → “Configure access” → “Add role”, viewer to read, editor if the agent should change resources. Then “Create new key” → “Create authorized key” → “Download file with keys” and paste the JSON in full: the private part is shown once. The Folder ID starts with b1.","connectorYandexCloudFolderId":"Folder ID","connectorYandexCloudSaKey":"Service account authorized key (JSON)","connectorYandexDataLensOrgLabel":"Yandex Cloud organization","connectorYandexDataLensSelectOrgDescription":"Select the Yandex Cloud organization to use for DataLens.","connectorYandexDatalensConnectHint":"datalens.ru → sign in with the Yandex account you use for dashboards and pick the right organization. Roles are granted per organization: “Service settings” → “Users” → “Send invitation”; datalens.visitor for access, datalens.metaReader for entities and the Public API, datalens.admin for full access. Content is opened separately: datalens.collections.viewer and datalens.workbooks.viewer.","connectorYandexDirectConnectHint":"Sign in with the Yandex login that holds the campaigns: client campaigns under an agency login won't show up. Rights carry over from the web interface — with read-only access the agent can only fetch data. The terms are accepted on the API Settings page, and its Parameters tab must have an empty allowed IP list.","connectorYandexDiskConnectHint":"Access comes from the account that confirms the code: for work files sign in to disk.yandex.ru with your Yandex 360 organization account. Colleagues' folders are visible only if the owner used «Настроить доступ» and granted «Редактирование» or «Просмотр». The request covers read of the whole Disk, write anywhere, Disk info and app-folder access, and cannot be granted partially.","connectorYandexFleetApiKey":"API Key","connectorYandexFleetClientId":"Client ID (Clid, e.g. taxi/park/<uuid>)","connectorYandexFleetConnectHint":"The fleet cabinet is fleet.yandex.ru. Only an employee with the \"Director\" role can edit the \"API\" section. In the control room open \"Settings\" → \"API\": keys are created there, and the partner ID (park_id) and client ID (X-Client-ID) are shown. The secret API key (X-API-Key) is issued at creation time — copy it right away.","connectorYandexFleetParkId":"Park ID (UUID)","connectorYandexMailConnectHint":"Mail settings → «Почтовые программы» (Mail clients) → enable «С сервера imap.yandex.ru по протоколу IMAP» and check that «Пароли приложений и OAuth-токены» is active: without it token login is rejected. Confirm the code under the address whose mail you are connecting — in Yandex 360 for Business the login is the full address, e.g. user@company.ru.","connectorYandexMarketApiKey":"API Key","connectorYandexMarketApiKeyConnectHint":"Yandex Market Partner account → Settings → API → “Create new API key”. The simplest option is “all-methods” (full access) — the agent gets every section.","connectorYandexMarketConnectHint":"Access is issued to a Yandex login, not to the cabinet: sign in with the one that has access to every shop you need in the partner cabinet at partner.market.yandex.ru — the agent sees only its campaigns (FBY, FBS, DBS). The role must open «Настройки» → «API и модули» (Settings → API and modules); a «Контент-менеджер» (content manager) cannot see it. A password change, a 2FA change or account recovery revokes the access.","connectorYandexMetricaConnectHint":"Sign in with the Yandex login that has access to the counter: the agent sees exactly its counters. Check yourself at metrika.yandex.ru under Settings → Access — the View level is enough for reports on visits, traffic sources and goals. If you aren't listed, the owner clicks Add user; access to a whole account is granted via Account settings → Representatives.","connectorYandexOAuthButton":"Connect","connectorYandexOAuthCode":"Confirmation code","connectorYandexOAuthDescription":"Follow the link and enter the code to connect","connectorYandexOAuthError":"Failed to connect Yandex. Please try again","connectorYandexOAuthWaiting":"Waiting for confirmation...","connectorYandexOrgId":"Yandex 360 Organization ID","connectorYandexOrgIdHint":"Yandex Tracker → Administration → Organization ID","connectorYandexTrackerConnectHint":"Sign in at tracker.yandex.ru with your work Yandex ID — the API acts on behalf of that user. The read-only role (the default without a Tracker subscription) only allows viewing: creating issues needs full access or administrator. Open the queues you need via Queues → settings icon → Access. The account's organization is shown under Administration → Organizations.","connectorYandexWebmasterConnectHint":"webmaster.yandex.ru → «Мои сайты» (My sites) → «Добавить сайт» (Add site), full address with protocol (example.com and www.example.com are separate sites). Then «Подтвердить права» (Verify rights): a yandex_*.html file in the root, a yandex-verification meta tag, or a DNS TXT record; the check takes up to 24 hours, and until a site is verified its data is closed. If a colleague owns it, have them grant your account full access.","connectorYandexWikiConnectHint":"Wiki lives inside a Yandex 360 for Business organization — sign in at wiki.yandex.ru with your work account, and if there are several organizations pick one and click Continue. Service accounts are barred from the API, federated ones need a Yandex Cloud IAM token. API permissions mirror the account's Wiki permissions: click the access button at the top (All employees), add yourself in the Page access window, then grant Reader or Editor.","connectorYandexWordstatApiKey":"API Key","connectorYandexWordstatConnectHint":"Yandex Cloud console → “Service accounts” → create an account and grant it the search-api.webSearch.user role on the folder: without it Wordstat refuses even a valid key, and search-api.executor is deprecated. Then “Create new key” → “Create API key”, “Scope” — yc.search-api.execute; the key starts with AQVN and is shown once. The folder ID is on the folder page under the name and starts with b1. A linked billing account is required.","connectorYandexWordstatFolderId":"Folder ID","connectorYclientsCompanyId":"Company ID","connectorYclientsConnectHint":"Sign in to YCLIENTS as the user who manages the branch and open yclients.com/appstore/developers: «Настройки аккаунта» (Account settings) → API key, that is the partner token. Then in «Мои приложения» create an app and in its «Доступ к API» section tick the system user's rights (clients, records, services); the «User token» field appears there. The branch ID is the number in the branch cabinet's address bar.","connectorYclientsPartnerToken":"Partner token","connectorYclientsUserToken":"User token","connectorYookassaConnectHint":"YooKassa dashboard: shopId is in “Settings — Shop”, the key in “Integration — API keys” → “Issue key”, confirmed by SMS password. You need the owner or “Developer” role, otherwise the section stays closed. The secret key is shown only once — copy it right away; after a reissue the previous one works for 48 more hours.","connectorYougileConnectHint":"YouGile has no UI for issuing keys. On any page of your company press Ctrl+Alt+Q (Ctrl+Option+Q on Mac) to copy companyId. Open https://ru.yougile.com/api-v2#/operations/AuthKeyController_create, fill login (your account email), password and companyId, press «Send API Request» and copy the string in key — about 48 characters. A key inherits its creator's rights, so make a master key as an administrator.","connectorYoutubeConnectHint":"Sign in with the Google Account that owns a channel: profile picture on youtube.com → \"Settings\" → \"Account\" → \"Add or manage channel(s)\". Check your role at studio.youtube.com → \"Settings\" → \"Permissions\" — only the owner and managers see the list. A channel still on a Brand Account is moved first with \"Move Permissions\". \"Manager\" covers everything except deleting the channel.","connectorYoutubeOAuthError":"Failed to connect YouTube. Please try again","connectorZapcapConnectHint":"The key is issued at platform.zapcap.ai/dashboard/api-key and only on the Pro ($16/mo) or Agency+ ($32/mo) plan — Free and Starter cannot issue one. Render credits are bought separately from the subscription, from $0.10 per minute of rendered video: without them the key works but render tasks are rejected. Copy the whole value — ZapCap expects it in the x-api-key header.","ctaOpenApp":"Open app","ctaSignup":"Try for free","dashboard":"Tasks","date":"Date","declineCardExpired":"Renewal failed: your card has expired. Add a new card to keep access to your plan.","declineCardInvalid":"Renewal failed: the card details are invalid. Add a new card to keep access to your plan.","declineCardRestricted":"Renewal failed: the payment was declined by your bank. Contact the bank or use another card to keep access to your plan.","declineInsufficientFunds":"Renewal failed: not enough funds on the card. Top up the card or use another one to keep access to your plan.","declineIssuerUnavailable":"Renewal failed: your bank is temporarily unavailable. We will retry, or you can use another card to keep access to your plan.","description":"Description","disabled":"Disabled","download":"Download","email":"Email","enabled":"Enabled","errAuthRequired":"Authentication required","errChatCodeFallback":"Error: {code}","errChatConnectionLost":"Connection lost. Try again.","errChatCorruptedFile":"File is corrupted or has an invalid structure. The size is fine — the problem is in the content.","errChatEmbeddingFailed":"Could not index the document. Try uploading it again.","errChatEmptyDocument":"The document has too little text to analyze.","errChatExtractionTimeout":"Document processing timed out.","errChatFileNotFound":"File not found. Upload it again.","errChatFileNotFoundNamed":"File \"{filename}\" not found. Upload it again.","errChatGeneric":"An error occurred. Try again.","errChatOcrRequired":"The document is a scan. Text recognition takes longer.","errChatPasswordProtected":"File is password-protected. Upload an unprotected version.","errChatSessionBusy":"This session is being processed in another window. Wait for the response or refresh the page.","errChatSuspiciousContent":"Document rejected by the security system: hidden AI instructions were found in the text.","errCheckInput":"Check the entered data","errFallbackGeneric":"An error occurred, try again","errFallbackValidation":"Data validation error","errInvalidCredentials":"Incorrect email or password","errInvalidOtp":"Invalid or expired code — request a new one","errPermissionDenied":"You don't have permission for this operation","errServerErrorRetryLater":"Something went wrong. Try again later","errServiceUnavailable":"Service temporarily unavailable","errSessionExpired":"Session expired, sign in again","errSignupFailed":"Sign-up failed, try again later","errTokenExpired":"Token has expired","errTooManyAttempts":"Too many attempts. Wait 1 minute","error":"Error","errorDetailsForDeveloper":"Details for developer","errorFullReload":"Full reload","errorPushokWorried":"Pushok is worried too, but nothing is lost — try again.","errorSomethingWentWrong":"Something went wrong","errorTryAgain":"Try again","errors.CAPACITY_EXHAUSTED":"Too much work in flight right now. Please try again in a few seconds.","errors.CONNECTION_LOST":"Connection lost. Please try again.","errors.CONNECTOR_SCHEME_BLOCKED":"This connection scheme is not allowed in the cloud environment.","errors.CORRUPTED_FILE":"File is corrupted or has invalid structure.","errors.DATA_USAGE_QUOTA_EXCEEDED":"Plan limit reached. Top up or wait for your limit to reset.","errors.EMPTY_DOCUMENT":"Document contains too little text for analysis.","errors.EMPTY_RESPONSE":"Could not generate response. Try rephrasing.","errors.EXECUTION_FAILED":"Operation execution error.","errors.EXEC_BUDGET_EXCEEDED":"The run hit its budget limit and was stopped. Increase the task budget and run it again.","errors.EXTRACTION_TIMEOUT":"Document processing timeout.","errors.LLM_CREDITS_EXHAUSTED":"A temporary problem on our side — the AI service is currently unavailable. We're on it; please try again a little later.","errors.LLM_ERROR":"AI service error. Please try again.","errors.LLM_NON_RETRYABLE":"The AI service rejected the request. Try rephrasing.","errors.LLM_TIMEOUT":"AI service response timeout.","errors.LLM_UNAVAILABLE":"AI service temporarily unavailable. Please try again in a few minutes.","errors.LOCAL_HANDS_NOT_READY":"The local executor on your computer is not ready yet. Open the desktop app and try again.","errors.ORCHESTRATOR_PARTIAL_COMMIT":"The response was only partially saved. Refresh the page and try again.","errors.ORCHESTRATOR_PREPARATION_FAILED":"Could not prepare the response. Please try again.","errors.ORG_POLICY_DENIED":"This action is blocked by your organization's policy.","errors.PASSWORD_PROTECTED":"File is password protected. Upload an unprotected version.","errors.PERMISSION_SCOPE_MISSING":"The API key is missing required permissions. Grant them in the service's dashboard and reconnect the integration.","errors.RATE_LIMITED":"Rate limit exceeded. Please wait a moment.","errors.RECONNECT_REQUIRED":"Access to the service has expired. Reconnect the integration and your tasks will continue.","errors.SERVER_ERROR":"Something went wrong. We're looking into it.","errors.SERVICE_QUOTA_EXHAUSTED":"The service quota is exhausted. Try again later or upgrade your plan.","errors.SERVICE_UNAVAILABLE":"Service temporarily unavailable. Please try later.","errors.SESSION_CONCLUDED":"Session ended — this run is already closed.","errors.STREAM_IDLE_TIMEOUT":"The response timed out while idle. Please try again.","errors.SUBSCRIPTION_REQUIRED":"This feature requires an active subscription.","errors.SYNTHESIS_FIRST_CHUNK_TIMEOUT":"The AI service took too long to start responding. Please try again.","errors.SYNTHESIS_STALL_TIMEOUT":"The response stalled midway. Please try again.","errors.TASK_ALREADY_RUNNING":"This task is already running. Wait for it to finish or stop it first.","errors.TRANSCRIPT_DEGRADED":"One step did not reach the transcript — work continues","errors.UNSUPPORTED_FORMAT":"Unsupported format. Please upload {supported_formats}.","expired":"Expired","externalExpiresOn":"Access until {date} — renew on the {provider} side","featureAIAssistant20Integrations":"1C, CRM, marketplace dashboards and 98+ services in one window","featureAccessAndRoles":"Member roles and permissions","featureAuditLogs":"Audit log of all actions","featureCreditPool":"Shared balance: whoever hits a limit draws from it instead of moving the team to Max","featureDailyTasksPro":"Up to 40 requests and 30 images a day","featureDocGeneration":"Invoices, letters, cards and decks in minutes","featureFreeChat":"Chat with the AI agent in the browser and Telegram","featureFreeDailyTasks":"Up to 5 requests and 3 images a day","featureFreeDocs":"Documents and calculations from your files","featureFreeIntegrations":"Connect 1C, CRM and marketplaces","featureFreeSearch":"Web search and legal database","featureFreeTasksPauseIfIdle":"Scheduled tasks run while you keep showing up","featureKnowledgeBase":"Shared team drive and knowledge base","featureMaxMultiplier":"Up to 160 requests and 75 images a day — 4× Pro","featureMemoryContractorsProjects":"Remembers projects, clients and past decisions","featureMixAndMatch":"Up to 5 free seats — same organization, Free plan limits","featureModelsOnRFServers":"Data stays in Russia — models on servers in the RF","featureModelsOnRFServersGdpr":"Data stays in the EU — processing on servers in the EU/EEA","featurePriorityQueue":"Priority queue — fast replies even at peak","featurePrioritySupport":"Priority Telegram support — replies within an hour","featureSandbox":"Ready conclusions from tables and exports","featureSchedules":"Scheduled tasks and triggers — they run without you","featureSeatsProrated":"Add or drop seats any time — the invoice is recalculated by the day","featureUnifiedBilling":"One invoice and contract for the whole team","featureVideoGeneration":"Up to 15 videos a month — Reels and Shorts","featureWebAndLegalSearch":"Finds facts, prices and legal norms","financeNavDesc":"Reconciliation, VAT, e-docs, receivables, reporting","financeNavLabel":"Finance","financeTry1":"Build a P&L for [period] broken down by business unit using 1C data.\nFor each unit: revenue, direct costs, gross profit, overhead, profit before tax.\nNext to it — the share of total company revenue.\nAllocate indirect costs only by the rule [by revenue / by payroll / by floor area]. If no allocation\nbase is set, don't spread them evenly — put such costs on a separate line\n\"not allocated\".\nBuild the report on the accrual basis: from sales documents, not from cash receipts.\nOutput an XLSX: a \"P&L\" sheet with units in columns, a \"Details\" sheet linking\nto the documents behind each line item, and a \"not allocated\" line with its total.","financeTry2":"Reconcile the bank statement [Tochka / Alfa / Sber — or the attached file] against the postings in 1C for [period].\nMatch operations by amount, date and counterparty. Collect separately: receipts and payments\nnot posted in 1C, postings with no bank operation, amount discrepancies within a single\noperation, likely duplicates.\nDon't force pairs: if an operation matched only by amount but not by counterparty or date —\nput it in \"needs a decision\", not in the matches.\nOutput an XLSX: a \"Discrepancies\" sheet linking to the operation number and source document, a\n\"Matched\" sheet and a total line — how many operations and what amount did not reconcile.","financeTry3":"Build a receivables report by counterparty as of [date] using 1C data.\nFor each customer: the amount owed, which documents it consists of, the payment term from the contract,\ndays past due, the date and amount of the last payment.\nCount overdue days from the contractual term, not from the shipment date. If the term is not filled in —\ndon't assume a standard 30 days, move the counterparty into a \"term not defined\" list.\nSort by overdue amount. Flag separately those whose debt has been growing for three months in a row,\nand those who pay reliably but late.\nAt the end — the total overdue amount and which five counterparties account for half of it.","financeTry4":"Prepare a reconciliation statement with [counterparty] for [period] using 1C and Diadoc data.\nMatch every UPD and VAT invoice from EDI against a posting in 1C by number, date and amount.\nCollect the discrepancies: a document exists in Diadoc but isn't posted in 1C, is posted in 1C but never arrived\nvia EDI, amounts or the VAT rate differ, the document was cancelled or replaced by a corrected one.\nDon't stop at a matching number: different contracts can share the same numbers —\nalso check the contract and the amount, otherwise move the row into \"needs a decision\".\nOutput the statement in the standard form broken down by dates and documents, a separate discrepancies sheet\nand the opening and closing balances — per our data and per the EDI documents.","financeTry5":"Check outgoing payments on the accounts for [period] against the statement and the postings in 1C.\nFind: payments with a matching payee and amount within [3 / 7 / 14] days, the same invoice or UPD\npaid by different payment orders, recurring payments that have no contract\nor acceptance act in 1C, and increases in the amount of a recurring payment.\nDon't treat scheduled recurring payments — [rent, leasing, payroll project] — as duplicates.\nDon't declare a payment a duplicate if the grounds differ: if the payment descriptions differ,\nmove the pair into \"looks similar, needs checking\".\nOutput a table: date, payee, amount, source document, suspicion type and the possible\noverpayment amount; at the end — how much money is worth reclaiming or cancelling.","financeTry6":"Build a payment calendar for [horizon: a week / two weeks / a month] based on account balances\nand the obligations in 1C.\nLay out the outflows by day: invoices due with their deadlines, taxes and contributions, payroll, loans\nand leasing, recurring payments. Mark which payments cannot be moved.\nInclude expected customer receipts as a single inflow line per day and only\nwhere the contractual payment date has already arrived; don't count sales reps' promises\nor \"they usually pay by Friday\".\nFind the first day the balance drops below the [minimum balance] and show the shortfall.\nOutput a day-by-day calendar and a list of payments that are candidates for moving, with a new date.","financeTry7":"Every morning at [time] send a Telegram summary of the accounts [list of accounts] for the previous day.\nFormat: opening and closing balance for each account and in total, total inflow and outflow,\nthe three largest receipts and the three largest payments with counterparty and description.\nIn a separate block — unusual operations: a payment above [threshold], a new payee never\npaid before, a payment on a weekend, a fee higher than usual.\nIf there were no operations — say exactly that, don't resend the previous summary and don't fill\nthe gap with average values.\nKeep the message within one screen: no tables and no explanations of why the balance changed.","financeTry8":"Check the attached invoice [PDF / photo / EDI document] before sending it for payment.\nCross-check against 1C: INN, KPP, bank account and bank — against the counterparty record; the subject, prices\nand amount — against the contract and this supplier's previous invoices; whether the same invoice\nhas already been paid or is already in the queue.\nTake the details from the body of the invoice, not from the email or the sender's signature. If a field is unreadable\nor missing in 1C, write \"not verified\" and don't substitute the value from a previous invoice.\nAt the end: what matched, what differed, whether there is a duplicate, and a verdict — pay, clarify or\nreject, with a one-line reason.","free":"Free","homeFooterCopyright":"© 2026 samreshuuu. All rights reserved.","integrationsAuthCredentials":"API key","integrationsAuthDevice":"Device code","integrationsAuthOauth":"OAuth","integrationsCatAds":"Ads","integrationsCatAnalytics":"Analytics","integrationsCatBanks":"Banks","integrationsCatContent":"Content","integrationsCatCrm":"CRM","integrationsCatDatabase":"Databases","integrationsCatDev":"Development","integrationsCatDocflow":"Document flow","integrationsCatGoogle":"Google","integrationsCatHr":"HR","integrationsCatLogistics":"Logistics","integrationsCatMarketplaces":"Marketplaces","integrationsCatMessengers":"Messengers","integrationsCatOther":"Other","integrationsCatPm":"Project management","integrationsCatYandex":"Yandex","integrationsHubEyebrow":"Integrations","integrationsStepCredentials1Desc":"Create a key in the service's account area — usually under \"API\" or \"Integrations\".","integrationsStepCredentials1Title":"Get an API key","integrationsStepCredentials2Desc":"Open Connectors, pick the service and paste the key — it is encrypted on save.","integrationsStepCredentials2Title":"Paste the key into Samreshuuu","integrationsStepCredentials3Desc":"Ask the agent a first question about the service's data — the link checks itself.","integrationsStepCredentials3Title":"Test the connection","integrationsStepDevice1Desc":"Click \"Connect\" — Samreshuuu shows a short device code.","integrationsStepDevice1Title":"Request a code","integrationsStepDevice2Desc":"Open the service's confirmation page and enter the code from this screen.","integrationsStepDevice2Title":"Enter the code in the service","integrationsStepDevice3Desc":"Once confirmed, the connection activates automatically.","integrationsStepDevice3Title":"Wait for confirmation","integrationsStepOauth1Desc":"The service's authorization window opens — you sign in on its side.","integrationsStepOauth1Title":"Click \"Connect\"","integrationsStepOauth2Desc":"Confirm the permissions Samreshuuu requests — you can revoke them at any time.","integrationsStepOauth2Title":"Grant access","integrationsStepOauth3Desc":"The service appears in your connections list, and the agent sees the data right away.","integrationsStepOauth3Title":"Done","interrupted":"(interrupted)","landingFooterColBusiness":"For business","landingFooterColCompany":"Company","landingFooterColCompare":"Compare","landingFooterColLegalTrust":"Legal & Trust","landingFooterColProduct":"Product","landingFooterColResources":"Resources","landingFooterCompareClaude":"vs Claude","landingFooterCompareGiga":"vs GigaChat","landingFooterCompareGpt":"vs ChatGPT","landingFooterCompareYa":"vs YandexGPT","landingFooterContacts":"Contacts","landingFooterCookieSettings":"Cookie settings","landingFooterCopyright":"© {year} samreshuuu. All rights reserved.","landingFooterDocs":"Documentation","landingFooterIntegrations":"Integrations","landingFooterOffer":"Offer","landingFooterPricing":"Pricing","landingFooterPrivacyPolicy":"Privacy Policy","landingFooterSkills":"Skills","landingFooterStatus":"Status","landingFooterTerms":"Terms","landingFooterTrust":"Security","landingFooterUseCases":"Solutions","landingNavApp":"App","landingNavAppDesc":"Desktop for Mac and Windows","landingNavBlog":"Blog","landingNavBlogDesc":"Articles and news","landingNavBookDemo":"Book a demo","landingNavDocsDesc":"Guides and reference","landingNavDocuments":"Documents","landingNavDocumentsDesc":"Contracts, proposals, reports","landingNavHelp":"Help","landingNavHelpDesc":"How to work with the agent","landingNavIntegrationsDesc":"1C, CRM, marketplaces","landingNavSecurityDesc":"TLS 1.3, AES-256, servers in Russia","landingNavSecurityDescGdpr":"TLS 1.3, AES-256, servers in the EU/EEA","landingNavSkillsDesc":"Catalog of skills and extensions","landingNavTasks":"Tasks","landingNavTasksDesc":"Trigger, agent, result","language":"Language","loading":"Loading...","login":"Log in","marketingNavDesc":"Campaigns, content, channel analytics","marketingNavLabel":"Marketing","marketingTry1":"Build a report on ad channels for [period — week from ... to ...] using data from Yandex Direct,\nVK Ads and Metrica.\nFor each channel and campaign: spend, clicks, conversions on goal [goal name in Metrica],\nrevenue from that goal, ROMI and the change versus [the previous week].\nCalculate ROMI only where revenue comes from Metrica. Where there is no revenue — don't substitute an average\norder value and don't carry it over from another channel, move such channels into a \"ROMI not calculated\" block\nand write what is missing.\nDon't explain a drop by seasonality until you show the same week a year ago.\nOutput XLSX: a sheet by channels, a sheet by campaigns and five lines of conclusions — what grew,\nwhat fell and where to move budget.","marketingTry10":"Collect [10] topics for a content plan for [month] for [Telegram / VK].\nFirst look at my publications over [period]: which formats and angles got above-average response,\nwhich topics repeated without result. Describe this in two or three lines before the topic list.\nGoals for the month: [warm-up / sales / audience growth] and events: [launch, season, date].\nEach topic: format, angle, who it's for, which goal it leads to and which facts it's built on.\nTake facts only from my materials. Don't make up cases, result figures and client quotes:\nwhere an example is needed — put [case needed] and describe which one exactly.\nDon't propose a topic if it already ran on my channel within [period] — or say how the new angle differs.\nOutput a table of topics and a week-by-week layout.","marketingTry2":"Write [5] post variants for the launch of [product and what changes in it] for [Telegram / VK].\nAudience: [who they are, what they already know about us, what stops them]. Offer and deadline: [what we offer].\nMake the angles different: usefulness, a specific pain, \"before and after\", handling an objection, news.\nRely only on the facts I gave. Don't invent numbers, deadlines, testimonials or client names:\nif a fact is missing for a strong line — leave a [gap] and write what to fill in.\nTake the tone from the attached posts, not from ad templates.\nOutput for each variant: the angle in one word, text within the platform limit, a call to action\nand a line \"who it's aimed at\".","marketingTry3":"Find where in Yandex Direct spend over [period] produced no result on goal [goal name].\nGo down the levels: campaign, ad group, ad, search phrase and ad network placement.\nInclude in the report only rows with spend above [threshold] — don't draw conclusions on smaller samples,\ncollect them in a separate \"not enough data\" line.\nDon't call a row wasted spend if it has conversions that are simply expensive: separate \"no conversions at all\"\nfrom \"cost above target\" — those are different decisions.\nSeparately show phrases with high CTR and zero conversions, and ad network placements with a bounce rate above [80%].\nOutput a table: level, name, spend, clicks, conversions, what you suggest doing\n(pause / add as negative / lower the bid) and how much money that frees up over [period].","marketingTry4":"Write a chain of three abandoned-cart emails: [how many hours until the first],\n[the second], [the third].\nMake the mechanics different: the first — a reminder and removing a technical barrier, the second — an answer\nto the reason for hesitation [delivery / price / size choice], the third — a deadline\n[what exactly is limited].\nWrite only about what I listed. Don't invent discounts, free delivery, \"only 2 left\",\ntestimonials and ratings: if a mechanic requires such a block — put [filled in\nfrom data] and describe where the value comes from.\nFor each email: three subject line variants and a preheader, the text, one button with its label, the send time\nand the condition under which the email doesn't go out (order paid, item out of stock).","marketingTry5":"Compare prices for my items on Wildberries with competitors using MPStats data as of [snapshot date].\nMy SKU list: [article numbers or category].\nTreat a competitor as comparable only on a match of [category, volume/size, composition, brand segment].\nDon't compare different pack sizes and bundles with single items — move such pairs into \"not comparable\"\nand explain how they differ.\nFor each SKU show: my price before and after discount, the median and the price range of competitors, the difference\nin percent, my stock and competitors' stock, the search position for [key query].\nFlag items where I'm above the median by more than [10%] while orders are falling, and where I'm the lowest\nof all but sales aren't growing.\nOutput a table by SKU and a short list: where the price is worth revisiting and in which direction.","marketingTry6":"Rewrite the listings [article numbers] on [Ozon / Wildberries]: title, specifications and description.\nTake buyer queries for this category and distribute them across the fields: the main ones — into the title\nand the first specifications, the rest — into the description, without listing them comma-separated.\nWrite only from the specifications in the listing and from what I attached. Don't add composition,\ncountry of origin, warranty, certificates or product properties: if a field is empty, put\n[to clarify] and move it into the list of missing data.\nRespect the platform's field limits and don't repeat a single keyword more than [3] times.\nOutput for each article number: the title, a specifications table, the description text, the list\nof queries used and the list of fields I have to fill in myself.","marketingTry7":"Link spend in Yandex Direct with leads in Bitrix24 for [period] via [source field / utm],\nreconcile conversions against Metrica.\nFor each channel and campaign calculate: spend, number of leads in CRM, CPL, number of leads\nin statuses [qualified] and the cost of a qualified lead.\nSeparately show quality: duplicates, spam and rejections with reason [not relevant], the share of leads\nleft untouched for longer than [N hours].\nDon't distribute leads without a source across channels proportionally — keep them as a separate line\n\"source not identified\" with their share of the total.\nShow the discrepancy between conversions in Metrica and leads in CRM as a number, don't smooth it over.\nDon't include revenue and deals in this report.\nOutput a table by channels, a table by campaigns and three lines: where CPL grew, where quality\nfell at the same CPL, where leads aren't being worked.","marketingTry8":"Analyse the finished campaign [name, dates] in Direct and Metrica and propose [5] hypotheses\nfor the next launch. Goal of the next launch: [what matters more — volume or cost].\nLook where the potential sits: segments with good conversion and small reach, creatives\nwith high CTR and a weak landing page, times and geographies with different cost per goal, devices,\nsteps on the landing page where people drop off.\nFrame each hypothesis like this: what we change, which numbers from this campaign it's built on,\nthe expected effect as a range, how we'll test it and on what budget.\nDon't pass off as a finding something explained by random spread on a small sample, and don't fit\nthe explanation to a decision already made — if there isn't enough data for a conclusion, call it an idea\nfor a test, not a hypothesis.","marketingTry9":"Calculate the economics of a [discount size] promo on [article number / product] on [Ozon / Wildberries]\nfor [period].\nTake the current price and the platform commission, cost from 1C, logistics, storage,\nacquiring and [ad cost share] for this product. Calculate margin per unit now and with the discount, the break-even\nsales uplift in units and percent, and profit in three scenarios: sales [+X%], [+Y%], [+Z%].\nIf I didn't specify some cost item — don't take a market average, put it as a \"not accounted for\" line\nand show how it moves the result.\nSeparately calculate the cannibalisation effect: how many sales will shift from [adjacent article numbers]\nand what that means for profit across the group.\nOutput a scenario table, the loss point and one line: at what uplift the promo makes sense.","monthly":"Monthly","name":"Name","onboardingGoalsChipUnitEconomics":"Unit economics","orderDeclineCardExpired":"The card has expired.","orderDeclineCardInvalid":"The card details are invalid.","orderDeclineCardRestricted":"The payment was declined by your bank.","orderDeclineGeneric":"The payment was declined.","orderDeclineInsufficientFunds":"Not enough funds on the card.","orderDeclineIssuerUnavailable":"Your bank is temporarily unavailable.","organization":"Organization","password":"Password","planFree":"Free","planLeadInFree":"Everything in Free and:","planLeadInPro":"Everything in Pro and:","planMaxName":"Max","planProName":"Pro","planTeamName":"Team","popular":"Popular","privacyTitle":"Privacy Policy","productNavDesc":"Research, feedback, specs","productNavLabel":"Product","productTry1":"From the Ozon and Wildberries reviews for [period] collect only product change requests: what is missing,\nwhat people ask to add, what they ask to bring back. Do not take complaints about delivery, packaging and support\ninto this list — count them on a separate line and stop there.\nGroup the requests by meaning, not by wording. For each group: frequency, share of all reviews\nfor the period, [3] verbatim quotes, the SKUs where it occurs.\nDo not turn a one-off wish into a trend: keep groups with fewer than [5] mentions in the\n\"weak signal\" section rather than in the main list.\nOutput a table: request, frequency, share, quotes, SKUs.","productTry2":"Compare our product with [a list of competitors or links to their sites] on features and pricing, and put the result\nin a Google Sheet.\nFor each competitor: pricing plans and prices, what each includes, limits and restrictions, the stated\nintegrations, who they position themselves for.\nBack every price and every feature with a link to the page and the date you saw it. Whatever is not on\nthe site — write \"not published\": do not infer it from a neighbouring plan, do not silently convert an annual price\ninto a monthly one, and do not carry what reviews and roundups say into the table as a fact about the product.\nOutput a \"Matrix\" sheet (rows — features, columns — competitors), a \"Sources\" sheet and a bottom line:\nwhere we are more expensive and which features we lack.","productTry3":"Build a draft PRD from [links to meeting notes, tickets, documents] and put it in Google Docs.\nStructure: the problem and who it hurts, what has already been tried, use cases, functional\nrequirements, what is out of scope, success metrics, open questions.\nMark every requirement with its source — a link to the note or a quote. If a decision was not made in the notes,\ndo not make it for the team: move it into open questions as options and state who is responsible.\nTake only metrics we already know how to measure; for the rest write which data source\nis missing.\nDuplicate the requirements as a sheet in Google Sheets: number, wording, source, status.","productTry4":"Read the backlog tasks in [Yandex Tracker / Kaiten], queue [name], and score each one\nby impact and effort.\nCount impact by [revenue / churn / support load] and by the number of users affected;\neffort — by the team's estimate, if it is set on the task.\nApply the [1–5] scale identically to all of them and attach a key explaining what each score means.\nDo not assign a score where the task has no description: collect those in a \"nothing to score\" list\nstating which information is missing. Do not pass your own guess about task size off as the team's estimate —\nmark where the effort came from.\nOutput a table: task, impact, effort, the rationale for each score, quadrant — and the ten tasks\nworth taking first.","productTry5":"Collect the feedback from Telegram, email and Ozon reviews for [period] and sort it by a single taxonomy\n[list of topics — or propose your own and show it for approval before the analysis].\nOne taxonomy for all three channels: the same topic is named identically in each. Assign every message\nto exactly one topic; put the debatable ones in \"unclassified\" and show them separately\nrather than splitting them across two topics at once.\nThe channels differ in volume, so besides the count compute the topic's share within its own channel — compare\nshares, not counts. Do not add the channels together into one overall ranking.\nOutput a \"topic × channel\" table: count, share within the channel, two quotes each — and a list of topics\nthat exist in only one channel.","productTry6":"Go through the Telegram tickets and the Ozon and Wildberries reviews for [quarter] and identify the five main user pain points.\nRank them not by mention frequency but by cost: how many users are affected and what happened to them\nafterwards — [left / did not buy again / reduced their basket].\nState the effect on churn and repeat purchases only where you computed it from data you actually\nsaw: attach which rows the figure was built from and how many people are in the sample. Where linking a ticket\nto subsequent behaviour did not work out — write \"effect not measured\" and leave the pain point in the list\nby frequency, instead of grading it with words like \"probably has an effect\".\nOutput five cards: the wording of the pain point, how many users are affected, [3] quotes, what happened to them\nafterwards — and, as a separate list, the hypotheses that the data does not confirm.","productTry7":"Break the feature [name and one or two sentences about its goal] into user stories and file them\nin [Yandex Tracker / Kaiten], in [queue or board].\nFor each story: the role, what they do, why; acceptance criteria as a list of checkable conditions;\nwhat is out of scope.\nSeparately go through the edge cases: empty state, external system failure, missing permissions,\nrepeated launch, cancellation midway.\nDo not invent requirements that are not in the description: where a decision has not been made, file a story\nmarked \"needs a decision\" with the question inside, rather than your own assumption presented as a requirement.\nOutput a list of stories with the dependencies between them and the order in which it makes sense to do them.","productTry8":"Build the week-by-week dynamics of negative reviews on Ozon and Wildberries for [period].\nCount [1–2 stars] as negative.\nFor each week: the share of negatives among all reviews that week, the number of reviews, a breakdown by complaint topic.\nCount the share specifically: growing sales lift the number of reviews too, and that in itself is not\na rise in negativity.\nMark the dates [list of shipped fixes] and for each topic show the share before and after. If less than\n[3] weeks have passed since the date or the week has fewer than [20] reviews — write \"too early to judge\"\nand do not call it an improvement.\nOutput a week-by-week table, a breakdown by topic and a list of topics where the share of negatives has grown for the third\nweek in a row.","profile":"Profile","pulsePetNameBear":"Bear","pulsePetNameBunny":"Bunny","pulsePetNameCat":"Cat","pulsePetNameCrab":"Crab","pulsePetNameFatcat":"Baton","pulsePetNameFox":"Fox","pulsePetNameGenBear":"Bear","pulsePetNameGenBunny":"Bunny","pulsePetNameGenCat":"Cat","pulsePetNameGenCrab":"Crab","pulsePetNameGenFatcat":"Baton","pulsePetNameGenFox":"Fox","pulsePetNameGenPanda":"Panda","pulsePetNameGenPenguin":"Penguin","pulsePetNamePanda":"Panda","pulsePetNamePenguin":"Penguin","relatedGuidesHeading":"Guides on this topic","renewalOffUntil":"Active until {date}, won't renew","resLinkAiAgents":"AI agents for business: what they are","resLinkAiBusiness":"AI for business: which solution to choose","resLinkAmocrm":"How to connect AI to amoCRM","resLinkAnalytics":"AI for marketplace analytics","resLinkBitrix":"How to connect AI to Bitrix24","resLinkBitrixAgents":"Best AI agents for Bitrix24","resLinkCards":"Optimizing WB and Ozon cards with AI","resLinkConnectors":"How to connect your business to AI: integration catalog","resLinkDashboard":"AI for sellers: dashboard, generator, agent","resLinkDocs":"AI for acts and closing documents","resLinkDocsFeature":"AI for documents: creation and recognition","resLinkGeo":"What is GEO, explained simply","resLinkIntegration":"{name} integration","resLinkIntegrationsCrm":"CRM integrations","resLinkIntegrationsHub":"Integration catalog for business","resLinkIntegrationsMarketplaces":"Marketplace integrations","resLinkMango":"AI for Mango Office telephony","resLinkMoysklad":"How to connect AI to MoySklad","resLinkOzon":"How to connect AI to Ozon","resLinkPriceAuto":"Automated repricing with AI","resLinkPricing":"AI pricing on marketplaces","resLinkReviews":"Auto-replies to Wildberries and Ozon reviews","resLinkRuAssistants":"Top Russian AI agents for business","resLinkSellerAuto":"How a seller can automate their business with AI","resLinkTopReviews":"10 review auto-reply services","resLinkTranscript":"AI speech analytics for calls","resLinkVsZapier":"AI agent or Make, Zapier, n8n","resLinkWb":"How to connect AI to Wildberries","retryCooldown":"Retry in {seconds} sec","salesNavDesc":"Leads, follow-up, quotes, forecast","salesNavLabel":"Sales","salesTry1":"Go through the new leads in Bitrix24 for [period — yesterday / the last 24 hours / since the last triage].\nFor each: source, what they're asking for, budget ballpark, region, contacts, whether this company is\nalready in CRM.\nAssign priority by the rules: [budget above threshold / target industry / repeat enquiry].\nIf there isn't enough data for priority — don't infer it from the company name and email domain,\nmark it \"not enough data\" and leave it in the general queue. Flag possible duplicates of open deals,\nbut don't merge them.\nOutput a table: lead, priority, suggested owner, deadline for first contact.\nAs separate lists — duplicates and leads without contacts. Create tasks only after\nI confirm the list.","salesTry2":"Build a proposal for deal [number or deal name in Bitrix24],\nusing template [link to document].\nTake the legal details, contact person and scope of work from the deal card, prices — from [price list],\npayment terms and the discount — by the rules: [rules].\nDon't fill blanks with plausible text: if CRM has no deadline, volume or contact\nperson — leave a [to clarify] marker in the document and collect all such spots in a separate list at the end.\nDon't round or recalculate prices yourself.\nOutput — a document following the template's structure, without extra blocks, followed by a list\n\"what to clarify before sending\".","salesTry3":"Find open deals in Bitrix24 that have no active task or no activity for longer\nthan [N] days, across pipelines [list of pipelines].\nFor each: amount, stage, owner, date and type of the last contact, date of the nearest task,\nif there is one.\nCount as contact only real activity — a call, an email, a meeting, a comment.\nDon't count a stage change or an automatic field update as contact and don't use it as a sign\nthat the deal is alive.\nGroup by manager, and within that by amount. Separately pull out deals with no owner\nand deals whose close date has already passed.\nAt the end — how many deals in total and for what amount are stuck.","salesTry4":"Find deals in Bitrix24 where a proposal was sent more than [N] days ago and there's no reply from the client,\nand prepare a draft follow-up email for each.\nBefore the email, gather the context: what was in the proposal, what was agreed on the last call,\nwhich objections have already come up.\nTake the reason for writing from the communication history. If there's nothing in the correspondence to hook onto — don't invent\nthe client's interest and don't refer to a conversation that never happened, write a short neutral email\nand mark it \"no context\".\nDon't offer discounts or new terms — only [permitted reasons].\nOutput a table: client, amount, days of silence, email subject — and the text of each email\nup to 120 words as a draft, without sending.","salesTry5":"Build the [quarter] sales summary from Bitrix24 and amoCRM and compare it with [the previous period].\nGive plan versus actual on revenue overall and by [breakdown — line of business / manager / region]: plan,\nactual, variance.\nFor each manager: closed amount, number of deals, average deal size, share of the total actual.\nSeparately — the five largest won and five lost deals with the stated loss reason.\nDon't add up deals from the two systems until you show that their stages and statuses are comparable;\ncount what isn't comparable separately and say so.\nBuild the forecast for the next quarter from open deals with a close date inside it, honestly\nstating the share of deals with no date.\nOutput XLSX: \"Plan vs actual\", \"Managers\", \"Deals\", a totals line.","salesTry6":"Find open deals in Bitrix24 and amoCRM above [threshold] that have been sitting at their stage\nlonger than the norm: [stage — period; stage — period].\nFor each deal: amount, stage, how many days it's been sitting, owner, last contact,\nwhose court the ball is in — ours or the client's.\nTake the reason it stalled from comments and correspondence. If it isn't there — don't infer the reason\nfrom the stage and the amount, write \"reason not recorded\" and set \"find out the status\" as the first action.\nFor each deal propose one specific action for this week and state what you need from me.\nDon't calculate stage conversion percentages — a list of deals is what's needed.\nSort by amount, with what can be closed before the end of [the period] on top.","salesTry7":"Assemble the sales summary for the past week from Bitrix24 and send it to Telegram\n[day and time].\nIn the summary: closed amount and number of deals versus last week, movement on large deals,\nnew leads and how many of them were picked up.\nFor each manager — a short line: closed, in progress, activity.\nSeparately name the areas of attention: whose result is falling for the second week running, who has no\nsingle contact on large deals, where the week fell outside the usual range.\nDon't call a one-off dip or spike a trend until it has repeated twice.\nKeep the summary to [15] lines: details — as a separate file on request.","salesTry8":"Reconcile the payment promises from Bitrix24 deals against actual receipts in 1C as of [date]\nand find clients with no payment for longer than [N] days.\nFor each: the promised date and amount, who recorded it and when, what actually arrived,\nhow many times the deadline was pushed, the date of the last conversation, the owning manager.\nLink client and payment by legal details. If a payment arrived without a link to a deal —\ndon't assign it to the nearest one by amount, move it into \"unidentified payments\".\nDon't reconstruct promises that aren't in CRM by logic: write \"agreement not recorded\".\nSort by amount. For each client propose the next step: a call, an email, escalation\nor handover to receivables collection.","samreshuuu":"samreshuuu","search":"Search","securityNavLabel":"Security & 152-FZ","securityNavLabelGdpr":"Security & GDPR","sellersChapter1Label":"Unit economics","sellersDemoTab1Prompt":"Build a payables report for suppliers as of [date] using [MoySklad / 1C] data\nand the account balances from Tochka.\nFor each supplier: the amount owed, which delivery documents it consists of, the payment term\nfrom the contract, days past due, the date and amount of the last payment.\nTake the term from the contract or the delivery terms. If the term isn't filled in — don't assume the usual\n14 days, move the supplier into a \"term not defined\" list.\nSpread the payments across the days of [period] so that the balance covers each day. If it doesn't —\nshow the day and the size of the gap instead of silently trimming the amounts.\nOutput an XLSX: a \"Payment queue\" sheet with date, amount and the reason for the priority, a\n\"Deferred\" sheet and a total line — how much is due and how much money is available.","sellersDemoTab2Label":"Unit economics","sellersNavDesc":"Unit economics, listings, reviews","sellersNavLabel":"Sellers","settings":"Settings","signup":"Sign up","skills":"Skills","status":"Status","suggestionWbReviews":"Wildberries reviews","supportNavDesc":"Requests, reviews, knowledge base","supportNavLabel":"Support","supportTry1":"Go through the tickets from Telegram, Avito and email that arrived between [shift close time] and [opening\ntime], and assemble a queue for the morning.\nPut the urgent ones on top: [payment went through, goods never arrived / repeat ticket about the same problem /\nthreat of a complaint or a return]. Below them — questions about availability and delivery times.\nAttach a draft reply to routine tickets. If the reply needs an order status that is not in the correspondence,\ndo not guess it — put [check in 1C] and leave the ticket for an operator.\nOutput a list: time, channel, customer, substance in one line, urgency, draft or \"needs a human\".","supportTry2":"Write replies to new Ozon and Wildberries reviews for [period] following the tone rules from [the attached\nfile / the examples below].\nSplit the reviews into three groups: reply with a template, reply individually, do not reply —\nand for each group name the signal you used to decide.\nIn the reply, state the substance of the complaint in your own words, do not open with \"thank you for your review\".\nDo not promise deadlines, refunds, discounts or replacements — nobody has confirmed those. Where the customer directly\nasks for goodwill compensation, leave [operator decision] in the text and move the review into the \"for a human\" group.\nOutput a table: review, rating, SKU, group, reply text, what to fill in by hand.","supportTry3":"Watch new reviews on Ozon and Wildberries and flag only what threatens the rating.\nThreshold: rating [1–2]; or [3] and below for an SKU from the list [priority SKUs]; or [2] negative\nreviews on one SKU within [24 hours]; or the words [defect, scam, swap, court, consumer protection agency].\nOne review — one alert, do not write about the same one twice.\nDo not raise an alarm for a rating without text or for a review about the marketplace's delivery — collect those in a separate\nsummary once per [period].\nIn the notification: SKU and name, rating, date, the full quote from the review, the listing's current rating\nand how much it moved, how many reviews this SKU got in [7 days].","supportTry4":"Go through the customer complaint from [the Telegram correspondence / the email] and propose goodwill compensation strictly\nby the rules in [the attached file].\nFirst pull out the facts: what was bought and when, what went wrong, what the customer asks for verbatim, which\nticket this is in order. Whatever is not stated in the correspondence — mark \"not specified\", do not fill it in.\nThen find the matching rule clause and name its number. If no clause fits or the amount\nexceeds the limit — say so, propose the closest option within the rules and send the case\nfor approval instead of stretching the rule yourself.\nIn the draft reply do not promise deadlines, refunds or replacements beyond the chosen clause.\nOutput: facts, rule clause, proposal, draft letter.","supportTry5":"Collect the recurring questions from tickets in Telegram, Avito and email for [period] and turn them\ninto knowledge base articles.\nGroup by the meaning of the question, not by matching words: \"when will it arrive\" and \"where is my parcel\" are one article.\nTake only topics that occurred at least [N] times, put the rest in a \"rare\" list.\nThe title uses the customer's wording, the answer comes from real operator replies with a link\nto the source ticket. Where operators answered differently, do not pick the correct version yourself:\nshow both answers and mark the article \"needs a decision\".\nOutput articles with the fields question, answer, source, ticket count — in descending order of frequency.","supportTry6":"Sort the tickets from Telegram, Avito and email for [period] by topic and count the load by week.\nTake the classifier from [the attached list of topics] or build your own and show it to me before the analysis.\nOne ticket — one topic; a conversation stretching over several days counts once, by the date of the first\nmessage.\nFor each topic: tickets per week, change against the previous week, distribution by day of week\nand by hour [time zone].\nA spike caused by a promotion, an outage or holidays goes on a separate line and is not mixed into the trend.\nOutput a \"topic × week\" table, a \"day of week × hour\" table and the three fastest growing topics.","supportTry7":"Merge the new messages from Telegram, Avito and email for [period] into a single queue.\nMerge messages from one customer into a single thread by [phone / email / order number]. If only the name\nmatched — do not merge: keep the rows separate and add a \"possible duplicate\" flag.\nSet the order like this: the primary key is [waiting time], with equal waiting time these go higher: [repeat\nticket / mention of payment or a refund / customer with status X].\nDo not write replies: each row contains only the substance of the ticket in one phrase.\nOutput a queue: time of the first message, how long it has waited, channel, customer, substance, priority\nand the condition it was assigned by.","supportTry8":"Build reply templates from the Telegram and email correspondence for [period].\nIdentify the situations that occurred at least [N] times, and write a template for each in the tone\nfrom [the attached examples].\nEverything that changes case by case — name, order number, deadline, amount — stays as a field\n[in square brackets]; do not fill in a typical value, or the operator will send someone else's deadline.\nDo not write deadlines, refunds, discounts and goodwill compensation into the text: put a field [decision per the rules]\nand note who is entitled to fill it in.\nFor each template: when to use it, when not to use it, what to fill in.\nOutput a table of templates in descending order of situation frequency.","team":"Team","ucBackToList":"All use cases","ucBankReconBest1":"Month-end close, when the statement and 1C disagree and you need to find exactly where.","ucBankReconBest2":"Several current accounts and a heavy flow of small payments — impossible to reconcile by hand.","ucBankReconBest3":"Not a fit if the postings for the period haven't been entered yet: there is nothing to reconcile against.","ucBankReconCheck":"Review your reconciliation. List:\n— operations matched on fewer than all three attributes;\n— discrepancies explained by a shifted payment date rather than an error;\n— counterparties that have several similarly named records in 1C;\n— rows where the counterparty was inferred from the payment description rather than from the bank details;\n— the total discrepancy amount and which rows make it up.\nDon't fix anything silently: whatever you can correct yourself, show as a \"proposed changes\" list.","ucBankReconInputs":"1C and the bank (Tochka or a statement in 1C format). From you: the list of accounts and the period.","ucBankReconStep1Desc":"The agent reads the statement and the postings directly, nothing needs to be exported. If there are several accounts, name the ones we are reconciling.","ucBankReconStep1Title":"Grant access and set the period","ucBankReconStep2Desc":"The agent matches on all three attributes at once and doesn't merge operations that agree only on the amount.","ucBankReconStep2Title":"Run the reconciliation","ucBankReconStep3Desc":"Before taking it to the accountant — make the agent review its own work","ucBankReconStep3Title":"Check the result","ucBestFor":"Who it fits","ucBottlenecksBest1":"A stand-up where you need to go through specific deals and decisions on them, not the pipeline in general.","ucBottlenecksBest2":"The quarter is ending and you need to work out which stuck deals can still realistically be pulled through.","ucBottlenecksBest3":"Not a fit if stages are maintained formally and a deal is only moved at the moment of payment: stalling will look the same everywhere.","ucBottlenecksCheck":"Check the analysis of stuck deals. List:\n— deals where the reason for stalling was guessed rather than taken from the correspondence;\n— deals stuck for an external reason — a tender, the client's budget, the decision maker's holiday — where pushing is pointless;\n— deals that are effectively lost and should be closed rather than analysed;\n— duplicates of the same deal created in both CRMs;\n— proposed actions that have already been tried and didn't work;\n— deals where the time at stage is counted from creation rather than from entering the current stage.\nEdit the wording of the actions yourself; leave the decision to close a deal or not to me.","ucBottlenecksInputs":"Bitrix24, amoCRM. Manually: a normal duration for each stage and the amount threshold below which it isn't worth digging.","ucBottlenecksStep1Desc":"Say how many days a deal normally sits at each stage — from your experience, not from an average. Set an amount threshold so small deals you won't have time for anyway don't get into the analysis.","ucBottlenecksStep1Title":"Set the norms","ucBottlenecksStep2Desc":"The agent picks out deals that have exceeded the norm for their stage, pulls the reason for stalling from the correspondence and proposes one action for each.","ucBottlenecksStep2Title":"Assemble the list","ucBottlenecksStep3Desc":"The list will become the stand-up agenda, and going through a deal that was actually lost long ago will eat the whole team's time.","ucBottlenecksStep3Title":"Check the result","ucCardSeoBest1":"Many listings were created, descriptions were copied from the supplier and they don't show up in the platform's search.","ucCardSeoBest2":"A product is being launched on a second platform, and the text needs rebuilding for its limits and field structure.","ucCardSeoBest3":"Not a fit if the product's real specifications aren't filled in: empty fields will produce text without a single concrete fact.","ucCardSeoCheck":"Check the listing descriptions. List:\n— specifications that weren't in the source data — composition, country, warranty, certification;\n— claims the platform might consider unprovable: \"the best\", \"hypoallergenic\", \"certified\";\n— fields where the character limit is exceeded or the platform's structure is broken;\n— queries you inserted for search volume rather than for the product's meaning;\n— listings where the description came out generic because there weren't enough facts.\nAt the end: which listings can be uploaded and which are waiting on data from me.","ucCardSeoInputs":"Ozon, Wildberries. Manually: the list of listings, priority queries or your keyword set if you have one, the platform's field requirements.","ucCardSeoStep1Desc":"Give the article numbers and everything you have on the product: the supplier's spec sheet, measurements, composition. The more facts, the fewer generic words remain in the text.","ucCardSeoStep1Title":"Select the listings and the data","ucCardSeoStep2Desc":"The agent distributes queries across the fields instead of dumping them at the end of the description, and flags everything that wasn't in the source data.","ucCardSeoStep2Title":"Run the rework","ucCardSeoStep3Desc":"A product description is the seller's statement about its properties, and an invented line in it costs more than a search position","ucCardSeoStep3Title":"Check the result","ucCartEmailsBest1":"Carts get abandoned and nothing follows except one \"you forgot an item\" email.","ucCartEmailsBest2":"There is a chain, but all three emails are about the same thing and the last one just repeats the first.","ucCartEmailsBest3":"Not a fit if the cart contents aren't passed to the mailing: without items and totals the emails become impersonal.","ucCartEmailsCheck":"Check the email chain. List:\n— promises I never made: discounts, delivery times, return guarantees;\n— numbers and testimonials you wrote yourself instead of marking as a placeholder;\n— places where the second and third emails repeat the first instead of adding an argument;\n— subject lines that lead to spam: caps, \"free\", extra punctuation;\n— emails that will arrive at a bad moment — at night, the day after payment;\n— what a lawyer needs to check if the offer has a deadline.","ucCartEmailsInputs":"Unisender, Email. Manually: the assortment and average order value, which discounts you're willing to give, legal limits on the offer.","ucCartEmailsStep1Desc":"Name the discount you're actually willing to give and on what — otherwise the third email will promise something that doesn't exist. Say which fields you can pull from the cart: items, total, reservation time.","ucCartEmailsStep1Title":"Describe the boundaries","ucCartEmailsStep2Desc":"The agent keeps three different mechanics and marks placeholders instead of writing pretty numbers straight into the text.","ucCartEmailsStep2Title":"Run the writing","ucCartEmailsStep3Desc":"The email goes out to the whole list, and a mistake in one block multiplies across every recipient","ucCartEmailsStep3Title":"Check the result","ucCashDigestBest1":"An owner or CFO who wants to see the accounts before the first meeting without opening the bank client.","ucCashDigestBest2":"Several legal entities or accounts with money moving back and forth, blurring the overall picture.","ucCashDigestBest3":"Not a fit if decisions are made on the balance right now: the summary describes yesterday, not the current balance.","ucCashDigestCheck":"Review the summaries for the last [7] days. List:\n— days where the closing balance didn't match the next day's opening balance;\n— operations that landed in \"unusual\" more than once — it's time to treat them as regular;\n— transfers between our own accounts counted as both an inflow and an outflow;\n— days with no operations: was the summary sent or silently skipped;\n— counterparties you called new although they had been paid before.\nSuggest which large-amount threshold fits our turnover more accurately.","ucCashDigestInputs":"Tochka, Telegram. From you: the send time, the list of accounts and the rule for what counts as an unusual operation.","ucCashDigestStep1Desc":"Name the large-amount threshold and what counts as an anomaly for you: a new payee, a weekend payment, a payment above the limit. Without this, the \"unusual\" block turns into a list of every operation.","ucCashDigestStep1Title":"Set the rule for what's unusual","ucCashDigestStep2Desc":"The agent runs on its own at the set time, reads the previous day's account operations and sends a message to your chat.","ucCashDigestStep2Title":"Set the schedule","ucCashDigestStep3Desc":"For the first week, check the summary against the bank client — that's how you'll see whether the threshold is too high and whether the thing you set this up for is drowning in noise","ucCashDigestStep3Title":"Check the result","ucCashFlowBest1":"Reporting for a bank, an investor or the board, where what's needed isn't account turnover but the structure of the cash flow.","ucCashFlowBest2":"There is profit but no cash — you need to see where it went: into inventory, into receivables or into loan repayment.","ucCashFlowBest3":"Not a fit if cash flow line items aren't filled in in 1C: there is nothing to assign operations to activity types by.","ucCashFlowCheck":"Review the cash flow statement. List:\n— the difference between the calculated closing balance and the statement balance, if there is one;\n— operations from \"needs classification\" and why the section couldn't be determined;\n— internal transfers between accounts: did you net them out or count them as turnover;\n— payments assigned to a section by payment description rather than by the cash flow item in 1C;\n— large one-off operations that distort the period's operating flow.\nWhatever you can reclassify by the rule, show as a list; leave the rest to me.","ucCashFlowInputs":"1C, Tochka. From you: the period and the rules for assigning debatable line items to activity types.","ucCashFlowPrompt":"Build a cash flow statement for [period] using 1C and bank data.\nAssign all receipts and payments to three sections: operating, investing, financing\nactivities. For each section — line items with amounts, inflow, outflow and net flow; above\nand below — the cash balance at the start and end of the period.\nDon't count transfers between our own accounts or currency conversion as either a receipt or a payment.\nIf the activity type for an operation isn't obvious, don't default it to operating —\nmove it into \"needs classification\" with the amount and the payment description.\nOutput an XLSX: a \"Cash flow statement\" sheet by section, a details sheet with links to the operations, and a control\nline — does the closing balance agree with the bank statement.","ucCashFlowStep1Desc":"Say where leasing, founder loans and equipment bought in installments should go, if you have an established practice. Otherwise the agent will move them into a separate list.","ucCashFlowStep1Title":"Set the period and the debatable rules","ucCashFlowStep2Desc":"The agent reads the postings and the statement, assigns operations to activity types and checks the closing balance against the actual account balance.","ucCashFlowStep2Title":"Build the statement","ucCashFlowStep3Desc":"A cash flow statement is verified by one number: the closing balance must match the bank — if it does, look for errors in the classification","ucCashFlowStep3Title":"Check the result","ucCashGapBest1":"Monday, when you have to decide which invoices go out for payment this week and which ones can wait.","ucCashGapBest2":"Several accounts and fixed dates — taxes, payroll, leasing — that cannot be moved.","ucCashGapBest3":"Not a fit if planned payments aren't recorded anywhere: building a calendar solely from past payments makes no sense.","ucCashGapCheck":"Review the calendar. List:\n— inflow lines placed on a date that isn't in the contract;\n— payments without a deadline that you spread across days at your own discretion;\n— fixed-date obligations that ended up in the \"move\" list — those must not be touched;\n— partially paid invoices: what amount is left and which day you placed it on;\n— the gap day and the shortfall — which rows it is made of.\nSeparately, say whether the gap disappears if the largest expected payment is removed.","ucCashGapInputs":"Tochka, 1C. From you: the planning horizon, the list of non-movable payments and the minimum account balance.","ucCashGapStep1Desc":"Make sure invoices due and their deadlines are entered in 1C, and name the payments that cannot be moved. Set the minimum balance that must not be breached.","ucCashGapStep1Title":"Collect the obligations","ucCashGapStep2Desc":"The agent takes account balances from the bank, lays the obligations out by date and looks for the first day with a negative balance.","ucCashGapStep2Title":"Build the calendar","ucCashGapStep3Desc":"A gap most often appears or disappears because of a single optimistic inflow line — check that one specifically","ucCashGapStep3Title":"Check the result","ucCategoryRecipesHeading":"Ready-made use cases","ucCheckPrompt":"Check the result","ucCheckPromptHint":"A second prompt — the agent uses it to review its own work and show what's left for you.","ucClosingDocsBest1":"Month-end close, when some acts and UPDs arrived via EDI, some by email, and some didn't arrive at all.","ucClosingDocsBest2":"An audit or an accounting request: you need to show quickly which sales aren't backed by documents.","ucClosingDocsBest3":"Not a fit if a significant share of primary documents travels on paper: the agent won't see them and will record them as missing.","ucClosingDocsCheck":"Review the package. List:\n— sales where a document was found by amount but the number or date didn't match;\n— counterparties on the \"missing\" list whose document is in email but not in EDI;\n— documents sent but not signed — those cannot be counted as closed;\n— continuing services where the act legitimately belongs to the next month;\n— the bottom line: how many sales are closed and for what amount documents are missing.\nDon't send the draft letters: show as a list who you intend to write to and with what text.","ucClosingDocsInputs":"1C, Diadoc, Email. From you: the month being closed and the list of counterparties whose document flow runs outside EDI.","ucClosingDocsPrompt":"Assemble the package of closing documents for [month] using 1C, Diadoc and email data.\nFor each counterparty, match the sale or service rendered against the acceptance act, the UPD\nand the VAT invoice: what is signed by both sides, what was sent and is hanging unsigned,\nand what is missing altogether.\nA document sent via EDI and not signed by the counterparty does not count as received —\nthat's a separate status, not a closed position.\nDon't fill a gap with a similar document from an adjacent month: if the number and date don't agree\nwith the sale, mark it \"not matched\".\nOutput an XLSX: a counterparty sheet with the status of every document, a \"missing\" sheet\nwith amounts, and draft letters to the counterparties on that sheet — one letter per counterparty.","ucClosingDocsStep1Desc":"Name the counterparties whose documents travel on paper or through their own portal — otherwise they will end up on the missing list for no reason.","ucClosingDocsStep1Title":"Set the month and the exceptions","ucClosingDocsStep2Desc":"The agent checks every sale in 1C against the documents in Diadoc and the email attachments and sorts the result by status rather than by \"there or not\".","ucClosingDocsStep2Title":"Assemble the package","ucClosingDocsStep3Desc":"The letters go to counterparties, so the \"missing\" list is worth rereading: some of the documents usually sit somewhere the agent didn't look","ucClosingDocsStep3Title":"Check the result","ucCompensationBest1":"Goodwill compensation is handed out by each operator's own judgement, and identical cases end with different amounts.","ucCompensationBest2":"The complaint is long and emotional, and you need to pull out quickly what exactly is being asked for.","ucCompensationBest3":"Not a fit if there are no written compensation rules: without them the agent will start inventing the norms itself.","ucCompensationCheck":"Check your analysis of the complaint. List:\n— facts taken not from the correspondence but inferred by implication;\n— the rule clause you applied and how the case differs from it;\n— places in the draft that promise something the chosen clause does not cover;\n— the customer's requests left unanswered in the draft;\n— signs that this is a repeat ticket about the same problem;\n— what can be sent as is and what the manager must approve.","ucCompensationInputs":"Telegram, Email. By hand: the compensation matrix with limits and exceptions, the order history.","ucCompensationStep1Desc":"Attach the compensation matrix — limits, conditions, exceptions — and the order history. \"How we usually do it\" told verbally does not work: the agent cannot tell a norm from a one-off precedent.","ucCompensationStep1Title":"Give the rules","ucCompensationStep2Desc":"The agent collects the facts from the correspondence, picks a clause and stops if the case does not fit it, instead of rounding in the customer's favour.","ucCompensationStep2Title":"Run the analysis","ucCompensationStep3Desc":"A proposal on a complaint becomes the company's promise the moment it is sent — taking it back costs more than proofreading now","ucCompensationStep3Title":"Check the result","ucCompetitorsBest1":"Revising pricing or positioning, when you need not an eyeball estimate but a table you can defend in front of management.","ucCompetitorsBest2":"Preparing a comparison for the sales team: what to counter with when a customer names a competitor.","ucCompetitorsBest3":"Not a fit if the competitors do not publish prices but quote on request: there will be nothing to compare beyond the feature list.","ucCompetitorsCheck":"Check the comparison. List:\n— cells with no source link and why they are filled in;\n— prices converted to another period or currency, and how you converted them;\n— features you judged identical for us and the competitor by name rather than by description;\n— anything taken from roundups, reviews or press releases rather than from the product site;\n— pages whose update date is older than [6] months;\n— which of the conclusions are verifiable against the sources and which are your interpretation of positioning.","ucCompetitorsInputs":"Google Sheets. By hand: the list of competitors or links to their sites, the list of features we compare on, the snapshot date.","ucCompetitorsStep1Desc":"Name the competitors and the 10–15 features the decision is actually made on. Without your own list the agent will take the structure from the first competitor's site, and the comparison will come out shaped by their worldview.","ucCompetitorsStep1Title":"Assemble the list and the comparison frame","ucCompetitorsStep2Desc":"The agent walks the sites and pricing pages, fills in the matrix and keeps a sources sheet alongside — a link and a date for every cell.","ucCompetitorsStep2Title":"Run the collection","ucCompetitorsStep3Desc":"Before showing the table to anyone else — check where the data is and where the guesswork is","ucCompetitorsStep3Title":"Check the result","ucContentPlanBest1":"The content plan is put together on the last day of the month and half the topics come off the top of someone's head.","ucContentPlanBest2":"There are publications, but they're all about the product, and there isn't a single topic people read to the end.","ucContentPlanBest3":"Not a fit if there are few posts in the channel: the agent has nothing to work out what resonates with your audience from.","ucContentPlanCheck":"Check the content plan. List:\n— topics that repeat posts already published, and how the angle differs;\n— conclusions about \"what resonates\" drawn from fewer than [10] publications;\n— topics that need a fact or a case I don't have;\n— numbers and examples you invented yourself;\n— the imbalance: how many topics are about the product, how many are useful, how many lead to a sale;\n— topics that won't fit into a week in terms of effort — filming, interviews, approvals.\nAt the end: which three topics I can put into the plan right away and which need preparation.","ucContentPlanInputs":"Telegram, VK Ads. Manually: the month's goals, product events and dates, topics you must not touch.","ucContentPlanStep1Desc":"Name the product events with dates and the goals — otherwise you'll get an even stream of topics without a single one leading to a sale. Say what must not be written about.","ucContentPlanStep1Title":"Set the month's boundaries","ucContentPlanStep2Desc":"The agent first goes through your past publications and only then proposes topics, marking the places where it needs a case from you.","ucContentPlanStep2Title":"Run the selection","ucContentPlanStep3Desc":"The monthly plan is approved once, and weak topics then get written up in a rush","ucContentPlanStep3Title":"Check the result","ucCopied":"Copied","ucCopy":"Copy","ucCplDashBest1":"CPL is counted in the ad account, but there are fewer leads in CRM and nobody knows where they're lost.","ucCplDashBest2":"Channels bring traffic of different quality, and comparing them by a single cost per lead no longer makes sense.","ucCplDashBest3":"Not a fit if leads arrive in CRM without a source: there'll be nothing to link spend to a lead by.","ucCplDashCheck":"Check the leads dashboard. List:\n— the share of leads that didn't link to a campaign, and how that changes CPL for each channel;\n— channels where there are fewer leads in CRM than conversions in Metrica, and the possible reasons;\n— campaigns where CPL is calculated on fewer than [10] leads;\n— duplicates: by what attribute you merged them and how many leads were lost in the process;\n— channels where quality fell because of one manager rather than because of the traffic.\nMark what you can recalculate yourself and where the CRM data needs cleaning.","ucCplDashInputs":"Yandex Direct, Yandex Metrica, Bitrix24. Manually: the period, which statuses in Bitrix count as a qualified lead, the source field.","ucCplDashStep1Desc":"Name which status in Bitrix counts as a qualified lead — the whole second half of the report depends on it. Specify which field holds the source.","ucCplDashStep1Title":"Agree on the status","ucCplDashStep2Desc":"The agent matches by tag, not by date and name, and doesn't smear leads without a source across channels just to make the table add up.","ucCplDashStep2Title":"Run the merge","ucCplDashStep3Desc":"Channels get cut at the stand-up based on these numbers, so it's better to show the gaps in the linkage yourself","ucCplDashStep3Title":"Check the result","ucDebtorClientsBest1":"The manager is sure the client is about to pay — but the promise was made three weeks ago.","ucDebtorClientsBest2":"Before the call round you need to know who is simply late and who has already pushed the date twice.","ucDebtorClientsBest3":"Not a fit if payment agreements live in the manager's head and never reach CRM: there'll be nothing to reconcile.","ucDebtorClientsCheck":"Check the reconciliation of promises and payments. List:\n— clients whose payment came from a different legal entity and therefore didn't match;\n— payments assigned to a deal by a matching amount rather than by a document;\n— clients where the promise was reconstructed from correspondence rather than recorded in CRM;\n— cases where the payment was partial and the client formally met the condition;\n— amounts that can't be quoted to the client until accounting confirms them;\n— clients on deferred payment or instalments whose due date hasn't arrived yet.\nPropose the next steps yourself; escalation and handover to receivables collection only through me.","ucDebtorClientsInputs":"Bitrix24, 1C. Manually: the threshold in days and the snapshot date.","ucDebtorClientsStep1Desc":"Name the date and the threshold in days — it should match what managers consider a normal delay. Specify which CRM fields mean a payment promise for you: a comment, a task or a separate date field.","ucDebtorClientsStep1Title":"Set the snapshot","ucDebtorClientsStep2Desc":"The agent reads the promises in CRM and the receipts in 1C, links them by the payer's legal details and doesn't attribute someone else's payment to a client just because the amount matched.","ucDebtorClientsStep2Title":"Reconcile against the facts","ucDebtorClientsStep3Desc":"The manager goes to the client with this list: a debt figure named by mistake nullifies the conversation.","ucDebtorClientsStep3Title":"Check the result","ucDebtorRemindBest1":"Payment reminders are written by hand and remembered a month after the due date.","ucDebtorRemindBest2":"You want the money conversation to follow one script across all sales reps rather than their mood.","ucDebtorRemindBest3":"Not a fit if your rules require the sales rep to call the debtor first: a scheduled mailout will override that order.","ucDebtorRemindCheck":"Review the texts and the schedule. List:\n— letters where the debt amount didn't match the reconciliation statement or includes disputed documents;\n— counterparties who would get two reminders at once for different invoices — those need to be merged;\n— recipients whose payment has already arrived but hasn't been allocated yet;\n— wording that must not go out without a lawyer: threats of court, penalty calculations, formal demands;\n— those who ended up in the mailout for the first time — better to show them to the sales rep.\nSay which letters can go as they are and which should stay in drafts.","ucDebtorRemindInputs":"1C, Email, Telegram. From you: the sending schedule, the tone of each letter, the signature and the list of exempt counterparties.","ucDebtorRemindPrompt":"Prepare three payment reminder texts and a schedule for sending them to the debtors from 1C.\nThe first — [three] days before the due date, neutral: amount, invoice numbers, payment date.\nThe second — on day [seven] past due, specific: how many days are overdue and what happens next.\nThe third — on day [thirty], formal: referencing the contract clause on late payment penalties.\nTake amounts and document numbers only from 1C. If a counterparty has an unallocated payment\nor a dispute over an acceptance act — don't send the letter, move them into a \"human first\" list.\nDon't calculate penalties in the text if the rate isn't filled in in the contract: write \"in accordance\nwith the contract\".\nOutput three templates with placeholders, a sending rule for each and a list of exceptions.","ucDebtorRemindStep1Desc":"Decide on which day each letter goes out and how the second differs from the first in tone. Name the counterparties we never write to — key clients and those in litigation.","ucDebtorRemindStep1Title":"Set the schedule and the tone","ucDebtorRemindStep2Desc":"The agent checks terms and overdue days in 1C, fills amounts and invoice numbers into the template and sends the letters by email, with a copy of the list to Telegram.","ucDebtorRemindStep2Title":"Run the mailout","ucDebtorRemindStep3Desc":"A letter about a debt that doesn't exist costs more than a few days of silence — read a sample before the first run","ucDebtorRemindStep3Title":"Check the result","ucDiffEasy":"Easy","ucDiffHard":"Hard","ucDiffMedium":"Medium","ucDirectWasteBest1":"Spend is on plan but there are fewer leads — you need to figure out which exact rows are eating it.","ucDirectWasteBest2":"The account has been running a long time, there are many campaigns, and half of them nobody reviewed after launch.","ucDirectWasteBest3":"Not a fit with low spend per campaign: on 3-4 clicks the absence of a conversion means nothing yet.","ucDirectWasteCheck":"Check the list of things to pause. List:\n— rows where the conclusion is built on fewer than [30] clicks;\n— phrases that produced assisted conversions but not the last click;\n— campaigns with a long deal cycle where the conversion simply didn't fit inside the period;\n— brand queries that you marked as ineffective;\n— the savings estimate: which rows it's made of and how much of it will come back as spend in other campaigns.\nMark what can be turned off right away and what should first be made a negative and watched for two weeks.","ucDirectWasteInputs":"Yandex Direct, Yandex Metrica. Manually: the period, the target action and the spend threshold below which it isn't worth digging.","ucDirectWasteStep1Desc":"The spend threshold cuts off noise: without it hundreds of phrases with two clicks land in the report. Name a single target action — otherwise micro-goals like \"click on the phone number\" will mask the absence of leads.","ucDirectWasteStep1Title":"Set the threshold and the goal","ucDirectWasteStep2Desc":"The agent goes top-down to the level of phrases and placements and separates rows with no conversions from rows with expensive conversions — the latter aren't paused, they're fixed with the bid.","ucDirectWasteStep2Title":"Run the analysis","ucDirectWasteStep3Desc":"Pausing a campaign is irreversible for its accumulated statistics, so the pause list is worth sifting through","ucDirectWasteStep3Title":"Check the result","ucDrrBest1":"The budget is scattered across Direct and the marketplace ad dashboards, and overall efficiency is estimated by eye.","ucDrrBest2":"You need a \"switch off or add budget\" decision on specific campaigns, not one overall figure for the channel.","ucDrrBest3":"Not a fit if campaigns are named haphazardly and tied to neither a category nor a SKU: there is nothing to match the spend against.","ucDrrCheck":"Review the ad cost share calculation. List:\n— campaigns where the conclusion rests on fewer than [20] orders or on [a few days];\n— which attribution model you took for each platform and where they don't agree;\n— orders that could have been counted twice in different dashboards;\n— awareness campaigns or new launches that ad cost share isn't measured on;\n— spend left without attributed revenue, and its share of the total budget.","ucDrrInputs":"Yandex Direct, Ozon, Wildberries. From you: the period, the target ad cost share and the rule for which orders count as the result of advertising.","ucDrrStep1Desc":"A period shorter than two weeks is usually noisy on marketplaces: orders arrive with a delay after the click. Name the threshold above which a campaign counts as loss-making.","ucDrrStep1Title":"Set the period and the target ad cost share","ucDrrStep2Desc":"The agent calculates ad cost share for each campaign separately and doesn't shift revenue between dashboards to paper over a hole in attribution.","ucDrrStep2Title":"Run the calculation","ucDrrStep3Desc":"Before switching campaigns off — make the agent review its own work","ucDrrStep3Title":"Check the result","ucDsoBest1":"You need to show management or the bank whether customer settlements sped up or slowed down, not who specifically owes money.","ucDsoBest2":"You changed the deferral terms and want to see whether it showed up in the actual payment days.","ucDsoBest3":"Not a fit if you need a list of debtors to call: this is a metric and its dynamics, not a debt collection plan.","ucDsoCheck":"Review the turnover calculation. List:\n— counterparties whose metric was calculated on fewer than [three] shipments;\n— months where the average balance was taken from two points instead of snapshots;\n— the effect of large one-off shipments and prepayments on the final figure — show the numbers with and without them;\n— bad and disputed debts that push the average days up and turnover down;\n— which conclusions about the trend are backed by data and which are your interpretation.\nState the formula you used explicitly.","ucDsoInputs":"1C, Google Sheets. From you: the period, the granularity of the trend and the formula you use for DSO.","ucDsoPrompt":"Calculate receivables turnover for [period] broken down by [months /\nquarters] using 1C data.\nGive company-wide figures: turnover in times, average days sales outstanding, average receivables\nfor the period. Then the same metrics per customer and by groups [wholesale / retail / chains].\nCalculate the average balance from monthly snapshots, not from the start and end of the period. If a counterparty has\nfewer than [three] shipments in the period, don't average their payment days — mark it \"not enough data\".\nDon't explain a change in the metric by seasonality or sales growth until you show the figures\nthat confirm it.\nOutput a Google Sheets table: company-wide dynamics, the counterparty breakdown, and a\n\"not enough data\" column.","ucDsoStep1Desc":"Say whether you calculate payment days on revenue with or without VAT and whether prepayments are included. Different formulas give different DSO, and periods can only be compared within one of them.","ucDsoStep1Title":"Agree on the formula","ucDsoStep2Desc":"The agent takes shipments, payments and outstanding balances from 1C, calculates the metrics on monthly snapshots and puts the trend into a spreadsheet.","ucDsoStep2Title":"Run the calculation","ucDsoStep3Desc":"The metric is easy to improve by accident — with one large shipment at the end of the period; make sure the trend isn't about that","ucDsoStep3Title":"Check the result","ucDupPaymentsBest1":"Several people pay invoices, and the same invoice sometimes goes out twice.","ucDupPaymentsBest2":"Lots of recurring payments: services, acquiring, fees — some of them haven't been needed for a long time.","ucDupPaymentsBest3":"Not a fit if you have standard identical scheduled payments (rent, leasing): they will have to be excluded manually, otherwise the list will consist of them.","ucDupPaymentsCheck":"Review the list. List:\n— pairs where only the amount matched while the payee or the grounds differ;\n— partial payments of one invoice that you took for a double payment;\n— refunds and reversals that close a duplicate you found — such rows don't belong on the list;\n— payments whose grounds weren't found because the document isn't posted, not because it doesn't exist;\n— the total possible overpayment and which rows went into it.\nMark what can be verified from the data and what requires a call to the counterparty.","ucDupPaymentsInputs":"Tochka, 1C. From you: the period, the duplicate search window in days and the list of recurring payments not to be treated as duplicates.","ucDupPaymentsStep1Desc":"Name the period and the window within which two identical payments count as suspicious. List the recurring payments that must not appear on the list right away.","ucDupPaymentsStep1Title":"Set the boundaries","ucDupPaymentsStep2Desc":"The agent matches outgoing payments in the statement against the postings and source documents in 1C and groups the matches by suspicion type rather than into one pile.","ucDupPaymentsStep2Title":"Run the search","ucDupPaymentsStep3Desc":"Half of the \"duplicates\" usually turn out to be partial payments of one invoice — filter them out before talking to the counterparty","ucDupPaymentsStep3Title":"Check the result","ucEdoInboxBest1":"Dozens of incoming documents a week, some of them sitting unsigned in EDI simply because nobody got to them.","ucEdoInboxBest2":"The supplier regularly sends documents with a price and quantity that differ from the order — the discrepancy has to be caught before signing.","ucEdoInboxBest3":"Not a fit if purchase orders to suppliers aren't created in 1C: there is nothing to compare the document with, and all you get is a register of incoming documents.","ucEdoInboxCheck":"Review the processing. List:\n— documents linked to an order by amount or date, without a matching number;\n— items where the product was matched by name rather than by SKU;\n— within-tolerance discrepancies that repeat with the same supplier month after month;\n— adjustment and corrected documents: did you link them to the original or count them as separate;\n— documents with no order: are they really absent from 1C or were you looking in the wrong period.\nMark what can be posted without questions and what must not be signed until the supplier responds.","ucEdoInboxInputs":"Diadoc, 1C. From you: the period to process and the acceptable price and quantity deviation.","ucEdoInboxPrompt":"Process the incoming documents from Diadoc for [period] and match them against the orders and contracts in 1C.\nFor each document: type, counterparty, number, date, amount, EDI status, the order\nor contract found. Sort into groups: full match, price differs, quantity or item\ndiffers, details don't match the record, no order found, document not posted in 1C.\nTreat a discrepancy as significant from [deviation] — flag anything smaller but don't escalate it.\nDon't match items by similarity of the name: if the SKU or code doesn't match, write\n\"not matched\" instead of picking the nearest item.\nOutput a table of documents indicating where each figure came from, and a separate list of\ndocuments awaiting signature for longer than [deadline].","ucEdoInboxStep1Desc":"Say from what price or quantity deviation a discrepancy counts as significant — otherwise the list will drown in penny rounding differences.","ucEdoInboxStep1Title":"Set the period and the tolerances","ucEdoInboxStep2Desc":"The agent reads the incoming documents in Diadoc, recognizes the details and the items and matches each document against the order and contract in 1C, preserving the EDI status.","ucEdoInboxStep2Title":"Run the processing","ucEdoInboxStep3Desc":"Signing is irreversible, so first look at where the agent matched a document to an order by eye","ucEdoInboxStep3Title":"Check the result","ucExcelDashBest1":"You need a file you can hand to a colleague: they swap in the export and everything recalculates by itself.","ucExcelDashBest2":"The existing dashboard breaks after every refresh: ranges shift, slicers come loose.","ucExcelDashBest3":"Not a fit if you need an online dashboard refreshed on a schedule — that's a different scenario.","ucExcelDashCheck":"Review how the file is built. List:\n— formulas and ranges that will shift if the new export has more or fewer rows;\n— cells where the value is typed in as a number rather than calculated from \"Source\";\n— pivots and slicers that will lose their link if the column order or names change;\n— elements not supported in [Google Sheets / Excel] that will break on opening;\n— what exactly a person has to do on a refresh and what they must not touch by hand.\nWhatever you can rebuild yourself, show as a \"proposed changes\" list; leave the rest to me.","ucExcelDashInputs":"Google Sheets, 1C. From you: the breakdowns you need in the pivots and the decision on where the file lives — in Google Sheets or in XLSX.","ucExcelDashPrompt":"Build a sales dashboard for [period] in [Google Sheets / XLSX] on 1C data.\nArrange the file like this: a \"Source\" sheet — a flat table with no merged cells and a date column\nin a single format; a \"Summary\" sheet — pivot tables by [breakdowns]; a \"Dashboard\" sheet — charts and slicers\ntied to the pivots rather than to the source directly.\nSet the pivot ranges as whole columns or named ranges so that nothing shifts when a new export\nhas a different number of rows.\nDon't hard-code calculated values into the dashboard cells: every figure must be recalculated\nfrom \"Source\".\nOn a separate \"How to refresh\" sheet describe: where to paste the new export, what to click\nand what breaks if the column order in the export changes.","ucExcelDashStep1Desc":"Google Sheets and Excel behave differently with slicers and pivots — name where the file will be opened more often so it isn't built for both at once.","ucExcelDashStep1Title":"Describe the breakdowns and where the file lives","ucExcelDashStep2Desc":"The agent spreads the data across three sheets and ties the charts to the pivots rather than the source table: that way a refresh doesn't break the visualization.","ucExcelDashStep2Title":"Run the build","ucExcelDashStep3Desc":"Before handing the file to colleagues — make the agent review its own work","ucExcelDashStep3Title":"Check the result","ucFacetCluster":"Work object","ucFacetDepartment":"Team","ucFacetReset":"Reset filters","ucFacetTaskType":"Task type","ucFaqKbBest1":"Operators answer the same question twenty times a week and write it from scratch every time.","ucFaqKbBest2":"There is a knowledge base, but it is written from inside the company, and the customer does not recognise their question in it.","ucFaqKbBest3":"Not a fit if the flow is small or every case is unique: the articles will end up being about one-off situations.","ucFaqKbCheck":"Check the draft base. List:\n— articles built on fewer than [N] tickets;\n— groups where questions of different substance sit under one title;\n— answers where you filled in the missing part yourself instead of taking it from the correspondence;\n— topics where operators answered inconsistently;\n— answers with prices, deadlines and promotion terms — they need a review date;\n— what can be published and what should first be shown to a lawyer or the support lead.","ucFaqKbInputs":"Telegram, Avito, Email. By hand: the period, the minimum number of repeats, the topics whose answers must not be published.","ucFaqKbStep1Desc":"A week gives a live snapshot, but below a threshold of five tickets random things get into the base. Separately name the topics whose public answer is cleared with a lawyer.","ucFaqKbStep1Title":"Set the period and the repeat threshold","ucFaqKbStep2Desc":"The agent groups tickets by meaning, takes the answer from the operators' correspondence and does not invent the missing pieces but flags the discrepancies.","ucFaqKbStep2Title":"Run the build","ucFaqKbStep3Desc":"A knowledge base is read by the customer with no operator alongside — a mistake in it spreads silently","ucFaqKbStep3Title":"Check the result","ucFeedbackTopicsBest1":"Feedback arrives in three places, and each is watched by different people with their own eyes — there is no shared picture.","ucFeedbackTopicsBest2":"You need to understand where a topic is genuinely widespread and where the channel is simply noisy: people write more often in a chat than on a marketplace.","ucFeedbackTopicsBest3":"Not a fit if there is no taxonomy and nobody to approve one: without a shared list of topics the classification will shift from run to run.","ucFeedbackTopicsCheck":"Check the classification. List:\n— topics you introduced beyond the approved taxonomy, and what landed in them;\n— messages that ended up in \"unclassified\", grouped by reason;\n— topics where a channel has fewer than [20] messages and the share jumps because of single items;\n— channels where the period is not fully covered — from which date to which there is data;\n— messages from the same person counted as several tickets;\n— which topics you can re-sort yourself and where a decision is needed on where something belongs.","ucFeedbackTopicsInputs":"Telegram, Email, Ozon. By hand: the period and the list of topics — your own taxonomy or consent to the one the agent proposes.","ucFeedbackTopicsStep1Desc":"Give your own list of topics or ask the agent to propose one and look at that first, not at the numbers: the whole downstream table depends on the taxonomy. Use the same list next time, otherwise the runs cannot be compared.","ucFeedbackTopicsStep1Title":"Approve the taxonomy","ucFeedbackTopicsStep2Desc":"The agent assigns each message to one topic, sets the debatable ones aside and computes shares within each channel separately.","ucFeedbackTopicsStep2Title":"Run the classification","ucFeedbackTopicsStep3Desc":"Before comparing channels — check that they are comparable at all","ucFeedbackTopicsStep3Title":"Check the result","ucFilterAll":"All","ucFollowupBest1":"Proposals went out in a batch, three people replied, and there's no time and it feels awkward to chase.","ucFollowupBest2":"A long deal cycle where the second and third contacts matter more than the proposal itself.","ucFollowupBest3":"Not a fit if correspondence with clients happens in messengers: the agent won't see that you've already been answered.","ucFollowupCheck":"Check the email drafts. List:\n— emails where you referred to an agreement that isn't in the correspondence;\n— clients who actually did reply — in another thread or from another address;\n— emails offering terms, discounts or deadlines that weren't agreed with me;\n— clients who have already received a follow-up — and how many times;\n— emails sent to the company's general inbox instead of the contact person.\nEdit the text freely; the recipient list and the terms only through me.","ucFollowupInputs":"Bitrix24, Email. Manually: how long to wait for a reply, the tone of the emails and what may be offered as a reason to write.","ucFollowupStep1Desc":"Say after how many days of silence we consider a client cooled off and what the manager is allowed to offer in the email. Separately list the clients who shouldn't be written to — for example, those who already declined.","ucFollowupStep1Title":"Set the frame","ucFollowupStep2Desc":"The agent pulls up the history on each deal and writes the email from what was actually agreed; where there's no history, it honestly marks the email as written blind.","ucFollowupStep2Title":"Assemble the drafts","ucFollowupStep3Desc":"The email goes out from the manager personally — an invented detail of a conversation is spotted by the client immediately and costs more than silence.","ucFollowupStep3Title":"Check the result","ucFreqBiweekly":"once every two weeks","ucFreqDaily":"every day","ucFreqMonthly":"once a month","ucFreqOnEvent":"on an event","ucFreqOneTime":"set up once","ucFreqQuarterly":"once a quarter","ucFreqWeekly":"once a week","ucFunnelLeaksBest1":"You need a repeatable funnel metric: where the percentages sagged and by how much versus the previous period.","ucFunnelLeaksBest2":"You changed the script or the order of stages and want to see whether it showed up in the transitions.","ucFunnelLeaksBest3":"Not a fit if sales reps move stages retroactively in batches: the transition history will show a CRM cleanup day, not the process.","ucFunnelLeaksCheck":"Review the funnel calculation. List:\n— stages where conversion was calculated on fewer than [30] deals;\n— deals whose stages were changed retroactively in a batch on a single day;\n— open deals still moving through the funnel, and how you counted them in the denominator;\n— stages you merged or skipped, and on what basis;\n— conversion changes explained by a change in the funnel itself rather than by the team's work.","ucFunnelLeaksInputs":"Bitrix24, amoCRM. From you: the period, the comparison base and which stages count as working ones and which as technical.","ucFunnelLeaksStep1Desc":"Remove the technical and service stages — otherwise conversion will smear across stages a deal passes through only formally. Name the comparison base.","ucFunnelLeaksStep1Title":"Set the period and the set of stages","ucFunnelLeaksStep2Desc":"The agent counts transitions from the change history rather than the current status, and separately shows deals that bypassed a stage.","ucFunnelLeaksStep2Title":"Run the calculation","ucFunnelLeaksStep3Desc":"Before drawing conclusions from these percentages — make the agent review its own work","ucFunnelLeaksStep3Title":"Check the result","ucGrowthPointsBest1":"The campaign has run, the totals are in, but what to change in the next launch is discussed on gut feel.","ucGrowthPointsBest2":"You need to hand the conclusions to a contractor or a new specialist as a list, not as a conversation.","ucGrowthPointsBest3":"Not a fit for a campaign that's still running: while impressions keep coming, segment statistics change every day.","ucGrowthPointsCheck":"Check the hypotheses. List:\n— hypotheses built on fewer than [20] conversions or [7] days of impressions;\n— conclusions where you explained the result after the fact rather than derived it from the data;\n— findings explained by the campaign's timing — holidays, season, a competitor's promo;\n— hypotheses that can't be tested on the next launch's budget;\n— overlapping hypotheses: if launched together it'll be unclear what worked.\nAt the end — which two hypotheses you'd test first and why.","ucGrowthPointsInputs":"Yandex Direct, Yandex Metrica. Manually: which campaign and its dates, the goal of the launch, budget limits for the next round.","ucGrowthPointsStep1Desc":"Give exact dates and say what matters more in the next launch — more volume or a cheaper goal. Which segments count as promising depends on that.","ucGrowthPointsStep1Title":"Name the campaign and the goal","ucGrowthPointsStep2Desc":"The agent looks for asymmetry — where conversion is above average but spend is small — and ties every hypothesis to specific campaign numbers.","ucGrowthPointsStep2Title":"Run the analysis","ucGrowthPointsStep3Desc":"A hypothesis goes into the next launch's budget, and a weak sample costs more than an extra hour of checking","ucGrowthPointsStep3Title":"Check the result","ucHowItWorks":"How the agent does it","ucHubEmpty":"Nothing matches these filters. Reset them or change the query.","ucHubSearchPlaceholder":"Search use cases","ucImpactEffortBest1":"Sprint planning, when the backlog holds hundreds of tasks and the priority is argued over from scratch every time.","ucImpactEffortBest2":"When you need to state out loud why a task is considered important — a score without a rationale does not survive the first argument.","ucImpactEffortBest3":"Not a fit if the tasks in the tracker are one-line titles with no description: there is nothing to score.","ucImpactEffortCheck":"Check the scores. List:\n— tasks where impact was set without leaning on a metric — on what reasoning;\n— tasks where effort is your guess rather than the team's estimate;\n— tasks that duplicate each other or are contained one within another;\n— tasks that cannot be done separately because of dependencies but ended up in different quadrants;\n— tasks where you scored the title because there is no description;\n— which scores you can refine by reading the linked tasks and which require a conversation with the team.","ucImpactEffortInputs":"Yandex Tracker, Kaiten. By hand: the queue or board, the metrics we count impact by, and the scoring scale.","ucImpactEffortStep1Desc":"State which board we take and which metrics impact is counted by: without that the agent will score \"importance in general\" and it will come out as a matter of taste. Say whether the tasks carry the team's estimates.","ucImpactEffortStep1Title":"Name the queue and the metrics","ucImpactEffortStep2Desc":"The agent goes through the tasks on a single scale, writes a rationale for every score and sets aside the ones where the description was not enough.","ucImpactEffortStep2Title":"Run the scoring","ucImpactEffortStep3Desc":"Before taking the matrix to planning — check what the scores rest on","ucImpactEffortStep3Title":"Check the result","ucInputsLabel":"What you set","ucInvoiceCheckBest1":"Invoices arrive in chat and by email from different managers, and one person sends them all for payment.","ucInvoiceCheckBest2":"There is a risk of bank details being swapped in an email — the invoice must be checked against the counterparty record, not the email signature.","ucInvoiceCheckBest3":"Not a fit for the first invoice from a new counterparty: there is nothing to check against, no record and no contract in 1C yet.","ucInvoiceCheckCheck":"Review your invoice check. List:\n— fields recognized with low confidence — show exactly what you read;\n— details taken not from the invoice but from the email or a previous document;\n— mismatches between the amount in words and in figures, the sum of the lines and the total, the rate and the VAT amount;\n— counterparty records with a similar name or a different bank account in 1C;\n— the grounds on which you judged the invoice a duplicate or, conversely, a new one.\nSay plainly what was missing for an unambiguous verdict.","ucInvoiceCheckInputs":"1C, Diadoc. From you: the invoice file and the contract or terms, if they aren't in 1C.","ucInvoiceCheckStep1Desc":"Send the PDF, a photo or the document received via EDI. If the contract isn't in 1C, state the agreed price and terms in text.","ucInvoiceCheckStep1Title":"Attach the invoice","ucInvoiceCheckStep2Desc":"The agent recognizes the details and amounts, cross-checks them against the counterparty record and the contract in 1C and looks for the same invoice among those already paid.","ucInvoiceCheckStep2Title":"Run the check","ucInvoiceCheckStep3Desc":"Look first at the fields marked \"not verified\" — that's where the discrepancy the agent missed is hiding","ucInvoiceCheckStep3Title":"Check the result","ucLaunchPostsBest1":"The launch is close, texts are written from scratch every time and they all come out the same.","ucLaunchPostsBest2":"You need to test several angles rather than pick one \"correct\" one by eye.","ucLaunchPostsBest3":"Not a fit if there's nothing specific to say about the product: without facts the agent will produce five paraphrases of one promise.","ucLaunchPostsCheck":"Check the post variants. List:\n— claims that weren't in my source data;\n— numbers, deadlines and client mentions you added yourself;\n— variants that essentially repeat each other — say which two to keep;\n— promises we could be held to: guarantees of results, comparisons with competitors;\n— places where the text doesn't fit the platform limit or the link preview breaks.\nAt the end: what you can rewrite yourself and where you need a fact from me.","ucLaunchPostsInputs":"Telegram, VK Ads. Manually: the product and offer description, the platform, a link to 3-5 past posts whose tone you like.","ucLaunchPostsStep1Desc":"Give the product description, the offer and the deadline — short, but with detail: what exactly changes for the client. Attach a few of your own posts the agent can take the tone from.","ucLaunchPostsStep1Title":"Gather the facts","ucLaunchPostsStep2Desc":"The agent keeps five different angles rather than five rewrites of one, and leaves explicit gaps where you didn't give a fact.","ucLaunchPostsStep2Title":"Run the generation","ucLaunchPostsStep3Desc":"The post goes out on behalf of the brand, so promises that aren't yours and invented details get caught before publishing","ucLaunchPostsStep3Title":"Check the result","ucLeadsTriageBest1":"Leads come from several sources, and in the morning nobody remembers who has already been picked up.","ucLeadsTriageBest2":"The flow has grown to the point where triage happens by leftovers and hot leads drown among spam.","ucLeadsTriageBest3":"Not a fit if the team has no priority rule: the agent will have nothing to tell a big lead from a random one by.","ucLeadsTriageCheck":"Check the lead triage. List:\n— leads where priority was assigned on incomplete data, and which field was missing;\n— leads marked as duplicates only because the company name matched;\n— cases where the owner was chosen by who was left rather than by the assignment rule;\n— leads from sources that weren't in my rules — how you handled them;\n— leads with a contact but no substance to the request: they can't be worked blind.\nDon't create tasks: show an \"I suggest creating\" list and wait for confirmation.","ucLeadsTriageInputs":"Bitrix24. Manually: the priority rules, the list of managers and the time standard for first contact.","ucLeadsTriageStep1Desc":"Describe what a hot lead is for you and list the managers with their areas — by industry, region or product. Specify the standard: within how many hours a lead must get its first contact.","ucLeadsTriageStep1Title":"Set the rules","ucLeadsTriageStep2Desc":"The agent reads new leads and deals, distributes them by your rules and doesn't assign priority where fields are missing — such leads go into a separate queue.","ucLeadsTriageStep2Title":"Run the triage","ucLeadsTriageStep3Desc":"Tasks will land in other people's day plans, so the owner list gets reviewed before they're created, not after.","ucLeadsTriageStep3Title":"Check the result","ucMarginAnomalyBest1":"Revenue is holding but there's less money at the end — and it's unclear which item ate it.","ucMarginAnomalyBest2":"After a promo or a change in marketplace fees you need to see quickly what went into the red.","ucMarginAnomalyBest3":"Not a fit if the cost of goods in 1C isn't up to date: margin will be calculated, but the deviations will show the state of the reference data, not the market.","ucMarginAnomalyCheck":"Review the margin calculation. List:\n— SKUs where the deviation rests on fewer than [20] sales in a week;\n— items where cost of goods wasn't taken as of the shipment date or is missing;\n— cases where margin dropped because of a one-off marketplace compensation or penalty rather than price;\n— costs you didn't allocate to SKUs and left in a common pile;\n— deviations where the factor was named on your judgement rather than derived from the breakdown.","ucMarginAnomalyInputs":"Ozon, Wildberries, 1C. From you: the depth of the period, the deviation threshold and the date to take cost of goods as of.","ucMarginAnomalyStep1Desc":"Three or four weeks are usually enough for the normal level to be visible. Set the threshold in percentage points — otherwise the agent will pull in the whole long tail of small SKUs.","ucMarginAnomalyStep1Title":"Set the depth and the threshold","ucMarginAnomalyStep2Desc":"The agent calculates margin for each SKU week by week and breaks the deviation down into factors in rubles rather than handing over one combined difference.","ucMarginAnomalyStep2Title":"Run the calculation","ucMarginAnomalyStep3Desc":"Before changing prices — make the agent review its own work","ucMarginAnomalyStep3Title":"Check the result","ucMinutes":"{count} min","ucMoMBest1":"A regular figure for the owner or the board: did things get better or worse, and by how much.","ucMoMBest2":"You need to see quickly whether the growth came from order count or from average order value — those are different stories.","ucMoMBest3":"Not a fit if the month isn't closed yet: some shipments and returns will land later and the comparison will drift.","ucMoMCheck":"Review the comparison. List:\n— differences between the months unrelated to demand: working days, promos, holidays;\n— rows where the growth came from a single large order — show the figure without it;\n— categories where the comparison base is under [50] orders and the percentages mean nothing;\n— returns that belong to the previous month but landed in the current one;\n— which percentages were calculated off a small base and look bigger than they are.","ucMoMInputs":"Ozon, Wildberries, 1C. From you: the two months being compared and what counts as revenue — shipment or payment.","ucMoMStep1Desc":"Say whether we count by shipment or by payment: mixing these two bases produces a discrepancy of tens of percent on the very same data.","ucMoMStep1Title":"Name the months and the revenue rule","ucMoMStep2Desc":"The agent calculates both months by one rule and separately sets out everything that makes them non-comparable instead of averaging it away.","ucMoMStep2Title":"Run the comparison","ucMoMStep3Desc":"Before sending it to management — make the agent review its own work","ucMoMStep3Title":"Check the result","ucNegAlertBest1":"A listing's rating drops from two or three reviews, and you need to know about them the day they are published.","ucNegAlertBest2":"\"A new review has arrived\" notifications fire on everything, and nobody has opened them in a long time.","ucNegAlertBest3":"Not a fit if reviews are read in a weekly batch: then you need an analysis, not an alert.","ucNegAlertCheck":"Check the trigger rule against the reviews from [the past week]. List:\n— how many alerts would have gone out per day and at which hours they cluster;\n— reviews that crossed the threshold because of a single word rather than their substance;\n— dangerous reviews the rule missed — and which condition was lacking;\n— repeat alerts on the same review or SKU;\n— SKUs where two negatives a day is ordinary background rather than a spike;\n— which threshold you propose to change and to what, leave the decision to me.","ucNegAlertInputs":"Ozon, Wildberries. By hand: the rating threshold, the list of priority SKUs, the address for alerts.","ucNegAlertStep1Desc":"Decide what counts as a dangerous review for you: a low rating, key SKUs, trigger words or several negatives in a row on one item. The narrower the threshold, the higher the chance the alert gets read.","ucNegAlertStep1Title":"Set the threshold","ucNegAlertStep2Desc":"The notification must answer the question \"do I open the seller account or not\" without opening it: the full quote rather than a paraphrase, and the rating before and after.","ucNegAlertStep2Title":"Describe the contents of the alert","ucNegAlertStep3Desc":"A threshold is tested against the past week, not the future — otherwise you learn how good it is after a month of silence or hundreds of alerts","ucNegAlertStep3Title":"Check the result","ucNegTrendBest1":"You shipped a fix and need to understand whether it showed up in the reviews or it just seems that way.","ucNegTrendBest2":"Weekly quality control, where what matters is not the fact of negativity but whether it is growing or fading.","ucNegTrendBest3":"Not a fit for products with rare reviews: on three reviews a week the share jumps because of one person.","ucNegTrendCheck":"Check the dynamics. List:\n— weeks with fewer than [20] reviews where the share is computed on too small a sample;\n— weeks with incomplete data: promotions, sales, gaps in reviews;\n— topics where the share changed after a fix but the sample does not allow talking about an effect;\n— cases where negativity grew along with the total number of reviews and did not change as a share;\n— topics you merged or renamed compared with the previous run;\n— which of the \"fix → reviews\" links are visible in the data and which are an assumption.","ucNegTrendInputs":"Ozon, Wildberries. By hand: the period, what counts as negative, and the dates of the shipped fixes.","ucNegTrendStep1Desc":"Say which ratings we count as negative and when the fixes were shipped — without the dates the agent will show only a curve, not its link to your actions.","ucNegTrendStep1Title":"Set the period and the fix dates","ucNegTrendStep2Desc":"The agent computes the share by week, breaks it down by topic and compares the weeks before and after each marked date.","ucNegTrendStep2Title":"Run the analysis","ucNegTrendStep3Desc":"Before reporting that the fix worked — check what backs that up","ucNegTrendStep3Title":"Check the result","ucNightQueueBest1":"The morning starts with sixty unread messages, and the first hour goes to reading rather than replying.","ucNightQueueBest2":"Customers are in different time zones: a message written at two a.m. has been waiting a full day by nine.","ucNightQueueBest3":"Not a fit if a dozen messages come in overnight: there is nothing to sort, reading them yourself is faster.","ucNightQueueCheck":"Check the queue breakdown. List:\n— tickets pushed to the top without a signal from my list;\n— drafts that state an order status or delivery date that was not in the correspondence;\n— messages continuing yesterday's correspondence — they must not be counted as new tickets;\n— several messages from one customer scattered across different queue rows;\n— autoresponders, marketplace notifications and spam that landed in the queue as tickets;\n— what can be sent after a quick proofread and what should only be opened with the customer history.","ucNightQueueInputs":"Telegram, Avito, Email. By hand: the boundaries of the night window, the urgency signals, the reply rules.","ucNightQueueStep1Desc":"Name the times when night starts and ends, and list the situations that go ahead of the rest for you. Keep the list of signals short: three or four items the agent applies consistently, ten it will interpret its own way.","ucNightQueueStep1Title":"Set the window and the urgency signals","ucNightQueueStep2Desc":"The agent gathers messages from three channels into a single queue, ranks them by your list and writes drafts only where the correspondence itself has enough data.","ucNightQueueStep2Title":"Run the analysis","ucNightQueueStep3Desc":"In the morning you reply fast and barely looking — so the queue needs one pass, but an attentive one","ucNightQueueStep3Title":"Check the result","ucNotFound":"Use case not found","ucNotFoundMetaTitle":"Use case not found","ucOpenInChat":"Open in chat","ucPipelineSummaryBest1":"The quarterly meeting with the owner, for which the summary is assembled in Excel over two days every time.","ucPipelineSummaryBest2":"Sales run in two CRMs after a merger or a migration, and the figures have to be brought into one picture.","ucPipelineSummaryBest3":"Not a fit if there was no quarterly plan: there'll be nothing to compare the actual with, only bare dynamics.","ucPipelineSummaryCheck":"Check the quarterly summary. List:\n— deals counted into the actual by creation date rather than close date;\n— revenue counted with VAT in one source and without VAT in the other;\n— managers whose result grew from transferred deals rather than their own;\n— loss reasons you generalised yourself because the CRM field was empty;\n— the share of the forecast resting on deals with no close date or no amount;\n— duplicate clients between Bitrix24 and amoCRM counted twice.\nFix the calculations yourself and show what changed; leave the interpretation of reasons and the forecast to me.","ucPipelineSummaryInputs":"Bitrix24, amoCRM. Manually: the revenue plan, the quarter boundaries and which period we compare against.","ucPipelineSummaryStep1Desc":"Send the quarterly plan in the form it was approved in and say which breakdown management looks at. Specify which statuses count as a win for you — in the two systems they may be named differently.","ucPipelineSummaryStep1Title":"Provide the plan and the breakdown","ucPipelineSummaryStep2Desc":"The agent counts the actual by close dates, not by deal creation dates, and doesn't merge the two CRMs into one figure until it has mapped their stages.","ucPipelineSummaryStep2Title":"Assemble the summary","ucPipelineSummaryStep3Desc":"The summary is shown to the owner, and any figure in it will come back to you as a question.","ucPipelineSummaryStep3Title":"Check the result","ucPnlBest1":"Month-end close, when company-wide profit is known but per-unit profit gets recalculated in Excel every time.","ucPnlBest2":"An argument about which line of business earns money and which one lives off the rest.","ucPnlBest3":"Not a fit if 1C has no analytics filled in per business unit: there is nothing to allocate costs by.","ucPnlCheck":"Review your P&L. List:\n— line items assigned to a unit by payment description rather than by the analytics in 1C;\n— costs that landed in \"not allocated\" and why no base was found for them;\n— documents posted within the period but belonging to the previous month;\n— units that have revenue but no direct costs — that doesn't happen;\n— intercompany turnover between units: did you net it out or count it twice.\nWhatever you can recalculate yourself, show as a \"proposed changes\" list; leave debatable analytics to me.","ucPnlInputs":"1C, Tochka. From you: the period, the list of business units and the rule for allocating indirect costs.","ucPnlStep1Desc":"Name the period, the list of business units and the base for splitting shared costs — rent, accounting, management. If there is no rule yet, say so: the agent will leave those amounts unallocated instead of inventing a share.","ucPnlStep1Title":"Set the breakdown and the rule","ucPnlStep2Desc":"The agent reads turnover and postings in 1C directly, assigns income and costs to line items and units, and keeps accruals separate from cash.","ucPnlStep2Title":"Run the collection","ucPnlStep3Desc":"The per-unit number almost always breaks on the allocation of shared costs — ask the agent to show where it guessed the base","ucPnlStep3Title":"Check the result","ucPrdDraftBest1":"After a series of discussions, when the agreements are scattered across notes, chats and tickets, and there is no document.","ucPrdDraftBest2":"When you need to see quickly what the solution is missing: the open questions matter more than finished prose.","ucPrdDraftBest3":"Not a fit if there are almost no notes and the solution exists only in someone's head: the agent will write a plausible document about nothing.","ucPrdDraftCheck":"Check the draft PRD. List:\n— requirements with no source link — where you took them from;\n— places where you picked one option out of several discussed, and why;\n— wordings that were a hypothesis in the notes but became a statement in the document;\n— metrics there is nothing to measure with given our current data collection;\n— contradictions between notes from different meetings that you smoothed over instead of showing;\n— what can be filled in from the existing notes and what requires a human decision.","ucPrdDraftInputs":"Google Docs, Google Sheets. By hand: links to notes and tickets, a PRD template if you have one, and the list of metrics you can actually count.","ucPrdDraftStep1Desc":"Give links to everything related to the feature, including the discussions where people argued and did not agree — those are exactly what produce the list of open questions. If you have your own PRD template, attach it.","ucPrdDraftStep1Title":"Assemble the input","ucPrdDraftStep2Desc":"The agent sorts the notes into sections, puts a source on every requirement and separates the decisions made from what is still unresolved.","ucPrdDraftStep2Title":"Run the build","ucPrdDraftStep3Desc":"Before calling the team to a review — check that the document has not been made up","ucPrdDraftStep3Title":"Check the result","ucPriceCompareBest1":"Sales on an item have dropped and you need to understand whether it's the price or something else.","ucPriceCompareBest2":"Before joining a promo you need to see what price level you're starting from relative to the market.","ucPriceCompareBest3":"Not a fit for goods without direct analogues: there'll be nothing to compare with, and forced pairs give a false picture.","ucPriceCompareCheck":"Check the price comparison. List:\n— pairs where the competitor was picked by name rather than by specifications;\n— SKUs compared against an item that's out of stock — such a price doesn't set the market;\n— items where the difference is explained by a different pack size or bundle;\n— rows built on fewer than [3] competitors — the median there means nothing;\n— cases where you compared a struck-through price with a post-discount price.\nSeparately: where you suggest lowering the price without knowing my cost — those rows I'll calculate myself.","ucPriceCompareInputs":"Wildberries, MPStats. Manually: your SKU list, the criteria for a comparable product and who we compare against.","ucPriceCompareStep1Desc":"Name the criteria that make a product comparable — volume, composition, bundle contents. Without this the agent will pick as competitors everything that looks similar by name.","ucPriceCompareStep1Title":"Define what counts as an analogue","ucPriceCompareStep2Desc":"The agent calculates the difference from the price the buyer pays after discount, not from the struck-through one, and keeps non-comparable pairs in a separate block.","ucPriceCompareStep2Title":"Run the comparison","ucPriceCompareStep3Desc":"Prices get changed off this table, and price is margin, so the pairs are worth looking over by eye","ucPriceCompareStep3Title":"Check the result","ucPromoEconBest1":"The platform is inviting you into a promo and you need to work out before the deadline whether the product can take the discount.","ucPromoEconBest2":"The last promo brought turnover but profit didn't grow, and you want to do the math beforehand rather than after.","ucPromoEconBest3":"Not a fit if the cost in 1C isn't up to date: the whole calculation rests on it, and an error in purchase price breaks everything.","ucPromoEconCheck":"Check the promo calculation. List:\n— cost items missing from the calculation, and how each one moves the break-even point;\n— which cost you took: the last purchase, the average or the one from the 1C card;\n— commission and logistics: as of what date they were taken and whether they changed over the period;\n— uplift scenarios: what the percentages are based on — a past promo or you picked them yourself;\n— what isn't accounted for: returns, change in search position, penalties for leaving the promo.\nSay outright which single figure influences the conclusion the most and how confident I should be in it.","ucPromoEconInputs":"Ozon, Wildberries, 1C. Manually: the discount size and promo period, what counts as cost, the share of ad spend attributed to the product.","ucPromoEconStep1Desc":"Say what goes into cost and what share of ad spend we attribute to the product. A missed item doesn't zero out the calculation — it flips it.","ucPromoEconStep1Title":"Gather the costs","ucPromoEconStep2Desc":"The agent calculates margin before and after the discount on the same cost base and keeps unaccounted items in a separate block instead of substituting averages.","ucPromoEconStep2Title":"Run the calculation","ucPromoEconStep3Desc":"The promo decision is made once and for the whole period, and rolling it back on the platform is no longer possible","ucPromoEconStep3Title":"Check the result","ucProposalBest1":"Managers assemble proposals by copy-pasting an old one and carry someone else's prices and deadlines into it.","ucProposalBest2":"One template, but many variations: a different set of services, different payment and discount terms.","ucProposalBest3":"Not a fit if prices are agreed individually on every deal: the agent will have nothing to fill in.","ucProposalCheck":"Check the assembled proposal. List:\n— every spot where data wasn't taken from the deal card, and where exactly it came from;\n— line items where no price was found in the price list, and what you put instead;\n— wording about deadlines and volumes that wasn't in the source data;\n— template blocks you removed or added, and why;\n— clauses that commit us to something — those get approved before sending.\nFix only formatting and structure yourself; don't change figures and terms, move them\ninto a list for approval.","ucProposalInputs":"Bitrix24, Google Docs. Manually: the template file, the current price list and the discount rules.","ucProposalStep1Desc":"Send the document you consider the reference one and specify which blocks are mandatory and which are situational. Attach the current price list separately — it isn't taken from CRM.","ucProposalStep1Title":"Provide the template and the price list","ucProposalStep2Desc":"The agent inserts the deal's data into the template structure and leaves a `[to clarify]` marker where the CRM field is empty instead of inventing wording.","ucProposalStep2Title":"Assemble the document","ucProposalStep3Desc":"The document goes to the client in your name, and an error in a price or deadline is later discussed as a commitment.","ucProposalStep3Title":"Check the result","ucReceivablesBest1":"The weekly collections call round, when the list is put together by hand every time.","ucReceivablesBest2":"When you need to separate \"pays late\" from \"stopped paying\" — those are different conversations.","ucReceivablesBest3":"Not a fit if contractual payment terms aren't filled in in 1C: there is nothing to count overdue days from.","ucReceivablesCheck":"Review the summary. List:\n— debts closed by a prepayment or an offset but still left in the calculation;\n— counterparties whose payments weren't linked to specific invoices;\n— rows where overdue days were counted from shipment because the term is not filled in;\n— installment contracts where there is in fact no overdue amount;\n— the amount that must not be quoted to the counterparty until accounting confirms it.","ucReceivablesInputs":"1C, Diadoc. From you: the cut-off date and the overdue threshold.","ucReceivablesStep1Desc":"Name the day the debt is measured on and from what overdue point a counterparty enters the workflow. If some customers have their own deferral terms, say so upfront, otherwise they will end up on the list for nothing.","ucReceivablesStep1Title":"Set the cut-off date and the threshold","ucReceivablesStep2Desc":"The agent takes shipments, payments and terms from 1C, counts overdue days from the contractual term and separates chronic non-payers from those who simply pay later.","ucReceivablesStep2Title":"Build the register","ucReceivablesStep3Desc":"A debt amount quoted wrongly to a counterparty costs more than a day of delay","ucReceivablesStep3Title":"Check before the calls","ucReconActBest1":"A quarterly reconciliation with a regular supplier or customer, with dozens of documents, some of them arriving via EDI.","ucReconActBest2":"The counterparty sent their own statement and you need to work out whose document dropped out of whose books.","ucReconActBest3":"Not a fit if some of the primary documents travel on paper: they won't be in Diadoc and the statement will be incomplete.","ucReconActCheck":"Review the reconciliation statement. List:\n— documents matched only by amount, without a matching number or date;\n— corrected and adjustment UPDs: was the original document counted twice;\n— documents sent via EDI but not signed by the counterparty;\n— rows where VAT was calculated at a rate different from the one stated in the document;\n— the balance discrepancy and exactly which rows it is made of.\nDon't fix anything silently: leave debatable rows in \"needs a decision\" — the accountant closes those.","ucReconActInputs":"Diadoc, 1C. From you: the counterparty, the reconciliation period and the statement form, if you use your own.","ucReconActStep1Desc":"Name the contract we are reconciling under if there are several. If you have your own statement form, attach it and the agent will build the document to it.","ucReconActStep1Title":"Pick the counterparty and the period","ucReconActStep2Desc":"The agent reads incoming and outgoing documents in Diadoc and the settlements in 1C and merges them line by line, marking each document's EDI status.","ucReconActStep2Title":"Run the matching","ucReconActStep3Desc":"The statement goes to the counterparty, so the cost of an error here is higher than in a normal reconciliation — reread the discrepancies before sending","ucReconActStep3Title":"Check the result","ucRelated":"Related use cases","ucReplyTemplatesBest1":"There are new operators on the team, and identical situations sound different from each of them.","ucReplyTemplatesBest2":"Templates exist, but they were written a year ago and have drifted from what operators actually write.","ucReplyTemplatesBest3":"Not a fit if tickets are almost always non-standard: the template will be rewritten in full every time and will only slow things down.","ucReplyTemplatesCheck":"Check the set of templates. List:\n— templates built on fewer than [N] cases;\n— places where a value from a specific conversation is filled in instead of a field;\n— texts promising a deadline, refund or goodwill compensation without a note on who approves it;\n— situations you merged into one template, and how they actually differ;\n— frequent situations from the correspondence left without a template;\n— which templates are ready for use and which the support lead must proofread.","ucReplyTemplatesInputs":"Telegram, Email. By hand: the correspondence period, the tone rules, the limits of what an operator may promise.","ucReplyTemplatesStep1Desc":"Take a period during which the current team was working and attach examples of replies you like. Separately list what an operator is not entitled to promise — that becomes fields rather than text.","ucReplyTemplatesStep1Title":"Give the correspondence and the boundaries","ucReplyTemplatesStep2Desc":"The agent groups situations by frequency and writes a template only for the recurring ones, leaving the variable parts as empty fields.","ucReplyTemplatesStep2Title":"Run the build","ucReplyTemplatesStep3Desc":"A template spreads across the whole team and will go out to customers unproofread — a mistake in it is multiplied by the number of operators","ucReplyTemplatesStep3Title":"Check the result","ucRevDashBest1":"The same report is rebuilt by hand every Monday — and it's always late for the meeting.","ucRevDashBest2":"You want the numbers to live at a link and refresh themselves instead of arriving as a file by email.","ucRevDashBest3":"Not a fit if the set of channels and breakdowns is different every time: a schedule makes sense for a format that has settled.","ucRevDashCheck":"Review the dashboard and the refresh schedule. List:\n— weeks where the data is incomplete but looks normal on the chart;\n— channels where revenue comes with a marketplace delay and the first days later change retroactively;\n— formulas and charts that will break if the number of rows or columns on the \"Data\" sheet changes;\n— what happens when a source doesn't respond: where a blank stays and where a zero gets substituted;\n— who receives the summary after a refresh and what it must not show without a human.\nWhatever you can fix yourself, show as a \"proposed changes\" list; leave the rest to me.","ucRevDashInputs":"Ozon, Wildberries, Google Sheets. From you: the day and time of the refresh, the list of channels and a link to the destination spreadsheet.","ucRevDashStep1Desc":"Create an empty spreadsheet and share the link — the agent will lay out the sheets itself. Name the day and time: the refresh must finish before anyone needs the report.","ucRevDashStep1Title":"Prepare the spreadsheet and the schedule","ucRevDashStep2Desc":"The agent builds the source sheet and the charts; after the first run it's best not to change the format — the schedule will reproduce exactly that one.","ucRevDashStep2Title":"Run the first collection and lock the format","ucRevDashStep3Desc":"Before putting it on auto-refresh — make the agent review its own work","ucRevDashStep3Title":"Check the result","ucReviewInsightsBest1":"Planning next month's backlog, when the ideas come out of your head rather than from what customers write.","ucReviewInsightsBest2":"When you need to separate a request for something new from a complaint about something broken: the first goes to the roadmap, the second to support.","ucReviewInsightsBest3":"Not a fit if there are only a few dozen reviews a month: two requests do not show demand.","ucReviewInsightsCheck":"Check the list of requests. List:\n— groups with fewer than [5] mentions that you nonetheless placed higher on the list;\n— requests merged into one group, and the signal you merged them by;\n— rows where the request is actually a complaint about delivery or support;\n— quotes from which the request does not read directly but was inferred by you;\n— SKUs with too few reviews over the period to draw a conclusion from.\nWhat you can regroup yourself — show as an \"I propose to change\" list, leave the decision to me.","ucReviewInsightsInputs":"Ozon, Wildberries. By hand: the period, the list of products or categories, the threshold below which a request counts as a one-off.","ucReviewInsightsStep1Desc":"The agent reads the reviews from the seller accounts itself, nothing needs exporting. Name which categories or SKUs are in scope — otherwise it will take everything and mix different products together.","ucReviewInsightsStep1Title":"Set the period and the products","ucReviewInsightsStep2Desc":"The agent keeps only product change requests, merges different wordings of the same request and separates out what was mentioned only once.","ucReviewInsightsStep2Title":"Run the collection","ucReviewInsightsStep3Desc":"Before you take the list to grooming — make the agent review its own work","ucReviewInsightsStep3Title":"Check the result","ucReviewsBest1":"Reviews pile up, replies come from one employee then another — and the tone drifts from terse to overfamiliar.","ucReviewsBest2":"Half the reviews are \"all good, thanks\", it feels wasteful to keep an editor on them, yet the marketplace requires a reply.","ucReviewsBest3":"Not a fit if the tone rules exist neither on paper nor as examples: the agent has nothing to pick up the brand voice from.","ucReviewsCheck":"Check your replies. List:\n— replies where you promised a deadline, refund, discount or replacement that is not in the rules;\n— reviews in the \"template\" group whose text contains a specific complaint;\n— replies where the complaint is restated inaccurately — show the quote from the review alongside;\n— reviews about the marketplace's delivery or someone else's product, which are not ours to answer;\n— reviews marked \"do not reply\" and the signal you used to decide;\n— what you can rewrite yourself and what needs an operator decision.","ucReviewsInputs":"Ozon, Wildberries, Telegram. By hand: tone rules, 5–10 of your own replies as a reference, a list of what must not be promised.","ucReviewsStep1Desc":"Give the agent several of your own replies that you consider the reference, and a separate list of what must not be promised. Without that list the agent will politely promise something you do not have.","ucReviewsStep1Title":"Collect the tone rules","ucReviewsStep2Desc":"The agent sorts the reviews into three groups and writes text only for the first two, leaving the debatable ones flagged instead of inventing a decision for the operator.","ucReviewsStep2Title":"Run the analysis","ucReviewsStep3Desc":"The reply goes out on behalf of the company and stays on the marketplace forever — read it before sending, not after","ucReviewsStep3Title":"Check the result","ucRomiBest1":"A weekly stand-up where you need one table to answer what each channel brought in money.","ucRomiBest2":"Budget is split between Direct and VK, and the reallocation decision is made every week.","ucRomiBest3":"Not a fit if revenue transfer isn't set up in Metrica: without it this is a spend report, not a ROMI one.","ucRomiCheck":"Check the weekly report. List:\n— channels where revenue was not taken from Metrica but calculated by you;\n— campaigns that didn't match between the ad account and Metrica, and where you assigned their spend;\n— rows where ROMI is calculated on fewer than [10] conversions;\n— the discrepancy between total spend in the report and the total in the ad accounts — show both figures;\n— conclusions that rest on a single week and fall apart over a month.\nWhatever you can recalculate yourself — show as an \"I suggest changing\" list, don't fix it silently.","ucRomiInputs":"Yandex Direct, VK Ads, Yandex Metrica. Manually: the week boundaries, the target action in Metrica and which period we compare against.","ucRomiStep1Desc":"Name which action in Metrica counts as the result — otherwise the agent will take every goal at once and the totals will drift apart. If there are more than two channels, list the ones included in the report.","ucRomiStep1Title":"Set the week and the goal","ucRomiStep2Desc":"The agent pulls spend from the ad accounts, conversions and revenue from Metrica, and joins them by the campaign tag, not by name — matching names doesn't satisfy it.","ucRomiStep2Title":"Run the build","ucRomiStep3Desc":"The report goes to a stand-up where money gets moved on it, so figures without a source are better removed in advance","ucRomiStep3Title":"Check the result","ucSalesDigestBest1":"The Monday stand-up, for which the summary is assembled by hand every Sunday evening.","ucSalesDigestBest2":"The head of sales runs several teams and wants to see who's falling behind before it becomes an end-of-month conversation.","ucSalesDigestBest3":"Not a fit if deals are closed in CRM in a batch at the end of the month: weekly dynamics will be noise.","ucSalesDigestCheck":"Check the weekly summary. List:\n— conclusions built on a single week — they can't be called a trend;\n— managers whose week was off because of holiday or sick leave rather than because of their work;\n— deals closed retroactively and therefore counted in the wrong week;\n— figures that don't match the previous summary, and why;\n— wording about specific people that shouldn't go into a shared chat without a conversation.\nWhatever didn't fit the line limit — show as a separate list, don't drop it silently.","ucSalesDigestInputs":"Bitrix24, Telegram. Manually: the weekly benchmark, the team composition and the send time.","ucSalesDigestStep1Desc":"Pick the day and hour so the summary arrives before the stand-up, not after. Specify the team composition and the weekly benchmark we compare the actual against.","ucSalesDigestStep1Title":"Set up the schedule","ucSalesDigestStep2Desc":"Say what an area of attention is for you: a drop two weeks running, silence on a large deal, leads not picked up. The agent selects by that rule and doesn't drag the rest into the summary.","ucSalesDigestStep2Title":"State the rule briefly","ucSalesDigestStep3Desc":"For the first two or three weeks the summary is read alongside the raw export: that's how you see what the agent treats as normal and what as a deviation.","ucSalesDigestStep3Title":"Check the result","ucSalesDropBest1":"Revenue fell, but in each dashboard separately everything looks \"roughly as usual\".","ucSalesDropBest2":"You need to separate a general demand decline from problems with specific listings — the fixes are different.","ucSalesDropBest3":"Not a fit if the operating model changed during the period (moved from FBS to FBO, changed legal entity): the before and after figures aren't comparable.","ucSalesDropCheck":"Review the analysis. List:\n— SKUs where the decline was calculated on fewer than [30] orders in one of the periods;\n— items that were out of stock, and this got confused with a demand decline;\n— comparisons where the periods have a different number of days or a different number of marketplace promos;\n— cases where revenue fell but margin grew — that isn't a problem;\n— which explanations of the decline you confirmed with a figure and which remain hypotheses.","ucSalesDropInputs":"Ozon, Wildberries. From you: the period, the comparison base and the list of SKUs that aren't of interest (clearance, discontinued items).","ucSalesDropStep1Desc":"The agent reads both dashboards directly. Name what we compare against: the previous month or the same month a year ago — the conclusions will differ.","ucSalesDropStep1Title":"Set the period and the comparison base","ucSalesDropStep2Desc":"The agent calculates the decline separately for each marketplace and breaks it down into price, quantity and returns rather than handing over one combined delta.","ucSalesDropStep2Title":"Run the analysis","ucSalesDropStep3Desc":"Before taking it to the stand-up — make the agent review its own work","ucSalesDropStep3Title":"Check the result","ucSalesMergeBest1":"The same item is named differently in 1C, on the marketplace and in the CRM — the mapping takes a week by hand.","ucSalesMergeBest2":"You need a raw consolidated base for any downstream report, not ready-made conclusions.","ucSalesMergeBest3":"Not a fit if the products have neither a common SKU nor a barcode: there is nothing to match on.","ucSalesMergeCheck":"Review the merge. List:\n— items matched by name rather than by SKU or barcode;\n— rows that could still be duplicates: one shipment in 1C and a deal in the CRM;\n— channels where revenue was taken with VAT while the others are without;\n— orders that fell into the period on different dates in different systems: shipment, payment, creation;\n— the share of rows left unmatched and what amount they carry.\nWhatever you can match up yourself, show as a \"proposed changes\" list; leave the rest to me.","ucSalesMergeInputs":"1C, Bitrix24, Ozon, Wildberries. From you: the period, the SKU mapping reference (if you have one) and the rule for whose price is the primary one.","ucSalesMergeStep1Desc":"If you already maintain a SKU mapping reference, attach it and the agent will use it as the basis. Say separately whether we count with or without VAT: recalculating later costs more.","ucSalesMergeStep1Title":"Give the period and the matching rules","ucSalesMergeStep2Desc":"The agent matches by SKU or barcode, removes overlaps between 1C and the CRM and doesn't invent pairs from similar names.","ucSalesMergeStep2Title":"Run the merge","ucSalesMergeStep3Desc":"Before building reports on this table — make the agent review its own work","ucSalesMergeStep3Title":"Check the result","ucSbisActBest1":"The counterparty works through SBIS and sends their own statement — it needs to be checked line by line, not by the closing balance.","ucSbisActBest2":"The statement is agreed over several rounds and you need to know what changed between versions of the document.","ucSbisActBest3":"Not a fit if settlements run in several currencies or through agency arrangements: line-by-line matching will produce false discrepancies there.","ucSbisActCheck":"Review the reconciliation statement. List:\n— lines matched by amount without a matching document number or date;\n— documents in \"sent\" or \"rejected\" status that you counted as agreed;\n— the part of the balance discrepancy that didn't break down into specific lines;\n— offsets, prepayments and refunds recorded by the two sides in different periods;\n— lines that got into the statement from another contract with the same counterparty.\nSay what can be fixed on our side before signing and what will have to be agreed with the counterparty.","ucSbisActInputs":"SBIS, 1C. From you: the counterparty, the period and the counterparty's statement, if they sent one.","ucSbisActPrompt":"Generate a reconciliation statement with [counterparty] for [period] in SBIS and check it against the settlements in 1C.\nMatch line by line: date, document, debit, credit. Collect separately the lines that we have\nand the counterparty doesn't, that the counterparty has and we don't, and those that match on the document\nbut differ on the amount.\nDon't level out differing balances by fudging: the discrepancy must break down into specific\nlines, and if it doesn't, say so.\nTake the document's SBIS status into account: sent, signed, rejected, cancelled — an unsigned\ndocument cannot be treated as agreed.\nOutput the statement in the standard form, a line-by-line discrepancy sheet indicating the side and the status,\nand the closing balance from both sides.","ucSbisActStep1Desc":"If the counterparty has already sent their statement, attach it: the agent will reconcile both sides line by line rather than only our data against SBIS.","ucSbisActStep1Title":"Pick the counterparty and the period","ucSbisActStep2Desc":"The agent generates the statement in SBIS, reads the document statuses and merges the lines with the 1C postings, marking whose line is missing and what status the document is in.","ucSbisActStep2Title":"Collect and match","ucSbisActStep3Desc":"A signature on the statement closes the period — a discrepancy not broken down into lines becomes your loss once it's signed","ucSbisActStep3Title":"Check the result","ucStaleDealsBest1":"The pipeline has bloated and nobody knows which of the open deals are alive at all.","ucStaleDealsBest2":"A manager went on holiday or left, and their deals were left with no owner and no tasks.","ucStaleDealsBest3":"Not a fit if managers don't log calls and meetings in CRM: activity will look like zero for everyone.","ucStaleDealsCheck":"Check the list of forgotten deals. List:\n— deals that got on the list because the communication happened in a messenger and never reached CRM;\n— deals at stages where a long pause is normal — approval, tender, awaiting payment;\n— deals with no owner and how you worked out whose they are;\n— deals that are effectively lost and just sit open — they need closing, not chasing;\n— which field changes you decided not to count as activity.\nDon't change statuses and owners: collect a separate \"I suggest closing\"\nand \"I suggest reassigning\" list.","ucStaleDealsInputs":"Bitrix24. Manually: the \"forgotten\" threshold in days and the list of pipelines we look at.","ucStaleDealsStep1Desc":"The period depends on the deal cycle: for a short pipeline a week is enough, for a project one a month is fine. Specify the pipelines we treat as active so archived ones don't get on the list.","ucStaleDealsStep1Title":"Set the threshold","ucStaleDealsStep2Desc":"The agent goes through the open deals, tells a real contact from a technical field change and sorts what it finds by manager.","ucStaleDealsStep2Title":"Assemble the list","ucStaleDealsStep3Desc":"The list will go to managers as a complaint, so it must not contain deals that were being worked outside CRM.","ucStaleDealsStep3Title":"Check the result","ucStarterPrompt":"Starter prompt","ucStarterPromptHint":"Copy the prompt or open it straight in a chat with the agent.","ucSupplierPayBest1":"There isn't enough money for all invoices at once, and the payment queue is put together in a notebook every week.","ucSupplierPayBest2":"Several dozen suppliers, each with their own terms and deferrals — you can no longer hold it in your head.","ucSupplierPayBest3":"Not a fit if deliveries are entered into the books a week late: you'll have to pay against documents that aren't in the system yet.","ucSupplierPayCheck":"Review the payment plan. List:\n— debts closed by a prepayment or an offset but still left in the calculation;\n— suppliers who have several records in the system, with the debt split between them;\n— rows where the payment term isn't filled in and the priority was set on your judgement;\n— days where the balance is only sufficient if the expected inflow arrives on time;\n— payments that can't be moved without approval — rent, taxes, payroll.\nDon't reorder anything silently: whatever you can correct yourself, show as a \"proposed changes\" list.","ucSupplierPayInputs":"MoySklad, 1C, Tochka. From you: the cut-off date, the list of accounts we pay from and the suppliers who must not be delayed.","ucSupplierPayStep1Desc":"The agent reads the debts and balances directly, nothing needs to be exported. If there are several current accounts, name the ones we pay from, otherwise the agent will pool them into one pot.","ucSupplierPayStep1Title":"Set the cut-off and the accounts","ucSupplierPayStep2Desc":"The agent counts overdue days from the contractual term rather than the delivery note date, and lays the payments out by day against the actual balance.","ucSupplierPayStep2Title":"Run the queue calculation","ucSupplierPayStep3Desc":"Before queuing the payment orders in the bank — make the agent review its own work","ucSupplierPayStep3Title":"Check the result","ucTaskAnalysis":"Analysis","ucTaskAutomation":"Automation","ucTaskContent":"Content","ucTaskDocuments":"Documents","ucTopicsLoadBest1":"It is time to rebuild the shift schedule, and the decision is being made on the feeling that \"Mondays are hard\".","ucTopicsLoadBest2":"The team is asking for one more operator, and you need to show which topic and which hours produce that increase.","ucTopicsLoadBest3":"Not a fit if there is less than six to eight weeks of history: on three points a trend cannot be told from a spike.","ucTopicsLoadCheck":"Check the load calculation. List:\n— topics that got fewer than [20] tickets over the period: their weekly dynamics mean nothing;\n— tickets that ended up in \"other\", and what they have in common;\n— conversations counted twice because the customer replied on different days;\n— weeks with holidays or an outage that must not be put into the trend alongside ordinary ones;\n— hours where the peak is explained by a single mailout rather than a steady flow;\n— what the data already shows for the shift schedule and what needs another [N] weeks of measurement.","ucTopicsLoadInputs":"Telegram, Avito, Email. By hand: the period, the list of topics or consent to the agent's own classifier, the shift working hours.","ucTopicsLoadStep1Desc":"Take at least eight weeks and name the shift boundaries and the time zone you count them in. If you already have a list of topics — give it, otherwise the agent will invent its own and next month will not line up with it.","ucTopicsLoadStep1Title":"Set the period and the shifts","ucTopicsLoadStep2Desc":"The agent counts one ticket per conversation rather than per message, and separates one-off spikes from steady growth.","ucTopicsLoadStep2Title":"Run the analysis","ucTopicsLoadStep3Desc":"These numbers move people around the schedule — the cost of an error is not a report but an empty or overloaded shift","ucTopicsLoadStep3Title":"Check the result","ucUnifiedInboxBest1":"Operators keep three tabs open, and the question \"who takes this one\" is settled by shouting in the team chat.","ucUnifiedInboxBest2":"A customer writes both on Telegram and by email — two people answer, or nobody does.","ucUnifiedInboxBest3":"Not a fit if the channels are already merged into a helpdesk: the queue becomes a second one and people stop opening it.","ucUnifiedInboxCheck":"Check the queue. List:\n— threads merged on an inexact customer match;\n— rows whose priority does not follow from my rule — explain each one;\n— tickets already answered in another channel but still hanging open;\n— service notifications, autoresponders and mailouts taken for tickets;\n— messages with no text — an attachment, a sticker, a voice note — that cannot be judged on substance;\n— what you can rebuild yourself and where you need my decision on the merging rule.","ucUnifiedInboxInputs":"Telegram, Avito, Email. By hand: the priority rule, the signals that identify one customer across channels, what counts as closed.","ucUnifiedInboxStep1Desc":"One primary condition and two or three tie-breakers — that is enough. Separately say which field you use to recognise the same customer across channels.","ucUnifiedInboxStep1Title":"Describe the priority rule","ucUnifiedInboxStep2Desc":"The agent gathers the messages, merges threads only on an exact match and next to each row shows why it has that priority.","ucUnifiedInboxStep2Title":"Run the merge","ucUnifiedInboxStep3Desc":"A queue is useful precisely because it is trusted without double-checking — so a wrong merge or a stray row costs more than it would in a report","ucUnifiedInboxStep3Title":"Check the result","ucUserPainsBest1":"Quarterly planning, when you need to pick not the most frequent thing but the most expensive one for the business.","ucUserPainsBest2":"A conversation with management where \"users are complaining\" does not work but \"this many did not come back\" does.","ucUserPainsBest3":"Not a fit if tickets cannot be linked to a person's later purchases: there will be nothing to compute the effect from, only frequency remains.","ucUserPainsCheck":"Check the top pain points. List:\n— pain points where the churn effect is computed and pain points where it is merely asserted — as two lists;\n— the sample size behind every effect figure and how many people could not be linked to purchases;\n— pain points that made the top thanks to one noisy channel;\n— complaints you merged into a single pain point, and by which signal;\n— cases where the number of users grew along with the complaints and the shares did not change;\n— which conclusions are verifiable against the data and which are your hypothesis; do not mix hypotheses into the top.","ucUserPainsInputs":"Telegram, Ozon, Wildberries. By hand: the quarter boundaries and what counts as churn and a repeat purchase for you.","ucUserPainsStep1Desc":"Say what counts as churn for you and over what period, otherwise the agent will invent its own rule. Specify which attribute links a ticket to a user.","ucUserPainsStep1Title":"Set the quarter and the definitions","ucUserPainsStep2Desc":"The agent groups recurring problems, counts the reach of each and separately what happened to those users after the ticket.","ucUserPainsStep2Title":"Run the analysis","ucUserPainsStep3Desc":"Before putting this into the quarterly plan — separate what was computed from what was assumed","ucUserPainsStep3Title":"Check the result","ucUserStoriesBest1":"The feature is agreed in broad terms, but the team needs wordings that can be estimated.","ucUserStoriesBest2":"When the edge cases are usually forgotten and surface in testing: empty state, external system failure, no permissions.","ucUserStoriesBest3":"Not a fit if the solution is still under discussion: you will get a set of stories for a scenario that does not exist.","ucUserStoriesCheck":"Check the stories. List:\n— requirements that were not in the feature description — where they came from;\n— acceptance criteria that cannot be checked without further agreements;\n— stories that cannot be estimated separately because they depend on neighbouring ones;\n— edge cases you closed with an assumption instead of a question;\n— places where one story is really three and will not fit into a sprint;\n— what can be worded out from the description and what a human must decide before the tasks are filed.","ucUserStoriesInputs":"Yandex Tracker, Kaiten. By hand: the description of the feature and its goal, the queue or board, your format for a story and acceptance criteria.","ucUserStoriesStep1Desc":"Give the goal, the audience and the boundaries — what is not part of this feature. If the team has its own story and acceptance criteria template, attach an example: the agent will reproduce its shape.","ucUserStoriesStep1Title":"Describe the feature and the format","ucUserStoriesStep2Desc":"The agent splits the feature into stories, writes checkable criteria for each and separately goes through the edge cases, flagging the places where there is no decision.","ucUserStoriesStep2Title":"Run the breakdown","ucUserStoriesStep3Desc":"Before taking the stories to estimation — check where the agent filled in the blanks for you","ucUserStoriesStep3Title":"Check the result","ucWbReturnsBest1":"The return rate grew and the reason isn't obvious from the dashboard reports.","ucWbReturnsBest2":"You need to work out whose area it is: the listing, the size chart, the packaging or the warehouse.","ucWbReturnsBest3":"Not a fit for items with one-off sales — on 5 orders the return rate means nothing.","ucWbReturnsCheck":"Review the analysis. List:\n— SKUs where the conclusion rests on fewer than [20] orders;\n— reasons you merged into one group, and on what basis;\n— cases where returns grew together with sales and nothing changed in relative terms;\n— losses with and without logistics — show both figures;\n— which of the conclusions can be verified from the data and which is your hypothesis.","ucWbReturnsInputs":"Wildberries. From you: the period and what we compare against.","ucWbReturnsStep1Desc":"State what we're measuring and what we compare against — the previous month or the same month last year. That determines what turns out to be seasonality and what is real growth.","ucWbReturnsStep1Title":"Pick the period and the comparison base","ucWbReturnsStep2Desc":"The agent calculates the return rate by SKU, category and warehouse and keeps defects, sizing and description mismatch separate — different people are responsible for them.","ucWbReturnsStep2Title":"Run the analysis","ucWbReturnsStep3Desc":"At small volumes the return rate jumps around on its own, so the conclusions are worth filtering","ucWbReturnsStep3Title":"Check the analysis","ucWhatYouNeed":"What you'll need","upgrade":"Upgrade","upload":"Upload","useCasesHubAll":"All use cases","useCasesHubEyebrow":"Use cases","workspace":"Workspace","yearly":"Yearly"}