Can separate users be defined for each chatbot? If a user logs into their account, can they see only the conversation history associated with their chatbot?
For example, if Tier 3 offers 15 chatbots, is it possible for each of the 15 users to have exclusive access to their own chatbot, see only their own conversations, and manage what information their chatbot learns?
All our plans/tiers require you to bring your own API key. The message limits still apply even when you bring your own API key. The reason for this is to allow fair usage of our platform. When your visitors interact with your chatbots, our platform is in between consuming storage, bandwidth and compute.
We're working on to enable email notifications, so that will come for sure. The second question is something we had not thought about. I think you are asking if each chatbot could have a certain email address that receives the conversation history.
We can think about this, perhaps it is too much in any way to send all conversation history by email. Imagine if your chatbot had 100...
The idea is that you mentioned you won't be offering a whitelabel dashboard anytime soon where my clients can check their conversation history. So, this daily email with all conversations could be a compromise solution, allowing each client to receive their history. However, it will be necessary for each chatbot to send the email to a separate address.
Ah understood. I think we should disambiguate these two things; White label dashboard does not mean your users cannot access it, we'll be offering Team features, so you can grant them access and they will only see the bots that you allow them to see.
On the other hand, a daily email will still include the Tiny Talk brand, even if it's subtle, and the sending email domain will be "tinytalk.ai".
Just to manage the expectations, it is not feasible to send chat history of each conversation every day by email. We're talking about thousands of conversations to hundreds of people every day. Please feel free to reach out at support@tinytalk.ai we'd be happy to continue our conversation over email.
Q: Slack Integration
Hey there! I see Appsumo says you have Slack integration, but your site says its coming. https://tinytalk.ai/docs/embed-and-integrate So which is it? Thanks
It is sort of both :) A native Slack integration is indeed in an upcoming state, but using Zapier you can already integrate with Slack in a certain ways.
Are you strictly looking for a native Slack integration? If you can, let us know your use cases and we'd be more than happy to consider them.
Hope this helps and let me know if I can help further.
My freelancers are on slack and I'd like to have my knowledgebase be able to be called through a slack channel. Every question that can be answered in our chat automatically would save so much time. It's really a no brainer
Q: Limit interactions to a specific website?
Can I limit interactions to a specific website to reduce token consumption on my OpenAI API key?
You can define domains where your chatbot should receive traffic from. For instance if the concern is that somebody will embed your chatbot into their website and send you unwanted traffic, this option can be helpful. You basically allowlist your own domain. Though there are ways around this to still send requests from a non-browser environment, it is not...
We're soon introducing a long awaited set of features like custom fields/forms, chat history retention on user side and widget/messenger updates and a few more things. After that we'll be working on already committed features like custom domains and team features.
But I think we could introduce rate limiting towards end of March or April for sure.
Q: Separate users be defined for each chatbot?
Can separate users be defined for each chatbot? If a user logs into their account, can they see only the conversation history associated with their chatbot?
For example, if Tier 3 offers 15 chatbots, is it possible for each of the 15 users to have exclusive access to their own chatbot, see only their own conversations, and manage what information their chatbot learns?
Share Tiny Talk
Q: about GPT 3.5 and GPT 4 (Bring your own key)
i need Bring my own key to use 30,000 messages per month or appsumo plan included those 30,000 messages per month?
bests
tinytalk
Feb 14, 2025A: Hello! 👋
Thank you for reaching out.
All our plans/tiers require you to bring your own API key. The message limits still apply even when you bring your own API key. The reason for this is to allow fair usage of our platform. When your visitors interact with your chatbots, our platform is in between consuming storage, bandwidth and compute.
Hope this helps, let me know if I can answer...
Share Tiny Talk
Q: Daily email with conversations ?
Is it possible to send a daily email with the conversation history?
And can this email be sent to a different address for each webpage?
tinytalk
Edited Feb 13, 2025A: Hey Nicolae,
We're working on to enable email notifications, so that will come for sure.
The second question is something we had not thought about. I think you are asking if each chatbot could have a certain email address that receives the conversation history.
We can think about this, perhaps it is too much in any way to send all conversation history by email. Imagine if your chatbot had 100...
Share Tiny Talk
The idea is that you mentioned you won't be offering a whitelabel dashboard anytime soon where my clients can check their conversation history.
So, this daily email with all conversations could be a compromise solution, allowing each client to receive their history. However, it will be necessary for each chatbot to send the email to a separate address.
Ah understood. I think we should disambiguate these two things;
White label dashboard does not mean your users cannot access it, we'll be offering Team features, so you can grant them access and they will only see the bots that you allow them to see.
On the other hand, a daily email will still include the Tiny Talk brand, even if it's subtle, and the sending email domain will be "tinytalk.ai".
Just to manage the expectations, it is not feasible to send chat history of each conversation every day by email. We're talking about thousands of conversations to hundreds of people every day. Please feel free to reach out at support@tinytalk.ai we'd be happy to continue our conversation over email.
Q: Slack Integration
Hey there! I see Appsumo says you have Slack integration, but your site says its coming.
https://tinytalk.ai/docs/embed-and-integrate
So which is it?
Thanks
tinytalk
Feb 13, 2025A: Hello,
Thank you for reaching out!
It is sort of both :) A native Slack integration is indeed in an upcoming state, but using Zapier you can already integrate with Slack in a certain ways.
Are you strictly looking for a native Slack integration? If you can, let us know your use cases and we'd be more than happy to consider them.
Hope this helps and let me know if I can help further.
All...
Share Tiny Talk
My freelancers are on slack and I'd like to have my knowledgebase be able to be called through a slack channel. Every question that can be answered in our chat automatically would save so much time. It's really a no brainer
Q: Limit interactions to a specific website?
Can I limit interactions to a specific website to reduce token consumption on my OpenAI API key?
tinytalk
Edited Feb 13, 2025A: Hello 👋
Thank you for the question.
You can define domains where your chatbot should receive traffic from. For instance if the concern is that somebody will embed your chatbot into their website and send you unwanted traffic, this option can be helpful. You basically allowlist your own domain. Though there are ways around this to still send requests from a non-browser environment, it is not...
Share Tiny Talk
Thanks for info! When you will introduce this rate limiting/throttling of users on a hourly basis ?
We're soon introducing a long awaited set of features like custom fields/forms, chat history retention on user side and widget/messenger updates and a few more things. After that we'll be working on already committed features like custom domains and team features.
But I think we could introduce rate limiting towards end of March or April for sure.