Overview

Export CSV Export PDF

Time	Partner	Outcome	Reason	Duration	Messages	Entry point	Source

Partner	Source	Status	Chats (30d)	Succeeded	Failed ⓘ

What the language model actually cost — translation, the checks around it, and the intake analysis. For insight only; nothing is billed on automatically.

Partner	Chats	Analysis	Translation	Back-translation	Quality check	Partner texts	Total	Per chat

Chats

No database has been configured yet. Set DATABASE_URL (locally) or PGHOST and PGUSER (Azure) and restart.

Tenant management

Every licensee on the platform. Click a row to start working in that environment.

Tenant	Slug	Label	Partners	Geld & mail	Created	Active

Usage per month

The details of the tenant you are working in.

Slug —

Name

Word for an outlet Empty = “Partner”. Plural different? Write it as Clinic/Clinics.

Records For a chain: choose “per tenant” and the veterinarian also sees the same customer’s earlier chats and pets at another outlet. A change applies from now on — existing records are not merged.

Veterinarians may see each other’s chats

Adds a “With colleagues” view to the inbox in VETTS for Vets, showing what other veterinarians in this tenant have picked up. Read-only — nobody can take over someone else’s chat from there. Off = every veterinarian only sees the inbox and their own chats.

Veterinarians may see the pet parent’s phone and e-mail

Off = the Dossier in VETTS for Vets shows no phone number and no e-mail address for the pet parent. The veterinarian keeps answering in the chat; the customer is still notified by SMS or e-mail as before. On = whoever picked up the chat can see and call them.

Veterinarians may transfer a chat to a specific colleague

Off = a veterinarian can only hand a chat back to the inbox, not to a named colleague. On = the usual "Hand over" menu with colleagues by name.

Provider

Who delivers the service: the brand shown next to an outlet’s name on the chat pages. Every field empty = the platform default — the grey text in the field shows what you get. Addresses must start with https:// (see below).

Provider name

Logo URL Favicon URL

“Powered by” text “Powered by” link

Support contact

Terms and conditions Privacy policy

Veterinarians on the page

The faces behind “who answers your question”. The page shows four. The one-liner appears when a visitor taps a face — leave it empty and the card shows just the name, the role and the photo.

Vet 1 — name Vet 1 — photo URL

Vet 1 — one line about them

Vet 2 — name Vet 2 — photo URL

Vet 2 — one line about them

Vet 3 — name Vet 3 — photo URL

Vet 3 — one line about them

Vet 4 — name Vet 4 — photo URL

Vet 4 — one line about them Photo on the widget button

Name in the conversation portal Role in the conversation portal

Avatar in the conversation portal

Colours and appearance

This tenant’s default colours. An outlet that sets its own colours overrides these — what you fill in here only applies to outlets that chose nothing themselves. Empty = the platform colours.

Primary colour

Accent colour (app)

Accent colour (hero)

Background colour

Text colour

Notation: #rrggbb or #rgb. Anything else is ignored and falls back to the default — the dot on the left shows which colour you get.

Texts

The default texts on this tenant’s chat pages. These are defaults too: an outlet with its own title or its own steps keeps them.

Hero title

Hero subtitle The default title puts one word in the accent colour and the subtitle two words in bold. To keep that, you may use simple markup here (<strong>, <em>); everything else is filtered out.

Hero image

Button text Tagline

Label for the response time

Statistics

Stat 1 — value Stat 1 — label

Stat 2 — value Stat 2 — label

Stat 3 — value Stat 3 — label

Label for the figure, narrow widget

How it works

Heading above the steps

Step 1 — title Step 1 — description

Step 2 — title Step 2 — description

Step 3 — title Step 3 — description

Frequently asked questions

The questions at the bottom of the web portal and on the widget’s intro screen. All empty = the four default questions. Fill in one and your list replaces the whole default list — a question only counts if it has an answer with it.

Question 1 Answer 1 Question 2 Answer 2 Question 3 Answer 3 Question 4 Answer 4 Fallback message Button below the questions

Domains

This tenant’s own addresses. Comma-separated; host name only, without https:// and without a path — this screen strips those itself.

Chat hosts The first host is the address in the magic links of the answer mail. Empty = the platform default (PUBLIC_BASE_URL), so today chat.vetts.app.

Hosts for the vet app Empty = this tenant’s veterinarians sign in on the regular VETTS app. Never put a chat host here: on a vet host /conversation/… deliberately returns 404, and then the link in the answer mail is broken.

What to put in DNS. A CNAME per host pointing at the gateway (the gateway), then bind the domain to the app with a certificate. Without that binding a visitor gets a certificate error and not a 404 — so that is not “it doesn’t work yet”, that is “the host isn’t ours yet”.

What happens then. On a host of this tenant, an outlet belonging to another tenant is unreachable (404, so its existence doesn’t leak), and / redirects to the “powered by” link from the Provider block. On chat.vetts.app nothing changes: every outlet stays reachable there.

Payments

Which Stripe account this tenant’s paid consultations arrive in. You don’t enter keys here — those live in the environment’s vault; below only shows under which name.

Payment account “From VETTS” is the default and changes nothing: same keys, same webhook, same invoices.

Not checked yet.

Publishable key Must start with pk_. Never paste an sk_ key here: the screen refuses it, because that one belongs in the vault.

Price id Payment methods id

The price id sets both the amount and the VAT rate of the consultation, and it belongs to this same account: a VETTS price id does not exist in the tenant’s account and the payment fails before the customer ever sees a screen. So create a new product with its own price in that account. The payment methods id (optional) sets which methods the customer sees — empty = whatever is enabled in the Stripe dashboard.

What must be in the vault

Put these two secrets in this environment’s Key Vault. The names are fixed — they follow from the tenant’s slug, so there is nothing to choose and nothing to type.

Secret key stripe-secret--…

Webhook signing secret stripe-webhook--…

Webhook address —

What does NOT happen with an own account. The payment runs through the tenant’s account, but the invoice and the payment mail on the tenant’s behalf don’t exist yet: per-tenant invoicing is a separate track (plan §7 and §13.2), because it touches the “invoice and mail at most once” logic and per-tenant VAT. Concretely: the customer pays and the question goes to the veterinarian as usual, but no invoice and no payment confirmation go out — the tenant sends those from its own Stripe. And the Tractive voucher stays with VETTS: those codes were bought and are not given away on someone else’s payment.

Mail

From which account and under which sender the mail to this tenant’s customers goes out. An outlet can still override the sender and the templates one by one — these are the defaults.

Mail account “From VETTS” is the default and changes nothing about the mail going out today.

Sender name Sender address

The sender address must be verified in the Brevo account in use, and the domain must have DMARC/SPF in order. If not, Brevo refuses the send or the mail lands in spam — and you only notice when a customer can’t find their answer. Hence the test mail below.

Templates

The Brevo template ids this tenant uses by default. Numbers are per account: switch mail accounts and the old numbers are worthless — so this screen clears them when you switch.

Confirmation of receipt Answer mail

The answer mail carries the magic link to the conversation; that link points at the first chat host above. The reminder a day later uses the same template.

SMS

SMS sender 3 to 11 characters, letters and digits. Empty = no SMS. At Brevo, SMS is a separate add-on with its own credit — switch it off and every message fails with “No sms related addons”.

The SMS says that there is an answer and carries the same magic link as the mail. Never any content: a message sits on a lock screen. The confirmation of receipt deliberately does not go by SMS — it only repeats what the widget just showed.

Test mail

Forgot password

New password

Verification code

No access

Overview

Partners

Chats

Veterinarians

Users

Add user

Role and tenants

New tenant

Change password