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 the support team needs a report card, not a feeling: score real threads, track CSAT and average handle time from the records, and draft the one fix per rep.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
실행 점수 미검증
설치 방법 보기설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.
Use this when the team needs a report card, not a feeling. Score real threads against a rubric, read CSAT and handle time from the records, and draft the one fix per rep.
The thread sample with dates and reps, the CSAT and average handle time (AHT) records with source and period, the QA rubric or talk track in play, and the last review's fixes.
Score on weighted dimensions the team agreed: acknowledgement speed, accuracy against docs and policy, resolution or a clear next step with a date and owner, tone and positive language, and logging. Calibrate before scoring — two reviewers score the same three threads and settle the differences — or the numbers are opinion. A rubric you cannot find gets the five dimensions above, marked INFERENCE, with a request for the official one.
A fixed sample per rep per week — newest, oldest, one escalated, one refund-adjacent — never cherry-picked wins. Score each thread with the quoted line behind every mark. A thread you cannot read is not scored.
CSAT with its response rate and sample size — a 4.6 on nine responses is not a trend; AHT beside first-contact resolution, never alone, because faster is not better if the customer writes back; reopen rate as the check on "resolved". Trend against last period with the source and period on every number. Never fill a number from memory.
One quoted miss, the better line, why it is better, and a re-check date. Praise one quoted win in the same note. The team-wide pattern — the miss three reps share — becomes a macro, a knowledge-base fix, or a talk-track change, staged for the owner.
The scored sample with quotes, the metric read with trends and sources, and the per-rep coaching drafts. Coaching notes go to the owner as drafts — never delivered to a rep or published as a score by you.
Thin records mean fewer scored threads, not padded scores. Say which record would settle each UNKNOWN.
아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.
로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.
아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.