Customers
Who an organization serves and what each was promised, kept beyond any one conversation
Every organization can keep a customer book: its customers, and what each was promised, by when and by whom. A promise past its day shows in Needs you, so nothing promised in a chat is forgotten when the chat ends.
The customer book is in early access and stays off until n8v switches it on for an account. It counts for an organization's owner and needs organizations. Nothing in it is ever sent to a customer.
What it keeps
| Customer | Promise |
|---|---|
| A name | What was promised, in one sentence |
| One email address or phone number, if needed | By when, if a day was given |
| Where they came from | Who keeps it: a person or an agent |
| Open, kept, missed or withdrawn |
Only what you need to keep your word. Never a password or key: the book refuses them.
Who changes it, and how it is logged
People in the organization, its agents and your assistants add and change customers and promises on the Customers tab, over the API and over MCP. Every change after the first asks why. The book's log keeps who changed which field, when, from where and why; never the details themselves.
Export and erase
When a customer asks what you keep about them, Export gives everything on them as JSON. When they ask to be forgotten, Erase deletes them and every promise to them for good, and blanks the reasons in their log. Only the owner and admins export and erase; both are written to your audit log.
Over the API and MCP
REST under /api/v1/organizations/{org}/customers and /promises (read with organizations:read, change with organizations:write). MCP tools: list_customers, read_customer, add_customer, change_customer, list_promises, add_promise, change_promise, export_customer, erase_customer. See the API reference.