Parameters combine with
&, as in any URL: ?features=all&pii=full. If you add
one, keep the ones you already had — it is the most common mistake when
reconnecting.?features= — which tool groups travel
Without this parameter four groups travel: core, manual, catalog and
conversations. Everything else is opt-in.
A
_write group always drags its read group along: ?features=catalog_write
also brings catalog, because to rewrite a whole row you have to be able to
read it first.
?features=all turns on everything, including the groups we publish later
on. It is the URL you do not have to touch again, and the one we give in the
quickstarts. In exchange, it also connects the destructive writes: if your
assistant is only going to read, do not use it.
?read_only=true — the handbrake
Disables every write and overrides any other option, all included. Useful
for letting someone look without being able to touch.
?pii=full — full phone numbers
By default your end customers’ phone number arrives masked (51•••••4321).
With pii=full it arrives whole. The tools that operate on an existing chat
address it by the conversation, so masking does not close off those operations:
it is only what your assistant gets to read. The only one that asks for a
number is simulate_new_chat (the testing group), and there you type it
yourself. The other dent is one of convenience — customer search accepts a
phone number, and masked it cannot be chained. The details and the why, in
Security.
?agent=<uuid> — pinning an agent
If you have several sales agents, almost every tool asks which one you mean.
This parameter leaves it pinned for the whole connection, and your assistant
stops having to ask you.
list_agents gives you the identifier. It has to be the complete UUID: if it is
written wrong, it is ignored without warning and you go back to the normal
behavior (your assistant will ask you which agent).