corporate-invoice
Corporate Invoice
You're handling an invoice or billing request for corporate reimbursement.
Common Scenarios
"I need an invoice for my company"
After purchase, they can download and add company details from purchases page.
"I need an invoice BEFORE I purchase"
We don't do pre-purchase invoices for individuals. Exception: Large team orders (5+ seats).
"What's your VAT number?"
We're US-based, no VAT. Can provide EIN or standard invoice.
"Can you fill out this tax form?"
We don't fill foreign tax forms. Can provide our tax info document.
Sub-categories
- Post-purchase invoice edits (company details, reimbursement)
- Pre-purchase invoice/pro forma requests
- VAT/EIN and tax info requests
- Foreign tax forms or residency certificate requests
Phrases That Work
- "You can add details to your invoice and download it from your purchases page"
- "We're a US based company so we don't have a VAT number"
- "After purchasing we automatically create the invoice"
- "We don't create invoices pre-purchase unless it's for a larger team order"
- "We don't fill forms for foreign taxes"
Key URLs
Direct customers to their purchases page to edit invoices:
| Product | Purchases URL |
|---|---|
| Epic React | epicreact.dev/purchases |
| Total TypeScript | totaltypescript.com/purchases |
| Epic Web | epicweb.dev/purchases |
| Testing JavaScript | testingjavascript.com/purchases |
Tone
- Helpful but clear about limitations
- No apologies needed for standard policies
- Direct them to self-service when possible
- Offer EIN as alternative to VAT
What NOT To Do
- Don't create custom invoices for individual purchases
- Don't fill out foreign government tax forms
- Don't promise things that require manual work unless necessary
Validation
Draft must:
- Provide a path forward (link or instructions)
- Be clear about limitations if declining
- NOT create custom invoices for individual purchases
More from skillrecordings/support
vercel-cli
Deploy and manage Vercel projects via CLI. Use when deploying apps, managing environment variables, configuring domains, or pushing secrets to Vercel. Triggers on deploy, vercel, env vars, production.
4ai-sdk
Comprehensive guide to AI SDK v6 for agent development, tool definitions, multi-step agentic workflows, and result extraction patterns
2lesson-content-question
Answer lesson-specific content questions. Use when a customer asks about a lesson, code example, or concept in a course.
2email-change
Transfer licenses to a new email address. Use when a customer wants to change account email, move a license, or update access after a job change.
2front-api
Reference for Front REST API integration. Use when working with Front API schemas, nullable fields, webhooks, or debugging Front SDK issues.
2course-builder-incident-forensics
Diagnose production incidents for any course-builder app (ai-hero, epic-web, etc.) across Axiom, Vercel logs, source code, and DB preconditions. Use this whenever a course-builder app has 4xx/5xx spikes, `/api/inngest` failures, shortlink/post-linking failures, or someone asks "what account/deploy/path is failing right now?
2