Invoice clarification
Takes one invoice (passed in by your client's billing system) and answers customer questions grounded strictly in its line items, dates, and totals.
Use for the daily 'what is this charge?' tickets. It dramatically reduces back-and-forth on routine invoice questions.
It cannot reach into your client's billing system. If the customer's question requires data outside the invoice, the workflow stops and hands off.
- intake
- collect
- close
Provisioning the MCP URL for Invoice clarification is part of Pro.
Free accounts can read the YAML, run the Live Preview, and provision one starter URL. Pro provisions URLs for the whole catalog.
Open YAML. Read it before you subscribe.
The harness that enforces this YAML is closed and hosted. The YAML is what you can audit, fork, and reason about.
1# invoice-clarification.yaml2name: invoice-clarification3version: 1.0.04category: billing5description: Walks the customer through one specific invoice.6 7inputs:8 - name: invoice9 type: object10 required: true11 fields: [id, date, total, line_items]12 13constraints:14 ground_in: invoice15 refuse_outside: true16 17harness:18 - step: intake19 - step: collect20 answer_from: invoice21 refuse_if_outside: "I can only answer from this invoice. For anything else I'll hand you off."22 - step: close23 on_completion: ask_resolution24 Need invoice clarificationtuned to one client’s voice, escalation logic, and required fields? That’s a $99 personalization.
One-shot fee. Turnaround stated up front. The result is yours, with the deterministic harness already wired.
- Refund request intakeCollects structured refund-request information and produces a handoff packet for human review.
- Subscription cancellationHandles cancellation intake, captures the reason, and confirms the effective date — without retention pressure.
- Payment failure recoveryWalks customer through updating a failed payment method.