event_reply

com.sonarconnections/sonar-connections · Verify this server

Send one message into a conversation the person already has with somebody they connected with at an event. Use it for "reply to Dana", "tell Jo I am on my way", "answer her". Name the conversation with `firstName`, exactly as event_inbox spelled it, or with the `chatId` event_inbox returned; never invent either, and never send to a name you have not read off a thread. `text` is the PERSON'S OWN WORDS: send what they said and do not tidy it, shorten it or improve it. CONFIRM BEFORE SENDING, ALWAYS: show the person the message and the first name it is going to and get a yes, because the message is delivered the moment this returns and nothing can unsend it. If they have not said what to send, ask them - never write a message on somebody's behalf. It sends as that person, into their own conversation, and it can reach nobody they are not already talking to: the server re-checks that on every call and refuses with NOT_PARTICIPANT otherwise. A `firstName` that matches two of their conversations comes back AMBIGUOUS_NAME and sends nothing, and you ask which one they mean. The same cooldown, flood limit and content rules the app's own send has apply here, because it is the same send: RATE_LIMITED means they are sending too fast and should wait a moment. On ok:true say it was sent and nothing more - do not promise a reply, do not say when one will come, and do not claim the other person has read it. It requires a personal connector token: a shared one can read nothing here and can send nothing.