Handling Billing Questions with a Purpose-Built Agent Skill

Where this fits

A customer disputes a charge from two months ago. Your agent needs to decide whether to refund, and how to communicate the timeline. Without a clear policy, the agent either overpromises or stalls. The billing skill from the AgentFootprint repository encodes a refund policy directly into the agent’s workflow, so it can handle these cases consistently and safely.

Why agents benefit

• Identity first: The skill mandates order ID and last four digits of the card before any action, preventing unauthorized refunds.
• Age‑based refund logic: It automatically applies full refunds for orders under 30 days, records a reason for 30–90 days, and escalates past 90 days without promising anything.
• Timeline guardrails: Agents never quote a refund timeline shorter than three business days, avoiding unrealistic expectations.
• Structured escalation: For older orders, the agent knows to say a specialist will follow up, keeping the conversation within policy.
• Covers broader billing: Beyond refunds, it handles disputed charges and invoice questions, reducing the need for multiple custom prompts.

Practical scenarios

Refund under 30 days

A customer asks for a refund on an order placed 10 days ago. The agent verifies the order ID and card digits, then immediately offers a full refund with a three‑business‑day timeline — no extra approvals needed.

Disputed charge at 60 days

The customer claims they were double‑charged two months back. The agent checks the order age, records the reason on the ticket, and processes a refund without promising a specific date. It also notes that a human may review if needed.

Invoice question for a subscription

A user asks about an upcoming invoice. The agent uses the skill’s billing context to explain the charge, confirm the payment method, and offer to send a copy — all while verifying identity first.

Add it to your agent workflow

Install the skill with:

npx skills add footprintjs/agentfootprint --skill billing

Then reference it in your agent’s instructions. For example:

When a user mentions a refund, dispute, or invoice, use the billing skill. Always start by asking for the order ID and last four digits of the card. Follow the refund rules exactly.

The skill’s README provides the full policy, so your agent can load it at runtime and apply the rules without hard‑coding them into your system prompt.

Compare before adopting

Before adding this skill, compare it against alternatives. Check how recently the repository was updated and whether the policy matches your own business rules. Look at the stars (currently 20) and any forks or issues to gauge community trust. Also consider whether a generic billing prompt would suffice — this skill is useful when you need consistent, policy‑driven behavior without reinventing the rules each time.

Why it is worth tracking

This skill is a small but well‑defined example of an agent‑ready policy. Its quality signals — clear README, explicit rules, and a focused scope — make it a good candidate for teams that want to avoid ad‑hoc billing logic. As the AgentFootprint repository grows, watch for updates to the refund thresholds or new billing sub‑skills. For a broader catalog of agent skills, see the listing at OpenAgentSkill. Evaluate it when you need to standardize billing responses across multiple agents or when you start seeing inconsistent refund decisions from your current prompts.