Build an invoice on any conversation and 3650HQ renders it as a PDF and sends it straight to the customer over WhatsApp, or as an email attachment if you're talking to them on Gmail or IMAP. No separate invoicing tool, no copy-pasting a price into a text bubble.
3650HQ generates and sends the invoice PDF and tracks its status (draft, sent, paid, void). Getting paid on it is a separate, connected step: see how in-chat payment collection works.
A sale that happens in a WhatsApp thread usually gets invoiced the same way it was negotiated: by typing. Someone totals the order in their head, types a figure into a chat bubble, and the conversation moves on. It works until it does not. The figure is now a message in a thread with four hundred other messages, indistinguishable from the haggling that preceded it, and there is no document to point at when the customer says they were quoted something else.
The knock-on problems are the expensive ones. There is no invoice number, so nothing reconciles against the bank statement at the end of the month. There is no record of what was actually ordered, only a running conversation you have to re-read. And there is no status: nobody can answer whether a given order was invoiced, whether the invoice went out, or whether it was ever paid, without scrolling.
An invoice solves this by being a separate object from the conversation while still living inside it. 3650HQ builds one on the thread, renders it, sends it in the same chat, and then tracks what happens to it.
An invoice is built on the conversation it belongs to, so the customer is already attached and you are not re-typing a phone number into a separate app. You add line items with quantities and prices, and 3650HQ renders a clean PDF.
Invoice numbers increment across your whole workspace rather than per conversation, so they behave the way an accountant expects: no gaps, no duplicates, and no two agents independently issuing invoice 004.
An order is rarely one thing. Each item carries its own quantity and unit price, and totals are denominated in the currency your workspace bills in, so a Lagos customer sees naira rather than a dollar figure they have to convert.
The customer receives an actual PDF in WhatsApp, the same way they would receive one by email. If the conversation started on Gmail or an IMAP mailbox instead, the invoice arrives as an email attachment. They do not have to install anything, sign up for anything, or open a link to view it.
Every invoice moves through draft, sent, paid and void. That status is what makes it possible to answer questions about money without re-reading conversations, and it is what the payment and delivery steps key off.
3650HQ's AI agent can draft an invoice from the conversation it is reading. If a customer has spent ten messages settling on two items and a quantity, the agent can turn that into line items rather than making you re-key them.
What it will not do is send that invoice on its own. A drafted invoice is a draft: it sits there until a human reviews it and sends it. This is a deliberate line rather than a missing feature. The same principle applies elsewhere in the product, where the AI that replies to public comments is given read-only tools and cannot reach invoicing or payment at all. Anything that moves money, or commits you to a number in front of a customer, gets a human in front of it.
Sending an invoice is only useful if getting paid on it is not a separate manual chore. In 3650HQ the invoice is what the rest of the order hangs off: sending one generates a dedicated virtual bank account for that specific order, the customer transfers into it from their normal banking app, and the invoice marks itself paid once the transfer is verified server-side.
Once it is paid, a courier can be booked against that same invoice and the customer gets a tracking link in the same thread. The invoice is the spine of the order, which is why it is worth having a real one rather than a number typed into a chat bubble.
Yes. Build an invoice on any thread inside 3650HQ, and it's rendered as a PDF and sent to the customer directly in WhatsApp.
Yes. Invoices use sequential numbering per workspace, support multiple line items, and are priced in your local currency.
Yes. 3650HQ's AI agent can draft an invoice from a conversation, which you review before it's sent.
It moves from draft to sent, and once the customer pays, it's automatically marked paid. See 3650HQ's in-chat payment collection.
Yes. Numbering increments across the whole workspace rather than per conversation, so there are no gaps or duplicates and two agents cannot independently issue the same invoice number.
Yes. If the thread is a Gmail or IMAP mailbox, the invoice is delivered as an email attachment instead of a WhatsApp document. The invoice itself is identical either way.
Your workspace's local currency. 3650HQ bills in NGN, GHS, KES, ZAR and USD, so a Nigerian business invoices in naira rather than quoting a dollar figure the customer has to convert.
Yes. An invoice can be voided, which is a distinct status from paid or sent, so the record of what happened stays intact rather than the invoice quietly disappearing.
No. It arrives as a PDF in the conversation they are already in. There is nothing to install, no link to click through and no account to create.