Document details

Document details live in Settings → Project & access, and in the settings side menu the section is called Legal details. Only the project owner and admins can open it. The details serve one document — the PDF statement of a conversation, downloaded for a payment dispute (chargeback), a claim or an audit: its header shows who issued it.

Fields

• Every field is optional: an empty one is left out of the statement. With nothing filled in, the left of the header keeps only the project's logo and name, and the right shows the statement number and issue date as always.
• Save in the bar at the bottom of the page applies the changes, and Discard brings back what was saved. Spaces around the values are trimmed on save, and a field won't take more than its limit. An email is saved only if it looks like an address: a name, an @ and a domain with a dot, such as support@example.com. If the server refuses a value — say, the email address isn't valid — a notification and a line under that very field say so. The field is highlighted and gets the focus, and the first edit in it clears the mark.

How the details look in a statement

The statement header is built from two places. On the left are the project's logo and name from the published version of the widget builder (the Brand section, the Logo and Project name fields). Without a name of its own there, the project's name in the dashboard is printed. Builder edits not yet published with Publish don't reach the statement. Under the name come the details, in three lines:

• The legal name and the registration number, separated by a comma.
• The registered address, on the same lines as in the field: every line break in the field is printed as a line break in the header too.
• The website and the contact email, separated by a comma.

On the right are the statement number and issue date. The line under the header is in the brand's accent colour. A colour too light for a white page is replaced with the default one. The legal name also goes into the PDF file's properties as the document's author — without it, the project name does.

When changes reach the statements

The details are written into a statement when it is issued and are part of its content: they are in the statement.json attached to the PDF and covered by the SHA-256 checksum (how it's checked is in Data export). So statements already issued don't change: new details appear in the next one.

Names in links and statements

The second block of the page is what's ticked by default when a conversation link or a PDF statement is issued: Hide the customer's name and contacts and Hide operators' names. In the issue window the boxes can be changed for one link or statement, and this block sets where they start. It's saved with the details by the same Save button. How links and statements are issued is in Data export.

• A hidden customer reads “Customer” in the messages. In a statement the header keeps only the customer's ID in the system instead of their name, email, phone and messengers, and the statement's verification page says “withheld in the statement”.
• Hidden agents read “Agent” everywhere, even where the project shows names to customers in the chat.
• Names inside the messages don't change: what was written stays.

Where these details aren't used

• The details from this section aren't put into emails to customers. For emails, the company details go into Footer text in the email templates.
• The details for Dedicated license invoices aren't these: they are filled in separately, in the Invoice details block on the license page, in the Renewal and purchases section. The block shows up once Invoice to a company is picked as the payment method.