Skip to main content

What Bolt deliberately doesn't do

The boundaries that are design choices — no broadcasts, no payments, no delivery promises, no invented answers.

J
Written by Joe

Some things Bolt won't do, on purpose. They tell you more about the product than any feature list.

Who this is for: anyone who wants the edges stated plainly.

No bulk messages

Bolt won't broadcast to your customer list — there's no bulk-send machinery to misuse. Anything customer-facing (a coupon, a banner) comes to you; you stay the one hitting send.

No payments

Bolt never takes a payment, moves money, or touches checkout. Discount codes with your confirmation are the closest it gets — even that runs through [Money safety by design].

No delivery promises

It reports tracking where it has it and refuses to guess where it doesn't. A made-up "it'll arrive Friday" costs the customer's trust — not allowed.

No invented answers

A question your data doesn't answer gets an honest "I don't have that", not a plausible guess. The fix: [The assistant doesn't know a product or policy].

No pretending to be human

It doesn't pass itself off as a human agent — shoppers deserve to know what they're talking to.

No silent store changes

Nothing changes without a preview and your typed YES — and there's no setting to loosen that.

Limits

These aren't roadmap gaps — they're the shape of the product. If one is a dealbreaker, better to know now.

Still stuck?

The positive version — what Bolt does do — is [Everything you can ask].

Did this answer your question?