Skip to content

Security & privacy ​

A contact center puts people and AI on the same customer conversation. These are the rules that keep it safe, and what you need to know when you set it up.

Only the people you list ​

  • Only people on an agent's Operator node are rung for that agent's hand-offs: the web and phone operators on its Team tab. A workspace role doesn't add anyone.
  • Only the supervisors listed on its Supervision tab can listen in, whisper or take over that agent's live conversations, and only with the actions ticked there.
  • The AI never chooses who is dialled. A phone operator's number is fixed on the Operator node or comes from your workflow data; it's never a number the AI picked. During a live call the AI can't start a new outbound call at all; to bring someone in, list them as an operator.

Supervisors must be fully signed in ​

Supervising needs no workspace role, but it does need a full sign-in: the supervisor must be a member of your workspace, and if two-step verification applies to their account they must have completed it in this session. Until they do, Monitor, Whisper, Take over, the Live board and hand-back are refused.

Which numbers can be dialled ​

Every call Perfox places goes through the same check: a phone operator on a hand-off, an operator's Transfer → A phone number, the chat widget's Call me, and outbound AI calls.

  • The number must be in a country your workspace may dial: India (+91) by default.
  • Premium-rate and special-rate numbers are never dialled, such as India's 1860 and 1861 numbers and international premium codes.

A number that fails the check is refused before anything is dialled.

Which number calls go out from ​

Every call Perfox places during a conversation, a phone operator on a hand-off or an operator's Transfer → A phone number, is dialled from the agent's own phone number: the number on its Phone Call trigger, on the connected Plivo account that lists it. An operator's own outbound call goes out from the chosen agent's Phone Call trigger number too. There's no workspace default caller ID. If the agent has no Phone Call trigger number, or no connected Plivo account lists it, nothing is dialled and your admins get a notification naming the problem and the fix (at most once a day for the same cause).

Callers recognised by phone number ​

An inbound phone call is linked to the customer by caller ID. Because a phone number can be faked, the agent gets none of that customer's details (profile, collected details, earlier sign-in, memory or attached files) until the caller proves who they are on this call, for example through your own sign-in or OTP tool. Only a sign-in made during this call counts.

One exception, by design: the greeting says the customer's saved first name ("Hi Ravi, …") when your agent's greeting uses it — the built-in greeting, or a Greeting with a {customer_name} token (see Persona → Greeting). This applies to every inbound phone line, whether the call reaches your Plivo number or arrives over SIP. Nothing else about the customer is shared, and the agent's own view of the conversation still leaves the name out until the caller signs in. The call's transcript shows the greeting exactly as the caller heard it. A pipeline voice agent on a Plivo number speaks its greeting itself, so it does know the first name it just said.

Closed conversations start fresh ​

A conversation can be closed while the customer's window is still open, for example when an operator's wrap-up marks it Resolved or someone resolves it in Cases. If the customer's chat window is still open and they write again, start a voice call or attach a file, Perfox doesn't reopen the closed conversation. The widget starts a new one and sends the message there, so a hand-off still reaches your team. A signed-in customer continues in their own open conversation if they have one. Files already attached to the closed conversation can't move over, so the customer is asked to attach them again.

A conversation the AI ended in the last 15 minutes does reopen, so a quick follow-up keeps its history.

A plain web chat that closed itself after 5 minutes of quiet also continues: nothing is sent to the visitor when it closes, and if the same visitor comes back within 24 hours they carry on in the same chat, with the same history. A conversation closed by a person, such as an operator's status change or wrap-up, never reopens this way.

Secrets stay masked ​

When a customer types or says a secret, such as an OTP, PIN or password, it's masked in the saved transcript once your agent's tool has used it. That holds while an operator has the floor, too.

Operators in your own app ​

An operator who works from your own app (an External ID on the Operator node) signs in with a signature your server makes from your site secret, and it expires within 24 hours. A visitor's widget signature can never act as an operator's. The older non-expiring operator signature still works until 15 January 2027, and stops working for a site as soon as it sends its first expiring one. See Operator SDK.

Your app can sign either an External ID listed on an Operator node, or the email a Studio user signs in with, when an Operator node lists that Studio user as a web operator. In the second case the session is that Studio user: the same availability, rings and calls as when they work in Studio, with no extra External ID row. A Studio user that no Operator node lists is still refused. Only your server holds the site secret that makes the signature.

Every step is on the record ​

Every hand-off, take-over, whisper, transfer and wrap-up is recorded in the conversation's timeline, next to one recording and one transcript of the whole conversation.