Skip to content

ZenUml/conf-app / .claude/skills/customer-followup

customer-followup

Verified

Prioritise Confluence customers for conversion, retention, win-back or pause using lifecycle, feedback, license, usage and conversation evidence. Draft follow-ups and update the tracker within the user's authorised scope; reuse existing query skills.

references/records.md

View on GitHub
# Portable customer record contract

The storage adapter maps these meanings to current header names, never fixed column letters or row numbers. Re-read table headers and find the row by stable ID before editing. Fail clearly on missing/duplicate IDs; do not select a customer by display-name resemblance alone.

## Opportunity summary

One opportunity per customer site + product + commercial goal. Related spaces stay in one opportunity unless separate buying processes justify another. Full and Lite usage can be compared, but licenses and events retain variant identity.

- Stable opportunity ID; company/domain and verified site key; product; goal/type.
- Opportunity stage: pending needs, contacted, waiting for customer, confirming buying conditions, procurement, won, declined, paused. For a purchase/renewal goal, a matched valid non-zero order with effective commercial license establishes won, regardless of Open settlement status. Refund/cancelled/free-only records and a commercial license without order evidence do not. A commercial win does not close unresolved technical work.
- License summary, payment status and their evidence date: separate fields. Payment values distinguish not checked, no matching transactions found, transactions recorded with settlement unconfirmed (retain Open/unknown), explicitly reported paid, partially paid and refunded. Do not turn unknown into unpaid or label a recorded Open order “no payment record”. Reported paid is not proof of vendor bank payout.
- Current blocker, next action, owner and next review date in a documented timezone.
- Main contact, decision-maker and role evidence (role unknown is valid).
- Potential annual value + currency + estimate/list/quote/contract basis and date. This is not received revenue.
- Evidence links and latest meaningful record reference.
- Pause reason and observable resume condition, or result date and closure reason.

Keep the summary short. Full messages stay in Gmail/tickets, license/transaction records in their source, and longer analyses in private Handbook files. An archive is not a refreshed fact.

A later full refund/reversal is a new outcome, not evidence the historical purchase never happened. Preserve its history, record the refund and current license facts, and do not present it as a retained active win. If the selected tracker has no truthful refunded/reversed stage, flag that mapping gap; do not invent a rejection or automatically reopen sales follow-up.

## Activity log

Append one row per meaningful actual communication, signal check or decision. Include record date, opportunity ID, contact, channel, factual summary (quotes clearly labelled), action taken, outcome/interpretation, evidence link, owner, record type, action status, execution time/timezone and stable activity ID.

Action states: draft, scheduled, sent, received, cancelled, failed, pending verification, not applicable. Old mixed records may retain "see original record"; do not fabricate exact transitions during migration. Preserve existing IDs; when importing old history mark it explicitly as historical organisation and preserve the evidence date.

## Safe write and verification

1. Inspect current values and latest activity. Preserve unrelated edits, formulas, formats, validation and source links.
2. Match source message/ticket/event identifiers to existing records before appending. A retry must not duplicate a sent event. If two actions are genuinely different, retain both.
3. Append the verified activity, then update affected summary fields consistently: commercial stage, outdated approval/blocker/next-action wording, result date and evidence link as warranted. A status-only request excludes proposing or executing new outreach, not correction of stale stages. Use the evidenced commercial event date for the result date; label unknown dates rather than using a query timestamp as the event. Keep raw settlement status separate. If an edit was only prepared, leave status as draft/pending and say where it is stored.
4. Re-read saved values, record ID and source link. For structural changes also verify table ranges, validation values, formulas and a screenshot. Flag partial writes for reconciliation; do not announce success for an unsaved tracker update.

Pause and payment do not overwrite communication history. Formulas are presentation aids, not authority for sending, billing or resuming contact. A review date schedules human attention; it creates no automation.

## When Sheets becomes insufficient

Revisit storage when multiple simultaneous buying processes, large contact relationships, frequent concurrent writes or missed/duplicated actions cannot be handled reliably by two tables and source links. Preserve this contract if moving to another CRM; do not embed its APIs into the decision policy.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall