What is not here yet

Every product has gaps. Most documentation hides them, or labels the whole product with a word that excuses them. This page does neither. Below is what Peaklight does not do today, stated plainly, with what to do instead.

There are no dates on this page. A date is a promise, and the value of this page is that it does not make promises it cannot keep. When something on this list stops being true, this page changes.

There is no self-serve payment

You cannot pay through the console. There is no checkout, no card on file, and no upgrade button. The billing screen is deliberately read-only: it shows you your plan and what your agent has actually used, and nothing more.

Instead, invoicing is handled directly with you. Your account manager arranges what you are billed and sends the invoice. If you want to change what you are paying for, that is a conversation, not a form.

You will notice the console says this on the billing screen itself rather than showing you a disabled button. That is on purpose. A control that does not work is worse than no control at all.

There is no team management, and one workspace per customer

You cannot add a colleague, create a second workspace, or change who has access. There is no screen for it and no way to request it in the product.

Instead, ask us. Adding a person to your workspace is something we do for you. It is not self-serve today, and if you need several people working in the console you should tell us early rather than discovering the limit on a busy day.

Five screens are visible but not switched on

Your navigation shows five items that you cannot open. They are visibly tagged as not yet available, and they will not respond when you click them:

• Policies: the agent's rules and the decisions it made under them
• Audit log: every consequential action, with the person or agent behind it
• Knowledge: the sources the agent is allowed to draw on
• Agent settings: role, voice, channels, and the actions it is forbidden to take
• Team & access: who can sign in and what they are allowed to do

We show them rather than hiding them because you should be able to see the shape of the product you are buying into, including the parts that are not finished. A hidden feature and an absent feature look identical from the outside, and we would rather you knew which one you were looking at.

Until those screens exist, the things behind them are handled by us directly. Your agent is configured and constrained by us, and changes to that are something you ask us for rather than something you can make yourself yet.

The billing screen leaves things out on purpose

If you look at your usage and expect a row that is not there, that is usually not a bug.

Peaklight only shows a usage meter when there is a real counter behind it. A metric that nothing has measured is left out entirely rather than displayed as zero, because a zero is a claim: it says "we measured this and the answer was none." If we have not measured something, we would rather show you nothing than show you a number we cannot stand behind.

The same rule applies elsewhere in the console. A conversation whose language could not be determined shows no language rather than guessing one. An agent that has never handled a conversation reads "No activity yet" rather than borrowing a date from somewhere else and looking busy.

So an empty row is worth one question to your account manager, not an assumption that the product is broken.

Why we publish this

The console follows one rule about things it cannot do: they are visible and explained, never hidden and never a dead link. This page is that rule applied to the documentation.

If you find something missing that is not on this list, tell us. A gap we have not written down is a gap we have not yet been honest about.