I'm trying to change the avatar shown on my smooch chat http://docs.smooch.io/ios/#configuring-agent-images
The docs say you simply make a gravatar account.
Is the email you use to sign into smooch to manage settings the same as the app maker's email address?
Is the email you use to sign into smooch to manage settings the same as the app maker's email address?
Not exactly. A team of app makers can reply from a variety of channels such as Slack and Zendesk in which case Smooch collects an email address from any of those those 3rd party account emails.
If the email we resolve matches that of the app maker's Smooch account, then the avatar they have configured in Smooch will be used. If you don't have a custom avatar configured in Smooch, gravatar is used as a fallback.
If however the 3rd party account email does not match the Smooch account, then any gravatar configured for that email will be used.
Note that you can also override the all outgoing messages, under Messaging Options you can set Use app icon and a single team name for all messages.
Related
I integrated my application with the chatbase, but I would like my clients to have direct access to their email directly, as if it were a single step.
When I click a button in my application, it is directed to the logged-in chatbase screen.
Today I can only get it to the login screen, where it is still necessary to put the password to go to the dashboard, not logging directly into the application.
Is this possible? if yes, is there any kind of quickstart?
I followed the tutorial below to get to the login area, remembering that I use node.js
https://scotch.io/tutorials/easy-node-authentication-google
Thank you for your interest in Chatbase. There is currently no support for OAuth logins. Please see our recommended steps for third party integrations below:
Have the user open a Chatbase account with a Google linked email address
Have the user create a Bot in order to obtain the API key
Have the user integrate their analytics on your platform by providing the API key
Send the messages from their bot to their Chatbase API
Provide the user deeplinks to the Chatbase reports from within your UI
I'm writing a Gmail add-on and I need the email address of the user's account.
How can I retrieve it using appsscript?
You can use the Session class:
Session.getActiveUser()
Note that there are some restrictions when the email address will be available, but for your use case - an add-on which likely receives express permission - this should not be an issue.
I have a web application wherein our users create contracts and we have integrated with DocuSign through an embedded recipient experience.
My web application is fairly involved in gathering the appropriate signers, sending emails, requesting signatures, keeping up with signer statuses, etc., and so I believe that an embedded recipient experience makes the most sense for us.
However, our first client using the integration has already been using DocuSign for some time and their signers (CEOs, CFOs and the like) are accustomed to logging into DocuSign, seeing envelopes in their inbox and clicking on them to sign - which is only possible in an integration by adding them as remote recipients. Embedded recipients cannot be associated to a DocuSign user account.
I'd like to keep using embedded recipients, but my client desperately wants to see envelopes created from my application in their DocuSign user account inbox and sign them from there without first having to log into my application.
Is there any clever way to deliver such a request with an embedded recipient experience? Even an atypical workaround, like sharing documents between the embedded recipient and the user account or some other recipient type of which I'm not aware, etc.?
Unfortunately not. When creating an embedded signing session the recipient becomes what's referred to as a Captive Recipient. Captive Recipients follow a different set of rules in regards to email notifications and presence in an inbox.
For example, Captive Recipients don't receive email notifications by default -- but they can supply an email to be CC'ed onto the envelope.
Since the Captive Recipient also has a universal account number, the user is technically part of an account outside of yours or your recipients.
IE: Your recipient views his inbox linked to his userId on account XXXXXXXXX.
The Captive Recipient is part of account YYYYYYYYYY with its own unique userId, so there's nothing for it to match up to.
If your app relies on embedded signing to load DocuSign envelopes into something like an iFrame, you can still do that without using an embedded recipient, which would give you the ability to load them through your webApp as well as let your signer access them via his DocuSign inbox.
To retrieve the signing URL, you make a POST call to https://{endpoint}.docusign.net/restapi/v2/accounts/{accountId}/envelopes/{envelopeId}/views/recipient with the following call body:
{
"returnUrl": "http://localhost/returnUrl",
"authenticationMethod":"email",
"email": "{recipientEmail}",
"userName": "{recipientFullName}",
"recipientId":"{recipientId}"
}
I'm looking forward to implement chat window for admin where admin can reply to all customers. I am able to integrate chat with slack channel where admin can reply,But I couldn't find any inbuilt tool/plugin(web) available to implement that. Also didn't find any way to create a group chat.
As you probably guessed, Smooch is a platform that hooks up with popular chat systems and CRMs that already exist, such as Slack. However, Smooch itself is not a CRM, there is no Smooch admin chat UI.
It is entirely possible to build your own admin chat UI for Smooch. The first place to start would be our REST API docs.
In fact, the amazing team of developers at Front did this themselves this past February. You can give their Smooch integration a test drive here.
To answer your question about group chats: Smooch's model supports having many agents join the conversation on the business side, but a Smooch conversation is only designed to connect to a single end user identity. Note that an end user may use multiple different devices/clients to connect to a Smooch conversation (eg Facebook, SMS, etc) all end user clients connected to a conversation are considered to be owned by the same end user identity. You can find more info on how this currently works here.
Google have multiple products like Youtube, Gmail, Google Drive and many more. When we login into one product like gmail then while hitting another product like youtube we will enter into this account without login. Then My question is how google uses cookies for different domain like youtube, gmail and any other. If anyone knows about this please let me know thanks in advance
This is not google specific thing. You have to study more about single-sign-on and claims based authentication to understand how this is achieved.
The common protocols used in these scenarios are OAuth and OpenId Connect.
Basically 3 parties involved here. The User, The Application, The IP(Identity Provider).
In this example Gmail, youtube and google drive, all are applications. They all use google(accounts.google.com) as identity provider. When user try to access an Application(gmail,youtube) he is redirected to the identity provider(accounts.google.com) and get authenticated. The identity provider issue a cookie(from accounts.google.com domain) to the user. The application receive Token from Identity provider saying user is authenticated and after validation of the token, application also issue another cookie(from gmail.com or youtube.com) to the user.
As long as user has the cookie issued from identity provider, he don't want to sign in again when he logs into an application that use the same identity provider.