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/contact-policy.md

View on GitHub
# Contact and action policy

## Match the offer to responsibility

- **Verified site administrator or site-wide procurement/licensing owner:** lead with Full only. Explain site-wide use, unified licensing and the upgrade. Do not include the $299 single-space alternative, even if no reseller is listed.
- **Actual user or space owner:** a verified single-space need can justify the single-space option. Confirm scope and current pricing. Do not assume every user owns a space or can approve spending.
- **Unverified role / technical contact:** state the known relationship, use Full as the site-wide context when relevant, and gently ask them to forward to the colleague responsible. Do not call them admin or invent decision authority.
- **Reseller/partner:** procurement channel is separate from contact responsibility. Label public Full list pricing as such; let the existing partner confirm their final quote. Do not imply a quote was approved or that we contacted the partner when neither happened.

Use the shared live Marketplace pricing implementation for Full. The locally configured single-space price is an internal reference, not proof of a current checkout price. Do not hardcode seat break-even points or compute annual price as ten monthly payments.

## Message shape

1. Remind them which app and host product this concerns. After a gap, link the verified Marketplace listing using its actual name, including Confluence where relevant.
2. Use customer-provided needs or prior correspondence as context. Keep internal telemetry out of customer messages: account counts, page/space activity, timestamps, inventory and inferred usage belong in private analysis; exposing them can make customers feel monitored.
3. Express interest in helping without usage claims or rankings.
4. Ask one easy next step: feedback, forwarding to the right colleague, or whether a quote would help. Avoid interrogating them about budget, ownership and procurement all at once.

The user's priority is adoption and converting a good-fit customer; flexibility can be discussed without inventing a discount or committing to an unapproved commercial term.

## Authorisation follows the actual request

Track action, actual recipient(s) or explicit batch, channel, content/template scope, timing and any constraints. An approved administrator is not permission to contact all administrators. A one-off batch is fixed to its authorised members. A genuinely dynamic or recurring authorisation follows the user's stated scope and end condition; do not add an arbitrary expiry.

Queries, analysis, drafts and tracker organisation do not confer sending or license-grant authority. Explicit permission already present in the conversation remains effective; do not ask again merely because a skill is entered or an item changes. Clarify only missing information needed to execute or a material action outside the scope. Where necessary, present the finished draft before asking.

"Don't send" overrides an earlier send plan. "I sent it" means inspect Sent and record the actual message, not send the draft again. Scheduled messages require their own verified status; cancellation must be explicit before marking cancelled.

These Markdown policies do not remove tool access from the agent; they are workflow rules, not technical isolation.
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: 323kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 323kUpdated 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: 323kUpdated Claude CodeCodexVerifiedInstall