event_set_intent

com.sonarconnections/sonar-connections · Verify this server

Set what the person is at an event for, and whether other attendees there may find them. Use it for "set my intent", "I am here to buy", "tell people I am looking for investors", "make me findable". ASK TWO QUESTIONS AND PASS BOTH ANSWERS IN THEIR OWN WORDS: "What are you here for?" is `headline`, and "Who do you want to meet?" is `lookingFor`. THOSE TWO SENTENCES ARE THE BADGE. Together with their name they are the whole of what makes a person findable at this event, and they are what the matcher reads to decide who they are shown to, so ask both, pass both, and do not compress them, tidy them or invent them. `intent` is OPTIONAL and is a quick pick rather than a question you owe: pass one of Buyer, Vendor, Networker or Social only when the person actually said one of those words, and otherwise leave it out, because the server works the category out from what they wrote and falls back to Networker exactly as their badge in the app does. IF THEY NAME A CATEGORY OF THEIR OWN - "investor", "director", anything - pass it as `label` and it is kept as their word rather than refused; never talk them out of it and never map it onto one of the four yourself. `discoverable` is a SEPARATE and REQUIRED answer and is never inferred from the intent: ask the person, because true puts them in the list other attendees can see and false keeps them out of it. TWO CALLS, ALWAYS: call it first with no `confirm` to get back a sentence saying exactly what will change plus a `confirmToken`, show that sentence to the person, then call it again with confirm true and that token. The token lasts two minutes, works once, and stops working if any argument changes. It requires a personal connector token: a shared one can read but cannot change anything. It changes that one person's badge at one event and reaches nobody else's. A badge with one of the two sentences still blank cannot be found by anybody yet, so it is refused naming the sentence that is missing rather than written. CLOUD 181a: `firstName` IS THE THIRD THING THE BADGE IS MADE OF, beside the two sentences above, and it is OPTIONAL in the same way they are. Pass it when the person has just told you their name or asked to change it and leave it out every other time: an omitted name leaves theirs alone and an invented one would rename them. Until this unit there was no door onto that field outside the app, which is why a person who had only ever used an assistant or a browser could not finish a badge however many sentences they wrote. A name the badge cannot take refuses the whole call rather than writing half of it, and the refusal says which thing was wrong with it.