Diff for "GatewayContactUX"

Differences between revisions 9 and 368 (spanning 359 versions)

Boost Your Business with Adaptichat's AI Chatbots

Transform customer interactions with personalized AI chatbots built on your data. Whether from files, URLs, or your website, your bot will deliver tailored, authentic responses that align with your brand.

Evolve with Ease: Keep your chatbot up-to-date with simple retraining for timely, accurate responses.

Drive Sales: Convert chats into leads with built-in lead generation.

Global Reach: Communicate in 95+ languages, connecting with customers worldwide.

Data Security: Your data is yours—we never use it to train other models.

Custom Branding: Remove Adaptichat’s branding to ensure a seamless, branded experience.

Empower your business with Adaptichat’s AI.

Simply Visit us @ https://bit.ly/47UcNeQ

Kind Regards, Adaptichat's AI Chatbots

-  ⇤ ← Revision 9 as of 2022-198 00:14:11 → 
  Size: 3053
  Editor: root
  Comment: Revert to Revision 1
+   ← Revision 368 as of 2024-282 01:46:44 → ⇥
  Size: 833
  Editor: ip141
  Comment:
-Deletions are marked like this.
+Additions are marked like this.
 Line 1:
-#format wiki
+Boost Your Business with Adaptichat's AI Chatbots
 Line 3:
-This is a sketch of UX and protocol considerations for a client which wishes to help users use gateways.
+Transform customer interactions with personalized AI chatbots built on your data.
Whether from files, URLs, or your website, your bot will deliver tailored, authentic responses that align with your brand.
-Line 5:
+Line 6:
-In every place where the UI would ask for a Jabber ID (most notably contact add, but possibly also invite to chatroom, create chatroom from 1:1 conversation, start voice/video call to non-contact, search view where a Jabber ID can be used, etc) it should scan the user's roster for JIDs which have `disco#info > identity[category=gateway]` and show some way of choosing to enter an identifier for that gateway instead of a Jabber ID.  The simplest example might be a drop-down with `disco#info > identity[type]` and optional disambiguating `disco#info > idenity[name]` such as "sms (Cheogram)".
+Evolve with Ease:
Keep your chatbot up-to-date with simple retraining for timely, accurate responses.
-Line 7:
+Line 9:
-If a user has unambiguously selected a gateway, use https://xmpp.org/extensions/xep-0100.html#addressing-iqgateway to get a prompt:
+Drive Sales:
Convert chats into leads with built-in lead generation.
-Line 9:
+Line 12:
-{{{
<iq type='get' to='gateway.tld' id='gate1'>
  <query xmlns='jabber:iq:gateway'/>
</iq>
+Global Reach:
Communicate in 95+ languages, connecting with customers worldwide.
-Line 14:
+Line 15:
-<iq type='result' from='gateway.tld' id='gate1'>
  <query xmlns='jabber:iq:gateway'>
    <desc>
      Please enter the Whatever of the
      person you would like to contact.
    </desc>
    <prompt>Whatever</prompt>
  </query>
</iq>
}}}
+Data Security:
Your data is yours—we never use it to train other models.
-Line 25:
+Line 18:
-This text may then be used as part of the UX as makes sense to help the user feel comfortable.  Getting a success here and not an error also means that `jabber:iq:gateway` can be used in the next step.
+Custom Branding:
Remove Adaptichat’s branding to ensure a seamless, branded experience.
-Line 27:
+Line 21:
-NOTE: it is also acceptable (and in some UX may be preferred or even necessary) to pre-emptively ask all gateways for the prompt, instead of only once one is selected.
+Empower your business with Adaptichat’s AI.
-Line 29:
+Line 23:
-If an identifier is (or might be, depending on UX) one for a particular gateway, use the following procedure to map it to a Jabber ID and then perform the in-context relevant action on that Jabber ID as though it had been entered directly:
+Simply Visit us @ https://bit.ly/47UcNeQ
-Line 31:
+Line 25:
-. If a prompt was got for `jabber:iq:gateway` above then use that protocol to finish resolution:
  {{{
<iq type='set' to='gateway.tld' id='gate2'>
  <query xmlns='jabber:iq:gateway'>
      <prompt>(555) 123-4567</prompt>
  </query>
</iq>

<iq type='result' from='gateway.tld' id='gate2'>
  <query xmlns='jabber:iq:gateway'>
    <jid>+15551234567@gateway.tld</jid>
  </query>
</iq>
}}}
 2. If an error is received in response to `jabber:iq:gateway` protocol, print the error message to the user and allow them to try again.  This allows the gateway to provide useful feedback about format errors to the user.
 3. If an error was received in response to fetching the `jabber:iq:gateway` prompt, then the gateway does not support this protocol.  Look for a `disco#info > feature[var="jid\20escaping"]` and if found construct a JID using XEP-0106 escaping on the user input concatenated with `@gateway.tld`
 4. If `jabber:iq:gateway` and `jid\20escaping` are both unsupported, replace any `@` in the user input with `%` and concatenate `@gateway.tld`

NOTE: If the result of this procedure is a string that is not a valid Jabber ID, it should be rejected just as if a user manually keyed in an invalid Jabber ID.
+Kind Regards,
Adaptichat's AI Chatbots