Support

I recreated a bot with the same Slack credentials, and mentions stopped relaying

Short answer: your Slack app still points at the deleted bot's webhook URL. Paste the new bot's URL into the app's Event Subscriptions and re-verify.

Symptoms

• Setup finishes clean: Slack accepts the token, the channel list loads, and the dashboard shows the bot Active.
• No mentions reach your operator channel.
• On the bot's settings page, Last relay activity stays None yet, and the activity log stays empty, with no dropped-message entries.
• Slack may email the app's owner about failed event deliveries.
• The app's pages on Slack may warn that your Request URL is failing.

Cause

• The Bot User OAuth Token and Signing Secret belong to your Slack app and stay valid until you reinstall or regenerate them, so the wizard accepts them.
• The webhook URL is different: BotFerry gives each bot its own, and it dies the moment you delete the bot. A recreated bot gets a fresh URL, never the old one back.
• Your Slack app still has the old URL under Event Subscriptions, so Slack posts every mention to a dead address and BotFerry answers 404.
• Nothing ties those failed posts to the new bot, so its activity log stays empty. After enough failures, Slack pauses event delivery until you re-verify the URL.

Fix

1. Copy the new bot's webhook URL, shown next to the app manifest in the setup wizard. It looks like https://<your BotFerry domain>/webhook/slack/<id>; the same <id> is in the dashboard address bar, for example /bots/<id>/settings.
2. Open api.slack.com/apps, select your app, and go to Event Subscriptions. Check that Enable Events is on.
3. Replace the Request URL with the URL you copied. Slack verifies it and shows a Verified check; click Save Changes.
4. If Slack paused deliveries after the earlier failures, click Retry on the warning banner so it resumes.
5. Mention the bot in a channel it belongs to. It reaches your operator channel within seconds, and the activity log records a relayed mention.

If it still does not work

• Confirm the bot is enabled in BotFerry. A disabled bot drops mentions on purpose and says so in its activity log.
• On a tunnel for testing? Check it is running and its domain matches the URL in Slack. A restarted tunnel often changes domain, which breaks the Request URL the same way a deleted bot does.
• The token and signing secret are rarely the cause: Slack keeps them valid until you reinstall or regenerate them yourself.

Upgrading or downgrading, and how you're billed

Change plans from your billing page while your subscription is active. The switch takes effect immediately and is prorated for the rest of the month.

• Upgrade: we charge the prorated difference to your card, and your larger allowance applies at once. If the card is declined, nothing changes and your plan stays where it was.
• Downgrade: we credit the unused part of your current plan to your next invoice. It lowers what you pay next month rather than paying cash back.

If your subscription is past due or scheduled to cancel, plan changes pause until you fix the payment or resume (see below).

Cancelling, and the 14-day money-back guarantee

Cancel from your billing page at any time. What happens depends on how long you have been subscribed.

• Within 14 days of subscribing: we cancel immediately and refund your most recent payment in full, back to your card through Stripe. This applies once per account and once per card.
• After 14 days: your plan is scheduled to stop at the end of the period you have paid for. You keep full access until that date, we take no further payment, and the current period is not refunded.

Changed your mind after scheduling a cancellation? Open your billing page and press Resume subscription before the period ends to keep your plan running.

Deleting your account does not by itself refund a paid subscription. If you think a refund should apply outside these cases, email us before you cancel or delete.

A renewal payment failed and my bots stopped relaying

Short answer: add a working card on your billing page. Stripe collects the overdue payment and your bots relay again on their own.

Symptoms

• Your bots stop relaying and new messages are dropped.
• The dashboard and the billing page both show that your last payment did not go through.
• You get an email about it.

Fix

1. Open your billing page and press Update payment method. This opens Stripe's secure portal, where you add or replace your card.
2. With a working card on file, Stripe collects the outstanding payment, usually within minutes, and keeps retrying on its own.
3. When the payment clears, your subscription returns to active, your bots relay again, and we email you to confirm.

If it stays unpaid

• After Stripe's retries, the subscription is cancelled. Re-subscribe any time by signing in and choosing a plan; your account and settings are kept.