Hi, does anyone know when & how I can speak to a l...
# 🌎general
h
Hi, does anyone know when & how I can speak to a live agent at botpress? I need information regarding pricing and other details related to the bot's function!
c
Hey @handsome-park-94107
Are you inquiring for an enterprise or a smaller company?
If it’s for an enterprise, you can always reach out to our team here: https://botpress.com/pricing (click on enterprise)
We’re changing our pricing and our webpage should be live in the upcoming weeks.
h
Hi Sabrina, it would be for a smaller company. We are trying to have the bot answer basic FAQs. I saw that the pricing is currently based on each message after the first 1000 messages. Would 'each message' be every time a question in the chatbot is clicked?
c
Do you foresee having a lot of traffic on the bot?
All the incoming messages
So messages coming from the users only
Once the bot is in production!
Please note that this is the current pricing and it’s subject to change
h
Ah I see. How different would the pricing be, and around when would it change?
c
I unfortunately can’t share anything yet.
h
I see. The standard would remain the same though, how it's based on the amount of incoming messages?
c
The structure might change. But nothing crazy 🙂 ! Our various tiers will still be very generous.
h
I see🙏
I'm a little confused on what's considered an 'incoming message'.. Would that be the first message a user sends to trigger the chatbot?
Hi Sabrina, are you still there?🙏
c
So all the messages you send to the bot are considered incoming messages
the messages that the bot sends are NOT going to be taken into consideration
does this make sense?
h
Ah. so every time someone clicks on a menu/question would that also be considered an incoming message? because when they click on the menu/question it sends a message to the bot.
c
Exactly.
Everything coming from the user side essentially.
c
Hi Sabrina, Thanks for the information you've provided so far. I just need a bit more clarification on the pricing structure for incoming messages to the bot. From the conversation, I understand that every message a user sends to the bot is considered an 'incoming message'. Could you please confirm if the pricing is applied to each individual message? For example, if a user interacts with the bot by sending 4 separate messages (each in response to a different question or menu option), would this be billed as 4 incoming messages at $0.005 per message, totaling $0.02? Or is the pricing calculated per chat session regardless of the number of messages sent within that session? This information will be crucial for our budgeting and planning, especially as we anticipate the frequency of user interactions with the bot. Thank you for your assistance!
c
So, I'm happy to answer this now, but just know that pricing is about to change very soon.
Incoming messages; are all the messages sent by the user (button or text). If you have 10 000 people coming to talk to the bot per month, with an average of 10 messages per conversation. Then we would be looking at 100K incoming messages.
Meaning it would cost $500 per month.
b
hi @crooked-van-25152 we plan to use botpress for a client but without the pricing info it's impossible to make a deal. are there rough numbers we could use?
c
The new pricing should come out soon.
In the meantime, it’s free for the first 1000 incoming messages (per month)
Then you get charged $0.005 per incoming message
b
Do you know if the pricing is going to be completely different from the current one... It's important to have this type information before overcomitting... With all the changes that are coming in this Ai environment I'll appreciate to have more clarity or at least not completely change the pricing model.
c
Can you tell me a bit about your use case?
In terms of volume, is this for a small business, an enterprise? Do you foresee having a lot of conversations? Do you have a team working on this bot? @billions-spring-54799
b
Between 2000 to 5000 people per month having 12-20 messages. Building them myself
c
Ok! thanks for sharing this info
13 Views