Relay V0'

[mrpaulmason]

following the prerequisite steps in #46, here's what I'm thinking:

• "single threaded" - use a different SMS number for each convo (up to a practical max like 20) and recycle numbers when conversations are ended. Moreover, a SURL can only have 1 invitee phone number assigned at a time, and paired with Paul's number (until we have other inviters). --This avoids Paul mixing multiple conversations in a single thread, which real users will never tolerate anyway. -- based on effort / cost, 10-20 SMS numbers to buy/assign on Twilio -- recycle SMS numbers when a connection is ghosted by either side -- Save all phone numbers for private beta invites / feedback testing

• vCards sent to Paul (the sole inviter) and invitees with the following fields -- first name: 'Meetable A' & for each additional vCard sent to Paul ONLY "Meetable B" etc -- last name: blank -- company: Meetable -- photo/image: white bubble w/ blue bg sent with Meetable A. additional colors and bg-less versions used for additional vCards sent to Paul -- phone number: the meetable number its being sent from -- phone number label: SMS (but if this requires custom work, then 'work') -- email: more@meetable.ai (confirm this addy with Paul) -- URL: http://meetable.ai

Message prefixes

Sent message prefix	Used for...	Received message prefix
none, not applicable	message from bot	🤖: (with a space after colon)
(blank)	response to bot	none n/a, messages received by bot are not displayed
' apostrophe or `back tick or ʹ prime or , comma (for Android)	relay text/mms* between users	[Sender's nickname]: ' or [Paul]: ' (note space between colon and apostrophe)
/ forward slash	relay text/mms* for Paul posing as bot^	🤖: Here's a cal invite http://ical.com/34343 (note space after colon)

Notes: -- All invitee relay messages will begin with [Paul]: because they can't set a nickname in V0' -- If API can't compute 'response to bot' message, auto reply with 🤖: not sure what that means, sorry. if you're texting Paul, start message with ' (apostrophe) or try me again! ^ allows us to test V0.0 features (ie Cal invites, reminders) before building *we can live without MMS for V0'

Table of messages sent/received

Messages received by PAUL	Messages received by INVITEE
1.) 🤖: Sally from Tinder visited SURL
2.) 🤖: Sally from Tinder submitted number
3.)	🤖: Welcome message - tbd
4.)	vCard
5.)	🤖: text to explaining to invitee how relay works

6.) 🤖: Sally from Tinder received welcome msgs 7.) | [Paul]: 'Hi [shortname] (sent 30 sec later by bot) shortname is first word of nickname 8.) 🤖: Hi msg sent

[mrpaulmason]

I cleaned up the above and added the 'Paul as bot' feature (to the Prefix table) that we've discussed. Let me know if it impacts the 2 week timeline or, of course, if there's an easier/better way to do it

Notes: ... ^ allows us to test V0.0 features (ie Cal invites, reminders) before building *we can live without MMS for V0'

[mrpaulmason]

summary of important changes made to ticket description: no more apostrophe! all messages except for those entirely in ALL CAPS will be relayed. -- there won't be texting to the bot for a long time, only CONFIRM, etc realized gap ALL invitee msgs need to go to Paul, not just the relay ones ie ALL CAPS ones (now with shell emoji) removed 🤖from user messages now only for bot updates to Paul removed colon from prefix syntax

[danieltynerbryan]

@mrpaulmason where does the shell emoji come in? I'm trying to work off the "Table of messages sent/received" list you put up but it now seems we've deviated from that. Any chance we can update that table with the list of messages to send/receive?

[mrpaulmason]

To review the ticket change lost by github:

1. messages sent by invitees written entirely in ALL CAPS should look like this to Paul: 🐚CONFIRM YOU IDIOT BOT

2. all other messages sent by invitees include no prefix

3. messages sent by Paul starting with / (forward slash) should appear like this to invitees: 🤖Here's an invite for drinks with Paul http://......

4. all other messages sent by paul include no prefix

[danieltynerbryan]

All caps messages coming from an invitee will now arrive to Paul prepended by the shell emoji rather than [User Name]. In addition, to initiate a new meeting messages must be prepended by "/". All other conventions remain the same. For example:

"/ Sally from Meetable. 6pm on Thursday b"