Q: We currently use Missive, and we're considering DB as an alternative.
I have a few questions though:
1. Do you have 1:1 and group internal chat rooms for private conversations between team members?
2. Can the admin manage each user's account for items like signatures, sending names and email addresses, job titles, etc...? Ideally, the admin should be able to configure this and it would be readonly for users.
3. Do you plan to support ChatGPT bots in your web messenger? Ideally, the bot would scrape the website and allow you to manually upload content for it to ingest. Then, it would function as an actual team member within DB. So when the bot is chatting with a customer, other team members would be able to view the conversation in real-time and take over if necessary. Also, if the customer asks for a representative, it would notify team members to take over.
5. I know that currently, you don't support Twilio for SMS, but I'm wondering if you plan to support it in the future. I'm not willing to port my numbers from Twilio.
6. Is the inbox universal in the sense that all messages including email, SMS, webchat, etc... flow into the same inbox? Do you support custom message sources via an API?
Edwin_
May 14, 2024A: Hi! I'm going to try to answer all your questions below:
1. We don't have an internal chat feature, however, you can @mention teammates inside email threads or SMS conversations with customers to collaborate. You can also assign/reassign those conversations as needed. I'll be happy to add this to our backlog and get back to you on timelines.
2. Admins have control over feature usage and visibility permissions at a granular level, however, your teammates are the only ones who can edit their profiles with job titles, signatures, etc.
3. ChatGPT/AI integration is in our roadmap for Q1 2024. You have lots of great ideas that I'll definitely pass along to the Engineering team for consideration.
4. I'll check with the Engineering team to see if this is something we can support. Is pricing the reason why you don't want to port?
5. Our inbox is designed as a timeline of customer/prospect interactions across channels (email, SMS, chat, calls); every touch point with a specific contact will sit in their timeline. We don't have support custom message sources via an API at this time.