Pipelines and sales
Bill a client and see what you were paid
Products, invoices, coupons, and the money reads, without opening the billing screen.
What you'll get
- An invoice raised against a real contact, itemised and priced, without touching the billing screen.
- A promo code you can hand out, and a product catalogue Claude can price from.
- A straight answer to "what came in this month", read from the account rather than a dashboard.
Say this
Invoice Dana Miller 250 dollars for a consultation, due in 30 days.
Show me every unpaid invoice.
Make a 10 percent promo code called SPRING10.
What payments have come in this month?
The pro prompt
The exact ask we run on real client accounts
Proven liveIn my [MCP Testing] account, raise an invoice for [Dana Miller] for [one consultation at 250 dollars], due [30] days from today. Build it as a draft and read it back to me with the total, the currency and the line items, so I can check it before anyone sees it. Do not send it. I will send it myself once I have read it.
Click the box to select it, then press ⌘C (or Ctrl+C)
Everything in [brackets] is yours to change. The last line matters more than the rest: sending is the step that reaches a real person, and it is the one thing worth doing with your own eyes on the screen.
What happens when you ask
- Claude finds the contact and reads their details, because an invoice carries the client's name and email on its face, not just a link to their record.
- It builds the invoice as a draft, priced in your account's currency, and reads it back with the total.
- It stops. Nothing is emailed until you say so.
Good to know
- Invoices are created as drafts and stay that way until sent. A draft costs nothing and can be deleted; a sent invoice has landed in someone's inbox and cannot be unsent.
- Say "do not send" in the ask when you are experimenting. Claude honours it, and it removes the only irreversible step in the whole flow.
- New invoices are real and payable by default. If you want one that cannot be paid, for a demo or a screenshot, ask for a test-mode invoice explicitly.
- Products are the catalogue, invoices are the bill. Creating a product does not create a price on its own, so ask for the price in the same breath if you want one attached.
- Coupons need a code, a type (percentage or fixed) and an amount. Without all three GHL rejects it.
- "What was I paid" is a different question from "what did I invoice". Ask for transactions or orders for money that actually moved, and for invoices for money you asked for.
- Invoicing needs the full license. The Free plan can read invoices and payments but not raise them.
Where people go wrong
| What happened | The fix |
|---|---|
| "Creating an invoice used to just fail." | It did, for everyone, until 3.65.2. The call was missing six fields GHL requires and crashed its server rather than telling us. Update and it works. |
| "It sent before I was ready." | Say "do not send it" in the ask. Sending is the only step here that reaches a customer. |
| "The invoice shows the wrong name or no email." | Those come from the contact record, not the invoice. Fix the contact first, then raise the invoice. |
| "My revenue number looks too low." | You are reading invoices, which is money requested. Ask for transactions instead, which is money received. |
| "The promo code was rejected." | A coupon needs all three of code, type and amount. Percentage discounts take a number like 10, not "10%". |