AI agents for e-commerce stores that look up the customer in your connected Shopify, WooCommerce, Wix, Squarespace or Stripe account before writing a word, answer shipping, returns and sizing from your help docs on email, website chat, social DMs and text, hand refunds and order changes to a person, and run reorder campaigns to the customers who bought last season. $25 a month, unlimited agents.
7-day free trial · Cancel anytime
One line of script puts a chat widget on your store in your colour, with your image and a greeting you write. When a visitor asks "does this run small?" or "do you ship to Ireland?", the agent answers from your size guide, your shipping policy and your Q&A pairs, links to the product or the policy page you allowed, and asks for an email address when the conversation is worth keeping.
That address ties the visitor to the rest of their history. When the same person emails a week later about the delivery, the agent already knows what they were looking at, and with the store connected, what they went on to buy.
Connect support@ with an app password for Gmail or Outlook, or as an SMTP and IMAP host for anything else. A customer writes in, the agent reads the connected store to see what they bought, what is still open and what they are worth, and replies from the same address with the order status and the policy that applies. It replies once per thread, ignores bounces and out-of-office replies, and stores every answer with the material it used.
Texts run on your own number through one of nine carriers. A customer who texts "did my parcel ship?" gets the same answer as one who emailed, from the same record.
The DM under the ad is a customer service ticket and a sale at once. Messenger, Instagram, WhatsApp, Telegram, LINE, Viber, Slack, Discord, Bluesky, Reddit and X are each connected with your own app credentials and answered by the same agent, inside each platform's own reply window, from the same knowledge base as the chat and the email.
A DM that asks "is the blue back in stock?" is answered from your Q&A pairs and data points, and the DM that says "my order arrived damaged" is handed to your inbox with the agent standing down, because you wrote that rule.
Every email, chat, DM and text lands in one inbox, newest first, tagged with the channel it came in on. Filter it to a single mailbox when you are working returns, or to a single agent when each brand on your account has its own.
Refunds, order changes, damaged goods and chargebacks are the conversations you name in the instructions, and they arrive with the agent standing down on that thread. Reply yourself, process the refund in the store, and hand the thread back. The agent picks up the next question from that customer where you left it.
Most of what an online store's inbox contains is the same six questions. Where is my order. Can I change the address. What size should I get. How do returns work. Do you ship to my country. Is this back in stock. They arrive by email, in the website chat, as Instagram DMs and as replies to the order text, at eleven at night and on the Saturday of a launch, and each one is answered by a person copying a tracking number out of the store into a reply. AI agents for e-commerce stores exist to answer those six questions from the order itself, in seconds, on whichever channel they arrived on, and to leave the person with the conversations that need one.
Bold Agent Kit is e-commerce support automation in one agent that works email, text messages, website chat and social DMs from a single knowledge base. You give it your material once: your shipping and returns policies, your size guide, your product FAQs as Q&A pairs, your delivery times by region as data points, and the pages of your store it may link to. Then you connect the store, Shopify, WooCommerce, Wix, Squarespace or Stripe, and before the agent replies to anyone it reads what that customer bought, what is still open, and what they are worth. "Where is my order?" is answered with the order. "Can I return this?" is answered with the policy that applies to that item and that date.
It is also the agent that works the campaigns you never get to. Pull a segment of past customers out of the connected store, the people who bought the starter kit ninety days ago, the people who bought last winter and not since, and run a reorder or win-back sequence at them by email and text, in the hours you set, from your own mailbox. Replies are worked by the agent, not left in an inbox. And with the one-line snippet on your store, a known customer who comes back to a product page and leaves can be followed up after a delay, on the channel they last used.
The whole thing is $25 a month, or $200 a year, with unlimited agents, contacts and lists, on your own mailbox, your own carrier account and your own AI key. There is no per-conversation, per-ticket or per-seat charge, and no percentage of the orders it helps sell. A store doing a few hundred orders a month pays a few dollars a month in model usage to answer every one of them.
The customer has already paid, or is about to. Four things get in the way of the answer, and none of them is the customer.
The question arrives at 10pm, and the answer is a tracking number sitting in the store. Nobody copies it into a reply until the next day, and by then the customer has emailed again, DMed on Instagram, and opened a dispute with their card because the parcel was late and nobody said so.
A visitor on the product page asks whether it runs small. The chat is unmanned, the size guide is three clicks away, and the visitor leaves. The answer was in your help docs the whole time; nobody was there to give it at the moment it was worth something.
The support mailbox, the website chat, the Instagram DMs and the order text replies are each watched by a different person, or by nobody. The same customer asks in three of them and gets three answers, or one, or a request to "confirm your order number" in every one.
The customers who bought the ninety-day supply ninety days ago are the cheapest revenue the store has, and the email to them is the job that always loses to the launch. The segment exists in the store. The campaign is never built.
You build the store agent once. From then on it answers on the channels you connect, reads the store before every reply, and only fetches a person for the conversations you named.
Connect Shopify, WooCommerce, Wix, Squarespace or Stripe and the agent looks the customer up before it replies: what they bought, what is still open, what they are worth. "Where is my order?" gets the status of that order. "Can I return the jacket?" gets the policy for that item on that date. It does not guess at an order it cannot see.
Shipping, returns, sizing, stock and product questions are answered from your documents, your Q&A pairs and your data points, with links only to the pages of your store you allowed. Email, website chat, text and eleven social DM platforms get the same answer, because it is the same agent, and every reply is stored with the material it used.
Write the rule in the instructions and a refund request, an address change, a damaged parcel or a chargeback lands in your inbox with the agent standing down on that thread. Process it in the store, reply, and hand the thread back. The agent cannot issue a refund or edit an order, and that is deliberate.
The widget is one line of script on your store, in your colour, with your image and a greeting you write. A visitor asks how much it is, or whether it ships to them, or what size to get, and the agent answers from your material with the link to the product or the policy page, and asks for an email address when the conversation is worth keeping. The visitor's story is drawn across the top of the thread: the pages they read, the questions they asked.
That email address is what turns a visitor into a customer the agent recognises. The cookie, the address and, later, the phone number and the Instagram handle are merged into one contact, so the next time they write in on any channel the agent reads the whole history first, and, with the store connected, the orders behind it.
Each one answers a problem above, and each one runs without anybody remembering to do it.
A "where is my order?" at 10pm is answered at 10pm with the status of that order, on the channel it arrived on. No queue, no "we aim to reply within 48 hours".
The return window, the shipping region and the item are read from the store and the policy. What it says is what your documents say, and every answer is stored with its source.
The chat visitor, the email, the Instagram DM and the text reply become one contact with one history and one set of orders behind it.
A segment of past customers pulled from the store, a reorder or win-back sequence by email and text, and replies worked by the agent rather than landing in an inbox.
Every send, reply, page view and order is recorded against a person and reported as a funnel, per agent and across all agents. This is the part that tells you whether the chat or the DMs are worth the attention, and what the reorder campaign brought in.
The funnel counts people rather than messages: how many customers the agent reached, how many replied, how many went on to visit the store, and how many converted, with the total value won and the median time to convert. Set a goal as a page rule on your order confirmation page, with a dollar value, and a win-back campaign reports what it sold, not how many emails it sent.
Below the funnel, a channel table shows where each customer first made contact and which channel they were on when they bought, and a pages table shows which product and policy pages known people read before ordering. One row per customer shows the whole journey: the chat in March, the order, the return question in April, the reorder text in July. Visit triggers close the loop: when a known customer returns to a product page and leaves, the agent tells you, or follows up after a delay on the channel they last used. Page goals and visit triggers need the one-line snippet on your store; conversations and marking a sale won do not.
Built from the cookie, email address and phone number attached to that contact, so activity months apart on different channels appears on one row.
Page goals and visit triggers require a one-line snippet on your website. Conversations, bookings and manually marking a deal won work without it.
Each of these is usually a separate app on the store, a separate seat or a separate person, and most of them are priced per ticket, per conversation, per contact or per seat. Here they are one plan.
| The job | What it normally takes | Bold Agent Kit |
|---|---|---|
| Answering "where is my order?" at any hour | A helpdesk app priced per ticket, or a person in the morning | Included, from the order |
| Live chat on the store that knows the size guide | A chat vendor priced per conversation or per seat | Included |
| Answering Instagram, Messenger and WhatsApp DMs | Whoever has the login, or another inbox app | Included, same agent, same inbox |
| Reading the store before replying | A person copying the order into the reply | Included, Shopify, WooCommerce, Wix, Squarespace, Stripe |
| Handing refunds and order changes to a person | Everything is handed to a person | Only the ones you named |
| Reorder and win-back emails to past customers | An email platform priced per contact | Included, from a store segment |
| Following up a known customer who came back to a product page | Another app, priced per contact | Included, with the snippet on your store |
| Knowing which channel produced the order | Attribution most stores do not have | Included, per channel and per agent |
Bold Agent Kit is $25 a month, or $200 a year, for the whole account: every agent, every channel, every customer, no per-ticket or per-contact price. The only other costs are your carrier's, for texts, and your AI provider's, typically a few dollars a month per agent, both billed to you at cost.
The same agent covers all of these. Many accounts run one per brand or one per store, each with its own mailbox, chat widget and knowledge base.
AI customer service for Shopify, WooCommerce, Wix, Squarespace or Stripe stores. Connect support@, the chat widget and the DMs, connect the store, and let the agent answer "where is my order?", "can I change the address?" and "how do I return this?" from the order and the policy, at any hour, handing the refund itself to you.
AI chat for online stores that sells. The visitor on the product page asks about sizing, materials, shipping to their country or when the colour is back, gets the answer from your material with the link to the right page, and is asked for an email address so the agent knows them next time.
The campaign to past customers that never gets built. Pull a segment out of the connected store, the ninety-day customers due to reorder, the people who bought last season and not since, and run a short email and text sequence at them, in the hours you set, with the agent working the replies. Not an abandoned-cart integration: a list you choose, worked properly.
Connect the tools you already run and the agent works them like an assistant would: it takes appointments straight into your calendar, writes notes and outcomes back to the CRM, and reads your store to see what somebody has bought before it answers them.
Bookings are real, not guesses. It is only ever given slots that are genuinely free, and it can only take one it actually offered — so it cannot invent a time or double-book you. The same connection pulls a segment of past customers into a list when you want to run a campaign at them.
HubSpot
GoHighLevel
Housecall Pro
ServiceTitan
Jobber
Google Calendar
Microsoft 365
Calendly
HubSpot Meetings
Zoho Bookings
Acuity
Cal.com
Square
Stripe
Shopify
WooCommerce
Wix
SquarespaceEach agent uses a model on your own API key, in the same way it sends from your own mailbox and your own phone number. Sixteen providers are supported: OpenAI, Anthropic, Gemini, xAI and Mistral; DeepSeek, GLM, Kimi, Qwen and MiniMax; Groq, Together, Fireworks and OpenRouter; and Ollama or any other OpenAI-compatible endpoint you host yourself.
Bring your own credentials and you own the whole stack: your model provider, your mailboxes, your carrier, your CRM. We charge for the software and nothing else — no token markup, no metering, no credit packs — so your provider bills you direct at their rates, usually a few dollars a month per agent.
OpenAI
Anthropic
Gemini
xAI
Mistral
DeepSeek
GLM
Kimi
Qwen
MiniMax
Groq
Together
Fireworks
OpenRouter
Ollama
Any OpenAI APIA new address sending forty cold emails a day gets filtered, and takes the domain with it. Mailboxes that opt into warm-up send each other ordinary mail on a ramp, starting at five a day. The receiving mailbox finds each message, moves it out of spam if it landed there, marks it read and replies to a share of them.
Each mailbox carries a health score out of 100 — SPF, DKIM and DMARC on the sending domain, seven days of real sends and bounces, and where its own warm-up mail is landing — with the reasons listed. A mailbox whose bounce rate or spam placement passes a threshold is pulled out of campaign rotation automatically, before it damages the domain.
Three steps. Inbound answering is a switch per channel; a campaign is created as a draft and shows you the whole plan before it sends anything.
Name it, choose a model and paste your API key. Then give it what it needs to answer a customer: your shipping and returns policies as documents, your size guide, your product FAQs as Q&A pairs, your delivery times by region and your support hours as data points, and the product, policy and tracking pages of your store it may link to.
Write the instructions last: how it should talk, what it may offer, and the exact situations in which it should stop and fetch a person. A refund, an order change, a damaged parcel and a chargeback are the usual four.
Add support@, the chat snippet for the store, the Instagram and Messenger accounts the ads run to, and a number if you text customers. Each one runs on your own account, so the reply comes from you and the reputation stays on your domain.
Then connect the store, Shopify, WooCommerce, Wix, Squarespace or Stripe, so the agent reads the order before it answers, and so a segment of past customers can be pulled into a list when you want to run a campaign at them.
Switch on auto-reply for email, chat and DMs and the agent starts answering from the store and the knowledge base. Refunds and changes come to your inbox as you instructed. Reply in any thread yourself and it stands down on that conversation until you hand it back.
For the reorder campaign, import the segment, build the sequence with the days, hours and time zone it may send, and read the whole plan on the review screen. Nothing leaves until you press Start, and you can pause it during a launch and resume it after.
One account runs unlimited agents, one per client, and nothing is shared between them. A knowledge base belongs to a single agent, and content from one agent is never used to generate replies for another.
Invite a client by email address and they get their own login, which opens onto the one agent you gave them: its conversations, its numbers, its analytics and a reply box. They cannot see your other clients, your API keys, your settings or your billing. Access is deny-by-default.
No seat tiers, no credit packs, no per-agent or per-channel pricing, and nothing held back behind an enterprise call.
| Agents | |
|---|---|
| How many | Unlimited — one per business, brand or job |
| Shared brain | The same identity, instructions and knowledge on every channel |
| Knowledge base | Documents, Q&A pairs, data points and pages of your own site |
| Isolation | One agent's content is never used to reply for another |
| Client seats | Invite a client into one agent, with their own login |
| Channels | |
| As many mailboxes per agent as you connect, rotated by campaigns | |
| Text messages | Nine providers — Twilio, Telnyx, SimpleTexting, Plivo, Vonage, Sinch, Bandwidth, MessageBird, ClickSend |
| Phone calls | Answering and dialling, with recordings and transcripts |
| Transcription | Google, or Deepgram nova-3 on your own key |
| Voices | Google, Amazon Polly and ElevenLabs, or your own ElevenLabs / Fish Audio account |
| Voice cloning | Record a voice in the browser and clone it on your ElevenLabs or Fish Audio key |
| Website chat | A widget on your site with your colour, image and greeting |
| Social DMs | Messenger, Instagram, WhatsApp, Telegram, LINE, Viber, Slack, Discord, Bluesky, Reddit, X |
| Inbox | |
| One list | Every channel's conversations together, newest first, tagged by channel |
| Filters | By channel, by mailbox or number, or by agent |
| Takeover | Reply yourself and the agent stands down on that thread |
| Hand back | Return the thread to the agent when you are done |
| Campaigns | |
| Multichannel sequences | Email, text and call steps in one campaign, each with its own timing |
| Send conditions | Send a step only if they opened, did not open, clicked or did not click |
| Schedule | The days, hours and time zone anything may be sent |
| Stop rules | A reply, a booking or an opt-out on any channel ends the sequence |
| Pacing | Per-mailbox and per-number hourly limits, pausable and resumable |
| Review before start | The full plan is shown; a campaign sends nothing until you start it |
| Templates | Email, text and call scripts, saved once and reused |
| Analytics | |
| Funnel | Reached, replied, visited, converted, plus value won and time to convert |
| By channel | Where each person started, and the channel they converted on |
| Pages | Which pages known people read, and how many of them converted |
| Journeys | One row per person: every message, visit, call and booking in order |
| Goals | A page rule or a manual "won", each with a dollar value |
| Triggers | A known person returns to a page — notify you, or send a follow-up |
| Open and click tracking | Recorded per campaign and added to that person's history |
| Integrations | |
| Calendars | Google, Microsoft 365, Calendly, Cal.com, Acuity, Zoho, Square, HubSpot Meetings |
| CRMs and commerce | HubSpot, GoHighLevel, Housecall Pro, ServiceTitan, Jobber, Stripe, Shopify, WooCommerce, Wix, Squarespace |
| Booking | Real open slots offered, and only an offered slot can be booked |
| CRM import | Import a segment of customers into a contact list |
| Deliverability and compliance | |
| Mailbox warm-up | Ramped sending across the network, with spam rescue and replies |
| Health score | SPF, DKIM, DMARC, bounce rate and inbox placement, with reasons |
| Auto-rest | A failing address is removed from rotation automatically |
| Unsubscribes | One click, honoured automatically, including on queued mail |
| Reply limits | One reply per thread, per-sender daily and per-channel hourly caps |
| Filtering | Bounces, out-of-office and no-reply addresses ignored |
| List building | |
| Contact extraction | Emails, phone numbers and social profiles, on any site. Unlimited. |
| Deep scan | Follows the pages of a domain most likely to carry contact details |
| Domain queue | Load a CSV of sites and work through them one at a time |
| Contacts and lists | Unlimited, by email or phone, with CSV import and export |
| AI | |
| Your own key | Sixteen providers, including any OpenAI-compatible endpoint you host |
| What we charge for AI | Nothing — no markup, no metering, no credit packs |
| On calls | Uses your provider's fastest model automatically |
| Account | |
| Platforms | Chrome side panel and web dashboard on one login |
| Members' forum | Six boards, visible only once you are signed in |
| Referral program | $50 a year per referral ($5 a month), recurring for the life of the account |
| Support | support@boldagents.co |
Billed monthly. No add-ons, no seat tiers. Cancel anytime.
$16.67 a month, billed once a year. No add-ons, no seat tiers. Cancel anytime.
From the store you connect. Shopify, WooCommerce, Wix, Squarespace and Stripe are supported, and with one connected the agent looks the customer up before it replies: what they bought, what is still open and what they are worth. A "where is my order?" is answered with the status of that order and the tracking page you allowed it to link to. If the customer is not in the store, or writes from an address the store does not know, the agent says what it can from your policies and asks for the order number rather than guessing. Every reply is stored with the record and the material it was generated from.
No, and that is deliberate. A refund, a cancellation, an address change or a damaged-parcel claim is the kind of message you tell it to hand over. Write the rule in its instructions and when a message matches, the thread lands in your inbox with the agent standing down on that conversation. You process the refund in the store, reply in the thread, and hand it back. The agent then answers that customer's next question as normal. Nothing it says about a refund is a promise it can make on its own; what it says is what you instructed.
It works with Shopify, WooCommerce, Wix, Squarespace and Stripe alike. The store connection does the same three things whichever you run: the agent reads the customer's orders before replying, a segment of customers can be pulled into a contact list for a campaign, and a goal on your order confirmation page reports what a campaign sold. Your help docs, size guide and policies are loaded the same way regardless of the platform, and the chat widget is the same one line of script on any storefront that lets you add a script tag.
Not in the way a cart-recovery app does. The agent does not see what is in a basket and does not send an automatic abandoned-cart email. What it does is two things you control. With the one-line snippet on your store, a visit trigger fires when a known customer returns to a page you named, such as a product page, and the agent either tells you or follows up after a delay on the channel they last used. And a campaign is a list you build, a segment of past customers pulled from the store or a CSV, worked on a schedule you set. Both are honest about what they are: page-based and list-based, not cart-based.
Email from any mailbox, with Gmail and Outlook on an app password and anything else as an SMTP and IMAP host. Website chat through the one-line widget. Social DMs on Messenger, Instagram, WhatsApp, Telegram, LINE, Viber, Slack, Discord, Bluesky, Reddit and X, each on your own app credentials, inside each platform's reply window. Text messages on your own number through one of nine carriers, and phone calls on Twilio if you want them. Auto-reply is a separate switch per channel, so a store can start with email and chat and add the DMs later. Every conversation lands in the same inbox, tagged with its channel.
They are treated as one person. Every handle seen for a contact, the browser cookie from the chat, the email address, the phone number from a text, the Instagram account id, is attached to one record, and when a new handle turns out to belong to an existing contact the two are merged and the history moves across. The agent reads that whole history before it replies, so the customer who asked about sizing in chat on Monday and emails about the delivery on Friday is not asked to explain themselves twice, and with the store connected the orders sit behind the same record.
Yes. Unlimited agents are included in the plan, each with its own identity, mailbox, chat widget, social accounts, store connection, knowledge base and analytics, and nothing is shared between them. A knowledge base belongs to one agent only, and content from one agent is never used to generate a reply for another, so two brands with different return policies never get each other's answers. An agency running stores for clients can invite each client into their own agent with a login that sees that agent's inbox and analytics and nothing else.
Nothing per conversation, ticket or contact. The plan is $25 a month or $200 a year for the whole account, with a 7-day free trial and unlimited agents, contacts and lists. You pay your AI provider for the model on your own key, one of sixteen supported, and your carrier for any texts, both at cost and typically a few dollars a month for a busy agent. Nothing is metered, marked up or sold as credits, and there is no percentage of the orders it helps sell.
One subscription, unlimited agents. What changes is the knowledge base, the channels and the instructions.
Connect support@ and the store, load the policies, switch on the chat, and see how it handles the questions that arrive after the warehouse has gone home.
7-day free trial · Cancel anytime