Use when a support account wobbles or a quarterly business review looms: read the health signals, run the success plan, and prep the review from evidence.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when a customer waits for an answer on any channel: a reply in company voice, grounded in docs, staged for the owner's yes.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
실행 점수 미검증
설치 방법 보기설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.
Use this when a customer waits for an answer on any channel: a reply in company voice, grounded in docs, staged for the owner's yes.
You need the ticket and its priority, the help-center or policy passage that governs it, the customer's name and history, and the company voice notes.
Find the governing help-center or policy passage and cite it; anything unwritten is marked as such and becomes a knowledge-base (KB) candidate, never a quoted rule.
Write short sentences with the customer's name, what you found, what happens next with a date and an owner, and one concrete step the customer can take now. State what you CAN do and when and how it resolves. Match the channel: phone notes get a talk track, chat gets two short messages max per turn, email gets a subject line, social gets public-safe wording plus a move to private — no customer name, account detail or case history in the public post, whatever the wording. Banned phrases: 'sorry you feel that way', 'unfortunately I can't', 'your call is important', and 'can I help with anything else' when nothing was solved.
Acknowledge, own, offer — in Problem-Solution-Benefit order: a sincere apology first (it wins back more than credit), then repeat the problem, share the solution and actions, and explain the benefit. Name the feeling, take responsibility for the experience, propose one concrete next step. Never blame, never jargon, never invent a date, amount, or policy.
Show the draft in chat, take one round of edits, then stage it as the canonical draft against the ticket. Anything money, exception, or externally visible waits for the owner's yes in the same conversation.
Deliver the staged reply above, channel-shaped, with its citation. Offer to log it to the ticket or CRM when connected, as a draft they approve first.
No governing doc means a reply built from the ticket and the owner's word, with every load-bearing line marked UNVERIFIED until the doc exists. Never send, post, refund, or promise anything without the owner's yes.
아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.
로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.
아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.
Use when a support account wobbles or a quarterly business review looms: read the health signals, run the success plan, and prep the review from evidence.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Reconcile accounts by comparing GL balances to subledgers, bank statements, or third-party data. Use when performing bank reconciliations, GL-to-subledger recs, intercompany reconciliations, or identifying and categorizing reconciling items.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Review open receivables and draft factual, staged payment follow-ups without inventing status or contacting a customer.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Write ad variants that each test one idea, within platform limits and supported claims.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use on the first conversation with Alex, or whenever their memory has no product preferences yet: learn what the user is building and who for, where specs, roadmap and numbers live, who decides dates and scope, and get them to a first real product deliverable.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when a strategic alliance needs joint selling governance: operating model, joint targeting, steering prep, and milestone accountability.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.