'self-service' 검색 결과

Use this skill when designing the UX and content strategy for a Salesforce-powered self-service portal or help center — pre-deflection article surfacing, Help Center search UX, friction-calibrated case submission forms, community peer support layers, and deflection measurement. Trigger keywords: design self-service portal, case deflection strategy, help center UX design, reduce support volume with self-service, knowledge base search experience. NOT for picking which contact reasons to deflect and through which channel — use architect/case-deflection-strategy. NOT for building the Experience Cloud site itself — use admin/experience-cloud-site-setup. More trigger keywords: article visibility matrix IsVisibleInCsp IsVisibleInPkb, which articles show in the customer portal, case visibility for portal users, CaseComment IsPublished customer visible comment, self-registration profile and account for a portal, Help Center template does not support login, deflection metrics SOQL KnowledgeArticleViewStat, self-service journey map, moderation policy for a support community.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when gathering requirements for a customer portal, partner community, or self-service Experience Cloud site. Triggers: 'gathering requirements for customer portal', 'planning Experience Cloud site', 'what license for community portal', 'portal user journey mapping', 'self-service requirements'. NOT for building the site in Experience Builder — use admin/experience-cloud-site-setup. NOT for designing the deal-registration and MDF processes themselves — use admin/partner-community-requirements. More trigger keywords: portal persona licence matrix, which Experience Cloud licence do these requirements imply, external user needs a Contact and Account, sharing set vs sharing rule for a portal, self-registration vs SSO for a portal, portal requirements catalogue, handoff to Experience Cloud site setup.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use this skill when driving adoption of CRM Analytics (Einstein Analytics) across an org — the Analytics Adoption App for measuring who uses which dashboards, embedding analytics into Lightning pages, pinning dashboards to the Analytics home page, self-service personas, and analytics success metrics. Triggers: analytics adoption, dashboard usage tracking, embedded analytics strategy, self-service analytics enablement, CRM Analytics rollout. NOT for building the dashboards — use admin/analytics-dashboard-design. NOT for the app, datasets and lenses — use admin/crm-analytics-app-creation. NOT for non-analytics rollout training — use admin/change-management-and-training.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Expert en platform engineering (developer experience, IDP, golden paths, self-service, métriques)

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Plan how users discover, try, and pay for a product through self-service. Compare product-led growth with sales-led approaches, improve the first useful experience, assess acquisition channel economics, and identify when sales support should step in.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Choose between product-led and sales-led growth
• Improve the first useful product experience
• Review free-to-paid conversion

Turn resolved support issues, recurring questions, and workarounds into help article drafts customers can search and follow. Choose an appropriate format, organize instructions clearly, and include metadata, source references, and publishing review notes.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Turning a resolved support ticket into a help article
• Documenting answers to recurring questions
• Explaining a known issue and its workaround

Compare seven customer acquisition approaches against your product, audience, budget, and team. Get fit scores, a prioritized mix of channels, suggested tools, and a 90-day execution plan covering resources, milestones, and success metrics.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Choosing customer acquisition channels for a product
• Comparing content marketing with direct sales outreach
• Assessing growth through product trials and self-service

Investigate Google Cloud access denials and choose a resolution path based on the caller’s permissions. Supports temporary access activation, structured escalation tickets, policy analysis, and administrator selection of roles that grant only the permissions needed.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Investigating Google Cloud access denials
• Activating temporary access for development
• Preparing access issue tickets for administrators

Choose a sales approach based on product price, complexity, and buyer needs. This skill helps plan self-service trials, human sales involvement, and experiences that let prospects recognize value before purchasing.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Choosing between product-led and sales-led growth
• Improving conversion from free users to paying customers
• Reducing the time until users first experience value

Plan customer acquisition as a solo founder, from choosing tools and sales channels to assigning work to AI agents. Organize priorities by revenue stage, divide time between building and selling, and assess when hiring makes sense.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Planning customer acquisition as a solo founder
• Dividing marketing and sales work among AI agents
• Choosing between self-service signup and sales calls

Builds the help center, in-product guidance, and knowledge base that let customers resolve problems without contacting anyone — content, findability, maintenance, and deflection measurement. Use this to build or fix a help center, reduce support volume, write documentation for customers, improve findability, or decide what deserves a help article versus a product fix.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Für Klausel Checkliste Self Service: ordnet Norm, Beweislast und Gegenargument; Ergebnis: Prüfprodukt mit Risiko und nächstem Schritt.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Build internal developer platforms (IDPs) with self-service infrastructure, golden paths, and developer portals using Backstage, Crossplane, and score.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Design and implement Internal Developer Platforms (IDPs) with self-service capabilities, golden paths, and developer experience optimization. Covers platform strategy, IDP architecture (Backstage, Port), infrastructure orchestration (Crossplane), GitOps (Argo CD), and adoption patterns. Use when building developer platforms, improving DevEx, or establishing platform teams.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

FAQ identification from support tickets, step-by-step tutorial creation, screenshot/video script guidance, search optimization, and self-service deflection tracking.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Expert guidance for Evidence, the open-source BI framework that generates beautiful, interactive dashboards from SQL queries and Markdown. Helps developers build data reports as code, deploy them as static sites, and create self-service analytics without heavy BI tools.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

DevOps 与站点可靠性工程 (SRE) — 平台 / 基础设施 / 可靠性工程师的认知操作系统, 覆盖软件交付 + 运维全生命周期 (CI/CD 与发布工程 trunk-based + 渐进式发布 canary/blue-green/feature flag + GitOps Argo CD/Flux / 基础设施即代码 Terraform/OpenTofu/Pulumi/Ansible + policy-as-code OPA / 容器与编排 Docker/Kubernetes + Helm/Kustomize + service mesh Istio/Linkerd / 可观测性 Prometheus + Loki + OpenTelemetry + Honeycomb + eBPF + RED/USE / SLO-SLI-error budget 与可靠性工程 Google SRE 学科 + 容量规划 + 优雅降级 / 事件管理与 on-call 事件指挥 + PagerDuty + runbook + 无指责复盘 + MTTR / 云平台与 FinOps AWS/GCP/Azure + 成本优化 + 弹性伸缩 / 平台工程与开发者体验 IDP + Backstage + golden path + Team Topologies / DevSecOps 与供应链安全 shift-left + SBOM + SLSA + sigstore + Vault / 韧性与混沌工程 fault injection + game day + 安全科学 / DORA 指标与工程效能 部署频率 + 变更前置时间 + 变更失败率 + Accelerate 研究 / 数据库与有状态运维 schema 迁移 + 备份容灾) — 不含 通用应用开发 / 纯云销售认证速成 / 'DevOps = 跑 Jenkins 的岗位' 窄化误解 / ITIL 工单文化传统运维 (旧范式仅做边界) / 把手工运维 ClickOps 当稳态 (是 toil, 本 skill 核心反模式) (DevOps & Site Reliability Engineering — the cognitive operating system of platform / infrastructure / reliability practitioners who own the full software delivery + operational lifecycle, covering (a) CI/CD & release engineering (build pipelines, trunk-based development, progressive delivery — canary / blue-green / feature flags, GitOps with Argo CD / Flux), (b) Infrastructure as Code (Terraform / OpenTofu, Pulumi, CloudFormation, Ansible, Crossplane — module design, state management, drift, policy-as-code OPA / Sentinel / Checkov), (c) containers & orchestration (Docker / OCI, Kubernetes — scheduling, networking CNI, storage CSI, operators / CRDs, Helm / Kustomize, service mesh Istio / Linkerd), (d) observability (the three pillars + beyond — metrics Prometheus / VictoriaMetrics, logs Loki / ELK, traces OpenTelemetry / Jaeger / Tempo, high-cardinality observability Honeycomb, eBPF, RED / USE methods, SLO-based alerting), (e) SLO / SLI / error budgets & reliability engineering (Google SRE discipline — service level objectives, error budget policy, toil budgets, capacity planning, load shedding, graceful degradation), (f) incident management & on-call (incident command, PagerDuty / Opsgenie, runbooks, blameless postmortems, MTTR / MTTD, error budget burn), (g) cloud platforms & FinOps (AWS / GCP / Azure well-architected, multi-region, cost optimization, autoscaling), (h) platform engineering & developer experience (internal developer platforms, Backstage, golden paths, self-service, Team Topologies), (i) DevSecOps & supply-chain security (shift-left, SAST / DAST, SBOM, SLSA, sigstore / cosign, secrets management Vault), (j) resilience & chaos engineering (chaos experiments, fault injection, game days, resilience engineering / safety science), (k) DORA metrics & engineering effectiveness (deployment frequency, lead time, change failure rate, MTTR, the Accelerate research), (l) databases & stateful operations (schema migrations, backups / DR, replication); NOT generic software development / app feature coding (是 平行学科, DevOps/SRE 关注 delivery + operability 不是 product feature), NOT pure cloud sales / certification cram without operational depth, NOT 'DevOps = a job title that runs Jenkins' 的窄化误解 (DevOps 是 文化 + 实践, SRE 是 Google 对 reliability 的工程化具体实现), NOT ITIL-heavy 传统运维 工单文化 (是 被 DevOps 取代的旧范式, 仅做边界标注), NOT manual ops / ClickOps as a steady state (是 toil, 本 skill 的核心反模式).) Master OS — automated mastery of DevOps & Site Reliability Engineering — the cognitive operating system of platform / infrastructure / reliability practitioners who own the full software delivery + operational lifecycle, covering (a) CI/CD & release engineering (build pipelines, trunk-based development, progressive delivery — canary / blue-green / feature flags, GitOps with Argo CD / Flux), (b) Infrastructure as Code (Terraform / OpenTofu, Pulumi, CloudFormation, Ansible, Crossplane — module design, state management, drift, policy-as-code OPA / Sentinel / Checkov), (c) containers & orchestration (Docker / OCI, Kubernetes — scheduling, networking CNI, storage CSI, operators / CRDs, He

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Designs AI-first help centers and self-service support. Use when shaping taxonomy, article templates, or content and answer contract for support AI, not the bot build.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Schadenfall-Guide und Entscheidungslogik. Leitet Schritt fuer Schritt durch jeden Schadenfall (Unfall, Krankheit, Haftpflicht, Hausrat, Auto, Rechtsschutz, Todesfall, Invaliditaet). Liefert Self-Service-Checklisten, klaert wann und wie melden, welche Nachweise noetig sind, und wie Fristen und Kommunikation laufen. Schweizer Kontext als Standard. Triggert bei Fragen zu Schadenfall, Schadenmeldung, Unfall melden, Versicherung melden, was tun bei Schaden, Schadenformular, Versicherungsfall, Schadenanspruch, Frist versaeumt, Versicherung zahlt nicht, Leistungsablehnung, Einsprache, Schadenregulierung.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Transition from static LLM chats to autonomous agents that execute multi-step tasks. Use this when you need to automate cross-platform reports (e.g., Snowflake to Google Docs), build self-service tools for non-technical teams, or create "anticipatory" engineering workflows that draft PRs based on Slack discussions.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Maintain local identity database transactions, file locking and atomic persistence, cross-instance credential revocation, authenticated self-service operations, TOTP replay/lockout state, and external-account attachments.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Uses Bubble's Plugin API and the Stripe.js SDK to embed a self-service subscription management portal inside a Bubble application. Configures Bubble's API Connector to call Stripe's Billing Portal Sessions endpoint and handles webhook events for real-time plan change updates.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when a task needs the judgment of a Business Intelligence Analyst — reconciling a metric discrepancy between reports, designing a dimensional model or semantic layer for self-service dashboards, setting a data freshness/latency SLA, or diagnosing why a dashboard's aggregate number is misleading.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Diagnoses, remediates, and manages Google Cloud Identity and Access Management (IAM) access issues. Supports two distinct operational modes: (1) Requester Flow for developers encountering access denials (capturing error context, self-service PAM JIT activations, elevated developer self-remediation, or logging structured tickets), and (2) Resolver Flow for privileged administrators (authoritative Policy Troubleshooter analysis, deny policy exemptions, least-privilege role discovery, and PAM/IAM provisioning).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.