'customer' 검색 결과

Turn interviews, surveys, support conversations, and public reviews into evidence-based customer insights. Identify recurring problems, buying triggers, and customer language, then build research reports, quote collections, or personas and plan interviews or surveys to fill gaps.

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

• Analyze customer interview transcripts
• Find recurring themes in reviews and support tickets
• Build customer personas from research evidence

Review customer retention and customer success plans through six focused questions. Examine churn causes, customer segments, staffing capacity, hiring, and compensation, then produce a decision report with a verdict and three concrete next steps.

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

• Investigating declining customer retention
• Reviewing a proposed customer success team expansion
• Reassessing customer segments and service levels

Analyze SaaS customer data with three Python tools that calculate account health, rank churn risk, and prioritize expansion opportunities. Use repeatable weighted scores to plan customer outreach and prepare quarterly business reviews.

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

• Scoring customer health across an account portfolio
• Prioritizing outreach to accounts at risk of leaving
• Ranking upgrade and additional-seat opportunities

When the user wants to conduct, analyze, or synthesize customer research. Use when the user mentions "customer research," "ICP research," "talk to customers," "analyze transcripts," "customer interviews," "survey analysis," "support ticket analysis," "voice of customer," "VOC," "build personas," "customer personas," "jobs to be done," "JTBD," "what do customers say," "what are customers struggling with," "Reddit mining," "G2 reviews," "review mining," "digital watering holes," "community research," "forum research," "competitor reviews," "customer sentiment," or "find out why customers churn/convert/buy." Use for both analyzing existing research assets AND gathering new research from online sources. For writing copy informed by research, see copywriting. For acting on research to improve pages, see cro.

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

When the user wants to conduct, analyze, or synthesize customer research. Use when the user mentions "customer research," "ICP research," "talk to customers," "analyze transcripts," "customer interviews," "survey analysis," "support ticket analysis," "voice of customer," "VOC," "build personas," "customer personas," "jobs to be done," "JTBD," "what do customers say," "what are customers struggling with," "Reddit mining," "G2 reviews," "review mining," "digital watering holes," "community research," "forum research," "competitor reviews," "customer sentiment," or "find out why customers churn/convert/buy." Use for both analyzing existing research assets AND gathering new research from online sources. For writing copy informed by research, see copywriting. For acting on research to improve pages, see cro.

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

When the user wants to conduct, analyze, or synthesize customer research. Use when the user mentions "customer research," "ICP research," "talk to customers," "analyze transcripts," "customer interviews," "survey analysis," "support ticket analysis," "voice of customer," "VOC," "build personas," "customer personas," "jobs to be done," "JTBD," "what do customers say," "what are customers struggling with," "Reddit mining," "G2 reviews," "review mining," "digital watering holes," "community research," "forum research," "competitor reviews," "customer sentiment," or "find out why customers churn/convert/buy." Use for both analyzing existing research assets AND gathering new research from online sources. For writing copy informed by research, see copywriting. For acting on research to improve pages, see cro.

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

When the user wants to conduct, analyze, or synthesize customer research. Use when the user mentions "customer research," "ICP research," "talk to customers," "analyze transcripts," "customer interviews," "survey analysis," "support ticket analysis," "voice of customer," "VOC," "build personas," "customer personas," "jobs to be done," "JTBD," "what do customers say," "what are customers struggling with," "Reddit mining," "G2 reviews," "review mining," "digital watering holes," "community research," "forum research," "competitor reviews," "customer sentiment," or "find out why customers churn/convert/buy." Use for both analyzing existing research assets AND gathering new research from online sources. For writing copy informed by research, see copywriting. For acting on research to improve pages, see page-cro.

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

Identify customers whose purchases have fallen behind their usual rhythm, prioritize them by past value and warning signs, and draft personalized follow-ups. Send approved messages and log activity, stopping the sequence when a reply arrives.

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

• Finding regular customers who have stopped ordering
• Prioritizing customers for renewed contact
• Drafting personalized messages to reconnect

Plan customer retention and customer success staffing for a startup. Break down renewal and churn patterns, group customers by value and fit, and compare service models to guide resource allocation and hiring.

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

• Reviewing retention metrics and reasons for churn
• Allocating support investment across customer tiers
• Estimating customer success staffing needs

Automate Customer.io broadcasts and review delivery, open, and click metrics through Composio. Retrieve audience segments, newsletters, transactional message templates, and broadcast execution history to support targeting and track customer messaging.

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

• Triggering a configured broadcast for a selected audience
• Reviewing delivery, open, and click metrics
• Checking audience segments before targeting

Bring together public reviews, complaints, and customer activity to identify recurring issues and customers who may leave. Produce evidence-backed themes, review reply drafts in the owner's voice, and personalized messages to win back inactive customers.

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

• Finding recurring issues across reviews and complaints
• Drafting replies to positive and negative reviews
• Identifying customers whose ordering has slowed

Find prospective customers resembling your best existing customers, identify relevant decision makers, and rank them by fit, buying signals, and ease of contact. Results include reasons to reach out, source information, and a full XLSX list.

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

• Finding companies similar to your best customers
• Building a prioritized prospect list
• Identifying decision makers and contact routes

Manage the recorded list of vendors that process customer data and check advance notices and audit evidence. The skill also explains temporary staff access to customer accounts, including access limits, revocation, and the actions recorded in customer audit logs.

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

• Adding a vendor that processes customer data
• Checking notice timing before sending data to a new vendor
• Retrieving notification evidence for an auditor

Automate Customer.io broadcasts and review delivery, open, and click metrics through Composio. Retrieve audience segments, newsletters, transactional message templates, and broadcast execution history to support targeting and track customer messaging.

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

• Triggering a configured broadcast for a selected audience
• Reviewing delivery, open, and click metrics
• Checking audience segments before targeting

Define ideal customer profiles and buyer personas with structured frameworks. Use when the user asks about ideal customer profile, ICP, buyer persona, target audience definition, customer segmentation, customer research, user interviews, or persona creation. Trigger phrases include "ideal customer profile", "ICP", "buyer persona", "who is my customer", "target audience", "customer profile", "persona", "customer segmentation", "user research", "customer interview", "who should I target".

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

Turn raw customer material into evidence-backed personas and verbatim voice-of-customer language. Two modes - analyse sources the user already has (call transcripts, support tickets, survey responses, sales notes, reviews), or source new material from public places customers actually talk. Produces quoted pains, objections, and switch triggers that other skills consume, never invented ones. Use when the user says "customer research", "voice of customer", "what do our customers actually say", "we need real quotes", "analyse these call transcripts", "read our support tickets", "build a persona from data", "find what customers complain about", or when a persona is marked provisional. For structuring the finished persona into the knowledge base, see brand-context. For the JTBD persona template itself, see customer-persona.

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

Find customers’ exact words about a feature, objection, or competitor across meeting transcripts and emails. Organize quotes with speaker details, dates, sources, and context, while showing which accounts lack source coverage.

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

• Collect customer quotes about a feature
• Review objections raised during sales calls
• Find customer comments about competitors

Research customer questions using available internal documents, account history, support records, and public sources. Produce a brief with an answer, source references, confidence level, unresolved questions, and recommended next steps before drafting a customer response.

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

• Check product capabilities before answering a customer
• Find previous bug reports and known workarounds
• Review what a specific customer was told before

Use customer research, surveys, and usage data to define an ideal customer profile: the customers most likely to gain value, stay, and expand. Summarize their characteristics, buying behavior, goals, needs, and fit criteria to guide sales and marketing priorities.

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

• Defining ideal customers from surveys and interviews
• Finding patterns among customers who stay and expand
• Aligning sales and marketing priorities

Guides implementation of audience uploads, individual removals, and full replacements through the Data Manager API. It covers formatting and hashing identifiers, validating requests, and checking processing results for Customer Match and supported device ID audiences.

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

• Upload Customer Match audience members
• Remove selected users from an audience
• Clear or replace an entire audience

Guide a workshop that maps a specific customer’s experience from start to finish. Capture stages, actions, thoughts, emotions, and pain points, then produce a customer journey map and a prioritized list of improvement opportunities.

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

• Mapping the onboarding experience for new customers
• Finding obstacles between trial signup and first value
• Reviewing support experiences for customers at risk of leaving

De-escalate a customer crisis using a structured acknowledge-triage-DRI-cadence-resolution framework. Use when user says "customer escalation", "angry customer", "exec escalation", "customer threatening to leave", "fire drill", "critical customer issue", "customer is livid", "customer complaint escalated", or "how do I handle this" about a tense situation - even if they don't say "escalation" explicitly. Applies to CSMs and CS managers managing high-stakes customer crises.

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

Reviews a proposal, business case, deck or plan in character as a Customer Advocate archetype, the seat for paying customers not in the room, and returns a DRAFT review in the chat with a verdict, findings that cite the exact passage, customer-side risks, what would change the verdict and five interrogation questions. Use when the user asks to "run a customer advocate review", "do a voice-of-the-customer pressure-test", "what would our customers say about this" or "what does this plan really ask of paying customers". Do not use for the product evidence or roadmap case, use cpo-reviewer instead; for revenue or pricing strategy, use cro-reviewer; for the staff who operate the change, use frontline-skeptic-reviewer. Drafts for human review; never approves, authorises or signs off.

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

Use WooCommerce's customer and session APIs correctly — WC ships its own session handler (WC_Session_Handler, single wp_woocommerce_sessions table for both guests and logged-in users) and its own customer object (WC_Customer via WC()->customer), separate from $_SESSION / native PHP sessions / wp_get_current_user. AI consistently reaches for $_SESSION (breaks with page caching, setcookie (no signing, no namespacing), or user_meta for guests (impossible). The correct path is WC()->session->set/get for ephemeral per-visitor data, WC()->customer->get_billing_* for the active customer context including guests, and new WC_Customer($user_id) for one-off loads. Important — WC()->session is auto-initialized only on frontend requests (incl. admin-ajax); REST, cron, and WP-CLI must call wc_load_cart() explicitly. Use when storing per-visitor state, reading the current visitor's billing data, or debugging session loss across page caches / REST / cron. Triggers on WC_Session, WC_Session_Handler,...

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