Stripe payments, Slack cards and a real live chat

A Meerlume bot can now charge a customer mid-conversation through your own Stripe account. Connect it under Integrations with a restricted key you create in Stripe, add a Take a payment step to the flow, and your message arrives with a Pay button showing the amount, on Telegram, WhatsApp, Messenger, Instagram and website chat alike. Tapping it opens Stripe Checkout with your business name on it, and the money goes to your Stripe balance directly: Meerlume never holds it and takes no cut.

The bot waits for the payment before it carries on, so a deposit can hold a slot, and a link that expires unpaid takes the failure branch you chose. Tell the builder your prices and it charges whatever the customer picked, or a share of it as a deposit. Payments are on Growth and above.

The Meerlume dashboard Overview gains a Taken this month tile once Stripe is connected: what customers paid through your bots, minus refunds, with each currency kept separate and money still settling shown beside the total. The Stripe page under Integrations lists every payment with the customer, the bot and the conversation, and each paid one opens in Stripe.

Payments also show in the inbox transcript beside the messages, paid, refunded, failed or expired, and the CSV export gains the amount, currency, status and Stripe payment ID for each conversation. You hear about a payment the way you hear about a submission, on the bell plus email, Telegram or WhatsApp where you have turned them on, and a payment that completes a booking arrives as one notice rather than two.

Meerlume now posts to a Slack channel of your choice each time a customer finishes a conversation or changes a booking: the answers, the contact, the booking, and an Open in Meerlume button into the inbox. Open Integrations, press Add to Slack and pick the channel in Slack's own picker. There is nothing to build and no URL to paste, and the app asks for one permission only, posting to that channel.

Connect as many channels as your team needs, narrow each one to the bots it should hear about, and send a test card before a real customer does. Slack is on Growth and above and does not use up the webhook endpoints your plan includes.

When a customer writes something like "can I talk to a human", in the bot's language or in English, a Meerlume bot now pauses, tells them you have been asked for, and notifies you. The same happens after three answers in a row the flow could not accept, so a customer stuck on a question is not left arguing with a bot, and outside your business hours the message says when you are back.

The phrases that trigger it are editable per bot under Wording in the builder. If nobody has replied after ten minutes the customer is told you are still coming, and a conversation left alone for two hours is handed back to the bot on its own; both timers are yours to change under Customer messages.

Taking over a conversation in the Meerlume inbox now reads like a chat: your side on the right, the customer on the left, day markers between days, and a marker in the transcript for every takeover, escalation and hand back. While you type, the customer sees a typing indicator on their channel, and on WhatsApp the composer counts down the 24-hour reply window and locks when it closes.

You can leave an internal note the customer never sees, insert a saved reply or save the one you just wrote, and press Draft with AI to start from a reply drafted from the transcript. Hand back is now a choice: resume the flow where the bot left off, start it over, or close the conversation.