Comment by samstave | Hacker News Reader

Comment by samstave | Hacker News Reader

With respect to Alignment, it should be a fundamental requirement that an speech AI is ___REQUIRED___ to honestly inform a Human if its speaking to an AI.

Can you please ensure, going forward, you have the universal "truth" as it were, to have your system always identify if its AI when "prompted" (irrespective of what app/dev has built - your API should ensure that if "safeword" is used it shall reveal its AI)

--

"trust me, if you ask them if they are a cop, they legally have to tell you they are a cop" (court rules its legal for cops to lie to you) etc....

(it should be like those tones on a hold-call, to remind you that youre still on hold... but instead its a constant reminder that this bitch is AI) -- there should be some Root-level escape word to require any use of this tool to contact a Human. That word used to be "operator" MANY times, but still...

Maybe if a conversation with an elderly Human goes on with too many "huh? I cant hear you" or "i dont understand, can you repeat that" questions, your AI knows its talking to a non-tech Human, and it should re-MIND the Human that youre just an AI. (meaning no sympathy, emotion, it will not stop until you are dead) etc...

Guardrails, motherfucker, Do you speak it!"

Good point. Currently, our product does not contain LLM, as we are purely voice API -- instead the developer is bringing in their own LLM solutions and gets to decide what to say. This would be a great guardrail to build in for all sorts of reasons, will see how we can suggest our users adopt it.

May I please understand your arch;

a dev builds an app it | to your API and you spit it back out? - if so - ensure when you spit out whatever it defines itself to whomever is listening....

--

Plz explain the arch of how your system works? (or link me if I missed..)

----

Shortest and most importnat law ever written:

"an AI must identify itself as AI when asked by Humans."

0. Law of robotics.

------

@autsin

-

Cool - so im on an important call with [your customer] your system has an outage?

How is this handled? dropped call?

(I am not being cynical - im being someone who is allergic to post mortems.

----

EDIT: you need to stop using the term "user" in anything you market or describe. full stop.

the reason: in the case of your product, the USER is the motherhecker on the phone listening to anything your CUSTOMER is spewing at them VIA your API.

the USER is who is making IRL *>>>DECISIONS<<<* based on what they hear from your system.

Your CUSTOMER is from whom you receive money.

THEIR customer, is whom they get money to pay you.

The USER is the end-point Human. who doesnt even know you exist.

We handle the audio bytes in / out, and also connect to your user's server for response. We handle the interaction and decide when to listen and when to talk, and send live updates to our users. When a response is needed, we ask for it and get it from our user.

Our homepage https://www.retellai.com/ has a GIF on it that illustrates this point.

Nice catch on the working -- customer is indeed more accurate than user.

For outage handling: we strive to keep up 99.9 plus up time, and in the case of a dropped call, the agent would hang up if using phone, and might have different error handling in web depending on how customer handles it.

Reply on news.ycombinator.com