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.
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.
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.